Related
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
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 PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
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 8.
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 (twrp-3.2.1-0-z380m.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-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.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". 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.
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
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
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 ?????
I've bricked my phone and am in need of help!
What I've done:
Unlocked bootloader with a code from DC-Unlocker then using minimal ADB and Fastboot to unlock
Flashed TWRP 3.1.1
Installed Magisk
Took TWRP backup - but I was unable to backup Data (I believe this was due to encryption - recovery.log shwed errors initially on Bluedorid files)
Wiped data with TWPR to try and do a factory reset
This is where my problems started and now I cant restore boot with TWPR the error is "No such file or directory"
I can ADB pull my recovery.log which says
Read info file, restore size is 12444160
Restoring 6 partitions...
Total restore size is 4512MB
I:Restore filename is: /external_sd/TWRP/BACKUPS/L5NDU17B18000539/Stock V7 2018-06-23--16-58-45/boot.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring Boot...
Error opening: '' (No such file or directory)
I can restore OEM recovery and do a factory reset but it hangs at 99%
power down then it goes back to factory reset and goes to 100% - message "Reset Successful!"
but... then it gets stuck in a boot loop
I've tried downloading other stock ROMS and extracting and flashing images via fastboot (Boot, cust, product, recovery, system, vendor, version)
I've tried Huawei Multi-tool but I lack the Userdata.img disk image
I've tried flashing Resurrection Remix N v5.8.5 For Honor 9 (STF) but without success, although the TWRP install says it is successful and the vendor.img flashes fine.
I've tried extracting UPDATE.app files and putting them in sd_card/dload and then 3 button resetting
I've tried the above in external_sd/dload (not sure why - desperation)
I've tried looking on as many threads as I can find on XDA but with no luck
I can always get to fastboot, flash TWRP or OEM recovery, I can also run ADB commands via Putty (in command line they display strangely)
Any suggestions would be greatly appreciated! I am at a loss an quite frustrated, and have been working on this for maybe 15 hours now.:crying:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Fixed!
Thank you, I think I even saw this thread but for some reason did not download the file, also the exfat formatting tip was excellent. I owe you a beer!
Can I always use this method to go back if I totally destroy things again even If I update to Oreo?
oslo83 said:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
Unfortunatly, there only nougat 'service repair firmware' available publicly as far I know.
So, for now, you can only use this when on nougat.
When on oreo, you should use HuRUpdater with oreo's Twrp.
Or if you're oreo device is really messed badly, a paying app called DC-Phoenix then HuRUpdater.
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.15 EU Full Stock Firmware for OnePlus Nord 2Requirements :
ADB & Fastboot + Google & MTK drivers
Partitionsbackupper ( @Raygen )
A.15 Firmware ( @AssoDiPicche )
Instructions :
Download the .zip and the latest version of PartitionsBackupper.
Download A.15 Firmware, extract it and put all files in the PartitionsBackupper folder.
Reboot your phone in fastboot mode (Power off, than power button + volume down)
Run PartitionsBackupper.bat, choosing the restore option, to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
Type on command line "fastboot flashing lock"
Enjoy your brand new OPNord2.
Credits:
@Raygen (For PartitionsBackupper)
@AssoDiPicche (To die with this phone for two days)
AssoDiPicche said:
/*
* Your warranty is... still valid!
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research before asking or use anything on this thread.
*/
OxygenOS 11.3 A.15 EU Full Stock Firmware for OnePlus Nord 2Requirements :
ADB & Fastboot + Google & MTK drivers
Partitionsbackupper ( @Raygen )
A.15 Firmware ( @AssoDiPicche )
Instructions :
Download the .zip and the latest version of PartitionsBackupper.
Download A.15 Firmware, extract it and put all files in the PartitionsBackupper folder.
Reboot your phone in fastboot mode (Power off, than power button + volume down)
Run PartitionsBackupper.bat, choosing the restore option, to flash all partitions with fastboot.
I reccomend to do a full data format with the stock recovery before going back messing around. It usually wipes better than TWRP.
Type on command line "fastboot flashing lock"
Enjoy your brand new OPNord2.
Credits:
@Raygen (For PartitionsBackupper)
@AssoDiPicche (To die with this phone for two days)
Click to expand...
Click to collapse
now I try to do the operation
The file it's in the same folder. Where i wrong?
Cugno83 said:
The file it's in the same folder. Where i wrong?
Click to expand...
Click to collapse
Change your ADB tool. try "Tiny ADB and Fastboot".
Ok, i restored all and lock bootloader. the guide is not really step by step, but it can work with a minimum of knowledge
Cugno83 said:
Ok, i restored all and lock bootloader. the guide is not really step by step, but it can work with a minimum of knowledge
Click to expand...
Click to collapse
please send me pm and tell me what you did!
Can i reflash stock oxygenOS rom and return completely stock without locking the bootloader? I flashed elixir, but the wifi doesn't work, so i would like to turn on stock, maybe doing root and installing magisk, viper ecc... Is there a complete oxygen that i can flash with maybe sideload on twrp or things like that?
Andrea17982 said:
Can i reflash stock oxygenOS rom and return completely stock without locking the bootloader? I flashed elixir, but the wifi doesn't work, so i would like to turn on stock, maybe doing root and installing magisk, viper ecc... Is there a complete oxygen that i can flash with maybe sideload on twrp or things like that?
Click to expand...
Click to collapse
If you use this, you must unlock bootloader and install twrp aftet that.
I did it, and the bat told me he flashed everything without problem, but then it rebooted me to twrp, and my bootloader is still unlocked, but most importantly, when i go "reboot system" it stays on oneplus logo and no os start... So I'm semi bricked now without OS, at least I have twrp to make some experiment... ideas? I retry the same thing?
Edit: the phone booted... with Elixir OS (?) so nothing changed, still my wifi and bluetooth don't work...
Andrea17982 said:
I did it, and the bat told me he flashed everything without problem, but then it rebooted me to twrp, and my bootloader is still unlocked, but most importantly, when i go "reboot system" it stays on oneplus logo and no os start... So I'm semi bricked now without OS, at least I have twrp to make some experiment... ideas? I retry the same thing?
Edit: the phone booted... with Elixir OS (?) so nothing changed, still my wifi and bluetooth don't work...
Click to expand...
Click to collapse
Try ask in "nord 2 community" telegram group. They are really helpful.
Try to press 1 botton. And use image of dn2103.zip
Don't try restore your backup file. Try restore file unzipped of a.15 firmware, and you return to stock and lock bootloader
Hi! I have a some problem! The first part of the firmware is fine, and after a reboot this happens
Same problem here.
Error with flashboot command.
Please put the "PartitionsBackup" folder with all the partition images in the same directory of this script.
----------------------------------------
Errors were detected while running the script.
You can find the error logs in the "PBlog.txt" file.
Press any key to continue . . .
I have tried this and it worked, partly. The process stopped on flashing vendor and nothing happened for hours. So I disconnected the phone and it boots fine. I can set up everything, but updates fails. It's now on A15 and will not update. I have also tried to lock the bootloader again, but then the phone won't boot at all, something about an error to boot/system. If I unlock the bootloader, it works again.
Something is clearly wrong here. How can I restore my device back to full working stock again?
I was on A17 before installing TWRP + PixelExperience Rom. But when I wanted to return to stock all hell broke loose
jadajada said:
I have tried this and it worked, partly. The process stopped on flashing vendor and nothing happened for hours. So I disconnected the phone and it boots fine. I can set up everything, but updates fails. It's now on A15 and will not update. I have also tried to lock the bootloader again, but then the phone won't boot at all, something about an error to boot/system. If I unlock the bootloader, it works again.
Something is clearly wrong here. How can I restore my device back to full working stock again?
I was on A17 before installing TWRP + PixelExperience Rom. But when I wanted to return to stock all hell broke loose
Click to expand...
Click to collapse
Any luck?
shivbizle said:
Please put the "PartitionsBackup" folder with all the partition images in the same directory of this script.
----------------------------------------
Errors were detected while running the script.
You can find the error logs in the "PBlog.txt" file.
Press any key to continue . . .
Click to expand...
Click to collapse
I've got the same error! Trying to restore my phone from a PixelExperience overheating and camera nightmare
Should I "Read Partitions" in mtkclient only the ones that are present in mtkclinet and not the A.15 firmware file?
Thanks a lot, this really saved me!
After flashing I got error: "The current image(boot/recovery have been destroyed and can not boot."
And here is how I got around that:
It was possible to boot into fastboot mode only after shutting down the phone first. (from recovery)
And then pressing the key combination while powering up.
Then I ran "fastboot flashing unlock" to get around that "error with fastboot command".
and then I flashed boot and vbmeta with the fastboot command. After that It finally booted.
Then I locked the bootloader and installed all the updates.
Hi everyone!
I'm using a Samsung gt-n8010. It could be done for due to the age, but maybe there is still hope.
My problem is that the tablet boots always to TWRP recovery and I can switch to download mode as well. Everything seems all right, internal storage and sd card shows exactly how they should, BUT... I can't do anything in TWRP. If I have the Keep system partition read only unticked, it still says the storage is read only and /data/media is not accessable. I can see it and access it with TWRP File manager. I tried flashing ROM and Recovery, also stockROM with Odin, but Failed. Clearing Cache, Data, Dalvik... also ends up with error. Format Data works, and also changing the partition types, but when I reboot device, it all comes back the same as before, no changes take effect. In Download mode I tried to use Adb from computer terminal, but it was stuck saying 'Waiting for device'. If Tab is in Recovery my PC shows both internal storage and sd card, but the internal storage is empty when I open it.
For details: I use Lineage OS 18.1 with TWRP 3.6.1_9-0. On my computer I use Linux Mint 20.3, but I tried with a laptop using Win10 as well, no success.
I've read many solutions on 'Unmodified system partition' or some had 0MB internal storage problem, but in my case that is different, as I have them all, but it seems all is read only and not accessable. I even tried to have the last Backup (2 month old) set using Restore of TWRP, but during the process, the tablet reboots and TWRP comes up again. I can't even turn it off, as TWRP comes up after some minutes.
Please help me somehow to be able to use the Tablet. If you need any further details, just tell me.
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
I see your point. I intended to change/downgrade LineageOS version, but I was not successful. Now I am not able to do a factory reset either with success from TWRP, but I give a try to your adb codes. Give me some time
leathan said:
TWRP is not out yet on android 12, if you have it as of writing it wont be able to unencrypt your device. So all you can do is use it to install roms (YOU MUST FIRST FACTORY RESET THE DEVICE).
I also have never used odin as I have prefered adb
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
adb should work in twrp?
Click to expand...
Click to collapse
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC). But no effect First I did a FactoryWipe (successful) and went back to the Terminal each time. I tried with ROM zip and TWRP img as well, but after rebooting, TWRP 3.6.1 comes back again. I downloaded Lineage OS 17.1 (with GAPPS pico) and TWRP 3.5.0-9. It seems somehow I got stuck with that TWRP 3.6 and all I get on every attempt of flashing or wiping is it can't see '/data/media (No such file or directory)' or 'Unable to make /cache/recovery: Read-only file system'. I hope there would be a solution to get my system out of Read-only state
Nektarin87 said:
Hi, I gave a try to that code both on TWRP and Linux terminal (from PC).
Click to expand...
Click to collapse
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
leathan said:
Do you have adb installed and do you see your phone when you type "
Code:
adb devices
"
Usually its as simple as just booting into TWRP -> Factory reset then install the rom and done.
Maybe you do need odin but im pretty sure you can use adb instead like I outlined above, I hated using odin but if you find the right file it should also fix your issue.
What is the codename for your tablet? I cant find it on lineageos's site, what guide did you use its an official lineageos im assuming?
Click to expand...
Click to collapse
Well, I have adb installed, but as my Tablet can only load in recovery it says like these:
adb devices
List of devices attached
4107cd04a2b611b5 recovery
When I load Odin or fastload mode (Download mode as tablet says) I can not list it with 'Fastboot device" command. It says 'waiting for device'.
My tablet is Samsung gt-n8010 (10.1) and I follow this thread to make changes:
LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in...
forum.xda-developers.com
I had Lineage OS 18.1 installed and maybe what caused the issue is that I did not update the TWRP, or we do not have a TWRP ready for it yet, but currently I have TWRP 3.6.1_9-0 installed and stuck with. As I mentioned, on rebooting tablet always starts with TWRP, asking if I want system read only or not with an Unmodified system partition heading. I can not boot OS at all, I can go to Download mode, but Odin always failed indicating my system is read-only.
Ok yes your device is listed as recovery because it has not booted anything. I'm not sure if the commands I gave work without the system actually booting however.
After you entered adb commands there was no error text?
Also if you cant get odin to recognize your phone (RUN IT AS ADMINISTRATOR) you should figure out that first as thats a last resort fix when you really mess things up which I dont think you have yet. I think you must have something off in your configuration if its not reading anything make sure u can access another phone to rule out your pc, but get this working asap.
Usually if your device boot loops you can wipe the cache, and now days remove magisk modules.
If your device still boots straight to recovery It should be as easy as I outlined above, try not isntalling the apps/plugins after the initial rom, and again make sure you wipe cache/data before hand.
If your device boots straight to the bootloader then your left with Odin.
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
leathan said:
Man I hate video guides. But it looks good (unless he forgot to wipe) should have been as simple as that. He does not however provide you with the firmware (not rom) file that I believe you are going to need if you improperly downgraded the android a full version number. Post on his youtube and find that firmware file and fix your odin connection and flash it. If odin is also dead I have no idea but I have never in nearly 20 years had a phone fully brick even when I try to brick them. But I know it can be possible but your most likely going to recover from this.
If he doesn't respond just read more and learn, you may need some specific large file though to flash over what I believe may now be missing partitions entirely.
Maybe someone else here can help too. Good luck!
Click to expand...
Click to collapse
Hi there, I actually find some videos or instructions useful and some helped me out a lot. But as always, things can only be proper if anyone is qualified to do it or when you have the exact same issue on the device. Now back to my case...
I tried many ways, many aspects, but none helped me out. There was this good and working Samsung 10.1 gt-n8010 and one afternoon I found it turned off. When I charged it for a while I turned it on and all it could load is TWRP and I could not do anything. It seems to be working, but I could not see internal storage, while it showed all the 12 GB amount I had, so the issue is not that it shows 0 GB like in many videos. I tried to wipe cache, data, system, even change partition types, all ended with a fail saying my 'system is read only'. I also tried to use Odin and Heimdall to flash new recovery and ROM, also gave a chance to stockRom with android 4.1 or 4.4, but in all cases it said FAILED. To conclude all: I think it could be a hardware issue and as the machine is more the 10 yrs of age, it would not be a surprise, but it's a same it can't be flashed.
If anyone had a similar issue or may have suggestions I'm all ears and the thread remaines, but I am out of ideas at the moment and put my Samsung tab on the shelves.