Secure boot enabled.
Device state - unlocked.
I tried to follow the Heisenberg tutorial to flash a custom Rom.
Finished the root. Decided I installed the wrong version of GApps. Went back to stock to redo the process.
Accidentally installed a 6p stock image instead of 5x. Then my troubles began.
I've tried a lot of different things. I don't have a full log of steps taken.
Have tried reflashing different 5x stock images. They flash fine but problem persists.
Problems:
1. Booting to Android bootloops
2. TWRP recovery GUI is non-responsive.
Fastboot works great.
Reflashing TWRP from fastboot doesn't help.
ADB access to recovery seems responsive, but I'm not sure whether commands are actually executing. For example running twrp factoryreset just hangs. All twrp commands do that.
I would like to perform a factory reset. I have TWRP backups that I could restore. I don't know how to do that from fastboot.
First download the full Nexus 5x stock rom from here: https://developers.google.com/android/nexus/images then boot your Nexus 5x into its bootloader then on your computer (I am assuming it's Windows) download 7zip from here: http://www.7-zip.org then right click the .tgz stock rom file you just downloaded on your computer then extract it with 7zip. Inside that you will find a .tar file. Extract that then you will find a zip file before extracting the zip file run the .bat file while your Nexus 5x is connected to your computer then hold down your shift key, right click and click open command window here (while you are in the folder where you extracted the zip) in the command window, terminal, CMD, whatever you like to call it then type fastboot -w (that does a factory reset) then type fastboot flash system system.img then fastboot flash recovery recovery.img than fastboot flash boot boot.img than fastboot flash cache cache.img then fastboot flash userdata userdata.img then fastboot flash vendor vendor.img then fastboot flash recovery recovery.img. You should be able to boot back into Android now but you will need to reflash twrp. Also download the any file for 6.0.1 not 7.0 because you will have to do some extra steps for that.
P.S. this MIGHT erase your twrp backups.
Thank You,
Sincerely VibraniumDroid
---------- Post added at 08:06 AM ---------- Previous post was at 08:05 AM ----------
leolittlebook said:
Secure boot enabled.
Device state - unlocked.
I tried to follow the Heisenberg tutorial to flash a custom Rom.
Finished the root. Decided I installed the wrong version of GApps. Went back to stock to redo the process.
Accidentally installed a 6p stock image instead of 5x. Then my troubles began.
I've tried a lot of different things. I don't have a full log of steps taken.
Have tried reflashing different 5x stock images. They flash fine but problem persists.
Problems:
1. Booting to Android bootloops
2. TWRP recovery GUI is non-responsive.
Fastboot works great.
Reflashing TWRP from fastboot doesn't help.
ADB access to recovery seems responsive, but I'm not sure whether commands are actually executing. For example running twrp factoryreset just hangs. All twrp commands do that.
I would like to perform a factory reset. I have TWRP backups that I could restore. I don't know how to do that from fastboot.
Click to expand...
Click to collapse
Tell me if this works
---------- Post added at 08:08 AM ---------- Previous post was at 08:06 AM ----------
Also after your done type fastboot -w again
vibraniumdroid said:
Tell me if this works
Click to expand...
Click to collapse
android stock version: MTC20F
flash-all.bat OKAY
fastboot -w OKAY
fastboot flash system system.img OKAY
fastboot flash recovery recovery.img OKAY
fastboot flash boot boot.img OKAY
fastboot flash cache cache.img OKAY
fastboot flash userdata userdata.img OKAY
fastboot flash vendor vendor.img OKAY
fastboot flash recovery recovery.img OKAY
fastboot reboot
RESULT: bootloop continues. fails to boot to android.
fastboot flash recovery twrp-3.0.2-1-bullhead.img OKAY
reboot to recovery mode
RESULT: GUI still unresponsive. No change.
Can only lock screen with power button.
vibraniumdroid said:
download the any file for 6.0.1 not 7.0 because you will have to do some extra steps for that.
Click to expand...
Click to collapse
I don't understand this line.
EDIT:
fastboot -w again
OKAY
No improvement.
Sorry typo
---------- Post added at 09:57 AM ---------- Previous post was at 09:57 AM ----------
Try reflashing the radio
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
vibraniumdroid said:
Sorry typo
---------- Post added at 09:57 AM ---------- Previous post was at 09:57 AM ----------
Try reflashing the radio
Click to expand...
Click to collapse
Try cyanogen recovery
vibraniumdroid said:
try...
Click to expand...
Click to collapse
Flashed radio, no change.
Cyanogen recovery interface functional.
Ran full factory reset. Wiped cache.
Able to navigate with physical buttons. Screen buttons still not working. Cannot use back button. Cannot exit menu.
Cannot reboot from adb due to loss of authorization when switching recoveries.
Rebooted with long power button press.
Wiped system.
Rebooted normally. Stuck on Google screen. I assume because I deleted the /system OS.
Reflashed stock using flash-all.bat. Still bootloops.
Reflashed CM recovery.
A CHANGE! Screen buttons now work.
Flashed TWRP recovery. Buttons work.
Copied TWRP backups to phone. They are for prior Android version, however.
Testing whether current version will boot. Nope; bootloops.
Restored backup. Attempted boot. Stuck on Google screen.
leolittlebook said:
Flashed radio, no change.
Cyanogen recovery interface functional.
Ran full factory reset. Wiped cache.
Able to navigate with physical buttons. Screen buttons still not working. Cannot use back button. Cannot exit menu.
Cannot reboot from adb due to loss of authorization when switching recoveries.
Rebooted with long power button press.
Wiped system.
Rebooted normally. Stuck on Google screen. I assume because I deleted the /system OS.
Reflashed stock using flash-all.bat. Still bootloops.
Click to expand...
Click to collapse
try to reflash really all manually (bootloader and so on) also try to format your userdata and then reflash it (will wipe internal storage)
Thargorsson said:
try to reflash really all manually (bootloader and so on) also try to format your userdata and then reflash it (will wipe internal storage)
Click to expand...
Click to collapse
New after you posted:
Reflashed CM recovery.
A CHANGE! Screen buttons now work.
Flashed TWRP recovery. Buttons work.
Copied TWRP backups to phone. They are for prior Android version, however.
Testing whether current version will boot. Nope; bootloops.
Restored backup. Attempted boot. Stuck on Google screen.
I will try what you suggest.
how do I make these lines:
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
instead of adding a second post?
Thargorsson said:
try to reflash really all manually (bootloader and so on) also try to format your userdata and then reflash it (will wipe internal storage)
Click to expand...
Click to collapse
wiped all from twrp. said no OS.
rebooted to fastboot. ran flash-all.bat for bullhead-mtc20f
Rebooted into android bootloop.
flashed all manually.
failed midway through on system transfer. switched to different usb cable. worked.
result: bootloop.
redoing with new wire.
flash-all.bat result - bootloop.
manually flashed all. result: bootloop.
leolittlebook said:
how do I make these lines:
---------- Post added at 09:58 AM ---------- Previous post was at 09:57 AM ----------
instead of adding a second post?
wiped all from twrp. said no OS.
rebooted to fastboot. ran flash-all.bat for bullhead-mtc20f
Rebooted into android bootloop.
flashed all manually.
failed midway through on system transfer. switched to different usb cable. worked.
result: bootloop.
redoing with new wire.
flash-all.bat result - bootloop.
manually flashed all. result: bootloop.
Click to expand...
Click to collapse
did you really ran "fastboot earease userdata"? and then "fastboot flash userdata userdata.img"
Thargorsson said:
did you really ran "fastboot earease userdata"? and then "fastboot flash userdata userdata.img"
Click to expand...
Click to collapse
I'm not sure whether I specifically ran the erase command manually on this iteration. I ran those exact two commands just now. It's bootlooping still.
leolittlebook said:
I'm not sure whether I specifically ran the erase command manually on this iteration. I ran those exact two commands just now. It's bootlooping still.
Click to expand...
Click to collapse
Hanging on what? google logo or bootanimation.
Youve tried LG download mode? (power + volume up, then plug usb into phone).
See https://www.youtube.com/watch?v=_47Y-yOTF8k
By the way try a full restore and after lock the bootloader.
It doesn't hang. It shows the normal sequence of GOogle screen and colored dots, then reboots.
I've accessed LG download mode but don't know what to do with it.
I assume you mean to follow these instructions:
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
leolittlebook said:
It doesn't hang. It shows the normal sequence of GOogle screen and colored dots, then reboots.
I've accessed LG download mode but don't know what to do with it.
I assume you mean to follow these instructions:
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
Click to expand...
Click to collapse
I gave those directions a try and I'm back at the bootloop with a locked bootloader. I don't know how I'm supposed to flash anything with a locked bootloader, aside from those TOT files, which haven't worked yet... sigh. I really appreciate how much help the community here has been though, hopefully we can get this sorted out on our devices.
leolittlebook said:
I'm not sure whether I specifically ran the erase command manually on this iteration. I ran those exact two commands just now. It's bootlooping still.
Click to expand...
Click to collapse
Could you try: fastboot flash vendor (name of MTC20F vendor) then try restoring your boot, system, and data for your nandroid?
Sent from my Nexus 5X using Tapatalk
Huskehn said:
I gave those directions a try and I'm back at the bootloop with a locked bootloader. I don't know how I'm supposed to flash anything with a locked bootloader, aside from those TOT files, which haven't worked yet... sigh. I really appreciate how much help the community here has been though, hopefully we can get this sorted out on our devices.
Click to expand...
Click to collapse
OTAs can be sideloaded with a locked bootloader.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Could you try: fastboot flash vendor (name of MTC20F vendor) then try restoring your boot, system, and data for your nandroid?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Phone shows up on LGUP. Loathe to try the other thread's directions if it might lock my bootloader.
Tried your suggestion. Didn't work.
flashed vendor stock, then restored nandroid backup all.
android boot sticks on google screen.
Followed these instructions through step 15
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
Still had bootloop. Cycling through colored dots. Couldn't continue, because couldn't unlock phone's bootloader.
Also can't flash images, because no TWRP recovery anymore.
Seems I'm dead in the water, yes?
Not a big change.
ma
leolittlebook said:
Followed these instructions through step 15
http://forum.xda-developers.com/nexus-5x/help/unbrick-nexus-5x-t3438133
Still had bootloop. Cycling through colored dots. Couldn't continue, because couldn't unlock phone's bootloader.
Also can't flash images, because no TWRP recovery anymore.
Seems I'm dead in the water, yes?
Not a big change.
Click to expand...
Click to collapse
why you cant access the bootloader?
may not. you now have a full stock phone with locked botloader. maybe you contact google at this point.
Thargorsson said:
why you cant access the bootloader?
Click to expand...
Click to collapse
because my DEVICE STATE - is now locked
I think I flashed the international tot file, whereas this phone is a different Hong Kong version.
see here:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740/page13#post68381176
Thargorsson said:
why you cant access the bootloader?
Click to expand...
Click to collapse
I think he means he has bootloader access, but it's locked (that is how my phone currently is as well). You can only flash valid/signed zips from there, not custom ROMs or recoveries.
My goal now at the very least is to get the bootloader unlocked again.
Related
I've got the Sprint HTC One M8. Bootloader unlocked, rooted, S-off, CWM recovery.
I'm trying to flash ViperOne M8 and done just about everything I can think of but without any luck. It completes install, but upon reboot, it boots back to the bootloader. At that point, I'm able to get into recovery but can't boot into ROM.
I've been trying ViperOne 1.6.0, and currently downloading an older version to see if that'll work.
I tried Android Revolution HD and InsertCoin. Both worked fine, so I know I'm able to flash custom ROMs just fine, but not ViperOne. Any ideas?
jlaprevote said:
I've got the Sprint HTC One M8. Bootloader unlocked, rooted, S-off, CWM recovery.
I'm trying to flash ViperOne M8 and done just about everything I can think of but without any luck. It completes install, but upon reboot, it boots back to the bootloader. At that point, I'm able to get into recovery but can't boot into ROM.
I've been trying ViperOne 1.6.0, and currently downloading an older version to see if that'll work.
I tried Android Revolution HD and InsertCoin. Both worked fine, so I know I'm able to flash custom ROMs just fine, but not ViperOne. Any ideas?
Click to expand...
Click to collapse
I was having problems with some ROMs as well and I was able to fix it by doing an "advanced wipe" in TWRP and wiping the cache, dalvik, data and system. The default wipe in TWRP does not wipe system.
Not sure if CWM does this or if you have similar options, but you might want to make sure you wipe system.
chobungus said:
I was having problems with some ROMs as well and I was able to fix it by doing an "advanced wipe" in TWRP and wiping the cache, dalvik, data and system. The default wipe in TWRP does not wipe system.
Not sure if CWM does this or if you have similar options, but you might want to make sure you wipe system.
Click to expand...
Click to collapse
Yeah, I've tried wiping everything multiple ways. I actually tried to switch recovery from CWM to TWRP so I could do their advanced wipe, but it wouldn't work.
I attempted to change to TWRP using fastboot (adding TWRP to fastboot folder, and using the "fastboot flash recovery" command), but when I did that, nothing happened. Command prompt went to the next line without any confirmation or error.
jlaprevote said:
Yeah, I've tried wiping everything multiple ways. I actually tried to switch recovery from CWM to TWRP so I could do their advanced wipe, but it wouldn't work.
I attempted to change to TWRP using fastboot (adding TWRP to fastboot folder, and using the "fastboot flash recovery" command), but when I did that, nothing happened. Command prompt went to the next line without any confirmation or error.
Click to expand...
Click to collapse
Hmm that's odd. Did you try using adb sideload? If that doesn't work I guess I would redownload the ROM (or maybe an older version), make sure to verify the md5, and try installing again.
Sorry I can't be of much help! Good luck!
Update: Resolved!
Tried previous versions of ViperOne with no luck.
Tried to flash TWRP again and I was able to do so just fine. Flashing with TWRP successfully installed ViperOne! Very happy with it.
Hmm... I have the Sprint M8 H/K edition and having the same problem ??
Using TWRP and did advanced wipe (cache, dalvik, data and system)
Also tried flashing both "stock" version and "viper" version in the aroma options and still same thing... goes through the flash process and then just boots into HBOOT???
I downloaded twice and also checked the md5 so that's not the issue
jlaprevote said:
Update: Resolved!
Tried previous versions of ViperOne with no luck.
Tried to flash TWRP again and I was able to do so just fine. Flashing with TWRP successfully installed ViperOne! Very happy with it.
Click to expand...
Click to collapse
Which version of TWRP did you use to resolve your issue?
Thanks!
Please help!
jlaprevote said:
Update: Resolved!
Tried previous versions of ViperOne with no luck.
Tried to flash TWRP again and I was able to do so just fine. Flashing with TWRP successfully installed ViperOne! Very happy with it.
Click to expand...
Click to collapse
Can you explain again what you did?
I'm trying to restore a TWRP backup that included ViperOne M8, but it just gets stuck in boot (never see desktop). It doesn't reset to HBOOT, but again, just stays on boot screen forever. Both ViperOne M8 TWRP backups I have don't work, but when I flash a pre-ViperOne M8 backup, it works. But now I'm back to like a month ago. I don't understand why my ViperOne M8 backups don't work, but the pre-VM8 one does.
Please help, if you can!
Thank You,
RockStar2005
does your current firmware match the firmware on the nandroid backup you are trying to restore?
remember, If you upgraded your firmware to 4.4.3, and you are restoring a nand that was made with 4.4.2 firmware, you could have issues
wase4711 said:
does your current firmware match the firmware on the nandroid backup you are trying to restore?
remember, If you upgraded your firmware to 4.4.3, and you are restoring a nand that was made with 4.4.2 firmware, you could have issues
Click to expand...
Click to collapse
It turns out the version I had of TWRP was corrupted. I'm going to delete it. So I guess I'm good now.
Thank You,
RockStar2005
I have the same problem! I just rooted my m8, flashed TWRP 2.8.1.0on my phone.
Flashed viper 3.2.1 (flashed successful) . but it boots into hboot mode everytime.
trekdrop said:
I have the same problem! I just rooted my m8, flashed TWRP 2.8.1.0on my phone.
Flashed viper 3.2.1 (flashed successful) . but it boots into hboot mode everytime.
Click to expand...
Click to collapse
did you erase the cache after flashing TWRP ?
fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot erase cache
fastboot reboot-bootloader
clsA said:
did you erase the cache after flashing TWRP ?
fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes.
Treid diffrent trwp... still no luck
Luckily i can restore everything with my nandroid back up.
trekdrop said:
Yes.
Treid diffrent trwp... still no luck
Luckily i can restore everything with my nandroid back up.
Click to expand...
Click to collapse
are your versions of adb and fastboot up to date ?
https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip?dl=0
clsA said:
did you erase the cache after flashing TWRP ?
fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Which version trwp do i need?
trekdrop said:
Which version trwp do i need?
Click to expand...
Click to collapse
your TWRP is fine, that's what I'm using
clsA said:
your TWRP is fine, that's what I'm using
Click to expand...
Click to collapse
i used this one: openrecovery-twrp-2.8.1.0-m8_whl.img because i have a sprint (HBOOT 3.19.0.0000)
I now used yourspenrecovery-twrp-2.8.1.0-m8
and now it boots ok... but after i enter my pin number it goes to htc screen (the white one whit green htc letters)
trekdrop said:
i used this one: openrecovery-twrp-2.8.1.0-m8_whl.img because i have a sprint (HBOOT 3.19.0.0000)
I now used yourspenrecovery-twrp-2.8.1.0-m8
and now it boots ok... but after i enter my pin number it goes to htc screen (the white one whit green htc letters)
Click to expand...
Click to collapse
don't flash a recovery not made for your phone ! ... If you have Sprint use the Sprint recovery
the question was what version of fastboot do you have and use, and did you erase cache after flashing the recovery
clsA said:
don't flash a recovery not made for your phone ! ... If you have Sprint use the Sprint recovery
the question was what version of fastboot do you have and use, and did you erase cache after flashing the recovery[/QUOT
s-on
Hboot 3.19
And yes i did erase cache.
---------- Post added at 10:32 AM ---------- Previous post was at 10:00 AM ----------
This is a screenshot from my bootloaderscreen.
http://i57.tinypic.com/1zdpz7a.jpg
Click to expand...
Click to collapse
trekdrop said:
clsA said:
don't flash a recovery not made for your phone ! ... If you have Sprint use the Sprint recovery
the question was what version of fastboot do you have and use, and did you erase cache after flashing the recovery[/QUOT
s-on
Hboot 3.19
And yes i did erase cache.
---------- Post added at 10:32 AM ---------- Previous post was at 10:00 AM ----------
This is a screenshot from my bootloaderscreen.
http://i57.tinypic.com/1zdpz7a.jpg
Click to expand...
Click to collapse
that's not the bootloader of a Sprint phone ... M8_UL is a GSM Phone, I hope the Sprint recovery you flashed didn't screw up your partitions
Click to expand...
Click to collapse
Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.
I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Curious, what happens if you flash recovery.img into the boot partition?
It's a nexus device so you should be ok with warranty and an unlocked bootloader.
Sent from my Nexus 9 using XDA Free mobile app
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
try clean flashing a stock image in fastboot. wipe everything.
k.s.deviate said:
try clean flashing a stock image in fastboot. wipe everything.
Click to expand...
Click to collapse
I manually flashed everything that the flash-all.bat file does, twice. I'm going to try to get it replaced with the warranty.
I can't help but think it is a hardware problem given that everything seems to work perfectly flashing it with factory images and then nothing happens when I try to boot it up.
sfhub said:
Curious, what happens if you flash recovery.img into the boot partition?
Click to expand...
Click to collapse
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
redg8gt said:
... is this different than flashing using fastboot? I flashed the stock recovery several times and redownloaded and tried again. TWRP didn't work either.
Click to expand...
Click to collapse
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I think you mean fastboot boot recovery.img. Not fastboot flash boot recovery.img. That'll hopefully boot you into recovery without actually flashing it.
Click to expand...
Click to collapse
Nope, I actually meant what I wrote. I wanted to test the theory that the emmc in the recovery partition is damaged and the easiest way to do that is to flash the recovery onto the boot partition, which might not be damaged.
The partitions are the same size so you won't damage the phone, you'll just cause the phone to boot the kernel which autostarts recovery instead of the kernel that tries to boot android.
fastboot boot recovery.img will just load recovery straight into memory across the USB cable. It won't allow diagnosis of whether the emmc in that section is damaged.
Ok, but if the EMMC is bad in any partition the device is still hosed.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Ok, but if the EMMC is bad in any partition the device is still hosed.
Click to expand...
Click to collapse
Actually that isn't necessarily true. While Emmc can have catastrophic failure, Emmc often has partial failure.
We discovered this when google added SecureTRIM to the kernel on the Samsung Epic Touch. The emmc was getting corrupted by this change and we found that we could lock out certain sections of the emmc by adjusting partition tables and have a functioning phone.
I figure this phone is going back for RMA anyway, so might as well get some useful failure analysis out of it.
redg8gt said:
My phone started acting really laggy today and began restarting by this evening. The restarts became more and more frequent and now I can't do anything with it. The phone is unlocked and was rooted with xposed. I can get into the bootloader and fastboot works fine. I cannot, however, get into recovery. The phone displays the unlocked warning, then the Google screen with the unlocked symbol on the bottom, and then it repeats.
Through fastboot, I flashed the newest update without wiping my data - didn't work. Then I extracted the zip file and flashed everything (radio, bootloader, recovery, system, etc..) and no change. I repeated the process with an older version just to see if there was a difference.. nope. Everything installs just fine but I get the same bootloop and inability to get into recovery. I also flashing TWRP, but no change.
Am I screwed? I voided my warranty when I unlocked the bootloader, right?
Click to expand...
Click to collapse
Try to do a factor oem lock and then unlock to completely wipe the phone , then try to adb sideload stock 6.0.1 ?
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Here is the link, http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740. Member bitdomo has been a savior on many nexus devices.
Sent from my Nexus 9 using XDA Free mobile app
The phone is indeed heading back to Google for a (refurb) replacement. I had tried to directly boot into recovery using both the stock recovery and twrp and had the same result. For the sake of science, I will try the LG tool later and see if I can get it working.
sfhub said:
What I was suggesting is
fastboot flash boot recovery.img
previously you would have been trying
fastboot flash boot boot.img
fastboot flash recovery recovery.img
I was suggesting flashing your boot partition using the recovery.img on the assumption that the recovery partition emmc might be damaged along with parts of the user partition.
If the boot partition area of the emmc is still good, flashing the recovery.img in there will allow recovery to startup.
Recovery and boot are basically 95% the same image. The partitions sizes are the same. So basically from a flashing standpoint, they are interchangeable.
The difference is the boot partition is automatically selected by the boot loader, while the recovery partition needs special button presses to start.
If you flash the boot partition with the recovery.img, then recovery should just start up automatically without special button presses.
Click to expand...
Click to collapse
I just tried this. Still bootloops.
Siddheshpatil said:
okay here's what you need to do:
1) Try the LG UP tool. There's a thread somewhere in 5x forums. 90% chances are that it will fix everything as it repartitions back to stock.
2) If the above does not work, then do this: Download the platform tools, shift right click, open command prompt, switch off the phone, connect it to pc and power on. Once you are past the google logo, type adb devices, it should show up there on the pc, if it doesn't then try the command again. once the device shows up on the command prompt, type adb logcat, once you have around 3-4 minutes of boot up logs on the cmd, copy everything and post it here, one of us will take a look and tell you what exactly is the problem.
Click to expand...
Click to collapse
1) I think I'm going to keep it broken so there is no issue whenever I send it in. I wish I would have waited to call Google. I'm curious now whether that would have worked.
2) There is no past the Google logo.. it resets before it gets past it.
redg8gt said:
I just tried this. Still bootloops.
Click to expand...
Click to collapse
Could you try 2 other things
1) try the fastboot boot recovery.img suggested earlier to confirm your recovery image can boot across USB cable
2) if not, please post a SHA1 hash for your recovery.img and which Android version you got the image from
This will just confirm that the recovery image that you are using is bootable in absence of the EMMC and if not, confirm whether the recovery.img is corrupted or not.
I experienced something similar when I moved from MM to N without wiping data. The data partition got encrypted even though I flashed that fedpatcher. Just couldn't get into twrp beyond its splash screen. The issue here might be unrelated, but I'd suggest a format userdata.
I got this problem a month ago , tried wiping everything and flash stock using fastboot command , then i got 9008 mode .
No recovery no downloads mode no fastboot . (Sometimes can go to fastboot try flash using nrt / manually , nothing happend)
Hello.
I would appreciate some help with this ...
I followed the 'How to Install CyanogenMod on the HTC One (M8) ("m8")' on the Cyanogen wiki and everything seemed to be going normally until I get to step 8, 'reboot the device into recovery'. Whenever I do, either by powering down and holding the Volume Down and Power buttons until HBOOT appears, then navigating to Recovery and selecting it - OR by simply navigate to HBOOT > Recovery directly after flashing the recovery, it says it is booting into recovery in pink text but then just goes straight to the Fastboot Menu.
I obtained S-Off using Sunshine and recovery was flashed as a root user in linux - both without any hitches. I tried this with both the twrp-2.8.7.0-m8.img linked to by the Cyanogen wiki and with the latest image from twrp, twrp-3.0.2-0-m8.img, with the same result. USB Debugging is on.
I'm attaching pics of the recovery flash dialogue from the linux terminal and of the fastboot screen that keeps coming up.
What am I doing wrong/missing here guys? Why can't I get into recovery??
Many thanks.
I still can't figure this out. Can anyone help?
krisbo9000 said:
I still can't figure this out. Can anyone help?
Click to expand...
Click to collapse
as your bootloader is outdated it may not enter to recovery. try another low version. and also change CID to super CID. you can flash MM firmware and use twrp 3.0.2-0. what is your current MID?
try fastboot boot recovery twrp.****.img
id also try a different recovery as well as updating firmware as suggested.
I changed the CID to a super CID and then flashed TWRP 3.02-0 and it worked!
Thanks so much for the help.
umesh.lk said:
as your bootloader is outdated it may not enter to recovery.
Click to expand...
Click to collapse
TWRP 2.8.7 should work fine on LP firmware.
---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------
krisbo9000 said:
I changed the CID to a super CID and then flashed TWRP 3.02-0 and it worked!
Click to expand...
Click to collapse
I don't see what SuperCID would have to do with anything. Possibly a placebo.
Often fastboot erase cache, and installing TWRP again, will fix the random issue of not being able to boot into TWRP.
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Wrong section
Hacker101 said:
I am no longer able to boot into my recovery. TWRP nor stock / default. I am on a custom ROM. I am on 7.1.2 root with magisk 12. I have tried all the fastboot commands to live boot into recovery. I have tried TWRP official app. I have tried FlashFire. Everytime I try to boot into my recovery my phone just reboots back into the OS.
Click to expand...
Click to collapse
So you have tried booting into the bootloader and entered "fastboot boot twrp.img" in adb?
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Alcolawl said:
This happens to me all the time. Using the advanced reboot menu on my ROM or "adb reboot recovery" while connected to my PC just results in the phone booting back into the OS. Pretty annoying. It has to have something to do with the Slots.
Anyways, to get around this, disconnect the phone from any power source, turn the phone completely off, wait 5-10 seconds, then press and hold Vol Down + Power to get to the bootloader. Then use the volume keys to select Recovery Mode and press power to boot into recovery. This method works every time for me. If this does not work for you or results in some other screen/error/whatever other than booting into TWRP, then you must live boot (as suggested in the above post) into TWRP and flash TWRP RC2.
Click to expand...
Click to collapse
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Hacker101 said:
I have done this 100+ times. Booting into recovery using any method does not work. Including live booting.
Click to expand...
Click to collapse
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
TheBobMiller said:
If you are still able to access the bootloader, I would suggest flashing a factory image (removing -w if you want to keep your data) with the flash-all.bat. It sounds as if your recovery partition has been removed somehow making it unable to be booted into. Perhaps flashing the factory image will fix your partitions and solve the problem. It's worth a shot I guess if you can't access it at all. Good luck to you!
Click to expand...
Click to collapse
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Hacker101 said:
How am I supposed to flash a factory image if I can't flash anything? Plus I am on a Linux computer not windows. Isn't .bat windows? Would I need a .sh type of command?
Click to expand...
Click to collapse
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
TheBobMiller said:
The factory image flashes in bootloader mode and should correct any issue you have. You have to install the Android SDK platform on your Linux machine. Go to this link https://developer.android.com/studio/index.html#tos-header and scroll down to almost the bottom for just the command line tools and follow the instructions to install. Then go to https://developers.google.com/android/images and download the factory image you want to flash and follow the instructions in that link to flash. I don't have a Linux machine myself, but I believe the process is fairly similar and it should work just fine.
Click to expand...
Click to collapse
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
Don't worry about the Thanks, cause I'm sure others have contributed more. Sorry I'm not more familiar with the Linux instructions!
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Hacker101 said:
Sweet I'll give it a try when I get home later. We got a nasty storm blowing in so I may not get to it today. Also I'll remember to Thank that post tomorrow lol limited to eight a day. When you have 100+ people helping you out at once it's hard to thank each one.
Click to expand...
Click to collapse
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
jkashuba07 said:
Ok having the same issue as OP. A and B slots do not allow me to boot into recovery mode. It just immediately restarts as soon as the white Google splash screen appears. I have just done a factory reset with N2G47O. After complete, the stock default recovery works fine. I booted TWRP from fast boot to install the latest, issue came again. Trying to get into recovery mode just causes it to bootloop until you hold the volume down button to get bootloader up to boot to system instead. I am downloading and will flash NOF27D (last 7.1.1) to see if I can reinstall twrp from that. I can confirm that installing twrp when on that image worked. Will report back...
Click to expand...
Click to collapse
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
TheBobMiller said:
I forgot to ask if you were on the latest May security update. If you were on that version then you need to use the Android Verified Signer.zip from chainfire after you flash twrp. What version are you running?
Click to expand...
Click to collapse
Yes I was on May.. Do you have link to Verified Signer?
jkashuba07 said:
Ok, I can confirm after doing factory reset to NOF27D I was able to reinstall TWRP and boot to it successfully
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Yes I was on May.. Do you have link to Verified Signer?
Click to expand...
Click to collapse
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
Thank you, and will do.. yes chainfire has done a lot of good work, definitely have appreciated him over the years
TheBobMiller said:
Here is the link to the verifiedbootsigner.zip from Chainfire: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Make sure you give him some Thanks and Donate if possible! He has earned plenty of both from all of us Android users!
Instructions: Anytime you flash anything that affects the boot partition (ie. twrp, rom, kernel, etc), make sure to flash the boot signer zip at the end of the flashing before a reboot.
Click to expand...
Click to collapse
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Hacker101 said:
That's only for May and so on correct? I am on April. Heard nasty things form root uses about root screwing up, bootloader problems, etc. So I stayed away from May and stayed on April.
Click to expand...
Click to collapse
Correct. Only the may bootloader requires the extra zip file to be flashed. I am still on April but I have heard people not having any problems and some having nothing but problems from May. I think I'm going to give it a try tomorrow and see how it goes.
Edit: Tried the May bootloader and couldn't get it to boot a custom rom or TWRP, so I went back to April after flashing the Android O Beta and playing with it for a couple of hours. I feel that the Beta is still too early for a daily driver, but it was nice to mess around with some of the features we will have once this OS is released.