Database Users

Back to stock gone wrong

In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien

jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
I'm in the same boat as you. I've tried 6 computers. 1 detects it and I can unlock/lock bootloader but fails when I try to flash stock image.The other 5 computers, when I plug it in it freezes my tab in fastboot. WTF

logan_izer10 said:
I'm in the same boat as you.
Click to expand...
Click to collapse
Welcome aboard !

in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me

jfpesant said:
In short :
I had to unroot and relock for warranty purposes. I used Nexus 7 toolkit.
I selected option 9 "Download, Extract + Flash Google Factory Rom". Then, option 2 "Flash Google Factory Image" without going through option 1 "Download Google Stock Image" before. I thought I had already downloaded the image, which turned out I hadn't.
I don't know what it flashed, but now I'm stuck in fastboot mode, locked and unable to enable USB debugging. The only thing I can do is unlock/relock the N7.
Can some wizard help me out on that ?!?
Julien
Click to expand...
Click to collapse
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Read all the directions before you begin and perform the steps at your own risk.
I want to assume that you have the correct drivers installed, but I wont. This and any following verbosity is not to be condescending, but rather not to assume anything. If you're certain the adb and fastboot drivers are correctly, skip to step 7.
To obtain the tools and drivers needed, download the Android SDK - http://developer.android.com/sdk/index.html
Run the SDK installer that you downloaded and follow the on-screen instructions.
Make note of the install location which defaults to: C:\Users\<user name>\AppData\Local\Android\android-sdk this is where the tools and drivers will be downloaded to. This will be referred to as your sdk directory
Note: Java SE JDK is required by Android SDK. Download and install the Java SE JDK from Oracle
Run SDK Manager.
Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
Under Extras, check the box labeled "Google USB Driver"
Press the "Install # Packages..." button and follow the on-screen instructions.
Install the abd driver - detailed instructions can be found at http://developer.android.com/tools/extras/oem-usb.html
Note: in order for your device to be detected, USB debugging must be enabled on the device
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are attached to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
The device should now be in fastboot mode and Windows should be attempting to install the fastboot driver. You can verify that the driver has been installed by running the following command:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Download the factory image for Nexus 7 from https://developers.google.com/android/nexus/images#nakasi. The resulting file will have the extension .tgz. You will need something that can reliably decompress and extract files from this archive. If in doubt at all, use 7-Zip http://www.7-zip.org/download.html.
Open the archive with 7-Zip you should see a single .tar file. Open the .tar file with 7-Zip as well.
Inside the .tar file is a directory that will resemble "nakasi-jro03d". Open that directory.
Extract the contents of the "nakasi-jro03d" directory to <your sdk directory>/platform-tools. The extracted files should be as follows: bootloader-grouper-3.34.img, image-nakasi-jro03d.zip, flash-all.sh, flash-base.sh
The flash-all.sh file is a shell script that contains all the commands required to flash the factory image using the fastboot command. In order to use fastboot, we need to boot the device to fastboot mode. This can be done with adb:
Code:
> adb reboot-bootloader
In order to do anything useful, the bootloader must be unlocked. Do that like so:
Code:
> fastboot oem unlock
Follow the directions on the device, using the volume and power buttons to select "Yes".
In fastboot with your device's bootloader unlocked, run the commands listed in flash-all.sh in sequence, waiting for each command to finish. For convenience I have them here:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-3.34.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jro03d.zip
# optionally re-lock the bootloader.
# You may want to do this if you're returning the device for warranty work.
> fastboot oem lock
# finally, reboot
> fastboot reboot
That should do it.

tonybhoy said:
in the toolkit make sure you have the right model number in the "change" section,in the back to stock section check the "cant boot up"bit,then click flash stock + unroot,works all the time for me
Click to expand...
Click to collapse
Worked for me !!! Thanks bro !
(I previously have tried this, but didn't choose the right model number... so it didn't work)

comminus said:
As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn. The following instructions assume some basic Windows command prompt skills.
Click to expand...
Click to collapse
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien

jfpesant said:
Thanks a lot for the insight. I'm all about DIY so I'll definitely give this a try next time I have to play in android.
Julien
Click to expand...
Click to collapse
No worries, I'm glad the simpler route worked!

