Develop Bugs

[Q] Stuck on Google boot Logo

I downloaded Nexus Toolkit 7.9 and ran a factory flash and unroot. Now im stuck on this Google boot screen. Iv'e tried to go into recovery nothing but boot logo. Ive tried doing almost every option. What else can I try? Help Please.

Advice not use toolkits, but that's your choice
Boot to fastboot and make sure your still unlocked, if not
fastboot oem unlock
Then wipe partitions again
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now flash new recovery
fastboot flash recovery nameofrecovery.img
Now boot to new recovery and go to advanced
Choose adb sideload
adb sideloade romofchoice.zip
Then probably need gapps
adb sideload gapps.zip
Now rebbot to ROM
These steps are to get you up and running with a custom ROM if you want stock unroofed than from fastboot lock bootloader and flash stock ROM of choice
Sent from my Nexus 7 using XDA Premium 4 mobile app

s6lin9s said:
I downloaded Nexus Toolkit 7.9 and ran a factory flash and unroot. Now im stuck on this Google boot screen. Iv'e tried to go into recovery nothing but boot logo. Ive tried doing almost every option. What else can I try? Help Please.
Click to expand...
Click to collapse
I've had the same issue and am still having it. Your tablet must be like mine where it doesn't like the new kitkat bootloaders. No one has been able to help me so far yet either so I will watch this thread as well

you can follow the instruction in this thread. I got boot loop too. And this tool worked like a charm
http://forum.xda-developers.com/showthread.php?t=2381582

Stuck in bootloader. Bootloop from recovery.

I was flashing the MaximusHD ROM with the new layout and in the middle of flashing my HOX rebooted and got stuck in a boot loop and now when I try to boot into recovery it just shows the splash screen of the recovery and reboots again and goes into a bootloop. I only have access to the bootloader. Please if someone can help as soon as possible I would be highly grateful.

ehte92 said:
I was flashing the MaximusHD ROM with the new layout and in the middle of flashing my HOX rebooted and got stuck in a boot loop and now when I try to boot into recovery it just shows the splash screen of the recovery and reboots again and goes into a bootloop. I only have access to the bootloader. Please if someone can help as soon as possible I would be highly grateful.
Click to expand...
Click to collapse
run the command from cmd fastboot erase cache when you are in fastboot mode and then try to go in recovery

Thant said:
run the command from cmd fastboot erase cache when you are in fastboot mode and then try to go in recovery
Click to expand...
Click to collapse
Tried it. Doesn't work. Tried flashing another recovery. Tried factory reset from bootloader. Nothing seems to work. It still won't boot into recovery.

Not being able to boot into recovery mode

My problem is that when I boot into fastboot and put the option to boot recovery mode It takes me back to fastboot. I able to boot normally. ASUS_Z00A-2.20.40.184

any solution? plss

p_machado said:
any solution? plss
Click to expand...
Click to collapse
install latest update it will fix recovery or flash it manually

I'm having a similar problem. I cannot boot into recovery or install any upgrades. Currently using UL-Z00A-WW-2.20.40.206-user.
Booting into the normal OS works fine. I can use the phone. But I cannot boot into recovery.
adb reboot recovery
... throws the phone into a bootloop. Recovery fails to load for some reason. I tried flashing different versions of TWRP, and the stock recovery.img, but nothing seems to work.
Anyone else facing this?

Z2 can't boot into recovery.

Hey guys. So here's the thing. I unlocked the zuk's z2 bootloader using the standard method (fastboot -i 0x2b4c flash unlock unlock_bootloader.img, with the img they sent me via email, and then fastboot -i 0x2b4c oem unlock-go), and then I went to flash the TWRP recovery. I downloaded the recovery image from the official twrp website and proceeded to flash it with "fastboot -i 0x2b4c flash recovery twrp.img". The flashing was successful. But before restarting the device, I chose the option to boot into recovery, so that the original recovery wouldn't overwrite TWRP. However, the phone does not boot into the recovery, ever. It "shuts down", tries to boot into recovery, and without showing anything on the screen simply restarts to the normal system. Even flashing a stock ROM in the phone with MiFlash (relocking the bootloader) and trying to boot into the stock recovery does not work.
And, the only method to boot into any recovery that works is to use "fastboot -i 0x2b4c boot recovery.img". But as we know this isn't permanent.
Anyways, sorry for the wall of text, I wanted to make sure what I said was clear Please help guys, what should I do??

Rokuw said:
Hey guys. So here's the thing. I unlocked the zuk's z2 bootloader using the standard method (fastboot -i 0x2b4c flash unlock unlock_bootloader.img, with the img they sent me via email, and then fastboot -i 0x2b4c oem unlock-go), and then I went to flash the TWRP recovery. I downloaded the recovery image from the official twrp website and proceeded to flash it with "fastboot -i 0x2b4c flash recovery twrp.img". The flashing was successful. But before restarting the device, I chose the option to boot into recovery, so that the original recovery wouldn't overwrite TWRP. However, the phone does not boot into the recovery, ever. It "shuts down", tries to boot into recovery, and without showing anything on the screen simply restarts to the normal system. Even flashing a stock ROM in the phone with MiFlash (relocking the bootloader) and trying to boot into the stock recovery does not work.
And, the only method to boot into any recovery that works is to use "fastboot -i 0x2b4c boot recovery.img". But as we know this isn't permanent.
Anyways, sorry for the wall of text, I wanted to make sure what I said was clear Please help guys, what should I do??
Click to expand...
Click to collapse
Why not flash twrp as an image file while in non permanent twrp? And while you're there flash supersu too.

