Hey guys,
i just created this account because i'm really lost right now.
since 3 days i'm trying to flash a new version of cyanogenmod on my phone, but it always failed because of an TWRP error (error status 7).
it wasn't really a problem because i just flashed the working version(cm-11-20131222-Nightly-i9305) back on and everything was alright.
but now i accidentally deleted this version and the cyanogenmod site doesn't list it anymore.
i've been trying to install a new version on the phone with always the same error no matter which version i try.
after i looked it up here, i deleted the assert part in the updater-script. doesn't work either.
so i upgraded the TWRP to the current version via Odin because i read it could help.
and now it only saids:
set_metadata_recursive: some changes failed.
E: Error executing updater binary in zip <PATH>
Error flashing zip <PATH>
and i can only boot into the download or recovery mode now.
i hope anybody can help me with that. i also could offer the recovery.log from TWRP if it would help.
Wrong forum, i9305 has a specific section where you're most likely to receive an answer. Report your own post and ask a moderator to move it.
Usual advice is to flash a full stock rom using odin then start over, check the md5 of any downloads.
Spice Dream Uno android 5.1.1 official OTA link captured!!!
LINK:-
https://android.googleapis.com/pack...-spice-mi498h-LMY47V-from-LMY47O.a818932c.zip
Instructions:-
Make sure u are on Stock 5.1 (LMY47O) & u have stock recovery
Place the ota zip in sdcard
Reboot to stock recovery
select apply update from sdcard
TA_DA!! U have android 5.1.1 running on your phone.
Credits:-
@mukeshpurohit
status 7 error
I am rooted and having stock recovery stock rom but while installing getting status 7 error.What to do?
There is an option in supersu to perform full unroot and then try again ( remember stock LMY47O recovery is required )
ujwal.p said:
There is an option in supersu to perform full unroot and then try again ( remember stock LMY47O recovery is required )
Click to expand...
Click to collapse
try that too but not working
The only thing I can imagine is that system files have been modified... Otherwise it should work..
Sent from my Mi-498 using XDA Forums
Error
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
aditya_chachad said:
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
Click to expand...
Click to collapse
Hmmm, try after full unroot, if that also doesnt work. There is one more method mentioned by people in the group. ie First flash the stock 5.1(LMY47O) ota and then on top of that flash 5.1.1 OTA, it will work.
How to successfully update to 5.1.1
Hey
Thanks for the suggestion :good: I managed to install 5.1.1 on my device.
My findings:
Before Lollipop, while updating from an OTA update, Google made android only check the system partition details to verify their OTA updates and that the installed version was the correct one.
However, with 5.0 Lolipop they introduced a new method of system checking. For each OTA update, the updater in recovery checked the file in the /system/bin/install-recovery.sh for its legit data. So any rooting or messing with the kernel or any part of the system made changes to it.
If any of the data is wrong or changed, the updater generates an error which most of us are getting. You won't even be able to manually flash the image as the system does not grant access to any recovery to patch the zip.
Even just installing SuperSU will change the data. A full unroot wont work as unrooting dosen't set back the default value for the files!! Only chance is if you have the stock image. without any messing around.
Sadly, I am not a professional developer and I don't know why Google did so?
The method that I used:
I flashed a stock image from another Spice Dream Uno device that my Dad has (that's silly) and restored the original system files.
And VOILA!, my OTA works just fine and I am on 5.1.1 now!
Edit: The updater checks every file in /system folder !! So if u even modify a stock apk, it will give an error.
Please Hit "Thanks" if this information was helpful!
aditya_chachad said:
Hey
Thanks for the suggestion :good: I managed to install 5.1.1 on my device.
My findings:
Before Lollipop, while updating from an OTA update, Google made android only check the system partition details to verify their OTA updates and that the installed version was the correct one.
However, with 5.0 Lolipop they introduced a new method of system checking. For each OTA update, the updater in recovery checked the file in the /system/bin/install-recovery.sh for its legit data. So any rooting or messing with the kernel or any part of the system made changes to it.
If any of the data is wrong or changed, the updater generates an error which most of us are getting. You won't even be able to manually flash the image as the system does not grant access to any recovery to patch the zip.
Even just installing SuperSU will change the data. A full unroot wont work as unrooting dosen't set back the default value for the files!! Only chance is if you have the stock image. without any messing around.
Sadly, I am not a professional developer and I don't know why Google did so?
The method that I used:
I flashed a stock image from another Spice Dream Uno device that my Dad has (that's silly) and restored the original system files.
And VOILA!, my OTA works just fine and I am on 5.1.1 now!
Edit: The updater checks every file in /system folder !! So if u even modify a stock apk, it will give an error.
Please Hit "Thanks" if this information was helpful!
Click to expand...
Click to collapse
Can you give the link for the system file I think I'm gonna try ur step...post the link ASAP.✌✌✌✌✌
& tell me how did you restore the system either using custom recovery or stock.
or
can you backup the current 5.1.1 system and post the Link...✌✌✌✌
SathishKies said:
Can you give the link for the system file I think I'm gonna try ur step...post the link ASAP.
& tell me how did you restore the system either using custom recovery or stock.
or
can you backup the current 5.1.1 system and post the Link...
Click to expand...
Click to collapse
As I mentioned, I had my stock recovery and system image backed up. I used custom recovery to restore my stock system.
For the safer side, I did do a full unroot from SuoerSU, which u can find it in the settings of SuperSU.
One thing I prefer is I never flash a recovery directly to my device.
Whenever I need custom recovery ( I use TWRP btw), I open it by using
Code:
fastboot boot TWRP.img
or whatever your file name is.
I then restored my backup from TWRP. In your case if you didn't backup your system before rooting then try flashing the stock system images from the links below.
After flashing the stock system, your OTA should work just fine.
There are many other threads where u can find the stock images.
Link for 5.1.1 flashable.
http://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Link for Lollipop 5.1 stock image.
http://forum.xda-developers.com/cro...general/lmy47o-stock-rom-android-one-t3076777
If the stock images don't work for you then please tell me. I will backup my system and provide it.
I have yet another workaround way which is a bit complex. I'll post that too if this method didn't help you.
Hit Thanks if this helped you!!:good:
aditya_chachad said:
As I mentioned, I had my stock recovery and system image backed up. I used custom recovery to restore my stock system.
For the safer side, I did do a full unroot from SuoerSU, which u can find it in the settings of SuperSU.
One thing I prefer is I never flash a recovery directly to my device.
Whenever I need custom recovery ( I use TWRP btw), I open it by using
Code:
fastboot boot TWRP.img
or whatever your file name is.
I then restored my backup from TWRP. In your case if you didn't backup your system before rooting then try flashing the stock system images from the links below.
After flashing the stock system, your OTA should work just fine.
There are many other threads where u can find the stock images.
Link for 5.1.1 flashable.
http://forum.xda-developers.com/crossdevice-dev/android-one-general/rom-t3120737
Link for Lollipop 5.1 stock image.
http://forum.xda-developers.com/cro...general/lmy47o-stock-rom-android-one-t3076777
If the stock images don't work for you then please tell me. I will backup my system and provide it.
I have yet another workaround way which is a bit complex. I'll post that too if this method didn't help you.
Hit Thanks if this helped you!!:good:
Click to expand...
Click to collapse
Hey man I tried it but, seriously its going to bootloop. If you provide the system backup of current OS & if its not much of a trouble give it as a recovery restorable file the flashable zip is not workin out for me. I believe that ur posting the 5.1.1 backup plz post it... :fingers-crossed::fingers-crossed:
SathishKies said:
Hey man I tried it but, seriously its going to bootloop. If you provide the system backup of current OS & if its not much of a trouble give it as a recovery restorable file the flashable zip is not workin out for me. I believe that ur posting the 5.1.1 backup plz post it... :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Hey,
Sorry to hear that the previous method didn't work.
Your device is probably going into bootloop because of the remains of your previous system and the dalvik-cache. Try clearing that once.
I am providing you with both the system recoveries below.
Link for Lollipop 5.1 system backup:
https://goo.gl/NkAxwo
Link for Lollipop 5.1.1 system backup:
https://goo.gl/TL6EqU
Link for TWRP custom Recovery for Spice Dream Uno (sprout):
https://dl.twrp.me/sprout/twrp-2.8.6.0-sprout.img
These backups are directly from TWRP Recovery, so I don't know how you will use them.
You can't just copy these folders on your ext sd card and do a restore from TWRP as it won't recognize it as a system backup (as far as I know).
So basically, what I did was, I made a fool out of TWRP!!
You can follow these steps too.
First download the files from the required given links and place it in a new folder.
1. Start your device into TWRP cutom recovery.
2. Keep your device plugged in to a PC. Do not unplug your device until the whole restoration process completes!! And create a system backup of your device using TWRP. DO NOT use compression and DO NOT check md5. Do not reboot the device after the backup!!
3. After a successfull system backup, you will get a folder it your ext sd card mostly in ext_sdcard\TWRP\BACKUPS\Mi498HA14090161\<recovery_name>
4. Locate the folder on a PC and open it. There will be six files in the folder. Replace these files with the backup files that I provided you with in the download.
5. Now go to Restore option in TWRP and you will find the backup that you just created. The backup name will be the same but the system images will be changed as we just replaced the system and boot files.
6. Select the backup and restore.
Reboot your device after a successful backup and you should now have a fresh un-mod system.
You can directly use the 5.1.1 system image, but I suggest, you use the 5.1 system backup and update to 5.1.1 OTA.
And for the bootloop problem, I prefer backing-up the data of my device and do a complete system wipe. Wipe off the data, system partition and cache. This sholud set your device to a untouched state and hopefully there won't be any further problems.
Hit thanks if this helped you!! :good:
aditya_chachad said:
Hey,
Sorry to hear that the previous method didn't work.
Your device is probably going into bootloop because of the remains of your previous system and the dalvik-cache. Try clearing that once.
Click to expand...
Click to collapse
Everything worked as a dime if you backed up stock recovery that came with 5.1.1 post me tat took✌✌✌✌
SathishKies said:
Everything worked as a dime if you backed up stock recovery that came with 5.1.1 post me tat took
Click to expand...
Click to collapse
Feels good to help a fella!! :good: :good: :good:
How to update manually to Lollipop 5.1.1 for release key error and other errors
aditya_chachad said:
Hey
My device is rooted but it is on stock ROM and stock recovery.
I downloaded the flashable zip and placed it on my ext sd card and flashed it using TWRP Recovery.
When flashing, it shows an error E: error excuting updater binary in zip <zip_file_location>
I tried this over three times and it still shows the same error.
Please Help!!
Click to expand...
Click to collapse
Youtube Search for teckspotindia "Android One Release Key Error | Update Lollipop 5.1.1 Error | Micromax Canvas A1 | Dream UNO"
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
manojnagendra said:
I am rooted and having stock recovery stock rom but while installing getting status 7 error.What to do?
Click to expand...
Click to collapse
How to update manually to Lollipop 5.1.1 for release key error and other errors
Youtube Search for teckspotindia "Android One Release Key Error | Update Lollipop 5.1.1 Error | Micromax Canvas A1 | Dream UNO"
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
I wanted to enable OTG on my NMO-L31 . So i had to root it and thought if i wanted to go that far i could use a rom as well and tried installing EliteRom . I unlocked the bootloader installed a custom twrp recovery by EliteRom ' s author and flashed it . Surprisingly any kind of audio playback doesn't work and now i want to go back . But i couldn't do it well and now stuck with EliteRom . I only have a full backup of my EliteRom and can only recover it using twrp .
To get the stock firmware i searched forums and found Huawei Firmware Finder , Huawei Update.app Extractor and Huwaei Multi Tool . There was numerous results with NMO-L31 so i had to find my region . The naming scheme was clear and after looking into available languages of changelogs for each firmware i detected my region.My plan was to get boot.img , system.img , cust.img and recovery.img . I couldnt find a cust.img and downloaded all firmwares of my locale overnight . I extracted everything they had and lastly found two cust.img to use . Here is the list :
NMO-L31C10B140
NMO-L31C10B140 OTA-Mf
NMO-L31C10B152
NMO-L31C10B351
NMO-L31C10B351 FullOTA-MF-PV
NMO-L31C10B355
NMO-L31C10B355 FullOTA-MF-PV
NMO-L31C10B357
I dont know meaning of MF or PV.
To use the unbrick opinion from Multi Kit i used :
system.img and boot.img of latest FullOta
EliteRom's custom TWRP as recovery.img
and used both cust.img seperatly in two seperate cases
But in both combinations the phone booted Android to show a encryption error and demanded me to factory reset and kicked me back to TWRP . TWRP has no factory reset opinion and i am afraid to flash original recovery.img to keep TWRP/my backup . If i flash stock recovery and the threre isn't a factory reset opinion there i cant flash anything again . I don't know a way to open up fastboot without pairing adb and adb pairing only happens when phone boots to Android . Maybe there is a way that i am not aware of.
Long story short i want to go back to stock rom and have handful of system,boot,recovery,cust images . I dont know which combination to use. I don't even know if it will work out or show that encryption error again . I don;t know if i can flash back twrp after flashing stock recovery . That would be the worst because i only have one backup and can only recover it from twrp . And i dont know if i have to format /data to ext4 before attempting to flash images . Wouldn't flashing an image handle filesystem releated parts of memory ?
What would be the best way out of this ? Can anyone with more experience help me ? Thanks in advance .
After some reading i used the unbrick method and selected originial recovery the log said it "Error! You are trying to flash the wrong image! " when trying to flash cust.img but said "All images are flashed succesfully" . Weirdly now phone booted to android and after getting the encryption error booted back to now stock recovery and did a factory reset . After booting back to Android i am surprised once again. I still have ElitreRom and everything is the same from model number to my home screen . What even happened ? :crying:
Shouldnt flashing the big system.img have solved everyting ? I thought it had everyting needed to bring back stock apps since it was the main file and the largest.
And now i have tried going with dload method . I put the big update.app file to dload folder on sd card and tried to force update with vol up + vol down + power button method . It failed at %5 saying
"Software install failed!"
"Incompatibility with current verison. Please download the correct update package"
Does it check the build and model number before installing anything ? They are still incorrect because EliteRom
Hi all. I was wondering if someone can help we with my XT1095. I've managed to unlock the bootloader. However I cannot flash any version of twrp recovery (victora or clark) to the recovery partition (keep getting a size mismatch error).
Additionally I can only fastboot boot 2.8.5.0 twrp victora version. This version does not allow me to install either lineageos 15 or 16 variants (I get an error when trying to install). Any help would be appreciated.!
My title was incorrect. I meant "Can't boot into recovery"
I figured this out so posting this here in case someone else wants to do this.
First off, it looks like TWRP doesn't work necessarily for the Moto X XT1095 (stupidly called the Pure version in the US - talk about confusing). I tried everyone to 3.3.1.0 and only 3.0.2.0 and 2.8.5.0 and below work. I used 3.0.2.0.
When trying to flash the ROM, the updater script can't read what type of device the thing is. So that sucks because it fails the zip install immediately. To get around this, I found this link that details modifying the updater-script to delete the check. You then need to zip up the contents of the exploded zip (do NOT zip up a parent folder containing the contents), and then wipe cache/system and finally install the zip. Got it to work! Took 2 days. Bleh.
Edit: I could never flash the recovery so I instead used fastboot boot twrp...img