[Q] Bricked Nexus 7 (stuck on google logo, can enter fast boot) - Nexus 7 (2013) Q&A

Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance

BoredAtWork said:
Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
Click to expand...
Click to collapse
Did you tried flashing stock google image from wug's kit by clicking "Flash Stock+Unroot" option

Further info:
Tried different factory roms, same flash method, same result
4.2.0
4.4.x
4.5.0
all flash using fast boot command shows success on screen.
fastboot recognize device when using "fastboot devices"

supersaayuj said:
Did you tried flashing stock google image from wug's kit by clicking "Flash Stock+Unroot" option
Click to expand...
Click to collapse
thanks for quick reply.
Tried Wug's kit (latest version since it auto update), and tried with command line using fastboot drivers (win7 environment)
Same result
Wug's kit logging shows no problems.

BoredAtWork said:
Further info:
Tried different factory roms, same flash method, same result
4.2.0
4.4.x
4.5.0
all flash using fast boot command shows success on screen.
fastboot recognize device when using "fastboot devices"
Click to expand...
Click to collapse
Then it should boot man! Try flashing factory image using NRT(wug's toolkit) by "Flash Stock+Unroot" and ticking SoftBricked/Bootloop below that.. hope this works

supersaayuj said:
Then it should boot man! Try flashing factory image using NRT(wug's toolkit) by "Flash Stock+Unroot" and ticking SoftBricked/Bootloop below that.. hope this works
Click to expand...
Click to collapse
I have tried exactly that. "flash stock+ unroot" with the nexus in boot loader mode. After complete, the nexus will remain in boot loader mode until I restart it manually (press power button on nexus). Wug's toolkit would not reboot it after successful flashing. Is that normal?
After manual reboot, it still stuck on google logo.

BoredAtWork said:
I have tried exactly that. "flash stock+ unroot" with the nexus in boot loader mode. After complete, the nexus will remain in boot loader mode until I restart it manually (press power button on nexus). Wug's toolkit would not reboot it after successful flashing. Is that normal?
After manual reboot, it still stuck on google logo.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=orZ_iBpkn_g
Get a look at this video... I can't further help... because this is a weird problem I haven't faced with my nexus 7. Mostly flashing stock would solve this kinda problem! :angel:
Reply back if you unbricked it!

Same problem here
I got the same problem here. First ElementalX kernel frozen touchscreen in 5.0, so I used ADB to flash stock image back. After that it get stucked at Google logo. Does anyone have solution?

Is there anyone can help?

micheldjerzinski said:
I got the same problem here. First ElementalX kernel frozen touchscreen in 5.0, so I used ADB to flash stock image back. After that it get stucked at Google logo. Does anyone have solution?
Click to expand...
Click to collapse
All of the above posts match my experience with the n7 2013...it has been a downwards spiral of malfunctions at the touchscreen department...ending at this...some time soon, i'm gonna pick up an axe or some other heavy-hitter tool and smash the f*****g thing to atoms!
yes, i have given up....hopefully you don't get to the same conclusion as i....good luck...

BoredAtWork said:
Have a nexus 7 in need of help. Hope can get some assistance here.
- Stuck on google screen when boot
- Can enter boot loader mode using power + vol down, and can use fastboot
- successful flash of recovery, rom, boot, boot loader partitions using cmd (fastboot) or wug's kit, but will not restart on its own.
- when tried to restart, it hangs again on google logo.
- Tried recovery mode with power + vol up after reboot, doesn't work. Cant get into recovery. NO "android robot with red !", stuck on google logo
- no access of ADB (since stuck before I can enter Android OS)
- wiped cache and wiped user data no change.
- cannot get into recovery so cannot do a hard reset
- pulled battery in hope of hard reset, same result
Any ideas? thanks in advance
Click to expand...
Click to collapse
I was experiencing this problem last night. However, I used WugFresh's NRT but when it asks to flash stock and unroot, make sure you check the box that says your nexus 7 is softbricked. Also, you may want to note what version of android it was last running before it was bricked. It worked for me and I was able to update to 5.0.1.
*Edit: The only thing you need to do is make sure fastboot is enabled, and you should be good to go.
P.S. DO NOT download the stock images from google to your computer, let the NRT automatically download it for you. It saves you time, storage and stress. Once done, also install the recovery from the NRT, that should be able to do the trick. Not sure why your device won't restart, you may have to flash again.

wugs
I had to use force flash in wugs, go to options and set it there and try a previous version. Best of luck.

It's fixed!
koymoy said:
All of the above posts match my experience with the n7 2013...it has been a downwards spiral of malfunctions at the touchscreen department...ending at this...some time soon, i'm gonna pick up an axe or some other heavy-hitter tool and smash the f*****g thing to atoms!
yes, i have given up....hopefully you don't get to the same conclusion as i....good luck...
Click to expand...
Click to collapse
Haha, I found the solution elsewhere in XDA. So if you haven't beaten your Nexus 7 so bad yet, TRY this: press and hold the power button for about 1 minutes. The slate turned off and on several times, and I found nothing. BUT after several minutes (while I was watching Youtube to see how to remove battery; that would be the last method before throwing 5 stories down to ground), the Nexus BOOTED BACK:good::good::good:. Good luck!:laugh:
And I'm using Glitch kernel and turn off flar2's double-tab-to-wake. It's a neat feature, but can get us into big troubles.

That still doesn't work for me. Pretty sure my eMMC is dead, so I'll need to replace the motherboard.
Anyone know if a 16GB motherboard works in a 32GB Nexus 7 2013? 16GB motherboards seem a fair bit cheaper, and less rare.

Related

Stuck on Google Screen - Restore Didn't Work

Good Morning All -
A few days ago, I dualbooted my N7 with Ubuntu. The installation went fine and the tablet was working with no issues over the last several days. Last night, I was using the tablet and set it down. I went to pick it up (roughly 5 minutes later) and the touch screen was unresponsive. I was at the lock screen but couldn't get it to unlock. I pushed the wrong key-combo first and the device took a screen shot.
I was able to reboot into fastboot and attempted to go to recovery. The device would just hang at the Google logo. I pushed a factory firmware update from my Ubuntu system and attempted to reset -- no joy. This morning, I used Nexus Root Toolkit from my Windows 8 machine to see if I could get it up. Root Tool kit worked fine, pushed the images over again and restarted but it continues to hang at the Google logo.
Looking for any other advice folks may have on getting the device to boot.
EDIT: I can get to the bootloader fine and the computer recognizes it.
Thanks!
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
xbi0s said:
Alright... I just attempted using NRT and flashing 4.4.2 instead of 4.4.3 to see if it would run through. No joy, again. Remains on the Google screen.
Click to expand...
Click to collapse
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
antonio824 said:
Im having the same problem with an unlocked unit. I would bet if you tried to do a factory reset in the android recovery menu it would give you a huge error all having to do with cache.
Click to expand...
Click to collapse
I'm unable to get into the restore menu. Hangs at the Google logo when attempting to get there.
I've tried about any solution I could find... Bumping one last time before I torch the unit :\
Nothing can be done. Its something inside. If its the 2013 model, call and get it rma'd. Sorry man.
Sent from my LG-LS970 using XDA Premium HD app
Resurrecting this thread to keep a work log.
I made have made some progress but hitting another roadblock. I've been holed up at home due to an auto accident so I started tinkering with the N7 2013 again.
Using the Nexus Root Toolkit, I am able to launch "Boot Temporary - Custom Recovery" from the advanced options. The problem I now run into is TWRP's touchscreen will not work. I attempted to do volume up/down to see if I could select but it wouldn't. The software is not frozen as I can see the temperature changing.
Anyone have any thoughts or information on how to boot another custom recovery that uses button inputs? I appreciate any input.
Updates:
1. I was able to push TWRP via "fastboot flash recovery." It went to the Google Logo then loaded TeamWin screen. I started to see errors when the program launched. "Unable to mount..." multiple times then the device rebooted. Device stuck on the Google screen.
2. Shut the device down, booted back into Fastboot. Selected Recovery and it began loading again. This time, the app launched and worked. Touchscreen does not work but the CPU temp is fluctuating and minutes tick up.
Update 4:49PM Central:
1. I am able to install and boot into TWRP 2.8.0.1 through TWRP 2.7.1.1. Those versions load but of course touch screen does not work.
2. I have been unable to get CWM to load... It installs fine but I cannot boot into.
3. The factory recovery images also do not load.

[Q] 'Secure boot Error!' at boot, download mode and factory reset don't work

Hello,
Here is what led to my issue:
I rooted my phone using this method: http://forum.xda-developers.com/showthread.php?p=38886073#post38886073
Downloaded clockwork rom manager.
Here comes the thing I don't remember. At least i know that the last thing i did was to click on 'backup current rom'
After this the phone reset itself and this message came up:
Secure booting error!
Cause: boot certification verify
Then i tried to reset using the power button, which led me to the 'battery full' screen - afterwards i was able to reboot. As stupid as I am I just tried the same thing again. And ever since i am stuck at the 'Secure booting error!' screen.
I am unable to enter download mode. I get to the 'Hard factory reset' screen, but if i accept doing so, it says 'Secure booting error!' again.
I also remember clicking on 'restart into recovery mode' at some point, but this is not the last thing i did.
I am really desperate. Please, help me!
Well i had the same issue today... It happened after i did two changes. One of them was to to try to relock from freegee and flash twrp again from freegee. In my case i was able to go in download mode and flash original kk rom with lg flash tool.
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Jubi-Wan said:
Unfortunatly, trying to boot in downloadmode, i still get the same error :/
Click to expand...
Click to collapse
How are you trying to boot into download mode? And what factory reset screen? It seems as though you did not unlock the bootloader using freegee, if you make any changes and relock the boot loader you will get that error. But it seems that it has not been unlocked. If you hold power and volume up what happens? Same thing when power and volume down, one of them is recovery (possibly factory reset you are seeing) and the other is download mode. I don't remember right now but you should read the whole softbrick thread and see if you are missing something. You may need to use LGPNST to go back to stock, you can also use that program to flash a new recovery so read carefully and follow all steps.
When this happened to me I was able to flash an unlocked bootloader and it allowed me to use my phone again as it was before doing something stupid (for me it was an attempt to re lock the bootloader).
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Jubi-Wan said:
well, i managed to get into download mode. Obviously i used the wrong method to get into download mode...
I used this method and everything worked fine, so far. : http://forum.xda-developers.com/showthread.php?t=2249500
My phone doesn't boot now. Fast Boot doesnt work aswell.
All that happens is a white battery showing on the screen and when i try to fastboot all that happens is that the LED is blinking or glowing red after some while.
Click to expand...
Click to collapse
What do you mean when you try to fastboot? Fastboot is basically the bootloader and allows you to select recovery or download mode. What you should have done after following that thread is go to recovery and wipe everything and flash a new ROM.
If you are saying that the bootloader is not coming up and allowing you into recovery then I believe something was missed.
After trying out some varioants of this it worked: http://forum.xda-developers.com/showthread.php?p=40274560&highlight=red+led#post40274560
I wiped the phone, but since I had to leave over the weekend i just turned it off and went away.
Now that I am back, nothing works now :/ The Phone doesnt react to anything, not even donwload-mode.
Is the battery too low maybe? It's on the wall now for a few hours, but it still doesn't react. It's not warm either.
edit:
when i charge the phone, i will get a 'watchdog bark' after some time allowing me to get into recovery. accesing downloadmode from there doesn't do anything. strangely, the recovery isnt trwp although it should be because teenybin comes with it. it's 'bbs.gaodi.net' which doesn't have a sideload feature. what do i do now?
edit2:
after 10000 tries i got into download mode. i don't want to **** up now so i won't do anything until i know exactly what to do.
any advice?
edit3:
got it working by flashing another teenybin which included trwp - then i installed miui via sideload. i don't have signal though, but i will open another thread for this since this is another issue.

Can't get to Recovery mode any more.

Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.
dubsteps said:
Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.
Click to expand...
Click to collapse
the "fastboot erase cache" should be done after flashing recovery:
Code:
fastboot flash recovery <name of correct twrp version>.img
fastboot erase cache
no need to wait for it to die out, POWER + VOLUP (possibly under a bright light) should do a forced reboot
nkk71 said:
the "fastboot erase cache" should be done after flashing recovery:
Code:
fastboot flash recovery <name of correct twrp version>.img
fastboot erase cache
no need to wait for it to die out, POWER + VOLUP (possibly under a bright light) should do a forced reboot
Click to expand...
Click to collapse
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).
dubsteps said:
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).
Click to expand...
Click to collapse
Not sure which recovery you're trying to flash but you might try a different version.
Magnum_Enforcer said:
Not sure which recovery you're trying to flash but you might try a different version.
Click to expand...
Click to collapse
I flashed TWRP 2.8.0.1 and it worked fine until I decided to try to get rid of the red text on the HTC bootloading screen.
dubsteps said:
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).
Click to expand...
Click to collapse
have you made sure
1- the recovery is the correct one for your phone
2- the file isnt corrupt (check MD5)
i don't know if this is related to the modded hboot (it shouldnt be) but who knows, i dont like messing with hboot
If all else fails, RUU and start over.
Magnum_Enforcer said:
If all else fails, RUU and start over.
Click to expand...
Click to collapse
Ok, I redownloaded the latest TWRP: 2.8.3.0 for the M8, checked it via MD5. I tried flashing the recovery file and nothing has changed... ( I now notice my phone won't connect to Bluetooth or wifi now)
Seems like all else is failing. I'll have to try RUU now. I'm starting to look around the M8 forum for info on RUU. Got anything threads handy to help me?
dubsteps said:
Ok, I redownloaded the latest TWRP: 2.8.3.0 for the M8, checked it via MD5. I tried flashing the recovery file and nothing has changed... ( I now notice my phone won't connect to Bluetooth or wifi now)
Seems like all else is failing. I'll have to try RUU now. I'm starting to look around the M8 forum for info on RUU. Got anything threads handy to help me?
Click to expand...
Click to collapse
Which carrier are you on?
Magnum_Enforcer said:
Which carrier are you on?
Click to expand...
Click to collapse
Originally the phone was with Rogers Wireless. I had to SIM unlock the phone so I could use it on Bell Mobility.
dubsteps said:
Originally the phone was with Rogers Wireless. I had to SIM unlock the phone so I could use it on Bell Mobility.
Click to expand...
Click to collapse
imho, try reflashing your firmware again (that would include stock hboot)
by removing the red writing you actually installed a custom hboot i think ...revert to your original hboot should fix things for you
nkk71 said:
imho, try reflashing your firmware again (that would include stock hboot)
Click to expand...
Click to collapse
Ok, so I flashed stock recovery and went to HBOOT>RECOVERY -> pressed VOLUP and POWER at red triangle w exclamation point screen.
- Wiped Cache, Factory Reset data (not sure if that is needed, but did it in case)
rebooted and the phone is working again (AND the red text is gone at startup)
dubsteps said:
Ok, so I flashed stock recovery and went to HBOOT>RECOVERY -> pressed VOLUP and POWER at red triangle w exclamation point screen.
- Wiped Cache, Factory Reset data (not sure if that is needed, but did it in case)
rebooted and the phone is working again (AND the red text is gone at startup)
Click to expand...
Click to collapse
nice :good::good:
no reason for custom recovery not to work since you were able to get to stock recovery, i've seen a few rare cases on the m7 where you had to delete the twrp settings file on the sdcard for it to work when going from one version to another (though really a very rarely)
nkk71 said:
nice :good::good:
no reason for custom recovery not to work since you were able to get to stock recovery, i've seen a few rare cases on the m7 where you had to delete the twrp settings file on the sdcard for it to work when going from one version to another (though really a very rarely)
Click to expand...
Click to collapse
Ok, it's definitely the download for the TWRP recovery I had. I'm able to reflash stock recovery and reflash other TWRP downloads (another download of the newest, then maybe 2.7.x.x)
-
OK, I flashed with TWRP 2.8.1.0 and that worked ok. I did MD5 the 2.8.3.0 TWRP, but it just won't work.
Thank you so much nkk71 and everyone who replied to my thread!
dubsteps said:
Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.
Click to expand...
Click to collapse
Got a similar problem like this one
unlocked bootloader
flashed twrp using the fastboot process of cmd
but i CANT get into RECOVERY MODE
when i click Recovery only a screen flashes saying "Entering recovery" and comes back to the bootloader screen showing HBOOT
PLEASE HELP
A TOTAL NOOB

Moto Z2 Play Reboots Straight into Recovery

Okay, so, I followed the guide to root my device. And everything went smoothly, until the new version of Android (8.0.0) was released for the phone and I made the mistake of trying to install it using the stock installer rather than through TWRP. Of course, it failed and I ended up doing the installation manually. Now, whenever I try to reboot my phone, it boots straight into recovery (which gives me the "No Command" error because TWRP is inexplicably missing). If I load up Bootloader (Volume Down + Power) and select START, then the phone boots like it should and I can use it just fine.
I've tried wiping the data through TWRP (After flashing it to recovery for the umpteenth time) thinking that would help, but no. It still boots directly into recovery. The command "fastboot oem fb_mode_clear" using minimal ADB and fastboot doesn't work either. Any help would be appreciated. I have no idea what else to do.
try to plugin charge cable and reboot again.
Nope. Still boots to recovery.
Hi, did you ever manage to solve this? I have the exact same problem.
Fiksdal said:
Hi, did you ever manage to solve this? I have the exact same problem.
Click to expand...
Click to collapse
try to boot to bootloader, and then use the option start

Missing Recovery on Android 10

I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.
You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:
jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.

Categories

Resources