Database Users

[Q] Nexus 7 "Booting Failed"

Hey Guys,
So I was trying to downgrade to 4.3 on my Nexus 7, and I was dumb enough to disconnect it before it was complete. I believe it was in the process of deleting user data. Now I have a screen that says "booting failed" on the left, the google logo in the middle, an unlock symbol on the bottom, and a start banner on the top left, but every time I try to hit start, it just stays on the same screen saying booting failed. Same results when I try to boot into recovery. Is there any hope?

You should investigate whether or not you can communicate with it using fastboot. You might need to get it to the bootloader screen (rather than the "failed boot" screen). [REF] Nexus 7 Button Combinations
If you can, then there is all sorts of hope (from what you describe, it sounds like the bootloader is unlocked). All you need to do is do a little reading about fastboot - for instance in the "return to stock" thread here on XDA.
fastboot is the gateway to all things root with the N7.

There might be hope
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.

bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
I've done exactly the same thing. Any update please?
Thank you

bmoney83 said:
I can get to fastboot. The hang comes when I run the fastboot erase userdata. It just gets stuck there.
Click to expand...
Click to collapse
Stuck as in no messages, no output, prompt never returns?
Have you tried soft-booting a recovery to see what happens? e.g.
e.g. TWRP
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
e.g. CWM
Code:
fastboot boot recovery-clockwork-touch-6.0.2.3-grouper.img
-OR- (non-touch version)
fastboot boot recovery-clockwork-6.0.2.3-grouper.img
(The above are just examples, I'm not recommending a particular version of either custom recovery)
That might be a start. By communicating with a soft-booted recovery (adb shell blah-blah-blah), you can look at the kernel log (e.g. "adb shell dmesg") and see if it is complaining about partitions, filesystems, etc. The only rub with this is that because of the N7's use of an "internal" pseudo-SD card, the custom recoveries try and mount the userdata partition as soon as they start up, so if there is something wrong with that filesystem, the recovery itself might get wedged. I think I saw this with TWRP for instance - the touch interface wouldn't come up when I had a effed-up userdata partition. So, either an older recovery or a non-touch interface recovery might be adviseable here if you have troubles.
good luck

Solved!
Alright, two things helped me out here.
1. I used a different computer and reinstalled everything.
2. When you unzip the stock rom, it still leaves one zipped file in there that also needs to be unzipped into the platform-tools folder.
And now I'm in business!

Bootloader unlock failed. ID: Bad Key?

I just got my Moto G5 Plus today, and ran Motorola's official Bootloader unlock guide.
Upon starting up, I am now receiving an error that says "Your device has been unlocked and can't be trusted. ID: bad key"
I confirmed multiple times that I provided the correct unlock_data and entered the correct unique key provided.
Because of this I cannot flash TWRP.
"(bootloader) Image not signed or corrupt"
What can I do here? Is there a way to re-do the unlock?
Do I have to flash stock back to the phone? I cannot seem to find any guide on how to perform that properly.

Are you sure TWRP didn't flash because it gave me that same generic error (because it's no longer stock recovery) but it had installed fine. Did you try selecting 'Recovery Mode' in the bootloader and see if it loads? Hopefully you're following the rooting tutorial in this forum because you need to follow it closely to correctly gain root.
That 'bad key' message on startup is normal after unlocking and can be removed by flashing another 'logo.bin' as shown in this video, so actually seeing it shows that you probably did unlock successfuly.

Correct, as everyone has stated, this is normal for a bootloader unlocked device. You can flash a logo.bin to make your boot up look better
Sent from my Moto G (5) Plus using Tapatalk

Were you able to fix this? I have a similar problem.

I am also having this problem. Everyone saying this is normal, is wrong.

donjuro said:
I am also having this problem. Everyone saying this is normal, is wrong.
Click to expand...
Click to collapse
The "normal" message once it's bootloader unlocked is "Your device is unlocked and can't be trusted...Your device will boot in 5 seconds." - it doesn't say anything about a "key".
EDIT: oh, and where his said "ID: bad key" mine says "ID: n/a"

Yes I found out my problem was that I was using a later version of twrp and you have to first use an initial build on one of the rooting threads.

I'm having the same issue. Got the unlock key from Motorola and successfully unlocked bootloader from CMD. The phone then booted up as if it were new. I access the recovery mode and get "device has been unlocked and can't be trusted". No other option. I've tried manually and through CMD. I've downloaded all necessary files including the kernel, ADB, fastboot and twrp. Nothing works. Phone operates as if I factory reset it.

I just rooted my Moto G5s plus last night...here were my steps:
1.) Do the Motorola unlock B.S.
I had fastboot.exe and adb.exe from the Android SDK installed
I did find that I had to unlock my phone or adb could not see it
2.) After unlocking, you get the "untrusted phone" screen
3.) Use fastboot to flash a new boot image: fastboot flash boot logo.bin (I built a logo with MotoBootLogoMaker), this gets rid of the untrusted screen
4.) I do have the "bad key" message show up during boot, but it hasn't impacted anything...it is in white, my boot logo is in white, so you don't see it.
5.) Get a copy of SuperSU.zip on your sdcard and load into your device
6.) I installed TWRP (twrp-3.11-sanders.img) to the recovery partition, but that caused an issue: fastboot flash recovery twrp-3.11-sanders.img)
* Recovery wouldn't boot after this, so I successfully booted the image directly with: fastboot boot twrp-3.11-sanders.img
6.) TWRP successfully loaded....
7.) Use TWRP to install SuperSU.zip (this roots the device)
* I wiped the dalvik cache, but that hung and I ended up powering off...but fortunately it didn't brick the device
8.) After reboot, I logged in with "adb shell" and did an "su" to prove I was rooted.
9.) I replaced bootanimation.zip with one more to my liking than the Lenovo one (/system/media/bootanimation.zip I think was the location)
That was it...

No system, no recovery, bootloader unlocked, FRP locked

After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!

CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.

Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service

Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.

Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)

dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!

CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.

Semi-bricked??

Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!

Can you fastboot boot the TWRP recovery?

Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus

Someone?

AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help

Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7

Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.

Stuck on "Bootloader is unlocked" bootloop, only fastboot and stock recovery available

Update : NVM I fixed it
I am sorry if I am posting this in the wrong place. But I need serious help.
-I was on Lineage 18.
-went to Lineage recovery
-used All in One tool to flash stock
-It was idle on System image 6 and I closed the window because nothing was happening on my phone's screen, it still showed Fastboot of Lineage. Stupid move I know
-I restarted and it showed the "Bootloader is unlocked screen" and is bootlooping to this screen ever since.
-I can only access stock recovery and stock Fastboot mode
- Tried restoring through ADB but it the device doesn't show up.
-On device manager under ports it shows Communications Port COM1 and under Other devices it shows "Android" with a yellow error symbol
Basically, I am stuck here and don't know how to proceed further.