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?
Related
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 ?????
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Completely Bricked
Me too need a stock rom of ta 1056. Please help if you could manage to provide a helping hand... ?
I had the same issue like yours, looping in twrp. then i tried to flash it with a so called stock rom from net, guess what it went completely bricked and I donnow what to do. ??
mrabudi said:
Hello everyone, after a long attempt at unlocking the bootloader i finally got it, i flashed TWRP and got a prompt for encryption password, and my password wasn't working and i also tried default_password,so i read that the format data option will decrypt the phone and people said wouldn't do anything to system, so i did it and now everytime i reboot it boots straight into recovery no matter what i try, it will also boot into fastboot, so i tried to find a stock ROM for TA-1056 but couldn't find it anywhere, the only the i found was a single ROM for the TA-1060, can anyone help? i really appreciate it!
Click to expand...
Click to collapse
It's simple. just get the stock recovery (and boot, optional) to flash it with fastboot and go to recovery and wipe it and you'll be ok.
and also using the twrp on this phone is not a great idea to wipe.
if you wanna wipe. please use "fastboot -w" to wipe the phone while bootloader is unlocked. or stock recovery to wipe.
Because twrp built this recovery with only formatting option was ext4 to /data and /cache. So the phone cannot operate properly. Which leads to fake failed decryption notification.
Data partition must need to be formatted under f2fs format.
And finding rom for this phone is pretty easy. Just find some nb0 file for this phone (any variant of this phone should work) and extract it with "nb0 extractor" and then flash it with SP Flash tool by mediatek.
That's my way. I don't know how will you do. But normally you only need the nb0 file and then flash it with OST LA (Nokia's flash tool based off Intel's SUT L1/L3 tool).
My Nokia 1 TA-1047 stuck at Nokia logo screen
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
cuantonhonhoi said:
Hi guys, sorry I'm newbie so after a long time surfing for solutions, I couldn't solve my own problem. That's why I come here to ask for your supports
Firstly I unlocked bootloader, installed TWRP and rooted my device and enjoyed it. But after decided to wipe (factory reset) this phone with TWRP, and my problem began...
1. I got stuck in TWRP loop booting. After that I tried to fastboot system.bin, cache.bin and recovery.bin from Stock Firmware but it still hung at Nokia logo booting
2. I still kept trying with SP Flash Tool, Miracle Box but there was still no hope:
- SP Flashtool v5_1548 gave me error: BROM ERROR: S_BROM_CMD_STARTCMD_FAIL (2005)
- Miracle Box 2.27A told me there was an error (i don't remember the code) occured in the location (i can't remember its code either)...
Anyone can solve it please help!!!! I love this phone much and as of now still suffering day by day since I can't do anything with it.
Kindly appreciate any suggestion and solution.
Thank you all!
Click to expand...
Click to collapse
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047. Since it's a universal ROM so any variant of the phone can also work) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to look at line with partition "metadata" and then edit "boundary_check" to false.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
kutiz21 said:
So here's the thing. The rom you downloaded from internet (about 2 GB) or ripped from your phone and reflashing from flash tool will NOT WORK.
The first reason you can't flash the ROM was:
You got into flashing mode but you didn't do the right way so it failed the downloading DA for the phone. Try again and it should work (Don't go into fastboot mode)
2nd reason:
Because of the unsupported chip that MiracleBox read. It said the phone was 6573 or something while the phone chip is 6737M.
So the app will create the wrong version of the scatter for the phone. Leads to the flash tool app downloading the wrong command and Download Agent for the phone makes the phone can't be flashed.
You need to get the official nb0 file for this phone (TA-1060 or 66 should also works, mine was TA-1047) and then extract the ROM. Then you can get the scatter text file from that nb0 ROM and then flash it over flash tool (version 5 recommended, version 3 more likely not work).
Remember to hide/delete line with partition "metadata" in scatter.txt and you can flash it perfectly.
PLUS:
If you flash it with your own dumped EMMC rom or flash it by dd-ing the partition in recovery will kinda work. But when you update the ROM over OTA (Google Play services's System Update app)
It will most likely bootlooped the phone when it's trying to verify the 2nd partition of the same recovery or kernel flashed into the phone (https://source.android.com/security/verifiedboot) and flash the updated one.)
So flashing from official ROM is mandatory.
And you can flash it over Intel's (Nokia modified) flash tool app SUTL3 (aka. OST LA) but I can't get it to work so you just stick with Flash Tool v5 from MediaTek and you'll be good.
Link:
The nb0 ROM (Security update around May 2018): https://drive.google.com/file/d/1XqwEAGG7GMaspzV2J_yzCxnRei8zsOJd/view
(Source: https://romprovider.com/2018/09/nokia-1-ta-1060-firmware/)
nb0 extractor, requires java installed (If extracting hurts your hard disk performance aka. frozen or lag. Don't worry, It actually works, DON'T DO ANYTHING. It will notify you once it's done.): https://forum.xda-developers.com/general/general/tool-unpack-repack-nb0-rom-t3495091
Smart Phone Flash Tool from MediaTek: https://spflashtools.com/
My fixed scatter file that actually works from nb0 file: https://drive.google.com/open?id=1gRoADGHBm4vIAw3NeDyc_h9QWj12XUrC
And don't use twrp for wiping the phone. Use "fastboot -w" to wipe or use stock recovery.
TWRP will wipe the data parition but in ext4 format and make the phone bootlooped. We need f2fs in order to make the phone's /data partition run correctly. (Unless you know how to make the phone not having encryption flag when booting up every first time. Or modify TWRP to wipe the /data partition with make_f2fs and not make_ext4 app. Or using make_f2fs in recovery to directly wipe /data partition over terminal, the actual partition is in /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/userdata.)
Or you just do this (I'm not tested it yet): Google "twrp f2fs format"
Click to expand...
Click to collapse
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
pabloluih said:
Thanks for your comment. I have recently bought that version (TA-1047) and I see that is more complicated to root it securely than I thought… Your comment gave me hope to try it. So, could you please say me if it is posible to do it without breaking it? I will read your comment when I have more time but I thank you for it!
As I see there is only stock rom for TA-1060 version, but as you say it is posible to recover it in case of breaking it, isn't it?
Thanks. :fingers-crossed:
Click to expand...
Click to collapse
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
kutiz21 said:
It's really easy to root the phone actually. Just unlock bootloader, install twrp recovery and install magisk.
And if you broke the phone's ROM. Just bring it to Nokia. Or flash it by yourself with the ROM I linked above by SP Flash Tool software.
Anyway the ROM is universal. So any variant of the phone can be flashed. (Proves that the elabel partition has 5 certifications images for 5 different models)
Just take sometime and read my words there.
Click to expand...
Click to collapse
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
That's weird. If you unlocked the bootloader and install adb/fastboot (must be latest version. Older version will not recognize the phone, download platform-tools from google dev site, don't download adb tools off XDA) + Nokia's driver from emulated CD drive (every time you plug the phone to computer with official rom, you'll see it) properly then it should be able to work.
You need to check the fastboot device driver Device Manager (devmgmt.msc) and see if the driver is properly installed yet.
You can only use "fastboot -w" once the bootloader is unlocked. And booting up the phone. It will say the bootloader is in Orange state.
You need to unlock oem bootloader from developer settings when the stock rom is there. And in fastboot too
Here is how you unlock it:
Enable oem unlock from dev settings
Then reboot to fastboot mode (bootloader)
Do this:
"fastboot oem key "serial number string converted to md5, not imei strings" "
"fastboot oem unlock"
Volume up
Then you are actually unlocked the bootloader.
Unlock from developer settings only will not do the trick. It only allows you to have ability unlock the bootloader in fastboot.
If you stuck on the Encryption unsuccessful screen. Try wipe it with stock recovery or "fastboot -w" (if you properly unlocked the bootloader)
If you think you can't do anything anymore. Just flash the ROM provided you above.
If you need the extracted ROM for SP flash tool and the fastboot driver. I can link it to you.
Most of all drivers will automatically install off Windows Update if you're on Windows 10 (except the fastboot driver, and yes. SP flash tool drivers are also provided by Windows 10 too)
Also. You should update the phone to the latest software update when flashing stock rom too. Because newer builds for this phone is compatible-friendly with GSI rom (Treble ROMs like AOSP Android 9 or 8.1 by phhusson)
Updates on Android 9/10
pabloluih said:
Many thanks! At the moment I achieved to root it with twrp. OEM unlock > installed twrp > fastboot -w > magisk.
At the moment all is okey but I have not been able to unencrypt DATA partition (I have done fastboot -w, but with no success, I have not tried TWRP format because of your advice). That's the only point I can complain about.
I hope I do not have to use the stock rom to unbrick, but I have your advice if I do.
Thanks again!
Click to expand...
Click to collapse
Nokia might harden the security of the device so you can't use Magisk on stock rom.
i downloaded the custom recovery for t20 (TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02) from gethub "i cant attach the link because of the forums rules"
then flashed it using fastboot , but then the tablet didn't boot into normal mode but i was getting the boot mode selection when i hold the (power + volume up) which gave me access to recovery mode and fastboot mode
the problem is that this custom recovery had issues with the touch screen and was basically not usable .
so i switched the phone into fastboot and i flashed the patched boot image that was working before but the tablet still didn't boot into normal mode , then i flashed the stock recovery image and now every thing gone .
the tablet has no options to boot into fastboot or recovery anymore.
basically the tablets boots and i get the teclast logo then the image of the broken android with a "no command" on screen and nothing else
i tried holding the volume up and plug in the usb-c cable but i got the same broken droid
holding volume up and power doesn't give the options for boot modes anymore
i would appreciate any help a this moment , thanks
hany20006 said:
i would appreciate any help a this moment , thanks
Click to expand...
Click to collapse
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
ViAlexSt said:
SP Flash tool should help you. Install stock firmware and everything should be restored, a device on MTK isn't so easy to kill. Just check the revision of your device (E1 or E2, on the back cover). I tried this TWRP and already spoke of that control it only with mouse (https://forum.xda-developers.com/showpost.php?p=78710093&postcount=5). I have my own version of the TWRP (3.2.2), there's also a problem with orientation of the screen. But PhilZ recovery works without problems, the management of keys.
Click to expand...
Click to collapse
thanks for the reply my version is E2
i tried flashing the stock but i keep getting an error that the preloader file is not valid . can u upload yours so i can try with it
hany20006 said:
my version is E2
Click to expand...
Click to collapse
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2: Chinese storage or my Y.Disk
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
ViAlexSt said:
Here's firmware T20 (T2E2)-Android7.1.1_V1.02_8F48 specifically for revision E2:
If stock firmware doesn't help you, here's my read preload-partition, I have E2 (I hope you know how to restore it in SP Flash Tool using Write Memory option).
Partition address and size:
Code:
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0x40000
Click to expand...
Click to collapse
thank you very much for providing the y.disk link , i spent the whole yesterday searching for a way to download from baidu without luck.
i managed to flash the stock software (using format all +download) and it worked and now the tablet is up and running (unfortunately its chines ) i changed the language but there is bits here and there with chines still i cant complain.
there is no recovery image with this tablet , do u think i should flash the twrp recovery even if it has touch issues.
i cant thank u enough for your help
have a nice day
hany20006 said:
do u think i should flash the twrp recovery even if it has touch issues
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
ViAlexSt said:
See here: https://forum.xda-developers.com/showpost.php?p=78758523&postcount=7
Click to expand...
Click to collapse
yeah i just rooted the device and then flashed the recovery using the Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek (TWRP 3.2.1-0)
the touch screen is till having issues , but i guess i have to use mouse as you said
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Draiter said:
Hey guys, have either of you had trouble using the flash tool to flash the patched boot image from Magisk? it will not flash no matter what I do. I just get a red bar .... THanks
Click to expand...
Click to collapse
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
hany20006 said:
Those are the notes i made for my self regarding your issue:
at the end we may get an error when flashing the patched-boot.img using sp flash tool
so we need to use fastboot instead
first we need to install ADB and fastboot in the PC (follow link bellow):
https://www.howtogeek.com/239798/how-to-unlock-your-android-phones-bootloader-the-official-way/
then power off the device then (hold the volume up+ power ) to enter the BOOT mode (the usb must be disconnected)
then select the fastboot from the menu
then we can use the commands :
#fastboot flash boot c:/patched_boot.img --> make sure the image is in the C folder
if this failed we need to unlock the OEM
#fastboot oem unlock -- > then confirm from the tablet
then try again
#fastboot flash boot C:/patched_boot.img
and when its done we can issue the command for restarting tablet
#fastboot reboot
Click to expand...
Click to collapse
Hey thanks for the quick reply, I will give it a go
Sent from my SM-G935F using Tapatalk
Got the boot.img flashed and recovery flashed (Phil's), but cannot do a full backup in recovery, cannot Mount data.
Have you been able to do a full backup?
Sent from my SM-G935F using Tapatalk
Draiter said:
cannot Mount data
Click to expand...
Click to collapse
Standard phenomenon for Nougat/Oreo: to mount a partition /date, must first format it. With loss of user data!
Some TWRP editions don't require this, /data mounted.
Hello.
Thanks ViAlexSt for the help, but I´m still having problems with root
, I try with (MTK) Auto TWRP recovery porter and with MTK Auto Philz recovery porter, with success only with TWRP.
Wiith Philz only get into recovery, when go to the OS the screen freeze with Teclast Logo in red.
With TRWP have an error, not able to mound device.
Is no possible install zip or create a backup.
Any idea??
I have a T20 T2E1
Thanks
I format with SPFlashtool with format+flash option, but not work, no backup, no any wipe.
Still with message Unable to mount parition.
I will try with an older version OF TWRP.
Some screenshots.
Thanks
https://photos.app.goo.gl/qwmLqnhxVk8vRmWA8
https://photos.app.goo.gl/VP5vJCDC7HaDpgaB8
AWLanzarote said:
Still with message Unable to mount parition.
Click to expand...
Click to collapse
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
ViAlexSt said:
Did you manage to do it? It's necessary to format the partition from CWM/TWRP!
Do you need additional explanations?
Click to expand...
Click to collapse
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
AWLanzarote said:
Thank you very much for yor reply.
Yes I try formating with twrp but the same problem, at the end I take the risk and use a downloanble image "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02". The one generated with the porter doesn´t work for my Teclast T20 (T2E1).
With this one "TWRP-3.2.3-TwrpBuilder-t20-2019-01-18_20-02.img works at the first".
And after that I was able to install "Magisk-v18.0.zip" and "no-verity-opt-encrypt-6.0.zip".
And finally I get root access, but after a wile I see the propblem with the IMEI wich was Inavild, after try with many options like generate the file MP0B_001, use Uncletools, droid tools, and many other Apps.
Finally today... I found a solution in a Spanisf Forum Dual Sim, Thanks to user "pedrogem" the most easy way to set an IMEI.
https://play.google.com/store/apps/details?id=com.rungetel.ghostphone&showAllReviews=true
Many Thanks..
Click to expand...
Click to collapse
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
toxstoxs said:
Are you able to make a T20 root step by step guide with all the necessary download's (patched boot.img included) ?
would be very appreciate.
regards
Click to expand...
Click to collapse
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
AWLanzarote said:
Hi toxstoxs.
Is already done in this link with all the downloads https://romprovider.com/2019/01/teclast-t20-root-twrp/.
I follow these steps exept the use of adb. In stead, I used SP Flash Tool, the utility included in the the original ROM which you can download from the official Teclast website.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
With SP flash tools, upload the recovry.img "the downloaded TWRP from the link above" and your boot.img "patched on your device with magisk manager from you original"
I use the boot image from the original rom downloaded from Teclast, which I flash previously.
Be sure to make the backups mentioned in the procedure NVRAM and nandroid, in case you lose your IMEI you will need restore the NVRAM backup.
Just take in mind... touch screeen is not working well in TWRP you should use a mouse, the touch screen is in portrait possition but wou will see the screen in landscape, I do it without a mouse but is not easy, if you can get a mouse will be bether.
Regards.
Click to expand...
Click to collapse
I went troght that step by step guide but :
1) into Pre requirement steps, i made a NVRAM backup with SP Tool.
step 2 is not so interesting to me as the tablet is new so no personal data are saved.
point 3 : How suppose to make a nandroid backup if no TWRP is intalled???
then.. i suppose that it mean to INSTALL a TWRP and just after make a nandroid backup right?
but...
just after ulock the bootloader and reaching step by step the point 7 and 8 of the guide,
after the command "fastboot boot recovery.img" the device reboot and go in permanent loop.
No way to access the recovery.
is there something that i may check? just once i been able to enter the twrp and the main problem were the impossibilty to access and format the /data partition so, no factory reset were possible and obviously no bbot as well (permanent boot loop).
Im not use adb tools, im only use sp fash tool.
I do it like this.
1 flash the downloaded Rom from Teclast with SP flash tool, to get all fresh.
2 Enable usb debug and oem unlock
3 copy in your device the stock boot.img from the folder firmware from the zip downloaded from Teclast,
4 in your device install the app Majisk manager and use it to patch your original boot.img
5 copy into sd the files magisk.zip, No verity opt encrypt.zip,
6 with sp flash tool flash the patched boot.img and the downloaded TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02"]twrp renamed to recovery.img ”this was the only one trwp which works on my T20”https://github.com/TwrpBuilderTests/android_device_teclast_t20/releases/tag/TWRP-3.2.3-TwrpBuilder-2019-01-18_20-02
7 reboot in recovery with TWRP and install magisk.zip and no verity opt encrypt.zip
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Things You must First Do
1. Install Qualcomm drivers for your PC
2. Learn how to remove the device back cover:
3. Learn how to boot the device to EDL mode :
4. Learn how to backup your device full firmware with a box like miracle box or cracked version :
5. Learn how to flash firmware with QFIL tool version 2.0.1.9 :
PROCEDURE 1
1. Get hold of your device full stock firmware. Some build numbers do not have stock firmware especially my Hot S3 build number do not have correct stock firmware.
2. Install latest official magisk manager apk.
3. Copy stock boot.img to your device internal storage.
4. Launch magisk manager app, select install magisk 18.1v or any version that will appear, there will be an options select patch boot.img. Now locate where you stored your boot.img. After patch magisk will show you the location of the patched bootimg.
5. Copy the patched boot.img into the device firmware folder. Remove the original boot.img from the firmware folder and save it somewhere and rename the patched boot.img to boot.img.
6. Now launch the QFIL tool and flash using the previous procedure.
7. After successful flash, boot to the device recovery (Volume up + power button) wipe partition and factory wipe, then power off and reboot.
8. After reboot update Google play store and services sign into your account successfully to have a recognize certify device. Install magisk manager apk. Launch magisk manager app, update and install any other updates that will pop up. Every installed thing in magisk will show green.
9. Reboot. The device successfully rooted.
NOTE:
1. Those who have their correct official firmware and have tested and working correctly, there will be firehose file, patch0 file, rawprogram0 files, NON-HLOS file. These are the necessary files for the flashing.
2. Those who don't have the correct stock firmware use the backup firmware from the miracle and rename these files as;
boot= boot.img
Cache= cache.img
dummy= dummy.img
misc= misc.img
persist= persist.img
recovery= recovery.img
splash= splash.img
system= system.img
userdata= userdata.img
aboot= emmc_appsboot.mbn
Modem=NON-HLOS bin
The rest of the files add .mbn to it end.
You need:
patch0.xml
rawprogram0.xml
prog_emmc_firehose_8937_ddr.mbn
if you don't have these files I will upload my full prepared stock firmware so that you take all the necessary files from it into yours and flash.
But if you have any downloaded stock HOT S 3 firmware with only one system and vendor inside you can use it.
3. Those who have their stock firmware, if the system and vendor in the folder is in multiple form meaning more than one ( system and vendor are in parts) you can't use QFIL tool to flash, it require different flash tool. Use your backup firmware.
4. If any find things difficult I will upload my stock firmware so that all builds can use to create their own stock firmware.
Thank you.
5. After every flash try to remove battery cable and replace for some seconds when the device cover is opened.
6. At a point where the device refuse to boot or power off, long press power button to power off or reboot.
7. Do not be in haste, take your time to follow all these procedures to avoid the device going dead. Because a device does not go dead in my hands. It may brick but when you use good and required flash files everything will be okay.
With ease, convenience and future developments for the device I have created Facebook group for that because some informations are hard to come by. I have posted a lot of help in different forums, nobody seems to help, so this how far I have gone. Now trying to Port custom recovery like twrp for the device even though bootloader is locked.
Procedure 2
1. Follow procedure 1 to backup device
2. Patch boot.img with magisk manager
3. Copy patched image rename as boot.img into backup folder.
4. Flash only the patched boot.img by any supported tool.
5. Reboot device install magisk manager apk reboot and update magisk done.
Those who have already rooted or gone far with the device can join the facebook group or provide me better links. Thanks
Facebook Group Link: https://www.facebook.com/groups/324251668449205/
CREDITS
Thanks to XDA for creating this wonderful platform
The best App ever magisk
The best tool ever Miracle box
Hamenth Jabalpuri my best friend XDA Senior Member
Thanks to everyone.
CAUTION
If any want to use this information in his site, don't forget to credit XDA.
TWRP LINK
https://forum.xda-developers.com/android/development/unofficial-twrp-infinix-hot-s3-x573-t4064705
Skyhuppa said:
Hamenth Jabalpuri my best friend XDA Senior Member
Click to expand...
Click to collapse
Thank you too for sharing this.....
Great tutorial thx
i can't get into edl mode
i used the shorting method via the back cover.. the device was blinking... was detected in device manager but when i clicked on port inside miracle box... nothing happened
i am trying to dump the firmware
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Click to expand...
Click to collapse
aus7een said:
i used the shorting method via the back cover.. the device was blinking... was detected in device manager but when i clicked on port inside miracle box... nothing happened
i am trying to dump the firmware
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Click to expand...
Click to collapse
I'm not getting your device blinking well but;
1. Make sure your device driver 9008 in edl mode installed well. When you open device manager you must see driver 9008 for your device. Download driver
https://www.allmobitools.com/download/Qualcomm_HS_USB_QDLoader_9008_Driver_Download.zip
2. If you are using windows 10 make sure you disable driver signature before installing any driver on your computer
3. Make sure you disconnect and reconnect battery cable on the board before and after every connection.
4. Use the miracle tutorial when you see driver Qloader 9008 in device manager after connecting device.
5. You must connect the two edl points well. Poor connection boot to battery charge.
6. Use miracle 2.82 version
Click to expand...
Click to collapse
did you have TWRP for infinix hot s3?
Nice well done thanks for sharing
agnitoya said:
did you have TWRP for infinix hot s3?
Click to expand...
Click to collapse
Not yet unless bootloader is fully unlocked.
Flash???
which file should i flash it,becouse i dont have the file... and almost all my frimware have .bak at the end so which flasher i should use,QFIL or others? heres the link of the pic of it
Nthn_Knt said:
which file should i flash it,becouse i dont have the file... and almost all my frimware have .bak at the end so which flasher i should use,QFIL or others? heres the link of the pic of it
Click to expand...
Click to collapse
Where did you get the .bak firmware files? Qfil can't flash such firmware. Use mobilsea tool or emmc tool.
Skyhuppa said:
INFINIX HOT S 3 ROOTING PROCEDURE WITH LOCKED BOOTLOADER
Things You must First Do
1. Install Qualcomm drivers for your PC
2. Learn how to remove the device back cover:
3. Learn how to boot the device to EDL mode :
4. Learn how to backup your device full firmware with a box like miracle box or cracked version :
5. Learn how to flash firmware with QFIL tool version 2.0.1.9 :
PROCEDURE 1
1. Get hold of your device full stock firmware. Some build numbers do not have stock firmware especially my Hot S3 build number do not have correct stock firmware.
2. Install latest official magisk manager apk.
3. Copy stock boot.img to your device internal storage.
4. Launch magisk manager app, select install magisk 18.1v or any version that will appear, there will be an options select patch boot.img. Now locate where you stored your boot.img. After patch magisk will show you the location of the patched bootimg.
5. Copy the patched boot.img into the device firmware folder. Remove the original boot.img from the firmware folder and save it somewhere and rename the patched boot.img to boot.img.
6. Now launch the QFIL tool and flash using the previous procedure.
7. After successful flash, boot to the device recovery (Volume up + power button) wipe partition and factory wipe, then power off and reboot.
8. After reboot update Google play store and services sign into your account successfully to have a recognize certify device. Install magisk manager apk. Launch magisk manager app, update and install any other updates that will pop up. Every installed thing in magisk will show green.
9. Reboot. The device successfully rooted.
NOTE:
1. Those who have their correct official firmware and have tested and working correctly, there will be firehose file, patch0 file, rawprogram0 files, NON-HLOS file. These are the necessary files for the flashing.
2. Those who don't have the correct stock firmware use the backup firmware from the miracle and rename these files as;
boot= boot.img
Cache= cache.img
dummy= dummy.img
misc= misc.img
persist= persist.img
recovery= recovery.img
splash= splash.img
system= system.img
userdata= userdata.img
aboot= emmc_appsboot.mbn
Modem=NON-HLOS bin
The rest of the files add .mbn to it end.
You need:
patch0.xml
rawprogram0.xml
prog_emmc_firehose_8937_ddr.mbn
if you don't have these files I will upload my full prepared stock firmware so that you take all the necessary files from it into yours and flash.
But if you have any downloaded stock HOT S 3 firmware with only one system and vendor inside you can use it.
3. Those who have their stock firmware, if the system and vendor in the folder is in multiple form meaning more than one ( system and vendor are in parts) you can't use QFIL tool to flash, it require different flash tool. Use your backup firmware.
4. If any find things difficult I will upload my stock firmware so that all builds can use to create their own stock firmware.
Thank you.
5. After every flash try to remove battery cable and replace for some seconds when the device cover is opened.
6. At a point where the device refuse to boot or power off, long press power button to power off or reboot.
7. Do not be in haste, take your time to follow all these procedures to avoid the device going dead. Because a device does not go dead in my hands. It may brick but when you use good and required flash files everything will be okay.
With ease, convenience and future developments for the device I have created Facebook group for that because some informations are hard to come by. I have posted a lot of help in different forums, nobody seems to help, so this how far I have gone. Now trying to Port custom recovery like twrp for the device even though bootloader is locked.
Procedure 2
1. Follow procedure 1 to backup device
2. Patch boot.img with magisk manager
3. Copy patched image rename as boot.img into backup folder.
4. Flash only the patched boot.img by any supported tool.
5. Reboot device install magisk manager apk reboot and update magisk done.
Those who have already rooted or gone far with the device can join the facebook group or provide me better links. Thanks
Facebook Group Link: https://www.facebook.com/groups/324251668449205/
CREDITS
Thanks to XDA for creating this wonderful platform
The best App ever magisk
The best tool ever Miracle box
Hamenth Jabalpuri my best friend XDA Senior Member
Thanks to everyone.
CAUTION
If any want to use this information in his site, don't forget to credit XDA.
Click to expand...
Click to collapse
TWRP LINK
https://forum.xda-developers.com/android/development/unofficial-twrp-infinix-hot-s3-x573-t4064705
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to