Boot loop after Android O DP2 update

I installed Android O DP2 update via OTA yesterday. The phone updated, rebooted to the new build and restarted abruptly and since then has been stuck in a boot loop. The Google logo shows up, goes to the android animation step and then Google logo appears again.
I don't have bootloader unlocked, don't have TWRP and have done OTA updates. I am able to get into the stock recovery mode.
How do I fix this, i.e. make it work in any way without erasing the user data? I don't mind extreme steps (without erasing user data) because I was planning to reflash 7 with unlocking & rooting today.

Try to wipe cache from recovery - in recovery hold volume-down and select "Wipe cache partition". Should do the trick

I tried, didn't work. Had to factory reset in the end. Also opted out of beta

I just read that some people that took the update from certain builds had boot loops due to the update only replacing part of the OS but leaving the 7.x.x system in place causing it to boot loop. I think it was like on android authority or something like that.
Sent from my Nexus 6P using XDA-Developers Legacy app

I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks

citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
citifone said:
I have similar problem. Phone became stuck at Google logo and bootloop. I didn't have OEM unlock and debugged enable when phone was working. Now I'm stuck because It cannot flash with any factory image rom. Anyone with solution, please help. Thanks
Click to expand...
Click to collapse
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
POWER BUTTON + VOLUME DOWN BUTTON
Click to expand...
Click to collapse
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.

