I am caught in a bootloop with my TF300T and am desperate for help or to know for sure if I bricked or if there is a way out. I have successfully rooted my TF300T a month or two ago by following the thread at http://forum.xda-developers.com/showthread.php?t=2187982. I kept the latest Asus ROM that I had before the root – I believe it was 4.2.1 but have no way to verify this now.
After rooting, I installed Super SU Pro and used “Root App Delete” and periodically “safe delete” (with undelete) bloatware, tested the tablet for a while, then safe deleted something else that seemed to be bloatware. Apparently I have deleted one to many essential components and am caught in a bootloop. I can’t tell which app deletion did me into this situation.
When booting to recovery using pwr + vol. down, I get the three icons (RCK, android, and wipe data) and am able to go into TWRP when selecting the RCK option. I was also able to flash an update to TWRP from my PC and upgraded from TWRP 2.5.0.0 to 2.6.3.0 in hope that the new version will be able to fix what my previous version didn’t. You may find it important that at the top of the Fastboot screen – the one with the three icons, it reads:
Key driver not found.. Booting OS
Android cardhu user bootloade <1.00 a> released by “US_epad-10.6.1.27.1-20130711” A03
Starting FastbootUSB download protocol
From TWRP I tried to wipe Dalvik and cash as some threads suggested, and to clear permissions. Clear permissions ran for 2-3 hours and didn’t complete. Those attempts produced the following message:
E: Unable to find partition size for ‘/recovery’
E: Unable to find partition size for ‘/boot’
Updating partition details…
Simulating actions…
…Followed by a “Failed” message
I also have a backup from shortly after the root and when attempting a restore it from TWRP, I get the same “Unable to find partition” message.
What I was trying to get to is to flash the latest Asus provided firmware for the TF300T (10.6.1.27.5, 508 MB) by putting the once unzipped zip file on a Micro SD card, and renaming the zip like the above referenced blog suggests, and then attempting to install it from the TWRP Install utility. This too failed resulting in the same “Unable to find partition…” messages above.
What does it really mean “Unable to find partition”? Why can't I restore my backup? Am I supposed to be able to flush a new ROM OS from TWRP Install utility? Any idea on a new direction will be appreciated. Please be patient with me – I am of the generation of printed manuals and am learning this new way.
I just installed SuperSU after unlocking...
When I boot into recovery, it says Unable to find the partition size for recovery and boot.
I then decided to factory reset to get ready to install a new ROM, and it kinda works... Then I try to install the ROM and it fails.
I reboot the system and it just boots into recovery. :/
I checked my downloads, and I downloaded the correct version(-4.2 blob) for my device(tf300t). I followed instructions but still ended up in this boot loop. Any suggestions?
Edit: Found a more updated version of TWRP(I had 2.6.x, found a 2.7)
Everything was smooth sailing from there.
Please help me, I have failed miserably and now need to understand what to do. Please bear with me for the detailed and step-by-step mess that I created.
I have a stock Nexus 9, not rooted, on 5.0.2. I got the OTA update for Android 5.1.1, it failed each time, and I ended up on the page with the little Android on its back, with the red triangle 'warning' sign and the mention 'error'.
I rebooted in Recovery, and cleaned cache, same result.
I rebooted in Recovery, performed a total wipe and reset + cleaned cache, then rebooted into stock Android, and without installing anything (i.e. just pure OS without anything, not even a single additional app), then waited and got the OTA notice again, launched it, only to see the whole thing fail as before.
Here is the log I got each time, when in Recovery (in yellow font):
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
/dev/block/platform/sdhci-tegra.3/by-name/APP hae been remounted R/W; reflash device
to reenable OTA updates
E:Error in @/cache/recovery/block.map
(status 7)
Installation aborted
Then I found this post and a couple of others, took many notes, and I thought I had figured out what needs to be done; here is what I did:
I downloaded adbsetup.exe from this post
I installed everything and it went well. I was able to unlock my bootloader. :good:
I then downloaded this file I got from a link in one of the "help" here posts on XDA (I think it pointed to some Google pages): volantis-lmy47x-factory-3efdc8d4.tgz and I extracted volantis-lmy47x-factory-3efdc8d4.tar.
I unzipped everything and I got image-volantis-lmy47x.zip, (which I unzipped to get the files for step 6 below), plus flash-base.sh, flash-all.sh, flash-all.bat.
I ran flash-all.bat and this updated what it needed to update, (I saw OK, OK, OK, etc. on the tablet while it was happening). :good:
Then I did the following:
- fastboot flash bootloader bootloader-flounder-3.43.0.0114.img :good:
- fastboot reboot-bootloader :good:
(waited for device to reboot)
- fastboot flash recovery recovery.img :good:
- fastboot flash boot boot.img :good:
- fastboot flash system system.img ...... this one failed!
- fastboot flash vendor vendor.img :good:
- fastboot flash cache cache.img :good:
- fastboot reboot :good:
I redid the whole sequence in step 6 above, since it had failed. I got the same results.
Since it was failing again, I went back to the Recovery and did wipe cache, factory reset, etc. and redid it once again.
My device now boots and it seems to have a different boot animation; but I get two messages that keep me from booting correctly: Unfortunately Nfc Service has stopped and Unfortunately, Phone has stopped. These message come on and on again, and I can't do anything else besides saying OK to them.
Please help, what should I do now???? I am open to anything: downgrading, flashing another ROM, etc. as long as I can use ADB.
Please help!!!!
@Xaltotun,
It looks like you need to update your Android SDK (on your PC). That's a typical failure for an out of date fastboot.exe. Google updated the Android SDK about 6 months ago, so that fastboot could handle these much larger system.img files. So I would try updating that first.
And you've done an excellent job, so far, of reading, researching, and fixing things yourself. One last point: whatever happens, DO NOT RELOCK YOUR BOOTLOADER. It will not fix anything, and you will be totally out of options.
cam30era said:
@Xaltotun,
It looks like you need to update your Android SDK (on your PC). That's a typical failure for an out of date fastboot.exe. Google updated the Android SDK about 6 months ago, so that fastboot could handle these much larger system.img files. So I would try updating that first.
Click to expand...
Click to collapse
Thanks for the hint; I followed your advice.
I re-downloaded everything, reinstalled everything, and started the whole process anew, like my step 6 above. And this time it worked! :laugh:
Boy was I relieved!
I however don't understand why flash-all.bat does not flash the system.img file, and why I have to unpack everything and flash it manually. The Google page only offers a cryptic (for those less used to these things) explanation: Once you have the fastboot tool, add it to your PATH environment variable (the flash-all script below must be able to find it). What????
Oh, well..... Next time if OTA does not work, screw it.
PS: I did not relock the bootloader, even if I was tempted....
Xaltotun said:
Thanks for the hint; I followed your advice.
I re-downloaded everything, reinstalled everything, and started the whole process anew, like my step 6 above. And this time it worked! :laugh:
Boy was I relieved!
I however don't understand why flash-all.bat does not flash the system.img file, and why I have to unpack everything and flash it manually. The Google page only offers a cryptic (for those less used to these things) explanation: Once you have the fastboot tool, add it to your PATH environment variable (the flash-all script below must be able to find it). What????
Oh, well..... Next time if OTA does not work, screw it.
PS: I did not relock the bootloader, even if I was tempted....
Click to expand...
Click to collapse
Flash-all simply does not work for N9 or Nexus 6. You'll just have to accept it.
cam30era said:
Flash-all simply does not work for N9 or Nexus 6. You'll just have to accept it.
Click to expand...
Click to collapse
I installed a custom rom (Nitrogen OS 8.1.0 oreo ) and just after 2 days I had issue with my phone services. So I restarted my phone but stuck in bootloop.
Then, I tried to install the stock rom from google that is 7.1.1 the latest one. but failed to flash with nexus toolkit.
I then tried it with fastboot but failed.
I also tried to fastbood the same nitrogen os 8.1.0 as adb sideload and Total xfer: 1.00x ruined me.
Please help me.
uzairahmad1986 said:
I installed a custom rom (Nitrogen OS 8.1.0 oreo ) and just after 2 days I had issue with my phone services. So I restarted my phone but stuck in bootloop.
Then, I tried to install the stock rom from google that is 7.1.1 the latest one. but failed to flash with nexus toolkit.
I then tried it with fastboot but failed.
I also tried to fastbood the same nitrogen os 8.1.0 as adb sideload and Total xfer: 1.00x ruined me.
Please help me.
Click to expand...
Click to collapse
I'm sorry, but this thread is nearly 3 years old, and dead. My N9 is long gone. I'd suggest you try another thread that is still active for help. Good luck.
uzairahmad1986 said:
I installed a custom rom (Nitrogen OS 8.1.0 oreo ) and just after 2 days I had issue with my phone services. So I restarted my phone but stuck in bootloop.
Then, I tried to install the stock rom from google that is 7.1.1 the latest one. but failed to flash with nexus toolkit.
I then tried it with fastboot but failed.
I also tried to fastbood the same nitrogen os 8.1.0 as adb sideload and Total xfer: 1.00x ruined me.
Please help me.
Click to expand...
Click to collapse
What you linked to is for the N6. I'm surprised it worked at all. Unless you're in the wrong forum as this is for the N9.
Sent from my [device_name] using XDA-Developers Legacy app
I've searched through the forums, but haven't found an answer, so I'm starting a new thread.
I received a G Watch as a gift last weekend, and it had a problem on the initial configuration. It wasn't able to connect and download any updates, so I manually flashed the updated firmware. Everything is working fine, and I'm on build LDZ22D. I was able to use G Watch Restore Tools V9 to flash system and recovery (and, in fact, boot, although that didn't seem to do anything), which got my watch up to an earlier version.
I then tried LG G Watch Return to Stock LDZ22D to get to my current build. However, I'm notified that there's an update available, but I'm not able to install it. When I try to install it through the regular user interface, it boots to recovery.
I've tried using the stock recovery, but had no luck with getting anything other than the android with the sore tummy appearing. I've used TWRP to try to flash update.zip (the stock downloaded update) and also tried this image.
When I try to apply update.zip through TWRP recovery, it gives me an error.
E: Error executing updater binary in zip '/cache/update.zip'
Package expects build fingerprint of lge/platina/dory:5.1.1/LDZ22D/19259530:user/release-keys or lge/platina/dory:5.1.1/LCA43/2160025:user/release-keys; this device has lge/cm_dory/dory:4.4.2/KVT9L/561735d166:eng/test-keys
It looks like the release keys are set to a nexus 7 build number (I don't understand how that's even possible). Is there a way to rewrite those keys? I understand they're part of the digital signing process, but I'm not sure why they didn't reset when I used the return to stock tool to flash my current image, which is the actual LDZ22D build. I appear to have a key mismatch. I've tried reflashing boot.img, system.img, and recovery.img manually (the ones included in the return to stock download), but they don't seem to work.
I get the same error when I try to flash the update I downloaded through ADB sideload. I'm frustrated, since my watch gives me this error, then after I reboot, it goes ahead and downloads the update.zip again, killing my cell data plan.
I'd love any help or insight into this. Is there a way to turn off the verification of the keys, or write the actual keys associated with my build? I'm new to working with a watch, and I've got limited experience working with phones/tablets through custom recovery. I'm not interested in a custom rom for my watch - I just wanted to get it to run properly on the stock image, and had a whack at getting it set up through developer options instead of letting it error out when I first got it.
Thanks in advance!
Still working on it
Okay, after quite a bit more research, it appears that my recovery.img doesn't match the rest of the build. I've tried the LDZ22D recovery.img, but it doesn't respond to any user input.
I'm now trying the factory image files from this post.
It seems there are a few people having problems getting to LCA43 recently. If you have an unlocked bootloader by now, you can try this method (TWRP restore from my LCA43 system+boot backup).
Hope this helps.
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 ?????
So Ive never thought about or had anyone around me ever talk about android developers or enthusiasts or whatever it is... the past few years I ran into quite a few issues that ive needed root.. so I tried researching and trying to learn and well.. i should of maybe hopped on here before i did the actual attempt... SO heres my **** up!
I unlocked my bootloader... then followed a guide and I had tried flashing a img without flashing twrp and magisk and so now I figured out how to boot into recovery, twrp... and flashed magisk and then I tried installing no verity opt encrypt 6.1 and it states failed then i started moving around through twrp and tried mounting data and it will not even highlight the data checkbox and wont let me repair the data under the wipe command and wont let me change it to any of the extensions? no os found it says it wont let me format userdata says this.
fastboot: error; cannot generate image for userdata
please if you can help me out... any help would be greatly appreciated and would be lifesaving... thx
I am new to trying out this kind of stuff i believe i flashed possibly the wrong boot img! before I had flashed twrp and well i was stuck in fastboot.. but managed to get twrp and then flashed magisk and tried flashing no verity opt encryption but it will not flash I'm unable to mount the checkbox data in mount It wont even highlight the checkbox... i go to try to wipe some partitions and the only one it lets me wipe is metadata... I've tried format and It said failed to generate userdata partition and then i = tried fastboot erase userdata it worked tried erase/format cache it didn't work so any help at this would be greatly appreciated... thanks for your time
Re-flash phone's Stock ROM to get rid off of all modifications you applied so far.
so just download original stock rom to my computer into the file that holds adb and fastboot and then flash it and then reboot and it should work?
You shouldn't post duplicate threads.. I noticed you already had one the same day a few hours earlier for the same thing.. You might want to read the rules before posting to avoid any issues.
@Learnitright Hello, as mentioned above, please do not make duplicate threads with same topic. All replies from other users can be on this thread.
I have merged another thread by you into this one. Thanks.
I am sorry i wasnt sure if the first one went through or not I am stuck with a slow computer isnt very good im just trying to fix my phone.. If anyone could help?
You need stock-ROM and msm-tool, sadly metro version stock-ROM might not available for public right now. You should have used
Code:
fastboot boot twrp-n200.img
instead of flash recovery.
kdm6389 said:
You need stock-ROM and msm-tool, sadly metro version stock-ROM might not available for public right now. You should have used
Code:
fastboot boot twrp-n200.img
instead of flash recovery.
Click to expand...
Click to collapse
even if its just named recovery.img in the folder where i open up the command prompt ? sorry im so new to this
try msm-tool with TMO-Stock-ROM, maybe yout phone become TMO from Metro.