Develop Bugs

[Q] How to update to 4.4.3 with root

Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.

UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.

UnfriendlyTurtle said:
Hey all,
So I received a notification for a system update to 4.4.3, and I had survival mode in SuperSU checked, so I went ahead and followed the procedure. Turns off, then reboots into TWRP. From there I reboot again using the TWRP option, and it boots into android just fine. Notification is gone, still with root. But then I go to settings >> about to find that I'm still running on 4.4.2. Manually check for update, says there isn't one available. Give it a day or so and the notification comes up again. Repeat, and same thing. I'm stuck with the notification again.
So, how do I get rid of the notification, or more preferably, how to I update to 4.4.3 keeping the root? Thanks.
Click to expand...
Click to collapse
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.

charesa39 said:
You can't update the "normal way" like that with a custom recovery. When you try to do that, it tries to boot into the stock recovery to update, but since you have a custom recovery, it will fail everytime if you do it that way. What you have to do is flash the OTA zip using TWRP. You can find the OTA zip in /cache on your device. Or you can just download the update zip from these forums.
Click to expand...
Click to collapse
Right, thanks for the information. So I repeated and booted into TWRP again. Tapped 'Install', navigated to /cache, saw a couple of folders named 'back up', 'lost+found', and then a file name of a large string of letters followed by the recognisable "razor KTU70 from KOT49H", so I went ahead and flashed the latter, checking 'verify signature'. Runs through a few commands and in a few seconds comes back as failed, so I reboot into the OS.
Any ideas?
Aerowinder said:
Since 4.4.4 is out, just download the full firmware package from Google and flash system, boot. Only those two.
If you don't know how to do that, the Nexus 5 forums has some great stickies that are mostly relevant to this device.
Click to expand...
Click to collapse
I think I have an idea, but I'll check just to be sure. Thanks for the direction.

Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.

Anderson2 said:
Exactly the same for me. Installing the ota sent me to my TWRP recovery. Reboot - > still in 4.4.2.
Reading this thread, I went to TWRP recovery, installed the update from cache and like you, it failed.
Any suggestions? Did your idea work?
Where do I find the 4.4.4 mentioned here and how do I flash it in TWRP? Is install the same as flash in TWRP?
Thanks.
Click to expand...
Click to collapse
If it fails look to see what the specific error is. It would help to know that. If you pulled it from your cache then I assume it was downloaded by itself and should be the correct OTA. I do NOT have the "Zip file signature verification." box checked or "Enable MD5 verification of backup files." but I am extremely careful to flash/install the correct files. The OTA installed fine for me two days ago using TWRP 2.7.1.0. The 4.4.4 mentioned earlier is the factory image. You will need adb and fastboot installed on your computer to flash the factory image or any image that is pulled from inside the factory image. Wug's toolkit will work also, I think, but I've never used any toolkits. Eventually there will be a stock 4.4.4 rom that you can flash/install in TWRP but I'm not aware of one right now.

You can take the normal updates with root and TWRP (I did), but a custom kernel will prevent them from installing.

