So a while ago I rooted my phone but messed it up because I uninstalled a few too many system apps. I just dealt with it for a few months since I could still make calls (but not much else). I finally bit the bullet to look into flashing the stock rom again, but to do so it looked like I had to install a custom recovery, but to do that, unlock the bootloader. So I first unlocked the bootloader using motopocalypse (batch file didn't work but apk did), and got the expected BOOTLOADER UNLOCKED message at bootup, with fastboot saying unlocked, code 3. I then tried flashing CWM recovery via Rom Manager, and it seemed successful, but I was unable to boot to it either from the UI of ROM manager or from holding the buttons during bootup, it would just hang for a few more minutes than normal at the BOOTLOADER UNLOCKED screen, then boot up like normal. So I kept reading, found RSDlite, and was able to flash the stock rom, which I downloaded from the internet and the phone boots up fine, but now fastboot says locked, status code 2, and motopocalypse does not unlock it again (either the batch file or the apk), but I still get the BOOTLOADER UNLOCKED message at bootup. So I'm not sure if my bootloader is unlocked or not and if I can proceed with installing CWM recovery again, so i can make a full backup in case I mess something up again.
So how do I reunlock the bootloader, or verify if it's locked or not?
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
RikRong said:
First, CWM and TWRP aren't official for this phone, so you can't use their apps to flash. You'll need to use fastboot, Flashify, or Rashr. Second, you're still unlocked, we've seen this error come from bad flashes. What is the complete text on your FB screen. You should be able to clear this by re-flashing with RSD. What firmware did you attempt to flash?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FB screen:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 00:54:39)
eMMC Info: Size 8GB
Device is LOCKED. Status code: 2
Battery OK
Transfer Mode:
USB connected
Fastboot reason: Reboot to bootloader
usb connected
I've tried reflashing with RSD previously but no change. I could try it once more if you want.
Not entirely sure what you're asking for with the firmware version, but the image I used was for android 4.4.2, version 183.46.10.XT907Verizon.en.US.
modemman11 said:
Device is LOCKED. Status code: 2
Click to expand...
Click to collapse
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Code 3 as well.
Sent from my XT907 using XDA Free mobile app
rahimali said:
I think your boot loader is still LOCKED. Mine is showing UNLOCKED. Status code: 3. You cannot flash a custom recovery on a phone with a locked BL. You need to motocalypse again!
Click to expand...
Click to collapse
Yes, that's why I'm asking. So I've got one vote for unlocked, one for locked. As I said though, motopocalypse isn't working a 2nd time.
AndyYan said:
To trace the issue from the ground up, if you're just trying to reinstall stock ROM, you should be relying on RSD instead of trying to mess with custom recoveries and BL unlocking. Just flash .10 (not .15) via RSD, root via Towelroot and you can start fresh.
Unlocking your BL is still highly recommended, though, 'cuz it's now or never.
Click to expand...
Click to collapse
I would like to flash custom ROMs later down the road, but for now I just want to get the stock stuff going.
On a side note, the version of the image I downloaded was 183.x.x, but my mother, who has the same phone, purchased at the same time, and has never rooted it or anything, has version 182.something, and that is also the version I had before I started messing with the bootloader/recovery stuff. The two versions were released at the same time, but I don't know what determines which version you got if you just did OTA updates, or if it even matters. Speaking of OTA updates, the version I downloaded is prompting me to do an OTA update now to another 183.x.x version. I wonder if I'd be able to grab the 182.x.x ROM from my mom's phone without rooting it via fastboot or something.
The 182/183 does not matter regarding root/boot loader unlock its the .10/.15 that matters do not take the .15 without unlocking your boot loader....
We cannot teach people anything; we can only help them discover it within themselves.
So no other thoughts? What would happen if I flashed a custom rom/recovery with a locked bootloader? I tried flashing the ROM again and fb still says locked, code 2, and motopocalypse still doesn't do anything like it did the first time.
modemman11 said:
What would happen if I flashed a custom rom/recovery with a locked bootloader?
Click to expand...
Click to collapse
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
modemman11 said:
So how do I reunlock the bootloader, or verify if it's locked or not?
Click to expand...
Click to collapse
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
lem22 said:
It won't let you flash a custom recovery. This is the difference between locked and unlocked.
Click to expand...
Click to collapse
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
If your bootloader is relocked for some reasons, try unlocking it again with
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Code:
D:\adt-bundle-windows-x86-20140702\sdk\platform-tools>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.031s]
finished. total time: 0.031s
Still locked code 2 though. Looks like it wants an unlock code from Motorola's website, I tried following the steps to get the code but it says I'm not eligible for bootloader unlock. So unless there's another way to get the unlock code...
modemman11 said:
I guess what I'm asking is, will it let me flash it but then the phone won't work or will give an error on boot, or perhaps brick my phone? Or will it just not flash in the first place? Because if it's the latter, then I can just try to flash a custom ROM/recovery and if it works then I know it's unlocked.
Click to expand...
Click to collapse
A "Code 0" locked device would refuse flashing an unofficial or older recovery. I have no idea about Code 2 though.
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
From what I was able to locate status code 2 indicates that the bootloader has been unlocked and relocked like by doing the whole "fastboot oem unlock unlock code" then the "fastboot oem lock" ... I'll look more into it but from what little I read it looks like it can not be unlocked again with out the Motorola unlock code...
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Same here, I can see what it means but cannot find any way to get back to code 3 other than using the unlock code from Motorola, which I am unable to obtain because it says I am not eligible. Surprising that someone hasn't cracked the unlock code yet or made a keygen, people are so eager to do it with pirated computer software before the software is even released.
I've read of someone getting locked status code 2 b4 from flashing an older gpt with rsd (if I remember correctly) I think all that was required to fix it and get unlocked again was to flash the latest gpt. Very important..... Are you sure when you were unlocked you didn't ota update to .15? Because flashing .10 gpt while on .15 may be what caused your false relock
Nope, no OTA update to .15. The ZIP I have of the rom does include the gpt.bin file with the same timestamp as all the other files. I suppose I could try reflashing the whole rom once again later...
Hmm strange, I went to find the old thread I read about the gpt relock issue but it's not exactly the same as your situation.
http://forum.xda-developers.com/showthread.php?p=51436123
Until now I didn't think relock was possible due to the way unlocking works. It's a physical change, a qfuse was blown when the motopocalypse apk was run the first time. It can't be unblown lol. Wish I knew what went wrong here.
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Also have the same problem generated by the very same software!!
Anyone have any further info please?
MiMilz said:
Hi everyone !
I searched for a case like mine on the forum, but didn't find a solution to my problem, so you're my last hopes !
I have a Nexus 7 (2012) WIFI for a while now and I wanted to return to stock, on Lollipop (I was on Paranoid Android ROM, 4.4.4).
So, l used the Nexus Root Toolkit and ran the "return to stock + unroot" feature.
I downloaded the last google image for my device (5.0.2) and let the thing began.
It erases all partitions like it has to do, but when it needs to write bootloader, it fails and says: "FAILED (command write failed (Unknown error))".
I tried severals time, but always same problem. So I tried to flash stock 4.4.4, but can't write bootloader too: "FAILED (No suck device)" or "FAILED (too many links)" errors appear, something like those.
So, in last hopes, I tried to do this manually and followed this thread: http://forum.xda-developers.com/showthread.php?t=1907796
I erased correctly all partitions, but when I need to flash bootloader with "fastboot flash bootloader bootloader-tilapia-4.23.img" command, I get "FAILED (command write failed (Unknown error))" too...
I can't flash recovery, get the same error as the bootloader one...
If someone had the same problem or if someone can help me to restore my Nexus 7, it would be very kind !
Thanks to everyone who'll read this
Click to expand...
Click to collapse
PaulG2000 said:
Also have the same problem generated by the very same software!!
Anyone have any further info please?
Click to expand...
Click to collapse
It's pretty well known that for some reason, the bootloader images included on many of the factory images for grouper are not valid, and Google has never corrected this. You'll need to grab a valid bootloader from a different factory image, and flash it manually.
Check this thread out, it's all been covered in great detail there: http://forum.xda-developers.com/showthread.php?t=2573015
Edit: Also, if you're already on a valid bootloader version 4.23, then there's no need to flash the bootloader again.
Need Help..
I Am trying to Unlock my Bootloader in my ZE550KL:
- I was on Marshmellow stock Rom.
- Flashed 1.17 but was not able to unlock my bootloader.
- Then Flashed to 1.16.40.763 But still unable to lock my bootloader.
I am running Asus official Bootloader unlock tool(Unlock Device Tool) it is running without any issues but when i check the phone status in fastboot mode.
fastboot oem device-info
But bootloader status is false..
Please can someone help me how to unlock my bootloader..
Same problem here. Help us out
same problem here
Me too! I got the same problem with you guys
Same Problem
Same prblm..no idea to unlock boot loader
Unlocked mine by using this
http://forum.xda-developers.com/zen...ock-bootloader-asus-unlock-app-t3405850/page1
If you want I can help you. I have unlocked mine using a unique way....
Akash Karthik said:
If you want I can help you. I have unlocked mine using a unique way....
Click to expand...
Click to collapse
Yeah. It would be really great if you help me out with
it.
What is that
If you want to flash a custom rom, you don't need to unlock bootloader for it.
You can flash custom recovery using fastboot mode, after which you can install custom roms.
Ashish8017 said:
If you want to flash a custom rom, you don't need to unlock bootloader for it.
You can flash custom recovery using fastboot mode, after which you can install custom roms.
Click to expand...
Click to collapse
I did the same method as you are telling. I was able to install twrp through fastboot successfully(without unlock the bootloader) and installed custom rom and gapps successfully too. But when I reboot my device after installation I stuck in boot logo every time. I waited more than 30mins but nothing happened. No matter which rom I tried but I had to face the same problem ?. I don't know how to get rid of this issue.
And also my twrp showing an error which is -failed to mount/factory (invalid argument).
I think this is the reason why I'm facing bootloop.
---------- Post added at 09:56 AM ---------- Previous post was at 09:41 AM ----------
-Zeus- said:
Unlocked mine by using this
http://forum.xda-developers.com/zen...ock-bootloader-asus-unlock-app-t3405850/page1
Click to expand...
Click to collapse
I also unlocked mine using the same method that you have used. And successfully unlocked my bootloader. Then I installed twrp using fastboot. But my twrp showing an error which is -failed to mount/factory (invalid argument).
Then I successfully installed custom rom and gapps ( I wiped cache after installation) but when I reboot my phone I stuck in boot logo. I waited more than 30mins but nothing happened.
I tried so many roms but had to face same problem.
Is the twrp errors the reason of my bootloop issue??
foysal04 said:
I did the same method as you are telling. I was able to install twrp through fastboot successfully(without unlock the bootloader) and installed custom rom and gapps successfully too. But when I reboot my device after installation I stuck in boot logo every time. I waited more than 30mins but nothing happened. No matter which rom I tried but I had to face the same problem ?. I don't know how to get rid of this issue.
And also my twrp showing an error which is -failed to mount/factory (invalid argument).
I think this is the reason why I'm facing bootloop.
Click to expand...
Click to collapse
https://www.asus.com/zentalk/in/thread-128115-1-1.html
Refer to this asus zentalk link.
flash twrp again and make sure to keep your volume down button pressed before entering the "FASTBOOT REBOOT" command.
Clear ur data after flashing twrp, flash trustzone fix also if you're getting error 7, install ur desired custom rom. It should work!!
I did the same a couple of days ago, it worked for me.
Ashish8017 said:
If you want to flash a custom rom, you don't need to unlock bootloader for it.
You can flash custom recovery using fastboot mode, after which you can install custom roms.
Click to expand...
Click to collapse
To install ROM you need a unlocked bootloader , screw twrp for now.
Hi everyone,
I have made a terrible mistake... I flashed twrp before unlocking my bootloader. The phone boots then shows a message like "please update to the authorized image", and the get stuck into bootloader, do you have any idea how to recover that, because now we need to login on the phone to get bootloader unlock code and, obviously, I can't.
I flashed twrp by doing, once rooted with kingroot, dd if=/path/to/twrp.img of=/dev/block/by-name/recovery.
When I try to flash with fastboot I get FAILED (remote: Command not allowed), is any alternative flasher available or another way to get the unlock key? I thought about useragent modification to make huawei website thinks it's the phone. So if anyone could send me is useragent by PM I'd be thankful.
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.