Develop Bugs

[Q] Unrootable?

i am running BML4 and wanted to root the phone, i tried all sorts of methods, saferoot, towelroot, impactor, all failed so i just flashed a custom recovery and installed supersu 2.00 from a flashable zip, boot the phone and adb shell in, type su, it returns me to $, every time, super su sees no problem and the su binary and daemonsu are in ./system/xbin but still i cannot get root access, have samsung finally won or something?
i also tried flashing a custom rom that already rooted, but any roms just bootloop as nothing seems to be based on bml4 and older stuff just doesnt seem to agree with this bootloader, any attempt to flash to an earlier version results in the bootloader just blocking boot entirely (thanks for that samsung, i really needed you to protect me from doing what i want with my device)
does anyone know a way to root this thing or should i just give up

Try installing BusyBox
you do not need busy box to have root.
But many root apps as well as settings in custom roms use busybox to run the scripts that make them work. so while you can root without busybox you are very limited as to what you can do with it.
so while you dont need it to have the phone rooted. its still prety much needed to take advantage of that rooting
Click to expand...
Click to collapse
from Here

I am running rooted BML4 without any issues. I have rooted using this post:
http://forum.xda-developers.com/showthread.php?t=2364980

[ROM] Nvidia Factory Stock ROOTED ROMs

Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-developer-os-images

For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.

Hi there,
my shield is on stock now with several apps on it.
How can I flash without losing my data? Is it enough to NOT flash the userdata?
THX
Chaos

Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos

BillTheCat said:
Nvidia makes pre-rooted stock ROMs available via their website. You'll have to register for access, but it makes life lots easier this way. I don't know if this factory pre-rooted ROM supports OTAs, and if it does accept an OTA if it will cause loss of Root, but if you have access to the Developer site, you can always flash another pre-rooted ROM version as they become available.
https://developer.nvidia.com/shield-open-source
Click to expand...
Click to collapse
I have a question, where do you find pre-root load in below link?
I only find Open source and recovery image.
you mean to modify Open source and build pre-root load?
https://developer.nvidia.com/shield-open-source

https://developer.nvidia.com/shield-developer-os-images

BillTheCat said:
https://developer.nvidia.com/shield-developer-os-images
Click to expand...
Click to collapse
thanks

hardwarechaos said:
Hi there,
gonna answer myself.
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
After that I installed the system as suggested by nvidia and restored my backup.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image.
THX
Chaos
Click to expand...
Click to collapse
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.

hardwarechaos said:
As my bootloader was not unlocked the system got wiped anyways while unlocking it.
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
I ended up installing root via twrp, no imho no real advantage using the developer image
Click to expand...
Click to collapse
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu

Hi
Tyler27 said:
Have you installed SuperSu and tested it with various apps?
Im debating installing this image instead of starting all over to root the "real" way.
Click to expand...
Click to collapse
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
IMHO if you have adb root there should be a way to install it via adb too, but I could not find one and didn't want to mess around with installing the SuperSU files manually.
THX
Chaos

hardwarechaos said:
After I saw that the developer image was root for adb only, I flashed twrp recovery and installed SuperSU via twrp.
So right now I don't see any benefit over the "standard image with root".
Click to expand...
Click to collapse
Agreed - turns out the Dev images are no real benefit. I found that installing TWRP, rebooting the bootloader, entering recovery and then flashing SuperSU works like a champ.

Anyone else having trouble flashing system and userdata? Keeps saying FAILED (Remote: data too large)

BillTheCat said:
For those who prefer a more stock system, but want some measure of control, I wanted to pass along that I was able to install Xposed, Xprivacy, TiBu and ES File Explorer to this ROM. I had to download and reapply SuperSU and allow it to relaunch/install via TWRP, but all's well.
I did this by flashing Zulu's full Android ROM first, installing some utilities, then flashing the Nvidia OEM system partition on top of it. Some apps appear on the SATV screen (ES, Xprivacy) others do not (TiBu, Xposed installer) but I'm sure there's a way to get the icons to appear.
In any event, for those who prefer the stock Nvidia look & feel, along with their installed apps, this is at least one way to get it done.
Click to expand...
Click to collapse
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?

jweaks said:
I'm on Zulu full with Amazon video working. Any idea if I go to stock rooted will that knock out the Amazon video?
Click to expand...
Click to collapse
Yes it will kill amazon video.