I retried to install the downloaded ota file from cache, but this time I checked zip file verification and got the error message that zip verification failed.
File name was
df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
So it seems the downloaded ota file may be corrupted. How do I get my Nexus 7 2013 to re-download a new one?
(The ota download for my Nexus 5 installed with no problems - but I think it didn't go through TWRP even though TWRP is installed there too).
Thanks
---------- Post added at 04:05 AM ---------- Previous post was at 03:59 AM ----------
Further
I renamed the ota file and in settings checked for system update and got a response that my system is upto date. But it is still 4.4.2.
Need to re-download the ota. How?

Changed the system date to 2 weeks earlier and succeeded in re-downloading the ota file.
So I retried installing it and it again took me to my TWRP recovery screen. I again installed the ota from cache and again the zip verification failed : 1
And the update failed again.
Still on 4.4.2
Did not change any system files as far as I know.
Need help.

Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.

Aerowinder said:
Why don't you guys download the stock firmware from Google (link in my signature), and use fastboot to flash system.img, boot.img (DO NOT run the batch file)? If it's a lack of knowledge, all you need do is ask, and I or someone else would be happy to teach you how to use it (fastboot). If you're going to be modifying your Nexus device, you need to learn fastboot. You guys have got to learn the proper way to do things.
You've put forth so much effort to fix a system that is not meant for modified (rooted, customized) phones. You can't fix it, stop trying. Just do it the proper way. And do not use a toolkit. They don't teach you anything, they spoon-feed.
Click to expand...
Click to collapse
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.

Anderson2 said:
I don't use a toolkit and would be happy to flash the system.Img and boot.img but need instructions on how to do it. You said the stock firmware link is in your signature but it isn't.
I would like to skip 4.4.3 and go directly from 4.4.2 to 4.4.4. I'm talking about a nexus 7 2013 wifi.
So I need the following information to proceed .
1. The Link to download system.img and boot.img for the nexus 7 2013 wifi. Which files exactly?
2. I have fastboot and adb installed on my windows 7 laptop because I used them (once) to root but I don't remember how I used them that one time. How exactly do I use fastboot to flash 4.4.4 ?
3. I presume I will lose root. How do I regain it after the above.
Thank you.
Click to expand...
Click to collapse
1. The Google firmware link in my signature is the one you want. You say you have the 2013 wifi model, aka flo, aka razor. "Factory Images "razor" for Nexus 7 [2013] (Wi-Fi)" is the proper section for you. You want 4.4.4 (KTU84P), and that's at the bottom of the razor section. Click the link to download.
2. Download the most up to date ADB/Fastboot from the link in my signature (19.0.2 (API 19)). Don't extract it yet.
3. You will lose root. Download SuperSU from my signature. 2.00 is the current version. After you download that, you can put it on your device so you can flash it in recovery in a few minutes.
The firmware you downloaded is razor-ktu84p-factory-b1b2c0da.tgz. This is a compressed archive, and you will need to extract it. If you don't know how, 7-Zip should work.
So, you've extracted the files. Delete flash-all.bat, flash-all.sh, flash-base.sh (so you don't accidentally run them).
Now, all you have left is bootloader-flo-flo-04.02.img and image-razor-ktu84p.zip.
Extract image-razor-ktu84p.zip to the current directory, so you will now have bootloader-flo-flo-04.02.img, boot.img, cache.img, recovery.img, system.img, userdata.img, android-info.txt, image-razor-ktu84p.zip in your folder.
Delete userdata.img, flashing this on accident will wipe your data. Delete image-razor-ktu84p.zip, android-info.txt, cache.img, recovery.img (this is stock recovery, you want TWRP).
Now you have boot.img, bootloader-flo-flo-04.02.img, system.img.
Remember the ADB & Fastboot zip you downloaded from my signature? Extract it to the directory with bootloader-flo-flo-04.02.img, boot.img, system.img. All 4 files. This directory now contains 7 files.
Back out of the razor-ktu84p folder. Just one step back. Now, hold shift the right-click the razor-ktu84p folder. Select Open command window here.
Reboot your device to bootloader mode. Do so by shutting it down. Then while the power is off, hold volume down and press the power button. Release these buttons when you see the big green Android.
In your command window, type the command: fastboot devices
Your device with it's serial number should show up on the list. If it does not there is a problem and you need to stop here.
If the device shows up, let's update it.
fastboot flash bootloader bootloader-flo-flo-04.02.img
<wait for it to finish>
fastboot reboot-bootloader
<wait for it to reboot>
fastboot flash system system.img
<wait for it to finish>
fastboot flash boot boot.img
<wait for it to finish>
fasboot reboot-bootloader
Done with fastboot.
At this point, enter recovery (TWRP) and wipe cache and Dalvik under advanced wipe.
Remember the SuperSU you downloaded earlier and put on your device for later? Flash that now.
Reboot, all done. Most of this is just juggling files around. If you have any questions ask.

You are wonderful aerowinder. This is just what I needed to go ahead. Thank you so much.
About your signature, it doesn't show the links when viewed in my Tapatalk version, but I went to the Web view and got it from there. (just FYI if others ask about your links).

is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!

droider137 said:
is it possible to just flash the system img in fastboot? It's still the same bootloader, not updated? Could I just flash the whole zip by sideloading in adb and TWRP? Just a lottle confused. Thanks!
Click to expand...
Click to collapse
If you were already on 4.4.3, all you need to do is fastboot flash system.img, that is correct.
No, you can't flash that firmware zip in recovery.

thanks

