Hi guys
I want to install on my Shield TV a full Android Rom
ADB 1.4.2 is installed
opened cmd box and gave "adb reboot bootloader"
https://drive.google.com/file/d/0B6EbGlAGPRmXRkhoanhHUi1FZVE/view?usp=sharing
Now this screen appears on the TV Shield
https://drive.google.com/file/d/0B6EbGlAGPRmXeS1uSmc0RG5IQVE/view?usp=sharing
from here I do not get ahead, maybe I'm too stupid
what am I doing wrong, I am on this side looked but this guide is probably for advanced users http://forum.xda-developers.com/shield-tv/development/rom-t3138575
someone can give me an exact step by step guide to understand even beginners
If you have the bootlaoder unlocked, you should flash a recovery
Tapatalk-kal küldve az én C6903-el
swarced said:
If you have the bootlaoder unlocked, you should flash a recovery
Tapatalk-kal küldve az én C6903-el
Click to expand...
Click to collapse
when I type the command appears
fastboot oem unlock
< waiting for divice >
and nothing happens
Did you allow USB debugging in the developer menu?
Tapatalk-kal küldve az én C6903-el
Yes, USB debugging is on
The usb driver of shield tv is not install , it must be , download it from nvidia and install ,unstall current drivers first
you can try this at command line
fastboot devices
leasing said:
The usb driver of shield tv is not install , it must be , download it from nvidia and install ,unstall current drivers first
you can try this at command line
fastboot devices
Click to expand...
Click to collapse
How can I tell if the correct USB driver installed?
at the moment it is so, if I connect the shield is the window where I can access the internal memory and SD card
im on the latest firmware aswell 2.1 and i got the bootloader unlocked and all but i cant seem to get twrp recovery installed no matter what i do.
i have flashed the full android os 5.1 from here with no problems at all but i want to have my stock fw 2.1 with twrp recovery installed instead....can someone explain why its not working for me or am i doing something wrong?
ok, have uninstalled everything
new USB driver from Nvidia
but no change in command "fastboot oem unlock"
it still comes "waiting fo device"
I use Win 10, makes a difference which OS I use
or do I still lack something
I have:
adb Setup 1.4.2
Full Android for Shield TV_2.1zip
Preparation
Install*Minimal ADB and Fastboot*if you do not already have it installed.Ensure the*Shield Family drivers*are extracted somewhere on your system and you know where they are.Make sure you know how to get to*Device Manager*on your PC.Extract*TWRP Recovery*image. Put this in yourMinimal*ADB and Fastboot*folder (usuallyc:\program files(x86)\Minimal ADB and Fastboot\).Copy*supersu.zip*into your*Minimal*ADB and Fastboot*folderPlug your Shield TV into the PC with USB cable.Plug your mouse into a USB port.Confirm drivers for ADB are installedn your PC, go to*Device Manager. *Find the yellow (!) ADB device. *If none exist, you probably already have drivers. *Skip to step 9.Right click the device and select*Update Driver.When offered, browse your computer for the driver and point it to the*Shield Family Drivers*folder you extracted inPreparation Step 2*above.When finished with the driver install, the (!) yellow device should be gone.Enable*Developer*mode on Shield TVOn the Shield TV, go to Settings->About->Build (tap 7 times on the BUILD to unlock developer mode) –*you have to back out of Settings and go back in before Developer will appear.Enable*USB Debugging*on Shield TVSettings -> Developer -> Debugging; set to*OnA popup should appear asking for this PC’s authorization. *Check the*Don’t ask again for this PC*box and select*Allow. *If it doesn’t show up now, it will later.
Root Procedure
Reboot into Bootloader on ShieldLaunch*Minimal ADB and Fastboot*from the Start Menu or icon on the PC. *This puts you in a black DOS box.Type “adb devices” and make sure your Shield TV appears. *Note: If you didn’t have a popup on your Shield TV screen in Step 10.2 above, it probably will appear now. *You’ll have to authorize the PC before it will show up under adb devices.Once you see your Shield TV when you run “adb devices” you’re ready to proceed.Type “adb reboot bootloader” and hit enter. *The Shield TV should reboot into the bootloader screen.Verify Fastboot Drivers are installedn your PC, go to Device Manager.See if a yellow (!) exists that mentions FASTBOOT. *If not,*continue to Step 3.Right click the device and select Update Driver.When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.When finished with the driver install, the (!) yellow device should be gone.Type “fastboot devices” and make sure your Shield TV is visible.Unlock BootloaderType in “fastboot oem unlock” and hit enter.You will see a PLEASE WAIT … appear on the Shield TV screen. *This will take several minutes (16GB) up to two HOURS (500GB). *Do not be impatient! *Let it finish.Reboot to Shield TV InterfaceOnce the bootloader is unlocked, reboot the Shield TV and return to the Shield TV main interface.Repeat*Preparation Steps 9 and 10*above to re-enable Developer/USB Debugging. *Note: at some point you will have to re-authorize your PC again; if an ADB command fails, be sure to look at your Shield TV screen for the authorization prompt.Push supersu.zip to the ShieldIn the*Minimal ADB and Fastboot*DOS window, type: “adb push supersu.zip /sdcard/”You should see text indicating the file was copied over correctly.Reboot to BootloaderType “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.Fastboot/Install *TWRPType “fastboot devices” and make sure your Shield TV is visible.If your Shield TV is listed, type “fastboot flash recovery twrp-shieldtv.img” and hit enter. *Note: This*is required for V1.4 update and above. *If you have 1.3, you can do a temp boot to TWRP with “fastboot boot twrp-shieldtv.img”.Select*Boot Recovery Kernel*in the fastboot menuYou should see the TWRP Recovery screenIf you are asked if you want to preserve Read Only on the system, say YES.Ensure your mouse is plugged in and working.Install SuperSUSelect INSTALL.Navigate and select supersu.zip.Follow the instructions to Swipe to FlashSuperSU will install.Reboot to SystemSelect REBOOT then SYSTEM from the TWRP menuAnswer NO if asked anything about fixing or restoring ROOTRun SuperSU application and apply any updatesOnce you are back up and running (first boot can take a little longer) find the SuperSU app installed on the Shield TV. *Run it and perform any upgrades (select “Use Normal” if asked).You are now rooted!
sended from iPhone 9
---------- Post added at 01:25 PM ---------- Previous post was at 01:15 PM ----------
swarced said:
Preparation
Install*Minimal ADB and Fastboot*if you do not already have it installed.Ensure the*Shield Family drivers*are extracted somewhere on your system and you know where they are.Make sure you know how to get to*Device Manager*on your PC.Extract*TWRP Recovery*image. Put this in yourMinimal*ADB and Fastboot*folder (usuallyc:\program files(x86)\Minimal ADB and Fastboot\).Copy*supersu.zip*into your*Minimal*ADB and Fastboot*folderPlug your Shield TV into the PC with USB cable.Plug your mouse into a USB port.Confirm drivers for ADB are installedn your PC, go to*Device Manager. *Find the yellow (!) ADB device. *If none exist, you probably already have drivers. *Skip to step 9.Right click the device and select*Update Driver.When offered, browse your computer for the driver and point it to the*Shield Family Drivers*folder you extracted inPreparation Step 2*above.When finished with the driver install, the (!) yellow device should be gone.Enable*Developer*mode on Shield TVOn the Shield TV, go to Settings->About->Build (tap 7 times on the BUILD to unlock developer mode) –*you have to back out of Settings and go back in before Developer will appear.Enable*USB Debugging*on Shield TVSettings -> Developer -> Debugging; set to*OnA popup should appear asking for this PC’s authorization. *Check the*Don’t ask again for this PC*box and select*Allow. *If it doesn’t show up now, it will later.
Root Procedure
Reboot into Bootloader on ShieldLaunch*Minimal ADB and Fastboot*from the Start Menu or icon on the PC. *This puts you in a black DOS box.Type “adb devices” and make sure your Shield TV appears. *Note: If you didn’t have a popup on your Shield TV screen in Step 10.2 above, it probably will appear now. *You’ll have to authorize the PC before it will show up under adb devices.Once you see your Shield TV when you run “adb devices” you’re ready to proceed.Type “adb reboot bootloader” and hit enter. *The Shield TV should reboot into the bootloader screen.Verify Fastboot Drivers are installedn your PC, go to Device Manager.See if a yellow (!) exists that mentions FASTBOOT. *If not,*continue to Step 3.Right click the device and select Update Driver.When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.When finished with the driver install, the (!) yellow device should be gone.Type “fastboot devices” and make sure your Shield TV is visible.Unlock BootloaderType in “fastboot oem unlock” and hit enter.You will see a PLEASE WAIT … appear on the Shield TV screen. *This will take several minutes (16GB) up to two HOURS (500GB). *Do not be impatient! *Let it finish.Reboot to Shield TV InterfaceOnce the bootloader is unlocked, reboot the Shield TV and return to the Shield TV main interface.Repeat*Preparation Steps 9 and 10*above to re-enable Developer/USB Debugging. *Note: at some point you will have to re-authorize your PC again; if an ADB command fails, be sure to look at your Shield TV screen for the authorization prompt.Push supersu.zip to the ShieldIn the*Minimal ADB and Fastboot*DOS window, type: “adb push supersu.zip /sdcard/”You should see text indicating the file was copied over correctly.Reboot to BootloaderType “adb reboot bootloader” and hit enter. The Shield TV should reboot into the bootloader screen.Fastboot/Install *TWRPType “fastboot devices” and make sure your Shield TV is visible.If your Shield TV is listed, type “fastboot flash recovery twrp-shieldtv.img” and hit enter. *Note: This*is required for V1.4 update and above. *If you have 1.3, you can do a temp boot to TWRP with “fastboot boot twrp-shieldtv.img”.Select*Boot Recovery Kernel*in the fastboot menuYou should see the TWRP Recovery screenIf you are asked if you want to preserve Read Only on the system, say YES.Ensure your mouse is plugged in and working.Install SuperSUSelect INSTALL.Navigate and select supersu.zip.Follow the instructions to Swipe to FlashSuperSU will install.Reboot to SystemSelect REBOOT then SYSTEM from the TWRP menuAnswer NO if asked anything about fixing or restoring ROOTRun SuperSU application and apply any updatesOnce you are back up and running (first boot can take a little longer) find the SuperSU app installed on the Shield TV. *Run it and perform any upgrades (select “Use Normal” if asked).You are now rooted!
sended from iPhone 9
Click to expand...
Click to collapse
http://nvidiashieldzone.com/files/...ne.com/files/shieldtv/shieldfamilydriver.zip
http://www.nvidiashieldzone.com/files/shieldtv/twrprecovery.zip
http://www.nvidiashieldzone.com/files/shieldtv/supersu.zip
sended from iPhone 9
MrAnhell said:
im on the latest firmware aswell 2.1 and i got the bootloader unlocked and all but i cant seem to get twrp recovery installed no matter what i do.
i have flashed the full android os 5.1 from here with no problems at all but i want to have my stock fw 2.1 with twrp recovery installed instead....can someone explain why its not working for me or am i doing something wrong?
Click to expand...
Click to collapse
I'd be VERY carefull with TWRP and the latest 2.1 firmware.......the two main devs for our shield both bricked their shields, something to do with 2.1 bootloader changes and twrp i think.......theres not much info, except that its advised not to flash twrp on 2.1 until a fix is found, IF one is found..............like i said, theirs not much info on what exactly causes the brick.......maybe twrp is fine, which i would love to be the case, but im waiting until thats confirmed for now
Ok, so I still have the SuperSu.zip and TWRP Recovery.image?
Where can I get this? Could anything about it in zulu99 Read the manual
DaveO88 said:
How can I tell if the correct USB driver installed?
at the moment it is so, if I connect the shield is the window where I can access the internal memory and SD card
Click to expand...
Click to collapse
The fact that "adb reboot bootloader" works, seems to imply that the adb drivers are installed properly
Might wanna write down step by step, what it is your doing right up until the moment you cant go any further.....and to be thourough copy and paste the actual instructions you're following........might get better help
Unlocking the bootloader wipes EVERYTHING, you start from scratch basically, this may take a while, alot longer on the 500gb versions...........keep an eye on the command line when unlocking bootloader or flashing, it should tell you that its doing something and when its finished doing something
Be carefull with these things
Another thing, incase you didnt know, you can navigate the bootloader screen with the power button, single touch goes through the menu, and long touch selects the highlighted option
Now I've done it, bootloader is unlocked
the Full Android zip is on the desktop
Unzip or not?
the next step will be in the command window "fastboot flash system system.img" should
but it comes "error - can not find Image"
DaveO88 said:
Now I've done it, bootloader is unlocked
the Full Android zip is on the desktop
Unzip or not?
the next step will be in the command window "fastboot flash system system.img" should
but it comes "error - can not find Image"
Click to expand...
Click to collapse
Put the system.img into your folder with athwr adb files
sended from iPhone 9
Thanks to all for the help, Full Android is now on the shield Tv
(Just want to share my experience.)
For those who wants to upgrade from stock 1.3, 1.4, 2.0 to 2.1, better to do OTA upgrade than download and flash stock from NVIDIA.
Just step by step OTA. If something is wrong, just do HW fastboot (pls google), then flash stock 1.3 and start from beginning.
You may brick yours by flashing 2.1 (stock dev) over stock 1.3. Therefore, pls avoid to flash any stock firmwares except stock 1.3.
After successfully upgrading to stock 2.1, you can follow the guide to flash Full Android OS.
You now have full android OS (rooted) on your Shield but no wireless Shield controller (wired one is OK).
DaveO88 said:
when I type the command appears
fastboot oem unlock
< waiting for divice >
and nothing happens
Click to expand...
Click to collapse
Ok, maybe you miss some thing,
when you to do this things ,you need connect you SATV HDMI to a display or TV,
first connect OTG to computer usbport will get a prompt at satv screen ,add trust PC in something like that,use satv Controller press a button to confirm.
have you done this?Because even if you don't do it, you can still see satv in the computer.
Here is a tip, when the restart into the FastBoot environment, the computer will have a sound prompt,if not,your computer driver or ADB environment Certainly not correct
DaveO88 said:
Thanks to all for the help, Full Android is now on the shield Tv
Click to expand...
Click to collapse
Glad to hear it
you can try this at command line
Related
Introduction
The purpose of this guide is to provide you with step-by-step instructions on how to unlock the bootloader on your Nvidia Shield.
Why Would I want to Unlock my Bootloader?
Unlocking your bootloader allows you to modify all aspects of your device to suite your needs which includes but is not limited to, installing custom Recovery images such as Clockworkmod Recovery or Team Win Recovery Project, installing custom ROM's, custom Kernels, as well as other MOD's and patches.
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield's bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
This warning being given please also see this post by JordanKeyes regarding warranty information as it relates to hardware issues or hardware failures.
Unlocking your Bootloader
1. Backup everything on your device that you don't want to loose such any apps (And there respective data), pictures, videos, music, etc. as unlocking your devices bootloader will erase all data on the device. You can fully backup your devices contents without root using ADB's backup command or by using the Holo Backup Tool.
2. Download and install the ADB and Fastboot drivers for your Shield, the drivers can be downloaded here. You can also follow along with wwjoshdew's excellent video tutorial on how to properly install the ADB and Fastboot drivers for your Shield on Windows.
3. Make sure you have ADB and Fastboot setup and installed on your computer. If you haven't already setup and installed ADB and Fastboot a simple ADB and Fastboot installer can be downloaded from here.
4. Fully power off your Shield by long pressing on the Power button until the power menu appears, then select the "Power off" option.
5. Boot your Shield into Fastboot mode using one of the following ways:
5. A. Power on your Shield while simultaneously holding the Power button + Back button + Home button. Release the buttons once the Fastboot bootloader screen appears.
5. B. Run the following ADB command from a command prompt window (USB cable must already be connected from your Shield to your Computer):
Code:
adb reboot bootloader
6.Now that you are at the Fastboot bootloader screen, connect your Shield to your computer using your USB cable. Make sure that your USB cable is plugged into a USB 2.0 port directly connected to your motherboard as sometimes USB 3.0 ports can cause problems and front panel USB connections can be unreliable.
7. Open up a command prompt window (cmd) in the directory where installed ADB and Fastboot to. For example if I installed ADB and Fastboot to a folder on my Desktop which is on my D: drive I would open a command window in "D:\Desktop\Fastboot_ADB".
8. From the command prompt windows enter the following command:
Code:
fastboot devices
If you device is detected and it shows your devices serial number you are ready to move on to the next step. If no device is shown make sure you have the correctly installed the ADB and Fastboot drivers from step number 2.
9. Now that your device is detected by Fastboot the following command is used to unlock your bootloader:
Code:
fastboot oem unlock
10. You will now be presented with the bootloader unlock menu. After reading the disclaimer, use the Back button and the Home button to navigate to the "Unlock" option. Once the "Unlock" option has been highlighted use the Shield button to confirm your selection of unlocking your bootloader. It's important to remember that unlocking the bootloader will wipe all your data from the device, and that a flag showing your warranty is void will appear at the bootloader screen.
11. Once your bootloader has finished being unlocked, you will be taken back to the fastboot bootloader screen. From here you can power off your Shield.
Re-locking your Bootloader
To re-lock your bootloader you can following steps 4-8 of the procedure listed above and when you come to step 9 run the following command instead of "fastboot oem unlock":
Code:
fastboot oem lock
The above command will re-lock your Shield's bootloader. Note: As previously mentioned re-locking your Shield's bootloader will not restore your warranty or remove the warranty void flag on your device's bootloader.
Conclusion
Now that you have successfully unlocked the bootloader on your Nvidia Shield you are free to flash custom Recoveries, ROM's, Kernel's, MOD's etc. enjoy :good:.
If you are stuck with the bootloader unlocking procedure I would recommend checking out this great video tutorial by wwjoshdew.
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Edit: followed the instructions in the following video and all is dandy now. http://www.youtube.com/watch?v=XSisjVwcPbE&hd=1
themichael said:
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Click to expand...
Click to collapse
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
fastboot error
chevyowner said:
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
Click to expand...
Click to collapse
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
gogul1 said:
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
Click to expand...
Click to collapse
Nvidia just released a new set of USB drivers in their Tegra for Android Development Pack which you can download from here. I would recommend installing the development pack and the drivers it includes.
ok
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
gogul1 said:
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
Click to expand...
Click to collapse
From that pic you posted the mount command failed because you were not root.
chevyowner said:
From that pic you posted the mount command failed because you were not root.
Click to expand...
Click to collapse
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
shimp208 said:
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
Click to expand...
Click to collapse
Huh??????????
EDIT
Were you trying to answer this post
chevyowner said:
Huh??????????
EDIT
Were you trying to answer this post
Click to expand...
Click to collapse
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
shimp208 said:
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
Click to expand...
Click to collapse
No problem.
I had to change to oil in my car in a parking lot earlier because it was cheaper to change it then it would have been add 3-4 quarts and change it when I got home. My car need 5 quarts of oil. I was not in a a good mood then.
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
thx. works nice.
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: [
How To Root the Nvidia Shield: []
Click to expand...
Click to collapse
Sweet thanks
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Click to expand...
Click to collapse
I tried another proggie to root and got jammed up.. following the videos josh did had me rooted in minutes. Great job and thanks!
why?
Code:
C:\Users\Thomas>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I tried it with the Shield RAM tool, but won't work either..
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
mr.dude5660 said:
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
Click to expand...
Click to collapse
Where did you find the towelroot apk? Been searching for over a month with no success.
Sent from my VS980 4G using Tapatalk
BTW, bootloader mode on the tablet:
- Hold "Volume Down" -> Press "Power" and continue to hold "Volume Down" until device boots into bootloader mode.
There is no home or back button to press while the device is off.
Sorry for bump this thread, but i have to.
I want to unlock my bootloader to revert back into KK and then try to do a clean installation of LP. Reading this guide and watching the videos, and also looking into the img downloaded from nvidia, it says i have to install the fastboot drivers. The problem is that i have already installed fastboot and adb drivers since i have some other devices as a Xperia and stuff. For me, there is no Yellow sign as shown in the video, my device is recognized as Portable Device and it already says "Shield Tablet" MTP.
I've tried going into bootloader to see if it prompts any new devices but i got nothing. adb devices show my device, but i'm not sure if i need more.
I ordered this from amazon.com USA and received it in China
I have just turned on this device and this is the first screen and there no option to skip it unless I complete it. When there is no WiFi connection, there is no option to click next.
So when I click next after connecting to WiFi which is the only way I can have the NEXT option enable so when I connect to WiFi and click next, after some loading screen I get this message: ERR_CONNECTION_RESET.
I am afraid if this is because the device must connect to some google's server (which is blocked in china) to get past this first step.
P.S. This is NOT my account registration it (as it didn't ask me about it yet) I think its device registration of some kind in the newest android stock version. Hope you understand
Is there a way to activate it without an internet so I can get past this process? Please advice.
start mobile internet as wifi hotspot. connect nexus 7 to it. and there u go. afterwards it wont ask again.
Sent from my XT1068 using XDA Free mobile app
cosmickamal said:
start mobile internet as wifi hotspot. connect nexus 7 to it. and there u go. afterwards it wont ask again.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
I think you did not read my post clearly... Yes you didn't
You might not like this solution (as it involves unlocking the bootloader and flashing a custom ROM), but you could flash a custom ROM like CyanogenMod. It doesn't come with Google Apps.
Nixtren said:
You might not like this solution (as it involves unlocking the bootloader and flashing a custom ROM), but you could flash a custom ROM like CyanogenMod. It doesn't come with Google Apps.
Click to expand...
Click to collapse
Please tell me how do I do it considering that I can not touch any option of this device as I can not access any of its settings. Please redirect me to the related thread/tutorial link.
Thanks a lot
a4abbas said:
Please tell me how do I do it considering that I can not touch any option of this device as I can not access any of its settings. Please redirect me to the related thread/tutorial link.
Thanks a lot
Click to expand...
Click to collapse
The following steps is in case you have Nexus 7 (2012), Wi-Fi edition:
1 - Install Android SDK (platform-tools) and Google USB Driver (read Software Requirements and Driver Installation)
http://forum.xda-developers.com/showthread.php?t=1907796
2 - Download TWRP for Nexus 7 (2012) Wi-Fi edition
dl.twrp.me/grouper/twrp-2.8.7.0-grouper.img
3 - Boot your tablet into bootloader/fastboot mode
Power off the device completely.
To enter Fastboot Mode you will need to press and hold Volume Down and Power, all at the same time.
– do not release the buttons.
Release all buttons when the Fastboot screen appears.
– that’s it, if you see the START option listed in the upper part of your screen you’re done.
Click to expand...
Click to collapse
4 - Connect your tablet to your computer via USB (if you don't have it connected already)
5 - Type in the command prompt "fastboot devices" (don't forget to open the command prompt and go to the fastboot folder)
You should see your device listed there. You don't see it? Don't continue and inform us.
6 - Move the file twrp-2.8.7.0-grouper.img to your fastboot folder
7 - Type "fastboot oem unlock", after unlocking the bootloader type "fastboot boot twrp-2.8.7.0-grouper.img"
Wait a few seconds and your tablet should boot into TWRP. TWRP is a custom recovery software for your tablet. It allows us to perform backups and restore your device, as well as installing custom ROMs. If you don't know what is a custom ROM, think of it as a "modified Android".
8 - Download CyanogenMod for your device
Here's the latest stable version available:
https://download.cyanogenmod.org/get/grouper-snapshot.zip
9 - In TWRP, go to "Wipe", "advanced wipe" and select "System" and "Cache" (and/or dalvik-cache). Wipe those partitions.
10 - In TWRP, go to "Advanced" and click "ADB Sideload"
11 - In your command prompt, type "adb sideload grouper-snapshot.zip" (replace "grouper-snapshot.zip" with the name of the zip file of CyanogenMod you downloaded)
12 - Wait until it finishes, it will take a few minutes. Don't disconnect the USB cable!
13 - Once it finishes, reboot to the system
Let us know if it worked
If you are stuck in a step it's better to come here and say it instead of trying to discover by yourself. Some people bricked their devices because they didn't knew what they were doing.
Also, I'm not sure if you can download the Android SDK, because of the censorship. Let me know.
Nixtren said:
The following steps is in case you have Nexus 7 (2012), Wi-Fi edition:
1 - Install Android SDK (platform-tools) and Google USB Driver (read Software Requirements and Driver Installation)
http://forum.xda-developers.com/showthread.php?t=1907796
2 - Download TWRP for Nexus 7 (2012) Wi-Fi edition
dl.twrp.me/grouper/twrp-2.8.7.0-grouper.img
3 - Boot your tablet into bootloader/fastboot mode
4 - Connect your tablet to your computer via USB (if you don't have it connected already)
5 - Type in the command prompt "fastboot devices" (don't forget to open the command prompt and go to the fastboot folder)
You should see your device listed there. You don't see it? Don't continue and inform us.
6 - Move the file twrp-2.8.7.0-grouper.img to your fastboot folder
7 - Type "fastboot oem unlock", after unlocking the bootloader type "fastboot boot twrp-2.8.7.0-grouper.img"
Wait a few seconds and your tablet should boot into TWRP. TWRP is a custom recovery software for your tablet. It allows us to perform backups and restore your device, as well as installing custom ROMs. If you don't know what is a custom ROM, think of it as a "modified Android".
8 - Download CyanogenMod for your device
Here's the latest stable version available:
https://download.cyanogenmod.org/get/grouper-snapshot.zip
9 - In TWRP, go to "Wipe", "advanced wipe" and select "System" and "Cache" (and/or dalvik-cache). Wipe those partitions.
10 - In TWRP, go to "Advanced" and click "ADB Sideload"
11 - In your command prompt, type "adb sideload grouper-snapshot.zip" (replace "grouper-snapshot.zip" with the name of the zip file of CyanogenMod you downloaded)
12 - Wait until it finishes, it will take a few minutes. Don't disconnect the USB cable!
13 - Once it finishes, reboot to the system
Let us know if it worked
If you are stuck in a step it's better to come here and say it instead of trying to discover by yourself. Some people bricked their devices because they didn't knew what they were doing.
Also, I'm not sure if you can download the Android SDK, because of the censorship. Let me know.
Click to expand...
Click to collapse
My device is Nexus 7 2013 (Wifi) Flo. Should I follow the same steps or not? Please advice!
Follow these steps for Nexus 7 (2013, Wi-Fi) (flo):
1 - Install Android SDK (platform-tools) and Google USB Driver (read Software Requirements and Driver Installation)
http://forum.xda-developers.com/showthread.php?t=1907796
2 - Download TWRP for Nexus 7 (2013) Wi-Fi edition
https://dl.twrp.me/flo/twrp-2.8.7.0-flo.img
3 - Boot your tablet into bootloader/fastboot mode
Power off the device completely.
To enter Fastboot Mode you will need to press and hold Volume Down and Power, all at the same time.
– do not release the buttons.
Release all buttons when the Fastboot screen appears.
– that’s it, if you see the START option listed in the upper part of your screen you’re done.
Click to expand...
Click to collapse
4 - Connect your tablet to your computer via USB (if you don't have it connected already)
5 - Type in the command prompt "fastboot devices" (don't forget to open the command prompt and go to the fastboot folder)
You should see your device listed there. You don't see it? Don't continue and inform us.
6 - Move the file twrp-2.8.7.0-flo.img to your fastboot folder
7 - Type "fastboot oem unlock", after unlocking the bootloader type "fastboot boot twrp-2.8.7.0-flo.img"
Wait a few seconds and your tablet should boot into TWRP. TWRP is a custom recovery software for your tablet. It allows us to perform backups and restore your device, as well as installing custom ROMs. If you don't know what is a custom ROM, think of it as a "modified Android".
8 - Download CyanogenMod for your device
Here's the latest stable version available (Android 4.4):
https://download.cyanogenmod.org/get/jenkins/90768/cm-11-20141115-SNAPSHOT-M12-flo.zip
9 - In TWRP, go to "Wipe", "advanced wipe" and select "System" and "Cache" (and/or dalvik-cache). Wipe those partitions.
10 - In TWRP, go to "Advanced" and click "ADB Sideload"
11 - In your command prompt, type "adb sideload cm-11-20141115-SNAPSHOT-M12-flo.zip"
12 - Wait until it finishes, it will take a few minutes. Don't disconnect the USB cable!
13 - Once it finishes, reboot to the system
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
Hi,
rooted 2017 16GB ShieldTV.
Unlocked bootloader.
TWRP was not installed just used to boot once and installed SuperSU (I feel like an idiot learning this only after)
Played with it - removed some critical system apps, and also managed to disable USB debugging (this only as I thought that TWRP was installed - and felt safe to do ANYTHING)
Now - boot to fastboot happens, but there is no adb.
Any saving method?
Original recovery gives options to ADB sideload and USB update.
Tried to use this by putting official Nvidia stock image on USB and but it reports signature failed, and refuses to flash.
Any help?
Thanks guys
SOLVED
Writting this as soon as I could cool down.
Situation:
- Shield ATV 16GB 2017. SW Nougat 5.2
- Unlocked bootloader (every boot gives that safety warning)
- System bootloop on Android circles animation (managed to root it previously and removed some critical apps by mistake)
- NO USB debugging
- NO custom recovery (as process for rooting only used TWRP to flash SuperSU, nothing else)
- Entering fastboot possible only by hardware method (controller connected by USB, hold A+B buttons while Shield is plugged off 10sec, then plug Shield in. Two short vibrations of controller and fastboot screen appears.)
However - NO adb in fastboot. (pinging with adb devices gives NO response). Only option that works is entering official recovery which gives options for adb sideload or update from USB. However - no zip file is accepted due signature check (and I tried tons of them)
Tools
1. Windroid
https://forum.xda-developers.com/showthread.php?t=2499926
2. Proper TWRP build
http://nvidiashieldzone.com/download/twrp-3-1-1-1-shield-tv/
3. Custom flashable rom (I used Lineage OS for Shield - lite and without Gapps - to speed up booting into environment that works). Put it onto USB drive
4. Oficial Nvidia recovery image (https://developer.nvidia.com/shield-open-source)
5. Minimal ADB and Fastboot (http://nvidiashieldzone.com/download/minimal-adb-and-fastboot/)
6. Nvidia controller plugged into USB port next to HDMI
7. Male-to-male USB cable (for ADB)
8. USB mouse
Process
1. Start Windroid and choose device (Nvidia, Shield TV)
Windroid will automatically download resources in Data folder (incl. TWRP that did not work for me), so dont block it with firewall.
2. Download proper TWRP from link above, and replace the one in Windroid Data/Recoveries folder using same name (Recovery1.img). You will notice difference in sizes. One that Windroid downloads is 25mb, while the one from link is ~ 16mb.
3. Enter fastboot on ShieldTV using hardware method (above mentioned with A+B buttons)
4. Now quickly In Windroid click button Refresh - and status will be updated to Fastboot
5. Then again in Windroid - click Flash TWRP and accept safety questions.
6. After successful flash - reboot into TWRP (here you need USB mouse - so you can unplug Nvidia controller, and plug mouse)
7. In TWRP - Choose Install - navigate to external USB and select flashable zip (Lineage ROM as above)
8. Once booted - enable USB debugging again. (you could be prompted on the Shield TV to allow your PC as debugging device, if so, say yes)
Getting back to full stock ROM with TWRP and unlocked bootloader
1. Install Minimal ADB and Fastboot you downloaded
2. Extract boot.img, system.img and vendor.img from Nvidia stock recovery image (leave other files out), and place these files into Minimal ADB and Fastboot folder (it is in Program Files x86)
3. While on (in LineageOS) connect Shield TV with PC using male-to-male USB cable
4. Start Minimal ADB from destkop icon and run following commands (commands are only in italic)
adb devices (checks if device is online. Its a must to proceed)
adb reboot bootloader (reboots to fastboot)
fastboot flash boot boot.img
fastboot flash system system.img (will take longer as its a big file)
fastboot flash vendor vendor.img
Once finished - reboot to TWRP, plug in USB mouse (instead of controller) to navigate, and perform Factory Reset.
If you wish to root you can do it via TWRP (which is what I did, flashing SuperSU previosly downloaded to USB)
Thats it - you are back from the dead!
Post updated - with process how to go back to stock
Thanks for this guide. It saved my ass!
Hi phnikola
thank you very much for your super instructions.
With this tool I could bring my TV Shield 2017 back to life, which got stuck in the Boot Animation.
I thought it was a trash can case, also contacted NVIDIA support to see what they were saying.
So I can also send the possible to me for the purpose of repair saved, thanks to you!!!!!!!!!!!!!!!!!!
Greetings Akki
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