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
Related
First of all I just bought Global Moto G 2014 (XT1063) from US Amazon and that was KXH21.85-23 (not updatable to Lollipop via shared OTA.)
So I did manage to unlocked the bootloader and flashed KXH21.85-17 and tried to flash the "Blur_Version.21.11.17.titan_retuglb.retuglb.en.US" which supposed to flash the Lollipop.
Unfortunately at first it failed to update me because "Printspooler.apk" mismatch the hash check. After attempt to flash (yes, I ignore the abort message and redo the process, It passed.... I don't know why) and stuck at some "xxx.apk" mismatch the hash again. After redo the process and bypass (for unknown reason that redo bypass the mismatch) I stuck at "velvet.apk" mismatch and this time It won't let me bypass and keep going on update to lollipop.
In my theory, Is it possible that I flash KXH21.85-17 from other country? Yes, any XT1063 (latin american, whereever on earth) supposed to flashable, but maybe the different country has slightly different apk. So that's why I failed the hash check.
Can anyone give me a URL or mirror to USA XT1063 for KXH21.85-17 that confirmed updatable to Lollipop? Since SBF-Dev and MotoFirmware is now down I couldn't find any.
I know what I'm saying is sound ridiculous, but I have no other theory that support my conspiracy anymore.
Hi @bankkung, I was facing similar problems. First you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Lamech242 said:
Hi @bankkungFirst you'd want to get back to stock kitkat which is up-gradable to Lollipop, so I would suggest downloading this file, http://180upload.com/bzl3ah1wov5g, which is 21.85-17, you can flash this file with fastboot by following this guide http://forum.xda-developers.com/moto-g-2014/general/index-guide-update-to-lollipop-android-t2941340. Next you'd want to download both Lollipop files, the first and second one. (The second one is the newest update that fixes memory management). First file: https://mega.co.nz/#!UoQ02KLQ!22OUNBctGLoAUOMd_frTRT9jgbB3tRPUa4pPqfesGho.. Second file: https://mega.co.nz/#!s8ZSVJDA!SqUWPZODvM4-GYuXo6MC2JWTmpE9_jdyqlH-ycWi78I. Download both of those files and put them somewhere accessible (like your SD card) so you can flash these in stock recovery, so after you downgrade to kitkat you can flash the first one, then boot up and then go back into stock recovery and flash the second file. I'd recommend factory resetting your phone after this to smoothen everything out.
Click to expand...
Click to collapse
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
Lamech242 said:
If all else fails you can flash TWRP recovery using this guide http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165, and then download this TWRP backup of the latest Lollipop, and place it in /data/media/0/TWRP/backups/(your device name here). All of that can be done right in TWRP recovery using the file manager (no need to root your phone). https://mega.co.nz/#!59AAiQaR!cPUsNpI5j-ZaIMX10uiS93EJqpLxua-iwKHj30InX1U
I would really recommend the first option tho, just in case any other updates come you can easily upgrade your phone.
Hope I helped!
Click to expand...
Click to collapse
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
bankkung said:
Hi Thanks for your help
I've done that several time and still having the same problem (yes, mine is unlocked bootloader and flashed-reflashed that 21.85-17 over twenty time right now)
I'm thinking about getting some Nandroid backup (never used TWRP before but I think this methond you gave is the same thing as I think) to get straight from Custom Recovery to Lollipop.
So what I need to do in the 2nd method is
a
flash TWRP
Place TWRP Backup of XT1063 Lollipop
restore
reflash Stock Recovery + Locked recovery
Is this sound corrected?
Click to expand...
Click to collapse
Yes once you place the backup on your SD card, flash TWRP, reboot into recovery and go to advanced then go to file manager, then finish following the instructions above. Once you place it in the right place then you restore it. As of the stock recovery issue, it wouldn't make much sense to do that unless you followed the first option, where the stock recovery would actually be needed. But if you find a recovery image then yeah. If you do the second method you won't be able to receive updates nor update it manually unless doing the first method.. But the TWRP backup is the latest lollipop so enjoy!
If you still need help you can just flash TWRP recovery, and download this and flash it. http://forum.xda-developers.com/mot...-stock-rom-t2970427/post57438355#post57438355
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"
Android One Universal STOCK ROMs [MM/LP]
These ROMs were dumped using the command "dd", 100% Stock without any modification.. These roms were put together for users who wants to fall back to google stock rom, And also for users who are having issues while installing the latest OTA. Nothing is removed from the original rom, and all signatures are intact. And Lastly, please take the time to read the instructions, FAQ, carefully and thoroughly before proceeding....
List of devices with known compatability
Code:
[CENTER][SIZE="4"]Cherry Mobile One G1 (Philippines)
General Mobile 4G (Turkey)
I-Mobile IQ II (Thailand)[/SIZE][/CENTER]
DOWNLOAD
[ AFH | DRIVE ]
FLASHING PROCEDURE :
Download the ROM
Move the file to internal storage
Reboot to TWRP custom recovery
Backup your current ROM (just in case)
Locate the file and install
Reboot and have patience while it boots up... It will take about 15-20 minutes
In case you want to fall back to stock recovery, ensure that "MOUNT SYSTEM PARTITION READ-ONLY" is enabled from the twrp MOUNT section prior to installation, otherwise uncheck it
Click to expand...
Click to collapse
FASTBOOT METHOD
Extract all the images to adb folder and ensure that USB Debugging is enabled.
Code:
#! adb reboot bootloader
#! fastboot flash system system.img
#! fastboot flash boot boot.img
#! fastboot flash modem radio-modem.img (For Marshmallow MRA58Y Rom only)
#! fastboot reboot
Frequently Asked Questions :
1. Is it compatible with my device?
Yes, as long as you are using an Android One 2nd generation [seed] with a qcom 410 processor (msm8916).
2. Will I still be able to recieve the official OTA updates in the near future?
Yes, as long as you've never rooted, changed recovery, or any other modification on your system.
In case you have rooted your device, all you have to do is reflash the ROM when a new ota arrives and you'll be fine
3. Do I need to Wipe my Data and cache partitions before attempting to install the ROM?
No, but it is recommended especially if you are having too many apps FCs
If you are having apps FCs, try clearing the app data of the affected app, or try hard reset.
If all else fail, do a clean install.
4. Got stuck with "Patching system image unconditionally"?
It might be a bad download
Always verify the hash prior to proceeding (check the howto verify the MD5sum below)
Wipe the system partition just in case
MD5 Signature
How to Verify the MD5 signature?
If you are running Windows just download HashTabs and install. Right click on the downloaded file then click properties and look for "FILE HASHES" tab, verify if md5 hash are the same. On unix based system just execute this line in the terminal "md5sum SPROUT4-STOCK-ROM-LMY47V.zip". On your phone, just use ES explorer and then click properties then tap "Show Checksum" then compare the md5 hash. If the file hashes are identical you are good to go, Otherwise, redownload the file again due to bad probably.
[MRA58Y] efa811732dd54ccdbe73a4cb8bdb085c
[LUZ56M] 5a58c232a6e5667c123236175a070a7e
Flash at your own risk :good:
MISC
Code:
[CENTER][URL="https://goo.gl/j7F8Mz"]DRIVE[/URL][/CENTER]
reserved 2
reserved 3
Thanks a lot for this. I will test it now and will let you know.
kiksilog said:
Thanks a lot for this. I will test it now and will let you know.
Click to expand...
Click to collapse
:good: :highfive:
General Mobile 4G Dual
1cefire said:
:good: :highfive:
Click to expand...
Click to collapse
General Mobile 4G Dual support?
My G1 is now running Marshmallow. It did took awhile on the boot screen but other than that :good:
Thanks again!
kiksilog said:
My G1 is now running Marshmallow. It did took awhile on the boot screen but other than that :good:
Thanks again!
Click to expand...
Click to collapse
Rom files is'nt enough folders, not even as work general mobile 4g , I have already My work is turkish forums . he doesn't come back lolipop
Anyone has the stock rom for lava pixel v1 (2nd gen android one)??india
JaxaPRO said:
General Mobile 4G Dual support?
Click to expand...
Click to collapse
Yes
kaankulahli said:
Rom files is'nt enough folders, not even as work general mobile 4g , I have already My work is turkish forums . he doesn't come back lolipop
Click to expand...
Click to collapse
Although we had different Lollipop rom build no., our device and roms are basically the same. Since Android M arrived we all share the same build numbers. How did I know this? By verifying the MRA58Y ota and comparing all the hashes including the radio-modem.img I found out we all share the same Android M stock rom. And lastly, the MRA58M ota will not touch any other partition other than the system, boot and modem, so basically, all you need is the system.img, boot.img and radio.modem.img to be able to update to Android M. The rest of the partitions are useless when it comes to updates
sourav4ganguly said:
Anyone has the stock rom for lava pixel v1 (2nd gen android one)??india
Click to expand...
Click to collapse
Sorry dude, I cant provide you the stock rom for Lava Pixel v1 since I dont own the device.
@1cefire
Can your TWRP files found here
androidfilehost dot com/?w=files&flid=43419
be used to root Marshmallow?
if yes, which one to use? (i.e. blue, classic, darkplay)
thanks.
@kiksilog
Any recovery will do as long as it runs on this device. Unfortunately, Marshmallow requires a permissive kernel, so far no one has manage to build an insecure kernel for seed without any issue. Even the latest beta supersu with a modded sepolicy boot.img failed to boot. Android M for seed is unrootable for now, hopefully supersu will get an update to support our latest OS
Oi
Android Marshmallow 6.0.1!!!
In case someone might consider upgrading to Android M 6.0.1 MMB29K
- install it via custom recovery philz / twrp / fastboot (visit the first page for more info)
- the rom contains system.img and boot.img only (the only partitions required to upgrade)
- the rest of the partitions were removed and will be provided separately for each device
Huge thanks to @dabotsonline for the link
How about posting the download url of the OTA update 6.0.1 file which I understand is only less than 90 mb? Thanks.. :fingers-crossed:
1cefire said:
Android Marshmallow 6.0.1!!!
In case someone might consider upgrading to Android M 6.0.1 MMB29K
- install it via custom recovery philz / twrp / fastboot (visit the first page for more info)
- the rom contains system.img and boot.img only (the only partitions required to upgrade)
- the rest of the partitions were removed and will be provided separately for each device
Huge thanks to @dabotsonline for the link
Click to expand...
Click to collapse
Wow, very helpful (Y)
1cefire said:
Android Marshmallow 6.0.1!!!
In case someone might consider upgrading to Android M 6.0.1 MMB29K
- install it via custom recovery philz / twrp / fastboot (visit the first page for more info)
- the rom contains system.img and boot.img only (the only partitions required to upgrade)
- the rest of the partitions were removed and will be provided separately for each device
Huge thanks to @dabotsonline for the link
Click to expand...
Click to collapse
are you a time traveler?
Yeah everybody. We already made it before google ????.
Wileyfox Swift cihazımdan Tapatalk kullanılarak gönderildi
@1cefire can i install it in aq4501???
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
1. Read the build information in the OP of the thread, it mentions all the differences.
2. It's the full stock FW but recovery flashable instead of fastboot and also rooted.
3. You would need to fastboot stock FW and manually root or flash the recovery flashable stock FW the was mentioned in question no. 2.
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
duba500 said:
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 Read this to get a better idea what to do.
duba500 said:
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
Click to expand...
Click to collapse
1)Differences would be that SuperSu is installed, busybox is installed, encryption is disabled in the kernel, important gapps such as google play services and the play store are updated to their newest current version so when you install the rom google services immediately work without needing to wait for a background update, gapps that can be fully functional by just downloading them from google play store (google+, youtube, google drive, etc) were removed from /system likely to save space to make it easier to install mods such as guitardedhero's viper/dolby sound mod, vanilla android's gallery photos app was added in place of google photos app, the little android debugging notification is hidden, and the tethering check was disabled to allow for tethering without a tethering plan.
2) The updated recovery flashable line is referring to the fact that the dev updated the google apps in the rom.
3) If you wanted to go totally stock then you'd need to just flash the boot.img and system.img out of a factory image from google since the rom is very very close to stock a userdata wipe shouldn't be needed and a cache/dalvik wipe may or may not be but as always have a backup in TWRP. Then go into TWRP before booting and install the latest SuperSu (2.65 iirc right now) installing the newest SuperSu's can cause a bootloop or 2 (in the middle of booting the phone will go back to the Google logo and booting again, it will usually do this 1 or 2 times before properly booting). (if you boot to android before going to TWRP it will be replaced since you have an untouched /system after flashing the system.img). And if you allow TWRP to keep /system as read only (it'll popup when you first boot into TWRP asking if you want to do that) then the stock /system will replace TWRP with stock recovery and OTA's will work if you do a total unroot from within the SuperSU app.
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download the factory image and just extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersyood it right?
Thanks for your advice-tip of the SuperSu version!
P.S:
LG doesnt have a dev site such as Google's have with all the Factory Firmwares?
Can I trust site such as: lgg3root. com/lg-g3-stock-factory-firmware
???
duba500 said:
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download G3 LS990 32GB and extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersood it right?
Click to expand...
Click to collapse
You have got a fantastic tip in looking here: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Search for fastboot.
It installed on top of any firmware (except firmware with the build date is higher than installed)(but you can edit updater-script). It can be installed through TWRP. Do not check the current state of the system. Installed without resetting.
https://developers.google.com/android/nexus/ota
what happens to root and xposed after installing them ? and currently i'm on MMB29K can i download MOB30H directly ? also do i lose any data in the process ?
xxqxpxx said:
what happens to root and xposed after installing them ? and currently i'm on MMB29K can i download MOB30H directly ? also do i lose any data in the process ?
Click to expand...
Click to collapse
Just downloaded this and unzipped it, but have not tried it yet. Looks like you just flash in recovery, so you should just be able to flash xposed and supersu after the zip. Only a system file in the ota zip, no userdata so you should be fine to upgrade. As always, back up first
You flash these using adb sideload as you would any other OTA zip. This are just official links from Google as opposed to us having to capture them and post in the OTA thread
EDIT: I would appear to be wrong. Although these are called 'OTA' there are full ROMs, and not incremental updates, that can be flashed via adb sideload as opposed to fastboot images. MUCH better if you don't wanna wipe the phone if you have a locked bootloader
One can't flash these with systemless root right (or modified system)?!