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] 4.4.2->4.4.4 VRZN Rooted

This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!

I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too

has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)

dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...

I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.

Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.

Whats the best twrp for root on 4.4.4

Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.

dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.

I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.

The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip

KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.

Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X

Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:

Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?

zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X

Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.

dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu

KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!

fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...

[Q] How to flash OTA updates once rooted/custom recovery?

Hi Nexus 6 experts -
My Nexus 6 arrived today, so of course the first thing I did was follow this thread to unlock the boot loader, gain root, and TWRP:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Now I'm reading about how this breaks OTA updates, and after 30 minutes of looking for the right answer across the forums, I'm in need of some more accurate advice.
1. Is this the right location for downloading factory images?
https://developers.google.com/android/nexus/images
Part of my confusion stems from the fact that my build number for 5.0 is currently LNX07M, and the one listed for 5.0 is LRX21O. Does this matter at all? Could I flash the files from 5.0.1 (LRX22C) without any issue?
2. In order to flash 5.0.1, is this the right procedure to follow?
http://forum.xda-developers.com/showpost.php?p=57411133&postcount=75
I'm looking for how to flash the right images in the right sequence with fastboot, as I'd rather not use any toolkits. The aforementioned post flashes the radio image, then the system image. Is anything else missing there?
3. I'm assuming I need to re-flash root again after this point - is the version listed in the beginners guide still applicable?
Since I've had the phone for all of 2 hours I'm trying my best not to brick it. Any insight would be appreciated, thanks!
EDIT: Download the factory images from the google link above and extract everything. The first extraction renders the radio and bootloader images, along with a zip file. Extract the zip file and you'll find the boot, cache, recovery, and system images. Using fastboot is easy:
fastboot flash <type> <filename>
example:
fastboot flash system system.img
As far as I can tell, <type> is specific to every file. Very easy, only takes a few minutes, and you only need to flash what you need.

Yes Lollipop requires 100% stock for OTA updates now. But OTA is overrated
1. Yes indeed. thats the right place. Wasn't LNX07M the pre-release developer preview?
2. The image contains a flash-all script for windows and linux, but this will wipe data (unless you remove the -w i believe) but I prefer to flash individually.
flashing Radio isnt essential but you will probably want to try it at least. You also want to flash the system and boot images (boot image is the kernel). Then flash SuperSU from recovery. I know OTA's have a script that replace your recovery on first boot if you dont immediately root. I havent flashed a factory image for a whiole so not sure if these have them too, so just a word of caution there.
3. I tend to go for the latest from the beta thread personally, but there is no hard going for older versions except that some things might not gain root properly due to the changes with SElinux etc

Hey thanks rootSU - this is exactly what I was looking for! Once I run through that process I'll add the details to my original post.

So I am on LRX210, rooted and am running twrp recovery. Sounds like I should download the 5.0.1 image and flash the boot, cache, recovery, system, and radio files individually, correct?
Any specific order?

scotbotmosh said:
So I am on LRX210, rooted and am running twrp recovery. Sounds like I should download the 5.0.1 image and flash the boot, cache, recovery, system, and radio files individually, correct?
Any specific order?
Click to expand...
Click to collapse
I only flashed a few of the files, like boot, system and radio. Recovery will remove twrp so you don't want that. Order doesn't seem to matter.

im on 5.01 decrypted boot img...if 5.02 comes out all i do is flash an xda modded 5.02 img boot decrypted file and all the other files except for userdata.img to save all my data and files/settings right? no neeed to revert back to stock, update to ota official 5.02, blah blah ...

cobyman7035 said:
im on 5.01 decrypted boot img...if 5.02 comes out all i do is flash an xda modded 5.02 img boot decrypted file and all the other files except for userdata.img to save all my data and files/settings right? no neeed to revert back to stock, update to ota official 5.02, blah blah ...
Click to expand...
Click to collapse
Yeah you shouldn't need to revert/unroot and use the OTA. Just flash what you need from the factory image. System is the only major one to flash, boot would be the kernel, so use whatever you need for the decrypted version.
I'm assuming userdata overwrites /data which would wipe your files and apps.

I using a rom based on the stock - Is there any deference to the original one?

Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!

1. Read the build information in the OP of the thread, it mentions all the differences.
2. It's the full stock FW but recovery flashable instead of fastboot and also rooted.
3. You would need to fastboot stock FW and manually root or flash the recovery flashable stock FW the was mentioned in question no. 2.

1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!

duba500 said:
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 Read this to get a better idea what to do.

duba500 said:
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
Click to expand...
Click to collapse
1)Differences would be that SuperSu is installed, busybox is installed, encryption is disabled in the kernel, important gapps such as google play services and the play store are updated to their newest current version so when you install the rom google services immediately work without needing to wait for a background update, gapps that can be fully functional by just downloading them from google play store (google+, youtube, google drive, etc) were removed from /system likely to save space to make it easier to install mods such as guitardedhero's viper/dolby sound mod, vanilla android's gallery photos app was added in place of google photos app, the little android debugging notification is hidden, and the tethering check was disabled to allow for tethering without a tethering plan.
2) The updated recovery flashable line is referring to the fact that the dev updated the google apps in the rom.
3) If you wanted to go totally stock then you'd need to just flash the boot.img and system.img out of a factory image from google since the rom is very very close to stock a userdata wipe shouldn't be needed and a cache/dalvik wipe may or may not be but as always have a backup in TWRP. Then go into TWRP before booting and install the latest SuperSu (2.65 iirc right now) installing the newest SuperSu's can cause a bootloop or 2 (in the middle of booting the phone will go back to the Google logo and booting again, it will usually do this 1 or 2 times before properly booting). (if you boot to android before going to TWRP it will be replaced since you have an untouched /system after flashing the system.img). And if you allow TWRP to keep /system as read only (it'll popup when you first boot into TWRP asking if you want to do that) then the stock /system will replace TWRP with stock recovery and OTA's will work if you do a total unroot from within the SuperSU app.

Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download the factory image and just extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersyood it right?
Thanks for your advice-tip of the SuperSu version!
P.S:
LG doesnt have a dev site such as Google's have with all the Factory Firmwares?
Can I trust site such as: lgg3root. com/lg-g3-stock-factory-firmware
???

duba500 said:
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download G3 LS990 32GB and extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersood it right?
Click to expand...
Click to collapse
You have got a fantastic tip in looking here: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Search for fastboot.

[GUIDE][TRICK][Links updated] How to flash Stock ROM/OTA update via TWRP

Update: Now you can download the updater-scripts from Android file host. Zip contains two updater-scripts [updater-script_Z00E-R for ZE500KL/G and updater-script_generic for other variants]
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the FOTA because you are running a custom ROM. One way of flashingf FOTA would be to flash stock recovery from fastboot and then downgrade to a lower firmware (say the last lollipop fota) and then flash the new update (say MM fota). many a times, update fails at verifying system image! Then you have to do everything again. Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. Moreover, if you edited it incorrectly, you may hard brick your device. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device to the zip. Flash via TWRP recovery. Simple!
INSTRUCTIONS & DOWNLOADS
ZE500KL & ZE500KG
Usage:
Upgrade to MM without reverting to stock lollipop
Downgrade to any stock firmware version
Go back to stock
Recover from failed custom ROM installs
Download updater-script_Z00E-R (link changed to mediafire)
[NOTE: Rename it to "updater-script" ]
A proof that this works is here​
All other variants
Edited updater-script for these devices will only flash system and boot. You have to flash last lollipop update and then only you can upgrade to MM
But there's is one benefit of this over other methods. You don't need to find and flash stock recovery!
How?
> Flash last lollipop update that your device was running using the edited updater-script.
> Reboot device and Do all the set up.
> Reboot again but this time INTERRUPT the reboot by holding power button till screen turns off.
> Asus Logo will appear again. Allow Rebooting this time.
> Voila! Your stock recovery is back. You can upgrade to MM now using the regular method.
( All FOTAs contain back up stock recovery but not in .img form. A failed boot causes auto installation of this stock recovery back up)
Other Usage:
Go back to stock
Downgrade to any stock firmware version without affecting bootloader and modem
Recover from failed custom ROM installs
Download link: updater-script_generic (link changed to mediafire)
[NOTE: Rename it to "updater-script"]​
Don't forget to hit thanks
Why the can't I make updater-script for these variannts the way I made for ZE500KL/G ?
There are 6 variants (excluding ZE500KL/G) . Each variant has 3 sub variants. Each sub variant comes with upto 4 SKUs.
Every FOTA contains critical firmware files like aboot, hyp, etc of all variants and cross-flashing these would hard brick. Hence, the edited updater-script_generic will only flash system and boot.
.

Thanks man. It would really be helpful.
Hit Thanks If I Helped

sziraqui said:
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the ota because you are running a custom ROM. One way of flashing ota would be to flash stock recovery from fastboot and then upgrade to a lower firmware (say the last lollipop ota) and then flash the new update (say MM ota)... Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device and android version to the zip. Flash via TWRP recovery. Simple!
DOWNLOAD LINK
Choose correct updater-script accorind to filename suffix
Z00L-T_MM = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Marshmallow OTAs
Z00L-T_LP = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Lollipop OTAs
Z00E-R_MM = ZE500KL, ZE500KG for Marshmallow OTA
Z00E-R_LP = ZE500KL, ZE500KG for Lollipop OTA
Rename file to "updater-script" before adding to zip.
Click to expand...
Click to collapse
Just no, it will cause many devices to flash wrong firmware leading to non working display and/or modem
TWRP label the device Z00T or Z00L unlike asus that for every variant ( ZE/ZD 550/551/600/601 ) they label it in a different way
This label is checked by the updater-script to flash the proper firmware and modem ( ex, it checks if the display is fhd or hd, check soc msm8929, msm8939, msm8916 )
Ex you have Z00L with the following specs: soc msm8939 && codename ZE600KL -> your script will flash msm8916 firmware and ZE551KL modem probably totally bricking the device
Remove the download links as fast as you can

Device- Z00LD
What I did- unpacked the MM OTA zip via 7zip.
Replaced the MM updater-script from MM OTA.
Repacked it.
Wiped everything through TWRP prior flashing it.
(Was on stock latest LP)
Flashed it.
But, while flashing was in process, it ended up with following line-
Updater process ended with signal: 11.
Overall, it simply didn't work
Hit Thanks If I Helped

sziraqui said:
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the ota because you are running a custom ROM. One way of flashing ota would be to flash stock recovery from fastboot and then upgrade to a lower firmware (say the last lollipop ota) and then flash the new update (say MM ota)... Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device and android version to the zip. Flash via TWRP recovery. Simple!
DOWNLOAD LINK
Choose correct updater-script accorind to filename suffix
Z00L-T_MM = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Marshmallow OTAs
Z00L-T_LP = ZE550KL, ZE551KL, ZE601KL, ZE550KG, ZD551KL for Lollipop OTAs
Z00E-R_MM = ZE500KL, ZE500KG for Marshmallow OTA
Z00E-R_LP = ZE500KL, ZE500KG for Lollipop OTA
Rename file to "updater-script" before adding to zip.
Click to expand...
Click to collapse
The first line in the original updater-script check if you have the required firmware to install the new one. If you flash on the wrong firmware your device will break your phone. When you update from LL to MM the zip needs to flash the new "firmware-update" No?

luca020400 said:
Just no, it will cause many devices to flash wrong firmware leading to non working display and/or modem
TWRP label the device Z00T or Z00L unlike asus that for every variant ( ZE/ZD 550/551/600/601 ) they label it in a different way
This label is checked by the updater-script to flash the proper firmware and modem ( ex, it checks if the display is fhd or hd, check soc msm8929, msm8939, msm8916 )
Ex you have Z00L with the following specs: soc msm8939 && codename ZE600KL -> your script will flash msm8916 firmware and ZE551KL modem probably totally bricking the device
Remove the download links as fast as you can
Click to expand...
Click to collapse
Well, just to check if it works, I flashed RR ROM and then Flashed Stock MM ota with edited updater-script. My phone booted up without any problem (ASUS_Z00L_63)
I know, custom ROMs label our devices differently. On RR, there was not ro.product.device=, line/ The updater -scripts will flash firmware-update package only if ro.product.device= is the same as that labeled by asus.. For all variants ro.product.device= have a suffix "ASUS_" which is completely differnt than what is provided by cm/rr/beanstalk and any other custom ROM. Just beacuse I respect you a lot, I am removing download links for now and I will look at all possibilities of brick. If found, i will remove the radio part of the script so that users don't end up flashing incorrect firmware. Thanks
edit: Just forgot to mention, I have modified the updater-script to prevent brick. Its 100% safe now.

sziraqui said:
Well, just to check if it works, I flashed RR ROM and then Flashed Stock MM ota with edited updater-script. My phone booted up without any problem (ASUS_Z00L_63)
I know, custom ROMs label our devices differently. On RR, there was not ro.product.device=, line/ The updater -scripts will flash firmware-update package only if ro.product.device= is the same as that labeled by asus.. For all variants ro.product.device= have a suffix "ASUS_" which is completely differnt than what is provided by cm/rr/beanstalk and any other custom ROM. Just beacuse I respect you a lot, I am removing download links for now and I will look at all possibilities of brick. If found, i will remove the radio part of the script so that users don't end up flashing incorrect firmware. Thanks
Click to expand...
Click to collapse
Modem is the easiest problem to fix, but if you flash wrong firmware it will be a big problem
Sent from my ASUS_Z00TD using Tapatalk

luca020400 said:
Modem is the easiest problem to fix, but if you flash wrong firmware it will be a big problem
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
By "radio" I meant lines of the script below "radio works" line. In short, removing entire firmware package update part of the script, so that it only flashes system and boot. But then this will it be only for those who want to revert to a stock firmware version that was flashes on their device at some point in time. Still useful

I think that the ideea is not bad. But sure, some checks should be in place.
I had to go back to stock several times just to get the latest baseband. It would be easier to flash the stock via TWRP - instead of flashing the factory recovery, factory firmware and then fastboot to go back to TWRP.
Would also help if we could get the newest baseband some other way - (like form OP links).

SoNic67 said:
I think that the ideea is not bad. But sure, some checks should be in place.
I had to go back to stock several times just to get the latest baseband. It would be easier to flash the stock via TWRP - instead of flashing the factory recovery, factory firmware and then fastboot to go back to TWRP.
Would also help if we could get the newest baseband some other way - (like form OP links).
Click to expand...
Click to collapse
Look at my signature, I have made a thread which has TWRP flashable baseband for all variants

Thank you for your Script
I have ZD551KL
I updated script file as you mentioned to Last LP OTA
i flashed updated zip file with twrp
more than 30 min its still on " patching system image unconditionally......"
Previously i installed RR Rom, and i try to revert to stock its not installing, so try to your method,
Kindly advice me to solve it.
Thank you.

Pretty useful. Thanks

You can also flash the files from CM13 then do the generic update script without going back to LP. That's what I did with mine.
Posted using a calculator and delayed by AT&T.

Not to be stupid but what and how do I use the updater script generic?

corybucher said:
Not to be stupid but what and how do I use the updater script generic?
Click to expand...
Click to collapse
Replace the same file in the stock update file that you downloaded from Asus or any other source.
Posted using a calculator and delayed by AT&T.

Hello, I don't understand, is the "stock recovery" the ROM zip file from the official website ? If so I don't find any updater-script file in it :/ ? Thanks
Edit : I finally find it in google folder, but still not working with TWRP when I try ton install, it says Zip file is corrupted :/

Can anybody give me an OTA stock ROM which is working with this ? I tried with 2 ota, replacing the system file, each time I got an error in TWRP saying can't find update-binary in the zip file :/
I'm using this ROM today [ROM][6.0.1] Smoothified Stock ROM [ALL VARIANTS] http://forum.xda-developers.com/zenfone-2-laser/development/rom-smoothified-stock-rom-t3404050
And wanna go back to an official one, please, thanks

Bibi86 said:
Can anybody give me an OTA stock ROM which is working with this ? I tried with 2 ota, replacing the system file, each time I got an error in TWRP saying can't find update-binary in the zip file :/
I'm using this ROM today [ROM][6.0.1] Smoothified Stock ROM [ALL VARIANTS] http://forum.xda-developers.com/zenfone-2-laser/development/rom-smoothified-stock-rom-t3404050
And wanna go back to an official one, please, thanks
Click to expand...
Click to collapse
Just download the OTA from asus website. Replace the update script. Then flash it.
Posted using a calculator and delayed by AT&T.

Thank you, but I already tried this, doesn't work for me :/ I can't access the recovery anymore (volume down+power on) so I've tried to flash it using twrp but it's not working :/
Can you give me a link for official ota please, thanks

sziraqui said:
You were running a custom ROM but at some point of time you decided to go back to stock. Unfortunately, you do not have a TWRP backup. Or probably there is an official update but you can't flash the FOTA because you are running a custom ROM. One way of flashingf FOTA would be to flash stock recovery from fastboot and then downgrade to a lower firmware (say the last lollipop fota) and then flash the new update (say MM fota). many a times, update fails at verifying system image! Then you have to do everything again. Maaaaahhhhhhhnnnnnnnnnnn. This is so painful.
Solution? Just by editing the updater script of any ota, you will be able flash it via TWRP. But then you probably don't know what to edit. Moreover, if you edited it incorrectly, you may hard brick your device. So here I have edited updater-scripts for you. Just delete the updater-script from your ota zip and add edited updater-script for your device to the zip. Flash via TWRP recovery. Simple!
INSTRUCTIONS & DOWNLOADS
ZE500KL & ZE500KG
Usage:
Upgrade to MM without reverting to stock lollipop
Downgrade to any stock firmware version
Go back to stock
Recover from failed custom ROM installs
Download updater-script_Z00E-R
[NOTE: Rename it to "updater-script" ]
A proof that this works is here​
All other variants
Edited updater-script for these devices will only flash system and boot. You have to flash last lollipop update and then only you can upgrade to MM
But there's is one benefit of this over other methods. You don't need to find and flash stock recovery!
How?
> Flash last lollipop update that your device was running using the edited updater-script.
> Reboot device and Do all the set up.
> Reboot again but this time INTERRUPT the reboot by holding power button till screen turns off.
> Asus Logo will appear again. Allow Rebooting this time.
> Voila! Your stock recovery is back. You can upgrade to MM now using the regular method.
( All FOTAs contain back up stock recovery but not in .img form. A failed boot causes auto installation of this stock recovery back up)
Other Usage:
Go back to stock
Downgrade to any stock firmware version without affecting bootloader and modem
Recover from failed custom ROM installs
Download link: updater-script_generic
[NOTE: Rename it to "updater-script"]​
Don't forget to hit thanks
Why the can't I make updater-script for these variannts the way I made for ZE500KL/G ?
There are 6 variants (excluding ZE500KL/G) . Each variant has 3 sub variants. Each sub variant comes with upto 4 SKUs.
Every FOTA contains critical firmware files like aboot, hyp, etc of all variants and cross-flashing these would hard brick. Hence, the edited updater-script_generic will only flash system and boot.
.
Click to expand...
Click to collapse
hello.
my phone is asus zenfone 2 laser ze500kl
i have removed OS by mistake. now TWRP says no OS found. my bootloader is not unlocked and i have perfect running TWRP.
when i flashed stock rom it was showing this error. This is for WW phones. this phone is asus zooed
when i followed your script it successfully flashed but when i reboot i stuck at the asus logo.
did i do the correct process? please help me. i need your help. thanks in advance. waiting for your reply