Mavelos said:
You can unlock your bootloader to flash a stock ROM. Do you need the steps?
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
To flash a system image:
Download the latest system image for your Nexus 6p, then unzip it to a safe directory.
https://dl.google.com/dl/android/aosp/angler-n2g47o-factory-dc258043.zip
or Download any of your choice from here
https://developers.google.com/android/images
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
adb tool
http://developer.android.com/tools/help/adb.html
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device.
If necessary, unlock the device's bootloader using one of the following methods:
Code:
fastboot flashing unlock
If you are updating an older device, run this command:
Code:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory or Open a command prompt from within your System image folder (navigate to where you have flash-all.bat located on your PC, shift + right click anywhere within that folder, select open command prompt here
Execute the flash-all script.
Code:
fastboot flash-all.bat
This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
Code:
fastboot flashing lock
or, for older devices, run:
Code:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.

citifone said:
Thanks for your reply..But you can only do this only if you have an unlocked bootloader and debugged mode on. I didn't have either so it won't allow to flash with locked bootloader.
Click to expand...
Click to collapse
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.

FAILED (remote: OEM unlock is not allowed)
Mavelos said:
Exactly why i posted that. You can unlock your bootloader without turning USB debugging ON. Just Boot up with the POWER + VOLUME down Combination and use the bootloader unlock command in my previous post.
Click to expand...
Click to collapse
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?

citifone said:
Yes, I got the same error. Again, it's because of bootloader locked and debug is off. Any other ways to unlock or flash this phone?
Click to expand...
Click to collapse
To unlock you first need to have ticked the allow OEM unlock from developer menu within the OS. It won't work otherwise.

Lord Aguacate said:
What I think he is telling you and the same problem I have, when We try the unlock command we are getting this error :
FAILED (remote: OEM unlock is not allowed)
any suggestions ?
Regards.
Click to expand...
Click to collapse
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here [="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
="https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip"]https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?

Mavelos said:
You'll have to use a Rescue OTA
Download the latest Nexus 6P OTA from here https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
STEPS TO FOLLOW
To apply an OTA update image:
Download the appropriate update image for your device below.
https://dl.google.com/dl/android/aosp/angler-ota-n2g47o-ec3f4df1.zip
Boot into your recovery from fastboot
use the key combination for your device
Code:
POWER + VOLUME DOWN
and then select the Recovery option from the bootloader menu. The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
Run the following command on your PC:
Code:
adb devices
and check that your device shows up with "sideload" next to its name.
Run the following command:
Code:
adb sideload ota_file.zip
where ota_file.zip is the name of the file you have downloaded and verified.
Once the update finishes, reboot the phone by choosing Reboot system now.
Click to expand...
Click to collapse
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.

scorneil said:
I have the same problem as others, stuck in a bootloop and had not enabled unlock in dev options. I can get to bootloader but not recovery mode (bootloops when I select this). I would love to try this OTA side load, but I can't see my device in adb. I can see it however in fastboot. Not sure how to get it up in adb....
Any help would be much appreciated.
Click to expand...
Click to collapse
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
Lord Aguacate said:
Dear Mavelos,
I already tried that and the installation was successful, but my first problem still there, when I installed the Android O Beta, the touch of my screen stop working after the 2nd day of installation.
Now I don't know if this is a problem with Android O or just a coincidence and the hardware its broken.
I went to a lot of forums but nobody its talking about that (Touch Screen not working)
Did You guys hear anything about it?
Click to expand...
Click to collapse
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.

i have the same problem with this, and i cannot unlock it too, is there anyway to unlock this phone?

OTG works Perfect! But.....
Mavelos said:
If you get a bootloop when selecting recovery, try rebooting to recovery with fastboot
Code:
fastboot reboot recovery
if that doesn't work, then i think your device is bricked.
---------- Post added at 06:19 AM ---------- Previous post was at 06:16 AM ----------
If your touch screen isn't working, it might be related to the Android O Beta you flashed. Can you boot the phone up? If you have an OTG cable, connect a mouse to your phone. Turn on OEM unlocking in developer options. Do a factory reset.
Click to expand...
Click to collapse
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards

Lord Aguacate said:
So I Follow your suggestion and I bought the OTG adapter, works perfectly I unlocked the bootloader from the developers options, did a factory restore with a previous image, etc.... Touch still not working, I'm starting to believe this a hardware problem with the screen.... Bad Luck maybe, I don't know! ..... I will have to buy that expensive screen ($140).
Anyway thanks for the help...
Regards
Click to expand...
Click to collapse
You're welcome. Get your phone fixed and return to the flashing community.

last night i my phone inside my freezer hehehe and this morning i tried to turn it on, and it pass the google logo boot normally but it only lasted for a few minute and then turn off and bootloop again. so i guess my 6p has a hardware faulty

Complete Rooting Guide!

I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!

Will it work with Le1s eco x509
Will the given method work with le 1s eco x509

Yes it will!

Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?

deepu_ said:
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
Click to expand...
Click to collapse
Intel driver will not work try downloading drivers from skyneel for our phone

deepu_ said:
Im stuck in <waiting for any device>. I've installed the Intel drivers , what do you mean by select unrecognized device and install the Intel driver in it?
Click to expand...
Click to collapse
Intel drivers worked for my leeco le 1s. Ideally, Intel drivers should work for all devices.
I'll make a tutorial with screenshots on setting up the drivers whenever I get time.

i cant find "open command prompt here" with shift+ Right click in platform-tools folder

junaidshaik96 said:
i cant find "open command prompt here" with shift+ Right click in platform-tools folder
Click to expand...
Click to collapse
Make sure the directory is writable .

stealthinator16 said:
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!
Click to expand...
Click to collapse
It works perfectly on x507, thanks bro

Orange State
stealthinator16 said:
I have seen a lot of people using unofficial and third-party methods to root, which can result in a lot of adverse circumstances to say the least.
So I'm presenting a complete noob-friendly guide to rooting.
Prerequisites:
1. A computer ( I'm using Windows 10 but any OS would do)
2. A USB cable
3. Basic computer know-how
Part 1 (Getting computer ready)
Download sdk tools (adb and fastboot) from here
Note that in the entire guide I'm using official products.
So in Windows, download the zip and extract it in any folder.
Now download latest twrp recovery from here
The lastest version as of 7th August, 2017 is 3.1.
The downloaded file will be named as twrp-x.x.x-0-x3.img.
Now rename this as recovery.img (this will make our work easier)
Now move that file to platform-tools folder which we extracted earlier.
Also, I suggest downloading Intel USB drivers for Android from here
Part 2 (Getting Phone Ready)
Unlocking bootloader didn't format my phone but taking a backup is still important.
Now go to Settings<About Phone and click on Build until it says "You have become a developer"
Now back to main settings menu and find "Developer Options". And turn USB debugging on.
Download magisk install.zip, unistall.zip ans apk from here
Now connect your phone to PC via USB cable.
Step 3 (Rooting!!)
Now open platform-tools folder and press Shift+ right click.
Select "open command prompt here".
Now a terminal will open.
Type
Code:
adb devices
Now you will get a prompt on your phone. Accept it.
Now type
Code:
adb reboot bootloader
Your phone will automatically reboot and fastboot will come up.
Now type
Code:
fastboot oem unlock
[Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
And type prompt. Now type
Code:
fastboot flash recovery recovery.img
Flashing will start.
When you get type prompt again, type
Code:
fastboot reboot
And when the screen switches off, hold power up+power button.
(
Code:
fastboot reboot emergency
should work but it's effect was same as
Code:
fastboot reboot
If you get something like red state... verification failed... Then it's a good news.
Wait a few seconds and then twrp will launch. I suggest swiping on the first screen
[because letv is almost dead and we can't expect any updates. Plus my bootloader was relocked in my first attempt when I didn't swipe.]
(I suggest wiping dalvik cache and cache)
Now you can just reboot your phone normally.
Now install magisk apk.
Now reboot again to recovery. (Easiest way is Update app>tree dots menu> reboot to recovery)
When twrp starts, go to install> download and find magisk zip. Swipe to install.
Reboot and you have a fully rooted phone!!
Click to expand...
Click to collapse
There was a prompt for TWRP update and Magisk Update.
After it has started showing Orange State instead of Red State.
The phone got rebooted and all installed apps were deleted.
Xposed got uninstalled.
Playstore, Googlemaps got unistalled.
Camera is working.
Calling is working.
Now it shows Orange State.
Is it safe.
Can we bring it to red state?
As per this link
https://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
Orange warning: Your device is in an “unlocked” state. This means that your operating system can’t be checked to make sure that it’s safe to use.
Red warning: The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks.
Orange State seems to be a better state than red.

eighty9sid said:
There was a prompt for TWRP update and Magisk Update.
After it has started showing Orange State instead of Red State.
The phone got rebooted and all installed apps were deleted.
Xposed got uninstalled.
Playstore, Googlemaps got unistalled.
Camera is working.
Calling is working.
Now it shows Orange State.
Is it safe.
Can we bring it to red state?
As per this link
https://www.androidauthority.com/verified-boot-warnings-in-android-6-0-marshmallow-650368/
Orange warning: Your device is in an “unlocked” state. This means that your operating system can’t be checked to make sure that it’s safe to use.
Red warning: The operating system on your device has been changed or corrupted and is not safe to use. The device may not work properly and could expose your data to corruption and security risks.
Orange State seems to be a better state than red.
Click to expand...
Click to collapse
I too got orange state when I had to reroot my device after it got bricked, but there was no issue, everything worked perfectly.

Hi l used this very step by step guides but sadly l got stuck at the :-
Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
Here l select the unrecognized device and install the Intel drivers but it stuck at the "Okay,,,,Okay" prompt. Meaning that l didn't get this okay prompts and it keeps me on waiting the whole day.
Secondly, till this command l stop it and power down the phone, so after l power back on and try opening the "Application" folder, then it's not working anymore, it shuts down itself.
Please help!!

Valambok said:
Hi l used this very step by step guides but sadly l got stuck at the :-
Alert! If you get <waiting for device> right click on start menu, select the unrecognized device and install Intel driver in it. Google for detailed instruction]
The process will start and you will get something like
(Okay ....)
(Okay....)
Here l select the unrecognized device and install the Intel drivers but it stuck at the "Okay,,,,Okay" prompt. Meaning that l didn't get this okay prompts and it keeps me on waiting the whole day.
Secondly, till this command l stop it and power down the phone, so after l power back on and try opening the "Application" folder, then it's not working anymore, it shuts down itself.
Please help!!
Click to expand...
Click to collapse
Don't power off your phone. Post a screenshot of what exact problem you face with driver installation.

Phone Dead
Hi, after completing this step by step guides my Le 1s can't boot to normal anymore, even if I try booting up system from twrp also it doesn't help, I cant even power off now. So, please please help me out again on how to get back to a normal phone. Thanks in advance.
N.B: My phone shows Orange state

[GUIDE] OnePlus X: How to Unlock Bootloader and Backup EFS

Warning: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU/Motherboard by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try.
Click to expand...
Click to collapse
Code:
Index
1. Set Up Fastboot & ADB
2. Unlock OPX Bootloader
3. Enable USB Debugging & Activate OEM Unlock
4. How to backup EFS & Other Partitions
Lets get started
1. Set Up Fastboot & ADB Drivers:
What’s ADB?
ADB stands for Android Debug Bridge. It works when the device is powered on and booted into OS or Recovery. The tool helps in sending basic linux commands, and a variety Android specific commands from PC to connected Android devices.
What’s Fastboot?
Fastboot works only in bootloader/fastboot mode. It allows you to re-flash system partitions on your Android device and requires a device with an unlocked bootloader. It’s particularly useful when you want to update your device manually or in a rare situation when you accidentally soft-brick your device and need to install a clean stock system image.
Download and run adb-setup-1.3.exe
2. Unlock OPX Bootloader:
Backup important files stored on your OnePlus X before proceeding with the steps below, as unlocking the OnePlus X Bootloader will completely wipe/delete all files on the device.
After the installation of drivers (OnePlus X, Fastboot & ADB drivers) follow the below to proceed with Unlocking the Bootloader of your Oneplus X
3. Enable USB Debugging & Activate OEM Unlock:
* Go to Settings > About phone, and then tap ‘Build number’ 7 times or until you get the message ‘You’re now a developer!’.
* Go back to Settings, choose ‘Developer options’. Find the ‘USB debugging’ option and use this toggle button to enable it. Accept warning by tapping on OK button.
Also in the ‘Developer options’. Find the ‘OEM Unlocking’ option and use its toggle button to enable it. It asks for your PIN/Screen unlock code, type it. Then accept the warning by tapping on OK button.
Connect your OnePlus X to windows now. You will get a pop-up on your phone when you connect for the first time after enabling USB debugging. Select ‘Always allow from this computer’ checkbox and then tap on OK button. (You may or may not get this prompt so don’t bother if you dont)
Boot your OnePlus X into Bootloader/Fastboot mode. (Make sure you have backed up all important data as you’ll lose everything on phone in the steps below.)
Connect your OnePlus X — in Bootloader mode — to PC. Let the driver install.
Open a command window on your PC.
For this:
>>Open the adb folder on your PC.
>>Hold shift key, right click on empty white space.
>>Choose Open command window here option from that.
Power off your phone then boot into fastboot mode (power + volume up).
Connect your phone to your windows via usb cable.
Confirm whether fastboot is working. With OnePlus X connected to PC, run the following command in command window.
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection to unlock the bootloader use
Code:
fastboot oem unlock
The device will now go through the automated unlocking process, just let it do its thing and it'll boot up into Android.
You’ll see a new screen on your device. Choose Yes and confirm it.
That’s it. The device will reboot automatically.
To confirm unlock status, reboot into bootloader and type the following command:
Code:
fastboot oem device-info
Code:
Device unlocked: true
Other lines are not that important
4. How to Backup EFS & Other Partitions (Root Needed)
* Download Partitions Backup And Restore App from Here
* Open the app and grant it root access.
* Click on the Settings icon above and select preference to .img
* Select the partitions marked in yellow and backup them by clicking on the download like button at the bottom right.
* Go to the storage and search for the Partitions Backup folder there you will three .img files (modem,modemst1,modemst2) . Save them to your cloud and as many places as you want as they are very important files.
This way you can back up all other partitions too. (I would recommend backing up all those that are not found in a factory image.)

Is it different from TWRP somehow?

Caraparbor said:
Is it different from TWRP somehow?
Click to expand...
Click to collapse
It is quite different from TWRP, though it is not mandatory to perform a EFS backup.

Hi folks, i unlocked the boot loader (see attached file) but i can't start TWRP or Partitions Backup and Restore, any ideas?

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