BillTheCat said:
Ditto here. Now that you've posted, it confirms what I experienced. At first, I thought I had made a mistake.
Here's what I did.
Unlock bootloader (fastboot oem unlock - easy enough!)
Flash the Nvidia 2.1 ROM to ensure stock condition (I used the 'rooted' Dev edition, but I doubt it matters)
Reboot bootloader
Flash TWRP
Reboot bootloader (to reinitialize partitions)
Flash SuperSU, Xposed
Reboot into system, sideload ES File Explorer, Xprivacy, TiBu
Click to expand...
Click to collapse
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill

dillfever said:
how did you flash TWRP to Nvidia through adb?? or through recovery on the Nvidia.....been reading to much can't comprehend...thanks dill
Click to expand...
Click to collapse
can close this got er all done.......dill

hardwarechaos said:
Concerning the root: From what I could see it is rooted for adb only. So apps don't gain root.
Click to expand...
Click to collapse
Hello,
Same result for me.
I've just received my Shield, I've followed the instructions given on the developers web page. I have an up-to-date 3.0.0 version, but applications don't have the root authorisations (tested with ES File Explorer).
I think I'll use the TWRP method...

i download 3.0 rooted version it came a zip with all files on it on nvidia shield.com tutorial said just ento bootloader and type comand flash-all.bat and gualahhh! but try like 1000 times and always said null error message and force close adb
can some one tell what im doing wrong please and thanks people!
bye the way gamestop its selling shield tv for 100bucks so for those who want another its the right time to get one

Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.

dismissthesky said:
Not trying to start drama here at all, but what steps would I need to go through in order to get off of Zulu's full Android 5.1 and on to this? I see he's gone through and deleted all of the posts detailing the process of how to install his ROMs so now I don't even know the steps that I took back in August to install that ROM in the first place. My Shield is having a very strange problem where it stutters hard every 60 seconds or so and I want to go back to stock or something vaguely stock just in case I have to RMA this thing.
Click to expand...
Click to collapse
to remove zulu rom this is easy.
just go to nvidia site and get the complete factory images for your shield.
it will come with a guide on how to flash your shield with them.
it will delete everything in your shield and it will be stock like brand new.
then you can root it if you want or install a different rom.

Help With Root

I'm a little lost on Root for the Pixel XL. I am currently running unlocked with Screw'd ROM - 3.1.2-****ery-20170712-1454. This is a BETA, but has been running really smooth for the last 2 days.
Security Patch Level - July 5, 2017
Vendor - NJH47D
Last time I tried to apply root while running PureNexus the phone continued to boot loop and I had to eventually flashall.bat and start over.
1. What version of SuperSU should I be flashing? The latest and newest or is there other versions that work better?
2. What are the correct steps? Is wipe cache/dalvik necessary before? Do I need to install anything on the phone beforehand?
Boot to TWRP, Flash SuperSU, Reboot? Easy as that?
I see this version being talked about a lot - SR3-SuperSU-v2.79-SR320170114223742.zip, but it isn't the latest available that I can see. The SuperSU thread states to install the latest version and using google brings me to many versions of SuperSU.
Lastly, after rooting will apps like SnapChat work? If not how to you bypass this?

So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?

jws86 said:
So I just found some information after searching more. Some of it is dated. I currently have twrp-pixel-installer-marlin-3.1.0-0RC2.zip version for TWRP installed.
Is RC1 needed for root, and with what SuperSU version. Or which combination of RC2 and SuperSU work together?
Click to expand...
Click to collapse
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.

sakumaxp said:
When I was rooted I initially was using RC1, I think my supersu was V2.8? And no Snapchat, Pokemon go, and Android pay, etc, will not work. So a little work around for Snapchat, you need to log in first then flash supersu, or just go with magisk and enable magisk hide to make life easier.
Click to expand...
Click to collapse
Is there a guide to Root with Magisk somewhere floating around?

jws86 said:
Is there a guide to Root with Magisk somewhere floating around?
Click to expand...
Click to collapse
I believe it's the same as when you flash supersu, don't quote me on that

sakumaxp said:
I believe it's the same as when you flash supersu, don't quote me on that
Click to expand...
Click to collapse
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?

jws86 said:
Yeah I found the guide. It seems I need to flash stock image first before. So Magisk gives you the ability to root first, then download apps such as snapchat and still login if you use magisk hide?
Click to expand...
Click to collapse
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet

sakumaxp said:
Correct, downloading isn't a problem, but it'll just prevent you from logging in since supersu, trips safetynet
Click to expand...
Click to collapse
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?

