Related
Hi,
i have a problem with rooting my nexus 10: After installing te recovery, i was to slow updating the drivers.
No i have a bootloop, my device dont boot the OS, it hangs on the animation.
I can enter the bootlaoder, so i assume that i dint brick the device.
What should i do? flash the factory image?
plz help
After fastboot oem unlock you need to do a factory reset... A userdata.img is included in stock images from Google at https://developers.google.com/android/nexus/images#mantarayjop40c
Sent from my Galaxy Nexus using xda app-developers app
so i have to flash this image in fastboot?
fastboot flash userdata.img ?
i just dl the factory image from here https://developers.google.com/android/nexus/images and run the flash-all bat but still a bootloop
fastboot flash userdata userdata.img
ok, i just hit this, letz hope it works, im a bit worried that i brick the device
edit : ok still a bootloop ;(
Do cache.img in the same way... See if that fixes it ( I did all this earlier too when I got a bootloop in the same manner)
Sent from my Galaxy Nexus using xda app-developers app
ok. ill gonna try it, how long shoul i wait, until im sure that it is a bootloop? 2 min?
yeeaahhh ill got a boot
should i reflash the factory image just to get sure all ist stock again, and all what i do is reverted?
I didn't flash system.img on mine after updating to latest stock (mine arrived with older firmware than stock image)... especially don't do it if you want to keep superuser installed.
Sent from my Galaxy Nexus using xda app-developers app
Many thanks for this, I stating to think I mad, This resolved my problem.
Bootloop and "Downloading-do not turn off target!!" in recovery
Hi there,
New here so please be gentle if possible Opened box, updated OTA firmware to latest 4.2, enabled developer mode & USB, used adb reboot fastboot and adb oem unlock to unlock. Confirmed unlock and now stuck in a bootloop. When I use Power+Down to go into recovery, I get the Android picture stating "Downloading... do not turn off target!!!". Fastboot and adb commands won't work, so I can't figure out how to get past this point. Any ideas? Thanks in advance.
It's a pain to get into the bootloader. Always takes me a few tries. Try holding down power and both vol keys. I have to do it several times, sometimes just vol - sometimes both. Eventually it will go to the bootloader without the downloading dialog.
avm1 said:
Hi there,
New here so please be gentle if possible Opened box, updated OTA firmware to latest 4.2, enabled developer mode & USB, used adb reboot fastboot and adb oem unlock to unlock. Confirmed unlock and now stuck in a bootloop. When I use Power+Down to go into recovery, I get the Android picture stating "Downloading... do not turn off target!!!". Fastboot and adb commands won't work, so I can't figure out how to get past this point. Any ideas? Thanks in advance.
Click to expand...
Click to collapse
Yes you are in Download mode not recovery or fastboot ...
Hold down BOTH volume keys and the power button to get to fastboot mode .. and you can get to recovery from there ...
Watcher64 said:
Yes you are in Download mode not recovery or fastboot ...
Hold down BOTH volume keys and the power button to get to fastboot mode .. and you can get to recovery from there ...
Click to expand...
Click to collapse
Big thanks to both of you who replied with hints. I confirm that holding down BOTH volume keys and power brought me into regular fastboot. I went into recovery (then pressed up+power) and did a factory reset. The (unlocked) Nexus then booted properly after that. I have had no issues since. *fingers crossed*
i have the same problem right now. im using the nexus10toolkit and I have reflashed it back to stock and unroot it. Im still stuck at bootloop. any ideas?
GreaseMonkey90 said:
i have the same problem right now. im using the nexus10toolkit and I have reflashed it back to stock and unroot it. Im still stuck at bootloop. any ideas?
Click to expand...
Click to collapse
Go back to fastboot. Once in fastboot, go into RECOVERY. You'll get android andy on its back with red exclamation point. Hold down POWER then briefly press VOLUME UP. You should then have the menus visible. Now just wipe your device. Reboot and it should work now. If not do the relock, unlock, relock and fastboot recovery and wipe data.
Sent from my SPH-L710 using xda app-developers app
GreaseMonkey90 said:
i have the same problem right now. im using the nexus10toolkit and I have reflashed it back to stock and unroot it. Im still stuck at bootloop. any ideas?
Click to expand...
Click to collapse
Sry for waking up this thread. I am in the same situation as this user, tried to use the nexus tool kit, reflashed the stock factory image and unrooted it and after everything was done its stuck at the google logo. If i try to acces fastboot i always go into download mode. It says downloading...do not turn off target !!
If i press the power button it restarts the device and again stuck in bootloop at the google logo. I cant unlock or lock because i cant get into fastboot at all.
Help?
LE: i havent manually booted in fastboot mode for so long that i forgot i have to press both the volume buttons for it, was only pressing vol down. Silly me, sorry for the post
lvnatic said:
Sry for waking up this thread. I am in the same situation as this user, tried to use the nexus tool kit, reflashed the stock factory image and unrooted it and after everything was done its stuck at the google logo. If i try to acces fastboot i always go into download mode. It says downloading...do not turn off target !!
If i press the power button it restarts the device and again stuck in bootloop at the google logo. I cant unlock or lock because i cant get into fastboot at all.
Help?
LE: i havent manually booted in fastboot mode for so long that i forgot i have to press both the volume buttons for it, was only pressing vol down. Silly me, sorry for the post
Click to expand...
Click to collapse
I have tried 100 times to boot in fastboot mode. I've done every combination of power, volume up, and volume down imaginable. All my tablet does is vibrate. It will boot to the nexus logo but stays in a boot loop. How can I get to the fastboot? Is it just bricked beyond repair. I was attempting to unlock it with the nexus toolkit and it rebooted my device during the process and started this bootloop. Can anyone help?????
Can adb find your device when in bootloop? If so
adb reboot bootloader
If not you will need to continue trying to get into fastboot mode with the hardware keys. I doubt you are bricked as the bootloader is still there or it wouldn't make it to splash screen
Sent from my Nexus 4 using XDA Premium 4 mobile app
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...
As the title says, I unlocked my bootloader and rebooted and my XT1687 RETUS worked fine. Then I rebooted to TWRP using the mfastboot boot string to boot the 3.1.1. version found in this forum. This is how I've done my G4, G4 Plus, G4 Play, G LTE, E 2015, etc. Anyway, the time was off and I wanted to understand why so I rebooted without backing up or changing anything, but now I get the bootloader unlocked trust message with the ID: bad key screen and it hangs.
Any idea why this would happen when I didn't flash TWRP or anything else?
Can I flash the POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml stock boot, system, and recovery and recover and then start again? Thanks!
vettejock99 said:
As the title says, I unlocked my bootloader and rebooted and my XT1687 RETUS worked fine. Then I rebooted to TWRP using the mfastboot boot string to boot the 3.1.1. version found in this forum. This is how I've done my G4, G4 Plus, G4 Play, G LTE, E 2015, etc. Anyway, the time was off and I wanted to understand why so I rebooted without backing up or changing anything, but now I get the bootloader unlocked trust message with the ID: bad key screen and it hangs.
Any idea why this would happen when I didn't flash TWRP or anything else?
Can I flash the POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml stock boot, system, and recovery and recover and then start again? Thanks!
Click to expand...
Click to collapse
you need to format with twrp, then you need to flash supersu in twrp and the modded boot img file.
https://forum.xda-developers.com/g5-plus/how-to/how-to-how-to-supersu-moto-g5-plus-t3587684
After that you will be able to boot to system
i booted into twrp after unlocking my bootloader but i couldnt make a back up so i decided to reboot to recovery from twrp and maybe it would fix it but nope now twrp doesnt boot up and i have no back ups to go from or any img files... i need help
Can you get into the bootloader by holding volume down + power button?
If so, can you plug the phone into your laptop and do the following? fastboot boot twrp-3.1.1-0-potter.img
If you can get into twrp that way, then you SHOULD be able to flash a new rom or just the boot image.
vettejock99 said:
As the title says, I unlocked my bootloader and rebooted and my XT1687 RETUS worked fine. Then I rebooted to TWRP using the mfastboot boot string to boot the 3.1.1. version found in this forum. This is how I've done my G4, G4 Plus, G4 Play, G LTE, E 2015, etc. Anyway, the time was off and I wanted to understand why so I rebooted without backing up or changing anything, but now I get the bootloader unlocked trust message with the ID: bad key screen and it hangs.
Any idea why this would happen when I didn't flash TWRP or anything else?
Can I flash the POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml stock boot, system, and recovery and recover and then start again? Thanks!
Click to expand...
Click to collapse
This happened to me too. I'm glad I'm not the only one. I relocked using the POTTER_RETAIL_7.0_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and decided to call it quits with rooting/ROMing.
reCoded said:
This happened to me too. I'm glad I'm not the only one. I relocked using the POTTER_RETAIL_7.0_NPN25.137-83_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and decided to call it quits with rooting/ROMing.
Click to expand...
Click to collapse
It's all because when twrp installs it disables the auto-flash of stock recovery by modifying system files. That's why it hangs when booting, it doesn't pass the system integrity check because system files were modified. That is perfectly normal, all you need to do is flash magisk or some other dm- verity disabler and the system will boot fine
It also happened to me, had a small heart attack when it didn't boot.
So what about just booting TWRP? Does make any difference?
I'm usually able to get my G7 to boot to system or recovery but it never gets there without stopping at the FastBoot screen. If I command it from the system to reboot to recovery, it stops at the FastBoot screen. But if I command it to boot to recovery from fastboot, it goes straight there.
If I command it to reboot from system or to boot to system to recovery, it stops at FastBoot. If I command it to boot to system from FastBoot it will but it might take 2-3 attempts before it just doesn't come back to FastBoot.
I suspect this might have something to do with me loading a boot screen for a G5 to try to get rid of the "unstrustworthy" nag after I unlocked the boot loader. I liked the design but couldn't find the same one for a G7, and I didn't think just using the wrong boot screen could mess anything else up (except the boot screen). It gave me a blank boot screen (which was better than the nag screen) but it also screwed up the FastBoot screen. Now the only thing on my FastBoot screen that's above the dead Android is the selection indicator next to the power button. I can still scroll through the selections and choose the one I want, but all the stuff that used to be from there up is gone. I thought maybe flashing a proper G7 boot screen would fix it but it didn't. The boot screen is good but the FastBoot screen wasn't changed.
I can't remember for sure that this thing about always stopping at the FastBoot screen started exactly then but it was close if not exactly then.
I'm currently on LineageOS 16 and in the process of rebuilding, so if this FastBoot screen thing is "fixable", I figure this is a good time to tend to it.
Any ideas what causes this (apart from operator error)?
Best to start over with fastbooting full stock pie rom and reinstall TWRP, etc.
HueyT said:
Best to start over with fastbooting full stock pie rom and reinstall TWRP, etc.
Click to expand...
Click to collapse
That doesn't appear to be an option. Since new the only way I've been able to flash any factory image was by extracting it and fastboot flashing the individual files (same method as used to restore boot locking). Now that isn't working either.
DrWu said:
That doesn't appear to be an option. Since new the only way I've been able to flash any factory image was by extracting it and fastboot flashing the individual files (same method as used to restore boot locking). Now that isn't working either.
Click to expand...
Click to collapse
Try
Code:
fastboot oem fb_mode_clear
fastboot reboot
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
Try
Code:
fastboot oem fb_mode_clear
fastboot reboot
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
WHOOAAAA!!!! That fixed it. Now it boots to wherever I tell it, every time. Thank you so much for that, sd_shadow!
The fastboot screen is still messed up but that's purely cosmetic, nothing to affect the functionality, and that's much easier to live with that the way it was.
So im having a problem with my OnePlus 6t Mclaren Edition. I have followed a guide i found on google from droid views but am having a problem when it comes to loading the temp TWRP image through fastboot.
I have unlocked the bootloader on the phone using Fastboot oem unlock and it worked just fine. but now when i boot the phone into fastboot mode, and type fastboot boot twrp-x3.2.3xxxxxxx.img the phone screen flashes and all thats on the screen is the oneplus logo and nothing else appears. ive let it sit but nothing... i have to hold the power and volume up keys to get the phone to restart and then it boots fine. i just cant get the temp TWRP img to load so i can sideload the zip file to the phone. any ideas?
You need twrp3.4.0 by maurofrino available in another thread