Related
After hours of trying different methods to root the z1, and struggling with chinese based apps ... and accidentally wiping the phone ..... nothing manage to root the phone. until i came across the following,
anyways to make life easy i have complied all the steps that you need to do to root the phone from 3 seperate guides. I didnt write this article i just compiled it for easy reading
http://techbeasts.com/2013/12/19/in...ng-latest-14-2-0-a-290-firmware-how-to-guide/
http://techbeasts.com/2013/12/18/in...ers-quickly-with-minimal-tool-on-windows-pc/
http://techbeasts.com/2013/12/18/how-to-unlock-bootloader-of-sony-xperia-devices-guide/
This guide is only for Sony Xperia Z1 C6903/2.
1. Do not try this on any other model, please check your device’s mode in Settings > About Device.
2. The CWM / TWRP recovery is only for Xperia Z1 C6903/C6902 running latest Android 4.3 Jelly Bean 14.2.A.0.290 firmware. Check your firmware version in Settings > About Device and make sure that it matches the one mentioned here.
3. You must have installed Android ADB & Fastboot drivers.
TO INSTALL ADB & Fastboot Drivers tool:
a. Download the Minimal ADB & Fastboot Drivers tool: Link 1 | Link 2
b. Run the minimaltool.exe file that you downloaded and install the tool.
c. You can run the tool now by either through the Start menu, through the icon that you created on the desktop or by opening Program files > Minimal ADB & Fastboot > Right click on an empty area while keeping the shift key pressed and click on “Open Command Window Here”. ( NOTE: just double clicking on the desktop icon opens the command prompt window)
d. Use the Command prompt to do whatever you want now!
e. To install any .img file, you will have to place that file in the Minimal Tool folder that is located under Program files. (in win8.1 its : C:\Program Files (x86)\Minimal ADB and Fastboot)
f. To access the Fastboot mode, you’ll have to first bring the Fastboot mode on your device and then connect it. E.g on HTC devices you can highlight Fastboot mode by accessing it through HBoot and then connect it, while on Sony you can turn off the device and then while keeping the back or volume up key pressed plug in the USB cable.
That’s All! You’ve successfully installed Android ADB & Fastboot drivers. I hope that it didn’t take more than 2 minutes for you.
4. Your device must have an unlocked bootloader. This is the slightly troublesome part but its straight forward.
How to Unlock Bootloader
Install Android ADB & Fastboot Drivers using the quick setup with Minimal tool. Find the guide here.
Now first of all you need to check if your device’s bootloader unlocking is allowed or not, to do so open the dailer on your device.
Type *#*#7378423#*#*.
As soon as you enter the above code, a menu will open up.
Tap Service info > Configuration > Bootloader Unlock. If it says Yes, that means bootloader unlocking is allowed, else you can also find out if the Bootloader is already unlocked.
Now in the dialer type “*#06#”, you should get the IMEI number of your phone. Note it down somewhere
After verifying the bootloader unlock permission, turn off your device completely.
Now open the Minimal ADB and Fastboot command prompt, that you created using the guide above.
Press the back key or Volume Up key on your Xperia Device and connect it to your PC while keeping the key pressed. The back key works for older Xperia devices, while for newer devices Volume Up key will work.
In case you are trying to unlock the bootloader of your Sony Xperia Z1, please make sure that it’s running on latest Android 4.3 Jelly Bean firmware. If you tried to unlock bootloader on Android 4.2.2 firmware, it will cause the camera crash on your device.
In the command prompt type: fastboot.exe -i 0x0fce getvar version and press enter, you should get a response now e.g (0.3). This step is to verify that your device is properly connected or not.
Now open this Pageand accept the legal terms and conditions by Sony to unlock the bootloader.
After accepting the legal terms and conditions, enter your name, your phone’s IMEI number (Remove the last digit of IMEI number) and your email and click Submit button
You should receive an email by Sony immediately, the email has the Key to unlock your phone’s bootloader.
Now again in the command prompt type this com: fastboot.exe -i 0x0fce oem unlock 0xKEY. Repalce KEY with the code that you got in the email by Sony and hit Enter.
As soon as you hit Enter, the bootloader will be unlocked and show you logs in the command prompt.
5 . Please make sure that your phone’s battery is charged at least over 60%. This is highly recommended in order to prevent any power issues during the recovery flashing process.
6. Please make sure that you backup all of your important media content, contacts, call logs and important text messages. This is highly recommended so that in case something goes wrong, you can still restore your data.
7. Use only OEM data cable to establish connection between your PC and Phone.
8. Now that the basics are done.... this is how to root
How to Install TWRP / CWM Recovery on Xperia Z1 C6903 and C6902:
Download your desired recovery.img file:
i recommend philz advance cwm , its easier and you arent required to download supersu
Philz Advance CWM Recovery for Xperia Z1 C6903/2
CWM Recovery for Xperia Z1 C6903/2
TWRP Recovery for Xperia Z1 C6903/2
Place the downloaded Recovery.img file in the Minimal ADB & Fastboot folder that you created using our ADB & Fastboot Quick Setup Guide.
If you are using Android ADB & Fastboot full package, you can place the downloaded Recovery.img file in the Fastboot folder or in the Platform-tools folder.
Open the folder where you placed the Recovery.img file. E.g Minimal ADB & Fastboot or Fastboot or Platform Tools. (in win8.1 its : C:\Program Files (x86)\Minimal ADB and Fastboot)
Press and hold the shift key and right click on an empty area within the folder, and click on “Open Command Window Here”.
Turn off your Xperia Z1 completely.
Now press the Volume Up Key and while keeping it pressed plug in the USB cable.
You should see a blue light in the notification light of your phone, that means your device is now connected in Fastboot mode.
Now type the following command: Fastboot Flash boot Recoveryname.img
You may rename the recovery.img file for your ease of access and replace it with Recoveryname in the command to flash it.
Hit Enter and it will quickly flash CWM / TWRP recovery in your Xperia Z1.
How to Root Sony Xperia Z1 C6903 and C6902:
WITH PhilZ Advance CWM without installing SuperSu:
Boot into recovery (when the sony logo appears on boot press volume up volume down until the recovery loads)
Select Reboot System Now
Select Root device
Your phone will restart
Congrats! You’re rooted now.
WITH SuperSu:
Download the latest SuperSu.zip file.
Place the downloaded SuperSu.zip file on your phone’s sd card.
Boot into CWM / TWRP recovery on your phone.
Select Install Zip / Install > Choose Zip from SD / Ext Sd card > SuperSu.zip
Select Yes and let it flash SuperSu.
As soon as flashing is done, reboot your device.
Find SuperSu in App drawer.
Congrats! You’re rooted now.
You could root Z1 by flashing 14.1.G.1.534 and root with rootkitXperia, but it was too late
If you never use music features related to DRM, it's OK though...
Learn more about TA:
http://forum.xda-developers.com/showthread.php?t=2440597
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
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...
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 TB125ZAAJ0198SE
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
It took a bit of work to root OnePlus 8 T-Mobile version on the latest Android 12 update. I am a long time lurker and simply I wished someone else had posted the boot image to save me time. Can be simply flashed using fastboot commands.
Please check to make sure you are on the latest update from T-Mobile and that software version is: IN2017_11_C.43 Android 12 Security update November 5, 2022.
Installation instructions:
*You must have your phone unlocked for any carrier otherwise OEM unlocking will be unable to set.*
#1 go to settings, about device. TAP software version five times to enable developer options under system settings. Go to developer options and tick the following options:
a OEM Unlocking
b Enable USB debugging
#2 Download the OnePlus 8 Windows drivers and ADB fastboot drivers if your using a PC or Termux from F-Droid if using another rooted phone.
PC instructions:
Go to the directory you installed ADB and Fastboot. Open the command prompt by either right click on an empty space in that folder and finding command prompt or going to the directory tree and typing cmd and hit enter. Inside the Windows command prompt the root directory should be the same folder as your ADB and fastboot executables. Move the attached boot image to the same folder as your ADB and fastboot executables and rename it boot.img. Attach your phone to your PC and run the following commands:
adb devices
This command is so you can check to see if your PC is correctly configured and it should send you a notification on your phone to allow debugging from your PC, make sure you will allow it always.
adb reboot fastboot
This command will reboot your phone into fastboot mode. Do not select any you on your phone and only type in the following commands on your PC.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This command will flash the magisk modified boot image which will grant you root access to your phone.
fastboot reboot
This command will reboot your phone. Congrats, your now rooted on the latest Android 12 update for your T-Mobile Oneplus 8!
what attached boot img?
zeromonarch said:
what attached boot img?
Click to expand...
Click to collapse
I must've somehow missed it too. I cant find any boot image to download
If only there were the elusive boot image...
It could have saved my ass from the current double-slotted brick I sit upon!
Does anyone have the boot image for the latest T-Mobile update?
IN2017_11_C.45
in fact this isn't even the latest as there is a new update waiting for me with the new security release or security update but I haven't updated yet also does this wipe data?