Database Info

[ROOT] Root NVidia Shield Tablet - Lollipop (also locked bootloader)

Hi all,
The original credits for the root go to SuperPichu for the following post: http://forum.xda-developers.com/shield-tablet/development/root-root-lollipop-t2945044
I simply "modified" his process, to make it even more "hassle free"
The process will wipe your data, so remember to backup it.
Besides, I'm not responsible if warranty voids or whatever. Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it. The fastboot unlock procedure has been taken directly by the NVidia Developer's site, so they actually expect the users to do that - but what you will do next, it's all your responsability
So, the overall procedure looks like:
Download&Install the "Mini" ADB/Fastboot from here: http://forum.xda-developers.com/showthread.php?p=42407269#post42407269 (remember to say yes to create the link on the desktop - it will be useful later)
Download&Install NVIDIA ADB Drivers from the official Nvidia site: http://developer.download.nvidia.com/mobile/shield/SHIELDTablet_WHQL_USB_driver.zip
Enable "Developer Mode" on the Nvidia Tablet (Settings -> About tablet -> Tap many times (5+) the "Build number" until the Developer Mode is activated
Developer Mode -> Enable USB Debugging
Copy the CWM image and SuperSU (rename it to supersu.zip) where you installed the Mini ADB/Fastboot (default: C:\Program Files\Minimal ADB and Fastboot)
Click the link created by the Mini ADB/Fastboot installation. It should open a DOS console already at the install folder.
(In the Windows console) Type "adb reboot bootloader"
From the rebooted tab, select "Load fastboot protocol" with Volume Keys and push the power switch to confirm
(In the Windows console) Type "fastboot oem unlock"
[ATTENTION: This step will wipe your device] Press the "Volume Down" button to select, with the "Power" button, the "Unlock bootloader" option on device
(In the Windows console) Type "fastboot flash recovery recovery.img"
On the tablet, select "recovery reboot"
You should be now on CWM. Simply select "install zip from file" -> install from sideload
In the console, type "adb sideload supersu.zip"
On CWM select "reboot system", CWM will ask to keep root => say yes
Enjoy your rooted tablet

Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.

wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
Well first off I havent had any issues with ota updates on CWM (took kitkat otas). Second, if you really don't want a custom recovery why not just obtain root then flash back the stock recovery??

wwjoshdew said:
Very nice! I wish there was a way to do this without installing custom recovery (so that we can accept ota updates). The Shield Portable is easier. Just unlock, and run the shield root image. It doesn't install Custom Recovery and is a very similar process to Chainfire's CF Auto Root methods.
Click to expand...
Click to collapse
To be honest with you, I haven't updated yet - but the OTA seems to work (i.e. it's currently saying that my Firmware is up-to-date, no errors). Just wait a couple of weeks (NVIDIA released a firmware update every month until now :good: ) and I'll let you know if it works
Btw, even if I loose the the root/CWM, it's not a great deal to install it again

FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app

An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Good to know. ?But we should be able to flash the ota zips via recovery and flash super su and possibly recovery (locked bootloaders, ota can overwrite recovery) just like we did to update to lolli. I usually see zips before I see the ota anyways.

sandrodjay said:
Just keep in mind that unlocking the FASTBOOT may void the warranty, as it will displayed when you will unlock it.
Click to expand...
Click to collapse
I have contacted NVIDIA today, asking steps to move back to Kitkat. I was given instructions to unlock the bootloader, and was assured it will not void the warranty. The assistant was being meticulous regarding this, since she asked around for her colleagues' advice before giving me the information.
So if I ever need to send in for warranty, all I have to do is reflash the factory image to get rid of the root and I'll be all set. If they make a fuss about me having an unlocked bootloader, I'll have a chat transcript to back me up. You guys may want to do the same too.

Thank you worked great!

An Droid said:
FYI, as soon as you root or modify a stock 5.x.x (Lollipop) image, you'll no longer be able to accept OTA anymore without first flashing back to stock (this applies to all devices - although you might be able to manually flash a new update) - I guess we'll find out once 5.0.1 is released for the Shield...
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Just took 5.0.1 (wasn't rooted or anything). So I was thinking if I flash the CWM, then do a stock backup, then proceeed to root I should be able to restore the backup when a new OTA comes out since it will be unrooted and stock. Then I can update, install recovery if needed, make another unrooted stock backup, for the next time then reroot, right?

Should work, but after restoring your stock backup you will need the stock Recovery too to update ota.

Hi
There is no need to flash the custom recovery if you don't want to. Just do a fastboot boot recovery <recovery.img>. I did that because i didn't want to change to another recovery.
After the reboot you will revert to stock recovery.
\Sorenjul

Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?

eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)

