Hey Guys,
I tried to root the nexus 7.
I am using a mac so I was following a mac guide.
I had forgotten to enabled the usb debug thingie.
I tried going into recovery mode and it just gave me the google sign with a lock.
Anyways, the current situation is I can go into the Fastboot mode and I have unlocked the bootloader following other instructions, but I can't boot into the normal bootloader.
I have tried to download stock rom only to find out that my bootloader version (flo-03.05) is no where to be found. I had downloaded flo-03.14
Please someone help.
Thanks.
kenaness said:
Anyways, the current situation is I can go into the Fastboot mode and I have unlocked the bootloader following other instructions, but I can't boot into the normal bootloader.
Click to expand...
Click to collapse
If you can go into fastboot mode, then that is the normal bootloader.
Or do you mean Recovery? Within bootloader mode, you can scroll the options using volUp/Down and find Recovery then Press Power to select.
kenaness said:
I have tried to download stock rom only to find out that my bootloader version (flo-03.05) is no where to be found. I had downloaded flo-03.14
Click to expand...
Click to collapse
We were never provided 3.05 bootloader as a flashable image from Google. It only came with the units.
I doubt you need to do anything with the bootloader though. It doesn't sound like anything you did should have killed it. If you are seeing the Google with the lock, then you have a working bootloader.
Got it!
Hey guys
Yea I followed a guide after I got home, to a windows PC and it was super easy and worked like a charm.
Thanks a lot
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
JohnathanKatz said:
Not really sure what happened, a while ago I had an issue with a game and restored my tablet back to factory settings to fix it, but now I discover that while trying to boot into recovery mode it's not there?
I'm trying to manually install the Android 4.4 Kitkat update, got sick of waiting for the OTA since I haven't gotten it yet and really want to use 4.4, but while trying to go into recovery mode to check everything is working because I'm paranoid like that and while I was successful into booting to the bootloader, trying to go into recovery mode resulted in seeing the little android guy with the red triangle saying no command underneath it, so I'm assuming somehow my recovery is missing?
I then tried to flash stock recovery onto my tablet using the Nexus 7 Toolkit and it told me there was an error in flashing the files and that it was because my device's bootloader was locked.
All I want to do is update to Android 4.4, but how am I supposed to do that when I can't boot into recovery? I've followed all the right steps to do it, did I do something wrong by locking my bootloader and unrooting my device?
Click to expand...
Click to collapse
GedBlake said:
Hi, JohnathanKatz...
Unrooting isn't the issue... it's locking the bootloader that's the problem.
If the bootloader of your device is locked, you won't be able to flash anything.
I don't use toolkits myself, but it's pretty straightforward to flash a recovery (stock or custom) using the fastboot tool...
* Unlock the bootloader with fastboot oem unlock
* Fastboot flash the recovery with fastboot flash recovery recovery.img
(...where 'recovery.img' is the name of the recovery image file to be fastboot flashed.)
Maybe there is an option in your toolkit that will unlock the bootloader again... however you do it (toolkit or fastboot), you MUST have an unlocked bootloader before you can flash a recovery.
Rgrds,
Ged.
Click to expand...
Click to collapse
Hi guys, I actually encountered this problem a minute ago when I attempt to flash a new version of TWRP recovery on my grouper. Whenever I go to the recovery, it just shows 'No command' with a red alert of Android on it (I started to panic when I found that there's an unusual error that prevents me from entering the recovery and this is the first time that I saw this error on my flashaholic experience *btw my previous recovery was CWM) I'm currently on stock 4.4.2 with an unlocked bootloader. I have no idea what problem is causing to display that issue when attempting to enter recovery but then I left it for like 5-10mins while it's displaying that error and after that the device reboots then it just quickly enter TWRP recovery normally as is :silly: sick of that haha, silly ol grouper jesus -_-
EDIT
After entering recovery, I got stuck forever on bootloader and recovery! whenever I reboot, I always get directly enter to the recovery and it forces me to not to enter the ROM oh my god at least I can still configure the recovery so I can backup and flash another ROM :|
Hi guys, hoping someone can help me here.
My Nexus 7 is stuck on the Google logo after trying to update to Lollipop using the Nexus Root toolkit.
It will boot into fastboot with this underneath:
Product name - grouper
Variant - grouper
MW version - ER3
Bootloader Version - 4.23
Baseband version - N/A
Serial Number -
Signing - not yet defined
Lock state - unlocked
I have tried a few things so far like using the root toolkit to root it, using the flash stock & unroot on soft brick setting, it'll download the package etc but when it comes to install them on the device it keeps coming back as failed on everything.
I also tried using the Minimal ADB & Fastboot from this thread here http://forum.xda-developers.com/showthread.php?t=2317790 to erase boot, cache, recovery, system data & user data all which come back as FAILED.
Is my Nexus beyond repair, or is there any chance I can bring it back from the dead.
Thanks :good:
Bandit1988 said:
Hi guys, hoping someone can help me here.
My Nexus 7 is stuck on the Google logo after trying to update to Lollipop using the Nexus Root toolkit.
It will boot into fastboot with this underneath:
Product name - grouper
Variant - grouper
MW version - ER3
Bootloader Version - 4.23
Baseband version - N/A
Serial Number -
Signing - not yet defined
Lock state - unlocked
I have tried a few things so far like using the root toolkit to root it, using the flash stock & unroot on soft brick setting, it'll download the package etc but when it comes to install them on the device it keeps coming back as failed on everything.
I also tried using the Minimal ADB & Fastboot from this thread here http://forum.xda-developers.com/showthread.php?t=2317790 to erase boot, cache, recovery, system data & user data all which come back as FAILED.
Is my Nexus beyond repair, or is there any chance I can bring it back from the dead.
Thanks :good:
Click to expand...
Click to collapse
Why did you try 'erase' commands on flashboot, instead of trying to flash the system/boot/cache and recovery stock partitions from the factory image? (just wondering). I think the problem you have may be that the toolkit failed to flash the bootloader and so the process stopped and didn't flash any other parition? We can't know for sure I think because the stock images bootloaders for grouper are ****ed hard mostly and all of them from 4.3? onwards have the same version 4.23 wrong labeled (source) :S
NEVER USE TOOLKITS, they can mess up the phone hard.. In your case I think you shouldn't have any problem to flash the system/boot/cache and recovery stock partitions from the stock factory image, or at least I'd try that. But do not touch the bootloader whatever you do!!!
Also for 5.0 and onwards you needed the 1.2 version of Minimal ADB and Fastboot, I think, be sure ur not using another one.
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Methods tried - 1-21
*TWRP #IRC*
Boot phone into TWRP, run these commands. You may have to flash factory images one more time if you get stuck at the splash screen (rather than looping)
Enter adb shell then copy and paste these two lines, separately.
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix bootloops for most. TWRP 3.2.1-1 causes a fatal error. The above shell commands should get 'most' running.
-----------------------------------------------------------------------
All methods below are MTC20F unless otherwise stated.
If you notice a method that worked, that I haven't listed please share with me with the source so I can have a full list.
Method 1
Followed instructions on flashing full firmware, found on g.co/ABH
Method 2
Followed instructions for OTA, found on g.co/ABH
Method 3
Followed @Heisenberg instructions in the HOWTO for manually flashing firmware via fastboot
Method 4
Flashed stock firmware, then wiped data/cache in stock recovery
Method 5
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-0
Method 6
Flashed stock firmware, then wiped data/cache in TWRP 3.0.2-1
Method 7
Flashed firmware via fastboot, then flashed full stock firmware through twrp (specify which version)
Method 8
Flashed firmware via fastboot, then flashed OTA firmware through twrp (specify which version)
Method 9
Utilized Wugs tool to flash full firmware
Method 10
Flashed firmware via fastboot, then sideload OTA via adb
Method 11
Flashed firmware, then flash your own TWRP backup
Method 12
@Eric214 says
Advanced wipe - System, Data, Cache and Dalvik.
Flash vendor image MTC20F.
Flash PureNexus, Gapps, SuperSu 2.76.
Reboot.
Method 13
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via fastboot
Method 14
Factory reset, flash TWRP, resize and repair all partitions, flash stock again via update.zip
Method 15
@shiftr182 method
Fastboot firmware, flash twrp, repair and resize, flash nougat bootloader, flash nougat update from HERE
Method 16
@neaznc021 method
"I'll note down the exact steps , most of which may or may not be relevant
1) Flashed MTC20F using TWRP 3.0.2-1
2) Booted into recovery and wiped everything and the partitions
- Add - Booted back into twrp 3.0.2-1 and then swiped to allow modifications
3) Then fastboot flashed TWRP 3.0.2-0
4) Restored my backup ( except recovery)
5) Still got stuck in the google screen.
Now the next parts are a bit weird
6) Booted into TWRP, flashed vendor.img from pure nexus rom
7) wiped everything except internal storage
8) Flashed vendor.img, pure nexus rom and gapps and then flashed vendor.img again
9) Rebooted and it worked"
Method 17
Fastboot stock, flash backup, flash MM ROM
Method 18
@rbouza1 method
"Fastboot format user data partition
Run factory image
Fastboot bootloader radio vendor
Flash twrp
Try and boot if not flash stock rom /any mm rom boot into twrp and try a restore. Those were my steps and it worked"
Method 19
@FragmentsOfLife method
1. Flash a stock image (I used the August stock image MTC20F)
2. Fastboot flash TWRP 3.0.2-0
3. Boot into TWRP
4. Select Wipe -> Advanced Wipe -> Select and repair each partition individually (some won't be able to, and that's fine, just move on to the next one)
5. Restore a full nandroid backup (make sure everything is selected) and reboot
6. You should now be free of the never ending boots, and if your device is bootlooped at this point (stuck at the boot animation), you can just flash stock again.
Method 20 @avivasaf
"Got backup from my friend, you need this!
Format userdata
Flash twrp
Make any backup
Move the good backup to the file backup
Restore it
Flash any Mm rom(i flashed cm13)
Fastboot flash mm bootloader, radio, vendor
And you got it!!!!"
Method 21 @Azhar05 method
flash developer preview 5 and flash latest twrp and then copy mtc 20f vendor image to twrp folder and then in twrp install image mtc 20f
Method 22
Let me know if you have more!
reserve 2
tr4nqui1i7y said:
I have a few ideas as to why the certain devices are getting, seemingly, hard-bricked. I won't put the info out there yet, I'd like to get more data first.
Can everyone do me a favour and fill this out? I want to try to find the exact issue at hand so we can better fight against it.
FORM:This info is found in the bootloader
Bootloader -
Baseband -
Variant -
CPU -
EMMC -
DRAM -
Console -
Qfuse status -
Download Mode -
This is found in bootloader - barcodes
Manufacture date -
Brief description of where the bootlooping started - Ex. "I was pushing system files via adb, and cmoding them. I ran SELinux fix in TWRP 3.0.2-0. Upon restoring my backup, I got bootloops"
I was able to fix the bootloop with these EXACT steps - OR*
*I have not been able to fix my device*
I have tried methods - *METHODS WILL BE IN POST #2*
My device is
Bootloader - 3.58
Baseband - 3.72
Variant - VN2
CPU - 0x20001
eMMC: 32GB Samsung
DRAM: 3072 HYNIX LPDDR4
Console - NULL
Qfuse status - Enabled
Download Mode - Disabled
Manufacture data - 11-13-2015
Click to expand...
Click to collapse
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
sixgunmojo said:
[/HIDE]
I don't have this problem but I have noticed that it appears that a lot of people with bootloop problems have either explicitly stated that they are "on TWRP 3.0.2-1" or say "I updated to latest TWRP". I've seen it mentioned enough times that I'm almost starting to wonder if there is an issue with TWRP 3.0.2-1. Just throwing this out, don't know if it helps or if you would also wish to collect TWRP version.
I would also like to see this issue resolved just for my own personal satisfaction. Good luck.
Edit - well hell you ninja'd me. I swear post #2 was reserved when I typed this.
Click to expand...
Click to collapse
Thanks, that would be useful. I'm thinking of how to incorporate that in a simple enough way that people don't accidentally provide incorrect information.
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
busbeepbeep said:
FORM:This info is found in the bootloader
Bootloader - angler-03.54
Baseband - angler-03.61
Variant - ANGLER-VN2
CPU - MSM8994 0x20001
EMMC - 64GB Samsung
DRAM - 3072MB HYNIX LPDDR4
Console - NULL
Device : Locked
Qfuse status - Enabled
Download Mode - Disabled
Manufacture date - 10/20/2015
Brief description of where the bootlooping started -
Stock, locked bootloader. Attempted OTA Friday night. It downloaded, then prompted to install. After some time I checked the phone, it had rebooted, but still in 6.0.1. It said Update failed, please try again. The OTA update came back up and asked me to download again. I decided to worry it about it later cause I needed to use the phone at that time.
On Sunday, phone locked up for 10 seconds while browsing CHrome, then restarted itself. Bootloop, showing the white google logo for 10 seconds, then black screen for 2 seconds, then back to google, infinite looping.
I can access the bootloader screen. From there, choosing any option besides Power Off results in the same bootloop with white google logo. Can't access recovery.
Contacted Google Support, they're sending me a new device. Very bizarre. It's crazy. After the failed OTA, I backed up some things from my device. I was going to research and finally unlock bootloader and root, and then phone crapped out before I had the chance.
I have tried methods - can't do anything except see the bootloader screen or the barcodes screen. Anything else results in white google logo
Click to expand...
Click to collapse
Your device isn't recognized by adb/fastboot?
tr4nqui1i7y said:
Your device isn't recognized by adb/fastboot?
Click to expand...
Click to collapse
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
busbeepbeep said:
Let me know if there are others commands I can try. At any rate, my replacement device is arriving Wednesday.
This is what I get:
adb devices: reports blank
fastboot devices: report serial #
adb reboot bootloader: reboots bootloader
adb reboot recovery: error: no devices/emulators found
fastboot flashing unlock: FAILED (remote: oem unlock is not allow)finished. total time: 0.014s
fastboot reboot: reboots and goes into white logo loop
Click to expand...
Click to collapse
Try this tool to make things a little easier, and more automated for now. Wugs
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
busbeepbeep said:
I've tried that tool to "temporarily boot stock recovery" but nothing happened on the device.
Click to expand...
Click to collapse
Boot into bootloader manually then try to run something
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Eric214 said:
Well I was able to update normally by flashing stock images and taking the OTA Thru the Phone. I did have an issue 2 days ago where I decided to wipe my phone and restore stock backup 7.0 At this point I started getting the boot loop nothing seemed to work so I'm assuming the newest version of TWRP has an issue with restoring backups on Nougat. Trying everything didn't work but what I had was my original EFS backups and the original stock back up from my phone which I believe was 29 Q I installed pure Nexus August 21st build restored my stock ROM and restored my EFS partition backup. Phone booted perfectly.
So now I'm wondering if the issue may lie in the efs partition.
Click to expand...
Click to collapse
What eMMC is your device using, if you don't mind?
tr4nqui1i7y said:
What eMMC is your device using, if you don't mind?
Click to expand...
Click to collapse
64GB Toshiba
Eric214 said:
64GB Toshiba
Click to expand...
Click to collapse
Just to clarify, you were able to get your device to boot?
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Jammol said:
Stock MTC20F ->adb sideload OTA -> Successfully booted and used N today. Factory Reset ->ensured OEM Unlock was still enabled -> flashed latest twrp -> performed full wipe including formatting data -> flashed MTC20F Vendor -> ran Flash-all script from factory image of MTC20F -> Running full stock MTC20F
Click to expand...
Click to collapse
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
tr4nqui1i7y said:
Just to clarify, you were able to get your device to boot?
Click to expand...
Click to collapse
Originally i had no issues I flashed factory images from Pure Nexus June build Via Fastboot. Rebooted the phone and took the OTA through the phone and then flashed TWRP 3.0.2-1 (the Newest one) and through TWRP flashed SuperSU 2.76 then FDR the phone before setting it up. All was fine and perfect. I made a backup and then factory data reset my phone Saturday and then restrored the backup. No go, Bootloop city. Got home did most of what was mentioned and nothing happened. Flashed PN through TWRP 3.0.2-1 and flashed my stock rom that came with the phone in Feb (29Q) and restored my EFS (I backup my EFS after any Android version change). The phone booted perfectly. no issues since. Took me about 2 hours total once i got home and was able to start using ADB and Fastboot commands.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
Also i forgot to add my info....
BL: 03.58
Baseband: 3.72
Varient: Angler-VN2
CPU: 0x20001
eMMC: 64GB Toshiba
DRAM: 3072MB Samsung LDDR4
UNLOCKED
Qfuse status: ENABLED
Off-mode-charge: Enabled
Download Mode: DISABLED
I also forgot, I was enrolled in the beta program obviously since i took the OTA through the phone.
tr4nqui1i7y said:
To clarify, this is for users to upgrade to N, then downgrade back to MM safely. This is not to correct the bootloop, correct?
Click to expand...
Click to collapse
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Jammol said:
Correct, this is just what I have done. Did not bootloop. Used N successfully for the first time today all day and then came back to MM.
Click to expand...
Click to collapse
Alright, thanks for clarifying. Didn't want to accidentally add something to the second post haha.
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...