[GUIDE][OTA]Manually flashing ota over rooted system (Latest v309) - Asus ZenFone Max Pro M1 Guides, News, & Discussio

[GUIDE][OTA]Manually flashing ota over rooted system (Latest v309) - Asus ZenFone Max Pro M1 Guides, News, & Discussio

Things needed:
1. Unlocked and Asus Zenfone Max Pro M1 (why dafaq so long name?)
2. Stock rom (recovery/fastboot doesn't matter) i used this to updated to 305, get accordingly from here
3. Modified TWRP recovery
4. Ota package
Instructions:
1. Download the full rom and ota (in your phone, from second post or get from our telegram group)
2. After download gets completed, go to /data/cache and copy dlpkgfile somewhere in sdcard, and rename it to ota.zip
3. Extract ota.zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
getprop("ro.build.asus.sku") == "WW" || abort("E3009: This package is for sku: \"WW\"; this is a sku: \"" + getprop("ro.build.asus.sku") + "\".");
ui_print("Source: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys");
ui_print("Verifying current system...");
containprop(getprop("ro.build.fingerprint")) ||
abort("E3001: Package expects build fingerprint of Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys or Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
i.e. everything till
Code:
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe") || abort("E3005: \"EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe\" has unexpected contents.");
Save it and zip back the ota
NOTE: Skip step 4 if you have stock fastboot images
4. Extract stock rom zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
(!less_than_int(1524926024, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sat Apr 28 22:33:44 CST 2018) over newer build (" + getprop("ro.build.date") + ").");
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
show_progress(0.650000, 0);
i.e everything till
Code:
ui_print("Patching system image unconditionally...");
Once done, zip it back
5. Reboot to bootloader and flash system.img vendor.img boot.img and modified twrp.img if you have correct version of fastboot rom, otherwise, just flash the modified twrp.img and force reboot to recovery by pressing and holding volume down + power key
6. Once in recovery, flash the rom.zip you made and right after that flash the ota.zip, once done, make a backup of boot, modem, system image, vendor image
7. (OPTIONAL) if you had decrypted data partition before, flash normal twrp using current twrp or fastboot and flash decrypt.zip again
8. (OPTIONAL) if you want rooted system no twrp and easy ota updates for future, flash magisk and stock recovery using modified twrp and reboot. you'll be able to flash ota normally after this with root access.
Enjoy.
What to do on next ota?
1. Flash the modified twrp
2. Restore the backup you made in step 6
3. Edit the ota as explained in step 3
4. Flash the ota zip and make another backup of system image, vendor image, modem, and boot (also any other partition depending on the ota)
5. Do the optional steps as said in steps 7 and 8

Modified OTA Links:
From 252 to 305
From 305 to 309

Wow... I just came here to say someone to write this out.. and seeing it already posted just few hours ago..

can you please explain it with detail, dude.. newbie here

8. (OPTIONAL) if you want rooted system no twrp and easy ota updates for future, flash magisk and stock recovery using modified twrp and reboot. you'll be able to flash ota normally after this with root access.
Click to expand...
Click to collapse
So we dont need to flash the original boot.img if we choose this? Because Magisk modified the boot image....

dimedevil said:
So we dont need to flash the original boot.img if we choose this? Because Magisk modified the boot image....
Click to expand...
Click to collapse
Depends on ota, if it has patch or complete boot.img
You can flash magisk uninstaller to restore boot.img too
Sent from my ASUS_X00TD using Tapatalk

Step 2 : I cant find data folder in me internal storage! Plz help me out
---------- Post added at 06:16 AM ---------- Previous post was at 06:07 AM ----------
Where to find dlkgpfile??? I couldn't find it

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
Click to expand...
Click to collapse
do you have this file before editing?

Sudeep Duhoon said:
Depends on ota, if it has patch or complete boot.img
You can flash magisk uninstaller to restore boot.img too
Sent from my ASUS_X00TD using Tapatalk
Click to expand...
Click to collapse
I see... but in my case, Magisk Uninstaller failed on TWRP and RWRP... error 1 it said...
So I'm going to try the 8th option... let's hope there's no problem flashing in the future...

please create video tutor easy to understand

.A.V.i.n.a.S.h. said:
Instead of doing the backup of the partitions & the restore before OTA, can I continue to modify full ROM + OTA and flash it.
Click to expand...
Click to collapse
Yes, full ota will work just fine
But if there is no full ota, backup and restore is the solution
Sent from my Phh-Treble with GApps using Tapatalk

.A.V.i.n.a.S.h. said:
Can you please clarify this final doubt.
If I go for Magisk+Stock recovery -
The Magisk update (like from v15.3 to v16.0) will effect the OTA or no.
Click to expand...
Click to collapse
if you flash magisk using modified twrp, and flash stock recovery afterwards
if there is complete boot.img in next ota, stock recovery will flash ota just fine, if there is patch for boot, ota will fail and you will have to flash stock boot.img using fastboot/modified twrp or flash magisk uninstaller by modified twrp.
.A.V.i.n.a.S.h. said:
So by step-7, I flash TWRP_unofficial and flash decrypt.zip
In step-8, flash TWRPnomount again over regular TWRP and flash magisk and stock recovery right.
Also should I stick with Magisk-16.0 or can I update Magisk without breaking OTA.
Click to expand...
Click to collapse
if you flash decrypt.zip you have to flash stock vendor.img before flashing next ota
both steps are optional and independent from each other, may break ota
also i am unable to understand what you are trying to achieve here. sorry.

Sudeep Duhoon said:
Things needed:
1. Unlocked and Asus Zenfone Max Pro M1 (why dafaq so long name?)
2. Stock rom (recovery/fastboot doesn't matter) i used this to updated to 305, get accordingly from here
3. Modified TWRP recovery
4. Ota package
Instructions:
1. Download the full rom and ota (in your phone, from second post or get from our telegram group)
2. After download gets completed, go to /data/cache and copy dlpkgfile somewhere in sdcard, and rename it to ota.zip
3. Extract ota.zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
getprop("ro.build.asus.sku") == "WW" || abort("E3009: This package is for sku: \"WW\"; this is a sku: \"" + getprop("ro.build.asus.sku") + "\".");
ui_print("Source: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys");
ui_print("Verifying current system...");
containprop(getprop("ro.build.fingerprint")) ||
abort("E3001: Package expects build fingerprint of Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys or Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.305-20180521:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
i.e. everything till
Code:
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe") || abort("E3005: \"EMMC:/dev/block/bootdevice/by-name/boot:47510824:9ca7a29f3b90af90492bfa0c07275390f72f397d:47502632:80fbccb727c484733397429a9df38a499dee67fe\" has unexpected contents.");
Save it and zip back the ota
NOTE: Skip step 4 if you have stock fastboot images
4. Extract stock rom zip and go to META-INF\com\google\android , open updater-script in text editor and remove these lines from it
Code:
(!less_than_int(1524926024, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Sat Apr 28 22:33:44 CST 2018) over newer build (" + getprop("ro.build.date") + ").");
containprop(getprop("ro.product.device")) || abort("E3004: This package is for \"ASUS_X00TD\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: Android/sdm660_64/sdm660_64:8.1.0/OPM1/14.2016.1804.252-20180428:user/release-keys");
show_progress(0.650000, 0);
i.e everything till
Code:
ui_print("Patching system image unconditionally...");
Once done, zip it back
5. Reboot to bootloader and flash system.img vendor.img boot.img and modified twrp.img if you have correct version of fastboot rom, otherwise, just flash the modified twrp.img and force reboot to recovery by pressing and holding volume down + power key
6. Once in recovery, flash the rom.zip you made and right after that flash the ota.zip, once done, make a backup of boot, modem, system image, vendor image
7. (OPTIONAL) if you had decrypted data partition before, flash normal twrp using current twrp or fastboot and flash decrypt.zip again
8. (OPTIONAL) if you want rooted system no twrp and easy ota updates for future, flash magisk and stock recovery using modified twrp and reboot. you'll be able to flash ota normally after this with root access.
Enjoy.
What to do on next ota?
1. Flash the modified twrp
2. Restore the backup you made in step 6
3. Edit the ota as explained in step 3
4. Flash the ota zip and make another backup of system image, vendor image, modem, and boot (also any other partition depending on the ota)
5. Do the optional steps as said in steps 7 and 8
Click to expand...
Click to collapse
After rooting phone, for ota update, If I flash stock recovery via flashify and uninstall magisk from magisk app then put rom in internal storage, will it detect software update & installe it?? Or if I flash updated zip by stock recovery will it work??

Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?
And thank you for posting the guide.

arnold991 said:
Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?
And thank you for posting the guide.
Click to expand...
Click to collapse
yes help

arnold991 said:
Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?
And thank you for posting the guide.
Click to expand...
Click to collapse
Kindly help brother.

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
From 305 to 309
Click to expand...
Click to collapse
Thank you, thank you.. You are a life saver!!! Please continue to upload the modified OTAs in the future too.. Really appreciate this..

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
From 305 to 309
Click to expand...
Click to collapse
I am on Redwolf recovery.
Unlocked bootloader and Rooted with magisk.
Can I flash this zip with Redwolf Recovery?
Do I have to follow full procedure?

Sudeep Duhoon said:
Modified OTA Links:
From 252 to 305
From 305 to 309
Click to expand...
Click to collapse
So this modified ota will work if just flash by TWRP or RWRP?? Don't need to flash system.img, vendor.img, boot.img???

Ariful Hasan Soikot said:
So this modified ota will work if just flash by TWRP or RWRP?? Don't need to flash system.img, vendor.img, boot.img???
Click to expand...
Click to collapse
No, it won't, I have tried that, you will get flashing error.
Full ROM is out. @Sudeep Duhoon
https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_Download/
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZB601KL/UL-ASUS_X00T-WW-15.2016.1805.309-user.zip
The questions I asked earlier.
Kindly explain the steps for those guys who are on 305 Version already, have it rooted and have TWRP installed and
1) Want to have root and TWRP intact after update
2) And data also remains
How can they update to 309 ?

Related

Patch LRX22C?

This may very well be a foolish question, but I'll ask anyway.
My wife and I both have Nexus 6 devices. I have unlocked, rooted and installed TWRP on both.
On mine, I just installed the Pure Nexus ROM; after trying a couple other custom ROMs.
However, my wife's phone is still running LRX22C (5.0.1); and I'd like to update to the latest 5.1.1.
So what is the problem, you may ask...
She has a lot of work stuff on the phone, she loves the phone, but to use it at work, she needs to accept the security policies from their IT dept and mandatory encryption (plus they pay most of the monthly invoice).
I just want to confirm that it would be ok to dirty flash LYZ28J (5.1.1 TMO stagefright fix) from the available zips in this post:
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
I just don't want to end up sleeping in the bathtub if anything were to happen to her data or settings.
Thanks in advance

poodleDoo said:
This may very well be a foolish question, but I'll ask anyway.
My wife and I both have Nexus 6 devices. I have unlocked, rooted and installed TWRP on both.
On mine, I just installed the Pure Nexus ROM; after trying a couple other custom ROMs.
However, my wife's phone is still running LRX22C (5.0.1); and I'd like to update to the latest 5.1.1.
So what is the problem, you may ask...
She has a lot of work stuff on the phone, she loves the phone, but to use it at work, she needs to accept the security policies from their IT dept and mandatory encryption (plus they pay most of the monthly invoice).
I just want to confirm that it would be ok to dirty flash LYZ28J (5.1.1 TMO stagefright fix) from the available zips in this post:
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
I just don't want to end up sleeping in the bathtub if anything were to happen to her data or settings.
Thanks in advance
Click to expand...
Click to collapse
Here's what I would do:
Back up all the important stuff to PC.
Unlock her bootloader and flash the entire factory image for the latest build. Then transfer the backup back to the phone.
Otherwise you can sideload OTA's but it will take much longer.

The_Merovingian said:
Here's what I would do:
Back up all the important stuff to PC.
Unlock her bootloader and flash the entire factory image for the latest build. Then transfer the backup back to the phone.
Otherwise you can sideload OTA's but it will take much longer.
Click to expand...
Click to collapse
Nope. Can't sideload OTA since the phone's not stock (root and TWRP).
What I would do is to backup everything (nandroid in TWRP) and then fastboot flash the factory image, leaving out userdata.img and recovery.img. I'd also take the opportunity to flash the latest TWRP. You'll loose root doing this, but just enter TWRP before booting (you need to do this anyway so that your recovery won't get overwritten) and it should ask you if you want to root when you reboot.
No data lost this way.

Didgeridoohan said:
Nope. Can't sideload OTA since the phone's not stock (root and TWRP).
What I would do is to backup everything (nandroid in TWRP) and then fastboot flash the factory image, leaving out userdata.img and recovery.img. I'd also take the opportunity to flash the latest TWRP. You'll loose root doing this, but just enter TWRP before booting (you need to do this anyway so that your recovery won't get overwritten) and it should ask you if you want to root when you reboot.
No data lost this way.
Click to expand...
Click to collapse
That sounds easy enough...
Nandroid backup
fastboot system.img
fastboot boot. img
fastboot latest twrp recovery
fastboot bootloader
fastboot cache
fastboot radio
boot recovery and have TWRP ask about root
Reboot
Does that sound right?
Thanks (used the Thx button for both of you guys).

Looking at the updater script in the zip file, this is what I see; so cna I just flash the zip from TWRP?
Sorry for keeping asking questions...
Code:
getprop("ro.product.device") == "shamu" || abort("This package is for \"shamu\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Writing logo ...");
package_extract_file("logo.bin", "/dev/block/platform/msm_sdcc.1/by-name/logo");
ui_print("Writing boot ...");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ui_print("Writing system ...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Erasing cache ...");
delete_recursive("/cache");
ui_print("Erasing oem ...");
package_extract_file("oem.img", "/dev/block/platform/msm_sdcc.1/by-name/oem");
The contents of the zip are:
META-INF -> com -> google -> android (update-binary & updater-script)
system.new.dat
system.patch.dat
boot.img
oem.img
file_contexts
system.transfer.list
logo.bin
Thanks again

Don't forget to flash bootloader, cache and radio as well... They're kind of important.
---------- Post added at 19:00 ---------- Previous post was at 18:54 ----------
poodleDoo said:
Looking at the updater script in the zip file, this is what I see; so cna I just flash the zip from TWRP?
Sorry for keeping asking questions...
Code:
getprop("ro.product.device") == "shamu" || abort("This package is for \"shamu\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Writing logo ...");
package_extract_file("logo.bin", "/dev/block/platform/msm_sdcc.1/by-name/logo");
ui_print("Writing boot ...");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ui_print("Writing system ...");
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Erasing cache ...");
delete_recursive("/cache");
ui_print("Erasing oem ...");
package_extract_file("oem.img", "/dev/block/platform/msm_sdcc.1/by-name/oem");
The contents of the zip are:
META-INF -> com -> google -> android (update-binary & updater-script)
system.new.dat
system.patch.dat
boot.img
oem.img
file_contexts
system.transfer.list
logo.bin
Thanks again
Click to expand...
Click to collapse
What zip are you talking about? An OTA update.zip? That won't work, since you're not stock...
I'm talking about the factory images from here:
https://developers.google.com/android/nexus/images?hl=en

What zip are you talking about? An OTA update.zip? That won't work, since you're not stock...
I'm talking about the factory images from here:
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I'm talking about these:
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
[FXZ][OTA] Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)

poodleDoo said:
[/COLOR]
What zip are you talking about? An OTA update.zip? That won't work, since you're not stock...
I'm talking about the factory images from here:
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I'm talking about these:
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
[FXZ][OTA] Nexus 6 Recovery Flashable Fastboot Files (Unlocked Bootloader Only)[/QUOTE]
As it says as long as you are unlocked with TWRP. Just flash the whole zip in TWRP. Still better off fastboot the full factory images. If locked and it fails you in for a butt full of hurt.

[ROM/GUIDE] Full Updates / Back to Stock Files via TWRP (A2017U, A2017G, A2017)

READ, READ BEFORE PROCEEDING
YOU'VE BEEN WARNED
Ok, I wasn't going to create a new Thread for this but is really needed to keep this a little separate but in the same thread, so here i'll be updating base on current updates for each variant this Thread will contain Current Updates and as for now current updates are :
REQUIREMENTS :
- Plain and simple, you just need TWRP. Either via @tenfar or @tennear Tools or happens that you already have TWRP install.
ROOT:
If you are UNLOCK BOOTLOADER proceed with STEP 7, if not you'll need to use @tenfar Modded boot image base on your system update to get root access.
Each steps will contain 2 files which are:
1- BootStack
2- System+Boot
Q: Why 2 Flashable Zip Files?
A: Well cuz a lot of us know you CAN use / try other variant system image , i have separate what is just needed to for that purpose, meaning if A2017U want to give a shot to A2017G or A2017 software you will just need to Wipe Cache -Dalvik - Data and Flash the A2017G or A2017 Flashable system file or vice-versa.
The Bootstack just need to be flash ONCE per variant, the A2017G CAN'T use A2017U Bootstack (well you probably can but IS NOT RECOMMENDED) .
- A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)
- A2017.B10 (Post # 4 or Click Here)
- A2017G.B08 (Post # 3 or Click Here)
- A2017G Flashable Stock Recoveries (Post # 5 or Click Here)
-------------------------------------------------------------------------------------------------------------------------------
I'll be Updating this thread base on current Updates and please let's keep this thread clean and on-topic
-------------------------------------------------------------------------------------------------------------------------------

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS 
A2017UV1.1.0B35 NOUGAT Update
-----------------------
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N) / B19(N) / B25(N) / B32(N)
-----------------------------------------------------
Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important
1- Download the following zip files
- A2017UV1.1.0B35_bootstack_by_DrakenFX.zip
- A2017UV1.1.0B35_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (Wipe Data if you aren't updating from B29-MM or B15-N)
5- Flash A2017UV1.1.0B35_bootstack_by_DrakenFX.zip( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- FlashA2017UV1.1.0B35_systemstock_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT AND KEEP TWRP after flashing Stock System, download SuperSU v2.79 (Or your preferable Root method)
WARNING - WARNINGNOTE : YOU MUST FLASH SUPERSU OR VM-VERITY ZIP, IF YOU WANT TO KEEP TWRP, THE B32 UPDATE HAVE STRIP BOOLODER
8- REBOOT and Enjoy Nougat B35 Rooted or Just Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
.
.
.

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS
A2017G.B09 Update ( Files Provided by @tron1 )
-----------------------
-----------------------------------------------------
UPDATING FROM B01, B02, B03, B05 , B06 or B08 Rooted or Stock
-----------------------------------------------------
1- Download the following zip files ( Thanks @tron1 for making the files )
- ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
- ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B09 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
.
. Here's the B08 Files in case are needed
. TWRP_A2017G.B08.BootStack_By_DrakenFX.zip
.
. TWRP_A2017G.B08.FStockSystem_By_DrakenFX.zip
.
..................................................................................................................................................................................................
.
. Here's the B06 Files in case are needed
. ZTE_A2017GV1.0.0B06_BootStack_by_DrakenFX.zip
. md5 : fa64983faaf4d37a26772dab53a61ff2
.
. ZTE_A2017GV1.0.0B06_StockSystem_by_DrakenFX.zip
. md5 : 3b34ac0d1c81248454666b9ae644da16
.
.................................................................................................................................................................................................
.
. Here's the B03 FIles in case are needed
. ZTE_A2017G.B03_BootStack_by_DrakenFX.zip
. md5 : ae0f260a9bd7ee486704842bc9efa202
.
. ZTE_A2017G.B03_StockSystem_by_DrakenFX.zip
. md5 : 5086d5a0d73e07a257b9f4cb4b7c7631
.
..................................................................................................................................................................................................
.
.
. Here's the TWRP B06 Flashable Stock Recovery
. TWRP_B06_StockRecovery.zip
.
. Here's the TWRP B08 Flashable Stock Recovery
. TWRP_B08_StockRecovery.zip
.
..................................................................................................................................................................................................

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS 
A2017.B10 Update
-----------------------
-----------------------------------------------------
UPDATING FROM B09 or Below Rooted B20
-----------------------------------------------------
1- Download the following zip files
- ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip
- ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B10 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------.
.
.B10 & B11 Flashable TWRP Files can be found here also :
https://www.androidfilehost.com/?w=files&flid=118419
.
.

----------------------------------------------
A2017G
Flashable Stock Recoveries
----------------------------------------------
Folder with A2017G Stock Recoveries B06 , B08 and B09
TWRP Stock Recoveries Flashable Zips
----------------------------------------------

Last Reserve for something else thread related

:good:

@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.

TheRoyalSeeker said:
@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.
Click to expand...
Click to collapse
System Dump for which variant? i know A2017G and A2017 are .dat but that can be converted to .img very easily, if you have windows you can use this Android DAT/IMG File Unpack and Repack V 2.0 , that's what i use to convert .dat to .img.
If you need more info just PM.

Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.

AllAboutAndroids said:
Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.
Click to expand...
Click to collapse
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.

xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Let me try that now and will let you know asap!

AllAboutAndroids said:
Let me try that now and will let you know asap!
Click to expand...
Click to collapse
Let's us know I'm mins away from doing this but NEED root!!

S8ntsHaz3 said:
Let's us know I'm mins away from doing this but NEED root!!
Click to expand...
Click to collapse
Noooooope. I went back to Stock Recovery somehow...even though I had TWRP all along.

Sad days

xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Trying this again!
S8ntsHaz3 said:
Sad days
Click to expand...
Click to collapse
Got TWRP back. I'm going to attempt the method above and let you know!

AllAboutAndroids said:
Trying this again!
Got TWRP back. I'm going to attempt the method above and let you know!
Click to expand...
Click to collapse
Awesome thanks !!!!

S8ntsHaz3 said:
Awesome thanks !!!!
Click to expand...
Click to collapse
Hmmm stuck at "Please Wait..."

Which method did you use to obtain root/TWRP?

S8ntsHaz3 said:
Which method did you use to obtain root/TWRP?
Click to expand...
Click to collapse
Using:
D:\Downloads\axon7root-us-b27>axon7root.exe -p 3 -r
That only gave me TWRP. I still can't get Root to work on the B27 Update.

Install OOS Open Beta 8 (N) / 7 (MM) without Breaking official TWRP

This guide allows you to install OOS Open Beta 8 (N) / 7 (MM) without having to switch to modified TWRP
All credits to the respective developers
Downloads : G-Drive | MEGA
Unified Links above contains the following.
[Added] OOS Leaked Open Beta 9 (Mirror only) will modify Once it is released
1- Modded OOS Open Beta 8 (No F2FS , Downgradable to any OOS version)
2- Modded OOS Open Beta 7
3 - Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Unified Flashable Zip)
4- Super SU 2.78-SR5
5- Official TWRP
6 - Modified TWRP Recovery 3.0.2-1.28 Credits @eng.stk
7- Latest Xposed Installer (Beta 7 Only) (It will give you the option to download / install the latest version of framework automatically)
8- Open Beta 8 Full flash able (F2FS support with Modified Recovery @Funk Wizard)
Instructions for Clean / Dirty Flash (Over any Open Beta after 3.5.1) :
1. Boot into TWRP (modified or official which ever you are on)
2. Wipe Dalvik / ART cache & cache OR Factory Reset ( If you are coming from another ROM)
3. Flash Modded OOS Open Beta 8 (Dont Switch /system and /data to F2FS if you want to root) or Beta 7
4. Wipe Dalvik and Cache
5 . Flash official twrp as image (even if you are already on it)
6. Reboot to into recovery directly (this will prevent recovery from being overwrite by the stock)
7. Flash SuperSu (Optional)
8. Flash Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Clear Google App Data after Booting) (Unified Flashable Zip) (Optional)
9. Reboot to System (It will reboot twice if you flashed SuperSU) - That is normal
You are good to go :good:
Regards ,
Muhammad A. Iftikhar

Is there any kernel for this build ???

Normas Interruptor said:
Is there any kernel for this build ???
Click to expand...
Click to collapse
Eng.stk yesterday teased us with an upcoming kernel for 3.5.4 Community Beta.
Whatch this thread: http://forum.xda-developers.com/oneplus-3/development/kernel-t3404970 .

Can I dirty flash it from FreedomOS based on 3.2.7?

xGOGI said:
Can I dirty flash it from FreedomOS based on 3.2.7?
Click to expand...
Click to collapse
Nope, they are two different ROMs on different channels: for instance you could have dirty flashed if you were on 3.5.2 or 3.5.3.

I need to wipe system too? Or only cache/dalvik + data?

xGOGI said:
Can I dirty flash it from FreedomOS based on 3.2.7?
Click to expand...
Click to collapse
Yes you can as you have firmware of 3.2.7

xGOGI said:
I need to wipe system too? Or only cache/dalvik + data?
Click to expand...
Click to collapse
System Wipe only if you are coming from another ROM , I.E CM or AOSP based / Nougut

How do i flash official twrp in modified twrp, do i have to extract the downloaded file?

puschkin said:
How do i flash official twrp in modified twrp, do i have to extract the downloaded file?
Click to expand...
Click to collapse
Click Install > "Install Image" it will showup in the location you download the file should have ".img" extention .
simply download it in the phone from the link in OP.

ahmediftikhar said:
Click Install > "Install Image" it will showup in the location you download the file should have ".img" extention .
simply download it in the phone from the link in OP.
Click to expand...
Click to collapse
Thanks for the quick reply!!

puschkin said:
Thanks for the quick reply!!
Click to expand...
Click to collapse
This will further help you out

Thanks for this great tutorial, worked like a charm

I want to try new CB but more likely I will be going back to official 3.2.7 I have nandroid backup ready. My question is, if I follow your guide and then I want to restore my backup, will I be able to do it without the hassle?
Wysłane ze zmywarki

ralph78 said:
I want to try new CB but more likely I will be going back to official 3.2.7 I have nandroid backup ready. My question is, if I follow your guide and then I want to restore my backup, will I be able to do it without the hassle?
Wysłane ze zmywarki
Click to expand...
Click to collapse
You can even dirty flash this over 3.2.7 (will take some time after 1st boot to optimize apps depending on the number of apps installed) , Nandroid can be restored with out hassle if you choose to clean flash 3.2.7 after testing CB

I'm on TWRP 3.0.2-1, and I can't install Rom zip, it always tells me that zip file is corrupted. I've downloaded it twice however, once from Google drive, once from AFH.
Any idea of what's wrong?

XS_31 said:
I'm on TWRP 3.0.2-1, and I can't install Rom zip, it always tells me that zip file is corrupted. I've downloaded it twice however, once from Google drive, once from AFH.
Any idea of what's wrong?
Click to expand...
Click to collapse
Try re-flashing Twrp by downloading a fresh copy , and manually mount system before flashing the ROM ,
You can also try downloading it directly to your gdrive and let it sync in your PC / phone by "make available offline" feature in drive app

how to back from 3.5.4 to stock again?

File corrupt from both links, also.

ritchiedrama said:
File corrupt from both links, also.
Click to expand...
Click to collapse
Yes... File is corrupted... So much of mobile data wasted..

[GUIDE] [OTA] [TWRP] Android Pie - TWRP, Decrypt, Magisk and OTA

Post my other thread for Android Oreo with OTA with TWRP ( https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269 ), wanted to continue the same but found pretty good solutions to have the process more quick and seamless.
So to have rooted Pie with TWRP and to flash OTA please follow below procedure.
Files needed,
Latest Pie full OTA file from Asus website.
Latest TWRP from here.
Decrypt File for Pie (recommedned).
Magisk (optional).
Debloat File (optional).
Steps to be followed to update to latest OTA,
Flash the latest TWRP and boot into it.
Flash downloaded full OTA package (point-1 above) from Asus website then reboot to recovery from TWRP menu.
Mount /system & /vendor partitions and flash decrypt-pie.zip file (point-2 above).
Reboot to recovery again, mount /system & /vendor and flash Magisk. (point-3 above)
Reboot to recovery and mount /system & /vendor and flash Debloat zip (point-4).
Finally reboot to system and HIT THANKS if it worked for you. This helps me and also gives confidence/credibility to others to try.
Post issues if any below.

It's not working bro

This ROM package works very well but cam2api is getting disabled. Did the build.prop method after root and also the fastboot method. It works for a few days than gcam stops.

As pointed out in the guide, official Pie zip is to be DL and flashed through TWRP. However, since it is official zip, will it flash successfully through TWRP recovery instead of Stock Recovery ?
Also, can anybody confirm if the phone is now system-as-root after upgrade to Pie ? (I am on v340 Oreo and system-as-root is not mandatory for devices upgrading to Pie).
Edit: Ok, so took the plunge and successfully updated from stock rooted v340 (Oreo) to v56 (Pie). Did everything as per the guide except for 2 steps:
1) Used TWRP flashable ROM instead of stock ROM zip.
2) Did not reboot to TWRP recovery after flashing updated recovery. Instead, continued through updated recovery, flashed ROM and then rebooted to recovery.

Bugs in the update v056 (Pie):
1) Sometimes "Recent Apps" list goes blank / stops working. Workaround: Reboot to safe mode and check "Recent Apps" (it usually is working), reboot to normal mode and everything works fine again.
2) Cam2Api breaks, even if you enable <persist.camera.HAL3.enabled=1> it will not work.
Add these lines to build.prop, save and reboot:
persist.camera.HAL3.enabled=1
persist.vendor.camera.HAL3.enabled=1
persist.camera.stats.test=5
persist.vendor.camera.test=5
persist.camera.eis.enable=1
(DO NOT FORGET to backup your original build.prop !)