Airtioteclint said:
Why not flash twrp as an image file while in non permanent twrp? And while you're there flash supersu too.
Click to expand...
Click to collapse
I did manage to flash a custom ROM, GApps and Magisk with the temporary TWRP and everything worked. But I just flashed the TWRP image as you said and the flash was successful, but the phone still doesn't boot into recovery
WTF is going on?? Its kinda like the image is being flashed correctly, but the phone fails to access the recovery partition to boot it... Halp!
Edit: Flashing via flashify also didn't work...

Re
Rokuw said:
I did manage to flash a custom ROM, GApps and Magisk with the temporary TWRP and everything worked. But I just flashed the TWRP image as you said and the flash was successful, but the phone still doesn't boot into recovery
WTF is going on?? Its kinda like the image is being flashed correctly, but the phone fails to access the recovery partition to boot it... Halp!
Edit: Flashing via flashify also didn't work...
Click to expand...
Click to collapse
As that window on boot shows that in 5 sec. to push anything, choose from that window Boot to bootloader, from there using volume buttons choose boot to recovery, it will reboot, wait those 5 secs and immediately after that window gone keep pushing both volume buttons and it should boot your recovery - it's the same for me and idk why

LaurynasVP said:
As that window on boot shows that in 5 sec. to push anything, choose from that window Boot to bootloader, from there using volume buttons choose boot to recovery, it will reboot, wait those 5 secs and immediately after that window gone keep pushing both volume buttons and it should boot your recovery - it's the same for me and idk why
Click to expand...
Click to collapse
Its works!!!1!! Much thanks mate!
Still though, it's really annoying having to do that every time to boot to recovery... If i figure out why that happens I'll shed some light here... And Would also be grateful if anyone who knows the reason for it explains why

Re
Rokuw said:
Its works!!!1!! Much thanks mate!
Still though, it's really annoying having to do that every time to boot to recovery... If i figure out why that happens I'll shed some light here... And Would also be grateful if anyone who knows the reason for it explains why
Click to expand...
Click to collapse
Great! Let us know if you'll find anything! Good luck

Thats It!
LaurynasVP said:
As that window on boot shows that in 5 sec. to push anything, choose from that window Boot to bootloader, from there using volume buttons choose boot to recovery, it will reboot, wait those 5 secs and immediately after that window gone keep pushing both volume buttons and it should boot your recovery - it's the same for me and idk why
Click to expand...
Click to collapse
As you said, is a patience problem:
I had the same problem and beeing serious I was very desperate, I tried and tried for weeks and nothing! BUT BRO! It was just beeing patient! You did it! You flashed the TWRP, now is just to wait!:
1. Turn on your device
2. Press volume keys to enter to the fastboot menu
3. Choose Recovery
4. Now the device will reboot and show the same thing as always(ZUK,Bootloader is unlocked,blablabla.), and here is when all starts, YOU NEED TO WAIT 5 SECONDS BRO!, AND THEN IT WILL BOOT TO TWRP!
5. Thats all, you're on!
P.D.: Apologize me for bad english :'v
Hope it worked!

mrscattergun said:
As you said, is a patience problem:
I had the same problem and beeing serious I was very desperate, I tried and tried for weeks and nothing! BUT BRO! It was just beeing patient! You did it! You flashed the TWRP, now is just to wait!:
1. Turn on your device
2. Press volume keys to enter to the fastboot menu
3. Choose Recovery
4. Now the device will reboot and show the same thing as always(ZUK,Bootloader is unlocked,blablabla.), and here is when all starts, YOU NEED TO WAIT 5 SECONDS BRO!, AND THEN IT WILL BOOT TO TWRP!
5. Thats all, you're on!
P.D.: Apologize me for bad english :'v
Hope it worked!
Click to expand...
Click to collapse
I did it the way you said but when i select recovery in the fastboot menu, the phone restart into fastboot, and even if I wait 5 secs it doesn't do anything! what can i do? thanks

Hi all, I have the same problem. Bootloader is unlocked and twrp is successfully flashed but the phone won't boot to twrp, it always boots to the stock recovery. can I flash twrp from stock recovery?

same problem here

My zuk z2 its not working i dont have a system and no recovery....
what i can do??

zuk z2 plus is not turning on..and the screen blinks and vibrates
zuk z2 plus is not turning on..and the screen blinks and vibrates...i tried to install custom rom of pixel experience...it works well but after 50% it gets shuts down..and now it is fully dead

M8s stuck in bootloader

Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!

Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone

It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.

Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!

Have you tried sideloading twrp ?

McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?

Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.

McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?

McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....

McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.