Hi Aerowinder
Thanks again for the excellent instructions. Everything went like clockwork until it didn't ?......
I got to the point where I issued the command fastboot devices which did show the tablet serial number. But my next command to flash the bootloader img gave me the error:
Cannot open 'bootloader-flo-flo-04.02.img
(I had copy pasted the command from your instructions).
The subdirectory below the command window contains that file (one of 7 files)
Sorry. What should I do?
In case you need the info, the device screen showed
Fastboot mode
Product name - flo
Variant - flo 32G
Hw version - rev_e
Bootloader version - flo-04.02
Carrier info = none
Serial number - xxxx
Signing - yes
Secure boot enabled
Lock state - unlocked
Thanks again.

Aerowinder, you are not only an expert but an excellent teacher. Your instructions above should be a sticky.
I'm all done. Everything is fine.
The problem I had above was a file path problem. Not sure why you told me to open the command window in the parent folder. When I opened it in the folder containing the seven files all your commands worked fine. (Except for your last one where you had a spelling mistake: fasboot instead of fastboot).
Thank you very much.

[Q] Software update problem (Red exclamation)

Hello,
I purchased HTC Desire 816 on eBay and unfortunately i received a Taiwan imported mobile.
When i try to update the phone it downloads the update and asks to install it now or later and when i click install now it reboots
and shows a green line for 20% of the full line and then i get a red exclamation mark. I have to restart it by holding power+volume up
buttons.
Can anyone help me out so that i can upgrade the software, i live in India.
I also did a factory reset from recovery mode but didn't resolve the issue and everything was in Chinese language after the reset.
Thanks.

Known69 said:
Hello,
I purchased HTC Desire 816 on eBay and unfortunately i received a Taiwan imported mobile.
When i try to update the phone it downloads the update and asks to install it now or later and when i click install now it reboots
and shows a green line for 20% of the full line and then i get a red exclamation mark. I have to restart it by holding power+volume up
buttons.
Can anyone help me out so that i can upgrade the software, i live in India.
I also did a factory reset from recovery mode but didn't resolve the issue and everything was in Chinese language after the reset.
Thanks.
Click to expand...
Click to collapse
@Known69 is your device currently rooted or do you have an unlocked bootloader? If so, root needs to be removed via the SuperSU app which will remove all root files and then going into the bootloader and typing
fastboot oem lock
Now you can try to update.
If your device is completely stock on the other hand it could be an issue with the update not downloading correctly. I will try to locate the RUU for your device so you can use it to restore to complete stock but could you provide me with the bootloader version of your device? Also you said you performed a factory reset and it didn't fix the issue, does that mean that you attempted to download the update once again and it failed at the same part in the process?
Sent from my 710C using XDA Free mobile app

@Known69,
I too received a Taiwan imported model. But my seller was so kind that he helped me to update the ROM to latest HTC sense 6. when I received the device, it was running sense 5.5 and rooted. Due to this the new update wouldn't install. After I installed the ROM, root is now removed and I can update when HTC releases further updates.

jaysoblitzed said:
@Known69 is your device currently rooted or do you have an unlocked bootloader? If so, root needs to be removed via the SuperSU app which will remove all root files and then going into the bootloader and typing
fastboot oem lock
Now you can try to update.
If your device is completely stock on the other hand it could be an issue with the update not downloading correctly. I will try to locate the RUU for your device so you can use it to restore to complete stock but could you provide me with the bootloader version of your device? Also you said you performed a factory reset and it didn't fix the issue, does that mean that you attempted to download the update once again and it failed at the same part in the process?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
No sir, it isn't rooted.
HBOOT-3.18.0.0000
Yes after the factory reset from the menu(Vol Down+Power) it completely changed the language to Chinese.
Then i tried it again and the same problem remained unsolved.

