Hi all, well I think I have all but wrecked my 16gb shield tv. I unlocked bootloader, installed twrp and rooted, all was working fine. Then I decided to flash the full android rom that is on the forum . before doing so, i used twrp and made a backup. I installed the full android rom, although it seemed to work fine, i was not crazy about it and decided to go back to the original OS, so I booted up in twrp and went to the restore function, there were no backups to restore , I guess when I installed the system img for the full android it erased my backup somehow. anyway, I next went to nvidia website and downloaded the restore image for the 16gb shield tv, i booted in to bootloader and was following the instructions to restore the shield. all seems to go fine until I try to flash the system img, then I get the error "invalid sparse file format at unknown block 0000" it tries to continue but fails, afterwards the system will not boot at all, I can get back to twrp recovery an flash the full android rom just fine, but am not able to flash back the original os without that error. any suggestions would be greatly appreciated, as I am stuck at this point as what to attempt next. thanks. Here is a pic of the errors i am getting.
Use a windows pc or the last fastboot version from android sdk or a better otg cable.
Is just a connection problem or the extracted system.img was corrupted when extracted.
If you not solve download again the stock firmware and unzip with a decent tool. Is possoble that when you extracted the archive your stock system.img was corrupted.
I flashed my Shield a million times with no problem. Also the ridiculous stock firmware just to do some logcat.
Shield Console is solid as a rock, you can do anything.
Thanks for the reply zulu, I will re download the img and try again, although I'm concerned something is wrong with the partition, as I was able to flash the full android rom, but now can no longer flash it either. I will let you know the results as soon as I'm able to retry.
cdsn99 said:
Thanks for the reply zulu, I will re download the img and try again, although I'm concerned something is wrong with the partition, as I was able to flash the full android rom, but now can no longer flash it either. I will let you know the results as soon as I'm able to retry.
Click to expand...
Click to collapse
Don't worry all is ok. I'm here to help you step by step if necessary.
my friend had a problem like this with another device, another firmware. He used a MAC OS to extract the firmware, and the system.img was not extracted well.
What are you using ? MAC, Windows, Linux ? what is your fastboot version ? do you use an usb otg cable ? what is your precise procedure to go in the bootloader ?
i use an usb otg cable to use fastboot from my PC.
to go in bootloader, I connect the usb otg cable to Shield, that is already connected also to my PC usb port, after i insert the power cable to Shield, and after i press quickly the power button for 5 seconds.
From Windows, if i try to install with the normal micro usb cable (exspecially the one that come with Shield), i have problems similar to your problem.
you can try also to install only the stock system.img to see what happen.
fastboot flash system system.img
fastboot -w (this clear user data, but is necessary when you switch from a firmware to another)
fastboot reboot
i installed the stock and the full Android many many times. If the Shield resist to me, can resist to all
zulu99 said:
Don't worry all is ok. I'm here to help you step by step if necessary.
my friend had a problem like this with another device, another firmware. He used a MAC OS to extract the firmware, and the system.img was not extracted well.
What are you using ? MAC, Windows, Linux ? what is your fastboot version ? do you use an usb otg cable ? what is your precise procedure to go in the bootloader ?
i use an usb otg cable to use fastboot from my PC.
to go in bootloader, I connect the usb otg cable to Shield, that is already connected also to my PC usb port, after i insert the power cable to Shield, and after i press quickly the power button for 5 seconds.
From Windows, if i try to install with the normal micro usb cable (exspecially the one that come with Shield), i have problems similar to your problem.
you can try also to install only the stock system.img to see what happen.
fastboot flash system system.img
fastboot -w (this clear user data, but is necessary when you switch from a firmware to another)
fastboot reboot
i installed the stock and the full Android many many times. If the Shield resist to me, can resist to all
Click to expand...
Click to collapse
Hi Zulu, thanks for the help, I don't have an otg cable, I just use the cable that came with the shield tv. Anyway, you were right, i re downloaded the image and all flashed well, who would have thought. wow, thanks so much for the info, hopefully I won't screw it up again. I like exploring new roms, but panic when I mess things up, I have been trying to re flash this thing for days, with all partitions flashing fine except for the system partition, anyway, downloading the new file must have fixed it , I also went into factory recovery and did a factory reset, maybe that had something to with it also, i really don't know. anyway, thanks again for your assistance.
cdsn99 said:
Hi Zulu, thanks for the help, I don't have an otg cable, I just use the cable that came with the shield tv. Anyway, you were right, i re downloaded the image and all flashed well, who would have thought. wow, thanks so much for the info, hopefully I won't screw it up again. I like exploring new roms, but panic when I mess things up, I have been trying to re flash this thing for days, with all partitions flashing fine except for the system partition, anyway, downloading the new file must have fixed it , I also went into factory recovery and did a factory reset, maybe that had something to with it also, i really don't know. anyway, thanks again for your assistance.
Click to expand...
Click to collapse
I'm at disposal. Thanks also to you to report back to me.
cdsn99 said:
Thanks for the reply zulu, I will re download the img and try again, although I'm concerned something is wrong with the partition, as I was able to flash the full android rom, but now can no longer flash it either. I will let you know the results as soon as I'm able to retry.
Click to expand...
Click to collapse
I had that issue before in a different device. The recovery had botched formatting the system partition. I tried to sideload the whole operating system, but in the end I just had to boot the recovery and format system again. It fixed my problem.
tooandrew said:
I had that issue before in a different device. The recovery had botched formatting the system partition. I tried to sideload the whole operating system, but in the end I just had to boot the recovery and format system again. It fixed my problem.
Click to expand...
Click to collapse
Yea I've experienced that too, I think the last time it happened it was on my Nexus 6. Try and execute this while in fastboot fastboot format system and then reflashing the system image.
Related
I was going back to full stock on my 5X, and things must have give sideways... It got stuck in a bootloop (even a stock recovery FDR hangs) and now I fear it might be bricked. I had always figured that if all else fails, I could flash something in fastboot, but that's not even available.
I can get out into the fastboot/rescue mode, and my laptop sees the device plugged in, but fastboot doesn't list it as a device, so I can't issue any commands.
Are there any 'last ditch' methods that might get this thing out of the toilet?
LeoRex said:
I was going back to full stock on my 5X, and things must have give sideways... It got stuck in a bootloop (even a stock recovery FDR hangs) and now I fear it might be bricked. I had always figured that if all else fails, I could flash something in fastboot, but that's not even available.
I can get out into the fastboot/rescue mode, and my laptop sees the device plugged in, but fastboot doesn't list it as a device, so I can't issue any commands.
Are there any 'last ditch' methods that might get this thing out of the toilet?
Click to expand...
Click to collapse
These are instructions I posted for someone else with a L24 you need to adjust the files to your phone L2x
The dload/update.app works, just be patient and follow the instructions I posted.
If you need to restore to Stock B151 use this TWRP backup >> https://www.androidfilehost.com/?fid=24588232905720643
You also need this version of TWRP to restore it >> https://www.androidfilehost.com/?fid=24545070682210514
Fastboot flash TWRP.img
in TWRP go to backup and check only boot.img > make the backup
now extract the b151 backup to your PC and copy it to the phone
their will be a directory named TWRP/BACKUPS/yourserialnumber/put the backup here
Now in TWRP choose Restore choose the backup you just copied over and be sure all the boxes are checked for restore
swipe to restore
be sure B331 dload/update.app are on the sdcard
In TWRP choose Reboot / Power Off
unplug the usb
hold power + volume up + volume down
when you see the first honor screen let go of power and hold the volume buttons till the update starts (be patient it takes a while)
EMUI recovery will load and do the update when it reboots your done
Click to expand...
Click to collapse
Yeah... been here, done this already unfortunately. The update.app is on there... The process actually gets to 5% then it goes and tries to boot, and hangs. That's where I was when I tried to get twrp on there to take a look at the filesystem.
Maybe the update.app file is corrupt/not fully copied. I'll copy it back on the SD and try again tonight.
Usually a very old (stable) release is more advisable if it's Lollipop.
Are you sure you're not running a second instance of ADB? I got that once and had to check windows processes.
Changing usb cable?
LeoRex said:
Yeah... been here, done this already unfortunately. The update.app is on there... The process actually gets to 5% then it goes and tries to boot, and hangs. That's where I was when I tried to get twrp on there to take a look at the filesystem.
Maybe the update.app file is corrupt/not fully copied. I'll copy it back on the SD and try again tonight.
Click to expand...
Click to collapse
So you restored a TWRP backup of the stock System / Boot and Recovery and the Update.APP failed ?
you used the wrong update.app or the wrong backup is the only explanation, as this works 100% of the time
Other option is you have messed up partitions, usually flashed img files from different rom versions.
Well, turns out that the update.app file on the SD was corrupt. I copied it again and the stock update till took over and loaded things properly.
Second issue is a bear... My laptop NP longer can communicate with the phone via fastboot. Based on what I see, it's a driver issue on my laptop... So I gotta figure that out of I want to get TWRP back on there.
LeoRex said:
Well, turns out that the update.app file on the SD was corrupt. I copied it again and the stock update till took over and loaded things properly.
Second issue is a bear... My laptop NP longer can communicate with the phone via fastboot. Based on what I see, it's a driver issue on my laptop... So I gotta figure that out of I want to get TWRP back on there.
Click to expand...
Click to collapse
[emoji3] sorry but you aren't getting any rest are you? Once you fix something you find another thing to fix...
If you use Windows, try and make restore points occasionally so that you can revert to the last fully working point.
Also if you can, see if there's any checksum for the firmware update files. It helps a lot.
Hi all,
I went ahead and rooted my Mate 10 Pro today - I unlocked my bootloader, installed TWRP and got it running pretty sweet. Then, like a tool - tried installing xposed framework and got myself into a boot loop.
I can get to fastboot, I can get into twrp - but for the life of me don't know how to get a system wipe and fresh format! I've tried flashing LineageOS - but that's stuck on a loading screen and then boot loops after about 10minutes.
What happens is I turn my phone on - see the bootloader message - if I do nothing there's a 50/50 changes Huawei's eRecovery window opens (where if i connect it to the wifi, it fails and gives me the option of reboot or shutdown) or LineageOS boot animation loops for about 10minutes before shutting down.
At this stage, I don't mind what rom i get working - i just want something working and I'm really regretting xposed (I should of googled!).
I really don't want to pay $40 usd - and am happy tinkering around, but would appreciate some solid advice on how I can use TWRP to wipe everything and start again!
I'm also a little confused as to why eRecovery is coming up at all - and why it can't download anything!!!!!
Can someone help me get a phone back?
Thanks!
Yeah, I bootlooped going with xposed too, but I have the Mate 10 (regular) and no TWRP. Can you get to TWRP and simply flash a clean ROM? If not, which I presume is the case, can you get to Fastboot? To try, when you get to the eRecovery window, use the option to shut down your phone. Then press the power button and, while holding it, plus in your USB cable (the other end which should already be attached to your computer). Then go to Mankindtw's thread for flashing ROMs (Mate 10 Flash Oreo one). Basically, you download three zip files from a russian language page with all the latest Huawei ROMs, repackage them within his utility, and then flash them from within his utility. Worked for me.
download update.zip (for your firmware) from http://pro-teammt.ru/firmware-database
Extract update.app from update.zip
Download Huawei Update Extractor (open it and go to settings and disable header check)
Open update.app in Huawei Update Extractor
Extract SYSTEM from update.app using Huawei Update Extractor.
(Not sure if Xposed modifies vendor too, so you might have to extract that as well)
Fastboot flash system system.img
See if it boots now. If not you could try extracting recovery_ramdisk and flash recovery_ramdisk.img to the recovery_ramdisk partition then factory reset from stock recovery.
If it does modify vendor you'd have to flash vendor as well.
Or you could try flashing lineage os system, flash recovery_ramdisk and factory reset from stock recovery (factory reset is needed to get aosp roms running)
If it still fails, use mankindtws HWOTA as described by rogerinnyc above. (link: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814)
Stock rom seems to be installing. TY for your help
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
ChriKn said:
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Click to expand...
Click to collapse
Install this regfix https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
However, you would probably have had problems before too when flashing twrp.
But worth a shot I guess.
Didn't see it said you tried on win 7 too.
And if it worked before on Win 10 it should work without it.
I guess you could push system.img to /data/system.img then tap Install and selectInternal storage, tap on (go up one level) in browser, now you'll be at /. Tap on /data and then on system.img. Flash to 'System Image'.
Edit: I've tested with recovery and that flashes fine from /data/.
please see below;
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Toldorn said:
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Click to expand...
Click to collapse
Boot.img is for Nougat. Oreo uses ramdisk.
Try wiping data in TWRP (Wipe - Format Data).
You can't turn off encryption in TWRP. It's controlled by /vendor/etc/*.fstab (* = kirin970 in this case). (You can temporarily turn off encryption but it re-encrypts after booting if fstab is untouched)
But removing encryption won't fix you bootlooping, and that command you used is for Full disk encryption, we use file based encryption.
You could also try flashing back stock recovery and do factory reset from there.
Edit: Oh, you're the guy who PM'd me
I've reflashed my 'system.img' as before - but im having trouble getting into factory reset menu.
all it ever does is go into e'Recovery instead, which is useless.
Also, my booting image is still a green page of pixels - rather than a huawei logo.
Hi. I have a bla-a09 and need help. can boot into twrp but will not boot.
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 ?????
In August, I bought this tablet, Lenovo TAB M10 (TB-X505F), to read and study for University. I rooted the device with Magisk. I also bought a 64 GB SD Card, which I installed and configured to expand the internal memory. About a month later, an OTA update failed to install; I removed the SD card, the OTA installed and the tablet went back to factory defaults; not pleasant, but not terrible. I reconfigured it, and kept using it.
Last couple of weeks, a new OTA was released. it tried to install a few times, and failed; just rebooted the OS with a generic failure message. One morning, it tried to update during the night, and I found it on the Recovery menu; a generic error message said it couldn't update. The OTA tried to update some more times, rebooting to the OS or going to the Recovery screen.
Yesterday, I removed the SD card and tried to install the OTA update; it failed, and sent the tablet again to factory defaults. Something happened, I can't tell what it was, and now the tablet is screwed. It won't boot; it won't go to recovery. I have no ADB, but I have Fastboot.
I worked with tablets and phones many times before: recovering, rooting, flashing, upgrading, downgrading, unlocking, unbricking, etc. I have the original ROM, and also the latest. I have the original boot.img, and the modified by Magisk. I tried to fastboot flash boot, recovery, and TWRP; it flashes "OK", but nothing happens: it won't boot to recovery. I tried to fastboot flash system, but it didn't do anything. This is a "system_1.img", "system_2.img", "system_n.img", not a ".sparsechunk"; I never had to deal with this one, I might be doing something wrong. I tried to fastboot flashall; nothing seems to work, although it looks like it is flashing ok. I don't know what to do or try anymore. Any help will be greatly appreciated. NB: I'm in Linux; I'll prepare a Windows box, in case it is needed.
Thank you very much. Best regards.
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
jwoegerbauer said:
I suggest you to re-flash tablet's Stock ROM to bring tablet back to its original state.
FYI: Installing official updates from your manufacturer or carrier is not supported by TWRP.
Click to expand...
Click to collapse
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your response. I'm assuming is a Windows tool... I'm finishing setting up a Windows box to test; I'll take a look at it as soon as I have it; I'll test it and post the results.
farotta said:
Yes, thank you for your suggestion. Any ideas on how? I got the stock ROMs, but when I re-flash each partition, it says "flash OK", except with the System partition, which fastboot seems to not being able to handle this "system_1.img", "system_2.img", "system_n.img" format... Besides, the recovery partition flashed OK, but I'm not able to boot to recovery mode. The flashall didn't work either, with or without the -w argument. I'm on a Linux machine.
Click to expand...
Click to collapse
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
jwoegerbauer said:
Why not re-flash the Stock ROM by means of "adb sideload" instead of "fastboot ..."?
Click to expand...
Click to collapse
Because I didn't have adb, only fastboot.
sd_shadow said:
There is a Lenovo smart assistant PC program
That can reflash firmware for some devices try the flash rescue option.
There is a link to download in my LMSA thread.
My thread is written for Motorola devices and I haven't used any Lenovo devices.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ocean using XDA Labs
Click to expand...
Click to collapse
THIS THING WORKED LIKE MAGIC! THANK YOU VERY MUCH!
It was more difficult to set up the Windows box to make it work, than the rescuing of the tablet with this tool. A few clicks, wait for the image to download, follow some easy and clear instructions, and my device is alive, again. I feel I can't thank you enough.
NOTE: Will just clarify, probably am an idiot and messed up a simple thing, so please do take everything I say here with a grain of salt.
The phone was rooted with Magisk v25.1, and I had also installed the unofficial TWRP from this very forum. I also believe I was on 11.0.4.0 of OxygenOS. It is the factory unlocked version.
I was following a guide to update the phone through fastboot, since stock recovery was just showing a screen with a keyboard, which appeared to be impossible to get past. Said guide is here.
Linked in the guide above is the 8th step of that guide, where you then flash the files from the OTA file after extracting them with payload_dumper. I believe the version I was extracting was 11.0.7.0, but to be honest, it was whatever I downloaded off of the Oxygen Updater app, so I'm not entirely certain. I had installed "boot.img", "dtbo.img", and "modem.img", then getting to "abl.img", before receiving an error: Flashing is not allowed for Critical Partitions. "Well," I thought, "I suppose I just can't do it then. *shrug*. Back to this version of OxygenOS I go." That was before remembering to attempt doing "fastboot flashing unlock_critical", which, gave me: Device already unlocked! Well, clearly not, as I should've been able to write abl.img. Attempting to flash again gave me nothing, so, I said screw it.
Well, upon trying to hit start in fastboot, I noticed the phone were now bootlooping back to fastboot over and over. So, I'm lead to a few conclusions:
a) I'm gonna need "dtbo.img" and "modem.img" (I already have boot.img) from the 11.0.4.0 stock image. I cannot find the actual image, so I'm lead to now needing some help here.
b) There has to be some way to continue flashing the files in fastboot (that is, if that is the correct course of action; I am assuming, please feel free to correct me).
c) There is a different way to fixing this than I am thinking.
d) Worst case scenario, this thing has to go back to OnePlus.
Would really hate to have to get to Step D, as this phone was a birthday present to me, and I'd find it wholly embarrassing to throw my hands up in the air a single day after getting the damn thing for my birthday just to need to send it back already, but if nobody can help me out here, then that's where I'm at.
Would appreciate any and all help/suggestions! Thanks.
EDIT: Phone is stuck in Qualcomm Crashdump mode now, bootable into fastboot with vol up+down+power. Looks like it's irreparable. Already working with OnePlus to get it replaced.
EDIT 2: Fixed it!! Big thanks to this thread for the help.
1)get a usb otg and pendrive
2)download and tranfer pixel experience full build zip file in you pendrive
3)go to fastboot and flash twrp recovery misc and vbmeta and boot to recovery
4)insert pendrive in usb otg and connect it to phone
5)click on install then click on select storage usb otg and flash the pixel experience like you flash other files
6)reboot the phone
7)after setting up download the rom you want to and go to fastboot then flash twrp again 3rd step
8)flash the rom you want to install and flash g-apps reboot your phone
9)complete all steps and you have your phone with custom os/rom
Raghaov said:
1)get a usb otg and pendrive
2)download and tranfer pixel experience full build zip file in you pendrive
3)go to fastboot and flash twrp recovery misc and vbmeta and boot to recovery
4)insert pendrive in usb otg and connect it to phone
5)click on install then click on select storage usb otg and flash the pixel experience like you flash other files
6)reboot the phone
7)after setting up download the rom you want to and go to fastboot then flash twrp again 3rd step
8)flash the rom you want to install and flash g-apps reboot your phone
9)complete all steps and you have your phone with custom os/rom
Click to expand...
Click to collapse
No offense, but this is a pretty dumb response. I don't think you're very familiar with how TWRP is on this device, nor the state of my own. I cannot mount storage, and even if I could, I don't even believe this rom exists for the N200 5G. Along with that, why would a USB OTG be necessary when there's.. I don't know, an SD card slot that works fine and is readable?
Also step 3 is a little laughable. That's why I'm even here in the first place; I couldn't flash every damn thing!
I'll share Oxygen OS 12 if you want it, and let me know if I should keep searching.
Just use payload dumper go to dump the payload and then flash the files with this guide.
Edit: Uploading it via xda didn't work, so here's the google drive link.
justauserthatusesaphone said:
I'll share Oxygen OS 12 if you want it, and let me know if I should keep searching.
Just use payload dumper go to dump the payload and then flash the files with this guide.
Edit: Uploading it via xda didn't work, so here's the google drive link.
Click to expand...
Click to collapse
Do you have one for metro T-MO variant?
Tyreethetruth said:
Do you have one for metro T-MO variant?
Click to expand...
Click to collapse
Nope, I also don't know how to get it, unfortunately.
sounds to me like you dont want a real answer i mean at least respect the one person that replied to your post, not our fault you got yourself in this situation.