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

[Please help]Bootloop, adb "unauthorized, fastboot flash not working, CWN not working

[Please help]Bootloop, adb "unauthorized, fastboot flash not working, CWN not working
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules

i have the same problem
jules.renz said:
Hi everybody!
First of all, I'm not an Android noob, I've experience with fastboot and adb commands, android app developement and Stock/Custom Roms/recoveries in general.
Also, I extensively used google and the xda search for this issue but unfortunately didn't come any further.
To make things a little shorter, and avoid a wall of text, here are my problems.
- I'm using CM11 and CWM on a rooted Maguro.
- Initial Problem: Device is stuck in a Bootloop and I want to backup my personal data
- Therfore, wiping is not desired.
- I can boot into Downloading Mode (e.g. for Odin) and Bootloader Mode
- I can boot into recovery (CWM 6.0.4.7) through bootloader menu or fastboot
- In recovery, adb recognizes the device but it is displayed as "unauthorized", so I cant pull any files that way
- Afaik, the device should be accessible in recovery mode, so I thought maybe it would be a good idea, if I installed TWRP instead of CWM and see if it works then.
- I tried installing the new recovery (TWRP) through fastboot (fastboot erase recovery, fastboot flash recovery), and fastboot states, that it was successfull. HOWEVER, when I reboot, the recovery is still CWM and untouched.
- I read, that CM11 may under certain circumstances overwrite any recovery with CWM ob boot, so I made sure to direktly boot into recovery from the bootloader after flashing TWRP over fastboot. Still, CWM is untouched.
- I tried installing TWRP over Odin. Odin too states, that flashing the recovery was successful, but again, CWM remains untouched.
- Then I tried erasing and reflashing "bootloader", "radio", "boot" and a stock "system" through fastboot. (I carefully did not erase "userdata"). All finished successfully according to fastboot but a reboot showed the system in the same state as before.
- At this point, I assume, that I don't have write-access to the device anymore, as silly as that sounds.
At this point, I'm stuck at a dead end and don't know how to proceed, so every help you could provide would be incredibly appreciated.
Of course, I'm also willing to go into more details, but in order to keep this post from getting too long, I didn't do it in the first place.
Many thanks in advance for oyu assistance!
Greetings
Jules
Click to expand...
Click to collapse
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1

majeida said:
ROM: FML-AOSP-5.0-20141207-maguro.zip (http://forum.xda-developers.com/galaxy-nexus/development/rom-fml-fork-life-06-05-2014-v2-t2764064)
Recovery: CWM V6.0.5.1
Click to expand...
Click to collapse
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"

sorry for the misunderstanding
jules.renz said:
Sorry, but I can't see, how this is supposed to help, since my problem is not "I'm looking for a new ROM"
Click to expand...
Click to collapse
sorry i have the same problem .
I'm using FML-AOSP-5.0-20141207-maguro and CWM V6.0.5.1 on a rooted Maguro.

Your personal data includes what?? Apps or photos and videos?

varadparulekarofficial said:
Your personal data includes what?? Apps or photos and videos?
Click to expand...
Click to collapse
yes

have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.

ashclepdia said:
have you tried using the fastboot boot "/path/to/recovery.img-name-here" fastboot option to just directly boot into twrp without installing it? I used to use fastboot boot for different recovery and boot imgs I wanted to test out first before actually installing them. and I had a similar issue to what yours sounds like before in which I was able to use fastboot boot recovery.img when I wasn't able to get different custom recovery to install at the time.
Click to expand...
Click to collapse
I used this method
*I boot into costum temporary recovery "TWRP 2.8.3.0" Then I tried erasing and reflashing "bootloader", "radio", "boot" and new "system" through recovery All finished successfully according to TWRP but a reboot showed the system in the same state as before

Flashing OTA failed. I need help to restore my phone.

Hi,
My phone is rooted and the DPI was customized. I tried to manually flash the OTA but the installation got stuck so I cannot boot into Android anymore. I tried those restore tutorials but when I try to flash using fastboot I get a "FAILED (remote: Permission denied). I tried to clear the cache in the recovery and then it got also stuck and now I can't access recovery.
This is what I can read in the bootloader
---------------------------
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI - 0094.0177
SERIAL NUMBER - Xxxxx....
SIGNING - ?
SECURE_BOOT - ?
continue fastboot process
-----------------------------

I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!

manlord said:
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
Click to expand...
Click to collapse
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....

ultramag69 said:
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
Click to expand...
Click to collapse
Thanks for your help. I did that earlier with the latest pre-rooted OTA and now it gets stuck on the splashscreen. I tried going to recovery (stock now) and doing a factory reset after flashing system.img and it still the splashscreen after I reboot. I know the 1st boot after flahing a ROM can be long, but now it's been an hour and I'm still on the splash screen...

The only other thing I can recommend is to flash a RAW rom image. As I have never needed to do this I can't say how this works but if you do a search you should find out the procedure...
This may relock your bootloader so just be aware....

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.

Redmi Note 5 Bootloop & Can't boot Recovery

Hello, need your help guys.
So my Whyred bootlooping now. What I did previously was wiping System, Cache, Dalvik & Data before flashing custom ROM -- I know, this shouldn't be an issue. But since I can do fastboot, I tried to flashes recovery. I tried a few (TWRP, RedWolf & Batik), for each the steps were all the same: Via fastboot flash the dummy image to manipulate ARB check, then flash Recovery and finish with boot into recovery.
The phone booting into recovery, I can see the screen of recoveries for few second, then phone bootlooping again.
What should I do?
And for additional information, my phone was unlocked bootloader -- it still unlocked because I can see the Unlocked sign on bootloop screen. I also tried to flash official MIUI rom via fastboot (whyred_global_images_V10.0.6.0.OEIMIFH_20181127) but it was failed because anti roll back -- I also don't understand this because the ARB was supposed not allowing me to downgrade, but why is it also not allowing me to flash the latest ROM too?
I am now stucked in bootloop -- still can do fastbooting, but really have no idea how to flash any rom and get into the system. Really need help help help please

Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img

Rush-er said:
Try this:
Code:
fastboot boot recoveryname.img
like fastboot boot RedWolf.img
Click to expand...
Click to collapse
Yes, for redwolf it was the command -- I was short typing but thats the idea.