Help
Anyone else not able to download supersu.zip the page wont load

Granger77 said:
Anyone else not able to download supersu.zip the page wont load
Click to expand...
Click to collapse
NM sorry just went it opened instantly, maybe to much traffic

eurominican said:
Just to make sure, if you unlock the bootloader through "fastboot oem unlock" theres no way to reverse it in case need to send in for warranty repair, just like samsung devices with the stupid KNOX e-fuse? Or you can just revert everything (flash stock image/recovery and then fastboot oem lock)?
Click to expand...
Click to collapse
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!

root method LTE compatible
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.

Driver issues
I cant for the life of me get my win 7 64bit pc to install the drivers I've tried uninstall and going through manually with the naked driver method and it still says the device doesnt need it his tutorial is for win 8 am I missing something, I'm losing my mind over here I want this thing rooted so bad I'm losing sleep, and google has been useless

cyraxx84 said:
Ofcourse you can relock and go to 99.999% stock. 99.9% bacause after un- & relock there will be a little sign which shows nvidia that your bootloader was unlocked but you can't remove it. But as far as i know it doesn't void your warranty!
Click to expand...
Click to collapse
Ty for info and reply.
Bogdacutu said:
Unlocking the bootloader doesn't void the warranty (and even if it did, they would still be able to figure out if you've unlocked it before, even after relocking)
Click to expand...
Click to collapse
Got it. Thanks!
oleg77 said:
Hello,
I'm expecting a 32GB tablet (LTE/4G device) soon. Does your ROOT method work for the LTE model, or is it just for the 16GB (wifi only) device ?
Thank you.
Click to expand...
Click to collapse
Same here. I got mine on sale with the controlller. I suspect its the same on both wifi only and LTE version.

Can i follow this guide to unlock and root 5.0.1?

Rooting Samsung Galaxy J3 (2018)

Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre

ben480 said:
Hi everyone, I hope I am posting this in the correct section, and if not, can an admin move my post to the appropriate place? I am a geek with PC's but mobile is new to me and I would like to root my device which is a Samsung Galaxy J3 (2018) version. I cannot find info here after searching. Here is what I achieved thus far. I downloaded what I think is the firmware file named FirmwareX.Net_J337WVLS2ASC1_J337WOYV2ASC1_PCM_8.0_Full which has my model number SM-J337W and part of build number in the filename. My build number fully is R16NW.J337WVLS2ASC1. The IMEI is 359229091474959.
I downloaded latest odin tool and just about to download TWRP and my model is not in their list and thats where I'm at. Can someone confirm if this is the actual stock firmware rom, and if I am ready to proceed and some steps would be appreciated. I was told by Oneclickroot service that they have a different stock firmware, and just wanted me to pay for something I can probably do on my own, so I'm puzzled by their reply as I had a very hard time finding this firmware which seems to be the closest match. Has anyone here ever rooted this particular device and provide me a sure step by step way to root it? I do have the setting options OEM Unlock and USB Debugging if that helps.
Bernard St-Pierre
Click to expand...
Click to collapse
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk

Droidriven said:
The stock firmware that you downloaded is for your model number but you need to verify that it works with your mobile carrier. If you downloaded the correct firmware for your region and your carrier.
There isn't a TWRP recovery or a known rooting method for your model number. You'll have to try the various universal rooting apps and the various rooting programs for PC and hope of them works.
Or you might can extract the boot.img from the stock firmware that you downloaded then use Magisk on PC to create a modified boot.img then flash that modified boot.img via Odin then reboot the device and install the Magisk root manager app on the device to gain root. If your bootloader is locked, you won't be able to flash the modified boot.img, you'll have to find a method to unlock your bootloader, if one exists for your model number, android version and build number.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre

