stockOpo Fails
nebucaz opened this issue · 8 comments
At line
fastboot reboot-bootloader
script fails with message
which results in bricked device
tried to rund fastboot with sudo, didi not help
Where does it fail?
https://github.com/offensive-security/nethunter-LRT/blob/master/stockOpoFlash.sh#L46
What message did it say? Can you go into recovery? Can you go into fastboot?
The phones/devices are very difficult to brick. You should at least be able to get into fastboot. (To get into fastboot hold volume down and power I believe)
fastboot reboot-bootloader how can a reboot brick a device dear?
Sorry for being unprecise, it fails at line 59 of https://github.com/offensive-security/nethunter-LRT/blob/master/stockOpoFlash.sh#L46 .
When running stockOpoFlash.sh, things go well until
[...]
Rebooting into bootloader
Rebooting into bootloader DONE
Flasing Stock Rom
!!!! DONT UNPLUG THE DEVICE !!!!
target reported max download size of 536870912 bytes
sending 'sbl1' (273 KB)...
OKAY [ 0.013s]
writing 'sbl1'...
OKAY [ 0.014s]
finished. total time: 0.028s
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.006s]
finished. total time: 0.010s
target reported max download size of 536870912 bytes
sending 'aboot' (445 KB)...
OKAY [ 0.019s]
writing 'aboot'...
OKAY [ 0.016s]
finished. total time: 0.035s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for any device >
I let the thing run and fans went up - Activity-Monitor shows 80% CPU for a "fastboot" -process. After 1h or so, console showed a timeout error, after another 30min console repeats following string "ERROR: Could not create iterator." At this point I pressed Ctrl-C and the device was left "bricked": no recovery, no fastboot mode available. I had to use some chinese-tools to get the device running again. Put into developer-mode, activated USB-Debug and tried second time. Same effect, chinese-utility restore again. Third try: I executed all commands manually, all the fastboot-commands using sudo (I read here http://forum.xda-developers.com/showthread.php?t=874511, that devices will not be recognized, if fastboot is not run as root). Again: < waiting for any device > was the lsat thing I saw.
That was the point I posted the issue (and went to bed)
Thank you for the detailed response. So running commands manually you still had same issue?
yep, third try was manually executing along the sequence of the script. After the command in line 59 the phone gets black and only commits a short vibration.
My system is a MacBook Air (13-inch, Mid 2011) running OS X 10.11.2 (15C50) with Android Studio with Android SDK 6.0 in $PATH (for ads and fastboot commands). Is it possible, that I have the wrong image (cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18)?
Ok I found.