Before I describe my issue I'll let you know I've been looking up articles on how to solve this for weeks now. first post to XDA, so bear with me I'm new
I have two OPT, both have a similar problem, but one is working (I dare not try to mess with it) and the other I've already tried and tried and now I'm stuck in fastboot, no recovery, no OS.
I HAD an OS on it (Paranoid Android 6.0.1), but I couldn't factory reset, and I needed to, so that I could sell the phone. when I tried to factory reset through OS settings, it would boot loop until I hard reset the phone. I had no recovery apparently (IDK how I did that) but trying to install a recovery requires the "OEM Unlocking" setting to be checked. and for some reason it won't let me check the box. My working OPT phone has the same problem, the "Allow OEM unlocking?" box pops up, I select enable, and the toggle moves itself back to the grayed out selection. so I couldn't install a custom recovery, I can't do any formatting or erasing in fastboot either without that selection for some reason either. trying to only gives me a "FAILED (remote: device is locked. cannot erase images)" or "FAILED (remote: device is locked. cannot flash images)"
AND SO, I tried this (search google for "mega unbrick guide for a hard bricked oneplus 2". I can't post links apparently as it is my first post. it will be on the oneplus website) and now I have no OS. or at least I believe I have no OS because trying boot causes a bootloop. I've tried all the methods, but I'm assuming because my bootloader is locked, It failed with the "A2001_save_brick_mini" tool.
And so, all I have right now is bootloader. didn't have a recovery I guess, and now I think I don't have an OS. and I can't do anything in fastboot because is returns with a "FAILED" hehe. dang locked bootloader. I have no idea how both of these phones have locked bootloaders anyways, because I obviously unlocked the bootloader to install a custom ROM in the first place. did the bootloader relock itself, or maybe during the process of installing the ROM, the bootloader relocked? I'm not sure as I wasn't watching for that. the phones had booted with the new OS, and so I happily went along my business and didn't find out I had a problem until I tried to factory reset one of them.
no I have no phones now with similar problems, but at different stages of the same issue.
My ONE A2005 is working, but I can't toggle the "OEM unlocking". At least it has a working custom recovery (TWRP)
and MY ONE A2003 is stuck in fastboot (fastboot recognizes it via "fastboot devices" and I can reboot and "fastboot oem device-info") with what I believe to be no recovery or OS.
ask me any questions to further explain my predicament, and PLEASE offer me any things to try. I ave two phones to test different things with. I would prefer to keep the working one working though.
Have you tried the fastboot oem unlock command?
DR_HAX34 said:
Have you tried the fastboot oem unlock command?
Click to expand...
Click to collapse
Ah yes, I forgot to write that in. That also results in a "FAILED (remote: unlock device to use this command)"
I can't unlock because of the OS, or perhaps lack of OS now; And I can't install a new OS or recovery because my bootloader is locked
use qualcomm recovery tool if you can't get any help. it'll restore your phone to 100% stock
Related
First, let me say this because i've used xda for a while and i know im going to get these responses:
I know this wont reinstate my warranty...
Why? Because I want to. I understand you think it's useless but it's not your phone...
I have tried "fastboot oem lock" and it doesnt work...
I've searched Motorola's site, got on a chat with them which was useless, and searched xda...
So I booted into AP fastboot and connected to my computer. Opened CMD and typed "fastboot oem lock begin"
That seemed to start the process so then ran RSD lite (as admin) and flashed a signed xml of 4.1.2
Yes, I edited the XML first and removed the 2 lines with "getvar" in them
RSD finished and the phone rebooted (which was great because before it was hung up on the unlocked bootloader warning)
Unfortunately after turning the phone off and then back on, the unlocked bootloader warning screen still came up.
And after booting back into AP fastboot it still said UNLOCKED.
did i miss a step?
I need to relock the phone. if anyone has useful information it would be extremely helpful. in the event it just cant be done thats fine. but i feel like it can, because after fastboot oem lock begin the command prompted told me that now i can flashed the signed images.
well crap. i may have just answered my own question. do i have to flash manually through CMD (ie fastboot flash system system.img) AND THEN run fastboot oem lock at the bottom? i'll try it tomorrow.
before i started this the phone was stuck on the bootloader warning screen so if anyone is stuck at that point this will allow you to boot up your phone. and if my results are typical, it did not relock the bootloader (obviously). hope I helped someone. hope someone can help me. thanks.
most likely not feasible
unlocking razr m involves phisically blowing a q-fuse, so you can't go back to locked
even if you could, it would be traced forever that you've unlocked the BL
You can relock the boot loader on the Dev edition, but once unlocked you can never go back to original status 0 of the boot loader and the boot logo will always display the warning even if you relock the boot loader. You have to flash that partition with another logo image to avoid that.
You also need to wipe the user data partition in fastboot first for the fastboot oem lock begin command to complete successfully.
Once that is done, when it reboots you will see that in fastboot it will display status 2 locked instead of status 3 unlocked.
This is a physical change that happens to the hardware when you unlock the boot loader an efuse on the board is blown and that memory location is permanently programmed. Its not even a question of them knowing, even though they do of course, the device itself is altered.
From my goodies
http://forum.xda-developers.com/attachment.php?attachmentid=2201206&d=1376991889
Flash from cwm or twrp.
Trade a locked one for your unlocked one? Lol I'm stuck locked on the newest ota
Sent from my XT907 using Tapatalk
I was using lineageos in my moto g4 plus. I wanted to flash stock again, so i did that. my bad I downloaded an update. After that i could pass the bootlaoder it shows an error message "failed to initialize partition table" . Recovery mode is also not working. since oem is locked i can not flash recovery, or any rom. what should i do to unlock the oem and flash a rom?
sunny_mathew said:
I was using lineageos in my moto g4 plus. I wanted to flash stock again, so i did that. my bad I downloaded an update. After that i could pass the bootlaoder it shows an error message "failed to initialize partition table" . Recovery mode is also not working. since oem is locked i can not flash recovery, or any rom. what should i do to unlock the oem and flash a rom?
Click to expand...
Click to collapse
almost the same here. my girlfriend´s moto g4 entered into bootloop, even though we havent tampered with custom roms, root or anything. so its got everything just like lenovo intented, rom, recovery, everything.
we managed to unlock oem at moto´s website, but since the system doesnt start, we cant enable it from developer options.
the bootloop takes us out of fastboot. and within fastboot we can scroll through the options but cant select any option.
is her phone a brick? or is there something we can do to save it?
we cant afford another phone nor tech service (right now), and she cant afford to be phoneless because of her job. so if anyone knows of anything it could help us a whole lot.
edit: also it doesnt charge
Hi. My friend mistakenly turned off her phone while it was performing an OTA.
Now it won't boot up and recovery doesn't even work. Fastboot does however work but not much else.
The device is completely stock with no USB Debugging and a locked bootloader. Additionally, the bootloader can't even be unlocked (fastboot oem unlock), as it wasn't enabled for unlock in developer settings.
This means I'm not able to do almost anything with fastboot.
What are our options here to restore the recovery and OS?
haverdaden said:
Hi. My friend mistakenly turned off her phone while it was performing an OTA.
Now it won't boot up and recovery doesn't even work. Fastboot does however work but not much else.
The device is completely stock with no USB Debugging and a locked bootloader. Additionally, the bootloader can't even be unlocked (fastboot oem unlock), as it wasn't enabled for unlock in developer settings.
This means I'm not able to do almost anything with fastboot.
What are our options here to restore the recovery and OS?
Click to expand...
Click to collapse
I suggest you guys try out the Unbrick Tool from this thread: https://forum.xda-developers.com/oneplus-5/how-to/op5-collection-unbrick-tools-t3898870
Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Gilly86 said:
Hello all! I have been trying to unlock my bootloader on my SGP311. I have searched the threads, followed the instructions, and still have problems. i initially looked at my service menu to determine if it is unlockable and it said yes. I then went through the steps to unlock it and it kept saying failed. Then, it finally worked, and my tablet rebooted. i got dual recovery loaded and then proceeded to wipe and install lineageOS from recovery. recovery kept failing to install the new rom. i then had to reflash a stock rom because the tablet wouldnt even boot into recovery again. now my service menu simply says rooting status: unknown and says nothing about the bootloader. What the heck happened?
Click to expand...
Click to collapse
You can't install LOS Rom from the dual recovery (XZDR). By flashing stock ROM, you bootloader may be locked again.
Check this guide to unlock it, and install LOS.
It simply will not let me unlock the bootloader anymore. And I can't seem to find a firmware that I can flash to get me to the appropriate version
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Gilly86 said:
so far, part of the problem is flashtool in androxyde still using the command fastboot -i 0x0fce oem unlock 0xkey. windows 10 denies this command every time and should be fastboot oem unlock 0xkey. But even doing so manually through the cmd prompt, it still will not let me unlock the bootloader. does anyone have a ftf file that has an unlockable bootloader? seems mine locked up completely when i reflashed the rom
Click to expand...
Click to collapse
bootloader is in device, not in firmware, so no such firmware exist you ask for.
Hi everyone,
Today I tried unlocking the bootloader on my Lenovo Z6 Pro to root my phone but I've hit a dead end.
I've enabled OEM unlocking and USB debugging on the developer options before using "adb reboot bootloader". I managed to get to bootloader mode alright, but neither "fastboot flashing unlock" nor "fastboot oem unlock-go" works; I always get "remote: flashing unlock is not allowed" or "remote: oem unlock is not allowed".
This makes it seem like I didn't enable OEM unlocking before, but I made sure it was enabled. Any ideas how I might solve this?
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Sayi Keshkar said:
Hi,
First you have to get the sn.img file for unlocking your bootloader from the zui website. Reboot to bootloader, first flash the img file and then enter the command for unlocking. As far as I have tried, you have to use this image file every time you need to unlock the bootloader(if you have locked it)
Good luck
Click to expand...
Click to collapse
Thanks for the reply. I gave up rooting my device for a while but I got tired of my phone bugging all the time so decided to give it another shot. This time I have another problem and it's driving me crazy: ADB wouldn't detect my phone when it's connected so I still can't unlock my bootloader. I tried installing every driver I could find but nothing works, but I can transfer files through explorer just fine. It occured to me that the USB might be the problem but it's the exact same one I used the last time I tried rooting it and I didn't have this problem back then.