Database Develop

[OTA CAPTURED][5.1.1]Spice Dream Uno official OTA link captured

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"

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

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

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

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

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

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

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

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

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

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

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

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

Pretty useful. Thanks

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

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

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

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

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

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

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

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

[RECOVERY] [UNOFFICIAL] TWRP_3.0_m86_patched_st0rm77

** BRICK WARNING/Disclaimer/Requirements **
>> Only flash with unlocked bootloader <<
>> Scripts are released under GPlv2 license <<
>> Run at own risk <<
Hi,
I patched the TWRP 3.0 recovery from faust93 to include important partitions
that make switching between different versions of Android/Ubuntu very simple.
All partitions are properly added to the fstab, but out of fear that some of
you will brick your device i disabled most of them.
Next version will contain a backup of all unique partitions, but i will have
to test this thoroughly.
Steps to install:
1. Download the zip file from attachments below
2. Unpack the zip file
3. Check checksum with md5sum -c *.md5
4. Put phone into fastboot mode (boot device with [vol-] and [power] button)
5. Flash recovery with:
# fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img
# fastboot reboot
then boot the device with [vol+] and [power] button, to enter recovery
[Requested by @p82maarj]
Already on an older TWRP version ?
- Flash "update_TWRP_3.0_m86_patched_st0rm77.zip" from TWRP
or
- Unpack the zip and flash the recovery manually in TWRP by selecting "install image"
Enjoy
Warning:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **

Hi @st0rm77
Thanks for your contrubution!
It will be good if you create a flashable zip of your new recovery. It can be flashed directly from the stock recovery or from the other twrp recovery without entering in fastboot.
Furthermore to have a flashable zip is usefull to flash a new rom update. For updating the new rom version I enter in TWRP, flash rom zip, flash unlocked bootloader zip and flash TWRP zip.
I attach the other flashable TWRP zip you can based on (only replace recovery.img by your recovery.img).

Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)

Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?

PYCON said:
Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?
Click to expand...
Click to collapse
Yeah, you get some extra abilities:
- Backup of Boot Logo
- Backup of Device Tree
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.

Thanks for everything you've been releasing, great work!

st0rm77 said:
Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)
Click to expand...
Click to collapse
Done Thanks!

st0rm77 said:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **
Click to expand...
Click to collapse
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!

Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?

PYCON said:
Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?
Click to expand...
Click to collapse
I know the answer to this one!
The first zip contains the img file that you can flash using fastboot.
The second (update) zip is the one you need if you already have (an older) TWRP and you wish to update to this version (use it from inside TWRP).

abePdIta said:
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!
Click to expand...
Click to collapse
boot.img is your boot partition, you need this one :good: (NEEDED)
bootloader is the locked bootloader from meizu, avoid this one as the plague (AVOID)
Dont brick your device, check everything carefully :fingers-crossed:

st0rm77 said:
Dont brick your device, check everything carefully :fingers-crossed:
Click to expand...
Click to collapse
Thank you very much! I will be careful in the future, I promise!

i follow the a to I tutorial
then unlock bootloader
then this
now when i conect meizu to pc i try to pass custom rom to internal memory and the phone restart
what is the problem
---------- Post added at 10:35 PM ---------- Previous post was at 09:56 PM ----------
managed to download the rom in phone browser now i have RR and all it´s ok

I flash stock recovery ( use update 5.1.10.0g) but not success, híc híc, help me restore stock recovery, many thanks!!!!

st0rm77 said:
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.
Click to expand...
Click to collapse
Just to be sure I understood :
Going from Flyme to CM :
-Backup Flyme (system+data+dtd)
-Flash CM archive
Going back to Flyme
-(optional) Backup CM (system+data+dtd)
-Restore Flyme (system+data+dtd)
Is there is a quikier way ?

TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:

help
hi .i change meizu pro 5 from china to national (5.6.1.19 daily )and unlock it and flash recover TWRP 3.0 but not login it the recovery .
i want updated

