Newflasher stucks on MacOS Ventura with M1
qwerzl opened this issue · 1 comments
qwerzl commented
Hi, another M1 issue again...
I've self-built Newflasher with the following makefile modifications.
ifeq ($(OS),Darwin)
CFLAGS+= -I/opt/homebrew/Cellar/libusb/1.0.26/include/libusb-1.0 -L /opt/homebrew/Cellar/libusb/1.0.26/lib
LIBS+=-lusb-1.0
endif
Build process was successful. However, it seems that it gets stuck while running. More specifically, it stuck after the dump trim area selection, no matter which option I give.
Here is a complete log:
> ./newflasher
--------------------------------------------------------
newflasher v55 by Munjeni @ 2017/2020
--------------------------------------------------------
Determining available free space:
Available space to caller = 17602452 MB
Total space on current drive = 194008576 MB
Free space on drive = 17602452 MB
Device properties:
bus number: 0
port path: 1 (from root hub)
speed: 480 Mbit/s (USB HighSpeed)
Reading device descriptor:
length: 18
device class: 0
S/N: 0
VID:PID: 0xFCE:0xB00B
bcdDevice: 0x100
iMan:iProd:iSer: 1:2:0
nb confs: 1
Reading configuration descriptors:
nb interfaces: 1
interface[0]: id = 0
interface[0].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0xFF 0x42 0x3
endpoint[0].address: 0x81
max packet size: 0x200
polling interval: 0x0
endpoint[1].address: 0x01
max packet size: 0x200
polling interval: 0x1
Set configuration: succed.
Claiming interface 0: succed.
Reading string descriptors:
String (0x01): "Google"
String (0x02): "Android"
Do you want to keep userdata? Type 'y' and press ENTER to confirm, or type 'n' to erase userdata.
y
Reboot mode at the end of flashing:
type 'a' for reboot to android, type 'f' for reboot to fastboot, type 's' for reboot to same mode, type 'p' for poweroff, and press ENTER.
s
Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n' and press ENTER to skip.
Do in mind this doesn't dump drm key since sake authentifiction is need for that! But it is recommend to have dump in case hard brick!
y
qwerzl commented
Ah sorry seems that it was because my device got stuck. Fastboot commands didn't work either. It worked after rebooting. Closing this issue. BTW thanks for your great work!