Known69 said:
No sir, it isn't rooted.
HBOOT-3.18.0.0000
Yes after the factory reset from the menu(Vol Down+Power) it completely changed the language to Chinese.
Then i tried it again and the same problem remained unsolved.
Click to expand...
Click to collapse
This file below is the Stock RUU only for the HTC Desire 816W / A5_DUG !
@Known69 Based off of you stating it was an Desire 816W via msg.
https://www.dropbox.com/s/h32sc97xl...8.3230.00D_F_release_389233_signed_2.zip?dl=1
Download it and make a copy of it.
Now rename both copies.
-Name one 0P9CIMG.zip
-Name one 0PC9DIAG.zip
Not sure which name your device uses but its one of these so just test both starting with the first one or put two copies one of each on your device.
You'll know because when you put this on the phone and go back into the bootloader it will ask you to use Volume Key to confirm the update. (Check to make sure it says A5_dug at the top)
Do this and let it update & complete.
Once done you can start up and update if its available but I'm pretty sure this is the latest full stock update for your device.
If its in Chinese and you want it to be a different language simply skip past everything and go into settings.
Go to this icon -> [[[A] (Should be the 7th icon from the bottom.)
Now select the first option.
Choose your language.
Done!
(P.S. Now you can root if you'd like!)

jaysoblitzed said:
This file below is the Stock RUU only for the HTC Desire 816W / A5_DUG !
@Known69 Based off of you stating it was an Desire 816W via msg.
https://www.dropbox.com/s/h32sc97xl...8.3230.00D_F_release_389233_signed_2.zip?dl=1
Download it and make a copy of it.
Now rename both copies.
-Name one 0P9CIMG.zip
-Name one 0PC9DIAG.zip
Not sure which name your device uses but its one of these so just test both starting with the first one or put two copies one of each on your device.
You'll know because when you put this on the phone and go back into the bootloader it will ask you to use Volume Key to confirm the update. (Check to make sure it says A5_dug at the top)
Do this and let it update & complete.
Once done you can start up and update if its available but I'm pretty sure this is the latest full stock update for your device.
If its in Chinese and you want it to be a different language simply skip past everything and go into settings.
Go to this icon -> [[[A] (Should be the 7th icon from the bottom.)
Now select the first option.
Choose your language.
Done!
(P.S. Now you can root if you'd like!)
Click to expand...
Click to collapse
Thanks for you time sir.
I have sent you PM regarding further issue if any, otherwise.

jaysoblitzed said:
This file below is the Stock RUU only for the HTC Desire 816W / A5_DUG !
@Known69 Based off of you stating it was an Desire 816W via msg.
https://www.dropbox.com/s/h32sc97xl...8.3230.00D_F_release_389233_signed_2.zip?dl=1
Download it and make a copy of it.
Now rename both copies.
-Name one 0P9CIMG.zip
-Name one 0PC9DIAG.zip
Not sure which name your device uses but its one of these so just test both starting with the first one or put two copies one of each on your device.
You'll know because when you put this on the phone and go back into the bootloader it will ask you to use Volume Key to confirm the update. (Check to make sure it says A5_dug at the top)
Do this and let it update & complete.
Once done you can start up and update if its available but I'm pretty sure this is the latest full stock update for your device.
If its in Chinese and you want it to be a different language simply skip past everything and go into settings.
Go to this icon -> [[[A] (Should be the 7th icon from the bottom.)
Now select the first option.
Choose your language.
Done!
(P.S. Now you can root if you'd like!)
Click to expand...
Click to collapse
Just tried with your solution.
The steps which i followed are:
Downloaded and renamed to the first name which you gave(0P9CIMG.zip) and placed in SDcard.
Loaded bootloader-->FastBoot-->Checking SD... and got an error "No image or Wrong image".
Then renamed it to "0PC9DIAG.zip" and repeated the same procedure and still got the same error.
Verified it was A5_dug and in the fast line it was stating "LOCKED" in red color, don't know if it is normal for this procedure or need it Unlocked.

Known69 said:
Just tried with your solution.
The steps which i followed are:
Downloaded and renamed to the first name which you gave(0P9CIMG.zip) and placed in SDcard.
Loaded bootloader-->FastBoot-->Checking SD... and got an error "No image or Wrong image".
Then renamed it to "0PC9DIAG.zip" and repeated the same procedure and still got the same error.
Verified it was A5_dug and in the fast line it was stating "LOCKED" in red color, don't know if it is normal for this procedure or need it Unlocked.
Click to expand...
Click to collapse
Do you see the green text that goes on and off within 3-4 seconds? In that green text when you first enter the bootloader it has the correct name that the file needs to be named.
Once it's on the SD/internal storage you don't have to click fastboot for it to flash. It will automatically scan and detect the moment after you see the green text in hboot/ first screen of bootloader.
As an alternative, you could also just flash the .zip image with
fastboot flash zip "zipname"
So for future example it will be
fastboot flash zip 0PC9IMG.zip
(No quotes)
Also you can type fastboot getvar all
It will show all your device information for you to double check everything is correct.
Sent from my 710C using XDA Free mobile app

I tried but it's reading both the files.
In first line **DIAG..Wrong or no image, continues in second line too. In third line **IMG.zip...Wrong or no image, continues in 4th line too. Now comes back to main boot loader screen.
I didn't get your manual instruction.
Where should I write those commands and which file as by default both the files are selected as stated above.
Thanks.

Known69 said:
I tried but it's reading both the files.
In first line **DIAG..Wrong or no image, continues in second line too. In third line **IMG.zip...Wrong or no image, continues in 4th line too. Now comes back to main boot loader screen.
I didn't get your manual instruction.
Where should I write those commands and which file as by default both the files are selected as stated above.
Thanks.
Click to expand...
Click to collapse
Doesn't matter which file you use and you can use those commands via fastboot in the bootloader, not hboot. Basically when you go into the bootloader just press the power button once and you'll be in fastboot. Plug it into your PC and use the command I posted above with adb on your PC to flash either file.
Sent from my 710C using XDA Free mobile app

jaysoblitzed said:
Doesn't matter which file you use and you can use those commands via fastboot in the bootloader, not hboot. Basically when you go into the bootloader just press the power button once and you'll be in fastboot. Plug it into your PC and use the command I posted above with adb on your PC to flash either file.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I got the 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"
}

Well when you enter the bootloader, the green text that comes up has the exact name that needs to be used for your device's RUU. I noticed that with the Virgin Mobile model it was 0P9CDIAG.zip
I also saw that some people stated their device says 0P9CIMG.zip
Your device zip name requirement could be different depending on the variant and you might have to reboot a few times to get the correct name written down correctly but it should be something along those lines provided above. Instead of IMG or DIAG it might say something else.
I also found the RUU for the Virgin Mobile model and I tested it but it only works when the device has the stock recovery and root permissions are removed.
When you remove all root from inside the SuperSU settings you HAVE to make sure to uninstall the app itself to ensure your device is completely stock. Use titanium backup if you have to.
After that I relocked my bootloader then the RUU flashed just by putting it on my SD card.
What I REALLY want to know is how your device has S-OFF.
Could you possibly make a CWM backup of your device and upload it? The boot.img would be really helpful with development of this device if S-OFF is achieved.
Sent from my 710C using XDA Free mobile app

jaysoblitzed said:
Well when you enter the bootloader, the green text that comes up has the exact name that needs to be used for your device's RUU. I noticed that with the Virgin Mobile model it was 0P9CDIAG.zip
I also saw that some people stated their device says 0P9CIMG.zip
Your device zip name requirement could be different depending on the variant and you might have to reboot a few times to get the correct name written down correctly but it should be something along those lines provided above. Instead of IMG or DIAG it might say something else.
I also found the RUU for the Virgin Mobile model and I tested it but it only works when the device has the stock recovery and root permissions are removed.
When you remove all root from inside the SuperSU settings you HAVE to make sure to uninstall the app itself to ensure your device is completely stock. Use titanium backup if you have to.
After that I relocked my bootloader then the RUU flashed just by putting it on my SD card.
What I REALLY want to know is how your device has S-OFF.
Could you possibly make a CWM backup of your device and upload it? The boot.img would be really helpful with development of this device if S-OFF is achieved.
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
Can you please help me achieving this "Could you possibly make a CWM backup of your device and upload it? The boot.img would be really helpful with development of this device if S-OFF is achieved."
Thanks.

Managed to take a screenshot of the error and the name.
http://puu.sh/cpSn2/3f0df7fc9c.jpg
Still failed.

Known69 said:
Managed to take a screenshot of the error and the name.
http://puu.sh/cpSn2/3f0df7fc9c.jpg
Still failed.
Click to expand...
Click to collapse
I will get the correct file for your device I noticed the CID and the S-OFF on your device. Is it possible to contact the source from where you obtained your device to ask them how they obtained those statuses?
Sent from my 710C using XDA Free mobile app

jaysoblitzed said:
I will get the correct file for your device I noticed the CID and the S-OFF on your device. Is it possible to contact the source from where you obtained your device to ask them how they obtained those statuses?
Sent from my 710C using XDA Free mobile app
Click to expand...
Click to collapse
I bought it from eBay and seller don't want to disclose the information
But he told he imported from Taiwan. I am sure he has tweaked something, he's fraud.

Bro For solving this issue you need twrp installed on your device.
Then ask someone for your stock recovery image and a twrp backup.
After obtaining this flash the image and install the backup and then try the OTA Update and im sure you will now be able to update

Known69 said:
I got the error.
Click to expand...
Click to collapse
I THINK ruu file should be ---.zip only ( not ---.zip.zip)
try that copy ruu file after rename it in your ext-memo and try

baager said:
I THINK ruu file should be ---.zip only ( not ---.zip.zip)
try that copy ruu file after rename it in your ext-memo and try
Click to expand...
Click to collapse
Yeah i too had the same doubt but didn't dare to try that out.
It booted up the **IMG.zip file for me.
Update is in progress...
Thanks.

Known69 said:
Yeah i too had the same doubt but didn't dare to try that out.
It booted up the **IMG.zip file for me.
Update is in progress...
Thanks.
Click to expand...
Click to collapse
you are welcome
just share us your final progress ???

[q] how to rename the asus zenfone 2 ze551ml firmware zip

Can someone please help me out with adb firmaware sideload. i have tried to flash a new firmware without root by adb sideload , but the problem am having is how to rename the stock firmware zip . for example UL-Z00A-WW-2.12.40.11-user. so that the command window will recognise it . i have tried many ways to rename the the zip , but all i get in the command window is zip not recognised.
C:\Users\MICHAEL\Desktop\FLASHTOOL>adb sideload
loading: 'UL-Z00A-WW-2.15.40.13-user.zip'
* cannot read 'UL-Z00A-WW-2.15.40.13-user.zip' *

segunmichaelolu said:
Can someone please help me out with adb firmaware sideload. i have tried to flash a new firmware without root by adb sideload , but the problem am having is how to rename the stock firmware zip . for example UL-Z00A-WW-2.12.40.11-user. so that the command window will recognise it . i have tried many ways to rename the the zip , but all i get in the command window is zip not recognised.
C:\Users\MICHAEL\Desktop\FLASHTOOL>adb sideload
loading: 'UL-Z00A-WW-2.15.40.13-user.zip'
* cannot read 'UL-Z00A-WW-2.15.40.13-user.zip' *
Click to expand...
Click to collapse
You cant sideload a zip file. You need to sideload the pre-rooted image then update to go back to stock...

ultramag69 said:
You cant sideload a zip file. You need to sideload the pre-rooted image then update to go back to stock...
Click to expand...
Click to collapse
My Asus zenfone 2 ze551mi was on CN firmware before . I decided to flash the pre-rooted system img on this website and ended up with WW firmware , i followed the instructions by downloading the OTA and then i put it in the root of the phone storage , but it starts update and end up with an error. i just want to have a non rooted and stock ww firmware on the device . is there a way out?

segunmichaelolu said:
My Asus zenfone 2 ze551mi was on CN firmware before . I decided to flash the pre-rooted system img on this website and ended up with WW firmware , i followed the instructions by downloading the OTA and then i put it in the root of the phone storage , but it starts update and end up with an error. i just want to have a non rooted and stock ww firmware on the device . is there a way out?
Click to expand...
Click to collapse
I also have a CN version flashed to WW.
I erased the boot image, recovery and system images using ADB then replaced them with WW version. I installed the pre-root img. for the sysem then updated. Once you update it will remove root for you, unless you find the latest pre-root files and ADB sideload that.
I believe the latest WW firmware is 2.15.40.13...
Cheers...

zenfone 2 flashing
i have this problem too. may i know how to flash the firmware? anyone know?

Have you tried an alternative method of "firmware flashing" using a MicroSD card?
segunmichaelolu said:
i followed the instructions by downloading the OTA and then i put it in the root of the phone storage , but it starts update and end up with an error. i just want to have a non rooted and stock ww firmware on the device . is there a way out?
Click to expand...
Click to collapse
segunmichaelolu said:
i have tried to flash a new firmware without root by adb sideload , but the problem am having is how to rename the stock firmware zip . for example UL-Z00A-WW-2.12.40.11-user. so that the command window will recognise it . i have tried many ways to rename the the zip , but all i get in the command window is zip not recognised.
Click to expand...
Click to collapse
I know this is a long past due thread never seeing a presentable solution and possibly not even needing one anymore, but I came across it and thought I might add to it if I can, in the event that it's found by someone else having a similar issue.
Rather than attempting to flash using adb/fastboot or using the command window or placing the update in the internal storage of the device for that matter; to apply the update try using this alternative method:
First rename the firmware zip file to the following:
MOFD_SDUPDATE.zip - No need for version numbers, world codes, region codes, etc.
Then, load the newly renamed .zip file onto a microSD card (again, not internal memory, but external) and then boot the Zenfone the same way you would when trying to get into recovery. The system should automatically recognize the .zip and on it's own, begin applying the update WITHOUTthe need of being connected to a computer. It's, in a way that's oversimplified and not to be taken literally, essentially tricking the system into thinking it's an OEM applied update and allows extraction and execution/flashing of the zip file more freely then say, through fastboot without properly set permissions and needing to be a .img file specified to a partition table address.
Hope this helps or somehow makes its way back a couple of years to the you who needed it xD If it doesn't, then simply DON'T hit the Thanks button and let me know what happens instead and I'll try to better assist you.

Zenfone 2 Z00AD doesn't have "System update"

Hi guys,
I just bought an Asus ZE551ML Z00AD. I do not have the "System update" voice under Settings > About, and i noticed that the DM Client is not installed.
What can I do? Thanks!

giuliog.96 said:
Hi guys,
I just bought an Asus ZE551ML Z00AD. I do not have the "System update" voice under Settings > About, and i noticed that the DM Client is not installed.
What can I do? Thanks!
Click to expand...
Click to collapse
Have you tried a factory reset? Either by recovery or settings should work fine

I tried a factory reset, without results.
I'm going to try to download the update from Asus website, hoping that it will find it when i put it in the root of the sdcard.
I'll let you know!

Go to about and check the rom version, it could be a WW rom over a CN rom but if the bootloader has been flashed you can't seem to go to a lower firmware version than whats on.
Go to the Android developement>pre-rooted roms and download a pre-rooted rom from there... Make sure it has an equal or higher build date than the installed rom.
I installed all the img files through fastboot using these commands (make sure you use these commands exactly or you will brick your phone, just flashing something over the same partition does nothing)-
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
The img files are inside the fastboot tools folders and must be named the same as the the end, system.img for the rom must be system.img, not 139.img or it won't find it...
Then I wiped cache also using "Fastboot erase cache".
I now have a pre-rooted rom installed with WW firmware. I may not get OTA as the serial number would be registered on the CN server not WW but these updates are easily installed thanks to the hard work of people like Shakalaka...

Just go to the ASUS website and download the latest update that matches your firmware, for example ww, cn, jp etc. When I first got my device it had a firmware from May installed which had no update options under the about phone settings too and as soon as I downloaded the latest firmware put it on the root of my device it detected it and installed.

PSA - Going back to stock from Treble.

I've noticed that many in this forum for the Honor 7x / Mate SE want to try a few ROMS, and then eventually go back to stock - Some just want to go back to stock. I had my own issues and thankfully there were others to help along the way. This method does not use fastboot to flash partitions, it uses TWRP, so the assumption is you have a working TWRP. Also I am not responsible for any bricks, I am just explaining what I did to get back to stock (And based on all the issues people are having, I'm staying there)
If you've tried a Treble ROM or others, the route I took to get back to stock was as follows:
1.) Download your firmware from Firmware finder or the Pro-TeamMT website:
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-l34&firmware_page=0
In this example, mine is the Mate SE..
You should have downloaded 3 files. The important one we want right now is the Update.zip - Extract this file. You should see UPDATE.APP within this folder.
2.) Download the Huawei extractor software by worstenbrood:
https://forum.xda-developers.com/showthread.php?t=2433454
3.) Use this software to extract the files from the Update.App - You may need to disable the Checksum checks under "Settings". When you select the UPDATE.APP file, you should get a list of the files that are compiled or compressed into the app. The main 4 files you want are Ramdisk, Vendor, System, and if you'd like the Stock recovery (Recovey_Ramdisk). Copy these files to your SD card.
4.) Assuming you still have the functioning TWRP, reboot into TWRP and wipe everything but the SD card.
5.) Flash the images to the appropriate partition, Ramdisk = Ramdisk, Vendor = Vendor Image, and System = System Image - Ensure you're flashing the image partitions. Ramdisk is necessary if you've ever rooted or used Magisk.
At this point you should be able to reboot and get back into stock...But you'll notice Themes do not work properly..That's because you've wiped / formatted data at some point in TWRP, and now the Data/hw_int has been wiped. You can fix this by flashing the update on top of itself by the instructions in this thread (Thanks to mrmazak):
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
See the "Flash update while on Oreo"...This has worked twice now to get me back my themes after wiping /data.
I counted on my TWRP backup to get me back to stock after trying a Treble ROM, and I ended up bricked. So hopefully this helps someone!
PS, if anyone has more to add this this, the more help the better.

Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???

crayonicle said:
Wait, wouldn't the recovery be the file "RECOVERY_RAMDIS.img"
???
Click to expand...
Click to collapse
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.

Corrections, please add to original post
smokinjoe2122 said:
You are correct...That is the name of the actual image in the UPDATE.APP, but I was basing the name off of the actual partition.
Click to expand...
Click to collapse
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883

crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
System image can fail too...that's why I said to flash everything in TWRP...Plus, flashing the update on-top of itself will not only give you theming back, but stock recovery.

crayonicle said:
Just learned today that you can't flash Vendor through Fastboot, so you have to copy all the necessary files onto a SD card or USD OTG.
The files needed are: "SYSTEM.img" "RECOVERY_RAMDIS.img" and "VENDOR.img"
Flash them through twrp in the required partitions, the partition names are literally the file names.
TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=28883
Click to expand...
Click to collapse
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.

Adithya Krishnakumar said:
Is this working ? Did you try ? I'm on RR ROM and couldn't get adb recognize my device. This is my only hope to return to stock as of now.
Click to expand...
Click to collapse
Yes, I tried it. It works flawlessly.

How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.

crayonicle said:
How can I get themes to work? I don't understand the original post, it makes no sense when explaining how to get themes to work properly. I do not know what to do with the link provided in the original post.
Click to expand...
Click to collapse
What part are you stuck on?
Essentially mrmazak created a flashable file that will take the 3 firmware files you download and flash them on top of your current firmware. This is helpful for doing an update or just reloading the firmware completely (Which is what you're trying to do)...
I'd follow the exact instructions that he's put out on that thread, but the 10,000 ft overview:
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
1.) Download files from link for your device
2.) Create a correctly named folder on your SD card, along with those files properly named in that folder (Ensure these files are named properly also.)
3.) Ensure you have the stock recovery on the SD card also.
4.) Copy the "xxx_Update.zip" he created onto your SD
5.) Flash the "xxx_Update.zip"...It will will flash the stock recovery, then boot into update mode and update with the 3 files you downloaded and put into that folder. This will basically "reflash" the firmware and give you back themes.
I would go step by step on his action list and follow them to a "T". I've verified it works perfectly. He also has a "Basic-Instructions" write up in the zip also.

