Hello,
owning a Gedified french Xoom with stock ICS, I thought the official Jelly Bean OTA upgrade would be easy ... But it was not !
That's why I thought it would be good to make a little tutorial on how to do it.
There are 2 conditions for the OTA upgrade to work :
1) The recovery installed on your Xoom should be the STOCK ICS 4.04 one.
2) The bootloader must be LOCKED.
In my case, when I GEDified my Xoom, I left the bootloader unlocked after having flashed the Honeycomb U.S. image. There was no problem at this time, I could then easily upgrade upto ICS 4.04 with my bootloader unlocked. But when I tried to update with Jelly Bean, after the Xoom rebooted it was stuck with an image of the Android robot laying down ... It was impossible to do the upgrade. So I flashed the stock 4.04 Recovery, the installation of Jelly Bean could then go a little more further, but crashed again.
So I tried to re-lock the bootloader, but when done, when the Xoom rebooted it was stuck on an error message :
"failed image lnx 0x0002"
So in the case where your GEDified Xoom has still its bootloader unlocked, as you cannot re-lock it when running ICS, you only have one solution which will let you loose all your Xoom datas :
you need to unlock the bootloader, then re-flash the stock U.S. Honeycomb, then relock the bootloader, then re-apply all the Android updates upto Jelly Bean. At the end, your Xoom will be locked, unrooted, but running the stock Jelly Bean.
Here is how to do this :
Put all the HWI69 files into the same directory as the adb commands (I assume that you already know how to flash a ROM into the Xoom and you know where to download the ROM as your Xoom should have been already GEDified in the past), then open a dos commands window and do the following commands :
adb reboot bootloader (wait for the bootloader screen to be displayed).
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
So as said earlier, then your Xoom will be running the stock Honeycomb but with a locked bootloader this time, which will then let you to update your Xoom upto Jelly Bean.
I hope this little Tutorial will help you.
So it means that if you have rooted your Xoom, you cannot update to Jelly Bean without reverting to stock Honeycomb and therefore loose your data ...
Now I will have to manually reinstall each software, one by one, from the market as no backup software works without root permission ...
If I knew that before installing ICS, I would think twice before rooting it !
Thanks
Thanks for this. I was in the same boat, ie UK GEDified Xoom with an unlocked bootloader...
As dizzy33 has said in the bottom of his post this seems to appear if you rooted your Xoom. If you only unlocked the boot loader to flash the US ROM to make you Xoom a GED and did not do the step to root it the OTA update will work successfully and your data won't be wiped.
Mark-IE said:
As dizzy33 has said in the bottom of his post this seems to appear if you rooted your Xoom. If you only unlocked the boot loader to flash the US ROM to make you Xoom a GED and did not do the step to root it the OTA update will work successfully and your data won't be wiped.
Click to expand...
Click to collapse
No, what you say is only partially true : on a GEDified Xoom you need to have a locked bootloader, otherwise the OTA will not work.
The problem of rooting a Xoom is that you need to unlock the bootloader, and you cannot re-lock a bootloader if your Xoom is running ICS.
That's why you need to go back to Honeycomb to re-lock the bootloader, and then proceed with all the upgrades upto Jelly Bean.
But there is still the root issue. You cannot gain root access.
dizzy33 said:
No, what you say is only partially true : on a GEDified Xoom you need to have a locked bootloader, otherwise the OTA will not work.
The problem of rooting a Xoom is that you need to unlock the bootloader, and you cannot re-lock a bootloader if your Xoom is running ICS.
That's why you need to go back to Honeycomb to re-lock the bootloader, and then proceed with all the upgrades upto Jelly Bean.
Click to expand...
Click to collapse
My boot loader was unlocked and the OTA worked fine so something else must have caused your problem.
Mark-IE said:
My boot loader was unlocked and the OTA worked fine so something else must have caused your problem.
Click to expand...
Click to collapse
Mine was unlocked and I did have the issue Rolled back to honeycomb, locked the bootloader and im now all JB'ed up. Odd.
I, too, have been going through this crapola with my Xoom WiFi. The culprit is the locked bootloader the HC laden Xoom shipped with (as are some of the HTC devices, which are also a PiTHB because of bootloader issues).
The only issue, albeit not a major one, is that the JB update after the OTA is not rooted. I suppose it is a matter of time before we get a JB custom ROM with root.
I had grown to like my ICS rooted, unlocked Xoom. Now the annoying JB OTA notice will not go away until I go back to HC.
---------- Post added at 09:20 PM ---------- Previous post was at 08:57 PM ----------
Forgot to mention that I have had no luck (YET) flashing stachre's Stock rooted JB build http://forum.xda-developers.com/showthread.php?t=1796335
dizzy33 said:
Hello,
owning a Gedified french Xoom with stock ICS, I thought the official Jelly Bean OTA upgrade would be easy ... But it was not !
That's why I thought it would be good to make a little tutorial on how to do it.
There are 2 conditions for the OTA upgrade to work :
1) The recovery installed on your Xoom should be the STOCK ICS 4.04 one.
2) The bootloader must be LOCKED.
In my case, when I GEDified my Xoom, I left the bootloader unlocked after having flashed the Honeycomb U.S. image. There was no problem at this time, I could then easily upgrade upto ICS 4.04 with my bootloader unlocked. But when I tried to update with Jelly Bean, after the Xoom rebooted it was stuck with an image of the Android robot laying down ... It was impossible to do the upgrade. So I flashed the stock 4.04 Recovery, the installation of Jelly Bean could then go a little more further, but crashed again.
So I tried to re-lock the bootloader, but when done, when the Xoom rebooted it was stuck on an error message :
"failed image lnx 0x0002"
So in the case where your GEDified Xoom has still its bootloader unlocked, as you cannot re-lock it when running ICS, you only have one solution which will let you loose all your Xoom datas :
you need to unlock the bootloader, then re-flash the stock U.S. Honeycomb, then relock the bootloader, then re-apply all the Android updates upto Jelly Bean. At the end, your Xoom will be locked, unrooted, but running the stock Jelly Bean.
Here is how to do this :
Put all the HWI69 files into the same directory as the adb commands (I assume that you already know how to flash a ROM into the Xoom and you know where to download the ROM as your Xoom should have been already GEDified in the past), then open a dos commands window and do the following commands :
adb reboot bootloader (wait for the bootloader screen to be displayed).
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
So as said earlier, then your Xoom will be running the stock Honeycomb but with a locked bootloader this time, which will then let you to update your Xoom upto Jelly Bean.
I hope this little Tutorial will help you.
So it means that if you have rooted your Xoom, you cannot update to Jelly Bean without reverting to stock Honeycomb and therefore loose your data ...
Now I will have to manually reinstall each software, one by one, from the market as no backup software works without root permission ...
If I knew that before installing ICS, I would think twice before rooting it !
Thanks
Click to expand...
Click to collapse
Hi
I wonder if you could help
I have a stock UK Xoom on ICS
I have been trying to get it to jellybean using this method
I have used these commands successfully
adb reboot bootloader
fastboot oem unlock
it's at
fastboot flash boot boot.img
I get stuck
The xoom is in debug mode and when I run this command all I get is "waiting for device"
What am I doing wrong
Thanks
Related
I installed the stock motorola US wifi xoom 1st and then it auto updated to honeycomb 3.1 to 3.2 to 3.2.2 to ICS finally.. all in an hours time
of course the 3g doesnt work..
but what the hell
Could you give me some details about how you installed the Wi-Fi ROM?
ashwanikoul said:
I installed the stock motorola US wifi xoom 1st and then it auto updated to honeycomb 3.1 to 3.2 to 3.2.2 to ICS finally.. all in an hours time
of course the 3g doesnt work..
but what the hell
Click to expand...
Click to collapse
Because the update concerns the GED Xoom WiFi-only US model as of yet. The Honeycomb 3.2 refresh took months to reach EU/Asian 3G models the last time.
download the GED rom from here http://developer.motorola.com/products/software/MZ604_HWI69.zip/
extract to platform tools
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock ( need not do this)
using adb
like you have to go to stock if you are on a custom ROM
then flash via fastboot
and its all done...
I tried flashing 4.1.1 fw for my device and now everytime i restart or shut off my device i get an errror" AP Fastboot Flash Mode" Device is locked!
Fastboot reason: Flash failure. I wanted to unlock my bootloader but couldnt because i took an OTA update to 4.1.2. Something went wrong. Is there way to unlock my bootloader on 4.1.2? & how can i fix my FLASH FAILURE ERROR? Thanks
brhudson2012 said:
I tried flashing 4.1.1 fw for my device and now everytime i restart or shut off my device i get an errror" AP Fastboot Flash Mode" Device is locked!
Fastboot reason: Flash failure. I wanted to unlock my bootloader but couldnt because i took an OTA update to 4.1.2. Something went wrong. Is there way to unlock my bootloader on 4.1.2? & how can i fix my FLASH FAILURE ERROR? Thanks
Click to expand...
Click to collapse
If you were on the latest firmware, you can't downgrade. That's why you are getting the flash fail. Also, you can't unlock your BL if you're on the last two OTAs. You'll need to flash the most current FW via RSD or House of Moto.
Can any one help me to restore my XT907 back to stock JB 4.1.2 from the stock kitkat 4.4.2 update?
My current System version is: 183.46.10.XT907.Veryzon.en.US
Android Version: 4.4.2
Baseband Version: SM_BP_101031.042.32.86P
Kernal Version: 3.4.42-g5170b6b
[email protected] #1
Fri May 2 00:30:06 PDT 2014
Build Number: KDA20.62-10.1
Build Date: Fri May 2 00:20:25 PDT 2014
Please help me.. Thanks in advance...
Wouldn't recommend you try it on a locked bootloader.
Those that are unlocked shouldn't have any issues.
Technically, with a locked bootloader, if Fastboot will allow you to downgrade, then it should be possible.
You'd have to boot into Fastboot, then run the command:
fastboot flash system system.img
Where system.img is the 4.1.2 image file extracted from the fxz file. If it won't let you do this, then downgrade isn't possible. It will likely say failed flash and you'll have to flash something to kick the phone out of fastboot like logo.img.
You could also try RSDLite and try to flash the 4.1.2 fxz, but I doubt that will work because bootloader and such are not downgradeable and it will likely fail.
GnatGoSplat said:
Technically, with a locked bootloader, if Fastboot will allow you to downgrade, then it should be possible.
You'd have to boot into Fastboot, then run the command:
fastboot flash system system.img
Where system.img is the 4.1.2 image file extracted from the fxz file. If it won't let you do this, then downgrade isn't possible. It will likely say failed flash and you'll have to flash something to kick the phone out of fastboot like logo.img.
You could also try RSDLite and try to flash the 4.1.2 fxz, but I doubt that will work because bootloader and such are not downgradeable and it will likely fail.
Click to expand...
Click to collapse
Thanks for ur reply..
My bootloader is locked. I want to try downgrade to stock 4.1.2. Can u please send me the link to download stock 4.1.2 img and exact steps to downgrade?
Thnaks so much in advance..
kulsforu said:
Thanks for ur reply..
My bootloader is locked. I want to try downgrade to stock 4.1.2. Can u please send me the link to download stock 4.1.2 img and exact steps to downgrade?
Thnaks so much in advance..
Click to expand...
Click to collapse
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
GnatGoSplat said:
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
Click to expand...
Click to collapse
Thank u so much my friend, I need to clear that I m using this phone in India with Reliance CDMA network. If downgrade will succeed then will it in verizon locked condition or it will remain unlocked for global use? Also I need to add that I have never unlocked my bootloader or rooted my phone.
kulsforu said:
Thank u so much my friend, I need to clear that I m using this phone in India with Reliance CDMA network. If downgrade will succeed then will it in verizon locked condition or it will remain unlocked for global use? Also I need to add that I have never unlocked my bootloader or rooted my phone.
Click to expand...
Click to collapse
I think it would stay unlocked since you wouldn't be reflashing the radio.
It is easy enough to re-unlock if that should get reversed, however.
Ah, nevermind. Don't bother to try it. Even if you could succeed, you'd end up with black screen after the logo. The newer bootloaders will not allow Jellybean to boot. There is no way to downgrade. KitKat is a one way road with a locked BL. Sorry!
GnatGoSplat said:
Ah, nevermind. Don't bother to try it. Even if you could succeed, you'd end up with black screen after the logo. The newer bootloaders will not allow Jellybean to boot. There is no way to downgrade. KitKat is a one way road with a locked BL. Sorry!
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
GnatGoSplat said:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
Click to expand...
Click to collapse
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
GnatGoSplat said:
You can get them here:
http://sbf.droid-developers.org/phone.php?device=8
You can extract the original system.img from the archive as well as logo.img in case the phone doesn't allow you to flash system.img, you can use logo.img to kick the phone out of Fastboot. You will need to install Motorola ADB drivers on your computer in advance, and also need a fastboot.exe file which I think you can find via Google, but if you have ever rooted your phone in the past, usually that also came with fastboot.
Anyway, get into fastboot mode by turning off the phone, then holding down all 3 buttons. Use vol- to select Fastboot and vol+ to choose it. Phone should boot into fastboot.
Connect to PC and issue command:
fastboot flash system system.img
If it works, the phone should be downgraded. If it says flash failed, then downgrade isn't possible. In that case, if the phone is stuck in fastboot mode and can't be rebooted, issue this command to get out of fastboot.
fastboot flash logo logo.img
That should let it reboot as normal.
I actually doubt it's possible to downgrade, but I haven't tried it myself so I can't say for sure.
Click to expand...
Click to collapse
I'm also on official KK with locked bootloader, Can i flash kk modified system.img via this method ?
Prohyper said:
I'm also on official KK with locked bootloader, Can i flash kk modified system.img via this method ?
Click to expand...
Click to collapse
Sorry, with locked BL, you can't flash modified system.img or older system.img. I tried it just to make sure, and the phone wouldn't allow it.
GnatGoSplat said:
Sorry for the bad news. I'm in the same boat now too. Thought I would experiment with ways to preserve root, and long story short, now I'm stuck on an unrooted phone on stock KK with locked BL.
Why do you want to downgrade? If it's to be rooted, sorry, no solution for that. If there is some other issue, maybe there is a solution for that specific issue.
Click to expand...
Click to collapse
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
kulsforu said:
The issue is my CDMA data is not working after upgrade to kitkat. I m from India and using Reliance CDMA sim. Before update, everything was working perfect. But now only data(EVDO or 1x) is not working. GSM data(3G & 2G) is working.
Please help if u have any solution for this issue.
Click to expand...
Click to collapse
Good news is that major developments happened a month ago. :good:
You can now root AND unlock bootloader on KitKat. I think you can find the info you need in this thread:
http://forum.xda-developers.com/showthread.php?t=2783806
Once you have bootloader unlocked, you can downgrade back to JB. I have tried it and can confirm it works.
Good luck!
GnatGoSplat said:
Good news is that major developments happened a month ago. :good:
You can now root AND unlock bootloader on KitKat. I think you can find the info you need in this thread:
http://forum.xda-developers.com/showthread.php?t=2783806
Once you have bootloader unlocked, you can downgrade back to JB. I have tried it and can confirm it works.
Good luck!
Click to expand...
Click to collapse
Thanks much for update..
I can not getting the method. Actually I m new with these things.
Can you please explain how to use tr.apk?
Thanks in Advance..
kulsforu said:
Thanks much for update..
I can not getting the method. Actually I m new with these things.
Can you please explain how to use tr.apk?
Thanks in Advance..
Click to expand...
Click to collapse
You just run it and let it do its thing. Your phone should be rooted once it has rebooted. You can verify with any rootchecker app.
Then install and run Motopocalypse.apk to unlock your bootloader.
You can the use RSDLite to flash back to JellyBean using the JB fxz file. You will need to edit the xml file in the fxz file, removing the lines with gpt.bin and tz.mbn.
GnatGoSplat said:
You just run it and let it do its thing. Your phone should be rooted once it has rebooted. You can verify with any rootchecker app.
Then install and run Motopocalypse.apk to unlock your bootloader.
You can the use RSDLite to flash back to JellyBean using the JB fxz file. You will need to edit the xml file in the fxz file, removing the lines with gpt.bin and tz.mbn.
Click to expand...
Click to collapse
Thanks.. I m getting you.. But I m not using verizon network. My Razr M is unlocked for both CDMA and GSM carrier. I m using my Razr M in India and both CDMA and GSM are working at present. only DATA in CDMA is not working.
My question is will it be remain unlocked for both CDMA and GSM career in India after flashing back stock JELLY BEAN?
Thanks in Advance..
kulsforu said:
My question is will it be remain unlocked for both CDMA and GSM career in India after flashing back stock JELLY BEAN?
Click to expand...
Click to collapse
I believe so, yes.
GnatGoSplat said:
I believe so, yes.
Click to expand...
Click to collapse
Thanks.
Can you please send link to download JB 4.1.2 fxz file. and step by step instruction to flash the file.?
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.
I had hardbricked my devices while installing an OTA update and the device was Hardbricked .
I blank flashed the device and it booted and bootloader.
Now the problem starts here.
I flashed the OEM_Lock.bat as I wanted to relock the bootloader. I'm not sure what went wrong but the flash didn't complete and stuck in middle.
The problem remains here is it shows
Fastboot Reason: Failed to initialize partition table
I am unable to flash anything now. Recovery.img fails, bootloader.img fails, twrp flashing fails.
Nothing flashes as Bootloader is locked.
I went to Motorola Service Centre. They also couldn't do anything and simply said that their software doesnt read the phone.
Is there anyone whoe can really help me out with anything left to do?
Any method to force flash recovery, even twrp?
Phone is detected as Fastboot athene_16mp S in computer. It doesnt detect as "Qualcomm HS-USB QDLoader 9008".
What firmware are you attempting to flash?
Your device looks like it's still on the blank flash provided bootloader, which means you have to flash at least the GPT and bootloader. The lack of a serial number and the generic identifier implies you have not been able to flash an actual GPT and bootloader. Also, OEM_locked is normal until you get an actual bootloader flashed over the blank flash bootloader, which usually means trying to flash a GPT and bootloader at least as new as the latest version you had on your device (regardless of downgrades).
I'd suggest downloading the latest Nougat stock ROM we have from here. Do not use any of the scripts at this time.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Edit - also, this post probably is better suited to the Q and A section...
echo92 said:
What firmware are you attempting to flash?
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Unzip the file, delete any old stock ROMs from your ADB folder and copy over the new stock ROM. Try to flash just the GPT and bootloader then reboot to fastboot. See if you reboot into a fastboot screen with details.
If you do, I would proceed to flash the rest of the new ROM without locking your bootloader. If your device boots then, then you can reflash with the locking commands.
Click to expand...
Click to collapse
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
mysteryno46 said:
The files in mentioned firmware did the trick. It flashed GPT and Bootloader and showed the needed info.:highfive: After that I flashed the same firmware via fastboot commands and device has booted to the stock 7.0 - Bootloader Unlocked. How crazy was I to ignore the proper files to flash? I probably tried 100 times to flash files (wrong once for sure). Thanks alot though for providing the link and instructions. :silly:
Now one last thing, should I flash OEM_Lock file to lock the bootloader so that I can get the lastest Oreo update? I might even think fo selling the device after locking the bootloader. Need your genuine opinion on this as well.
Click to expand...
Click to collapse
Eh, you live and learn. Besides, you've now got your device running now!
Honestly, it's up to you. Having a locked or unlocked bootloader will not affect your ability to receive OTA updates - you should still receive updates so long as your firmware matches your software channel (and since your device was XT1643, the NPJS25.93-14-18 April 2018 security update should be the correct firmware). At this moment in time, you'll have to use the NPJS25.93-14-18 firmware to re-lock your bootloader - we don't have the stock Oreo firmware at this time. Thus, if you update to stock Oreo, you will not be able to re-lock your bootloader until you can get a leak of the Oreo firmware.
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Back to Locked Bootloader, complete stock.
echo92 said:
Eh, you live and learn. Besides, you've now got your device running now!
If you're selling, I'd choose to re-lock the bootloader. Else, a potential buyer who is not used to flashing custom ROMs might wonder if there's any tampering with the device (the bootloader unlocked warning, to someone not used to flashing custom firmware, might scare off potential buyers).
Click to expand...
Click to collapse
I am back to Locked Bootloader as feel the same as you said that anyone buying might get scared by looking the warning sign. Thanks for helping out. :highfive:
Oreo Update via OTA has already started rolling out as per the news I've been reading. I just wanted to see the oreo 8.1 before I sell the phone.
Anyways I got a new device now, Realme C1, 3|32GB as my smartphone usage has declined a lot recently and might remain similar. This device will suffice my requirements.
Thanks for the help and support. :victory: