Database Develop

[INFO] Nexus 5 OTA Help-Desk

..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OTA Help-Desk
*5.1.1 LMY48B Available*
*5.1 LMY47I Available*​
*5.1 LMY47D Available*
This thread is only for OTA help and nothing else!
Flash stock recovery before proceeding
​.​
NOTE: If You are a rooted non-stock user I suggest you look at @rootSU's thread before proceeding as his method for rooted users is far less prone to cause issues.
http://forum.xda-developers.com/google-nexus-5/general/info-rooted-user-learn-to-update-t2927876
First, let's talk about what an OTA is:
An OTA (Over the Air) update is the method of updating your phone's software. When the OTA is downloaded to your phone it will prompt you to reboot and install. It is not a complete image, but a series of patches to the OS. Patches in the OTA can include: bootloader, radio, system, recovery and kernel. While it's installing, the script checks the files it is patching to make sure the original files are correct. If everything is correct, the update will finish successfully. If it's not, the process will stop. That's why it is critical to make sure everything is in its "out of the box" state. Don't worry though. It is easy to get your phone back to a state where you will have it up and running, with the latest software.
We are also able to manually flash this file. When the URL of the OTA is discovered, you can download it and use adb or a custom recovery to apply it.
Now that you have read the important info above, Let's update your Nexus 5!
In order for the OTA to apply successfully without intervention; you must be completely stock
From 4.4.4 KTU84P
Current Bootloader: HHZ11k
Current Radio M8974A-2.0.50.1.16
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
From 4.4.3 KTU84M
Current Bootloader: HHZ11k
Current Radio:M8974A-2.0.50.1.13
Stock Kernel: 3.4.0-gd59db4e
All /system apps present
No modifications to existing /system files of ANY kind.
Note: Literally any modification will break the OTA. Xposed, DPI, build.prop, volume mod, etc. ANYTHING!
Seriously, I'm not joking guys.
If you meet the above criteria, the OTA will complete successfully.
If you don’t meet the criteria or don’t want to wait for the OTA to hit your device then see below.
Current OTA's
5.1.1 LMY48B from LMY47D: https://dl.dropboxusercontent.com/u/33560221/OTA_update_from_lmy47d_to_lmy48b.zip
5.1 LMY47I from 5.0.1 LRX22C: http://android.clients.google.com/packages/ota/google_hammerhead/90bd789f499ea5ad33510c568ec920aae7214d34.signed-hammerhead-ota-LMY47I-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0.1 LRX22C: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX22C-radio-restricted.zip
5.1 LMY47D from 5.0 LRX21O: http://android.clients.google.com/p...d-ota-LMY47D-from-LRX21O-radio-restricted.zip
Legacy OTA's
5.0.1 LRX22C from 5.0 LRX210: http://goo.gl/eoV0GE
5.0.1 LRX22C-from-KTU84: http://android.clients.google.com/packages/ota/google_hammerhead/6dadaf477bab65f42f5681b03bd535f431594b95.signed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip
5.0 LRX21O-from-4.4.4 r2 KTU84Q: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84Q.67fdc56d.zip
Thanks @pppp6071
5.0 LRX21O-from-4.4.4 KTU84P: http://android.clients.google.com/p...ed-hammerhead-LRX21O-from-KTU84P.c1a33561.zip
Thanks @saberdragon18
4.4.4-KTU84P-from-4.4.3-KTU84M:[/COLOR][/B] http://android.clients.google.com/p...ed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip Thanks @sucro
http://forum.xda-developers.com/showpost.php?p=46289250&postcount=1 Thanks @oldblue910
These are the most common scenarios. If you aren't sure where you fit, feel free to ask.
NOTE: Starting with Android 5.0 (LRX21O) you MUST sideload the OTA in a STOCK RECOVERY. No exceptions.
Scenario #1
You are completely stock. Unlocked/locked bootloader. No root permissions.
Continue to Section A
Scenario #2
You are stock, with root. Custom Recovery without any modifications or deletions.
Continue to Section B
Scenario #3
You are stock, with Xposed Framework installed.
Continue to Section C
Scenario #4
You are stock, with a custom kernel and/or old radio and no other modifications.
Continue to Section D,1
Scenario #5
You are stock with any modifications to /system/ including removed system apk(s) and a custom kernel.
Continue to Section D,2 or See 2nd Post (Special Scenario #1) **Special Scenario #1 is not updated yet**
Scenario #6
You are running a Custom ROM
Continue to Section D,3
Section A: adb sideload
NOTE:Make sure you have the latest version of adb. It seems people are having issues with older versions. It's attached at the bottom of this. Also Starting with Android 5.0 you must sideload the OTA through a stock recovery. Custom recoveries for now will error out.
1) Download the OTA.zip on your PC, rename the file update.zip, then place file in the same directory as adb.
2) Make sure you have USB Debugging checking in the Developer Options, then connect your phone.
3) Open the command prompt from the directory above on your PC and type the command: 'adb reboot recovery'
4) When in recovery, you’ll see an android laying down. Press and hold POWER, and then press volume up and release. The menu will appear. Select “apply update from adb
5) Using the command prompt type: 'adb sideload update.zip' The file will load and the update will begin.
6) When completed, select reboot.
Section B: Flashing in a Custom Recovery (TWRP- CWM)
(For Flashing 4.4.4 OTAs and Below ONLY!)
1) Download the OTA.zip and copy to your phone.
2) Boot into recovery.
3) Flash the OTA just like you would a ROM.
4) Reboot.
Section C: Uninstalling Xposed Framework
Use the Xposed Framework Installer to remove the framework before applying the OTA.
Go into Xposed Framework, Framework-> Uninstall (it will restore the original file "app_process") then reboot.
NOTE: If you just uninstall Xposed Framework (the app itself), even after a reboot the "app_process" file (in /system/bin) is still the modified one by Xposed Framework, the original file is not restored.
Xposed Installer and info can be found here.
Once Xposed is uninstalled; jump back up to Section A on stock recovery (5.0 and above) and Section B on custom recovery (4.4.4 and below).
Thanks @Hammer_Of_The_Gods & @C3C076
Section D: Let’s get back to stock
1) Flash the stock boot.img and/or radio.img (whatever is applicable) from the factory image using fastboot. Also flash recovery.img if updating to 5.0
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash radio radio-hammerhead-M8974A-1.0.25.0.23.img
fastboot flash recovery recovery.img
NOTE: Some custom kernels will modify files in /system/ If this is the case you will see a status 7 error and the file modified. The easiest way to fix this is to flash the system.img
2) Replace the stock kernel or .apk(s) you removed or modified.
If you don't have a backup of removed or modified apk(s) flash the system.img
Note: These must be the exact versions that shipped with the rom.
Fastboot commands used in this section would be:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
3) Flash the KOT49H stock image. Follow abaaaabbbb63's guide if you need help.
--------------------------------------------------------------------------------------------------------------------
After completing the steps needed to return to “stock” make sure you meet all the criteria at the top of the page then revert to:
Section A if you are running stock recovery.
Section B if you are running a custom recovery (for 4.4.4 OTAs and below only).
Feel free to ask any questions you may have. I’ll do my best to answer them as quickly as possible. Perhaps others may answer them as well. Please read to see if your question has been answered before asking.
FAQ
Q: When in Recovery/Bootloader the phone isn't listed in Windows Device Manager.
A: Uninstall all current N5 drivers and install the Universal Naked driver. Turn on USB Debugging in Developer Settings and boot to recovery
Q: I'm seeing a status 7 error when trying to install the OTA
A: Look at the error closely. It will describe on the file it is failing at. Post the file path so we can help resolve the issue.
Q: The ota applied successfully but I lost my custom recovery and I want to re-root. How do I get root back?
A: Flash the custom recovery of your choice in fastboot and use it to regain root permissions
Q: I've tried everything, but I'm still getting status 7 errors.
A: Unfortunately you may have to start from scratch. Follow Section C1.
Q: I flashed a .zip file that modified (insert mod here.) Will I the OTA install successfully?
A: No, any modification at all will cause the OTA to fail.
Q: Why do I get a "cannot read update.zip" error when trying to sideload?
A: If you named the file update.zip, the actual name would be update.zip.zip. Windows auto names extensions by default. That could be your problem. If not try another usb cable or a different usb port. If that still doesn't work, make sure you type exactly what you renamed the file. You may have made a typo. It is also case-sensitive.
UPDATED: 6/19/14 - Updated for KTU84P

..
Special Scenario #1
If you are running the stock ROM, rooted, with a custom kernel, and you want to retain root after the OTA; follow this great detailed walkthrough by @Lettuce!
If it helps you, make sure you thank him on the original post, located here:
http://forum.xda-developers.com/showpost.php?p=48212456&postcount=2681) downloaded factory image from https://developers.google.com/android/nexus/images#hammerhead
2) extract the tgz, the tar within that, then extract the the zip within that to get the system.img and boot.img files
3) moved these two files into the adb folder (for the fastboot/adb method)
4) download Latest SuperSU from http://download.chainfire.eu/supersu
5) put SuperSU.zip on your phone's internal storage
6) download the 4.4.1 OTA update zip from http://android.clients.google.com/p...ed-hammerhead-KOT49E-from-KRT16M.7ed504f6.zip
7) rename it to ota.zip
8) move ota.zip onto your phone's internal storage
9) boot into bootloader
10) open command prompt from your adb folder
11) connect USB cable
12) type 'fastboot devices' to check the connection
13) type 'fastboot flash system system.img'
14) type 'fastboot flash boot boot.img'
15) use volume and power buttons to boot into recovery (TWRP)
16) install ota.zip
17) install latest SuperSu.zip
18) clear dalvik and cache
19) reboot phone​UPDATED: 1/25/15

Good job :thumbup:Nice to see you here
Sent from my NEXUS 5

Scenario #2: Will I receive a message ?
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).

If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.

david31262 said:
Thanks for this thread. It's just what I've been trying to figure out.
So, if I'm Scenario #2, will I received a message on the phone when the OTA is available? Can I let it download then install through TWRP ?
If I'm reading correctly, the custom recovery will not let it install automatically (and maybe I don't want it to since it could wipe out TWRP). On reboot will TWRP prompt me to root the phone (that's how I got to root the first time).
Click to expand...
Click to collapse
I believe the new versions of recovery will ask to keep the custom recovery and/or root. We'll see how the custom recoveries handle the OTA on the N5 and I'll update the post accordingly.
BirchBarlow said:
If you're rooted, but with stock ROM, do you know for sure OTA updates won't go through? Thanks.
Click to expand...
Click to collapse
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel.
Sent from my Nexus 5 using Tapatalk

What about cf auto root? From the description it looks like that only adds the root apps and nothing else.

El Daddy said:
It all depends on how you gained root access. If you used cf-super boot it will not go through because it modifies the kernel. Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.

Evo_Shift said:
What about cf auto root? From the description it looks like that only adds the root apps and nothing else.
Click to expand...
Click to collapse
BirchBarlow said:
WHen you say cf-super boot you mean installing SuperSU through TWRP right? Thanks.
Click to expand...
Click to collapse
Cf-auto root and super su should be fine as they don't modify the kernel.
Sent from my Nexus 5 using Tapatalk

Nice!!
Every time someone mentions me, I regret choosing this username.

abaaaabbbb63 said:
Nice!!
Every time someone mentions me, I regret choosing this username.
Click to expand...
Click to collapse
Yeah, I regretted mentioning you.
Thank you copy & paste.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.

maxal said:
Hi I would just like to confirm if the Nexus 5 is like my old HTC One in that I would receive OTA updates on a stock rom and stock recovery with a unlocked bootloader.
Click to expand...
Click to collapse
As long as everything is stock an unlocked bootloader does not effect an OTA.
Sent from my Nexus 5 using XDA Premium 4 mobile app

El Daddy said:
Nexus 5 OTA Help-Desk​
Scenario #3
You are stock, with custom kernel, any modifications or removed system apk(s)
Continue to Section C
Scenario #4
You are running a Custom ROM
Continue to Section C
Section C: Let’s get back to stock
You have two options to do this:
Option #1 Flash the KRT16M stock image. Follow @abaaaabbbb63 guide if you need help.
If you want to keep data intact flash only the boot.img, system.img, and recovery.img (optional)
OR
Option #2 Replace the stock images or .apk(s) you removed or modified.
Note: These must be the exact versions that shipped with the rom.
Click to expand...
Click to collapse
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.

Synyster06Gates said:
Just to be sure, flashing only boot.img and system.img will keep my apps and all user data, correct? I can live without the center clock mod and battery % for now.
Click to expand...
Click to collapse
That is correct.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
That is correct.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did it... everything booted correctly, my apps and settings were still there, but for what ever reason - my APN settings will not stay. I save it, and it takes me back to an empty menu. Any ideas?

Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Try pressing the menu button in apn's and reset to default.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Tried that. Says it's done, nothing comes up.
I tried searching for network as well but that didn't work either. The wifi works, but no network.
I restored a backup I made last night and it still isn't working. Any ideas?
Tried to do a system wipe then restore again
E: Unable to mount '/cache'

Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Hmmmm. I've never heard of that issue before. I'm not sure what else to try.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed it. I went ahead and flashed the stock cache.img as well and all is working. Some how I guess the cache corrupted or deleted.

[Q] How to upgrade bootloader to 10.26.1.18 ?

Hi,
I bought today a 701T ww, with bootloader version 10.26.1.7.
I've been able to unlock the bootloader, root the rom, and install a custom CWM (now 6.0.4.6).
I installed the custom rom CROMi-X 6.0b2
But I'm now unable to upgrade the bootloader to 10.26.1.18.
I reverted to stock 10.27.1.7 rom thanks to the nandroid backup I made prior CROM install, I've tried downloading the official update package from Asus, which is supposed to be the only way to upgrade the bootloader. I've put the UL-K00C-WW-10.26.1.18-user.zip file on the root of a MicroSD, the tablet recognized the update file, and rebooted to install it. Problem is that, after reboot, the tablet enters in the CWM with the following error :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Off course if I try "Yes - install untrusted.zip" it doesn't rework, and the tablet reboots ....
many thanks if you can help !

Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]

berndblb said:
Turn off "signature verification" in CWM and try again
BTW: How did you miss this??????
TF701T USERS: YOU MUST BE UNLOCKED, ON THE ASUS STOCK JB 4.3 BOOTLOADER VERSION 10.26.1.18 AND HAVE A WORKING RECOVERY - CWM 6.0.4.6+ BEFORE FLASHING THIS ROM. SEE UPGRADE INSTRUCTIONS BELOW IF YOU ARE UNSURE[/SIZE]
Click to expand...
Click to collapse
Hi Berndblb, thanks for your reply.
Toggling the signature verification didn't help, I've already tried that.
I didn't miss this, but as I've never been able to upgrade the bootloader thanks to the official update, I thought that with CROMI the bootloader would be upgraded too. I noticed that was'nt the case, that's why I restored my nandroid backup to revert to the stock 10.26.1.7.
Now I'm in 10.26.1.7, and precisely want to upgrade the bootloader to be able to install CROMI with the correct bootloader. Therefore my question.
Would a "fastboot flash boot boot.img" using the boot.img file included in the official asus 10.28.1.18 package be a good idea ?

Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:

usoska said:
Okay, I finally solved it ... Here's what I did :
I downloaded the stock recovery from this url : http://droidbasement.com/db-blog/?p=3210
I booted on this recovery (fastboot boot recovery.img), and the upgrade could be completed.
I'm now under stock 10.26.1.18, with corresponding bootloader :good:
Click to expand...
Click to collapse
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?

Calp said:
Hey man! Thanks for the explanation. I seem to have a similar problem as you had and tried to use your steps to fix it.
However, when I boot into the stock recovery the green android figure appears and falls on the back (with exclamation mark) after about 2 seconds... Is there something else to take care of, any ideas what I might have missed?
Click to expand...
Click to collapse
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go

berndblb said:
That is great news! The Android on his back is the stock recovery not finding a valid update file.
Download the .18 firmware again (remember - you edited the update script) and you should be good to go
Click to expand...
Click to collapse
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!

Calp said:
Wow! I hope you're right.
Will I need the original WW_epaduser_10_26_1_18_UpdateLauncher.zip or the once unzipped UL-K00C-WW-10.26.1.18-user.zip - and what about the WW_10_26_1_18_SDupdate.zip? Where do I have to place them, on internal storage or fat32 formatted microsd card? Thanks in advance!
Click to expand...
Click to collapse
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.

berndblb said:
Copy the xxx.18-user.zip to the root of your internal, meaning not into any folder, just into /sdcard.
A notification to upgrade should pop up. If not, reboot.
The SDupdate.zip is only available for the WW version and I suspect Asus provided it because a few weeks back they pushed a bad update to WW users, causing their tablets to hang in boot. I suspect it's specifically meant to be used to update from the microSD in your recovery (if you cannot boot system), but that's just a guess.
So if method one doesn't work, copy the SDupdate file to a microSD, boot into stock recovery and it should recognize the file and flash it.
Click to expand...
Click to collapse
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!

Calp said:
THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
You're very welcome !
That looks correct.

Calp said:
It did indeed start installing the update just as you said it but after 30 % or so an error errupted and the android guy fell over again. I booted the tablet and received "error no 12 - the update package is not compatible with your current software. please check your software version and number in the settings and use the right update package."
I did use the UL-K00C-WW-10.26.1.18-user.zip which is for WW SKU, and the build number in the settings says:
JSS15J.WW-epad-10.26.1.7-20131108
The method with SDUpdate file doesn't work either. It doesn't recognize it in the bootloader (as explained in the official info document from asus) and when I boot into recovery manually the installation fails after a second or so.
I'm really sorry for bothering that much, but do you know what's my fault?
Update: I just kept on trying and with the fourth try it did work! It did update to .v18, now the build number in settings AND the bootloader confirms it. THANK YOU SO MUCH, everyone @ berndblb, usoska, super0dd, Sleepy2 and sbdags! I'm in your all's debt.
So I will now flash
- this recovery : http://droidbasement.com/db-blog/?p=3223
Once this is done,
- I finally flash the CROMi-X ROM with the just installed CWM 6.0.4.6
Is that correct or did I miss anything?
I am so thankful, guys!
Click to expand...
Click to collapse
WooHoo! excelent. Glad you got everything all sorted out.

Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
2 days, how dare you. You should be concentrating on b4 and only b4.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

sbdags said:
Guys I've tried for 2 days to make a flashable zip to flash the latest bootloader and recovery but the tools asus provided only appear to work with the stock recovery. CWM currently does not support this method and I'm giving up at the risk of bricking.
So the method for now is the one posted above:
Fastboot flash the asus stock recovery.img and then update to the latest firmware then fastboot flash the latest CWM.
Click to expand...
Click to collapse
Wow, you're crazy! I really appreciate your help, mate.
For anyone else needing to do these stips, here's the download link for the stock recovery which you have to flash first: http://droidbasement.com/db-blog/?p=3210 ( i also tried a different one but only this one did work in the end)
Also, thanks a lot for the ROM, sdbags. I've been using it for a couple of hours now and it seems to work like a charm. Great work, mate!
Sent from my K00C using xda app-developers app

How can I tell which bootloader (BL) and firmware (FW) I run currently? When I hold power/volume down, the top of the screen says user BL released by "US_epad-10.26.1.7". When I boot into Android and go into settings -> about -> software, I see Build number "JSS15J.US_epad-10.26.1.18". Is the 1.18 the firmware (FW) version?
Finally, is there a way to upgrade BL/FW to ...1.18 version without using an external SD card?

US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card

Thanks. Just to verify, you don't think doing "fastboot flash boot boot.img" will work? (using boot.img from UL-K00C-US-10.26.1.18-user.zip).
Also, by SD-card method, are you talking about the rename “WW_10_26_1_18_SDupdate” to “T4_SDUPDATE.zip" process etc.? It seems that I have the US SKU, and not sure if this would work, being that it mentions WW in the file name.
Sleeepy2 said:
US_epad-10.26.1.7 is your BL version
JSS15J.US_epad-10.26.1.18 is your OS version.
Currently the only way to updated the BL is from the SD card
Click to expand...
Click to collapse

I am no expert but I am pretty sure that the fastboot method doesn't work as there have been several people with the wrong bootloader issue and and the only way to do it was with the official update.
I am not sure about using the WW file or not. I am in canada and I used the other file to update and that did the bootloader also. With the status your in now I am not sure if the US one will work or not. I would try the US one first and then if not go with the steps from pershoot
http://forum.xda-developers.com/showpost.php?p=52187532&postcount=87

Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.

MilesWilford said:
Can someone please rehost the stock recovery.img file? The link's dead and I need it to get myself fixed up.
Click to expand...
Click to collapse
It's still there, try this link
http://droidbasement.com/asus/tf701t/stock/

NEM-L51 (Android 7.0/EMUI 5.0) OTA update fails

Hi,
I have a rooted NEM-L51 (with TWRP 3.1.1-0 as recovery) running Android 7.0/EMUI 5.0 (build number NEM-L51C432B350).
A new OTA update is available (build number NEM-L51C432B355) but after downloading and rebooting to recovery (TWRP) to apply it, it fails with the following error:
Code:
script aborted: assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
assert failed: block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")
Updater process ended with ERROR: 7
I googled it but couldn't find anything that seems useful. You'll find attached the complete log (I was using TWRP 3.1.0-2 at the time and has since upgraded, thinking it could be related to it).
Does anyone have any idea about what's going wrong here?
Could it be because the system partition has been modified in the process of rooting the phone (I'm thinking about that because of the 'block_image_verifiy(.../system...)') — note that I was able to apply OTA updates on my rooted device in the past?
Thanks!

You have magisk or SuperSU?!

why you trying to install updates on twrp....

Try useing stock recovery from the update.

PalakMi said:
You have magisk or SuperSU?!
Click to expand...
Click to collapse
SuperSU, v2.82.
thelous said:
why you trying to install updates on twrp....
Click to expand...
Click to collapse
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
AlexMihai26 said:
Try useing stock recovery from the update.
Click to expand...
Click to collapse
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?

Try magisk!

In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?

fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash. (someone please confirm if it is zip or update.app). Are you using the openkirin twrp?
Click to expand...
Click to collapse
Update.app with stock recovery, zip with twrp

sclarckone said:
SuperSU, v2.82.
It reboots automatically under TWRP after downloading the update. If I choose to apply the update later, I can force it to boot to Huwaei eRecovery but I'm not sure I can apply the update from here without wiping my /data ?
As far as I remember it didn't reboot to TWRP for the previous OTA updates but since it seems to be executing a script for the update what difference does it make if it's executed from TWRP?
I'm not sure about what you mean: do you suggest I try to extract the Honor recovery from the update files and flash it using fastboot?
Click to expand...
Click to collapse
Yep

PalakMi said:
Try magisk!
Click to expand...
Click to collapse
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
fishnchips2 said:
In order to do a normal ota update you need the stock recovery. To update with twrp you need to have the zip file to flash.
Click to expand...
Click to collapse
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_data_public.zip (around 13 MB) which seems to contain updates for Honor system apps.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
fishnchips2 said:
Are you using the openkirin twrp?
Click to expand...
Click to collapse
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^

I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Twrp and root were lost during the update because the rom replaces them with its own files in the first boot. I don't know why the ota updates worked before.

Because you can hide root with magisk.

fishnchips2 said:
I haven't flashed an update with TWRP myself but I think the first file is the critical one and the others are regional patches and app packages. I think you should flash them in the order: Update.zip, update_nem-l51_hw_eu.zip then update_data_public.zip. However I should stress that I haven't done it myself.
Click to expand...
Click to collapse
Just to be clear, these files I mentioned in my previous post are the one downloaded by the OTA updater of EMUI (and TWRP fails on flashing the first one, update.zip) so I shouldn't flash them with TWRP, right?
I'm a bit confused about this because if ZIP files are supposed to be used with TWRP and the APP files with the stock recovery, why did the EMUI OTA updater download ZIP files (I would expect it to download files as if I had a stock recovery)?
fishnchips2 said:
As for the files you're looking for, https://forum.xda-developers.com/honor-5c/development/repository-honor-5c-file-depot-t3640712 should contain most of the necessary files but oddly doesn't have a stock Nougat recovery...
Click to expand...
Click to collapse
So these are the files flashable with TWRP (in that case I don't need the stock recovery)? The ones corresponding to the upgrade I'm looking for seem to be the following:
The OTA one seems to be exactly the same update.zip that was downloaded by the EMUI OTA updater. Should I try the FullOTA variant?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry if I sound a bit meticulous but I'd rather not brick my phone and understand what I'm doing. ^^

The error you're getting is error 7 which means the rom is supposedly incompatible with your device. As this is the official update, I have no idea why this error is coming up. I think that once you get past that error, twrp should be fine flashing the zip file.
The difference between ota files and fullota files is that a fullota contains most of the files needed by the rom while the ota only replaces files that have changed. As you are on b350 nougat already, an update to b355 should only need a normal ota update.
Don't worry about asking questions, it's good that you're cautious with your phone.?
---------- Post added at 09:52 PM ---------- Previous post was at 09:45 PM ----------
EDIT!!!
Sorry I was wrong in the previous reply. Twrp can't flash an ota update because it only replaces some files, whereas twrp will flash the entire system. However, a fullota file should work (haven't tried??).
This also explains why it had error 7: the manufacturer doesn't want someone accidentally flashing an incremental update as a full rom.
More info is here : https://twrp.me/faq/officialota.html
---------- Post added at 10:01 PM ---------- Previous post was at 09:52 PM ----------
Further edit : I believe that you have to wipe certain partitions (system and cache?) before flashing an update because 'dirty flashing' doesn't always fully replace everything and causes issues later. However this may be different for stock roms. Nevertheless, always make a backup!
Hopefully final edit: a dirty flash means that you don't wipe data first. This should be fine for an official update. Opinions vary on wiping system, cache and dalvik but I think the recovery should do that for you.

Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.

PalakMi said:
Yes, as you said TWRP flashes the entire system, that's you need fullOTA,?.
Click to expand...
Click to collapse
Yup I believe so

Honor devices are one of the most complicated when it comes to flashing ROMs.

I know ? at least it isn't the s8 exynos version. I hear you can't even unlock the bootloader on that.

Yeah, however, I wish honor makes it simple with upcoming devices (like OnePlus)

sclarckone said:
I'm OK to switch to Magisk if necessary but why would it solves my error during update? Is it because Magisk doesn't touch the /system partition (I don't even know if SuperSU did)?
Besides, this thread says I must restore my stock boot image and I don't have it.
OK. What's "strange" about this is that I was able to apply the last two OTA updates even though I did have a custom recovery at the time -- and I had to flash TWRP and root again after each of these updates.
Anyway, I got the updates files (by looking for the files mentioned in the TWRP log) and they already are zip files (the error I get occurs while executing the first) :
update.zip (around 180MB), which contains among other files the UPDATE.APP file.
update_NEM-L51_hw_eu.zip (around 16MB), which might be a firmware update given the name?
Are these the files I'm supposed to flash with TWRP?
Yes.
@AlexMihai26: I've looked into the zip files mentioned above and didn't spot any file that should be the stock recovery. Do you have any idea where it should be located?
And thank you all for your help, of course! ^^
Click to expand...
Click to collapse
Use Huawei update extractor,and you should find a recovery.img

Q: Howto get my X4 to a working LOS setup after having bricked it and used blankflash

Hello,
I few weeks ago I got myself a Moto X4 XT1900-7 after my old mobile suffered a broken display.
I unloaded the boot loader and proceeded to install LOS right after getting the phone and getting it unwrapped from its shipping box.
This is now my 4th mobile were I installed LOS or Cyanogenmod and out of hubris I did not create a backup before the install.
I followed the instructions on the LOS website for installing and ended up with a bricked X4 (https://wiki.lineageos.org/devices/payton/install).
Now after xmas I investigated further and was able to use the blank flash as provided here (https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529/page6) to get to the state were the mobile is at a fastboot screen after the blank flash.
https://imagebin.ca/v/4RUBbOmjIGs9
At this point I can fastboot boot twrp (https://dl.twrp.me/payton/)
fastboot boot twrp-3.2.3-1-payton.img
to get into a twrp recovery.
But installing a LOS install package (https://download.lineageos.org/payton) and rebooting only gets me back to the state of the bricked phone, so I must be missing something.
So my question is how do I proceed to get the phone back to a working state ? The LOS install instructions to not work at this point - I tried and after installing LOS I just get back to the state were the mobile is bricked and I have to use blank flash again.
My end goal would be a working LOS installation.
Thanks
BR

Hey let's compare build numbers and kernel info, Android version etc. Maybe ours differ from others on here. Since I had a similar experience as you in that flashing a ROM bricked my phone, maybe we'll find a commonality that others here don't have...
I could not get blankflash to work for me. The phone showed in device manager the way the instructions said it should with the port number. I downloaded stock rom unzipped it to my address folder and unzipped the blankflash package to the same folder. I would run the .bat file but it errored out everytime. Luckily I was able to bring the phone back and Fry's just accepted it and gave me another one .
I don't want to end up with another bricked phone. Out of curiousity was yours freezing up after rooting, but before the rom installation.?
---------- Post added at 02:52 AM ---------- Previous post was at 02:36 AM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you try following the guide in the ROM thread (https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265)?
I bricked my device on the first attempt while following the LOS site install instructions, but after getting it back to stock I followed the ROM thread instructions instead (with a minor adjustment).
First things first, if you haven't gotten back to working bootable image on your device, boot to the bootloader and follow this thread's instructions. I am not 100% sure this is necessary, but I don't have another device to test with atm. One thing to note, make sure to get your variant's stock 8/8.1 Firmware. I have an XT1900-1 variant while that thread features links for the XT1900-6 variant.
Next follow these instructions:
erfanoabdi said:
How to install:
Boot the newest TWRP .img from the Official TWRP Project Site.
IF YOU ARE COMING FROM STOCK AND WANT TO INSTALL CUSTOM ROMS FOR FIRST TIME, INSTALL "Copy Partitions Zip" FROM POST #2
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need to be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Click to expand...
Click to collapse
Following those instructions should get you a working LOS install. Make sure to get the correct Copy Partitions Zip for your variant.
All that said, I diverged a bit at the start and end:
Before starting TWRP, I ran the Copy Partitions Zip flash_all.bat/sh at the bootloader.
Before letting the system start, I ran the flash_all.bat/sh at the bootloader again.
For the first change, I couldn't get TWRP to run the ZIP, so I extracted it and realized the bat/sh scripts were fastboot flashing the contents of the ZIP. The second deviation is because my system wouldn't make it past the boot logo screen and when I loaded TWRP, it was giving errors about firmware issues in the terminal.
After performing all that, your LOS should boot and be configurable. Your experience may be different to the difference in variant.

Ty for the pointer to the ROM thread, I am reading through that.
How do the different variants of the X4, i.e. XT1900-1 through XT1900-7 (that is the one I do own), differ ? And connected to that question - can I flash a stock image from a different variant (maybe a XT1900-1) than my XT1900-7 to my XT1900-7 without causing further problems ?
Also what is the purpose of Copy Partitions Zip ? What does it do ? I downloaded the zip file and I understand that I shall install it via adb sideload or from the sd card when I have booted the twrp recovery from fastboot. Do I need to modify anything in copy partitions zip specifically to match my XT1900-7 ? Or does Copy Partitions Zip work the same on all variants of the moto X4 ?
Ty
BR

I'll be honest, a more experienced member would have to answer that because I don't really know how they differ. You can try to push a XT1900-1 to -7, but I wouldn't recommend that. I have two versions of this device, an A1 and Retail. The A1 version is generally Fi related and I accidentally loaded the firmware for the Fi version on my Retail and now it is giving me issues with my carrier (I think this is the cause, but am not 100% sure).
From what is said by TadMSTR in the thread, the Copy Partitions Zip is for duplicating partitions between the two OS slots:
TadMSTR said:
The Moto X4 uses the A/B slot setup that Google introduced with the Pixel. However, Motorola decided to only setup the partitions in slot A. The copy partition zip copies the partitions from slot A into slot B. This allows you to now flash/install a ROM into slot B. Without flashing copy partitions zip I'm not sure you would even be able to change to slot B. You definitely would not be able to flash anything to it.
ROMs should include everything needed to boot into the OS. Lineage includes boot, system, and recovery. If you don't want to use Lineage recovery then you need to flash the TWRP zip after flashing Lineage, even after just flashing an update. So technically all you need is the Lineage zip to have a fully functioning Android OS. However, you will most likely also want gapps. You should be good following the tutorial in the beginning of this thread. For applying updates see my post above.
Click to expand...
Click to collapse
You won't be sideloading that zip. As I stated before, it's a bunch of fastboot commands in the a bat/sh file with support files included. You will be running while at the bootloader according to Skeeterdrums in the thread:
Skeeterdrums said:
See the previous post, you need to unzip and run the flash_all bat/sh file while connected to your phone in the bootloader. Those scripts run a series of fastboot commands to get everything copied over and installed.
Click to expand...
Click to collapse
You don't need to modify the zip, it should work on your variant according to posts in the thread.

erukami said:
I'll be honest, a more experienced member would have to answer that because I don't really know how they differ. You can try to push a XT1900-1 to -7, but I wouldn't recommend that. I have two versions of this device, an A1 and Retail. The A1 version is generally Fi related and I accidentally loaded the firmware for the Fi version on my Retail and now it is giving me issues with my carrier (I think this is the cause, but am not 100% sure).
From what is said by TadMSTR in the thread, the Copy Partitions Zip is for duplicating partitions between the two OS slots:
You won't be sideloading that zip. As I stated before, it's a bunch of fastboot commands in the a bat/sh file with support files included. You will be running while at the bootloader according to Skeeterdrums in the thread:
You don't need to modify the zip, it should work on your variant according to posts in the thread.
Click to expand...
Click to collapse
@erukami I have the Android One variant with the Fi firmware. Only had data when using my Verizon work sim. Flashing the US Retail firmware loaded the correct radios and I was able to get full service on Verizon. Custom roms typically do not include the radio files. Restore the US Retail firmware and you should be fine. Can flash any custom rom after that.
I may have misspoke a bit about the copy partitions firmware. It doesn't setup the partitions as they are already there. It merely copies what is on A to B and vice versa, depending on which slot you are currently on. Though I think when coming completely from stock the B slot is "empty" as Moto didn't bother with it. Not sure if you need to bother flashing the zip when restoring to stock but I did anyway. Fastboot was only flashing to slot A. Maybe that can be tweaked with the flash-all.bat file.
@Afongo You should restore the stock firmware for your variant and start over. Making sure to flash copy partitions zip in TWRP before flashing LOS. When I restored stock firmware I made sure slot A was the active slot. After the restore let the phone boot up into stock. Reboot to the bootloader then boot TWRP. Flash copy partitions zip. Flash Lineage and then flash TWRP zip. Reboot to recovery. Flash gapps and Magisk (if you want root). Factory reset or wipe data/cache as needed before booting into Lineage the first time.
You need to reboot back into recovery after flashing a ROM due to the A/B slot logic. Flashing a ROM automatically changes the active slot so in order to flash anything after the ROM, with the exception of TWRP, you need to reboot to recovery to continue. Due note that LOS overwrites TWRP recovery on a fresh install and any updates. You'll need to boot TWRP from the bootloader if you need to get back in TWRP or you can just use LOS recovery.

Ty all for the provided info. I understand more now than before.
I am still looking for a firmware for a XT1900-7, does anybody know the filename so that I can google for it ?
For example I downloaded a PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, but how do I know for which variant of the Moto X4 that file is ? What is the naming scheme ?
Ty
BR

Afongo said:
Ty all for the provided info. I understand more now than before.
I am still looking for a firmware for a XT1900-7, does anybody know the filename so that I can google for it ?
For example I downloaded a PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip, but how do I know for which variant of the Moto X4 that file is ? What is the naming scheme ?
Ty
BR
Click to expand...
Click to collapse
You have the correct and most recent Android 8.1 firmware for you device (PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip). This works for all regions. The firmware does not determine the region. The xt1900-7 is 'reteu'.

Look here for Pie ROM.

Root any BL UNLOCKED T-Mobile/Metro OnePlus Nord with Magisk and temp root

Disclaimer: NOT RESPONSIBLE FOR ANY BRICKED DEVICES
YOUR DEVICE MUST HAVE AN UNLOCKED BOOTLOADER FOR THIS TO WORK
My first tutorial, gonna keep this short and sweet
1. Go to settings > About Phone > check your version number (eg 10.5.9 for mine)
2. Go to this thread and download the global zip with the corresponding number https://forum.xda-developers.com/t/...ota-oxygenos-repo-of-oxygenos-builds.4253501/
3. Use payload dumper to extract the payload.bin file in the zip (you don't have to extract the whole thing, I killed mine when I got my boot.img file)
4. Install Magisk on your device and patch the just extracted boot.img
5. Copy patched boot.img to your computer
6. Reboot into bootloader, run this command and NOTHING ELSE
fastboot boot <location of patched boot.img>
7. Now your device should be booted into a rooted state and if your wifi or cellular doesn't work, have no fear. This is only temporary and we need root for the next few steps
8. Install Partitions Backup https://www.apkmirror.com/apk/wanam/partitions-backup/partitions-backup-2-3-0-release/
9. Use that to dump boot.img from both slots to your device
10. Use Magisk to patch both boot.img files just dumped from Partitions Backup
11. Copy all dumped and patched boot.img files to your computer
12. Reboot into bootloader and fastboot boot into your newly patched boot.img files
13. If everything works, reboot back into the bootloader and flash the working patched boot.img files to both slots
14. Profit and enjoy! Tested and working on 10.5.9 for my N100, not yet tested on Android 11, do so at your own risk!
Leave a thanks if this helped you, this is for folks like me who couldn't find a backup of their OS build on the internet and needed a temp way to root their carrier devices

I'm going to try this now. Thank you for the idea!

I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.

bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
Unfortunately, I can't even get into EDL mode. So this brick might be permanent. I'm asking for help from the community here: https://forum.xda-developers.com/t/nord-n100-edl-mode-dead-gone.4341305/

bouyakasha said:
I've tested this method on BE2012 / 11.0.1.BE82CB and unfortunately the global rom's boot.img bricks the device - it won't get past the T-Mobile loading screen.
I'm going to try to restore via MSM and try it with 10.5.8.BE82CB now.
Click to expand...
Click to collapse
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it

luridphantom said:
youre not supposed to flash the global rom boot.img but boot from it, thats why it relies on a temp root. and the versions have to be exactly the same or you'll brick the device
what version was your old device on? good luck unbricking it though, hope you get another shot at it
Click to expand...
Click to collapse
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB

bouyakasha said:
You're right about the flash, my mistake. Sigh.
Versions need to be exactly the same anytime you're rooting with a boot image.
This is version I was attempting to root: 11.0.1.BE82CB
Click to expand...
Click to collapse
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine

I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.

bouyakasha said:
I just tried this method with N200. 11.0.2.0 is the latest good rooted boot.img I have, but 11.0.3.0 is latest update and there's no MSM.
Anyway booting to 11.0.3.0 using the 11.0.2.0 rooted boot.img works great! Still, I tried this method and when I extract the BootA and BootB partitions and try to flash them with Magisk, Magisk tells me it's an unsupported file. This is true when I try it as tar.gz (that's how it comes from Partitions Backup) and if I rename it to *.img - either way I can't get Magisk to want to flash it. Any ideas?
In the meantime, using the 11.0.2.0 rooted boot image seems to work fine with 11.0.3.0. So, maybe I can just go with it?
Anyway this is an awesome guide and I learned a lot from it. HUGE THANK YOU.
Click to expand...
Click to collapse
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it

luridphantom said:
partitions backup compresses the dump so you cant just simply rename it. think theres an option to dump it uncompressed so you can pass it on to magisk. the other way is to untar it then pass it to magisk
i'd just experiment a bit more as long as you remember to use fastboot boot until you get the config you want then you can flash it
Click to expand...
Click to collapse
Oh, thank you! That makes sense. I will try to UN-Tar it

I used Zarchiver to unarchive the TAR into boot.img for both, and this all worked! Thanks so much. Awesome guide.

@onlycash You should try this!

luridphantom said:
yea if you had booted from a magisk rooted 11.0.1 global boot.img and followed the rest of the steps you wouldve been ok because as soon as you reboot you lose root and boot from your original boot partition again
the number 1 rule of rooting with fastboot is always boot from it and test it before flashing it. other users were warning about wifi/cell failures so i played it safe and am still fine
Click to expand...
Click to collapse
I tried several times and it's not working for me.
Everything appears to be fine till I try to "fastboot boot patched.img".
I'm trying to do this on an Metro N100 which is on 11.0.1BE82CF
I downloaded the global: 11.0.1: OnePlusN100Oxygen_14.O.21_GLO_0210_2107241056 MD5: a895312987628f21d0232d44575d0742
I extracted the payload and dumped the boot.img
I patched it in Magisk
I successfully "fastboot boot" that patched file but then it just hangs at the at the Metro boot screen.
I waited a minute or two but it didn't move past that screen, should I have waited longer?
In any event, I could hold down the power key and reboot into the unrooted stock 11.01 without issue.
Does anyone have an idea what I'm doing wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.

onlycash said:
I tried several times and it's not working for me.
Click to expand...
Click to collapse
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.

thomaskmaagaard said:
Dude your phone is an anomaly Another dude in the TWRP post has had some success on his BE2015
I'm baffled.
Click to expand...
Click to collapse
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.

onlycash said:
Interesting...
I went and read tabuRebel post and I'm not sure what he did. What I'm unsure about is if he flashed TWRP or just fastbooted it and I think he rooted 10.5, not 11.01 but that's not totally clear either. Did he ever get TWRP to flash a zip or did he use a prepatched boot.img? Lots of what he did and how it ended up are very unclear to me.
Even the posts in this thread are not always clear to me. Did they fastboot a global patched img that matched or didn't match their installed ROM?
For example did bouyakasha above used an 11.02 img to temp root his 11.03? Maybe I'm just misunderstanding what he posted.
The ambiguity in the posts can make being sure what others had success with a bit difficult to discern.
I really don't think my phone is different than any other. I think how others were successful is not as cut and dry as it may seem.
Maybe I need to update to 11.03 first.
.
Click to expand...
Click to collapse
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it

My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.

luridphantom said:
you might also want to disable dm-verity by flashing an empty vbmeta image which you can find in other threads on xda
if you can get twrp for android 11, it's better to boot that and patch your boot image than to flash it
Click to expand...
Click to collapse
I posted a good deal on the TWRP thread. I can fastboot the TWRP on my phone but I can't see any files only folder tree, even with my SD card I don't see any files either with TWRP.
I should add I'm running TWRP on a Metro N100 which is both SIM and bootloader unlocked. Also I didn't flash the TWRP I only fastbooted it, could that be the problem?
I really would rather flash the zip and root that way if I could get the TWRP to work.
I'm unsure what "disable dm-verity by flashing an empty vbmeta image" means in my case. What does this do?
Again I'm truly grateful for any help, thank you.

bouyakasha said:
My experience was this method word great for:
N100 / BE2012 / 10.5.8.BE85CB
N200 / DE2118 / 11.0.3.DE18CB (allowing me to create a boot image for an update that has no binary posted yet by OP)
My experience was this method didn't work great, and bricked because I didn't read the instructions and flashed the boot image instead of booting to the boot image to test it first for:
N100 / BE2012 / 11 (can't remember rest, but I tried with current 11 version)
Hope that helps.
Click to expand...
Click to collapse
Just to be clear I have a Metro N100 BE2015 running 11.0.1BE82CF.
With that being said, did you only get root when you went back to 10.5.8?
Are you rooted now on 11 and if so how did you get there?
Did you brick and go back to 10 then root 10 and update to 11 and keep root? How did you patch the img file after going to 11?
Any help and info would be much appreciated.
.

@onlycash I have constructed a small/random theory with no real basis. Could your problems be related to OOS 11? It sounds as dumb to me as it probably does to you, but I'm getting a nagging sensation that folks with success on your model aren't running the new update.
Just a weird hunch with no proper research, but I find it weird that you have these "unique" problems so I'm just spitting random junk at this point.