My device build number was BND-L21C185, I bricked my device once but I managed to get it back. Since then I have strange build number which is system 8.0.0.046(063f). Does this method fix it?

This info helped me bring my phone back to life,thank you sir for the step by step instructions.

Found a way to get back to stock without all this hassle lol
So I thought this was the only way to get back to stock... turns out there is a much easier way
This method also enables themes, I checked myself.
https://forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722

Is it possible to flash all of the partitions from fastboot?
I have the BND-L34 and I am unsure as to what happened.
I have been running the RROS surdu_petru posted for about 3 weeks now and it was running fine.
2 days ago I grab my phone and it was booted into error mode. Now when I try to boot into twrp I get an error code for my recovery. When I try to boot into the system it throws a different error code for boot image.
I have a twrp backup stored on an sd card, and all 3 OTA's I saved back during the June update. I have the Pro-TeamMT app on my pc and have found/extracted every file for the brick method only get the same errors, 1 right after the other.
I am no noob, (although I am not a Senior Member with a giant banner either ) but I have been rooting android devices going on 8 years now, and have never completely bricked any of them.
My last 2 phones were Oneplus 1 and Oneplus 3, so I am familiar with flashing all the partitions using fastboot. But with those phones there were about 9 different individual flashes that needed to be done in a particular order.
Any help or advice would be greatly appreciated.