PYCON said:
TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:
Click to expand...
Click to collapse
I too vote for a port!

3.1.1 was released

munky-head said:
3.1.1 was released
Click to expand...
Click to collapse
Not for PRO5

[ROM] [STOCK] [08-Mar] TWRP flashable Stock ROM [v340]

Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues.
If already on Stock Rom then visit THIS THREAD for OTA updates.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - TWRP_Stock_v340.zip from this post.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
Users coming from Android Pie reported microphone issues - in case you face it then flash DolbyPlus-Oreo_8.1.zip from THIS post via Magisk which might resolve the issue.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.

To ROOT the ROM
Flash Magisk from TWRP and you will have root access

Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......

piku2008 said:
Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......
Click to expand...
Click to collapse
Did you performed factory reset and flashed ROM & decrypt.zip
The TWRP survives the flash and Magisk can be flashed to Root the ROM but after above two files are flashed.

Well I successfully flashed ROM after complete factory reset with internal memory tooo ......
But some how TWRP got replaced with factory default (the one with root checker) with bootloader unlocked screen

Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available

Aftab_khatri said:
Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available
Click to expand...
Click to collapse
Will do

Thank You bro.. Your Guide has tested successfully from AOSiP build to stock ROM 309.. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app

AOSP to Stock
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...

jroviel18 said:
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...
Click to expand...
Click to collapse
Great .. Sorry could not reply earlier but you got the resolution of the query.
For subseqeunt update with TWRP intact .. please follow this guide in future .. https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269

Update - WW-15.2016.1805.311
Updated Stock ROM file - TWRP_Stock_v311.zip now avaliable.
For those who are already on stock ROM,
The instructions to flash are in THIS POST.
For those who are on custom ROM,
The instruction to flash are in THIS POST

Do these zips format internal storage or not ??

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
No

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
I believe this is the exact same firmware as the official one. It is just modified to work with TWRP. Nothing more, nothing less.

aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
You will have to format data (i.e. factory reset) but the Internal Storage will be safe.

aaa
Work For Max Pro M1 ?
This rom XOOT not XOOTD
---------- Post added at 11:26 AM ---------- Previous post was at 11:07 AM ----------
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - Stock_X00T_Patch_May_Version_311_TWRP.zip.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
This will update your firmware to WW-15.2016.1805.311 to have updates after this follow THIS THREAD.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english

arielrizuly said:
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english
Click to expand...
Click to collapse
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.

.A.V.i.n.a.S.h. said:
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.
Click to expand...
Click to collapse
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.

Abby 244 said:
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.
Click to expand...
Click to collapse
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.

.A.V.i.n.a.S.h. said:
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.
Click to expand...
Click to collapse
No response even in fastboot.

[GUIDE] Back to stock ROM howto / Downgrade howto

