Database Users

[GUIDE] [NS4G] Simple Root/Unroot

This guide is the easiest way to root and unroot your nexus s 4g. If you follow the instructions well you should be fine, included is odin and the files needed if something goes wrong, but it shouldn't as my 11 year old sister could follow them correctly. READ ENTIRE POST BEFORE ASKING QUESTIONS PLEASE.
If your pc doesn't recognize your phone in fastboot make sure your sdk is up to date including thirdparty installs, and download pdanet trial version and those drivers will work. get drivers here http://hotfile.com/dl/92897696/7ae5290/drivers.rar.html
or if your not comfortable installing drivers download pdanet here and install as it will automatically install drivers for you
http://www.junefabrics.com/android/download.php
ROOTING..................
Ok download the files attached and extract them. For the first part for rooting you will need the:
superuser.zip
recovery3101.img
-Ok put the superuser.zip on the sdcard of your phone.
-Power off phone, when off hold volume up and power button to get to bootloader.
-Go the the tools folder of your android sdk and open command prompt and enter the following command: (easiest way is to hold shift and right click on tools folder and hit the button that says "open command window here" then type these command...
fastboot devices (make sure your device shows up, if not your drivers aren't installed)
fastboot oem unlock
-this will unlock the bootloader and you should follow the prompt and accept (volume up, then power button)
-Some have reported unlocking the bootloader erases sdcard..if so when you reboot after unlocking make sure to put superuser.zip back on sdcard.
-this should reboot your phone, now power off, when off hold volume up and then power button to get back to bootloader.
-place the recovery3101.img in the tools folder and type the following command
fastboot flash recovery recovery3101.img
-You should see it say flash ok in the command prompt, now scroll down (on phone) to recovery and hit the power button (ok button)
-Go to flash zip from sdcard and select the superuser.zip and let it flash.
-when done reboot phone, sign into google accnt, download rom manager, open up rom manager go down to All clockworkmod recoverys and flash 3.1.0 (the newest recovery doesn't work for me as my phone can't get into recovery that is why we are flashing the other one )
-All set you can flash other roms, MAKE SURE TO CREATE BACKUP OF YOUR CURRENT STOCK ROOTED ROM FIRST.
UNROOTING.........
Get files http://www.4shared.com/file/N5g8Hav_/root.html?]
-download and extract files, we will be using odin, the 3 tar files.
-extract tar files to desktop along with odin.
-run odin and in the files section select the boxes bootloader, pda, phone.
-click the buttons next to each and direct it to the .tar files we extracted to desktop, so....
click the bootloader box, direct it to sph-d720-bootloader.tar ...then..
click the pda button direct it toward the sph-d720-pda.tar....then..
click the phone button and direct it toward sph-d720-phone.tar....
-now turn off your phone, when off hold volume up and volume down buttons simultaneously, then quickly press the power button....a huge yellow triangle will pop up and say "downloading'.......
plug your phone via usb to computer....odin should automatically see it.....click the start button in odin and let it do its thing and bam...all set.
If you want stock recovery too place the recovery.img in tools folder, open command prompt..type the following command..
fastboot flash recovery recovery.img
Done.

Ill give this a try when I get home....but I'm sure you need to make sure you have all the correct drivers installed...or when you run the fast boo command it won't recognize your phone is connected.

Subbed for when I have time.
Since the NS4G doesn't have a SD Card where do you put the superuser zip?

This will work for the 3g version, correct?
Sent from my Nexus S using Tapatalk

yes it should work for 3g

where the files to download?dont see the links

dodgeram02 said:
where the files to download?dont see the links
Click to expand...
Click to collapse
Links are right under the post, i'll post the unroot guide tonight as i am at work and cannot do it.

need some help..when i hook my phone to my computer which has windows vista 32..i get a found new hardware that pops up SM BUS CONTROLLER..why is that..but if i go into my DEVICE MANAGER under OTHER DEVICES it has a question mark next to SM BUS CONTROLLER...and at the top of the list i do have ANDROID PHONE.when i expand that there is ANDROID COMPOSITE ADB INTERFACE...this crap is driving me crazy tried everything....HELP.....

I have rooted a EVO IPHONE AND ETC..but for some reason I just cant get this thing to root or to comunnicate to my computer.

MAKE SURE PDANET IS INSTALLED http://api.viglink.com/api/click?fo...ers&txt=http://www.fileserve.com/file/5bgRBX5
OR HERE http://hotfile.com/dl/92897696/7ae5290/drivers.rar.html

dodgeram02 said:
need some help..when i hook my phone to my computer which has windows vista 32..i get a found new hardware that pops up SM BUS CONTROLLER..why is that..but if i go into my DEVICE MANAGER under OTHER DEVICES it has a question mark next to SM BUS CONTROLLER...and at the top of the list i do have ANDROID PHONE.when i expand that there is ANDROID COMPOSITE ADB INTERFACE...this crap is driving me crazy tried everything....HELP.....
Click to expand...
Click to collapse
install pda net before doing this root process..

ok i got it figured out but when i do the RECOVERY STEP I GET A "!"IN A TRIANGLE.

-place the recovery.img in the tools folder and type the following command
fastboot flash recovery recovery.img
-You should see it say flash ok in the command prompt, now scroll down (on phone) to recovery and hit the power button (ok button)
this part isnt workin for me.........

dodgeram02 said:
ok i got it figured out but when i do the RECOVERY STEP I GET A "!"IN A TRIANGLE.
Click to expand...
Click to collapse
redownload the files....
Just in case i reuploaded the recover.img and named it recovery3101.img
place in tools folder and type
fastboot flash recovery recovery3101.img
and should flash just fine...

DUDE YOUR THE MAN!!!!!!GOT R DONE...you been very helpful....out of trying all the other damn ROOTING GUIDES yours was the FASTEST AND THE EASIEST......Thanks bud!!!!

dodgeram02 said:
DUDE YOUR THE MAN!!!!!!GOT R DONE...you been very helpful....out of trying all the other damn ROOTING GUIDES yours was the FASTEST AND THE EASIEST......Thanks bud!!!!
Click to expand...
Click to collapse
No problem.

I can't seem to get this to work. I have Win7 64 and I used PDAnet to install the drivers but when I get to the part where I have to type "fastboot oem unlock" the command prompt just says < waiting for device > and there is nothing on the Nexus S 4g other than the normal fastboot options for me to select.

DarkManX4lf said:
I can't seem to get this to work. I have Win7 64 and I used PDAnet to install the drivers but when I get to the part where I have to type "fastboot oem unlock" the command prompt just says < waiting for device > and there is nothing on the Nexus S 4g other than the normal fastboot options for me to select.
Click to expand...
Click to collapse
Make sure you installed the right drivers....reboot computer, make sure you opened the command prompt in the tools folder as that is where the fastboot commands are located....also it will automatically reboot in the "unlock bootloader menu" you don't select anything...until that menu comes up..make sure your sdk is updated as well..even third party installs..

I want to thank you, these are great instructions so far. I have been trying for days, got my phone unlocked by a mistake, had to Odin back (came from Epic so know and love that system), but it stayed unlocked.
I cannot get it rooted. Used your instructions and get to second part - cannot install fasboot recovery.
My files are in tools listed as recovery-clockwork-3.1.0.1-crespo4g. I ran fastboot, came up with a large square of instructions, not ok, with command and option. So I tried again. nothing
Then went to phone with it connected, tried to select from card the su file. It goes to yellow triangle and finally get back to a reboot.
I am so close, can you help with what I am doing wrong? It is not rooted and cannot get it to do anything.

nmoreman said:
I want to thank you, these are great instructions so far. I have been trying for days, got my phone unlocked by a mistake, had to Odin back (came from Epic so know and love that system), but it stayed unlocked.
I cannot get it rooted. Used your instructions and get to second part - cannot install fasboot recovery.
My files are in tools listed as recovery-clockwork-3.1.0.1-crespo4g. I ran fastboot, came up with a large square of instructions, not ok, with command and option. So I tried again. nothing
Then went to phone with it connected, tried to select from card the su file. It goes to yellow triangle and finally get back to a reboot.
I am so close, can you help with what I am doing wrong? It is not rooted and cannot get it to do anything.
Click to expand...
Click to collapse
MAKE SURE IT IS UNLOCK BY TYPING
FASTBOOT OEM UNLOCK
JUST TO BE SURE ITS UNLOCKED.
to open the command prompt for fastboot when you see the tools folder in android sdk folder hold shift, right click on tools folder and choose option "open comand prompt here"
first use the recovery3101.img i provided. Flash that by typing
fastboot flash recovery recovery3101.img
command prompt will say flash ok...look at your phone..scroll down to recovery option and hit the power button..should load you into clockwork recovery....let me know if you get that far..

Downgrade Orea beta to Nougat

Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.

are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help

Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse

I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.

swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.

tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied

swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm

tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.

Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.

trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.

And now what i do with my Axon 7?

Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...

Let me link you my ingenious, allmighty Axon 7 Companion Thread.

Try to install twrp with MiFlash if you can enter edl mode

macerf said:
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Click to expand...
Click to collapse
Your phone works normally
You don't have fastboot
You have stock recovery
If this is the case then most surely you have EDL working...
Install TWRP from EDL mode:
This is taken from Controllerboy's guide
BE SURE THAT WINDOWS SHOWS FILE NAME EXTENSIONS!
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.

Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.

macerf said:
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
Click to expand...
Click to collapse
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again

Choose an username... said:
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Click to expand...
Click to collapse
Hello and thanks for the advice. Unfortunately it does not change anything.. I have done exactly as you say but the result does not change anything...io have connected the device, Open command window, type "adb devices ", is viewed as "Cd07b2e9 device ", I type "adb reboot EDL ", it restarts in EDL, then go to management Devices and is viewed as "QUSB_BULK ", Run command "Axon7tool-r GPT boot recovery " but it says "Failed to connect ", then I'll return to Device Manager, hold volume up & Down & Power, Icon disappears and returns after a few seconds, close window and launch command "Axon7tool-r GPT boot recovery " but still give "failed to connect "...
So, recapping: I have bootloader unlocked, I can get into EDL but PC does not see device although on Device Manager it exists...
I now launch device into the wall... problem solved.

if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.

kitcostantino said:
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
Click to expand...
Click to collapse
Of course I'm kidding... have just purchased this device, have a great hardware but the software does not go well for nothing. I have had a dozen phones, I changed about 60 ROMs, so for me it is not difficult to change the software...ma in this case have problems. Is it possible that I fail to solve this problem? Be a way to reset everything and start from scratch? Okay, the bootloader be unlocked but not be any other way to go back? I have seen many guides but not able to solve the problem. I fail to make flash of TWRP, fail to do downgrade to MM....io hope someone help me... thanks.

are you using a USB 2.0 or 3.0 port? it may not apply to this scenario, but with Motorola and RSD Lite, I always had to use usb 2.0 ports or it wouldnt see my device when flashing.
also, the steps @choose an username listed out are the best way to start from scratch, but obviously you have to be able to have your computer see the phone in the desired mode.
@DrakenFX has several guides in the axon 7 forums that should help once the computer sees the phone as well.

I use USB 3.0 with original cable ... but if you now tell me that maybe this is my problem, then I use USB 2.0. Thank you...

Good morning...
Nothing to do... I put the original cable on USB Port 2.0, have redone procedure from window PowerShell, on command "adb devices " Everything OK, on command "adb reboot EDL " It enters EDL mode, but then all the procedures are failed... if command "Axon7tool-R recovery GPT boot "I always get out of the inscription " Failed to connect ", it remains in EDL and I just have to reboot... I replaced the drivers with Zadig 2.3 but did not change anything... are there any other moors to make flash of TWRP? exist lthough an app that do this? I remember that for LG G3 I'll fix everything with an app...

Tutorial to Flash Lineage on Oneplus8t with magisk. Works with devices with originally locked bootloader (tmobile locked models)

READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down) Recommended to use Command Prompt commands instead of powershell (type cmd in platform-tools directory) https://developer.android.com/studio/releases/platform-tools
Unlock oem bootloader
Enable developer options (click build number several times)(make sure you’re connected to internet)
Enable oem unlocking, advanced reboot, usb debugging
Reboot to bootloader/fastboot
fastboot oem unlock
Unlock bootloader
Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding volume down while
booting)
Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
fastboot flash boot (path to boot.img)
fastboot flash dtbo (path to dtbo.img)
fastboot flash recovery (path to recovery.img)
Download firmware (https://kremowka.xyz/files/8fw/)
Enter recovery mode, enter fastbootd
Advanced > enter fastboot
Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload
LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in
there somewhere
Open notepad, copy commands from lineage, save as (file name).bat, drag into powershell from file explorer
(flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
adb devices (to confirm phone is connected properly and device drivers are configured properly)
adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are
too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
Reboot recovery?
adb sideload (path to copy partitions .zip)
Back > Reboot system now
It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have
data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done
that before this step (do it in fastboot, search up adb shell pull)
If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something
happened.
OPTIONAL (if you want magisk/root)
Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
Search in settings for “advanced”, click “advanced restart” and enable
Hold power button, restart, recovery
Apply update > apply from adb
adb devices
adb sideload (path to magisk .apk)
Signature verification failed, install anyway
Volume up to go to back arrow, reboot system now
Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file
transfer is on
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
What I use: Safetynet universal fix and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
Install from storage
Order I did it in was safetynet then raven, rebooting between each one but I'm not sure if it matters
Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click
google play services, google play store, and carrier services (the square check box next to the name, make sure
every check below when you open it as a dropdown menu is checked
Reboot phone
Now you can download whatever you want
If you install twrp, make sure you are using android 12 version and not android 11, android 11 twrp will destroy
your recovery if you try to use it on android 12.
Add on: If your phone is not detected by your pc, or is detected as “MTP” with an exclamation mark, you do not
have the right drivers. There are plenty of resources online to fix this, but one that I had trouble with was that I
was on windows 10 N instead of whatever the other version is, which doesn’t come with “mediafeaturepack.”
You need to install that on your own from https://www.microsoft.com/en-us/software
download/mediafeaturepack, or, if your device isn’t listed, go to windows application “optional features” and
add it from there.
If your computer won’t download qdloader 9008 qualcomm drivers through device manager, there are a few
things i’ve tried to fix it. Make sure you have correct drivers
from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008
“The system cannot find the file specified”
Open command prompt as administrator
Type DISM /Online /Add-Package /PackagePath:"Full path of .cab file"
I put mine in C: drive folder but I'm not sure it matters
Also I'm not sure which one of the three I downloaded from the website. Did not cause any issue downloading
and trying to install all three, let me know if you figure out which one works. Maybe you need all three, I don’t
know.
If that doesn’t work, do sfc /scannow
Open windows update, make sure all updates are applied and restart windows (make sure you go to optional
updates and select qualcomm drivers)
Fastboot won’t connect
Make sure you’re using a usb 2.0 port instead of a usb 3.0 port, and make sure your usb cable is a data cable.
Google the difference if you don’t know what it is. Download usb drivers
from https://developer.android.com/studio/run/win-usb, open device manager, see if anything is there, if it
shows something in “other devices” click on it, click update drivers, browse my computer, let me pick, have disk,
and then browse to android_winusb.inf and click update, click bootloader interface. If you get “error 10 device
won’t start” when installing bootloader interface, one possible solution is to disable driver signing.
Open command prompt as an administrator (doesn’t have to be in platform tools directory)
bcedit /set testsigning on
Reboot, try to install driver again.
If your device is bootlooping, and you enter fastboot after updating to a12 firmware AND you have magisk\
modules downloaded AND you have twrp installed, do not press the up volume button, only cycle through
options with volume down, because it may enter an option cycle and you won’t be able to do anything unless
you fastboot flash boot twrp.img.
It’s recommended that as soon as you root, you backup persist.img, which contains imei info (you don’t want
that to get destroyed) I am unsure if there’s anything else device specific you need to backup, I've heard
vendor_image may be but it’d not as important as persist.
To backup persist.img, put phone in recovery, type in command prompt or powershell
adb shell dd if=/dev/block/bootdevice/by-name/persist of=/tmp/persist.img
adb pull /tmp/persist.img persist.img
This should save persist.img to your computer. Back it up somewhere you keep important things. Also don’t
give it out at random as it contains your imei number, not sure what the consequences of that could be but
nothing good is likely to come of it.
Important shortcuts:
Power + vol up – boot into system
Power + vol down – boot into fastboot
Power + vol up + vol down – boot into edl
IF DEVICE IS BOOTLOOPING AND YOU CAN’T ENTER ANY DIFFERENT MODES, CONTINUE HOLDING POWER +
VOL DOWN IN RANDOM PATTERNS. IT HAS TAKEN ME 20 MINUTES OF RANDOM BUTTON COMBINATIONS TO
GET INTO FASTBOOT FROM A BOOTLOOP. YOU WILL ALWAYS BE ABLE TO EXIT A BOOTLOOP IF YOUR PHONE
IS PHYSICALLY UNDAMAGED.
If VoWifi doesn’t work, pixelify dialer can get it working. Probably also just any custom dialer, but I like Google
dialer. Wait for the interface to change slightly, don’t clear data until you’ve waited at least a minute or two and
closed and reopened it a few times, but if it doesn’t change after installing pixelify then force close, clear data,
and wait a minute or two, reopen, and then wait. If it continuously doesn’t change you can reflash pixelify.
Note – If using pixelify module, disable auto update for android system intelligence, it will break gboard
translate and possibly slow down device.
You can also use magisk module “mindetach” to detach com.google.android.as from play store, which will fix
any auto update bugs. Credit to vewu for showing me that
https://github.com/j-hc/mindetach-magisk
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community.
Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for formatting, this is copied from a word doc. Please feel free to indent and number list yourself and
send me a better version

Does the third option work?

INTseed said:
Does the third option work?
Click to expand...
Click to collapse
did you configure the denylist? try clearing cache and data for google play services, google play store, and carrier services and rebooting

Mrmcfeffers said:
READ THIS WHOLE THING BEFORE STARTING. THERE ARE SEVERAL WARNINGS.
Flash eu firmware using msmtool mod (https://www.xda-developers.com/t-mobile-oneplus-8t-rebrand-without-bootloader-unlocking/) (if msmtool doesn’t work make sure windows is in test mode with proper qualcomm drivers) (if your device bootloops and you can’t recover it just flash it again with msmtool, power it off and power it back on holding both volume up and down)
a. Unlock oem bootloader
i. Enable developer options (click build number several times)(make sure you’re connected to internet)
ii. Enable oem unlocking, advanced reboot, usb debugging
iii. Reboot to bootloader/fastboot
iv. .\fastboot oem unlock
v. Unlock bootloader
b. Boot back into oos, (repeat steps I. ii. And iii.) or (boot directly into fastboot by holding
volume down while booting)
2. Flash boot, dtbo, and recovery (https://mirror.math.princeton.edu/pub/lineageos/full/kebab/20220818/)
a. .\fastboot flash boot (path to boot.img)
b. .\fastboot flash dtbo (path to dtbo.img)
c. .\fastboot flash recovery (path to recovery.img)
3. Download firmware (https://kremowka.xyz/files/8fw/)
4. Enter recovery mode, enter fastbootd
a. Advanced > enter fastboot
5. Follow https://wiki.lineageos.org/devices/kebab/fw_update to flash it, and without rebooting sideload LineageOS 19.1, sideload mindthegapps, then reboot. https://wiki.lineageos.org/devices/kebab/install fits in there somewhere
a. Open notepad, copy commands from lineage, add .\ before each line, save as (file name).bat, drag into powershell from file explorer (flash ram separately for safety) I named mine “flashfirmwareforoneplus8t.bat”
b. Be careful with ddr4 vs 5. do not brick your phone. Ddr4x is ddr4 for these purposes.
c. Without rebooting, enter recovery > apply update > apply from adb (it should say version 18.1 in the top left)
i. .\adb devices (to confirm phone is connected properly and device drivers are configured properly)
ii. .\adb sideload (path to lineage 19.1 .zip)
Sideload will likely get stuck at 47%. This is normal. Just wait.
d. Volume up to go to back arrow, advanced, reboot to recovery (make sure it says version 19.1 now)
i. .\adb sideload (path to mindthegapps .zip) note that most gapps packages will not install properly as they are too large. Just download them all from google play store once booted.
Signature verification failed will pop up, just confirm “yes”
e. Reboot recovery?
i. .\adb sideload (path to copy partitions .zip)
6. Back > Reboot system now
a. It may say “can’t load android system your data may be corrupt” just factory data reset it’s fine unless you have data you want to keep then you’ll have to google it, I don’t know how to recover that and you should’ve done that before this step (do it in fastboot, search up adb shell pull)
7. If the start page has clouds and blue then good job you loaded gapps properly. If it’s not then something happened.
8. OPTIONAL (if you want magisk/root)
9. Go into settings, enable developer options (tap build number repeatedly) make sure usb debugging is on
a. Search in settings for “advanced”, click “advanced restart” and enable
b. Hold power button, restart, recovery
10. Apply update > apply from adb
a. .\adb devices
b. .\adb sideload (path to magisk .apk)
i. Signature verification failed, install anyway
ii. Volume up to go to back arrow, reboot system now
11. Boot into device, reboot, magisk should appear, click on it and click accept on whatever it prompts
a. Open magisk, do whatever it prompts. To install a file, drag whatever module .zip you want in, make sure file transfer is on
12. DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
a. What I use: Safetynet universal fix, disableflagsecure (lets you screenshot netflix lol), and raven.A12L (spoofs as pixel 6 pro to let safetynet work)
i. Install from storage
ii. Order I did it in was safetynet, then raven, then flag secure rebooting between each one but I'm not sure if it matters
b. Install safetynetfix, then go into settings, click zygisk, click enforce denylist, click 3 dots, show system apps, click google play services, google play store, and carrier services (the square check box next to the name, make sure every check below when you open it as a dropdown menu is checked
c. Reboot phone
13. Now you can download whatever you want
https://github.com/Pixel-Props/raven/releases
https://github.com/kdrag0n/safetynet-fix
https://forum.xda-developers.com/t/disable-flag-secure-magisk-module-v3-0-by-mehedi-hjoy.4490475/
Dm me on here if you have any questions. I am not a dev, I learned these steps from others in the community. Shoutout pizzalovingnerd, Luk1337, raven, poang, and nvcore for helping me out a lot.
Apologies for the ****ty formatting, i copied this from a word document. I don't know how to paste the indents.
Click to expand...
Click to collapse
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.

optimumpro said:
How can you claim this 'works on locked bootloader', when right at your ( 2) you say 'unlock bootloader'. And if your instructions require unlocked bootloader (which they surely do), then they are useless, because once your bootloader is unlocked, you can simply flash Magisk with recovery.
Click to expand...
Click to collapse
modded msm tool allows bootloader unlocking

Mrmcfeffers said:
modded msm tool allows bootloader unlocking
Click to expand...
Click to collapse
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.

optimumpro said:
What does this have to do with your 'working on locked bootloader'? That statement is false. You can't flash anything on locked bootloader, and if you unlock bootloader, then you can simply flash Magisk via recovery without the need for your 'method'.
Click to expand...
Click to collapse
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.

Mrmcfeffers said:
seems to have worked for me. i meant "working on locked bootloader" as in it include steps to unlock. it's also a guide to installing lineage, not just magisk. i'm not sure what issue you have here, it's a specific tutorial for a specific problem.
Click to expand...
Click to collapse
It's just a decription in thread name that is a bit misleading.
At first it appears like it can be done on locked bootloader.
And it's obviously not, as stated in your instruction point #2.
Otherwise, nice tutorial.

Mrmcfeffers said:
DO NOT USE ACC OR ACCA (battery manager) FROM F-DROID IT SOFT BRICKED MY PHONE
Click to expand...
Click to collapse
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?

jinncarry said:
So is acc incompatible with this device? Or is this a warning only at that step in the tutorial?
Click to expand...
Click to collapse
Don't use acca from f-droid. Acc from the official GitHub (https://github.com/VR-25/acc) is fine and works perfectly

Lenovo M10 Plus 3rd Gen Root Guide (TB125FU)

Notice! This process also completely resets your tablet! Backup all files and information.
This is just me documenting my process for rooting my tablet. I am not responsible for any damage or lost information due to the process changing, errors in execution, or mistakes in my documentation. Let me know of any errors, corrections, or updates that may need made.
Thank you to contributors to the thread linked below for the information provided that allowed me to create this more detailed root guide.
Custom Rom / rooting Options vor TB-125FU (Lenovo Tab M10 Plus 3rd Gen)
Hey everyone, I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU...
forum.xda-developers.com
This process was completed on Model: TB125FU
Follow documentation at your own risk!
First I updated my tablet until it was the newest system update available. For me that was version "TB125FU_S000118_220927_ROW"
Step 1 - Install tablet drivers on your computer
Download drivers folder and unzip
https://forum.xda-developers.com/attachments/android_adb_interface-zip.5741369/
Plug tablet into computer
Open Device Manager
You’ll see a line item labeled “ANDROID” with a yellow exclamation mark
Right click on it and select update drivers
Select Browse Computer and navigate to the unzipped driver folder
Make sure the Include Subfolders box is checked and select Next
This will install the drivers for the tablet
Step 2 - Unlock your tablet for usb debugging
Open settings on your tablet
Search for “build”
Click “Build Number”
Click the Build Number box seven times to unlock developer options
Close and reopen the settings app
Under System there is now a Developer options, open it
Toggle the selections for OEM Unlocking and USB debugging
Step 3 - Obtain boot.img
Download and install Lenovo LSMA
https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
plug your tablet into the computer
run program, select rescue
check the allow USB debugging popup on your tablet
select tablet in the LSMA program and select the allow popups on your tablet
select Download when it shows the firmware for your tablet
DO NOT CLICK START RESCUE
close the program when it finishes downloading the ROM
The ROM will download to C:\ProgramData\RSA\Download\RomFiles
Make sure ROM folder name matches the current system update version on your tablet
Copy from the downloaded ROM folder “boot.img” to your tablet
Step 4 - Modify boot.img
Download Magisk apk from the official Github page
https://github.com/topjohnwu/Magisk/releases
install APK on your tablet
open Magisk
Select Install
Select “Select and Patch a File”
Navigate to the location you copied the boot.img file and select the file
Select “Let’s Go”
Wait for flashing lot to say “All done” indicating it modified the boot.img file
Transer modified file to your computer, for me it was called “magisk_patched-25200_rgIWh.img” I then renamed it “magisk_patched.img” to make future typing commands shorter
Step 5 - Unlock bootloader and flash modified boot.img
Download Minimal ADB and Fastboot Tools
I chose to download the portable version
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
unzip folder
Place the modified .img file in this folder as well
Navigate to this folder, right click and launch a Command Prompt
Plug in your tablet to your computer if it isn’t already
Type “adb devices” to confirm your computer sees your tablet
Type “adb reboot bootloader” this should reboot your tablet into fastboot
Type “fastboot devices” to confirm the computer sees your tablet
Type “fastboot flashing unlock” read the instructions on screen which will tell you to press the volume up button (volume button closest to power button) to unlock bootloader.
Press the volume up button, It will say it was successful, wait a few seconds for the tablet to return to fastboot
Type “fastboot flash boot magisk_patched.img” and when you hit enter you should see a transferring status on your tablet (if you named your modified .img file something else, type that into the command instead)
When you see the transfer is complete type “fastboot reboot” which will restart the tablet.
The tablet should now be rooted which will completely reset the tablet. You will need to setup the tablet again and reinstall the Magisk app from the official Github. The Magisk App should now have superuser controls
You can relock the bootloader and return the tablet to factory image. IT WILL WIPE ALL DATA AGAIN!
To unroot you just reverse a couple steps.
Put the original boot.img (Make sure it is the boot.img of the same version ROM) in the Minimal ADB and Fastboot Tools folder on your computer
Navigate to this folder, right click, and launch a Command Prompt
Plug in the tablet to your computer
Type “adb reboot bootloader” this should reboot your tablet into fastboot
When the tablet reboots into fastboot type “fastboot flash boot boot.img”
When you see the transfer is complete type “fastboot flashing lock” read the instructions on screen which will tell you to press the volume up button (volume button closest to power button) to lock bootloader. Press the volume up button.
Type “fastboot reboot” which will restart the tablet
You tablet should now be back to normal.
***Note, if you relock the bootloader first it will not let you flash the original boot.img file. If you make that mistake as I did once you'll be able to manually startup recovery mode by first powering off the tablet by holding down the power button, then boot into recovery by holding the power button and the volume up button until the recovery screen appears. Then you can unlock the bootloader again.

Hello,
Please can you confirm that the model you tested is the same as
Lenovo Android TB125​ZAAJ0198SE​
The one above is a mediatek helio G80 4GB+64GB 2000*1200 resolution with Android 12 (bought some days ago, for sure it is M10 Plus 3rd Gen).
Thanks in advance.

Mine is: ZAAJ0401US
The process detailed above should still work on yours. Remember, you will be downloading the boot.img that Lenovo is recommending for your tablet, not using one I uploaded. So you will be rooting your specific file.
I doubt there would be differences between our ROM anyway but even if there were, it wouldn't effect you be because you are creating your own rooted .img.

Thanks for this guide. What system app did you uninstall after rooting?

I didn't remove any system apps when I rooted. I'm sure some are extra and can be removed safely.

Sorry, what is the reason for rooting then, when there are no custom roms yet?

Some apps require root access.

fastboot flash boot magisk_patched-25200_ofAPj.img
Sending 'boot_a' (98304 KB) OKAY [ 2.660s]
Writing 'boot_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Now what? The bootloader is already unlocked.
EDIT: I had to use the volume keys to select "recovery mode" which opens a menu. From there I have to select "fastboot" (not "bootloader") which displays "fastbootd" (note the "d" on the end), then fastboot commands work.
BUT, after flashing the boot.img, it just powers off after the logo, no option to enter any kind of recovery, no USB connection. At most, if I hold Power for 15 seconds, then release and hold again, sometimes it turns on, and then if I hold VolUp, it boots to a recovery menu, but the only options are "try again" and "factory data reset". if I reset, it shows the animation for half a second, then shuts down.
On this menu it appears in "adb devices" as "unauthorized".
UPDATE: I was able to use Lenovo's "Recovery and Smart Assistant" tool to repair, but it has to be run on a Windows machine (will not connect in VirtualBox). It doesn't recognize the serial number, but by selecting "help finding serial" there's an option for manual entry of model number.
Choosing TB128FU and following the directions I was able to flash the stock firmware, but, the tool downloaded the wrong version. After flashing, the device claims the firmware isn't compatible with the hardware, and shuts down.
To fix this, I've had to find "TB128FU_CN_OPEN_USER_Q00012.0_S_ZUI_13.5.365_ST_220526_qpst" online. The tool downloads to C:\ProgramData\RSA\Downloads\RomFiles. You need to replace the contents of the folder in there (back it up!) with the contents of this, then it will flash a working firmware. (I think you can also use this to flash the patched boot.img, but I haven't tried). The only catch is, this is the Chinese ZIUI firmware, not the Global firmware it came with. It can be used in English, so I might keep it if I can't find the correct Global firmware.
https://wiki.postmarketos.org/wiki/Lenovo_Tab_M10_FHD_Plus_(lenovo_tbx606) PostMarketOS Wiki mentions that another file needs to be flashed any time you enter fastboot to prevent this brick. The article is for a different model, but probably the same applies.

I'm not sure why you got that error if the bootloader was unlocked. My patched .img file only failed like that when I failed to unlock the bootloader first.
Did you toggle the "OEM unlocking" in developer options on the tablet before trying to unlock the bootloader with command prompt commands?
When the bootloader is unlocked the tablet gives a warning message for a few seconds on every boot telling you that the bootloader is unlocked.

The "OEM unlocking" was grayed out saying the bootloader is already unlocked, and it does show the message at startup.
The problem might be that this is model TB128FU (not TB125FU) which is only sold in China, so it doesn't accept the same firmware. I don't know how the seller put the global firmware on it originally.

ok, i think i understand. Your tablet model number is different.
When going through the rooting process it downloaded the wrong version for your tablet without you realizing it so you patched and attempted to install the wrong version of ROM boot.img.
If so it means it is extra important to follow the line in step 3, "Make sure ROM folder name matches the current system update version on your tablet"
It is weird though that the Lenovo Rescue Tool didn't download the correct software for your tablet.

Does anybody know how to unlock bootloader for TB128XU? It is the same tablet but with Snapdragon SOC.
I am failing on unlock command. Both of these won't work :-(
fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse

So everything worked great for me.
As a launcher I now use the Microsoft Launcher.
Nice interface and features.
The OTAs with Magisk Root also work great.
As described by the developer.
Section Devices with A/B Partitions
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io

Thanks for this! I haven't rooted an Android device since Gingerbread (2.3) in 2010, so it was good to have a basic guide for the newer stuff.
One thing I noticed: Step 1 says to find the "Android" device in Device Manager and manually install the drivers. However, that device didn't appear in Device Manager for me until I booted into fastboot mode. So effectively I had to move step 1 to instead be later, immediately after this sentence:
Type “adb reboot bootloader” this should reboot your tablet into fastboot
Click to expand...
Click to collapse

zippy411 said:
Notice! This process also completely resets your tablet! Backup all files and information.
This is just me documenting my process for rooting my tablet. I am not responsible for any damage or lost information due to the process changing, errors in execution, or mistakes in my documentation. Let me know of any errors, corrections, or updates that may need made.
Thank you to contributors to the thread linked below for the information provided that allowed me to create this more detailed root guide.
Custom Rom / rooting Options vor TB-125FU (Lenovo Tab M10 Plus 3rd Gen)
Hey everyone, I've been looking for options to Install a custom Rom or root since I bought the Tablet several month ago. It seems like there are some options for the Full Hd Version, but I have a hard time finding anything useful for the 125FU...
forum.xda-developers.com
This process was completed on Model: TB125FU
Follow documentation at your own risk!
First I updated my tablet until it was the newest system update available. For me that was version "TB125FU_S000118_220927_ROW"
Step 1 - Install tablet drivers on your computer
Download drivers folder and unzip
https://forum.xda-developers.com/attachments/android_adb_interface-zip.5741369/
Plug tablet into computer
Open Device Manager
You’ll see a line item labeled “ANDROID” with a yellow exclamation mark
Right click on it and select update drivers
Select Browse Computer and navigate to the unzipped driver folder
Make sure the Include Subfolders box is checked and select Next
This will install the drivers for the tablet
Step 2 - Unlock your tablet for usb debugging
Open settings on your tablet
Search for “build”
Click “Build Number”
Click the Build Number box seven times to unlock developer options
Close and reopen the settings app
Under System there is now a Developer options, open it
Toggle the selections for OEM Unlocking and USB debugging
Step 3 - Obtain boot.img
Download and install Lenovo LSMA
https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa
plug your tablet into the computer
run program, select rescue
check the allow USB debugging popup on your tablet
select tablet in the LSMA program and select the allow popups on your tablet
select Download when it shows the firmware for your tablet
DO NOT CLICK START RESCUE
close the program when it finishes downloading the ROM
The ROM will download to C:\ProgramData\RSA\Download\RomFiles
Make sure ROM folder name matches the current system update version on your tablet
Copy from the downloaded ROM folder “boot.img” to your tablet
Step 4 - Modify boot.img
Download Magisk apk from the official Github page
https://github.com/topjohnwu/Magisk/releases
install APK on your tablet
open Magisk
Select Install
Select “Select and Patch a File”
Navigate to the location you copied the boot.img file and select the file
Select “Let’s Go”
Wait for flashing lot to say “All done” indicating it modified the boot.img file
Transer modified file to your computer, for me it was called “magisk_patched-25200_rgIWh.img” I then renamed it “magisk_patched.img” to make future typing commands shorter
Step 5 - Unlock bootloader and flash modified boot.img
Download Minimal ADB and Fastboot Tools
I chose to download the portable version
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
unzip folder
Place the modified .img file in this folder as well
Navigate to this folder, right click and launch a Command Prompt
Plug in your tablet to your computer if it isn’t already
Type “adb devices” to confirm your computer sees your tablet
Type “adb reboot bootloader” this should reboot your tablet into fastboot
Type “fastboot devices” to confirm the computer sees your tablet
Type “fastboot flashing unlock” read the instructions on screen which will tell you to press the volume up button (volume button closest to power button) to unlock bootloader.
Press the volume up button, It will say it was successful, wait a few seconds for the tablet to return to fastboot
Type “fastboot flash boot magisk_patched.img” and when you hit enter you should see a transferring status on your tablet (if you named your modified .img file something else, type that into the command instead)
When you see the transfer is complete type “fastboot reboot” which will restart the tablet.
The tablet should now be rooted which will completely reset the tablet. You will need to setup the tablet again and reinstall the Magisk app from the official Github. The Magisk App should now have superuser controls
You can relock the bootloader and return the tablet to factory image. IT WILL WIPE ALL DATA AGAIN!
To unroot you just reverse a couple steps.
Put the original boot.img (Make sure it is the boot.img of the same version ROM) in the Minimal ADB and Fastboot Tools folder on your computer
Navigate to this folder, right click, and launch a Command Prompt
Plug in the tablet to your computer
Type “adb reboot bootloader” this should reboot your tablet into fastboot
When the tablet reboots into fastboot type “fastboot flash boot boot.img”
When you see the transfer is complete type “fastboot flashing lock” read the instructions on screen which will tell you to press the volume up button (volume button closest to power button) to lock bootloader. Press the volume up button.
Type “fastboot reboot” which will restart the tablet
You tablet should now be back to normal.
***Note, if you relock the bootloader first it will not let you flash the original boot.img file. If you make that mistake as I did once you'll be able to manually startup recovery mode by first powering off the tablet by holding down the power button, then boot into recovery by holding the power button and the volume up button until the recovery screen appears. Then you can unlock the bootloader again.
Click to expand...
Click to collapse
ok thank you bro for this very clean tuto, for me all went well, all works well, except for the restart where I have the Orange state problem with the 5 sec delay !!! ????
I tried what I was advised:
modify the LK.img, all went very well saying ok on the tab, ok on my Pc, but NO !!!!
I was a brick I think: black screen and nothing.
From there I rescued and redid everything,
conclusion : still the same, all goes except orange state and 5 delay
Can anyone or you ZIPPY411 help me with this please, I am lost with the veritydm pls
Thanks for reading and thanks again for all the work

Tacotac78570 said:
ok thank you bro for this very clean tuto, for me all went well, all works well, except for the restart where I have the Orange state problem with the 5 sec delay !!! ????
I tried what I was advised:
modify the LK.img, all went very well saying ok on the tab, ok on my Pc, but NO !!!!
I was a brick I think: black screen and nothing.
From there I rescued and redid everything,
conclusion : still the same, all goes except orange state and 5 delay
Can anyone or you ZIPPY411 help me with this please, I am lost with the veritydm pls
Thanks for reading and thanks again for all the work
Click to expand...
Click to collapse
By orange state I assume you are describing the unlocked bootloader warning screen.
Unfortunately I don't know of a way to get rid of that delay and warning screen from the boot process. It should not have any effect on your tablet other than just notifying you that the bootloader is unsecured. Rooting a tablet does this and creates a more vulnerable system state that the manufacturer wants to make sure you are aware of. The tablet should boot normally after the few second delay.

zippy411 said:
By orange state I assume you are describing the unlocked bootloader warning screen.
Unfortunately I don't know of a way to get rid of that delay and warning screen from the boot process. It should not have any effect on your tablet other than just notifying you that the bootloader is unsecured. Rooting a tablet does this and creates a more vulnerable system state that the manufacturer wants to make sure you are aware of. The tablet should boot normally after the few second delay.
Click to expand...
Click to collapse
Yeahhh all good bro ty, well I ve just change the lk.img in XD.dex and after flash fastboot the lk_a and perfect ,finish the Orange state

Tacotac78570 said:
Yeahhh all good bro ty, well I ve just change the lk.img in XD.dex and after flash fastboot the lk_a and perfect ,finish the Orange state
Click to expand...
Click to collapse
Hello @Tacotac78570
Could you write a tutorial how to remove orange state? What software you used to remove orange state in lk.img?
Best regards!

tajfunPL said:
Hello @Tacotac78570
Could you write a tutorial how to remove orange state? What software you used to remove orange state in lk.img?
Best regards!
Click to expand...
Click to collapse
Sup bro anyway easy u follow this thread and that take 10 min //
How to remove Orange, Yellow & Red state warnings on MTK
This guide will explain how to hide or remove Yellow, Red and Orange state warnings on a Mediatek Android device. Its ideal for those who feel irritated by constantly seeing these warnings on reboot.
www.hovatek.com

Hello,
Got a new TB125FU with firmware ver. "TB125FU_S000160_230227_ROW".
Anyone tried and succeeded rooting with this version?
Thank you