ben480 said:
Thank you for the reply Droidriven, I thankfully have the option in settings to unlock the bootloader called "OEM Unlock" unlike most other J3's who do not. So basically, you are saying that I can root this device with Magisk with your suggested Magisk method correct? Could you elaborate this method step by step?
Bernard St-Pierre
Click to expand...
Click to collapse
I'll explain the "OEM unlock" setting a bit first. The OEM unlock setting does not necessarily unlock your bootloader. On some devices, enabling this setting unlocks bootloader but on most devices it does not actually unlock the bootloader, it only puts the device in a state that the bootloader "can" be unlocked using some form of unlock method after enabling the setting. In these cases, the unlock method would not work without enabling OEM unlock setting before implementing the unlock method.
So, basically, what I'm saying is that even though you have the OEM unlock setting, this does not necessarily mean that your bootloader is unlocked just by toggling this setting, it may still be locked even after toggling the setting. You'll have to verify whether your bootloader is actually unlocked or not. Do some Google searches for:
"Check bootloader status on Samsung devices"
This should give you results to find a method to verify your bootloader status.
Once you have verified that your bootloader is unlocked, you can use the Magisk rooting method. Read the "Boot Image Patching" section in the link below, there are also several other guides all over the internet and videos on YouTube that give instructions on patching your boot.img. As for actually flashing the boot.img, you will be flashing it using Odin. Use 7zip to compress the patched boot.img into a .tar compressed file. When you flash the file using Odin, place .tar file in the AP slot in Odin.
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md
Sent from my LGL84VL using Tapatalk

Question about low level of android

Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !

oops I created another thread by editing my old one. Sorry.

isman77 said:
oops I created another thread by editing my old one. Sorry.
Click to expand...
Click to collapse
Hi
You are going to be flogged! [emoji6]
Envoyé de mon GM1913 en utilisant Tapatalk

isman77 said:
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
Click to expand...
Click to collapse
Just use MSMtool to reflash your phone. The links are in the guides section

isman77 said:
Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check).
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !
Click to expand...
Click to collapse
From what I've seen from a few people on here, nolimits doesn't really do anything useful. Debloat a few apps but everything else it doesn't isn't that good, apparently. I used it before and thought it was good. But I'm pretty sure I get better battery and performance on stock with a custom kernel and used something else to debloat.
Also, as some else suggested, MSM tool is great to get back to stock with everything proper.

Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?

isman77 said:
Thank you for your answers @Jinsuke32 and @GeekMcLeod
I would like to know if you can use MSM Tool with a locked bootloader and does this tool erase all data during flash?
Click to expand...
Click to collapse
Not sure if it can be used with locked bootloader. But it erases everything.

GeekMcLeod said:
Not sure if it can be used with locked bootloader. But it erases everything.
Click to expand...
Click to collapse
Ok, thanks for your quick response.

Root and Update

I got a 5 ii and will root soon after playing with stock for a few days. Currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification.
Would it be better to root / update by flashing per guide, or can I update the rom and root using the same method?

mtshure said:
I got a 5 ii and will root soon after playing with stock for a few days. Currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification.
Would it be better to root / update by flashing per guide, or can I update the rom and root using the same method?
Click to expand...
Click to collapse
Make the latest update normally if you're not rooted yet (Make a backup before continue)
Unlock your bootloader, and enable developer option & USB debugging
Download the latest firmware of your device with the tool xperifirm to have the flash_boot.sin
Use Unsin to make a patchable boot.img for Magisk and put it in your device
Download Magisk manager (use the beta or canary only)
Click "Select patch target file" and select the boot.img you just made
Then put the magisk_patched file to your computer and put your phone into fastboot mode
and flash magisk_patched both slots A&B
Reboot.

flyl0 said:
Make the latest update normally if you're not rooted yet (Make a backup before continue)
Unlock your bootloader, and enable developer option & USB debugging
Download the latest firmware of your device with the tool xperifirm to have the flash_boot.sin
Use Unsin to make a patchable boot.img for Magisk and put it in your device
Download Magisk manager (use the beta or canary only)
Click "Select patch target file" and select the boot.img you just made
Then put the magisk_patched file to your computer and put your phone into fastboot mode
and flash magisk_patched both slots A&B
Reboot.
Click to expand...
Click to collapse
I asked because I didn't see any post saying that the phone can be rooted using the same method on 58.0.A.28.51 firmware. Are you saying the same method will work on the new firmware version?

mtshure said:
I asked because I didn't see any post saying that the phone can be rooted using the same method on 58.0.A.28.51 firmware. Are you saying the same method will work on the new firmware version?
Click to expand...
Click to collapse
if you take the boot.sin file and create a patchable img of each updates and patch this file with magisk after flashing the update with newflasher then yes. Just don't forget to remove userdata.sin & persist.sin to keep your data.
The method to root will never change.

