Related
Hi all.
I found this look through the Kindle thread.
I didn't know it existed until now.
Check it out...looks interesting.
http://www.youtube.com/watch?feature...&v=xMdj_QzfGmw
http://teamw.in/project/twrp2
Naice! Just read about this on AndroidPolice but didn't see that video, nice to see it working right off the bat on a Gtab
wow neat! I wonder what android kernel version this is based of off...
fosser2 said:
wow neat! I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
Yeah..I bit the bullet and DL it and followed directions.
I couldn't boot into recovery.
It hangs at the birds.
Normal boot runs the underlying ROM fine though.
I'm on a 1.2BL. Was running a series of FB from 8.0 to 10.1 without NVFlashing.
I had only factory reset and wipe and booted into Beasty/Clem Ultimate as the latest ROM. (This FROYO is very fast and stable btw...)
Tried the TWRP 2.0 but couldn't get it to work either.
It's on the YT video though. Obviously it works
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?
qkster said:
I wonder maybe they were on the 1.1 BL...
Anybody running 1.1BL confirm this recovery works?
Click to expand...
Click to collapse
Works fine on the 1.1 bootloader.
rajeevvp said:
Works fine on the 1.1 bootloader.
Click to expand...
Click to collapse
Yup, confirmed by Jazzruby.
only for 1.1 BL.
JR did emailed TeamWin re: possible 1.2BL application
thanks..
how do you like it btw?
Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al
aabbondanza said:
Looks like they just changed one of the 2 links...both were pointing to the same 1.1 file yesterday.
Now one points to twrp-harmony-12-2.0.0RC0.zip (1.2) & the other to twrp-harmony-11-2.0.0RC0.zip (1.1).
Al
Click to expand...
Click to collapse
will give it a try...thanks
fosser2 said:
I wonder what android kernel version this is based of off...
Click to expand...
Click to collapse
It's a (newly compiled) stock VS kernel for 1.1 and a clemsyn kernel for 1.2 bootloaders.
---------- Post added at 09:02 PM ---------- Previous post was at 08:45 PM ----------
qkster said:
JR did emailed TeamWin re: possible 1.2BL application
Click to expand...
Click to collapse
It's easy enough to insert a 1.2 kernel into any recovery partition since the both the boot and the recovery partition on the gTab has an identical structure (necessarily so).
1. Download any of pershoot's kernel zips.
2. Replace the kernel/zImage file in the zip file with either a stock 1.2 kernel from an existing recovery image (Or, just use pershoot's 1.2 kernel).
3. Edit META-INF/com/google/android/updater-script and
a) get rid of the lines involving /system
b) change the string "boot" to "recovery" in the first run_program() and the write_raw_image() directive.
4. Pack everything up into a zip file and then just flash it.
how do you like it btw?
Click to expand...
Click to collapse
Works as advertised.
Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.
timbck2 said:
Has anyone else gotten this to work? I flashed it and now I can't boot into recovery - my GTab just hangs at the three birds (with the message about the recovery key being pressed at the top left). I can boot into Flashback just fine, just not recovery. I'm on BL1.2, and I downloaded TWRP 2.0 for BL1.2 and followed the instructions.
Click to expand...
Click to collapse
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.
rajeevvp said:
This is a TWRP screwup. Both zip files have identical MD5/SHA1 checksums, which means that both have the same recovery image, and hence, the same kernel--ie. a 1.1 kernel.
This was the reason for my post, above.
Click to expand...
Click to collapse
Ah, I see. Did they give any indication when you contacted them that they were going to fix this? I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).
timbck2 said:
Did they give any indication when you contacted them that they were going to fix this?
Click to expand...
Click to collapse
Haven't contacted them--I'm running on a 1.1 bootloader, and, as I said, the problem is easy enough to fix on your own.
I don't know how to replace the kernel in the recovery.img file myself (I can't seem to find anything that can extract or mount the .img file so I can modify it).
Click to expand...
Click to collapse
You don't need any tools if you have a 1.2 kernel ready; otherwise you need the unpackbootimg program.
See post #9 and just use a pershoot 1.2 kernel.
I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.
timbck2 said:
I contacted them, and they say the zip downloads have been fixed. I checked, and the BL1.2 download has been updated. I can't try it until I get home this evening, but I will and I'll post the results.
Update: After NVflashing and then installing TWRP 2.0 from the new download, it works as advertised. Very nice! One thing I'm disappointed about is that it doesn't appear to recognize CWM backups.
Update #2: The next time I rebooted and tried to go into recovery, my GTab wouldn't boot again; it got stuck at the three birds image, and did NOT give me the message about the recovery key being pressed. Even worse, it refused to boot normally after this - essentially, it appears that TWRP soft-bricked my tablet. I'm NVflashing again and going back to CWM. Very disappointing.
Click to expand...
Click to collapse
Same here...
I had NVflashed back to 4349.
Comfirmed the stock 4349 worked.
Booted into cwm.
Wiped everything in cwm. Partition 4096 then back to 2048/0
Aplied the twrp update.
Booted into recovery.
TWRP 2 looks great. The menu and screen is responsive.
Tried wiping with it...looks good
I then flashed a rom with it...Beasty/Clem Ultimate to be exact.
Installation reported complete.
Booted up and...got the birds....nothing else...
Tried going back in recovery... recovery is also gone too...
Soft bricked...
Good thing I know how to nvflashed back to stock but for someone new to gtablet, twrp2 may be bad news.
I saw a few post with people having twrp2 installed...has anyone successfully install a rom with twrp?
I have gone total brick (no boot, no recovery) twice and both times TWRP2 was loaded. I can't prove it is the cause, but I never had that problem before even with heavy duty flashing of ROMs etc.
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
That has fixed it with no data loss every time for me.
Meanwhile, I've gone back to cwm.
Oh, I should say that TWRP2 did work most of the time. But sometimes I would reboot and just hang permanently until MSC gets reflashed.
I liked it in general, although it looked on the internal SD and not external like the version of CWM I have does. Would be nice to either pick or have a 2nd version. But if it keeps corrupting MSC and hanging the box, it isn't worth the trouble. CWM is clunky but fine.
wd5gnr said:
However, all you really need to do is clear the MSC partition.
Use the --getpartitiontable command in nvflash and figure out what your MSC partition is (mine was #7). Then grab a "stock image" and flash its MSC partition (look in the cfg file, usually 7 although my true blue stock was at 6) into partition 7 with --download.
Click to expand...
Click to collapse
It's better to wipe it clean using the ``--format_partition'' flag to nvflash instead of relying on someone else's partition images.
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh
Hello -
I encountered an issue with restoring a backuped image in TWRP
My phone doesn't have a password at all; even after ROOT
Decided to back up just in case i messed with something and have to revert to my old set up
Here are the steps I did -
1. Back up cache - dalvik - data
2. Tried restoring - restoration sucessful
3. after completely booting i was prompted on the locked screen a PIN option
4. Me - Clueless as i didnt put pin at all
Thanks in Advance
It seems that there were some bugs in initial releases of TWRP for ZenFone 3 Ultra by Shakalaca. Those bugs led to PIN issues that you've mentioned.
Check this link for all available releases of TWRP for ZenFone 3 Ultra by Shakalaca and download the latest release of TWRP:
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
Compare your release of TWRP that you were using with the latest release of TWRP. Probably you were using the older buggy release of TWRP.
Shakalaca is active in Taiwanese Asus forums:
https://www.asus.com/zentalk/tw/thread-216020-4-2.html
Test the newest release of TWRP and please let us all know.
Bob May said:
It seems that there were some bugs in initial releases of TWRP for ZenFone 3 Ultra by Shakalaca. Those bugs led to PIN issues that you've mentioned.
Check this link for all available releases of TWRP for ZenFone 3 Ultra by Shakalaca and download the latest release of TWRP:
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
Compare your release of TWRP that you were using with the latest release of TWRP. Probably you were using the older buggy release of TWRP.
Shakalaca is active in Taiwanese Asus forums:
https://www.asus.com/zentalk/tw/thread-216020-4-2.html
Test the newest release of TWRP and please let us all know.
Click to expand...
Click to collapse
Thank you - will go ahead and try it
@summerpastor
Have you solved the problem?
Bob May said:
@summerpastor
Have you solved the problem?
Click to expand...
Click to collapse
No nit yet, but i did install the latest from the link you gave me with last 2 digits of xxxx13. If i remember correctly the initial TWRP installation i did has xxxx8
ill post an update as soon as i have tried it
i cannot find anything on how to root this. everything i find is fake
piezan said:
i cannot find anything on how to root this. everything i find is fake
Click to expand...
Click to collapse
1. Use the Bootloader unlock tool provided by Asus.
2. Install TWRP.
3. Use TWRP to install SuperSU.
4. Enjoy your rooted phone.
If you want more specific instructions, read these forums a little more closely.
Thanks I actually found something, but I cannot download twrp for whatever reason. Any links or files would be appreciated.
Here is the download link to TWRP for ZF3U:
https://mega.nz/#F!9tEj2azZ!QKmvc-VJZR1Iqk6H7alQnQ
It is a Mega link with folders. I downloaded the latest dated version. Where you see OLD, thats where the recovery and boot images are in case you want to revert to original recovery. I have installed it successfully and rooted the phone but I messed my android 7 to 6 downgrade and have some issues with my device but you should be fine as long as you are not doing any downgrade. İf you want to read more aboit my issue i have posted it in detail in another thread and hope someone can help.
piezan said:
Thanks I actually found something, but I cannot download twrp for whatever reason. Any links or files would be appreciated.
Click to expand...
Click to collapse
Mega works just fine for me. Make sure to create an account and login before downloading from Mega.
However, I've uploaded the latest version of TWRP to Google Drive:
https://goo.gl/qLSKJr
Any idea WHY - after unlock, sucessfully loading SU and twrp - i can NOT get an img to load? All i get is the boot screen. I go back and try to load MM or nougat but still just get the boot screen. any ideas?
If someone could load a twrp backup (WW - not china) i think that twrp could load it from a backup.
help please !
.
hillg001 said:
Any idea WHY - after unlock, sucessfully loading SU and twrp - i can NOT get an img to load? All i get is the boot screen. I go back and try to load MM or nougat but still just get the boot screen. any ideas?
If someone could load a twrp backup (WW - not china) i think that twrp could load it from a backup.
help please !
.
Click to expand...
Click to collapse
Sorry to reply to an old thread, but I was just wondering if you ever figured this out? Or if anyone sent you twrp backup files?
No replies. I'm sorry that I took a while to get back too. In any event, I've managed to get the device in even worse condition. All i get now is a black screen and a vibration. The red LED will blink. That's it. I've read of a way to reload, but got another ultra & set this bricked one aside for another day. Such a shame this device got so little attention.
This is mainly a temporary repost of @rakomancha's TWRP announcement in a new thread. He is the maintainer of this TWRP but has not signed into XDA for a while. There is an updated TWRP that I wanted to share. When he comes back and creates his own thread, I will replace this post with a link to his.
-------------------------------------------------------------------------------------------------------------------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 3S 10 Z500M
The next big step forward for Z500M development is here!
This is the first working custom TWRP recovery for the Asus ZenPad 3S 10 Z500M [P027], based from TWRP v3.2.1.
diplomatic and I had both been working on a port separately, and I offered to test his version. In a few hours we worked out a functional and install-friendly version.
Please NOTE that this is NOT an official TWRP. After this post, I'll be working on making the port official and update here.
ACKNOWLEDGEMENTS
This project, and my own motivation, would not have been possible without the incredible work and input of:
diplomatic, who has been instrumental in propelling Z500M development forward. He worked on the issue of perm root and discovered and revealed important intricacies of the Z500M restrictive bootloader. By the end of Dec 2017, he developed a method to unlock the Z500M bootloader based on his amazing work with the Z380M. With amartolos as his testing assistant, the Z500M bootloader unlocking tool was quickly developed and released Jan 5th 2018.
overkillZ, who in Sept 2017 introduced us all to rooting the Z500M
toineh, who did legwork of establishing temp root by manipulating system permissions & redirecting files through adb. Then he took the boot.img posted by LGiki, explained how to patch it through Magisk and posted the first patched boot image. He also served as a guiding voice on this front.
amartolos, who first attempted perm flashing the patched boot image of toineh's method and worked with diplomatic on the developments afterward, which led us to today. Also has served as a guiding voice.
LGiki, who was the first to post an extracted WW_27 boot image that got things rolling forward
DISCLAIMER
This image has only been successfully tested by me at this point.
Please exercise caution and care when attempting to flash anything to your device.
You are completely responsible for any possible issues or damages resultant from undertaking the following procedures.
That being said, this image and method should be safe.
REQUIREMENTS
ZenPad Z500M tablet, upgraded to Android N
Bootloader Unlocked, using Diplomatic's tool. Tablet should be showing Orange State during initial bootup.
Root with Magisk installed, Permanent Root preferable
BACK UP YOUR INTERNAL USER DATA, in case you need to factory reset
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
Knowledge of adb/fastboot and basic Linux shell
INSTRUCTIONS
Ensure REQUIREMENTS are all met
Ensure to RE-READ all instructions and understand them before starting
Reboot into fastboot mode
do fastboot boot twrp-3.2.1-0-z500m.img, TWRP should boot up in a few seconds. The theme should be blue.
In TWRP, go to BACKUP and back up Boot, Recovery, Data, System and SystemImage. Full backup took me about 10GB of space.
Copy the created TWRP Backup to your PC or an external location for safekeeping
Copy the TWRP twrp-3.2.1-0-z500m.img to tablet storage if not done already.
In TWRP, go to INSTALL, select Install Image and choose the twrp-3.2.1-0-z500m.img. Installation should only take a few seconds.
Unplug from USB and Reboot back into Recovery through the REBOOT menu
If installation went well, TWRP should boot up in a YELLOW theme. From my testing, I'm confident it is functionally the same.
RESOURCES
In this shared folder are
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
version 0.5 of Diplomatic's Unlock Tool
diplomatic's Z500M device source
hxxps://mega.nz/#F!SQlyDapC!XbbW0fftZWFfVx2lmL_JUQ [down, get the file below]
GOING FORWARD
I successfully tested replacement of Magisk with SuperSU. My steps taken were:
"Completely Uninstall" Magisk through the Magisk Manager
reboot directly into Recovery
INSTALL a previously downloaded official SuperSU zip file & REBOOT
I very much enjoyed this process of developing for uncharted regions of Android technologies and I owe all of that to the existence of this forum and the people in it. Next, I am reading up on porting a custom ROM, LineageOS looked very nice. I'll update here with significant progress until I get capability to start new forum threads. Thank you all and enjoy delicious functional TWRP custom recovery on your Z500M for the first time in history. Here's to looking forward to development exploding on this device.
-------------------------------------------------------------------------------------------------------------------------------------------------------
NEW DOWNLOAD
Updated February, 2018
Fixes the yellow color rendering in installed mode
twrp-3.2.1-0-z500m.zip
ADDITIONAL WARNING: At first boot of TWRP, it will ask you if you want to keep system read-only. Touch the Keep Read Only button at this screen and only mount system in read-only mode if you need (rarely needed). This is necessary because of dm-verity and is no different than most Android 6+ devices. Unless you have unlocked your bootloader and installed permanent root with dm-verity disabled, mounting the system partition in r/w mode will make changes to it and your tablet will instantly become unbootable.
This is great. Tempted to try this. thanks for the effort!
Thank you very much, I did this and also switched to SuperSU with no problems!
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
ratus69 said:
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
Click to expand...
Click to collapse
Well, recovery of course. ...because it's a custom recovery.
Hey guys I hope you can help me I had my Z500m partially rooted using the patched Magisk boot method and accidentally erased some stuff before I could permanently root it. Everything snowballed and all I have now is my firmware stored on pc I can get to fastboot mode but I have stock recovery still. can i flash my firmware through fastboot? I’ve been researching and it seems with Mediatek it’s different or at least not as simple. All searches keep coming up for Zenfone and I’m lost. Apologies if Im in wrong area.
diplomatic said:
Well, recovery of course. ...because it's a custom recovery.
Click to expand...
Click to collapse
Well I'm glad having nothing done until I get a reply from the Master himself
Thanks a lot diplomatic !
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
mirek54 said:
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
Click to expand...
Click to collapse
hold volume + and - together for 10s
There was a time that it was unthinkable development. I appreciate the time that cames after. Nice tutorial!
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Hi, soleera,
To install TWRP, you must have some way to flash it and a bootloader that's either unlocked or doesn't care about unofficial images. I'm not sure that's possible in Z500KL. Look into that first. The Z500KL is about as much a version of this tablet as a Lenovo Tab4 is a version of this tablet. They are completely different platforms, just with a similar model name.
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
soleera said:
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
Click to expand...
Click to collapse
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
diplomatic said:
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
Click to expand...
Click to collapse
Sounds good, I'll see what I can do when I get the time.
For some reason one of the official unlock tools for a different model worked on my tablet - I believe it was for the ZE552KL, although I could be wrong since I can't seem to install it any more ("the package conflicts with an existing package by the same name"). I'm definitely unlocked though since I can flash using fastboot without any errors...
Since we now have official unlock. Any chance at custom roms for this device? I would love to see it get some oreo love.
soleera said:
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Click to expand...
Click to collapse
Hello soleera
Have you succeeded to port twrp to Z500KL?
Do you know of any custom recovery for Z500KL?
Do you know how to root it?
Dr.Ghobar said:
Do you know how to root it?
Click to expand...
Click to collapse
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
diplomatic said:
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
Click to expand...
Click to collapse
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Dr.Ghobar said:
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Click to expand...
Click to collapse
Basically, just do the procedure in this post. It's not that complicated. Reading through that thread may also help. Oh, and you have to unlock your bootloader first with an Asus unlock tool, as soleera has mentioned. I think the tool for the Z500M may work. It's essentially the same app for every device.
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said