There maybe a number of reasons to go back to the stock ROM. We do not discuss them here
But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? Here is super quick howto guide. There are other possible ways and sequences to perform the task, but the one listed below is tested.
The same procedure applys for a case when you want to downgrade you phone (when its bootloader unlocked). Say, current custom ROMs are based on ColorOS 6.1/Android 9 vendor contents but you have realmeUI/Android 10 already. In order to try one of those custom ROMs you should downgrade to the latest Android 9 stock firmware first.
The essential part of the customized phone is custom recovery. Currently Realme OZIP file does not contain stock recovery inside. It is being generated as explained below, in the post #2, see EDIT3. It means you need to find somewere PROPER stock recovery corresponding to your ROM to put it back. See Realme X2 stock recovery links below, post #2, EDIT4.
Which stock recovery to use? The one for your model and which version is not newer than the ROM version you are flashing. For example, you need A.17 stock ROM for CN model (RMX1991). Then any recovery of A.12, A.14, A.16, A.17 for RMX1991 will work for you.
Download and unzip the stock recovery partition image from the next post, this will be a file like rmx1991-sde20-stock_recovery.img.
Download stock ROM ozip file (for example, from here). Put it to a SD card with a filesystem which supports files more than 2GB (ext4 works fine. Stock recovery, but not ColorOS, supports it). Put the SD card into the phone.
Start (reboot) phone into fastboot mode
From a computer perform fastboot flash recovery rmx1991-sde20-stock_recovery.img
From the fastboot mode by means of volume buttons select 'Recovery mode' and push Power button
From the stock recovery select language needed (there are three only), then 'Install from storage device', then 'From SD card', tap the OZIP file with your ROM
When the update process is done, phone reboots. Most likely, it will not be able to boot normally because you need to wipe out data. Either help the phone with keeping Vol Down button pressed during reboot, or it will boot recovery by itself. Now wipe data (confirm by entering random 4-digit code), select 'Format data'. Phone will reboot
Here it is. Enjoy (or sell your Realme X2 with its shiny stock experience...
If you want to lock bootloader after all above mentioned steps (you have to make them all unless you wanna get a brick ), boot fastboot mode, perform fastboot flashing lock. This will wipe your data again. Then optionally lock 'OEM Unlock' option in 'Developer Options'. Even further, you can install In-DepthTest.apk and sign out from In-Depth Test program.
2022-12-25 EDIT: For downgrade from Android 11 to 10 read this post

I have found out that in fact stock recovery does not exist as a prebuilt file It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p
It means in theory you can recreate stock recovery having only Realme ozip file.
EDIT1 The command to do it in Linux shell is
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
Cool! Tested.
EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.
EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.
EDIT4 In order to combine everything in one place:
Stock recoveries for RMX1991 (China version): here
Stock recoveries for RMX1992 (India version): here
Stock recoveries for RMX1993 (Euro version): here
EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.
EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).

So this method works if you brick your phone trying to install a global rom to china variant..

Hi,
does only works with SDcard insert.
Because the internal storage is decrypted.
And it does not work on X2.
But why?
Installation failed?

This method will bring back my FP working again right?

Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/

SkyeJace said:
This method will bring back my FP working again right?
Click to expand...
Click to collapse
You have to lock bootloader for this. See the very last part of the howto, post #1

AldRezaine said:
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
Click to expand...
Click to collapse
The site provides generalized instructions for everything
As for Realme X2, there are two methods claimed, one is for ozip file, another for ofp file; last one is not yet publicly available somewhere (the link is replaced by the Coming soon promise).
If you find there something certain regarding ozip procedure for Realme X2, give me the link, please. I couldn't

why I back to stock rom, apps i uninstalled it is don't auto reinstall?

hello guys, how can i get the 1993ex stock recovery? i screwd up big time !

hammerheading said:
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
Click to expand...
Click to collapse
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it

BaDuc said:
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
Click to expand...
Click to collapse
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.

yakovpol said:
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
Click to expand...
Click to collapse
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).

yakovpol said:
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
Click to expand...
Click to collapse
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?

hammerheading said:
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
Click to expand...
Click to collapse
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.

BaDuc said:
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
Click to expand...
Click to collapse
Those I have are uploaded to here.

yakovpol said:
Those I have are uploaded to here.
Click to expand...
Click to collapse
thanks you very much

yakovpol said:
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
Click to expand...
Click to collapse
Thank you so much, that did the trick!! i was able to flash the a17 and the phone is working fine now . But i'm not trully satisfied, i can't find a away to flash a GSI rom successfully, but that's another topic ... Thank you again and keep up the good work !

can u plsss provide stock recovery for realme x2 rmx1992, i bricked my phone trying to install stock os since 2 days, cant find a way..if some has the recovery pls provide it. im able to boot to twrp, bootloader is unloced and with the other recoveries im not able to intsall the stock rom.pls help.

Can send me 1992 stcok recovery file ozip please.