Related
Hi,
I did a mistake by not S off my mobile prior to upgrade. However, I under stood from the response (http://forum.xda-developers.com/verizon-htc-one/help/sunshine-su-access-denied-t2845121/) that I'll have to wait till sunshine 3.0 come out.
Meanwhile, I've a long history of ROM/OS issues with this device. Now it got OTA update from 4.4.4 to Lollipop
Unfortunately, there seems to be missing files from my last system erasing
For example, the Exchange ActiveSync keep deciding on random basis not to sync, asking for the password (which is not changed) then it resolve the issue by itself. Another example is the camera, where I cannot enable video recording from inside the camera, I seem to be able to make from within messenger apps!!! :S
So, my question would be how can I reapply the Lollipop ROM again?
I've downloaded both, the exe file from HTC support site, and the zip file from RUU famos article on this forum.
The exe version says it will reboot to recovery but it never finish (stops on black screen with HTC gray logo)
The zip file installation through recovery failed, and through renaming it to 0P6BIMG.zip and put it on the SD root failed as well.
Any ideas?
Need to add, I've downloaded the file "RUU_M8_UL_L50_SENSE60_MR_BrightstarUS_WWE_4.16.1540.8_Radio_1.24.21331147A1.09G_20.68.4196.01_F_release_411207_signed_2.exe"
Now, when running this tool, it says the update will be:
From Image version: 4.16.401.10
To Image version: 4.16.1540.8
I'm not sure, but is this file for another model?
Read carefully here
http://forum.xda-developers.com/showthread.php?t=2701376
Read it well and it has all the answers to get back to stock backup and update again.
If you are s-on you can't flash any other ruu than the one that matches your phone.
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Same problem but didn't understand your procedure
Thank you for your solution but I didn't understand
I had the same problem : I rooted my phone by flashing pre-rooted system.img. It worked but now I want to be able to update OTA. So I need to replace pre-rooted system.img with stock one.
Can you please explain how you "erased system, boot.img and droid_boot.img then reflashed WW versions"?
I tried the following : fastboot erase system, fastboot erase cache, and then adb sideload UL-Z00A-WW-2.13.40.13-user.zip with official firmware downloaded from asus.com. But now my phone is blocked on black boot screen "ASUS in search of incredible, powered by android". I can only boot to recovery. Can you repair my phone without wiping data? Thank you.
Not even any clue
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
remidem said:
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
Click to expand...
Click to collapse
Apparently you can unroot through supersu. This should then allow OTA updates...
Already tried
ultramag69 said:
Apparently you can unroot through supersu. This should then allow OTA updates...
Click to expand...
Click to collapse
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
remidem said:
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
Click to expand...
Click to collapse
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Impossible to update with sdcard
ultramag69 said:
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Click to expand...
Click to collapse
Thank you for your reply. I tried OTA update with sdcard:
1) In Settings/About/Software information, my current version is 2.13.40
2) I dowloaded, from http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999 update from 2.13 to 2.14
3) Copied to external sd, in root folder, and renamed zip to MOFD_SDCARD.zip
4) Rebooted in recovery
5) Update failed. Here is my log:
Finding update package...
I:Update location: /sdcard/MOFD_SDUPDATE.zip
Opening update package...
E:file path:/sdcard/MOFD_SDUPDATE.zip
Installing update...
script aborted: Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_20150529_9543_user:user/release-keys.
Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_2015
E:Error in /sdcard/MOFD_SDUPDATE.zip
(Status 7)
SD Installation aborted.
This is because the version of system.img is 2.18 and the fimware version is 2.13.
Indeed I have 2 choices:
- override system with a system.img in version 2.13, but I cannot find any.
- try to apply OTA update 2.17 to 2.18 or 2.18 to 2.19 but it seems risky.
Finally I found!!! I think that a version of the firmware is tagged in system partition and another version (classically the same) is tagged in data partition (this is the one you see in Parameters -> About -> Firmware version). When I wanted to flash a firmware the same version as the one written in parameters (2.13), my phone refused to downgrade because the version of system was higher (2.18). So I had to format the system partition, apply update with official 2.18 firmware. And it worked! My phone was unrooted and I could apply method 3 root.
My issue occurred because I made the following:
1) bought a phone with a 2.13 firware
2) used it for months, applied OTA updates until 2.18
3) flashed a 2.18 pre-rooted system.img
4) used it for weeks until a made an update of supersu
5) my phone couldn't boot any more, so I wiped data (I could avoid that, if I knew!). It made a factory reset, ie get back firmware to 2.13, but system was still in 2.18
Here is the procedure to revert a phone flashed with a pre-rooted system.img (to sell it, send back to warranty, or root with another method):
1) Download official firmware from asus website in the same or higher version of your pre-rooted system.img. Do not rely on version in Parameters -> About -> Firmware version. Or simply download the latest version.
2) In your phone bootloader, enter the following commands with your PC:
fastboot erase system (I'm not sure it is necessary)
fastboot format system
3) With your phone, go into recovery menu, then to "Update with adb"
4) With your PC, go to the directory where you downloaded the firmware as zip, and enter the following command: adb sideload nom_du_fichier_teléchargé.zip
5) It takes about an hour
6) You can reboot
After that I used method 3 to root again, so that I can now OTA update exactly the same way I used to do before rooting. Moreover, I think I can update supersu as well.
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
wrecklesswun said:
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
Click to expand...
Click to collapse
Someone said you need to use fastboot to flash droidboot.img, boot.img, system.img and recovery.img to go back to an older version. Not sure if this works as I unlocked bootloader when I had the chance.
If you can't then you might have to wait for the "Official" unlock tool but ASUS will know and you will be out of warranty.
ultramag69 said:
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Click to expand...
Click to collapse
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
kamranyusuf said:
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
Click to expand...
Click to collapse
VERY IMPORTANT - Make sure you have checked the MD5 checksum on the boot, droid_boot and recovery image files as these are definitely needed to boot phone. If these are corrupt then you can brick your phone... You have been warned...
Download firmware from here-http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
It is pre-rooted but the other files needed are included in the folder.
2. Put phone in fastboot mode and erased droid_boot.img, boot.img, recovery.img and system.img using command "fastboot erase (put choice here)"
3. Flash the files I just erased back on using fast boot - "
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
This got me the pre-rooted 2.13.40.13. As the supersu has been inserted it is fine to use OTA to update, just make sure you don't update supersu before the OTA flash.
Good luck....
And may you retain a strand or 3 of hair like Homer Simpson....
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.
hello every one,i have desire 816 w (a5 dug j__15)
the problem is that i have downloaded ota official android update( 5.0.2) but because of having custom recovery,i couldnt use it,i simply copy the zip file to pc then flashed the stock recovery and put the update zip file back to download folder(where it has been before) on phone storage,then rebooted the phone,but it does not find update and when i check for new software update it says you have to download it,(it is already placed on download folder on phone storage)what should i do to not to download 839MB again?
i also tried updating from stock recovery but it says failed to map file
i flashed twrp and tried installing zip but it has error too,i'm really confused
thanks
That's easy you need a handy file manager on your phone (I personally use ES file explorer); put the complete OTA.zip somewhere else first. then hit download update, after a couple of minutes turn off your Wifi and mobile data, the download will be paused. now simply delete the small file in your file manager and replace it with your own complete file (names will naturally be the same, so no problem there). then turn on your internet again, it will recognize the file and proceed with update without further download.
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.