Carrier unlocked XT1687, bootloader unlocked and with rooted stock potter 25.137.35.
I never allowed the Motorola Security Update to load, I 'd been tapping "Maybe Later" for a week.
On Friday I noticed the "Maybe Later" option wasn't there, so I simply "backed-out".
Saturday morning, the update was shown as completed. WTH??
I did still have root (was able to use root permission apps) so I rebooted but it kept going into TWRP recovery.
Using "start" would allow the phone to boot normally.
I tried a few non-destructive things, no joy.
I finally reflashed the stock potter. As a phone it's working OK
But now..
adb and fastboot seem to function OK, but when I try reboot bootloader commands I get "bad boot" state.
I also noticed the OEM unlock in dev options is gray-out, it may have been that way after the bootloader unlock, I just never noticed?
When I boot into recovery, TWRP 3.2.x main screen just sits there no way past it.
I'm now in way over my head,
Any help/advice is appreciated.
drk
Flash stock image again thats all
When I flashed the stock, I got the bootloader image signed with key bad key.
When I tried flashing recovery twrp.img (3.2.1-potter) I got image not signed or corrupt
I didn't expect to see bad key when flashing stock.
And Oops I forgot it will show bad or corrupt no matter.
All fixed.
Thank You
Related
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 :|
My 6p is stuck in a bootloop. nbd90x build my bootloader is locked is there anyway to unlock from adb. I have already tried sideloading ndb90x through adb wipping chache and user data and still no luck. Help me Xda youre my only hope..
So you previously enabled USB debugging, how about OEM unlocking? If so, use 'fastboot flashing unlock' to unlock the bootloader. Note that internal storage will be completely wiped. Everything. Though with USB debugging enabled, you should be able to adb pull the contents of you SD card first. If you can unlock the bootloader you can try flashing factory images with fastboot. Otherwise, not much else besides RMA it with Google. There's been a few reports of stock N6Ps bootlooping. Haven't seen anyone post that Google denied the claim.
no bootloader is locked so cant flash using flashboot but debugging is enabled so I am able to use adb .
I know. What I'm asking is if you enabled allow OEM unlocking in developer settings? That doesn't unlock your bootloader in itself. You still need to use fastboot to do it. However if that setting IS enabled what you can do is... Use ADB to pull your internal storage to PC. Then use fastboot to unlock the bootloader and flash factory images. If the setting is not enabled, and wiping data and flashing an OTA don't work, I'm not sure what else can be done.
You can try downloading the 7.1 dev preview OTA and seeing if it updates whatever is causing it to fail. Other than those, RMA would be your best bet.
https://developer.android.com/preview/download.html#device-preview
After sideloading a ton of times between 7.0 and 7.1, one time i got it to boot up then i immediately enabled oem unlock then it crashed again... so now I am able to flash through fastboot although I havent been able to get it to boot again. Is it normal for bootloops to not get fixed by flashing?
Hijacking your post to report what is happening to me. I posted the same thing on the Android Beta program community on G+.
Have been using the latest beta since it came out on completely stock 6P (locked bootloader, unrooted). Everything working normally when yesterday around 10 or 11AM, phone starts to bootloop OUT OF NOWHERE, it was just sitting there on the table while I was working. I could still get to bootloader/recovery, so that was a bit of a relief. First thing I tried: clear cache, nothing. Then proceed to wipe/factory reset the device, to no avail. Immediately downloaded the latest factory image from Google's page, tried flashing it but couldn't since the bootloader was locked (OEM unlock option also disabled). Then downloaded the beta OTA and sideloaded it, process went through OK but device still bootloops. Tried sideloading the latest stable OTA but didn't work since it was from a previous build. Ran out of ideas. So there I was creating a thread on XDA for help while the device was still on its bootloop rush, about to hit the Submit button when again OUT OF THE BLUE SKY the device decides to boot itself back up. First thing I did was unlock the bootloader. Phone worked normally for 6 or 7 hours, when I'm doing something on it and then again, screen froze and bootloop starts again. This time I only reset the device and left the it bootlooping, after about 30 minutes it boots up again. I unenrolled from the beta and installed the latest 7.0 build. Everything working fine for the last 12 hours. Anyone have any idea on what can cause the device to bootloop like that? Never seen anything like it.
Yea I signed up for the beta program too do you have the link to unenroll? So you just reset and let it sit?
Here you go
google.com/android/beta
do you remember what you did to get it to boot?
noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
Well, that's the thing. Everything I tried didn't seem to work. I couldn't flash the factory image since the bootloader was locked. I was able to sideload the beta OTA but the device still bootlooped after that. So I just left it bootlooping and after around 20 or 30 minutes the device booted normally. I have no idea what caused it and what I did to make it work again.
P.S: device restarted 2 times while I was typing this.
noetre said:
do you remember what you did to get it to boot?
Click to expand...
Click to collapse
If your boot loader is locked you are screwed, sorry to say, I would RMA it. Unbelievable an update can mess a phone up...that's why I always unlock the bootloader first thing and never lock it. I need complete control of my phone.
Edit: Only thing I can think of is delete the partitions with fastboot or adb and reflash factory image.
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
noetre said:
boot loader is unlocked now Ive tried flashing using the flash-all script but the phone still wont boot
Click to expand...
Click to collapse
As a last resort, flash all of the images manually with fastboot. This will wipe all userdata and completely format the SDcard. Nothing will be left. Extract the bootloader and radio images from the factory images zip. Flash them in fastboot. Reboot to fastboot again. Extract the next zip in the same folder as BL & radio images and flash the vendor, system, boot, recovery & userdata image files. Just for good measure, boot to recovery (stock Android recovery) and perform a factory reset & cache wipe. If the phone still fails to boot, your only option would be to RMA it at this point.
Note: As per Heisenberg's sticky thread, do NOT flash userdata.img if you have anything besides the 32gb model as you will only have the ~32gb storage available. If you're using a model with more storage, just use fastboot to format userdata but don't flash the image.
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
noetre said:
Ill try that.. but isnt the warranty voided because the bootloader is unlocked?
Click to expand...
Click to collapse
Not on a Nexus, no.
Added: I had to RMA mine after the phone got its first update. I unlocked the bootloader and stayed stock for a long time (until N came out). I took the OTA in About Phone and it applied with no problems but the phone would not boot. Factory images also couldn't get it running. Stock recovery and all. RMA'd without issues. I didn't tell them, just sent it in. If they tried to boot it they would've seen the unlock symbol. There's also a thread somewhere buried in the general section where someone called Google and asked and they confirmed to them that unlocking does not void warranty. I'll try to find it for you.
Found it: http://forum.xda-developers.com/nexus-6p/general/unlocking-bootloader-warranty-google-t3229804/page1
I also returned 4 faulty Nexus 5's (mostly screen artifacts) all unlocked with no problems.
I was running Pure Nexus. My camera won't focus at distance, so I was trying to revert the phone to stock before RMAing it.
I used #10 in this guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) and flashed all the pieces.
This is the zip I used for the images - https://dl.google.com/dl/android/aosp/angler-n4f26o-factory-c53f0a50.zip
Then I formatted userdata, relocked the bootloader, and tried to reboot. It's now stuck on the Google logo. It doesn't look like it's looping, it's just stuck.
I can boot into the stock recovery, but since it's a fresh install, USB debugging is not set so I don't think I can ADB anything. And since I locked the bootloader, I don't think I can fasboot flash anything either.
Am I out of luck?
Since I was going to send it back anyway, should I just blame the return on the fact that it won't boot?
Thanks
Edit: Huh, I think I got it to work. I had tried the guide to flash a full OTA as a fix, but when I got to "ADB devices", it wouldn't see my phone. But I tried it again, and it did see the phone and I was able to flash the OTA. It's rebooting now.
Hi guys...
So my OnePlus 2 was having some issues yesterday, and I flashed the stock ROM. This was completely fine and dandy, but I also wanted to put the stock recovery on it. I made sure OEM unlocking was on, went into fastboot, and typed in "fastboot oem unlock" like normal. It finished in like a tenth of a second which I thought was a little strange. The phone rebooted and I put it back into fastboot. I tried to flash the recovery and it said (remote device is locked. Cannot flash images). So at this point I was frustrated. I went into TWRP and installed the SuperSU binary. Then, I went to the Play Store, downloaded Flashify, and flashed the recovery onto my phone. I restarted my phone.... and bam. Recovery wouldn't work anymore. And then when I tried to boot into normal Android it still wouldn't work, just stuck on the OnePlus and Android screen, as if there was no /system/ partition. I can still get it into Fastboot, and I put it in EDL mode and installed the Qualcomm 9008 driver, and flashed OxygenOS 3.0.2 through the MSM downloader from https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ and the MSM downloader just gave me an error that, in garbage text, said something about Sahara and Firehouse or something like that. I did get it to go successfully by downloading a different recovery package (I believe it was Color OS 2.0) but I have a ONE A2005 and I belive that was meant for ONE A2001 and it caused my phone to constantly flash rapidly at the Oneplus and Android screen (it would start to boot then immediately shut off). Fastboot still works but it still says the bootloader is locked so I can't really do anything. Any help would be much appreciated!
Jack
Update: I finally got Recovery to work. However, it still gets stuck on the OnePlus & Android screen, even after sideloading a stock ROM and installing it via the stock recovery. I fear my boot.img is corrupted. Does anyone happen to know where I can find a stock ROM that comes with recovery.img, boot.img, system.img, et cetera?
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
superblox02 said:
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
Click to expand...
Click to collapse
You should be able to unlock it in fastboot or adb
OEM unlock or something like that
Check this thread https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
Hello, I've recently been stumped. Last night I attempted to install Lineage OS on my Axon 7 A2017U. I used Axon7Toolkit to unlock the bootloader and install TWRP. This was the first I've seen of the warning from google telling me to lock my bootloader. (My Motorola Nexus 6 never did this) So I ignored it until I had Lineage installed and when I tried to boot, the system was encrypted with a password. The internet said there is no password. I just have to wipe in TWRP. So I tried that to no avail. At that point I said screw this. I'm gonna go back to stock before I mess anything up. Flashed stock using MiFlash. Everything is good and dandy except that aforementioned warning message when booting. No matter what I try, I can't get into fastboot to lock the bootloader. Every time I try, it shows that message and boots normally. I've tried using "adb reboot bootloader" it went to the message and boots to OS. I tried holding power and volume up then selecting bootloader. Same result. I tried holding power and volume up then selecting recovery (this is when I realized TWRP was gone. It must have been overwritten when flashing stock firmware) and then reboot to bootloader. Same result. I really don't know what else to try. I guess I could ignore it, but that's really not what I'm looking for.
ScottDemon said:
Hello, I've recently been stumped. Last night I attempted to install Lineage OS on my Axon 7 A2017U. I used Axon7Toolkit to unlock the bootloader and install TWRP. This was the first I've seen of the warning from google telling me to lock my bootloader. (My Motorola Nexus 6 never did this) So I ignored it until I had Lineage installed and when I tried to boot, the system was encrypted with a password. The internet said there is no password. I just have to wipe in TWRP. So I tried that to no avail. At that point I said screw this. I'm gonna go back to stock before I mess anything up. Flashed stock using MiFlash. Everything is good and dandy except that aforementioned warning message when booting. No matter what I try, I can't get into fastboot to lock the bootloader. Every time I try, it shows that message and boots normally. I've tried using "adb reboot bootloader" it went to the message and boots to OS. I tried holding power and volume up then selecting bootloader. Same result. I tried holding power and volume up then selecting recovery (this is when I realized TWRP was gone. It must have been overwritten when flashing stock firmware) and then reboot to bootloader. Same result. I really don't know what else to try. I guess I could ignore it, but that's really not what I'm looking for.
Click to expand...
Click to collapse
The sticky edl thread has stock b15 with fastboot. Make sure to fully wipe and have stock recovery before attempting to relock.
Sent from my ZTE Axon 7 using Tapatalk
ScottDemon said:
Hello, I've recently been stumped. Last night I attempted to install Lineage OS on my Axon 7 A2017U. I used Axon7Toolkit to unlock the bootloader and install TWRP. This was the first I've seen of the warning from google telling me to lock my bootloader. (My Motorola Nexus 6 never did this) So I ignored it until I had Lineage installed and when I tried to boot, the system was encrypted with a password. The internet said there is no password. I just have to wipe in TWRP. So I tried that to no avail. At that point I said screw this. I'm gonna go back to stock before I mess anything up. Flashed stock using MiFlash. Everything is good and dandy except that aforementioned warning message when booting. No matter what I try, I can't get into fastboot to lock the bootloader. Every time I try, it shows that message and boots normally. I've tried using "adb reboot bootloader" it went to the message and boots to OS. I tried holding power and volume up then selecting bootloader. Same result. I tried holding power and volume up then selecting recovery (this is when I realized TWRP was gone. It must have been overwritten when flashing stock firmware) and then reboot to bootloader. Same result. I really don't know what else to try. I guess I could ignore it, but that's really not what I'm looking for.
Click to expand...
Click to collapse
No, you don't have to WIPE in TWRP, you have to FORMAT DATA! It does roughly the same thing (you lose all your data and internal storage) but since the internal partition is encrypted, it de-encrypts it. To avoid having to lose the internal storage again you just have to flash Magisk or SuperSU right after flashing the ROM (before booting for the first time) and you'll be able to change ROMs with no problem. (but flash magisk right after changing the rom too, of course).
The unlocked bootloader disclaimer is completely normal, however if you're annoyed by it you can get rid of it by following Raystef66's guide called "remove unlocked bootloader inscription".
Happy flashing. Knowing all that, you can go back to Lineage or sth again. Just remember this: If you have access to EDL mode you can get out of the nastiest of bricks. And the A2017U defaults to EDL if there's something seriously wrong. So the U os basically unbrickable
p.s.: NFound's AEX bootloader comes premade so that you won't have the unlocked bootloader inscription. But you have to use one of the Oreo ROMs.
p.p.s.: You can reinstall fastboot and lock but it's just a very bad decision. Just ask if you ever have that sort of trouble, at least I will see it and reply