jws86 said:
I read through this thread: https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
Seems pretty straightforward, however currently I have a ROM installed I'm really liking. To do this I would have to flash back to stock image, then go through the root process. My question would be after rooting, if I went to flash Screw'd again, doesn't it wipe everything and I would lose root again, then just have to flash it after the ROM?
Click to expand...
Click to collapse
Myself I've never been on screwd before, I would assume so, but in my experience the pixel XL is more complicated than my previous phones

If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.

jhs39 said:
If you just want root you shouldn't need to flash the stock image again. You would need to do that if you wanted to flash a custom kernel but not for root. You need to download the modified version of Magisk for the Pixel XL. The official version doesn't work on the Pixels. I'm not currently rooted as I went back to stock but I was using Magisk. At that time the latest version wasn't stable but it might be fixed now. You need to boot into fastboot TWRP, flash the Magisk zip, flash the TWRP zip and then boot up. After you are booted up you install the Magisk Manager app. The tricky thing is installing the right version of Magisk Manager that works properly with the unofficial build of Magisk that you are using. You can get more information in the Resurrection Remix rom thread which for some reason is the official place where the modified version of Magisk is hosted if you can't find good info about which combination of unofficial Magisk and Magisk Manager you should be using. Also when I used Magisk you needed to enable core only mode for it to pass Safety Net but that may no longer be the case. You should be able to find the most up to date info either in the thread you cited or the RR rom thread. Just remember that official builds of Magisk do not work on the Pixel. You need to stick with one of the unofficial builds.
Click to expand...
Click to collapse
I think I got which versions of magisk and magisk manager I need to use from the other thread I had posted earlier. This helps to clear some things up for me though. I have both the .apk and the zip on my phone now. Getting a bit of a charge and I guess I'll go ahead and try it.

It worked, I'm officially rooted .Thanks for the help!

jws86 said:
It worked, I'm officially rooted .Thanks for the help!
Click to expand...
Click to collapse
Cool.

Has anyone rooted using Kingroot?

I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?

GroovinChip said:
I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?
Click to expand...
Click to collapse
Why use kingroot? Remove the first step and you basically have hot to flash su..

pcriz said:
Why use kingroot? Remove the first step and you basically have hot to flash su..
Click to expand...
Click to collapse
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Sent from my Google Pixel XL using XDA Labs

GroovinChip said:
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Click to expand...
Click to collapse
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.

pcriz said:
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.
Click to expand...
Click to collapse
This makes sense. Thanks
Sent from my Google Pixel XL using XDA Labs

Even if it did work it wouldn't work the way you are describing. King Root basically acts like malware and refuses to give root privileges to any app that interferes with its functioning. Adaway won't work with King Root because adware is part of the King Root program. You also wouldn't be able to install SU while King Root is on your phone. King Root will actively prevent you from installing any other root program. People used to be able to do what you describe but King Root was updated to prevent you from installing SU.

Wich root methods do you prefer for the Xiami 5s?

After I switched to this phone, I miss the root possibilities, I miss playing around with ROMs (I killed my old, really old phone #android 4.3, but it was fun).
Which one is the best option? (I don't want to kill this phone).
- The one click rootapps on android?
+ Kingroot
+ Kingoroot
+ Oneclickroot
+ Other...
(And after installing one of them, I will install SuperSU)
- The one click root applications on the pc?
+ iSkysoft toolbox
+ Kingo
+ Other...
- Installing a flash zip with my pc?
- Other options?
I used some of them with my old phones. Which one you prefer?

The best method is to unlock your bootloader, install TWRP and than flash Magisk

You should only use Magisk (downloaded from the official XDA thread, and flashed via TWRP), and nothing else. Maybe there are some new, opensource root managers but Magisk is the best ATM, and you should stay away from the new versions of SuperSU, a chinese company bought it from Chainfire and now they developing it.

iamnotstanley said:
You should only use Magisk (downloaded from the official XDA thread, and flashed via TWRP), and nothing else. Maybe there are some new, opensource root managers but Magisk is the best ATM, and you should stay away from the new versions of SuperSU, a chinese company bought it from Chainfire and now they developing it.
Click to expand...
Click to collapse
Really thanks! I didn't know that SuperSu was taken over.

first unlock the bootloader, then install twrp (i used adb with my computer) and finally flash magisk.
i tried loads of one click root app and none worked.