Files are here: https://www.mediafire.com/folder/7wjjhuada4b0p/ZenFone_2_PreRootSystemImages
https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw (repack and split to 200MB per file with md5sum)
Just grab it, unzip, use fastboot to flash into the phone, update the su binary and reboot.
Caution: You may lose root after OTA update
Caution: YOU SHALL NOT APPLY OTA UPDATE or you will restore stock ROM to avoid boot loop
Currently we have
550ML
Z008_2.12.40.11_preroot_system.zip
Z008_2.13.40.11_preroot_system.zip
551ML
Z00A_2.12.40.11_preroot_system.zip
Z00A_2.13.40.13_preroot_system.zip
For 500CL I need someone brave enough, since the format of the stock ROM is different
Tools for packing system.img sit here: https://github.com/shakalaca/ZenFoneSystemImageCreator/tree/5.0
For other part of phone images: http://www.mediafire.com/folder/setyy42t2cymy
Mirrors and suggestions are welcome
#Reserved
2015-05-11
* Add Z00A WW 2.15.40.13 in MEGA (system.img / boot.img / droidboot.img / recovery.img)
* Add Z00A CN 2.16.40.10 in MEGA (system.img / boot.img / droidboot.img / recovery.img)
* Add Z008 WW 2.15.40.13 in MEGA (system.img / boot.img / droidboot.img / recovery.img)
* SuperSU updated to 2.46
2015-04-29
* Add Z00A WW 2.15.40.10 in MEGA (system.img / boot.img / droidboot.img / recovery.img)
* Add Z008 WW 2.15.40.11 in MEGA (system.img / boot.img / droidboot.img / recovery.img)
Starting from this version the OTA process will always check if the recovery and system are the same version. Flash recovery.img and do not update SuperSU & su binary if you want to apply next OTA update.
2015-04-28
* Add Z00A WW 2.14.40.19 in MEGA (system.img / boot.img / droidboot.img / recovery.img)
* Add Z008 WW 2.14.40.17 in MEGA (system.img / boot.img / droidboot.img / recovery.img)
Those two builds are safe to apply OTA, but remember: DO NOT UPDATE SuperSU and su binary
shakalaca said:
Files are here: https://www.mediafire.com/folder/7wjjhuada4b0p/ZenFone_2_PreRootSystemImages
Just grab it, unzip, use fastboot to flash into the phone, update the su binary and reboot.
Current we have
550ML
Z008_2.12.40.11_preroot_system.zip
Z008_2.13.40.11_preroot_system.zip
551ML
Z00A_2.12.40.11_preroot_system.zip
Z00A_2.13.40.13_preroot_system.zip
Tools for packing system.img sit here: https://github.com/shakalaca/ZenFoneSystemImageCreator/tree/5.0
Click to expand...
Click to collapse
AWESOME!!! Thank you soooooo much for your effort.
Thanks! I wonder how easy it would be for someone to create a CM or AOKP rom now that we are rooted.
As soon as we have a custom recovery my ZF2 will be Broken!!
Sent from my Nexus 7
Hi, how can I use fastboot to flash it on my zenfone 551ML ? Please anyone give a more detail guide, thanks
tuilalnvinh said:
Hi, how can I use fastboot to flash it on my zenfone 551ML ? Please anyone give a more detail guide, thanks
Click to expand...
Click to collapse
What system are u running?
---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------
tuilalnvinh said:
Hi, how can I use fastboot to flash it on my zenfone 551ML ? Please anyone give a more detail guide, thanks
Click to expand...
Click to collapse
http://www.asus-zenfone.com/2015/04/asus-zenfone-2-pre-root-systemimg.html?m=1
I don't know about him but I'm using OSX. It's always fun to root things on my Macbook.
Sarcasm. Hah.
lordpipa said:
What system are u running?
---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------
http://www.asus-zenfone.com/2015/04/asus-zenfone-2-pre-root-systemimg.html?m=1
Click to expand...
Click to collapse
Thanks, i could get root now [emoji1]
Btw, do we could still get OTA update after root as OP mentioned ?
tuilalnvinh said:
Btw, do we could still get OTA update after root as OP mentioned ?
Click to expand...
Click to collapse
read carefully...you can ota update but you'll lose root.
shakalaca said:
Files are here: https://www.mediafire.com/folder/7wjjhuada4b0p/ZenFone_2_PreRootSystemImages
Just grab it, unzip, use fastboot to flash into the phone, update the su binary and reboot.
Caution: You may lose root after OTA update
Currently we have
550ML
Z008_2.12.40.11_preroot_system.zip
Z008_2.13.40.11_preroot_system.zip
551ML
Z00A_2.12.40.11_preroot_system.zip
Z00A_2.13.40.13_preroot_system.zip
For 500CL I need someone brave enough, since the format of the stock ROM is different
Tools for packing system.img sit here: https://github.com/shakalaca/ZenFoneSystemImageCreator/tree/5.0
For other part of phone images: http://www.mediafire.com/folder/setyy42t2cymy
Mirrors and suggestions are welcome
Click to expand...
Click to collapse
If root is successful, then I guess bootloader is unlocked? Is it just a process of flashing our boot.img and flashing it back to original if it doesn't work? Same with system.img or does it need to be signed? Sorry it's been a very long time since I developed kernels but I just got this phone and somehow this tickled my curiousity
in general section someone posted this http://www.unlock-bootloader.info/2015/02/asus-zenfone-2-ze551ml-6917.html
i wonder if this is true.i dont heve the phone yet but i think things are going fast!!!
glockaki said:
in general section someone posted this http://www.unlock-bootloader.info/2015/02/asus-zenfone-2-ze551ml-6917.html
i wonder if this is true.i dont heve the phone yet but i think things are going fast!!!
Click to expand...
Click to collapse
Don't think this is true, just looking at the dates of the comments, it doesn't add up. I have a feeling that doesnt a fastboot oem unlock (with a droidboot.img) can brick the device. BTW, I have compiled a kernel using the instructions by ASUS but I need help. It gave me an output of kernel and bzImage (both have the same size as the default zImage). I used the kernel and renamed it to zImage and then compiled it using the Android kitchen. It created a boot.img.... unfortunately flashing this via fastboot could brick the device especially if the bootloader is locked. Unless of course, if ASUS gave us an unlocked bootloader and we just don't know it
clemsyn said:
Don't think this is true, just looking at the dates of the comments, it doesn't add up. I have a feeling that doesnt a fastboot oem unlock (with a droidboot.img) can brick the device. BTW, I have compiled a kernel using the instructions by ASUS but I need help. It gave me an output of kernel and bzImage (both have the same size as the default zImage). I used the kernel and renamed it to zImage and then compiled it using the Android kitchen. It created a boot.img.... unfortunately flashing this via fastboot could brick the device especially if the bootloader is locked. Unless of course, if ASUS gave us an unlocked bootloader and we just don't know it
Click to expand...
Click to collapse
I'm quite new to the Android scene, I was a bit more of a Windows Phone kind of guy. I'd feel like we've got an unlocked bootloader since it's the first time I've ever seen a manufacturer make kernel sources available for a particular phone... maybe I'm wrong? Perhaps shooting an email asking about it?
TW version
I have a ze551ml TW version and I'm worried the WW version of these images will brick me. Could you explain how you pulled these off the phone?
I've used fastboot to mount the /system as rw and push superuser.apk and su over to the phone, but stuck actually gaining root in order to dump the partitions. Your help would be greatly appreciated.
ddfault said:
I have a ze551ml TW version and I'm worried the WW version of these images will brick me. Could you explain how you pulled these off the phone?
I've used fastboot to mount the /system as rw and push superuser.apk and su over to the phone, but stuck actually gaining root in order to dump the partitions. Your help would be greatly appreciated.
Click to expand...
Click to collapse
I have the TW too. The OTA update on April 7 is WW and it went without a hitch. I confirmed flashing the prerooted.img and have root no problems.
lordpipa said:
I have the TW too. The OTA update on April 7 is WW and it went without a hitch. I confirmed flashing the prerooted.img and have root no problems.
Click to expand...
Click to collapse
My worry is LTE firmware/bands are different between the WW and TW so the modem/chipset may not be 100% the same. I'm fine with flashing it, but I want to dump my bootloader/recovery/system beforehand.
ddfault said:
My worry is LTE firmware/bands are different between the WW and TW so the modem/chipset may not be 100% the same. I'm fine with flashing it, but I want to dump my bootloader/recovery/system beforehand.
Click to expand...
Click to collapse
I see what you mean. It was weird to me that the update would come in WW and not TW.
lordpipa said:
I see what you mean. It was weird to me that the update would come in WW and not TW.
Click to expand...
Click to collapse
The TW phone came with 2.13.40.13. If and when they drop a new build I'm sure they will include all the flavors. For now though, it doesn't help us.
Related
This thread is strictly for info regarding Root/Twrp/Roms
If you have any ideas or have tried anything please post here
I AM IN NO WAY A DEV ,i am using google and common sense
Here is the link to the sprint boot.img (https://drive.google.com/file/d/0B9Vkl8ldvnNdOGlyLW4wOXNDRUk/view?usp=drivesd)-Thanks to @XirXes
Heres what i have tried
-So far i have tried signing the sprint boot.img to magisk with no luck,it gives me files are read only errors.I was able to get past the the first two steps of this post for systemless root via adb (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
-Flashing the stock sprint boot.img to confirm compatibility hint hint its compatible
ROOT HAS BEEN ACHEIVED!!
UPDATE- As of 9/13/17 we now have root in the form of a patched boot.img thanks to @themustached for patching the boot.img so gracefully for us
To install the boot img you need to reboot to fastboot and run the command "fastboot flash boot (name of boot.img).img
https://drive.google.com/file/d/0B8kodjBRTHoZR2Zob1VLX0xOVkU/view?usp=sharing
Just a update as I have been away from this phone for a bit
We have kernel source now (like 2 months ago) and there are 3 AOSP ROMs that I know about being worked on so far I don't know any details or anything but what I do know is that they completed the build process they are working on getting it running on our phone
joemossjr made the the ncp Rom and got TWRP for us so big thanks to him!
Substratum works on legacy with root and newest version of TWRP just in case anyone was wondering.
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
joemossjr said:
https://pastebin.com/uk8uCTX2 created one!
---------- Post added at 12:36 AM ---------- Previous post was at 12:31 AM ----------
https://drive.google.com/file/d/0B1tqDJm_qQf4Y2VibG5fZ3NzZmc/view?usp=sharing
Click to expand...
Click to collapse
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
altimax98 said:
Booted but no root
Also when toying around do not do Fastboot flash, do fastboot boot. We dont have a clean T Mobile kernel and could really wind up in a bad place due to a bad flash.
Click to expand...
Click to collapse
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
I have insurance and I'm willing to risk my device worst case,it's not a problem,I've noticed if you boot it,it doesn't like to set correctly
joemossjr said:
i tried flashing to the a and b partition no luck used the magisk 13.6 thinking we need to get hold of the pixel magisk
Click to expand...
Click to collapse
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Downloaded them all found no recovery
Verified ATT & Sprint boot.img works om Tmobile
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
bart bart said:
Ok I have verified these 2 posted images boot ok on the TMobile Z2 Force. What do I need to do to use fastboot to extract system images? I cant use adb to get any system partition yet. I dont have the info, I tried to use adb and it would not let me read /dev/ permission denied. If you tell me what to do from fastboot or adb I can dump it, bootloader is already unlocked. Thanks!
Click to expand...
Click to collapse
We are all in this situation. It is likely going to be quite some time before we get root due to the dual partition system.
Based on the Pixel info, we need TWRP first
Sent from my Moto Z (2) using Tapatalk
The recovery is in the boot.img of 7.1 and up devices
Dumper US Cellular Boot.img
altimax98 said:
I totally forgot about the dual partitions with this.
We really need the stock recovery to get TWRP built. Even the Sprint/AT&T versions should be fine
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Here is dumped boot.img of US Cellular Boot.img. There is a recovery under sbin folder. Hopefully you can make a bootable TWRP from it?
https://www.dropbox.com/s/hjfr8wj2da...ootus.zip?dl=0
If anyone wants to join our efforts the let us know and we can add you in
I want to join your efforts.
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
joemossjr said:
Figured I'd give a status update on people looking for root. So as it looks roots gonna have to be put on the back end for right now as magisk isn't updated to 13.6 for the Google pixel it's on 13.4 which means we can't use the 13.6 manual boot image patching funtionallity. The reason we are using the pixel is because as of right now it's the only other device to use the a and b partitioning that has magisk. So what this all means is we need to try to get twrp going so we can at least get backups going and pre rooted roms. I personally have pmed everyone I could with little to no response. I'll update when I get any responses.
Click to expand...
Click to collapse
Thank you
Sent from my SM-N930F using XDA-Developers Legacy app
Deleted
Any progress? Anything I can do to help? I have T Mobile variant with unlocked bootloader.
We brought in another guy from the pixel forum who made their twrp recovery he's going to take a look and see what can be done
Question before I delve further.
fastboot -i 0x2b4c flash:raw boot <kernel> [ <ramdisk> ] rather than just flash <partition> [ <filename> ] perhaps for the twrp? Just a spit ball idea as I wrap my head around. Been a few years since I bothered with phones rather than.. other systems. I'm sure this round probably already been tried but curious of the turn before I fry the new toy xD.
joemossjr said:
If anyone wants to join our efforts the let us know and we can add you in
Click to expand...
Click to collapse
I can test stuff when the time comes.
I am not responsible if you break your phone in any way, these are here for your aid. I will help as much as i can, but it is on YOU, the user to read the OP and understand exactly what it is you are doing at ALL times.
READ THIS: http://mata.readthedocs.io/en/latest/ LEARN FROM IT, DONT EVEN CONTINUE UNLESS YOU HAVE READ THIS
These can be used to return to 100% stock as long as you can get into fastboot mode on the device, and have unlocked the bootloader and critical partitions. All images contained in the zips are directly from the essential Fastboot zips and OTA's, and dumps for the rest
Prerequisites:
1. Working fastboot environment in bootloader: (test using the command fastboot devices should return your s/n) Windows drivers are at the bottom of the OP.
Essentials windows drivers contain working ADB/Fastboot and places an environment variable to link to these binaries, i would HIGHLY recommend ditching any and all adb/fastboots you may have (minimal, HTC, etc) and use what is supplied by essential, they just work (Not gonna help you either if your hellbent on using your adb/fastboot).
The zips contain all the firmware (19 Images), TWRP11.img (the latest version), and a stockboot.img (so you can conveniently place on your phone and flash in twrp) when rooting with magisk, and boot.fix.red.img (In case you kill verity).
2. Bootloader unlocked: run the command fastboot flashing unlock in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock will relock the bootloader. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
3. Critical partition unlocked: run the command fastboot flashing unlock_critical in bootloader (THIS WIPES USER DATA, BACKUP BEFOREHAND), conversely fastboot flashing lock_critical will relock the critical partition flashability. I dont recommend this, as there are lots of bricks from messing up a flash and locking yourself out afterward.
4. Common Sense: Use IT!!!!!
Downloads
Android 10 BTS Folder: https://sourceforge.net/projects/mata-bts/files/10
Q Beta BTS Folder: https://sourceforge.net/projects/mata-bts/files/Q-Beta/
Pie BTS & Novendor Folder: https://sourceforge.net/projects/mata-bts/files/Pie
P Beta BTS: https://sourceforge.net/projects/mata-bts/files/P-Beta/
Oreo BTS & NOVENDOR: https://sourceforge.net/projects/mata-bts/files/Oreo/
The Files below are OLD as dirt BTS
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
OPM1.170911.130 mega.nz (oreo 8.0 beta)
NMK32F AFH (latest nougat 7.1)
NMJ88C mega.nz (nougat 7.1)
NMJ51B AFH (nougat 7.1)
NMJ32F AFH (nougat 7.1)
NMJ20D mega.nz (nougat 7.1)
NMI81C AFH (nougat 7.1)
Drive Folder of Patched Essential Boot images Credit Goes to @dazeone
Some OLD AS DIRT Novendor zips aswell... if anyone still cares
OPM1.180104.010 mega.nz (oreo 8.1 beta1)
OPM1.170911.254 mega.nz (oreo 8.0 beta3)
OPM1.170911.213 mega.nz (oreo 8.0 beta2)
Windows Drivers
drivers
Unzip this and check out the flash-all.[bat,sh] scripts for win/lin (they're identical but provided for easier flashability).
They're set up to flash to both slots. Most people will want to do this on a back to stock mission, but they can be adjusted if your goal is something else.
If coming from some other rom, you're also going to want to wipe your data, or you're not going to boot. This can be accomplished by the command in the bootloader: fastboot -w keep in mind there are multiple scripts to wipe for you in the zips.
These can also be used to make custom roms/rooted boot images/etc too, so have fun with it!
Thanks:
@invisiblek - aer0zer0 stole his thread, he put most of it together
@aer0zer0 - i stole the thread from aer0, his 2yr old son makes more use of the PH-1 than he does.
@bmg1001 - Root thread, found here root
@dazeone - Provides independent patched boot images and has an awesome YouTube Channel of Guides! DazeOne Youtube Channel
Enjoy
Heck ya
Yesssss
Ill be giving this a shot in a few days hoping to return my phone back to complete stock.
Hot diggity... been fun reading/watching you all work on this through Discord, think I'll go ahead and unlock it while I still have my S8 in case I trash things
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
vekenti said:
Anyone planning on trying to make some custom roms for this phone? I am waiting to see if there will be any decent dev community for this phone before I actually buy it.
Click to expand...
Click to collapse
Lineage okay for you lol?
You've got one of the top devs on Lineage working on this so I think you're good.
Thank you! I'll be rooting now that we have a safety net!
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
invisiblek said:
So as we're still waiting for Essential to release official factory images, I thought it'd be helpful to link the dumps that we've produced. These can be used to return to 100% stock as long as you can get into fastboot mode on the device.
Click to expand...
Click to collapse
Thanks for this. My fingerprint sensor was not working for some reason after rooting and I thought i would go completely stock. This thread helped me to go completely stock and get the fingerprint back to working.
Thought I haven't locked the bootloader yet. Will try it later.
---------- Post added at 05:55 AM ---------- Previous post was at 05:48 AM ----------
sarcoptic said:
I am trying this out now got a lot of errors saying:
FAILED (remote: Flashing is not allowed for Critical Partitions
However the main partitions like modem and system seem to work fine.
Click to expand...
Click to collapse
For flashing to critical partition you need to unlock them. The command is similar to unlock boot-loader.
Code:
fastboot flashing unlock_critical
And to lock it again
Code:
fastboot flashing lock_critical
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
sarcoptic said:
The unlock_critical command worked fine....have you tried updating to the latest build from essential? I tried a couple times and I keep getting a installation problem.
Click to expand...
Click to collapse
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Freaking rockstar thanks!
invisiblek said:
New zip on the way. I know why that is. The system image was modified (I had forgot I mounted it once which broke its signature).
I'll update once its ready. Sorry about that.
EDIT: OP updated with new link. Again, sorry about that. Slight oversight. With the new zip the OTA will take fine.
Click to expand...
Click to collapse
Thanks mate.
Thanks for the dump! Just yesterday I was trying to figure out how to do the adb backup command but I gave up cause I couldn't get a good reliable connection to my phone (driver issues, then to failed to connect to device, then to using the adb shell and a mouse on recovery, fun times.)
Great
please can someone guide on how to root it
chambar said:
please can someone guide on how to root it
Click to expand...
Click to collapse
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
charlie.s said:
I'm not sure how you missed this:
https://forum.xda-developers.com/es.../guide-rooting-essential-ph-1-magisk-t3701976
Click to expand...
Click to collapse
Much appreciated, indeed dunno how i missed it.
free XDA points for @invisiblek .......Thanks for putting it all together, hopefully you can get a teiko sports watch when you turn all the points in, LOL
Seriously, thanks for putting it all together
Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from [U]Stock WW-15.2016.1804.252[/U] on primary device. Also I will try to help out in case of issues.
If on Custom Rom then visit THIS THREAD to first return back to Stock Rom.
If you want to DOWNGRADE then visit THIS THREAD to revert to older firmware.
This thread is for those who are on stock rooted rom with TWRP installed and want to have system update WITHOUT LOOSING DATA.
How to ,
Backup important app data like whatsapp chats etc. (precautionary step & is not needed, but better be safe).
Download latest modified system update file - WW-15.2016.1902.340.
Download decrypt.zip from HERE.
Download Magisk from HERE .
Reboot to TWRP.
Flash the ROM file.
Flash decrypt.zip file.
Flash Magisk zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
No partition is required to be wiped before or after flashing these files.
Also you do not have to uninstall Magisk before the procedure.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
Older full firmware packages :
WW-15.2016.1805.309 (14th June 2018)
WW-15.2016.1805.311 (04th July 2018)
WW-15.2016.1805.316 (16th July 2018)
WW-15.2016.1805.318 (23rd July 2018)
WW-15.2016.1808.323 (21st August 2018)
WW-15.2016.1808.326 (06th Sept 2018)
WW-15.2016.1808.327 (20th Sept 2018)
WW-15.2016.1809.331 (17th Oct 2018)
WW-15.2016.1810.334 (02nd Nov 2018)
WW-15.2016.1810.337 (20th Nov 2018)
WW-15.2016.1811.338 (19th Dec 2018)
WW-15.2016.1901.339 (22nd Jan 2019)
.A.V.i.n.a.S.h. said:
Modified full firmware packages (New packages will be added as they are available on Asus site) :
WW-15.2016.1805.309 (24th June 2018)
Click to expand...
Click to collapse
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Tolay said:
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Click to expand...
Click to collapse
I am on data pack right now .. tomorrow I will have WiFi access.
I will download and compare ZB602KL version full rom and reply back if I find a difference.
As far as I know, both versions are same but let me check once. I will let you know
first i remove my magisk or not,or flash without removing magisk
plz tell me full procedure to flash
.A.V.i.n.a.S.h. said:
I am on data pack right now .. tomorrow I will have WiFi access.
I will download and compare ZB602KL version full rom and reply back if I find a difference.
As far as I know, both versions are same but let me check once. I will let you know
Click to expand...
Click to collapse
Same here , ZB602KL variant.
Courious about different..
rajesh.880889 said:
plz tell me full procedure to flash
Click to expand...
Click to collapse
Yes .. flash without removing Magisk as we do not want to setup Magisk again.
We will reflash Magisk during installation.
Please follow given sequence of flash .. Rom - Decrypt - Magisk :good:
Tolay said:
Will this Mod Rom work on indonesian version (ZB602KL) ?
I am on custom rom now and would like to back to stock and still rooted with this modified rom.
Thanks
Click to expand...
Click to collapse
Please refer to other guide -- [ROM][STOCK][ZB601KL/ZB602KL] TWRP flashable Stock ROM
This guide is for those who are on Stock ROM. Process is little different.
Randyshare said:
Same here , ZB602KL variant.
Courious about different..
Click to expand...
Click to collapse
The method is applicable for both ZB601KL and ZB602KL .. Confirmed
how to flash rom steps
plz steps for rom flashing what to delete what to have,
i am on stock rom and magisk installed
rajesh.880889 said:
plz steps for rom flashing what to delete what to have,
i am on stock rom and magisk installed
Click to expand...
Click to collapse
Please follow the steps as in first post.
You should have TWRP along with Stock rom which you have I believe.
Download the 3 files mentioned in first post - ROM + Decrypt + Magisk and keep them in storage.
Reboot to TWRP and flash files in below seqeunce -
Stock_X00T_Patch_May_Version_309_TWRP.zip
decrypt.zip
Magisk-v16.0.zip
Do not wipe anything in TWRP before or after installation .. do not uninstall Magisk or anything else.
Just flash the files are reboot.
Other than the changes to the update script, are there any other changes you have done? The script output in twrp says 'patching system image that is modified by ....."
So I am wondering if you made changes to the system.img file too?
candiesdoodle said:
Other than the changes to the update script, are there any other changes you have done? The script output in twrp says 'patching system image that is modified by ....."
So I am wondering if you made changes to the system.img file too?
Click to expand...
Click to collapse
No changes .. it is just for testing .. I have not created the entire ROM so I mentioned this is Guide section and not the ROM development section.
Also the new file I have updated has no such message but just a message to identify the ROM change. You must have the old version which was there on Sunday.
.A.V.i.n.a.S.h. said:
No changes .. it is just for testing .. I have not created the entire ROM so I mentioned this is Guide section and not the ROM development section.
Also the new file I have updated has no such message but just a message to identify the ROM change. You must have the old version which was there on Sunday.
Click to expand...
Click to collapse
I downloaded last night only. About 24 hrs ago. I am referring to the first line In the script. See the SS
Also who made the new zip? I am interested in finding out what changes are being made if any other than the updater script.
candiesdoodle said:
I downloaded last night only. About 24 hrs ago. I am referring to the first line In the script. See the SS
Also who made the new zip? I am interested in finding out what changes are being made if any other than the updater script.
Click to expand...
Click to collapse
New zip name - Stock_X00T_Patch_May_Version_309_TWRP.zip
As already mentioned, the message was put just to let me know if the flashed file is changed one or original one from Asus.
I am taking Asus original rom and doing modification in update-script and if needed will make changes to boot.img (replacing with old boot image from Asus) and any other file to keep Magisk+TWRP to be working after update. I test the update for some time and then share it with all.
I will mention any substantial changes if any (for v309 no changes are there).
I have no intention to change what Asus has provided.
Purpose is to provide stock tested firmware for easy update at one stop .. and an easy way for people to come back to stock ROM.
.A.V.i.n.a.S.h. said:
New zip name - Stock_X00T_Patch_May_Version_309_TWRP.zip
As already mentioned, the message was put just to let me know if the flashed file is changed one or original one from Asus.
I am taking Asus original rom and doing modification in update-script and if needed will make changes to boot.img (replacing with old boot image from Asus) and any other file to keep Magisk+TWRP to be working after update. I test the update for some time and then share it with all.
I will mention any substantial changes if any (for v309 no changes are there).
I have no intention to change what Asus has provided.
Purpose is to provide stock tested firmware for easy update at one stop .. and an easy way for people to come back to stock ROM.
Click to expand...
Click to collapse
Thanks for confirmation. Great work
update ota automatic
hey after i follow your guide, can i get automatic update ftom system udpate?
hi.
can you make a guide on how you modify the zip file?
i successfully used it to update from 247 to 309
Kionaru said:
hey after i follow your guide, can i get automatic update ftom system udpate?
Click to expand...
Click to collapse
You will get update notifications .. no issue. But the update will not flash if you have TWRP and Magisk.
I will provide TWRP flashable file (after testing) in this thead in future. So expect the update within 48 hrs after new update (full ROM for the OTA) is relased by Asus.
To flash OTA there is an excellant guide HERE you can follow that to flash OTA (i.e. delta file). In this thread you can get full file.
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from [U]Stock WW-15.2016.1804.252[/U] on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is for those who are on stock rooted rom with TWRP installed and want to have system update WITHOUT LOOSING DATA.
If you are coming from Custom ROM then
How to ,
Backup important app data like whatsapp chats etc. (precautionary step & is not needed but better be safe).
Download modified system update file from
[*]Download decrypt.zip from
[*]Download Magisk from
[*]Reboot to TWRP.
[*]Flash the ROM file.
[*]Flash decrypt.zip file.
[*]Flash Magisk zip file.
[*]Reboot & Enjoy.
[*](optional) If you want to boost up by debloating then
No partition is required to be wiped before or after flashing these files.
Also you do not have to uninstall Magisk before the procedure.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
Dude, i'm on Stock - 14.2016.1804.305 with TWRP & Magisk. will it work on me?
Thanks
boneyd26 said:
Dude, i'm on Stock - 14.2016.1804.305 with TWRP & Magisk. will it work on me?
Thanks
Click to expand...
Click to collapse
Yes .. it is for all those who are on stock ROM.
You can update from any past version i.e. v247,v252 &v305 to v309
Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks
smeogle said:
Hello all,
I was wondering if there has been any development / root process for the E5 Play XT1921-1?
Thanks
Click to expand...
Click to collapse
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
I will give it a go, thank you for your info!
smeogle said:
I will give it a go, thank you for your info!
Click to expand...
Click to collapse
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.
MotoJunkie01 said:
To play it completely safe, instead of actually flashing TWRP as an initial step, use the boot-only method:
fastboot boot twrp.img
This way, you can ascertain whether the TWRP build functions on your device normally before flashing the /recovery partition.
Click to expand...
Click to collapse
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.
MotoJunkie01 said:
Very glad you tried and confirmed this. I'll add the info to my stock ROM thread regarding the intercompatability between these two devices.
Click to expand...
Click to collapse
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.
smeogle said:
Upon further use, there is some stability issues. When I navigate to Settings -> System -> About Phone -> Hardware Information, the popup 'Motorola Settings has stopped' appears. Additionally, camera doesn't launch.
Click to expand...
Click to collapse
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.
MotoJunkie01 said:
Interesting. That would appear to indicate some minor differences between the two devices in terms of firmware configurations. Try this, using the factory firmware package for your device, flash the /boot and /oem partitions only (since the camera drivers are located in /boot). Then boot into TWRP recovery and flash Magisk (or a no-verity script) in order to disable dm-verity and for root patching. Wipe the cache and Dalvik and reboot system.
If that doesn't do the trick, do a clean firmware install and do a TWRP dump of your system image and /boot partition. Upload them to a host like Google Drive, send me a link, and I'll build you a TWRP flashable stock ROM specifically for xt1921-1.
Click to expand...
Click to collapse
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!
smeogle said:
After following the flash boot and oem steps, it got caught in a bootloop. Once that occurred, I wiped and reflashed your stock rom (followed by Magisk). Once it booted again, the previously mentioned instability (camera and hardware settings) have disappeared. Good job!
Click to expand...
Click to collapse
Give me a TWRP backup of your system image and boot partition and I'll make a TWRP flashable stock ROM for the XT1921-1.
Thanks for testing. I'll add the intercompatability info to my stock ROM and firmware threads.
Unlocking Bootloader on XT1921-1
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
dcluvsme said:
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
---------- Post added at 09:57 PM ---------- Previous post was at 09:46 PM ----------
Just wondering how you unlocked your Bootloader??? Motorola site states it is unlockable?
Click to expand...
Click to collapse
I followed the guide the on the following Motorola website:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Thanks
smeogle said:
I followed the guide the on the following Motorola website:
Click to expand...
Click to collapse
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.
dcluvsme said:
Using Linux, I was refused, did the exact same thing in Windows,and it worked.
Who knows.
Thanks for the tip.
Click to expand...
Click to collapse
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?
smeogle said:
When you tried in Linux, what do you mean it did not work? I performed mine with Linux Mint. Did you get any specific error? How did you install adb and fastboot?
Click to expand...
Click to collapse
I used Puppy Xenial,but I also have Linux Mint. I am sure it was an error on my part. No worries.
smeogle said:
Well, it worked!. I had to flash your stock ROM in TWRP due to it being stuck in a bootloop, but overall, it runs well! I guess the steps outlined for 1921-5 are confirmed to work for XT1921-1. Thank you again for your help!
Click to expand...
Click to collapse
can u please help me i think im stuck in the same boat you were in
MotoJunkie01 said:
If you have unlocked your bootloader, you should be able to use @CodyF86's TWRP and root method from this thread. https://forum.xda-developers.com/mo...very-twrp-moto-e-5-play-james-t3796323/page23
The xt1921-1 appears to be the unbranded variant of xt1921-5.
Click to expand...
Click to collapse
is there a way to do it without twerp? my phone is in a boot loop i installed the wrong rom i think i cant find the correct one for this phone.
LG G6 Oreo 20a
Note: I know someone created a complete flashable, But I wanted all 3 packages like @autoprime does.
WARNING: Understand my meanings behind, B1,B2 and C1, C2:
B1: Means Bootstock with LAF
B2: Means Bootstock without LAF (Normally H872 users have TWRP on LAF)
C1: Means Complete with LAF
C2: Means Complete without LAF (Normally H872 Users have TWRP on LAF)
All zips check contents with sha1, all zip files are md5hash listed:
LG-H872_Oreo-20a_Bootloader_B1.zip (W/LAF) [md5hash:a52e86bd30ca0b4725c1839eb1ad38d3]
LG-H872_Oreo-20a_Bootloader_B2.zip (WO/LAF) [md5hash:7c72ae1f5b82ba54dcc9b7007754ebf9]
LG-H872_Oreo-20a_Modem_Only.zip (Safe Either Way) [md5hash:2f3ad7cd2c468a0d50f52094ad2643f6]
LG-H872_Oreo-20a_Complete_C1.zip (W/LAF) [md5hash:172d01c25cc308a1c2c39def6d13918e]
LG-H872_Oreo-20a_Complete_C2.zip (WO/LAF) [md5hash:7b17a29044d98fe1883ec9fe0e9c9b93]
DOWNLOADS:
LG-H872_Oreo-20a_Bootloader_B1.zip (W/LAF)
LG-H872_Oreo-20a_Bootloader_B2.zip (WO/LAF)
LG-H872_Oreo-20a_Modem_Only.zip (Safe Either Way)
LG-H872_Oreo-20a_Complete_C1.zip (W/LAF)
LG-H872_Oreo-20a_Complete_C2.zip (WO/LAF)
All Future Firmware Updates Will Be listed Here: lg-g6-stock-firmware/H872_T-Mo/
WARNING:
Complete's have unmolested system images But no Recovery. In other words, make sure you install magisk before rebooting,
or at least delete the recovery restorer in system...
please, can you create an flashable zip to downgrade the version bootloader to 11h?
I want to use your firmware AEX, but without a finger scanner, to live is not so good ....
or should I wait when you add support for 20a?
DmytroPitenko said:
please, can you create an flashable zip to downgrade the version bootloader to 11h?
I want to use your firmware AEX, but without a finger scanner, to live is not so good ....
or should I wait when you add support for 20a?
Click to expand...
Click to collapse
I think @autoprime already created and released a 11h bootstock....... im almost sure he did.........
Eliminater74 said:
I think @autoprime already created and released a 11h bootstock....... im almost sure he did.........
Click to expand...
Click to collapse
I think autoprime's bootstock is for 10h, and sadly I dont think people on ARB01 can't go back to that. I didnt realize that the bootstock is what is needed for the fingerprint issue. I will try to release an 11g bootstock that will do the same thing.
I'm sorry if this is a dumb question, but here goes: I get that the Complete images are unmolested, and I therefore assume, identical to what you get on a G6 from TMobile directly, just in Zip flashable format, but what does "Bootstock" mean? I did try googling the term, but it just defined "Bootlicking" for me, and I didn't find that helpful . I'd imagine that Bootstock means it's just the stock image stripped of all the bloat, but I'm not sure if that's wishful thinking.
Also, my H872 is bootloader unlocked, TWRP flashed to both Recovery and LAF, currently running the AOSP Extended ROM (which seems to be very problematic, at least for me), so if I choose any of the above, will they overwrite my recovery?
Thank you!
Tried flashing the C2 variant, and TWRP reported it failed verification. Also, downloaded the other ones to see. File size tells me what I need to know, LOL. Is there any way to use the complete zip versions as a base and pull out just the bloat, in order to get something more like a clean install? A point in the right direction would be greatly appreciated. I'm working on learning a lot more about Android
Thanks!
jasongw said:
what does "Bootstock" mean?
Click to expand...
Click to collapse
Its the entire bootloader, which normally contains laf and recovery.
I don't believe these include recovery images. just the optional laf.
By the way @Eliminator74 I did notice that the updater-script for the full stock zips tries to do a hash check of boot, modern, system, rct and persist from the /tmp/ directory which they are not extracted to. so the apply patch check fails.
jasongw said:
Tried flashing the C2 variant, and TWRP reported it failed verification. Also, downloaded the other ones to see. File size tells me what I need to know, LOL. Is there any way to use the complete zip versions as a base and pull out just the bloat, in order to get something more like a clean install? A point in the right direction would be greatly appreciated. I'm working on learning a lot more about Android
Thanks!
Click to expand...
Click to collapse
Can confirm this. I tried flashing C2 and it fails verification in TWRP. Then I tried B2 and that worked, but the Modem Only zip also failed verification. Is there any way to resolve this? Thanks.
Hi.
I recently flashed AospEX on my LG G6 H872 and went through the rooting method for this device where you install TWRP on you laf partition and then onto the recovery partition.
I want to get laf back to regular Download Mode.
I want to know if flashing this 20a bootstock (bootloader) with laf will not cause any problems to boot into the Aosp Extended Rom. I guess my question is, are they compatible?
Thanks in advance and thank you all who have contributed to rooting and unlocking this phone.
Links not working - Anyone got mirror ? @Eliminater74, are you able to help send/re-upload?
Same here. Does someone have a copy?