So I realized that there wasn't much support out there for the padfone X. I love my padfone X regardless of its tiny battery, lack of developer support, and unpopularity. So I decided to embrace my love for tech and support the device myself.
So, Asus is still showing love to the padfone S(not X). That being the case it's the international version of the AT&T X; the hardware is almost identical. I decided to turn my X into an S, unlock the bootloader, upgrade to Android 5(I know its not the latest but it's better than 4.4.2), root and enjoy.
Breaking, bricking, whatever... This is all on you, this is what I did to my phone. I'm only sharing my experience. Make sure your phone is fully charged before you begin. Don't say I broke your phone, your taking a risk. I take no credit if this does or doesn't work. This process is time consuming and might not work for you. Don't blame me for wasted time.
This should give you carrier unlock as well.(not tested) and you should be able to use the Padstation with Lollipop. I'll leave download links below.
Steps
#1 back up all your data(titanium etc)
#2 download and run New Kingroot(took 5 tries to work)
#3 download and run superSume Pro
#3a step 3 should have installed SuperSU... Uninstall Kingroot & update SuperSU (use normal method); get a root checker and check root
#4 download a custom recovery(I personally like TWRP, but its buggy on this phone whatever) store the recovery.img on your phone's internal storage(not sd)
#5 install a flash tool(rashr or flashify will do) flash the custom recovery img.
#5a you should have root and custom recovery now, even if the bootloader is locked.
#6 The hard part. Put the S firmware on your internal storage(not sd card)
#7 in recovery mode you need to make another back up(back ups are awesome) do a factory reset in recovery(also wipe cache)
#7a install S firmware(do this in recovery mode) and restart phone. (Initial boot takes about 2 minutes). This might not work the first time(took 5 restores for me to finally get it)
Congratulations!!! You now have a "Padfone S"
#8 preferably using clockwork mod, install crowlock zip file by quarx to unlock bootloader
#9 to upgrade from 4.4.2 to 5.0 you need to go through about 4 updates from the Asus website. Follow this link(only use WW upgrades)
#10 after the upgrades you may have lost root. Just follow steps 2 and 3 again.
Asus "says" they will be releasing Android 6 for the Padphone S... Don't know how true that is, hope so. ENJOY!!!
Downloads and links
Kingroot:
http://www.appsandroidapk.com/tools/kingroot/
S firmware: thank you to tjsnooley!!!
http://forum.xda-developers.com/padfone-x/general/i-have-done-it-t3053207
TWRP/Cwm: thanks quarx!!!
http://quarx2k.ru/asus_padfone_s/recovery/
Crow Lock:
http://quarx2k.ru/asus_padfone_s/
Asus upgrades:
https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
The superSume Pro costs money, you'll have to find it on your own, sorry...
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Surgeman said:
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Click to expand...
Click to collapse
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
This is an other on how to do a conversion in a different way.
There are other guides that are written up that do the exact same thing.
I have also written a guide to do this as well if that helps, its kinda of different but it is comprehensive.
One difference is that to root the padfone x I did towelrootv1 (other versions don't work) because its easier and not worrisome by default. ( I haven't mentioned that because I assumed people have rooted it already and know what they are doing)
Another difference is that you don't need to keep updating the device to the latest, that's just wasting time.
You could just go from the at&t 4.4.2 version, to the absolute latest version of the padfone s firmware.
I just don't want to see any confusion out of this guide in general, but keep in mind that this is a similar but different guide to a conversion.
---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------
Surgeman said:
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Click to expand...
Click to collapse
Wait what device do you have?
Padfone x mini?
Thanks for the advice xtermmin but something has changed with the newer units.Flashify just crashes and if you fastboot flash the recovery you get this command has been stubbed.Also...towelroot won't even touch it for root now.I did manage to get it rooted with the intel tool with a temp cwm recovery,and flashed the SU zip beta.I have tried flashing the recovery with terminal emulator no go.If you boot with the intel temp cwm recovery and flash the Crowlock zip it errors out.I have followed several threads and so far nothing will tough it...Asus has been watching us....lol...
Oh the device is AT&T Padfone X mini by the way.
Surgeman said:
Thanks for the advice xtermmin but something has changed with the newer units.Flashify just crashes and if you fastboot flash the recovery you get this command has been stubbed.Also...towelroot won't even touch it for root now.I did manage to get it rooted with the intel tool with a temp cwm recovery,and flashed the SU zip beta.I have tried flashing the recovery with terminal emulator no go.If you boot with the intel temp cwm recovery and flash the Crowlock zip it errors out.I have followed several threads and so far nothing will tough it...Asus has been watching us....lol...
Oh the device is AT&T Padfone X mini by the way.
Click to expand...
Click to collapse
The Padfone x mini contains an intel processor so they have a different kind of bootloader than the Padfone x, which has a Snapdragon 800.
Towelroot was patched when newer updates came along, but it still works with the original padfone x since they never got an update from at&t in the last year.
Also the padfone s fw is not compatable with the padfone x mini, since there is a different dock involved. (different screen and resolution).
Overall both devices may look similar but have completely different hardware, so that why it will not work for you.
Thanks for verifying the regular X processor..I seen it said it had the Snapdragon but was curious of the fact.Well I guess I'm on my own,and maybe I need to start a support thread for this thing.lol...Thanks for everyone's help...
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
leo025 said:
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
Click to expand...
Click to collapse
xtermmin said:
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
Click to expand...
Click to collapse
Simple and works!!! LL 5.0 in my Padfone X :highfive:
Easy as pie
xtermmin said:
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
Click to expand...
Click to collapse
Yeah this is exactly what I did, but in case of rooting (for some bizarre reason) the only method that worked for me was using Kingroot and then to purchase the app Super Sume Pro in order to get root access. After that I strictly followed the above procedure and now both devices are functioning flawlessly!!!
Big thanks to all doing the tutorials on the padfone x to s!
For the folks following this thread - any issues with band 17 like described in the other threads? I think the twrp.img link is not the one that allows restoring of EFS (Nexus5repack-A01) so just curious if anyone having issues with LTE or band 17 (if you care )?
I also received a software update from ATT recently - got excited it was finally Lollipop but it turned out to be updated built ATT_11.10.11.1. Anyone else get this, any issues converting / unlocking BL on this build before I plunge L)
Thanks again!
Phone: Padfone X
Build: ATT_11.10.11.1
Mods: TowelRootv1, TWRP (twrp_2.8.7.8_v5.img)
synergysemantics said:
Big thanks to all doing the tutorials on the padfone x to s!
For the folks following this thread - any issues with band 17 like described in the other threads? I think the twrp.img link is not the one that allows restoring of EFS (Nexus5repack-A01) so just curious if anyone having issues with LTE or band 17 (if you care )?
I also received a software update from ATT recently - got excited it was finally Lollipop but it turned out to be updated built ATT_11.10.11.1. Anyone else get this, any issues converting / unlocking BL on this build before I plunge L)
Thanks again!
Phone: Padfone X
Build: ATT_11.10.11.1
Mods: TowelRootv1, TWRP (twrp_2.8.7.8_v5.img)
Click to expand...
Click to collapse
Wow at&t pushed an update to this device, I thought that was the end of the suport due to this thing not selling much at all.
At&t will probably not update the Padfone x to lollipop as there are rumors that the Padfone X2 might be coming out around march.
I flash those different versions of twrp to keep my band 17 and for call settings to actually work.
With out that I cannot make my phone number show up on caller id, and call forwarding to work.
Using PFS Fw, This phone is incredibly stable and all of the features actually work despite doing that conversion.
Probably worried as to what could happen if Marshmallow gets pushed out for the S, would we still be able to use the firmware then? We'll see from there. Its probably better to go to CM13, once everything starts working. (its been improving, but not suitable for being a daily driver as some apps FC and tablet support almost works.)
As always you could check my guide, a bit longer, though its understandable and help you prevent losing Band 17 and call settings
youngson87 said:
So I realized that there wasn't much support out there for the padfone X. I love my padfone X regardless of its tiny battery, lack of developer support, and unpopularity. So I decided to embrace my love for tech and support the device myself.
So, Asus is still showing love to the padfone S(not X). That being the case it's the international version of the AT&T X; the hardware is almost identical. I decided to turn my X into an S, unlock the bootloader, upgrade to Android 5(I know its not the latest but it's better than 4.4.2), root and enjoy.
Breaking, bricking, whatever... This is all on you, this is what I did to my phone. I'm only sharing my experience. Make sure your phone is fully charged before you begin. Don't say I broke your phone, your taking a risk. I take no credit if this does or doesn't work. This process is time consuming and might not work for you. Don't blame me for wasted time.
This should give you carrier unlock as well.(not tested) and you should be able to use the Padstation with Lollipop. I'll leave download links below.
Steps
#1 back up all your data(titanium etc)
#2 download and run New Kingroot(took 5 tries to work)
#3 download and run superSume Pro
#3a step 3 should have installed SuperSU... Uninstall Kingroot & update SuperSU (use normal method); get a root checker and check root
#4 download a custom recovery(I personally like TWRP, but its buggy on this phone whatever) store the recovery.img on your phone's internal storage(not sd)
#5 install a flash tool(rashr or flashify will do) flash the custom recovery img.
#5a you should have root and custom recovery now, even if the bootloader is locked.
#6 The hard part. Put the S firmware on your internal storage(not sd card)
#7 in recovery mode you need to make another back up(back ups are awesome) do a factory reset in recovery(also wipe cache)
#7a install S firmware(do this in recovery mode) and restart phone. (Initial boot takes about 2 minutes). This might not work the first time(took 5 restores for me to finally get it)
Congratulations!!! You now have a "Padfone S"
#8 preferably using clockwork mod, install crowlock zip file by quarx to unlock bootloader
#9 to upgrade from 4.4.2 to 5.0 you need to go through about 4 updates from the Asus website. Follow this link(only use WW upgrades)
#10 after the upgrades you may have lost root. Just follow steps 2 and 3 again.
Asus "says" they will be releasing Android 6 for the Padphone S... Don't know how true that is, hope so. ENJOY!!!
Downloads and links
Kingroot:
http://www.appsandroidapk.com/tools/kingroot/
S firmware: thank you to tjsnooley!!!
http://forum.xda-developers.com/padfone-x/general/i-have-done-it-t3053207
TWRP/Cwm: thanks quarx!!!
http://quarx2k.ru/asus_padfone_s/recovery/
Crow Lock:
http://quarx2k.ru/asus_padfone_s/
Asus upgrades:
https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
The superSume Pro costs money, you'll have to find it on your own, sorry...
Click to expand...
Click to collapse
Hello, thanks for you work, a have a question, the padstation work fine after change padfone x to padfone s firmware?
Regards.
i think i need help, in twrp i cant do wipe data cache dalvik, i try to do data factory reset from options, but after insert code, nothing... doesn't start.. i try to install a rom ww of padfone S, doesn't work.. T___T my internal storage is near to full and my telephone have stock icons and no other applications.. Any suggestions to do ?
colla.paolo said:
i think i need help, in twrp i cant do wipe data cache dalvik, i try to do data factory reset from options, but after insert code, nothing... doesn't start.. i try to install a rom ww of padfone S, doesn't work.. T___T my internal storage is near to full and my telephone have stock icons and no other applications.. Any suggestions to do ?
Click to expand...
Click to collapse
Hmmm Try it with a different recovery such as cwm, thats strange that twrp would not work. After boot into it and factory reset then flash cm12.1 just to make sure that the internal storage not full, then it will be best to install twrp afterwards to flash the padfone s firmware.
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
colla.paolo said:
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
Click to expand...
Click to collapse
I have never had luck with CWM on this phone, that is why I use TWRP.
If you still have difficulty mounting: From TWRP, go to wipe, advanced wipe, select the partition you are having difficulty with, tap Repair or Change File System, tap Repair. If that isn't successful, tap Change File System, then choose EXT4.
For the error: ASUS_T00N file, this is t00n
1. open the rom.zip, do not extract, just open.
2. Browse to \META-INF\com\google\android\ then open updater-script. Most people suggest to use a unix based text editor, but wordpad works fine for me.
3. Delete the first line containing: getprop("ro.product.device") == "ASUS_T00N" || abort("This package is for "ASUS_T00N" devices; this is a "" + getprop("ro.product.device") + "".");
4. Save and close. (this is the part where I have trouble with using Note++ or other unix based editor, I can't get it to save within a zip file. That is why I just use wordpad which i have never had issue with.)
5. Transfer to phone and flash.
6. Profit.
If that doesn't work, just use ADB sideload through TWRP.
1. From TWRP go to Advanced, ADB Sideload, tick checkboxes, swipe to Start Sideload. (Note, make sure phone is connected to PC.
2. From PC command prompt, run command ADB Devices to verify device is connected and detected as being in Sideload mode.
3. From PC command prompt, run command ADB Sideload filename.zip
Note: To make using ADB easier, I just drop the rom into the folder where adb.exe is located. From Windows explorer, CTRL+Shift+Right Click Folder containing ADB, click Open Command Window Here This way I don't have to do a bunch of CD commands or provide file path to ROM that I am using.
^ Follow his guide first ^
colla.paolo said:
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
Click to expand...
Click to collapse
I assume that you did unlock the bootloader prior to that, but if not do that in cwm (if its still installed) since that works well by putting the file into the sd card.
Ok, but you were able to fix cache, I wouldn't say its bricked as you could just boot a different recovery through fastboot, so twrp is what you must use to flash the ww fw to the phone since cwm doesn't like that fw.
So put your phone to fastboot mode which is power and volume up at the same time, the logo should be frozen, which is good. Then put in the usb cable into the computer afterwards, and let the computer recogonize the device. If it does good, and thats when you need to get fastboot running on your computer and hope that the phone gets detected. If it does great.
The next step is putting the twrp recovery in a place that would be able to be activated from the computer, there are many tutorials how to get it to set up perfectly, but as long as the command you are about to put in should give you "cannot" locate file. Heres a nice guide: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
The command is fastboot boot (then the file name).img and presto you got a recovery rolling for you to flash a rom on to the phone.
After flashing the fw the bootloader does get locked and the recovery will be replaced with stock so make sure to reflash the bootloader unlock through flashing the zip file and the twrp recovery file under img flash. (there should be an option there)
I've been there and that sucks but as long as you are careful and know what your'e doing I think you could get yourself out of that state where there is no rom installed.
The guy who posted above me does have the other solutions with the other errors if you run into them.
Good Luck
How to turn Padfone x to s
Am new at this How i can my Padfone x to s
King 242 said:
Am new at this How i can my Padfone x to s
Click to expand...
Click to collapse
Read the first page of this thread.
The basic steps:
0. Grab the following and throw them on your microSD card:
Latest Padfone S Worldwide (WW) firmware from ASUS: https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
CrowLock: http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip
TWRP Recovery: http://quarx2k.ru/asus_padfone_s/recovery/twrp_3.0.0.img1. Root (via Kingroot, Towelroot v1, whatever)
2. Install Flashify from the Play Store
3. Use Flashify to flash the TWRP recovery on your microSD card
4. Boot into TWRP recovery and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. System > Reboot > say yes to rooting the device. Enjoy.
Related
Do I have root?
First you install the unlock APK, unlock it...Install goo beta, Install Open-Script Recovery, reboot and ill have TRWP? and be able to install custom roms?
IM READY TO JUMP SHIP!
You have your recovery to install everything.....
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
It has its own recovery? or do i need to install one...
David522d said:
It has its own recovery? or do i need to install one...
Click to expand...
Click to collapse
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
also a video showing you how to flash a custom rom, with TWRP and goo manager, is there also
demandarin said:
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
Click to expand...
Click to collapse
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Anyone ?
I don't know about goo manager but I flashed cwm touch with fastboot (normal cwm didn't work and twrp wasn't out)
Sent from my sgs2 running cm9
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Yeah steps sound good. you could always flash a ROM that has root. I dont think you need root to install twrp. Double check though. post in twrp thread to make sure.
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
David522d said:
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
Click to expand...
Click to collapse
There is nothing that will work 100%, but its pretty close, maybe 98%? Anytime someone does anything with the bootloader, recovery rom, or OS rom, there is a chance for bricking: interuption in the write process, loss of power, corrupted dl (crc check should catch most of those). If your worried about bricking it, leave your TFP stock and await the OTA's - that way if it gets bricked by Asus then they are responsible and you havent nullified your warranty.
Unlocking the bootloader allows the use of non stock bootloaders/recoveries to be installed and used. From the new bootloader/recovery, you can install a rom that either has root, or not. You don't even have to change roms after unlocking. The 2 are independent.
Right -
Unlocking with the APK does not root or in any other way modify or prep the prime for what you're about to do. Depending on your stock ROM revision this is either very easy or a complete pain in the ass, I'll provide both versions:
For Stock ROM ending .15 or earlier -
* DO NOT RUN THE GOO IM.MANAGER FIRST. Follow these steps below.
* Download Sparky's APK to root - it's in the development forum for the TF Prime. Run it. This will get you root access on the system. It's automated and practically idiot proof, just follow the on screen instructions.
* If you're going the Team Win route, once rooted, load up the Goo.im manager, then follow the instructions as per a rooted installation for getting TW Recovery into place. This is pretty painless really and works automatically, approve the Superuser permissions as required. Once the recovery is in, you can reboot into it and then get with the flashy.
-----
If you're on the Stock ROM ending .21, you're going to have to do what I did. As you're already unlocked using the BLOB files to downgrade -will- result in a hard brick. SO!
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
Hope this helps.
This whole blob thing is new for me since i have always insta-rooted, and CWM'ed any android device i get; but from what I've gathered, it is used by ASUS to lowlevel write the os on locked systems, similar to the way nvflash dumps img's directly to the memory. Once your unlocked with the CWM or twrp, then you can no longer use blobs, just the rom zips. The recovery rom handles the unpacking and dumping of the kernel and OS into the appropriate partitions. Some roms are zipped with install scripts that wipe your cache, user space and dalvik - but its always a safe bet to do that anyways.
Nice writeup Hobbesian
Well, some blobs are fine, but generally they're strictly either Team Win Recovery or Clockwork mod recovery suites, and they need to be slipped in using fastboot (I believe ROM manager and GOO managers use their own scripts to handle installation) as a rough rule. The "big" BLOB files which Asus puts out are a guarantee to hardbrick an unlocked device (some days I wonder if it would kill Asus to offer a route to re-lock and re-stock a device on the proviso that if you brick it doing so you're still out of warranty).
That said - Virtuous Prime is definitely an excellent first step into Custom ROM tinkering, it gives you root and all the associated useful features, as well as the ability to start experimenting with more feature heavy ROM builds such as Cyanogen and AOKP Cornerstone. They're even nice enough to include a partially tweaked build.prop which saves you a lot of the work in modifying that.
I should point out my guide is relevant only if you already applied the unlock APK to your system, if you haven't done so, there's alternative routes including the downgrade blob option to get root without unlocking your device.
paddycr said:
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
Click to expand...
Click to collapse
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
David522d said:
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
Click to expand...
Click to collapse
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
EDIT: if you're in fastboot and you cannot get adb to recognize your prime you need to install the correct drivers for your pc/mac. Hobbesian describes how to do this a few posts above this. In his nice write up he also describes how to flash TWRP directly from fastboot. If you want TWRP, follow his instructions since you'll have less messing around to do.
paddycr said:
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
Click to expand...
Click to collapse
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
David522d said:
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
Click to expand...
Click to collapse
Yes, all of the roms will have root. Hit my thanks button if it works for you
paddycr said:
Yes, all of the roms will have root. Hit my thanks button if it works for you
Click to expand...
Click to collapse
Would it be easier to install CWM, then install TWR
David522d said:
Would it be easier to install CWM, then install TWR
Click to expand...
Click to collapse
I think both ways are the same. There's no correct answer to that. It depends on whether you would prefer to use CWM or TWRP.
Hi guys
I've tried everything, i bought this watch today and i was so hyped about it.
I tried to update it to 6.0.1 using adb on my mac.
The problem is when i do this command "adb reboot recovery" and then "adb devices" it shows no devices! (before entering recovery it actually shows the device in the list!
This is so wierd and there is absolutely no solution that worksfor me... anyone has any ideas?
Edit: The problem more clearly:
Ok guys so the problem was that my LG G Watch (square) for some unknown reason wasn't available in recovery mode through adb, that means when i would use the command "adb devices" in recovery mode, i would see the empty list without any devices, while anywhere outside the recovery (system, fastboot etc) i was able to communicate with the device. (Since i was so frustrated i didn't make it clear enough in the original post ) And my watch was on 4.4! ( :| )
The solution:
Ok, so the problem was the watch, because i tried a OS X (and a windows on the same mac) and 2 windows laptops, all with drivers installed (and done the "update driver..." stuff on all) and the problem still persisted.
This solution is for people whose device is not displayed while in the recovery mode in cmd/terminal.
This is what i did: (i didn't do this in the order because i literally tried every solution on the internet! but this is the order that i was finally able to solve the problem with.)
1. I downloaded this tool from this topic (go to the link, click on LG G Watch > G watch script tool > LG G Watch Restore Tools V9.8.zip)
2. Run this bat (i used a windows but it works on the mac too) 1 LG G Watch Tools for Windows.bat
3. Let it recognize the device
4. When the blue list comes up choose 4 ( you should be in bootloader)[cmd > adb reboot bootloader] when it's done, your device should be on 5.1.1.
5. Download this tool from this topic
6. In cmd/terminal type "adb reboot bootloader" then type "fastboot flash recovery [draggedfile] and drag the downloaded .img to the cmd and press enter.
7. Now you have installed a custom recovery called CWM
8. In cmd type "fastboot reboot" then after reboot "adb reboot recovery"
9. Now inside this tool swip down to "install ..." and swip (to right i guess) and stay here on the watch.
10. Now in cmd type "adb push -p [draggedfile] /sdcard/0/Download" and drag the 6.0.1 OTA update and press enter
11. Now the update is in your device as a zip file in this path : /sdcard/0/Download (it didn't work when i wanted to push it to "/sdcard" folder so i had to go deeper)
12. Now swip on install from sdcard and navigate to the path and choose the zip file.
13. Done! you have successfully updated your device without going into recovery mode!
Thank you very much @lfom for sticking to this topic and helping out in the process!
I just tried it with windows as well and ain't working... im so frustrated...
There's a guide in General section that you may want to read:
http://forum.xda-developers.com/g-watch/general/guide-how-to-fix-6-0-1-adb-bug-t3347122
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
miladkalbasi said:
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
Click to expand...
Click to collapse
So you are on 4.4 and want to update? What else? Rooted and custom recovery?
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
lfom said:
So you are on 4.4 and want to update?
Click to expand...
Click to collapse
Yes, i bought this watch yesterday and it's on 4.4 and i want to update to 6.0.1 (or any newer update)
lfom said:
What else?
Click to expand...
Click to collapse
I have never had developer experience with any android device before so i learned everything in like 6-7 hours, therefore there is a high probability that i might have made mistakes in the way but here's what i have done so far:
1. i tried to update the watch from "About" on the watch itself but kept getting "Something went wrong" error and couldn't fix it.
2. so i moved on to use my mac to do the update which took me 4-5 hours to figure out what SDK platform tools, ADB, OTA updates, bootloader, fastboot etc means.
3. i figured out all this and went on until i reached here: i have to use this commend in the terminal (it's like windows cmd): adb devices
so that i know my device is there and authorized on the companion android device (i see the device in the command shell), i then proceed to this command : adb reboot recovery , as soon as i type this command and press enter, the device reboots and enters recovery mode but it is also vanished from the system, by typing adb devices i no longer see it, i just see an empty list.
4. i also did unlock, wipe, restore back to stock ROMs (5.1.1 ROMS), tried TWRP (i then realized i can't do OTA updates with this tool)
5. i did all of these steps several times and always got the same results!
6. i also tried the windows on my mac and got the exact same results.
7. i tried 3 different windows laptops in the household (2 of which run win 8 and one runs win 7) but was not able to make it through installing the drivers (i couldn't see the android device when i clicked on update drivers...)
lfom said:
Rooted and custom recovery?
Click to expand...
Click to collapse
no i haven't rooted the device
lfom said:
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Thank you very much for your suggestion, i have already tried that and it doesn't actually give me any more options that i already have.
I've come to the believe that it's either my laptop (which only has 2 USB 3.0 ports and some people say it causes issues) or my watch. I have to try to use a different computer but i don't think i can access more computers or solve the driver problem on the 3 existing ones.
I really wish i could solve this by myself, i live in a country that i can't access warranty and stuff so i either have to fix it myself or get a professional's help.
i found this topic as well, that's exactly my problem.
I can communicate with the watch in bootloader and TWRP but not in the recovery mode (stock)
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
lfom said:
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
Click to expand...
Click to collapse
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
miladkalbasi said:
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
Click to expand...
Click to collapse
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
lfom said:
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
Click to expand...
Click to collapse
I solved the problem!
Funny thing is i didn’t see your answer and fixed it by myself but you actually proposed exactly what i had to do! Thank you very much for your effort and spending your time on this topic!
For others who might run into the same problem in the future I'm gonna update the first post and say what i did.
Cheers!
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
joaomPT said:
Hey guys,
I've had a total of 4 android smartphones during the last years, and I did root all of them and even install diferent ROM's, but on this phone (Honor 7) was kinda diferent.
The root process is way more complex than all the other androids I did root (simply flash a .zip file...) so I've been post-poning this task over and over..
Finally yesterday I gained courage to try out rooting my phone, and while attempting to root my Honor 7, after flashing SuperSU from TWRP, my phone no longer booted.
Stressed as I was, I just told to myself "f*ck it" and formatted the system and I didn't care much if there was a fix without needing to format the system. (but then I realised that I could not find any .img ROM files to flash from TWRP recovery, so basically I did my actions wrong once again)
I followed the tutorial from guidebeats.com which talks about rooting EMUI 4.0 Android 6.0 (I cant post links)
Basically this is the story:
While unlocking the bootloader, even though, the tutorial said the phone would reboot itself after typing "flashboot oem unlock 1234934829" I did a hard reboot (or reset?) holding (VOL+) + Power button and I have the feeling that the bootloader unlock was not 100% done, even if it said it was unlocked. (Phone was working perfectly fine there)
Then I flashed SuperSU, and I could no longer boot. After powering up my phone, after the first splashscreen, the screen would only turn black.
What (I think) I need to now is remove the TWRP recovery, and use the stock one and attempt to install an "update" using (Vol+) + (Vol-) + Power. (please correct me if I'm wrong)
But now there's some issues I got that I'd like some help with:
1- How can I get back to the stock recovery? (NOTE: I currently got no OS installed on my Honor 7, since I formated it)
2- Will I need to lock and unlock my bootloader again (if I want to 'fix' the bootloader unlock?)
3- Where can I get official Honor 7 stock ROM? (would be awesome if there was already the Android 6 stock rom for a clean install)
4- What are the steps on this tool (Honor 7 Multi-Tool) to root my phone?
I need my Honor 7 asap
Sorry for the long post, It's my first time doing a more advanced root and I have all these questions.
Thank you very much for any kind help!
Click to expand...
Click to collapse
As you are already familiar with adb and other stuff so will write a short post for you.
To download latest firmware, head to
http://forum.xda-developers.com/hon...tock-firmware-packages-honor-7-t3448747/page1
Google, download and install Huawei update extractor and open UPDATE.APP in it (obtained after extracting firmware).
You can see all the images. Just extract recovery and boot to platform-tools folder.
Meantime, do the unlocking command again, with
Fastboot OEM unlock xxxxxxxxxxxxxxxx
Followed by fastboot reboot
And press and hold the vol down button again until you reboot in bootloader.
Flash the recovery and boot you extracted using
Fastboot flash recovery recovery.img
Fastboot flash boot boot.img
(I got a habit of extracting and flashing system and Cust using
Fastboot flash system system.img
Fastboot flash Cust Cust.img
But they are not necessary)
Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again).
Please do report back if it comes to life.
To root, just flash twrp and then use SuperSU 2.62 (no other version) and update it later using play store.
Sent from my PLK-L01 using XDA Labs
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
joaomPT said:
Hey!
Thank you alot for your reply.
From the link you sent about the firmwares, there are alot of Builds for the L01 (EU) model. Can I simply use the latest from the list or I gotta install 1 by 1 (from older to newer)?
Also, the bootloader unlock thing, is it ok if I wait to do it until I install the stock ROM again? Because I think I don't have the code anymore (Also don't know about IMEI)
Other thing, yesterday before bricking my phone, I tried to re-unlock the bootloader as you said above, but it didnt let me because "it was already unlocked".
I really have no idea if it's 100% unlocked or not.
important thing!
With those ROM's, I still have the right to receive official OTA updates from the HiCare app right?
Thank you again
Click to expand...
Click to collapse
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Just use B380 as it's the latest full firmware available there.
Unlocking bootloader again was just a precautionary measure (proceed without it and if it is not 100% unlocked and if something goes wrong, we can troubleshoot later, which imo, won't happen)
And yep, if you keep the firmware as it is, but if you flash twrp and root, you will still see the update available in Hicare but will have to install stock recovery again before upgrading. (Nothing else is needed as SuperSU 2.62 gives a systemless root so you only need to flash back stock recovery for an update)
I am not against honor-tool bit it's best to do things manually as it makes you learn stuff and is easy to troubleshoot if something is amiss.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
joaomPT said:
Alright, btw, about the thing you said
"Now you are set to try a 3 button update (sometimes it gets stuck so if it's stuck for 15 minutes, try 3 button again)."
I gotta do that myself with an "update.app" file or what?
Sorry, I missed that part
Cheers!
Click to expand...
Click to collapse
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You have to make a dload folder in SD card and copy UPDATE.APP to that folder.
Then just turn off the phone, press and hold power + vol up + vol down until phone boots.
Let go of power but keep others two pressed for 5, 6 sec more. Your phone will boot into recovery and start installing UPDATE.APP
It likes to get stuck at 5% (most reports) but sometimes, somewhere else. If its stuck for 15 minutes on a particular percentage, just press and hold the above three buttons again using the same process.
Multiple tries make it work...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said » version 2.62 «
I cant thank you enough!! Can I pay you a coffee?
Thank you!
joaomPT said:
Hey man!
Good news, my phone is alive and root is done.
The problem was on the SuperSU that I flashed, it was version 2.71, instead of the one you said �?�» version 2.62 �?�«
I cant thank you enough!! Can I pay you a coffee?
Thank you!
Click to expand...
Click to collapse
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
You can find him somewhere in this thread
http://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554/page1
Decision is yours
muradulislam said:
That's great... Enjoy your phone and as for coffee, well, let's say, you owe me one and we will leave it at that
Better yet, you can search DigiGoon and pay him for the coffee, he taught me what I told you.
Whichever you like...
Click to expand...
Click to collapse
Alright man, cheers
joaomPT said:
Alright man, cheers
Click to expand...
Click to collapse
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
joaomPT said:
Hello.
Do you have unlocked bootloader and TWRP recovery? You can format your phone from TWRP recovery.
I think the only option for you is to get the old ROM img and flash it (starting from 0)
You can dirty-flash (Flash a different ROM with same android version as yours, e.g: flashing custom android 5 ROM over your stock android 5 ROM without factory resetting your phone) but I dont think you can do that from Android 6 to 5.
Click to expand...
Click to collapse
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
tgergo said:
Yes I have unlocked bootloader and currently not twrp but I can flash it at any time.
The last two paragraphs you wrote are different solutions or the last one is a more detailed explanation of the previous?
I have android 6 so the later method won't work as you said.
But formatting it and flashing a stock android 5 rom - is it that simple? Nobody here suggested this before, however I have been asking for months.
All the phones are empty when they leave the assembly line.
How did you flash the new rom to your formatted phone? Extracted update.app and flashed each file with fastboot? Any issues you faced?
Click to expand...
Click to collapse
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
I'll try... But seems too simple to be true...
joaomPT said:
From my last 2 paragraphs, the first was a solution, the second was an impossible alternative that I thought it would work.
My issue was that I had a custom recovery but I had no ROM installed, so I had to install the stock recovery and boot (extracting from update.app) and flashing it via fastboot, to afterwards force the update with 3-button method.
-----
What you'll need to do is:
- Flash TWRP
- Wype system, data, cache.. (so that you completely delete your current ROM)
- Extract recovery.img and boot.img from an update.app of an Android 5 ROM you'd like to have (Official ROM for your device model)
- Flash them via fastboot (You'll go back to stock recovery again)
- Shutdown your device
- Create a folder named "dload" on your sdcard and put UPDATE.APP file in it.
- Reboot
- Do the 3-Button update ([Vol+] + [Vol-] + Power)
- If it works, it will auto install
(- If it gets stuck on 5% for over 5/10min, force reboot pressing [Vol+] + Power) and try again the installation
- After installing it will boot normally (first boot takes a while)
NOTE: I'd recommend creading the dload folder before wiping the ROM, because usb didnt work for me afterwards. (It would still work if I was on recovery tho)
>> Remember to make a full system backup before wiping aswell, dont be stupid like me xD (thats why I had to full wipe my system after soft-brick)
Im answering based on what I did and was explained here to me
Click to expand...
Click to collapse
Hi again,
I'm doing this OS installation now. It starts fine but stucks at 90%, (I'm trying to install the latest stock ROM which can be downloaded from Huawei site, B220 or221). Did you have the same issue? I waited more than half an hour at 90% but did not go on.
tgergo said:
Hello
How did you format your phone?
I'm still struggling with going back to Android 5 and EMUI 3.1 since there is no rollback file available. (PLK-AL10, B396) Maybe formatting and installing the old rom could be a solution, like in your case?
Click to expand...
Click to collapse
Maybe formatting, Flash stock Android 5 recovery using Honor multitool , and then Flash a Android 5 firmware
Not sure it Will Work without rollback..
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
tgergo said:
Finally, after 2 months of struggling I managed to get back to Android 5 and EMUI 3.1 without a rollback file.
Here is what I did:
0. Download a full ROM you want to install
1. Backup of the current system with Hisuite (everything. Apps, media, contacts, call log, etc.)
2. Flash TWRP recovery with fastboot (start phone in fastboot mode)
3. Wipe (and format!) everything you can with TWRP
4. Extract boot.img and recovery.img from update.app of the new ROM with Huawei Update Extractor
5. Flash boot.img and recovery.img with fastboot.
6. Copy update app to dload folder on SD card, insert into the phone.
7. Restart phone with [VOL+] + [VOL-] + [Power] buttons to force update.
8. The system will be installed from SD card. I had no issues with the installation. First I did not format the phone (just wiped) and it did not work.
9. Restore data from backup.
The only strange thing is that the native app icons look different than my previous lollipop system. Don't know why. They are less colorful. I installed C00B220 for PLK-AL10.
Click to expand...
Click to collapse
Is this really work? i cant rollback to any version.
Yuaru said:
Is this really work? i cant rollback to any version.
Click to expand...
Click to collapse
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
tgergo said:
Yes it does. (It did for me.) Technically this is not a rollback but installing a brand new system on an empty phone. That's why it is important to do a backup upfront.
Click to expand...
Click to collapse
Thanks for the answer. Im gonna try this method. I can't reflash any region rom.
UPDATED to include instructions for flashing other ROMS
I've successfully unlocked, flashed TWRP, rooted, and flashed Lineage on both an XT1602 and an XT1607. I'd done this before on other devices, but had forgotten just how it all came together, so when I was done I went back and made this step-by-step guide. It's a bit shorthand.
Many thanks to squid2 for his TWRP port, to the folks who make superuser, to parrotgeek1 for superSUFixer.zip, and to spiked_mistborn for reminding me about it. And, of course, huge thanks to squid2 and Alberto97 for the killer Lineage ROM. It is far better than stock or the last Nougat CM. If I forgot anyone, or made any mistakes here, somebody please point them out. Have fun!
1. Preparation (if the links don't work, search on xdaDevelopers or with Google)
a. Backup entire phone to the extent you are able, either with a dedicated tool and/or to Google via the Android backup feature
b. Download and install Motorola Device Manager on your computer from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 so as to make sure you have the proper drivers
c. Download adb and fastboot tools onto your computer from
http://forum.xda-developers.com/showthread.php?t=2588979 or
http://forum.xda-developers.com/showthread.php?t=2317790d. Download TWRP for Moto G4 Play to same folder as adb and fastboot tools from http://forum.xda-developers.com/devdb/project/?id=16870#downloads
e. Depending upon whether you want to flash Lineage or stay with the stock ROM, download to the same directory on your computer either:
i. Lineage and the Lineage SU addon (if you want root) from https://forum.xda-developers.com/g4-play/development/rom-lineageos-14-1-moto-g4-play-t3544646 and Google apps (arm 7.1 micro) from http://opengapps.org/; or,
ii. superSUFixer.zip from http://forum.xda-developers.com/g4-play/development/automatic-flashable-zip-fix-supersu-t3464396 and superusersu.zip from http://www.supersu.com/download
Note: I did not find superSUFixer.zip necessary when I intially rooted, but after later installing squid's kernel it was indispensable to reinstallation of superusersu.zip.g. Attach phone to computer with USB cable, enable file transfer on phone and either copy the Lineage zip and Lineage SU addon zip and gapps.zip to your phone, OR copy superSUFixer.zip and superusersu.zip to the phone (you don't need to copy twrp)
2. Unlock bootloader
a. Enable developer options (Settings/About Phone/tap Build Number 7x)
b. Enable USB debugging on phone (Settings/Developer Options)
c. Enable OEM unlock on phone (same)
d. Open command window and change to the directory where you put adb, fastboot, and twrp
e. > adb devices (to check that you are connected - you should get a response with a device id)
f. > adb reboot bootloader
g. >fastboot oem get_unlock_data
h. On computer, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a (you need to proceed through the login and to the second page)
i. Copy data returned by phone in the command window (make sure you copy all of it!)
ii. Paste that data into the Data Scrub Tool on the web page
iii. Copy scrubbed data, paste it into the box on the web page at step 6, and click the button; if it says you can't unlock your device, either you didn't copy and paste all the data, or your phone can't be unlocked and you're done; otherwise,i. Copy unlock key from email
j. > fastboot oem unlock <unique unlock key>
3. Flash TWRP
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
4. Flash Lineage and root, or just root -- when the phone has rebooted into recovery (you'll be in TWRP now)
a. follow prompts to make TWRP permanent or not
b. DO A FULL BACKUP OF EVERYTHING with TWRP
c. make sure you performed step b (or you may wish you had later, if something goes wrong!)
d. To flash another ROM, in TWRP
i. Wipe Data, Cache, and Dalvik. (Yes, you have to do this.)
ii. For Lineage - Install the Lineage zip file, the Lineage SU addon zip file, and the gapps zip file, one after the other, in that order, WITHOUT REBOOTING in between. TWRP will let you add all three to its queue to flash in order;
iii. For other ROMs - see instructions for those ROMs, but in general, install the ROM zip file, and then the gapps zip file, one after the other without rebooting in between. For root access, depending on the ROM, you may need superSUFixer, supersu.zip, or both; again, see the instructions for the ROM you are flashing.OR
e. To stick with the stock ROM but get root access, DO NOT WIPE, just flash superSUFixer and then supersu.zip
5. If TWRP does not automatically reboot your phone (if you unchecked the "reboot when done" box), then reboot to the System; if you left the box checked, then your device will reboot by itself once the zip files have been flashed.
6. Follow the prompts to set up your new ROM or stock Android.
7. Reboot into recovery (TWRP) and make another backup!
8. Want to get rid of the "Unlocked Bootloader!" warning screen? Flashing this file from TWRP worked for me (all the others I tried did not work):
https://forum.xda-developers.com/attachment.php?attachmentid=4065906&d=1488923356
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
fireball0093 said:
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
Click to expand...
Click to collapse
Any word yet on that unlock code?
loociddreemr said:
Any word yet on that unlock code?
Click to expand...
Click to collapse
After talking to their customer support, I never got an email. The next day however I decided to go online to their boot loader page and put my code in, then it worked! The data scrub tool or whatever it may be called that they have I recommend using it too.
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Thanks a ton for the guide
haher2 said:
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Click to expand...
Click to collapse
They are in a subdirectory of the TWRP directory. With the proper drivers installed on your PC you can transfer them via File Explorer. Or, 20 pounds/euros/dollars will get you a 64gb SD card.
3. Flash twrp
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
Click to expand...
Click to collapse
I tried to fastboot boot recovery from the bootoader but it didn't work. I rebooted the phone first and did it with: "adb reboot recovery" in windows.
Overall nice guide, works like a charm, i also flashed the unlocked bootloader warning with a custom logo.bin, no issues here and works like a charm (I flashed it with the stock logo you see when you first bought the phone with a locked bootloader)
Thank you!
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
loonix said:
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
Click to expand...
Click to collapse
Yes and, adding to what you said, you need to re-enable the "Allow bootloader unlocking" and "USB Debugging" in Developer Settings if you failed to flash your recovery as the device expects to be flashed. Else, you'll get a "unable to load kernel" error in the bootloader log and being rebooted again to the bootloader menu.
Great tutorial indeed, thanks a lot. Nandroid backup doesn't worked for me but i'm going on.
Edit - worked after disable sd as internal memory
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
hamelg said:
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
Click to expand...
Click to collapse
In concept, I don't see any reason why you couldn't use TWRP to flash the stock ROM and then fastboot to flash the stock recovery ... or fastboot to flash both (be easier and quicker). The Moto website may have instructions for re-locking.
mkollersms said:
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
Click to expand...
Click to collapse
In a command window use the cd command to change directories. For example:
C:> CD \mytopdirectory\mysubdirectory
Another link to consider about OTA update if you stick with the stock ROM :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
Thanks again.
If your phone is from Verizon Prepaid, Moto will say the device is not eligible to be unlocked. Knowing Verizon, it's not likely to be unlocked later along down the line either. Hopefully someone comes up with a good way to bypass this restriction and install some ROMs.
Does this method work on the Verizon prepaid model, or does it have to be from moto/amazon?
Moto g play twrp IMG file not IMG it's **** IMG file please develop it
Does this works with LATAM version? XT1601?
Thanks :good:
This is basically a copy of my Z380M TWRP thread adopted for the ZenPad 10. I decided to start a new one since the OP of justshaun's original recovery/rooting thread has gone stale, even as I had posted several new releases of TWRP over the months. Its instructions are also a little outdated. I've also compiled a version for the new Z301M(F) models and needed a place to post it. This is where I will be posting TWRP updates from now on.
In addition to this thread, referring to the Z380M TWRP thread and the original Z300M thread (links above) may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the others.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows or Linux PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)
MediaTek VCOM drivers (available through Windows Update)
ZenPad 10 scatter file for SPFT, attached (choose the one for your tablet)
Recovery image, attached (choose the one for your tablet)
ZenPad Z300M, Z301M or Z301MF tablet upgraded to Android N
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 10.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image for your device (twrp-3.2.1-0-z30*m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z30*m.img
Once inside TWRP, flash twrp-3.2.1-0-z30*m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". On the Z301M/Z301MF, that option is labeled Factory Reset. Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
WARNING 2: Make sure you use the correct scatter file for your device (i.e. don't mix up the Z300 and Z301 files). For the initial flash, there is no check for scatter file correctness. If you use the wrong one, SP Flash Tool will alter and lock your GPT to that scatter file layout, possibly bricking your device. It will not be easy to restore it. Flashing with the correct scatter file later on will not work because Flash Tool will not allow you to use a different file than the one you used initially.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
SP Flash Tool v5.1532
Z300M Scatter file for all storage sizes (right click, Save link as...) -- do not use for other models
Z300M TWRP 3.2.1-0 image -- updated March 15, 2018
Z301M(F) series Scatter file for all storage sizes (right click, Save link as...) -- do not use for Z300M or other devices
Z301M TWRP 3.2.1-0 image -- updated March 13, 2018
Z301MF TWRP 3.2.3-0 image -- updated August 29, 2018
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Heya, thanks for the new thread..
Stupid question(coming from Samsung flashing)
Ive got Zenpad S3 10 P027, is this TRWP not ideal for this?
Currently, have some su (root) issues. Recovery shows Android icon chest with ! and says "No Command"
When running su in Terminal ADB via PC, says command not recognized.
Looks like I need to reflash recovery. When in TRWP (launched via fastboot boot twrp on PC) I flashed stock recovery but had system mounted read only. Could that be the problem?
Bro, I think you need to do some more homework on root, su, dm-verity, mods, etc. and read the instructions more carefully before applying these hacks. You are making a lot of simple mistakes and ending up shooting yourself in the foot for it. I don't think there's anything wrong with the Z500 TWRP. It can handle installing the stock firmware just fine. The problem is elsewhere. The unlock tool also works fine in TWRP as well in my testing.
The No Command screen is normal. That's been answered many times... you need to hold power+vol. up (or down) to get to the menu. There is no way the stock recovery image can be broken and still boot up.
The su thing, IDK what the problem is, but I'm sure if you install Magisk Manager and make your own patched image from your currently installed firmware, and fastboot-boot with it, you will have su functionality. Just like what it says in the unlock tool instructions.
Lastly and most important, never mount system in read-write mode, as I've repeated several times and exactly as it says in the directions:
7. At the TWRP welcome screen, do not select to modify the system partition and touch Keep System Read-only instead. Doing otherwise will render your tablet unbootable.
8. Mount system in TWRP (in read-only mode)
Click to expand...
Click to collapse
The only time you can mount it in read-write mode is when you are absolutely sure you have disabled dm-verity in your boot image.
I've successfully installed TWRP on Z301M using the instructions from the first post, but then I somehow managed to lose the system. Yes, I should have backed up like the OP suggests.
I thought I should be able to reinstall the original firmware downloaded from Asus (e.g. UL-ASUS_P028_1-WW-3.3.12.0-user.zip) but both the 'adb sideload' method and the TWRP failed to install that firmware zip. My device looks bricked. The only thing I can do is to boot into TWRP (I actually need to select Factory Reset on the bootloader screen to get into TWRP). The folder 'system' is empty.
Can anyone suggest what I am doing wrong when trying to restore the Asus firmware?
When I try to sideload the zip, setting TWRP in the sideload mode, the computer begins uploading but after a few seconds gives the message "Total xfer: 0.01x" and stops, while Android errors with "set boot part fail. can not open misc-sd".
When I install the firmware zip from TWRP it also starts installing fine but shortly gives the same error "set boot part fail. can not open misc-sd".
Thanks
@ahacker, first of all, thank you for the feedback on the Z301M platform. You are literally the first person to have said anything about that version of TWRP.
To see the files on system, you first have to mount the system partition. Did you do that? If not, I suggest mounting it read-only. If there was any corruption on it, then reinstalling the firmware should have fixed it. The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
At which point did it stop booting? Also, did you use the scatter file from first post? And can you tell me if the touch screen works fine in TWRP on your tablet?
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
diplomatic, thanks for replying!
diplomatic said:
[MENTION=4776997]
To see the files on system, you first have to mount the system partition. Did you do that?
Click to expand...
Click to collapse
I do mount the system partition. It appears empty. When I reboot into system TWRP says that the OS is not installed.
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
I would indeed try to mount the system read only. This is not the first Android system I rooted (maybe fifth), and I was always able to restore the system either from sideload or recovery. But here it seems Asus is making us jump extra hoops to do that.
diplomatic said:
[MENTION=4776997]
Reinstalling the firmware should have fixed it.
Click to expand...
Click to collapse
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
diplomatic said:
[MENTION=4776997]
The "misc-sd" errors are normal. Pretty sure they happen on stock recovery too. The stock firmware does not have dm-verity enabled, so letting TWRP modify system to prevent overwriting recovery should not have caused any problems.
Click to expand...
Click to collapse
Thank you for the information.
diplomatic said:
[MENTION=4776997]
Also, did you use the scatter file from first post? Does the touch screen work fine in TWRP on that tablet?
Click to expand...
Click to collapse
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
diplomatic said:
[MENTION=4776997]
I'm not sure what the deal is with adb sideload. I don't think I've ever actually tried it....
Click to expand...
Click to collapse
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
---------- Post added at 01:19 AM ---------- Previous post was at 12:57 AM ----------
Now system refuses to mount
ahacker said:
I don't remember the details of how I lost the system partition. First time I entered into TWRP it asked for a password, probably to mount some partition. I pressed cancel or something. Then I might have cleaned the caches. But I am sure I haven't wiped system. I might have pressed Factory Reset somewhere, because I don't have any data yet on the new tablet.
Click to expand...
Click to collapse
Er, the password should have been for decrypting your userdata. If you didn't have one set up, there might be something wrong there.... Or possibly just unformatted.
ahacker said:
That seems to be my main problem now. I cannot reinstall the Asus firmware. It may look like I might be installing a wrong version, but I am positive that I have Z301M tablet. This is what I bought and what the boot-loader says. I download Z301M firmware from the Asus website (e.g.). So it must be a correct firmware.
Click to expand...
Click to collapse
Yeah, that has to be the right one. The installation script has to match the model name reported by the recovery. Otherwise it would simply abort.
ahacker said:
Yes. I found that to be the only scatter file that worked. I tried scatter.txt from the firmware zip, but the Flash Tool refuses tio pick it up. TWRP seems to be working fine with touches working as expected.
Click to expand...
Click to collapse
Great! Guess my kernel patch was on the dot and the partition layout has not changed from the Z300.
ahacker said:
This is the unbricking method described here. It probably does the same thing as the "Install Zip" from recovery, because the errors that both methods give are the same.
Click to expand...
Click to collapse
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
diplomatic said:
When you installed the zip, did you unmount system completely? BTW, when you mentioned the errors, the installation does keep going for like 5 to 10 minutes afterwards, right?
Click to expand...
Click to collapse
I've tried both ways, with and without system mounted, a few times. The installation would fail after something like 5 seconds.
diplomatic said:
If you still can't resurrect it, please post or send me the recovery & kernel log that has your installation attempt.
Click to expand...
Click to collapse
I think I am giving up on this cheap tablet. I cannot even format it in the Flash Tool: it says "To format code area is forbidden on this phone". Asus is forbidding too much for me to ever buy it again. Attached the logs.
Thanks, diplomatic
OK, found the problem. Check your PMs, ahacker.
diplomatic said:
OK, found the problem. Check your PMs, ahacker.
Click to expand...
Click to collapse
I have replied (twice), but the reply does not appear in my Sent Items. I hope it has reached you. If not, I'll paste the reply here, if you don't mind.
i not understand... i have Asus ZenPad 10 LTE Z301MFL.. a root method has been released ???
@diplomatic
Would this be compatible with Z0310M ? can't find anything for this damn model...
Hi, NeBouse,
Are you sure you have the correct information? It looks like just a misspelling of Z301M, aka P028....
I have z301m.
One thing that was a surprise for me is that the TWRP recovery flashed with the method described in the original post does not stick. You have to flash it each time you use it. If you are like me this information is important, because the original recovery plainly wipes your data without asking or warning.
After you have flashed TWRP on the device, to go to the recovery mode you have to chose "Factory Reset" in the bootloader. Then it will complain about wrong OS, which is the sign that flashing TWRP worked; choose 'yes'. The first thing you should do in TWRP is a ful nandroid backup. (Not listening the OP's advice about backing up when Installing TWRP with a wrong scatter file almost cost me the device. Thankfully diplomatic managed to remotely fix my problem, probably spending a lot of his personal time. The scatter file in the original post is a correct one now.)
Creating a nandroid backup in TWRP takes unusually long time, I even once decided that it hanged. Taking long time, like 10-30 minutes, for a full backup is normal.
Asus Z300M , Magisk 16.3 (beta) and FW 5.3.19 WW now works!
z301m, WW-3.3.12.0 firmware
For rooting I've installed in TWRP Magisk v15.3 (diplomatic warned against 16.x, someone else against 15.4) - link.
Installed in TWRP xPosed framework 88.2 - link, and xPosed Installer apk from within Android - link.
So far, so good.
What I've found is that TWRP seems to have problems with external sd cards (lots of fs corruption). I found it safer to unmount by hand by unticking the sd card checkbox in "Mount". Not very conclusive about this though.
Thanks, ahacker. Good feedback. Although to be fair, I didn't say to avoid Magisk 16.x. I said 16.0. I'm pretty sure whatever bug it had is already fixed in the latest version.
Now that you've installed root, TWRP will stick around on the emmc. The stock recovery only gets installed if you have the original unpatched boot image on it. I mean, this is not unique to these devices. That's been standard Android functionality since some 4.x or 5.x version. And this is essentially what's in the warning on the OP.
The backup I'm talking about in the installation method is done with the SP Flash Tool readback function. That will pull the partition tables and your device's "metadata" that's unique to your unit. I don't think nandroid covers that...
Oh, and what is this SD corruption you're talking about? What file system is it formatted in? Have you checked your card for errors in Windows?
Asus releases so many difference Z301M model, so I am curious if this also works on Z301MF model?
Notice Z300MF has the MTK8163BA (or MTK8163A?) CPU model while Z301M uses : 8163B
Anyone tested that already? Thanks.
my zenpad 10 has frp lock. it this a solution to remove the frp lock?
Pls help how i flash original software via fastboot ?????