Database Develop

[Q] CM nightlys fail, used to work???

i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman

TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'

blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4

i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!

Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk

Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!

Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)

Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk

luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....

[Q] Couldnt Update to Lollipop, LF USA XT1063 Mirror

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

[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"

[Need Help From Experts] Fix An HTC One From A Big Mess

All I wanted was to upgrade my Rooted M7 to the latest software upgrade, so long short story I flashed recovery to TWRP and my M7 got stuck on logo. I know that I should install a ROM, but I don't know which one I should download and how to install it. How can I fix that? FYI you are talking to a noob :crying:.
Additional Information:
UNLOCKED
M7_UL S-ON
HBOOT 1.57
OS 6.09.401.11
HTC_J15
TWRP 3.0
More Information:
I have downloaded theses files see if I can use it:
cm-12.1-20160217-NIGHTLY-m7.zip
cm-12.1-20160217-NIGHTLY-m7-recovery.img
Android_Revolution_HD-One_93.0_ef29f7.zip
Flash_recovery_7.15.401.1.rar
One_M7_7.15.401.1_stock_system_dump.zip
One_All-In-One_Kit_v3.1.rar(Hasoon2000)
And I have this update from a long time I think it was downloaded from my M7:
OTA_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2-6.09.401.11_release_4217922wykl7uamtts1919.zip
I had a big problem in update too, I had an error I think it was in xbin dexdump something like that. I'll remember it when I can update.
Note: Anyone can help me should help me from this problem to the end of updating my M7.
Thanks in Advance

mohdhasan3 said:
All I wanted was to upgrade my Rooted M7 to the latest software upgrade, so long short story I flashed recovery to TWRP and my M7 got stuck on logo. I know that I should install a ROM, but I don't know which one I should download and how to install it. How can I fix that? FYI you are talking to a noob :crying:.
Additional Information:
UNLOCKED
M7_UL S-ON
HBOOT 1.57
OS 6.09.401.11
HTC_J15
TWRP 3.0
More Information:
I have downloaded theses files see if I can use it:
cm-12.1-20160217-NIGHTLY-m7.zip
cm-12.1-20160217-NIGHTLY-m7-recovery.img
Android_Revolution_HD-One_93.0_ef29f7.zip
Flash_recovery_7.15.401.1.rar
One_M7_7.15.401.1_stock_system_dump.zip
One_All-In-One_Kit_v3.1.rar(Hasoon2000)
And I have this update from a long time I think it was downloaded from my M7:
OTA_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2-6.09.401.11_release_4217922wykl7uamtts1919.zip
I had a big problem in update too, I had an error I think it was in xbin dexdump something like that. I'll remember it when I can update.
Note: Anyone can help me should help me from this problem to the end of updating my M7.
Thanks in Advance
Click to expand...
Click to collapse
Are you able to access TWRP recovery?
If you can you can use my Nandroid backup here. https://www.androidfilehost.com/?fid=95897840722641162
Extract the zip on your desktop. You should get a folder and a zip file.
Copy the folder to the TWRP Backups folder on your device using MTP in TWRP.
Location :- /TWRP/BACKUPS/XXXXXXXXXXX/.
Return to twrp home screen and select restore. Then select my backup. Once that's complete you should be good. Reboot from recovery. TWRP may ask if you want to root the device at this point but it's best to wait until after the updates are installed.
To install the ota you need to flash the Stock recovery back to the device. You will find it in the zip file that came with the backup.
Open the zip file on your pc and extract the recovery.img. Copy it to your fastboot folder and flash it like twrp
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Once that's done reboot the device and it should be ready to receive OTA updates. You will need to install 4 or 5 updates to bring your device to the latest. So just keep going untill no more are available. Once you've installed all the updates. Reflash TWRP and root the phone :good:
Sent from my HTC One using Tapatalk

Danny201281 said:
Copy the folder to the TWRP Backups folder on your device using MTP in TWRP.
Location :- /TWRP/BACKUPS/XXXXXXXXXXX/.
Return to twrp home screen and select restore. Then select my backup. Once that's complete you should be good. Reboot from recovery. TWRP may ask if you want to root the device at this point but it's best to wait until after the updates are installed.
To install the ota you need to flash the Stock recovery back to the device. You will find it in the zip file that came with the backup.
Open the zip file on your pc and extract the recovery.img. Copy it to your fastboot folder and flash it like twrp
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Once that's done reboot the device and it should be ready to receive OTA updates. You will need to install 4 or 5 updates to bring your device to the latest. So just keep going untill no more are available. Once you've installed all the updates. Reflash TWRP and root the phone :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks for replying, the file you provided is damaged I think, it should be 1.2 gb but I can download only about 88 mb of the file and its damaged. By the way, I wonder how can I copy the folder to TWRP using MTP

mohdhasan3 said:
Thanks for replying, the file you provided is damaged I think, it should be 1.2 gb but I can download only about 88 mb of the file and its damaged. By the way, I wonder how can I copy the folder to TWRP using MTP
Click to expand...
Click to collapse
The uploaded file is fine. It's been downloaded and used many times. How are you downloading it? Through your browser or with a download manager?
Newer versions of TWRP recovery allow MTP connection while in twrp. This allows you to copy files to the device in recovery mode just like if you were doing it in Android. I have not used TWRP 3.0. myself so can't confirm it supports MTP. I'll check and get back to you :good:
@mohdhasan3 can you provide a link the the TWRP 3.0 download you flashed please?
Sent from my HTC One using Tapatalk

Danny201281 said:
The uploaded file is fine. It's been downloaded and used many times. How are you downloading it? Through your browser or with a download manager?
Newer versions of TWRP recovery allow MTP connection while in twrp. This allows you to copy files to the device in recovery mode just like if you were doing it in Android. I have not used TWRP 3.0. myself so can't confirm it supports MTP. I'll check and get back to you :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Dear Danny,
Could you check the link for me or upload it to another site, because I checked the two links in Mozilla and Opera with download manager and without with VPN and without its always about 88 mb file
This is the link for TWRP 3.0:
https://dl.twrp.me/m7/twrp-3.0.0-0-m7.img.html
I see now the MTP Device yeah it just like you said. I can see a TWRP folder and a TWRPS File with no name inside the folder. So I'll add a new folder naming Backup and wait for your working link.
By the way, thanks for helping I appreciate your effort

mohdhasan3 said:
Dear Danny,
Could you check the link for me or upload it to another site, because I checked the two links in Mozilla and Opera with download manager and without with VPN and without its always about 88 mb file
This is the link for TWRP 3.0:
https://dl.twrp.me/m7/twrp-3.0.0-0-m7.img.html
I see now the MTP Device yeah it just like you said. I can see a TWRP folder and a TWRPS File with no name inside the folder. So I'll add a new folder naming Backup and wait for your working link.
Click to expand...
Click to collapse
I e checked it and your right, there seems to be an issue with the Mirrors. I can upload it again but unfortunately I'm still waiting for my fiber broadband upgrade so it may take some time to upload. I will update you here once it's ready
Unless I can find somthing else where that you can use :good:
Sent from my HTC One using Tapatalk

Danny201281 said:
I e checked it and your right, there seems to be an issue with the Mirrors. I can upload it again but unfortunately I'm still waiting for my fiber broadband upgrade so it may take some time to upload. I will update you here once it's ready
Unless I can find somthing else where that you can use :good:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Phew.... I thought it was my bad day

mohdhasan3 said:
Phew.... I thought it was my bad day
Click to expand...
Click to collapse
I have started the upload but I also found another backup here https://www.androidfilehost.com/?fid=95864024717072880
Although since its not my own I can't guarantee its full stock. But worth a try while your waiting. You can still use the I can provide the Stock recovery no problem it's only 12mb
Sent from my HTC One using Tapatalk

Danny201281 said:
I have started the upload but I also found another backup here https://www.androidfilehost.com/?fid=95864024717072880
Although since its not my own I can't guarantee its full stock. But worth a try while your waiting. You can still use the I can provide the Stock recovery no problem it's only 12mb
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Ok, I'm downloading it now I'll keep you in touch :highfive: :good:
@Danny201281 By the way, when I entered TWRP before maybe an hour there is something popped up asking I think to be able to do modifications by swiping the arrow or to Keep System Read Only, so I pressed Keep System. I don't know what is it but I hope that I didn't messed up again.

mohdhasan3 said:
Ok, I'm downloading it now I'll keep you in touch :highfive: :good:
@Danny201281 By the way, when I entered TWRP before maybe an hour there is something popped up asking I think to be able to do modifications by swiping the arrow or to Keep System Read Only, so I pressed Keep System. I don't know what is it but I hope that I didn't messed up again.
Click to expand...
Click to collapse
No it's fine for the moment. But if you are going to use custom roms after the update you will want to change it to read/write :good:
Were you able to figure out how to use mtp in twrp to copy the files to the device?
Here's a link to the Stock recovery https://www.dropbox.com/s/iej6thyyjakwgjc/recovery.img?dl=0
Sent from my HTC One using Tapatalk

Danny201281 said:
No it's fine for the moment. But if you are going to use custom roms after the update you will want to change it to read/write :good:
Were you able to figure out how to use mtp in twrp to copy the files to the device?
Here's a link to the Stock recovery https://www.dropbox.com/s/iej6thyyjakwgjc/recovery.img?dl=0
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes, I'm. Now I'm extracting the zip then I'll copy the folder as you said to TWRP/BACKUPS/********* :good:
Updating Progress:
Putting the folder in TWRP/BACKUPS/"In Here" will not work. So I did a backup to see where it goes. After it completed, the Backup saved in TWRP/BACKUPS/SH35********(Device Serial[1])/2016-02-19--11-28-11(Today's Date)/"In Here". Then I replaced this Backup Files with the Nandroid Backup Files.
[1] Device Serial can be found with ADB writing in the command prompt opened from the ADB folder location after connecting the device to the PC and enabling USB debugging "adb devices"

You succeeded -my bro- in restoring my M7 again to normal thank you very much :victory:, but still didn't reach my goal I'll continue now in progressing and will keep you in touch :good:
Updating Progress 1:
After I downloaded the latest OTA, I installed it. M7 rebooted then it went to the recovery that showed up with red triangle, pressed the three combinations Power + Volume Up + Volume Down I got the recovery menu, then I wiped cache partition and the red triangle went to I think green likely circle. Rebooted, tried again it starts to updating then after maybe about a quarter of the updating bar red triangle showed up again saying installation aborted. Rebooted, then tried again -here is my problem from long time- OTA was deleted after I went to check for updates now I'm downloading again and will try one more time. I need your help my brother @Danny201281
Updating Progress 2:
Same. Installation aborted after almost half-quarter of the updating bar then red triangle again. Help is appreciated.
I think I know the solution now, but first the error is same like this except the Package:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.102.008
Package expects build fingerprint of htc/vodafone_uk/m7:4.4.3/KTU84L/366813.9:user/release-keys
or htc/vodafone_uk/m7:5.0.2/LRX22G/476210.2:user/release-keys;
this device has htc/vodafone_uk/m7:4.4.3/KTU84L/366813.5:user/release-keys.
Installation aborted.
Write host_mode:0 done
The one had this error fixed it and said that he installed the wrong recovery
As you can see that your link OS is 6.09.401.11 but the link you provided OS is 6.09.401.12 maybe thats why the recovery is different from each other. What do you say

mohdhasan3 said:
You succeeded -my bro- in restoring my M7 again to normal thank you very much :victory:, but still didn't reach my goal I'll continue now in progressing and will keep you in touch :good:
Updating Progress 1:
After I downloaded the latest OTA, I installed it. M7 rebooted then it went to the recovery that showed up with red triangle, pressed the three combinations Power + Volume Up + Volume Down I got the recovery menu, then I wiped cache partition and the red triangle went to I think green likely circle. Rebooted, tried again it starts to updating then after maybe about a quarter of the updating bar red triangle showed up again saying installation aborted. Rebooted, then tried again -here is my problem from long time- OTA was deleted after I went to check for updates now I'm downloading again and will try one more time. I need your help my brother @Danny201281
Updating Progress 2:
Same. Installation aborted after almost half-quarter of the updating bar then red triangle again. Help is appreciated.
I think I know the solution now, but first the error is same like this except the Package:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
L50QCT.01.102.008
Package expects build fingerprint of htc/vodafone_uk/m7:4.4.3/KTU84L/366813.9:user/release-keys
or htc/vodafone_uk/m7:5.0.2/LRX22G/476210.2:user/release-keys;
this device has htc/vodafone_uk/m7:4.4.3/KTU84L/366813.5:user/release-keys.
Installation aborted.
Write host_mode:0 done
The one had this error fixed it and said that he installed the wrong recovery
As you can see that your link OS is 6.09.401.11 but the link you provided OS is 6.09.401.12 maybe thats why the recovery is different from each other. What do you say
Click to expand...
Click to collapse
Normally such a small difference shouldn't cause a problem but let's try the correct recovery I found a firmware zip download link below ?
Download this firmware zip. https://www.androidfilehost.com/?fid=23991606952612395
Extract it on your pc and use the recovery from it. It will then match your Rom
Sent from my HTC One using Tapatalk

Danny201281 said:
Normally such a small difference shouldn't cause a problem but let's try the correct recovery I found a firmware zip download link below ��
Download this firmware zip. https://www.androidfilehost.com/?fid=23991606952612395
Extract it on your pc and use the recovery from it. It will then match your Rom
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
FINALLY I UPDATED MY M7 :victory:!!
I made a great progress. I opened the OTA that I had from the start -its the same as the latest OTA I was downloading- and opened the firmware.zip and extracted the recovery.img from it, flashed, downloaded OTA again from device, installed it, and succeeded in upgrading to the latest OTA. I recommend for anyone have this problem too to download the latest OTA from device, copy it to desktop, extract recovery.img from firmware.zip inside the OTA, flash, then install update and it will work PERFECTLY :good:
I don't know how to thank you my brother you are GREAAAT :fingers-crossed:. Thank you very very much. All credits goes to @Danny201281 for fixing my device.
If you may could I use more of your services?
If I can how can I install ROMs and how can I S-OFF M7?

mohdhasan3 said:
FINALLY I UPDATED MY M7 :victory:!!
I made a great progress. I opened the OTA that I had from the start -its the same as the latest OTA I was downloading- and opened the firmware.zip and extracted the recovery.img from it, flashed, downloaded OTA again from device, installed it, and succeeded in upgrading to the latest OTA. I recommend for anyone have this problem too to download the latest OTA from device, copy it to desktop, extract recovery.img from firmware.zip inside the OTA, flash, then install update and it will work PERFECTLY :good:
I don't know how to thank you my brother you are GREAAAT :fingers-crossed:. Thank you very very much. All credits goes to @Danny201281 for fixing my device.
If you may could I use more of your services?
If I can how can I install ROMs and how can I S-OFF M7?
Click to expand...
Click to collapse
Yes you can now flash custom lollipop roms, the process is fairly simple. Choose the Rom you want. Download it and copy it to your devices storage. Reboot TWRP recovery and install the Rom.
To gain s-off your only option is Sunshine app. It's not free to use unfortunately but its very simple and effective.
All other methods have either been patched against by HTC or discontinued by there developers. Rumrunner still works but only for devices with hboot 155 or below. ?
Sent from my HTC One using Tapatalk

[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