How To Guide ROOT REALME GT2 (RMX3312) in 10 minutes

REQUIREMENTS - BL UNLOCKED
You need to be on VERSION : RMX3312_11.C.12_IN_202304230924
If not on RMX3312_11_C.12 version - download the entire OTA PACKAGE from the above link & LOCAL INSTALL
Reboot to Bootloader adb reboot bootloader or Power + Volume Down
Take the ROOT BOOT image from the zip file given below and PASTE it in platform tools folder
FLASH the ROOT BOOT IMAGE fastboot flash boot RMX3312_11.C.12_ROOTBOOT.img
Type - fastboot reboot
Finished - Now your Realme GT2 - RMX3312 is now ROOTED!
P.S. : FLASH ON BOTH SLOTS
To keep ROOT when you receive an OTA update
DOWNLOAD THE OTA UPDATE
Let it UNZIP
When it shows - INSTALL / REBOOT TO INSTALL option, put to recents - Open MAGISK
There in MAGISK - SELECT THE INSTALL OPTION on the TOP RIGHT
& then select INSTALL TO INACTIVE SLOT (AFTER OTA) OPTION
Click on OK on the POP-UP MENU in MAGISK
NOW THE DEVICE WILL REBOOT - UPDATE TO THE LATEST OTA & STILL KEEP ROOT!
DOWNLOADS : Both STOCK & ROOT boot images are attached below in one ZIP FILE!
Each Boot Image is 192MB & the compressed ZIP FILE below is 72.6MB.
NOTE : I'm NOT RESPONSIBLE FOR BRICKS, STONES, BLASTS, WIPES etc. of RMX3312

Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?

gx7x said:
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
Click to expand...
Click to collapse
He means you need to run the flash boot command for each slot
for instance your system runs on a slot, as soon as you type the
fastboot flash boot [boot image]
if it shows writing boot_a
then you need to type
fastboot flash boot_b [boot image]
to flash in the b slot also
if it shows writing boot_b
then you need to type
fastboot flash boot_a [boot image]
to flash in the a slot also
and you can pass the safteynet easily even when in root, u can use zygisk and magiskhide to pass the safteynet and you can run any banking app you want

Please do not use the boot images provided if you have not updated to the current latest version
Note: EU version boot image might be different so don't try
p.s you can extract boot images yourself from any version you want!

Stano36 said:
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
Click to expand...
Click to collapse
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..

b0nb0n3v said:
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
Click to expand...
Click to collapse
We have two partitions so that if one fails the other can safely boot however most of us are careless and flash on both partitions so it's not really helpful for us

How to root gt 2 running on pixel os?

_PsyDuck_ said:
How to root gt 2 running on pixel os?
Click to expand...
Click to collapse
extract the pixel os file & patch the boot image using magisk & flash the magisk patched boot image

Thanks

Database Develop

welcome