Today I changed roms from AICP (w/TWRP) to AOKP (w/ their custom recovery) and have bumped into numerous issues, the main being that I can't sign into google and play services keeps crashing (it accepts the email/pass combination and the 2fa code sent to my phone but 'can't connect to google's servers' when finishing up). Before this the internal storage had disappeared, adb and fastboot wasn't working, the rom itself ran fine apart from play services crashing. As such I've decided to re flash everything, recovery included, using adb and fastboot rather than flashfire (which is I think what messed things up) only to find that my bootloader has locked itself and won't unlock with the oem unlock device command. It says that the operation completed but checking with fastboot I find my device is still locked so I'm stuck unless I sideload which is no good because if re flashing doesn't work I'm going back to TWRP and a different rom. Any help, much obliged
i have backed up every single partition last year with flashfire. i can send you if you want. dont know if it helps to restore bootloader partition. its kinda scary idea.
Related
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.
Previously I have unlocked the bootloader using
Code:
fastboot oem unlock
and it worked just fine. Using
Code:
fastboot oem device-info
both the "tampered" and the "unlocked" bit were set to "True".
Recently, and I have no clue why (possibly a program I tried to use for work that ended up not working), both of these bits are now set to "False"
I cannot flash a new recovery using fastboot, though my original TWRP recovery is still there.
I can still adb sideload update my OS, have root access, etc.
Now running
Code:
fastboot oem unlock
reboots into TWRP recovery with no effect on the bootloader status
I have already tried a few things suggested around here to no avail.
The only thing I can think of to do now is to treat it as a hard brick and completely reset everything and install a stock ROM to start from scratch following something like this thread.
If I can avoid this that would be preferable...
I had the same issue. For some unknown reason my partitions were all messed up so I was getting "bootloader locked" every time, witch is basically what they call a hard brick.
I've used that recovery tool and did fresh start with the latest TWRP and a new ROM. All back on track! Working well since over a month now.
I know it's a pain doing a factory reset and all but I think it's the only thing you can do...
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
Hi all,
I had recently unlocked my bootloader on my moto e4 (woods), installed twrp, and install magisk, and everything was going smoothly. Until recently, where i had a OTA update for the device. Me not thinking, i installed the update and then my device refused to boot to system, and only rebooted to twrp. I tried everything to get it to boot, but it just didn't.
I today, found on another thread, that you could reinstall the stock firmware onto the device, and followed the instructions, which were basically just running 'fastboot erase ----' and 'fastboot flash ----'. Everything was going well, until i came to system, which failed to install. I then tried restarting the device (because i wasn't thinking properly), and now the device will show the boot screen for approx 10 seconds then loop again. It has the message of ">device unlocked" at the bottom of the screen, and the moto logo and "powered by android writing on it". I have tried to access the recovery and bootloader on the device by using the hardware buttons, but there was no luck when i was doing it. It would just carry on with it's bootloop. I also tried plugging the device into a windows system, and ran 'adb devices', and 'fastboot devices' but nothing was being picked up. I also checked device manager, and no new devices were being shown.
I am 99% sure that i have indeed hard bricked the device, but i am turning to the amazing people of XDA devs for any help or tips that they can give to possibly get the device back and running.
Anything will be useful, since i can't make the device any less usable now anyway.
Thank you to anyone that replies
just Google the model number and get the original stock firmware and use SP flash tools and the scatter file took a hit to the latest firmware then use fastboot commands to unlock the bootloader flash custom recovery and root the device