Hi,
My orange EE UK phone is on version Android 4.2.2 ,It is rooted etc with clockworkmod installed I have a update to 4.3, this won't install and have been told that I should flash back stock recovery .
I downloaded the 4.3 OTA file and copied the file onto my laptop from my phone.
I have read somewhere the within the 4.3 Zip file there is the stock recovery file that I need , is this true ?? if so where in the zip file will I find the recovery file.
If when I get the stock recovery file will I be able to flash it with the software (One_M7_All-In-One_Kit_v1.0 ) if not what software would I need to download.
I hope I've made my self quite clear and hope somebody can help me.
Take care everybody and thanks for all your help over the years
topbanana4 said:
Hi,
My orange EE UK phone is on version Android 4.2.2 ,It is rooted etc with clockworkmod installed I have a update to 4.3, this won't install and have been told that I should flash back stock recovery .
I downloaded the 4.3 OTA file and copied the file onto my laptop from my phone.
I have read somewhere the within the 4.3 Zip file there is the stock recovery file that I need , is this true ?? if so where in the zip file will I find the recovery file.
If when I get the stock recovery file will I be able to flash it with the software (One_M7_All-In-One_Kit_v1.0 ) if not what software would I need to download.
I hope I've made my self quite clear and hope somebody can help me.
Take care everybody and thanks for all your help over the years
Click to expand...
Click to collapse
You will need the stock recovery from your 4.2.2 version, not the 4.3. If you have that ruu you can extract from the firmware folder. If you don't have, try this link. Be sure to get the version for your current OS ie: 3.x.x.x
http://forum.xda-developers.com/showthread.php?t=2545227
The toolkit should work for you but select your recovery , or just use adb directly (fastboot flash recovery recovery.img)
my version is 2.24.61.1
I cant find this version anywhere
topbanana4 said:
my version is 2.24.61.1
I cant find this version anywhere
Click to expand...
Click to collapse
I think any recovery from a 2.24.xxx.x will work, but wait and see if someone else comments.
the recovery from this zip, would likely work. I used a Telus one for my Rogers device.
http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
I flashed 5.0 ages ago since I live in NZ and I heard that I can get the official version now so I need to return to stock somehow so I can install the latest update, so does anyone have a stock rom or a method to return to stock and still be able to receive the updates
See any response by the forum member "reefuge" - his signature contains a stock ROM link.
For example, in my thread http://forum.xda-developers.com/moto-g-2014/help/xt1068-ota-lollipop-update-failing-t3035150
try to flash the rom via fastboot, using the commands on 4.2 on this thread
You need a XML zip of the rom , to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download is very slow, here a mirror but the mirror is incomplete.
download, unzip, to the some folder of mfastboot and give the commands a try, while the phone is conected via USB to the PC in the bootloader screen, you must have motorola driver update, to know if you have the drivers, just plug the phone on normal on mode, and see if you can copy and past files to the phone...
If you follow this procedure you will erase everything on the phone, so do a backup...
To receved a OTA update, you will need to have everything on stock so no root no custom recovery, the bootloader state don't matter. :fingers-crossed: :good:
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
Hello,
english powered by google
I desperately my Xperia SP on Android is trying to switch 4.4. Unfortunately, most Totourials are useless, alone because very often missing files or they are just out of date.
After so many problems I managed to flash my Xperia. Unfortunately nothing had the desired effect due to the files.
Currently I have the following problem which I do not get resolved:
I have loaded with the Flash tool the Cyanogenmod bootfile via fastboot, earlier I had installed CWM course with USB debugging and deactivated Bootlock. ect.
Unfortunately, he did not start the CWM but the CyanogenMod and I did not have the possibility to install the ZIP file on the SD card. Instead, I've obviously just all deleted.
Currently I have no system, but only the CyanogenMod. A flash on Standart is suddenly no longer possible FAILED (remote: Download size too large). Even when I extracted the System.sin I had problems to start them in fastboot mode.
I had previously done with older files, unfortunately the installation was on the ZIP file in recovery mode error. Why I have updated the files and all programs.
Restoring the standard firmware previously ran flawlessly ...
So I really do not go on and am really desperate.
I very much hope that my one helps the more clueless than me.
Best regards,
Ben
So i assume you now have installed official sony firmware? If yes , and you have unlocked bootloader then all you have to do is install twrp recovery(TWRP recovery for Xperia SP), then download Custom rom(i.e Cyanogenmod-Cyanogenmod builds for Xperia SP), if you like also google apps(OpenGapps) and install trough recovery. It might seem difficult, i know i did not explain it very good but its late... If you have any question or you want me to write a tutorial how to install cyanogenmod step by step just tell me.
Edit: even if you cant access the system it will be easy to install cyanogenmod
Problem Solved:
Flashtool was the Problem. I used the newest Version. After a Downgrade to 9.8.16 it worked.
Thank You very much
Hey guys,
I was trying to unlock my phone and install a custom ROM so I installed TWRP and everything was going smooth until I tried installing a custom ROM. In TWRP I hit "Install" and click the zip file for the ROM I want (PureNexus) and it says "Invalid zip file format! Error installing zip file '/sdcard/PureNexus.zip"
Does anyone know what the problem is? I can't figure this out. This is the first time I'm doing anything from the bootloader so I'm a bit of a newb. I would be fine going back to stock everything if it means my phone will turn on. I tried installing the official image from google (7.1.1) and I get the same zip error.
So where I'm at is I do not have an OS installed on but I do have access to TWRP. In the command prompt on my desktop it recognizes my phone when I type 'adb devices' but it doesn't do anything when I type 'fastboot devices'.
Any help is greatly appreciated. I'm scared.
Okay, so I figured out what fastboot was and I was able to install Google's 7.1.1 stock image using the command prompt. I was freaking out for a few hours and even though I didn't get the custom ROM I wanted I'm really happy I didn't brick my phone. I've never done anything like this on my phone so it was a fun learning experience
I'm still curious what I did wrong and why TWRP couldn't unzip any of the zip files (PureNexus, Google Stock, etc). If anyone knows I'm still interested in learning what I did wrong.
Unheard7 said:
... why TWRP couldn't unzip any of the zip files (PureNexus, Google Stock, etc).....
Click to expand...
Click to collapse
TWRP: wrong version or damaged;
ZIP: damaged or incomplete download.
Latest version TWRP is 3.2.1.0.
NLBeev said:
TWRP: wrong version or damaged;
ZIP: damaged or incomplete download.
Latest version TWRP is 3.2.1.0.
Click to expand...
Click to collapse
Yes, and the Google factory image isn't meant to be flashed that way. I guess the Google OTA image might be flashed from TWRP, but I haven't tried it.
TWRP will flash an image (. img) file if you set it to by tapping the img button. If you don't have that set and try to flash an image it will error. If you have it set to img and try to flash a zip it will also error.
1. Unlock the bootloader.
2. Install the latest TWRP recovery.
3. Wipe.
4. Install the required ROM.
To go back to stock firmware, just download the relevant factory firmware zip, extract it and run the script. I think a readme file is provided in the zip explaining how to go about it.
Cheers! Happy New Year!