flyl0 said:
if you take the boot.sin file and create a patchable img of each updates and patch this file with magisk after flashing the update with newflasher then yes. Just don't forget to remove userdata.sin & persist.sin to keep your data.
The method to root will never change.
Click to expand...
Click to collapse
I haven't rooted my device yet, but given that the method to root is the same, it looks like it will be better to update first then root because it will reduce the number of steps needed. Thank you for the reply.

mtshure said:
I got a 5 ii and will root soon after playing with stock for a few days. Currently on 58.0.A.10.3 and received 58 0.A.28.51 update notification.
Would it be better to root / update by flashing per guide, or can I update the rom and root using the same method?
Click to expand...
Click to collapse
I am having some difficulties rooting the phone. I have the bootloader unlock code, but each time I try to unlock the bootloader (https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/) it doesn't work. I am able to get into recovery mode on the phone, but plugging it i, and running "fasboot devices" yields nothing via the Android SDK. I have another thread open, and am willing to give you a $100 USD gift card for the assistance! "
"Sony Xperia 5 II XQ-AS62 root"
Thank You!

TCL A503DL Bootloader Unlock

This TCL A503DL phone comes with a Tracfone loaded android 8.1. Has anyone unlocked the bootloder?
I only saw one option "jump to camera" under Settings/Gesture. Is this because of a hardware limitation, or Tracfone's programming that disable the other gestures?
TIA,
Furb

On the TCL A509DL model I went into the settings, then I scrolled to system, then I scrolled to about phone. Next scroll to build number and tap on it 7 times to unlock development mode. Once in development mode scroll down to unlock bootloader.

furballi said:
This TCL A503DL phone comes with a Tracfone loaded android 8.1. Has anyone unlocked the bootloder?
I only saw one option "jump to camera" under Settings/Gesture. Is this because of a hardware limitation, or Tracfone's programming that disable the other gestures?
TIA,
Furb
Click to expand...
Click to collapse
On the TCL A509DL model I went into the settings, then I scrolled to system, then I scrolled to about phone. Next scroll to build number and tap on it 7 times to unlock development mode. Once in development mode scroll down to unlock bootloader.

Andrecastertroy said:
On the TCL A509DL model I went into the settings, then I scrolled to system, then I scrolled to about phone. Next scroll to build number and tap on it 7 times to unlock development mode. Once in development mode scroll down to unlock bootloader.
Click to expand...
Click to collapse
hey is there any way we could teamview and let me make a dump of your a509dl? I bricked mine and really need a dump to fix it.

r1pp3d2 said:
hey is there any way we could teamview and let me make a dump of your a509dl? I bricked mine and really need a dump to fix it.
Click to expand...
Click to collapse
I need the dumps too!!

iamx51 said:
I need the dumps too!!
Click to expand...
Click to collapse
i swear we will find a dump one day lol

furballi said:
This TCL A503DL phone comes with a Tracfone loaded android 8.1. Has anyone unlocked the bootloder?
I only saw one option "jump to camera" under Settings/Gesture. Is this because of a hardware limitation, or Tracfone's programming that disable the other gestures?
TIA,
Furb
Click to expand...
Click to collapse
To dump all the firmware/flash files & unlock the bootloader in order to root the a503dl I used the live cd from https://github.com/bkerler/mtkclient
Then after rebooting the phone and enabling usb debugging I used adb to copy the original boot.img over to the phone's internal storage and install the latest version of magisk.
Next on the phone I used magisk to patch but not install the boot.img.
After that I went back to the computer and copied the newly created magisk patched boot.img from my phone to my computer.
Then I used the mtkclient live iso to write the newly created magisk patched boot.img to the A503DL flash/firmware and rebooted the phone to go through the usual steps to make sure magisk is fully installed and updated etc.
Then I used the Android Kitchen toolkit for windows to port twrp recovery to the A503DL using this guide https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
I have uploaded the A503DL ported unofficial twrp recovery image here.
UNOFFICIAL a503dl twrp.7z
drive.google.com
Here's a full stock dump for the A503DL.
A503DL Full Stock Dump.7z
drive.google.com
Here's a full prerooted TWRP backup.
2022-11-27--21-09-50_A503DL_Root TWRP Backup.zip
drive.google.com
Finally you can get a mtkclient backup of the full firmware prerooted with twrp installed here. This is probably the easiest way to get root and twrp on this phone until I work out the kinks with the recovery.
a503dl root w twrp mtkclient dump.7z
drive.google.com
If your phone says it can't boot securely or something after flashing it you need to reboot in bootloader and unlock the bootloader with mtkclient.
Please forgive me if this is not the correct place to share this but o.p. asked and I had the answer.