Related
[edit] I bought a Moto X, and got this to work. See second post [/edit]
Preface: I do not yet own a Moto X so I cannot try this myself, but I will buy one if I can achieve my immediate goal. ( I currently have a Nexus S where everything is easy...) Forgive me if this post seems long or silly. I really have been reading, and I want a new phone...
Given:
My carrier is AT&T (locked bootloader, can only fastboot flash signed .img files)
If you take .54 OTA you cannot downgrade to original rootable SBF
Immediate goal: rooted + rw on /system, and call quality/camera update (.54) without taking OTA (I want to retain the ability to downgrade and start over, etc)
Plan:
(start with At&t stock .51)
a. Backup /efs
b. PwnMyMoto (root + overwrite recovery.img with .51 boot.img )
c. Create a flashable zip of /system taken from .54 SBF
- -or-
- Wait for flashable zip to materialize: http://forum.xda-developers.com/showthread.php?p=46490214#post46490214
d. Install safestrap and create a new/empty slot
e. Flash /system (from step c) via TWRP to new safestrap slot
f. Flash superuser via TWRP to new safestrap slot
g. Fastboot flash boot boot.img from .54 SBF (boot safestrap with .54 kernel)
h. Fastboot flash modem NON-HLOS.bin from .54 SBF (boot phone with .54 modem)
i. Fastboot flash recovery boot.img from .54 SBF (change recovery to .54 version of kernel for rw on /system)
Questions:
1. Has "fastboot flash boot boot.img" (.54 version from SBF) and "fastboot flash NON-HLOS.bin" (again .54 version) actually been tested with the original .51 bootloader?
I read it should be possible ( http://forum.xda-developers.com/showthread.php?p=46356343#post46356343 seemingly confirmed by step 15 from this post: http://forum.xda-developers.com/showthread.php?t=2466191 )
2. When will this technique "break down" and not allow me to upgrade?
Technique = booting with latest signed kernel, latest signed modem and latest /system in safestrap slot, keeping original bootloader and original .51 /system (mismatched with kernel and modem) in 'stock slot'(I am guessing the answer is:
1. when the signed kernel requires an updated bootloader or
2. when no official version is released - like android 5 is not released for the Moto X)
Any feedback to confirm the validity of this plan is appreciated.
Many thanks - Ctrl-Freak
I got this to work, thought I would post an update, and I would still like an answer to my second question of my OP.
- I bought a Moto X
- I followed my aforementioned plan in the OP:
1. Rooted
2. Installed Safestrap and created new rom slot
3. Installed the deodexed rom from this post via SS TWRP: http://forum.xda-developers.com/showthread.php?t=2485166
4. fastboot flash boot boot.img <--- from .54 SBF
5. updated the modem to the .54 SBF version:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
6. flashed chainfire's superSU via SS TWRP
The first time I booted to the safestrap romslot, WIFI was not working (slider was greyed out). I simply rebooted, and it worked ever since...
I have played around for a couple of hours, and so far, I cannot find anything that doesn't work.
Hope this helps - Ctrl-Freak
or just flash the verizon safestrap rom that has entitlement in it. Works great with no changes. Only thing i notice is that I get a verizon webpage when i plug in my phone lol
mj0528,
I guess I just wanted a clean .54 (camera update) AT&T install with SafeStrap using the corresponding .54 kernel and modem. After all, it is not clear to me if the camera update involves the kernel (or not).
Ctrl-Freak
The Verizon rom is as clean of a process as it gets.
Sent from my XT1060 using XDA Premium 4 mobile app
mj0528 said:
The Verizon rom is as clean of a process as it gets.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does it have root for those of us on att?
Sent from non rooted motoX :'(
Yea, just flash the su available in that thread in the op
Sent from my XT1060 using XDA Premium 4 mobile app
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
FYI NOTE - I originally did this for the Moto X back when I still had it. Video below was on a VZW Moto X back in September. I also did the EXACT same process when I received my MAXX two days ago. Exact same hardware, same process.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Devices: VZW Moto X AND Droid MAXX
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Excellent guide, I'm not bricked but I'm pretty sure it will be useful for someone else!, thanks for your time and effort
Sent from my Nexus 7 using XDA Premium 4 mobile app
Nice guide. Used rsdlite and flashed stock. Just upgraded 4.4. Very satisfied with new version along with nova pro
Sent from my XT1080 using xda app-developers app
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
Yes it does, I'm using a custom radio too, I'm waiting for the kit Kat sbf
Sent from my Nexus 7 using XDA Premium 4 mobile app
allquixotic said:
Question: will this method work if I flashed a custom radio? In other words, does this completely overwrite all pre-existing mods (custom bootloader, custom radio, system file mods)? Thanks!
Click to expand...
Click to collapse
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Sent from my XT1080 using xda app-developers app
YoungSkeezy said:
What kind of custom radio? Thought you couldn't flash that kind of stuff without an s off device?
Click to expand...
Click to collapse
Just the radio that leaked that everyone thought was a test of AWS. The radio worked, but I didn't notice any higher speeds.
No, you don't need S-OFF to flash a custom radio.
will it work if i want to downgrade from 4.4 to 4.2 ?
No
YOU SIR...ARE THE MAN!!!!! worked flawlessly..i thought i had permanently bricked my replacement phone.. but thanks to you and another fellow who directed me to the FXZ files.. the new phone is up and running..and I can send the old one back!!!
Worked great. Not difficult at all.
Sent from my XT1080 using xda app-developers app
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
kanagadeepan said:
First of all, a lot of Thanks for this useful thread sir...
I am using DroidMAXX with Unlocked BL, rooted and customRecovery flashed... I can see the lines to flash boot image and recovery image. So on flashing this my phone's BL will be relocked and stock recovery will be flashed, isn't it. Later I can again unlock using the code, right? And I can use this method to receive OTA (for 4.4.2) right?
Click to expand...
Click to collapse
No, this will NOT re-lock your bootloader. It does flash the stock recovery and unroot you so you can receive an OTA.
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
kanagadeepan said:
OH... Thanks ji for the clarificaiton... So I can flash it and reroot by flashing twrp recovery? Why I am asking is I have messed with the active notifications and other Moto apps using Titanium Backup.. Now I want my root + Active Notifications back...
Thanks again, my friend...
Click to expand...
Click to collapse
yes, just flash twrp and reroot
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Jay_P11 said:
I know that this won't work for downgrading from 4.4 to 4.2.2, but I'm wondering why not? What is making it so that this doesn't work? I'm thinking it has something to do with the new recovery that was flashed with the update, but I'm not sure.
Click to expand...
Click to collapse
Bootloader
akellar said:
Bootloader
Click to expand...
Click to collapse
Alright thanks for clarifying. My battery life is absolutely horrid, about 8 hours MAX per day before I need a charge, and it was never like this on 4.2.2 :/ 4.4's "Battery Saver" feature in WiFi settings never works anymore either, it just turns itself off the second I turn it on. Definitely some major bugs in this build, and I'm hoping they get fixed in the next update. If they don't, then I'm just going to pony up $300 for early termination and get an LG G2.
One more thing, this should work for restoring back to factory 4.4 on 4.4 then right? Maybe my update is broken and it just needs a clean install for the battery saver to work?
TechSavvy2 said:
First simply boot into fastboot mode - manually OR adb reboot bootloader
Code:
fastboot oem fb_mode_set
Click to expand...
Click to collapse
So I just send up sitting at "waiting for device" after executing that line. RSD won't recognize my phone either--tried different cables.
Thoughts?
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
Hi guys the recent Australian firmwares N920IDVU3BPL2 of N920I has restriction which forces to stay on latest firmware. My LTE is not working on N920IDVU3BPL2 and it is not allowing me to install any old firmware to me.
If I still try to install any old firmware which was working and had good LTE on same phone then I get
"SYSTEM REV CHECK FAIL DEVICE 1 BINARY 0" error"
I think if I can flash my old firmware modem through twrp then I may fix LTE signal issue. Can anyone provide any assistance on how to create TWRP flashable modem and bootloader zip file because ODIN does not allow me to flash old firmware now.
Did you found it? I need the modem too. Question, is it necessary to flash bootloader too in order to flash modem?
When trying to flash any stock carrier firmware (Verizon or Tmo) Odin successfully flashes, but then Android System Recovery comes up with the error "Can't open dir '/data/vendor_de' (Permission Denied) failed the resizing-data".
Attached are photos.
How do I fix this?
https ://imgur.com/a/JuFTXyp
Have you tried flashing the firmware that came with your phone?
aspiller98 said:
When trying to flash any stock carrier firmware (Verizon or Tmo) Odin successfully flashes, but then Android System Recovery comes up with the error "Can't open dir '/data/vendor_de' (Permission Denied) failed the resizing-data".
Attached are photos.
How do I fix this?
https ://imgur.com/a/JuFTXyp
Click to expand...
Click to collapse
I had that too when flashed firmware, but I just ignore it and reboot the device
I did that. However I have a tmobile s10 and was trying to flash verizon firmware. When rebooting after the error I'm still running tmobile firmware.