I have read multiple threads from people trying to relock there device and having a nightmare experience and I have also been thru the LNX 0x0004 experience so this is why I am posting this.
First off I flashed back to stock unrooted via the SBF files that were originally available to receive the OTA to 3.1.
Now that I am on 3.1 the SBF files no longer work to revert back to stock.
Being that I took the OTA what are my options to get my Xoom relocked ?
I know the latest images for 3.1 are not available yet (if ever) and when I originally tried to flash the 3.01 img files that is where I ran I to LNX 0x0004.
What could have went wrong? Bad download? Or Is it a no no to flash the 3.01 files over the 3.1 OTA update?
Brenardo said:
I have read multiple threads from people trying to relock there device and having a nightmare experience and I have also been thru the LNX 0x0004 experience so this is why I am posting this.
First off I flashed back to stock unrooted via the SBF files that were originally available to receive the OTA to 3.1.
Now that I am on 3.1 the SBF files no longer work to revert back to stock.
Being that I took the OTA what are my options to get my Xoom relocked ?
I know the latest images for 3.1 are not available yet (if ever) and when I originally tried to flash the 3.01 img files that is where I ran I to LNX 0x0004.
What could have went wrong? Bad download? Or Is it a no no to flash the 3.01 files over the 3.1 OTA update?
Click to expand...
Click to collapse
Try the following instructions:
http://forum.xda-developers.com/showthread.php?t=1052644
Related
Dear friends,
I just rooted and installed the cw recovery in my newly bought ASUS TF. The current version is 8.4.4.11, 3.1. Then how can I update my machine to V8.6.5.9, 3.2 without wipe?
Thank you very much!
Depending on which rooting method you used, if you read the root thread, it will advise you to update to the latest firmware for your model before rooting. You won't be able to update to the latest firmware after rooting and installing cwm recovery because the update will fail. You will need to return back to full unrooted stock with no cwm recovery, then update to the latest firmware, then reroot. PM me for instructions on how to return to stock.
smslike123 said:
Dear friends,
I just rooted and installed the cw recovery in my newly bought ASUS TF. The current version is 8.4.4.11, 3.1. Then how can I update my machine to V8.6.5.9, 3.2 without wipe?
Thank you very much!
Click to expand...
Click to collapse
cavsoldier19d said:
Depending on which rooting method you used, if you read the root thread, it will advise you to update to the latest firmware for your model before rooting. You won't be able to update to the latest firmware after rooting and installing cwm recovery because the update will fail. You will need to return back to full unrooted stock with no cwm recovery, then update to the latest firmware, then reroot. PM me for instructions on how to return to stock.
Click to expand...
Click to collapse
I have seen this a few times, you do not have to return to stock to update your firmware. A couple of nice people have made the update compatible with CWM and you just have to put the zip on your SD card and install it from CWM. Here's the links to go to .9 and .13 Cheers.
http://forum.xda-developers.com/showthread.php?t=1234734
http://forum.xda-developers.com/showthread.php?t=1281161
After looking at what firmware you are at, I'm not sure if there are zip updates that go back that far, but you can certainly search to see...Cheers.
ckuke4 said:
I have seen this a few times, you do not have to return to stock to update your firmware. A couple of nice people have made the update compatible with CWM and you just have to put the zip on your SD card and install it from CWM. Here's the links to go to .9 and .13 Cheers.
http://forum.xda-developers.com/showthread.php?t=1234734
http://forum.xda-developers.com/showthread.php?t=1281161
After looking at what firmware you are at, I'm not sure if there are zip updates that go back that far, but you can certainly search to see...Cheers.
Click to expand...
Click to collapse
But mine is 8.4.4.11, 3.1 rather than 8.6.5.9, 3.2....
Install a new custom rom
I need to go in the opposite direction many guides explaining how to downgrade the firmware to attain root. Got my tablet back from RMA with Jb .16 on it and downgraded, rooted, installed rootkeeper, flash, etc with no problems. Now I can't get back to JB. Everything I'm trying is erasing the root. I'm using stock firmware and still locked device. Should I be waiting for the device to get OTA updates back to JB? Every time I check it says no update. Are there simplified versions of the upgrade firmware that won'tt do clean installs and erase everything?
This is basically what I've been doing
-downgrade to firmware and use debugfsroot with no problems
-install rootkeeper, do a back up of root
-transfer any version of stock JB to the memory card (I've tried it with renaming the file or leaving it and letting the OS detect the upgrade)
-go back into rootkeep or SU and root is gone
There a step I'm missing? I've been at this for 5hrs now and have no problem feeling sheepish if there is a setting somewhere I need to check on.
fsured said:
I need to go in the opposite direction many guides explaining how to downgrade the firmware to attain root. Got my tablet back from RMA with Jb .16 on it and downgraded, rooted, installed rootkeeper, flash, etc with no problems. Now I can't get back to JB. Everything I'm trying is erasing the root. I'm using stock firmware and still locked device. Should I be waiting for the device to get OTA updates back to JB? Every time I check it says no update. Are there simplified versions of the upgrade firmware that won'tt do clean installs and erase everything?
This is basically what I've been doing
-downgrade to firmware and use debugfsroot with no problems
-install rootkeeper, do a back up of root
-transfer any version of stock JB to the memory card (I've tried it with renaming the file or leaving it and letting the OS detect the upgrade)
-go back into rootkeep or SU and root is gone
There a step I'm missing? I've been at this for 5hrs now and have no problem feeling sheepish if there is a setting somewhere I need to check on.
Click to expand...
Click to collapse
I suspected you do a full firmware upgrade which will wipe out your root (the one you download from Asus site is full firmware version), doesn't matter if you have OTA root keeper. You need to follow the incremental upgrade using dlpkgfile method can be found here: http://forum.xda-developers.com/showthread.php?t=1803090
Wow that was fast. Thank you. I think I've hit my point for the night in trying to get it to work. I've booked marked the page and will give this a shot tomorrow.
I am selling my 300T and I have downloaded the latest JB .20 ROM from Asus. I am currently on JB .18. I want to return everything to stock before I sell it. I am currently rooted with an unlocked bootloader and have deleted some stock apps. I have TWRP recovery currently installed. Will flashing via Fastboot be the best method? Will this flash the recovery as well? I saw another thread saying that flashing the blob file via fastboot restored the tablet to stock completely, but there was a discrepancy on the command to use. Thanks for the help.
Refer to the link below, it's a thread I just posted in concering the same issue
http://forum.xda-developers.com/showthread.php?t=2136796
Hi guys,
I have a rooted xt925, and I'm having some problems to take the update. I've read that rooted phones can't update OTA, so I have removed the root, but I still can't update the phone. I've tried to do it via motorola device manager too, but it says that there's no updates to my phone. I've already searched how to solve this, but I'm very noob
Any suggestions?
Thanks
easiest way is to do a factory reset, keep in mind that will erase all your data then try update . You can also flash the OTA but that involves few more steps. Check
http://forum.xda-developers.com/showthread.php?t=2760840
Because you rooted, that modified the system partition. Removing root might work, but your best bet is to flash an SBF if one exists for the XT925. I don't have an XT925 (I have an XT926), so I have no idea if SBFs exist for XT925.
And before you ask, no. You cannot use and XT926 SBF to flash back to stock.
Oh, I did factory reset two or three times, and ota update continues to fail.
I will try to search more about SBF. And it's possible to flash a kitkat rom without have a kitkat bootloader?
For xt925,you flash European cee 4.1.2 jb, then take the update or flash it itself.
Hi there !
I have U11 2.31.400 version
-Bootloader Unlocked
-TWRP installed
- Root with Masgik
Now i want get OTA update
-First, NO RUU, i tried Restore NANDoid backup and Flash stock recovery (same version)
(https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=1564536856)
-> Not work
-I tried flash stock Firmware ( got 35_RU_Partition_not_support firmware error)
Anyone can tell me how to got OTA with out RUU??
Hi there
I think we're in the same situation.
I also unlocked my phone, installed TWRP and Magisk on stock system and did a NANDroid Backup before doing so.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
Thanks
Edit: Hi, in case you're still having this problem, here's a solution:
Reverting to stock