I have a Sprint L720 GS4 that was originally rooted and running CM 10.1 off of the official nightlies. I flashed the new CM 10.2 build for jfltespr posted here : http://forum.xda-developers.com/showthread.php?t=2383143
Aside from a few apps acting weird because of the new way Android 4.3 handles notifications, everything runs pretty smooth. Biggest issue is that I lost root after upgrading. (Focal is bada**, in case anyone was wondering lol. I love having Photosphere on a non-nexus device)
The research I have done trying to solve this says all I should need to do is flash Chainfire's newest SuperSU app (v1.43 at the time of this post) and bingo, you will have root access again because version 1.43 gets around whatever issue Android 4.3 has with root. I have flashed this via CWM recovery and get the error "There is no custom binary installed and SuperSU can't install it, this is a problem. If you just upgraded to 4.3 you must manually re-root." when opening the SuperSU app after the phone reboots, and no root apps like Root Explorer or Adaway work anymore.
I have wiped data, cache, davlik, fixed permissions, re-flashed the CM 10.2 ROM and the 4.3 Gapps, then the re-flashed SuperSU app, fixed permissions again, and still nothing, tried several variations of the above process for several hours. As per procedure from Chainfire's G+ posts on how to do this, I did select 'No' when asked if I wanted to disable stock recovery flash as CWM is rebooting the phone. What am I missing?
BTW, I have no access to computer/laptop ATM, so if there is a way to do this without having to use ODIN or some other rooting tool, that would be great.
Verilin said:
I have a Sprint L720 GS4 that was originally rooted and running CM 10.1 off of the official nightlies. I flashed the new CM 10.2 build for jfltespr posted here : http://forum.xda-developers.com/showthread.php?t=2383143
Aside from a few apps acting weird because of the new way Android 4.3 handles notifications, everything runs pretty smooth. Biggest issue is that I lost root after upgrading. (Focal is bada**, in case anyone was wondering lol. I love having Photosphere on a non-nexus device)
The research I have done trying to solve this says all I should need to do is flash Chainfire's newest SuperSU app (v1.43 at the time of this post) and bingo, you will have root access again because version 1.43 gets around whatever issue Android 4.3 has with root. I have flashed this via CWM recovery and get the error "There is no custom binary installed and SuperSU can't install it, this is a problem. If you just upgraded to 4.3 you must manually re-root." when opening the SuperSU app after the phone reboots, and no root apps like Root Explorer or Adaway work anymore.
I have wiped data, cache, davlik, fixed permissions, re-flashed the CM 10.2 ROM and the 4.3 Gapps, then the re-flashed SuperSU app, fixed permissions again, and still nothing, tried several variations of the above process for several hours. As per procedure from Chainfire's G+ posts on how to do this, I did select 'No' when asked if I wanted to disable stock recovery flash as CWM is rebooting the phone. What am I missing?
BTW, I have no access to computer/laptop ATM, so if there is a way to do this without having to use ODIN or some other rooting tool, that would be great.
Click to expand...
Click to collapse
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
nicotheandroidguy said:
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
So did that, went to superuser in the settings app, made sure apps had access, made sure prompt was on, everything else looked OK, rebooted. Still getting the 'No custom binary installed' thing with SuperSu and have no root access. Any other ideas?
Verilin said:
So did that, went to superuser in the settings app, made sure apps had access, made sure prompt was on, everything else looked OK, rebooted. Still getting the 'No custom binary installed' thing with SuperSu and have no root access. Any other ideas?
Click to expand...
Click to collapse
Reflash the rom and Gapps you won't loose any apps make sure you don't have any trace of super su then do what I said in the last post.
Sent from my SPH-L720 using xda premium
Couldn't get the supersu app to uninstall so I did a data wipe to get rid of it, re flashed ROM and gapps, went into superuser settings and set them as above. Still no root access via root checker, other root apps also don't work. Any other ideas?
Same issue on Pac-rom 4.3.
Anyone have any more thoughs on this? I know there's a huge movement that thinks Root isn't really needed anymore, but I do it for Adaway and being able to move files I download from internal to SD Card (which file explorers won't do without root for some reason), not to mention having CM on my phone. Lol, I almost can't wrap my head around the fact that I have a custom ROM and a custom recovery but no Root access.
Verilin said:
Anyone have any more thoughs on this? I know there's a huge movement that thinks Root isn't really needed anymore, but I do it for Adaway and being able to move files I download from internal to SD Card (which file explorers won't do without root for some reason), not to mention having CM on my phone. Lol, I almost can't wrap my head around the fact that I have a custom ROM and a custom recovery but no Root access.
Click to expand...
Click to collapse
ES File Explorer will accomplish this file moving without root.
Are you using Odin?
No computer... Answers that.
Do you have goo manager?
If no DOWNLOAD IT.
You may have to flash the recovery file (again. You have to do it two different ways to achieve root) through goo manager.
Goo> Menu> Install Custom Recovery it will ask you if you have custom installed. Select yes and it will freeze up for about 10 seconds and USUALLY reboot into recovery and voila, full and proper root achieved.
Source: I dealt with this for almost 2 days and accidentally figured it out. None of my super apps would work. SuperSU, SuperSU Elite, Superuser, nada.
Sent from my SPH-L720 using Tapatalk 2
Thanks for the suggestion. Downloaded GooManager. The path you specified doesn't exist. It is GooManager>Menu>settings>install OpenRecovreyScript. I tried that path anyway in case you had just accidentially misphrased it. It downloaded a TWRP file, and then did nothing else, didn't reboot. I tried rebooting to recovery directly through the main menu in GooManager, but it gives an error because I don't have root access. I have to manually reboot to recovery. Thankfully (I prefer CWM to TWRP) it didn't install TWRP. I still have CWM and nothing else has changed, still no root access.
Using a file manager when trying to move something from the downloads folder on my internal memory to the SD Card, it says operation failed every time, and in GooManager, I cannot access my SD Card files, only internal memory. I tried to re-flash the ROM via GooManager in case that would get results, but the /extsdcard is not listed and I cannot access the root folder to get to it.
I will try just about any suggestion that anyone throws up here because I am at the end of my rope with this, but doing anything via the settings or through an app is likely not going to work because you have to have root access for these things to function to start with in most cases. I had a similar issue when I first rooted my S4. I carelessly accepted the OTA update on initial activation without thinking about it, then when I went to root it I found out that update added a SETUID RESTRICTION to the kernal, essentially changing how Superuser apps interact with the kernal. I had to track down the original kernal and flash that to remove the SETUID RESTRICTION so SuperUser would work. I have a feeling the solution to this will be along those lines, but in hours of researching the only thing I can find to do is 'Flash SuperSU, it will re-root your phone'.
Is there anyone else that has had this issue with the unofficial nightlies of CM 10.2 linked in the OP where the Chainfire SuperSU workaround for re-rooting doesn't work?
I'm not entirely sure what I did, but my Super SU is working properly now.
Last thing I did was flash a version of Super SU I knew worked pre-4.3 (https://dl.dropboxusercontent.com/s...UHFu_xV9MFXYEd9A8ZltJ8l6RjX2l2QtUcGFlWWA&dl=1). I opened it and it gave me the regular error, so I gave up and decided I'd wait a few days. However, I just checked this thread to see if any other solutions were available, and someone mentioned GooManager, so I opened it and it asked for SU permission, and it was granted. I then opened Super SU and noticed it works properly now.
Sorry if this doesn't help.
PwnCloud said:
I'm not entirely sure what I did, but my Super SU is working properly now.
Last thing I did was flash a version of Super SU I knew worked pre-4.3 (https://dl.dropboxusercontent.com/s...UHFu_xV9MFXYEd9A8ZltJ8l6RjX2l2QtUcGFlWWA&dl=1). I opened it and it gave me the regular error, so I gave up and decided I'd wait a few days. However, I just checked this thread to see if any other solutions were available, and someone mentioned GooManager, so I opened it and it asked for SU permission, and it was granted. I then opened Super SU and noticed it works properly now.
Sorry if this doesn't help.
Click to expand...
Click to collapse
I tried an earlier version of SuperSU, sadly no dice.
nicotheandroidguy said:
Roit is now in the setting app under superuser make sure prompt is on then reboot and you'll be fine. It worked for me.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
So I continued to play with this, and I FINALLY got it to work. The thing is that you actually have to turn it on in two places, in superuser and developer options as well. I had tried that before, but it hadn't worked I think because I also had the SuperSU app on there. so steps I took when I got it to work:
1) Wiped data/cache/davlik (again, uggh, must have been my 7th data wipe in 3 days)
2) Reflashed ROM and Gapps
3) Wiped cache and davlik a second time
4) Fixed permissions
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
I verified root access after that with root checker. While in developer options, I also turned on USB Debugging, I doubt that had an effect, just noting for thoroughness.
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
zxhian said:
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Ah yes, I realized I did that too, didn't think it had an effect though.
zxhian said:
this did it for me:
5) When phone rebooted and initial setup was finished, go into settings>superuser>menu>settings>superuser access>apps and adb
6) Activate developer options (tap 7 times on build number in about phone if anyone is still in the dark about that)
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Worked for me
zxhian said:
this did it for me:
7) Settings>developer options>root access>apps and adb
Click to expand...
Click to collapse
Since I did no data wipe, this was all I had to do - switching from root access "apps" to "apps & adb" Thanks for the hint :good:
Fixing root for me was just going into recovery and fix permissions then reboot and boom I got root
I'm on PACman 4.3 and I don't manage to have a working SuperSU...
I flashed it twice from TWRP (SuperSU update v1.65).
I put apps & ADB in SuperUser menu + in Developer Options
I fixed permissions via TWRP
It doesn't still work... When I open TricksterMOD a pop up shows up "Trickster Mod needs a rooted device and root access"...
I had a few wks a while back where I was computer-less. I used a friend's pc and slapped Odin and a few unzipped rom tars, cf-auto root. ..etc on a sdcard.. I did this so that if I had an issue I could quickly fix my phone from anywhere on anyone's pc.. Just a suggestion for anyone who doesn't have access to a computer...?
Sent from my SPH-L720 using Tapatalk 4
Related
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?
So I was having a similar problem to the users in this thread
http://forum.xda-developers.com/showthread.php?t=2434063
and I did a full unroot as someone suggested, and the update went through and updated my phone finally. I go back and flash SuperSU (1.51), and CWM says that it successfully flashed the zip, but there is no SuperSU app or root access on my phone. Any ideas on how I can fix this?
Try flashing SU v1.60. You are flashing an outdated version.
Version 1.55 is already reworked. Maybe flashing an updated SU will work for you.
Send from my Nexus 4
Nope. No go. I tried flashing 1.55 and 1.60, but neither create the SU app even though CWM says it flashed correctly. Maybe I will try installing a different recovery.
Edit: New recovery didn't work either.
MildewMan said:
Nope. No go. I tried flashing 1.55 and 1.60, but neither create the SU app even though CWM says it flashed correctly. Maybe I will try installing a different recovery.
Edit: New recovery didn't work either.
Click to expand...
Click to collapse
Make sure you have USB debugging enabled in settings menu. Same happened to me today and it turns out that I only found out that this had become unticked when I flashed v1.55 and tried to run titanium backup and it gave me a message that USB debugging was not enabled. Ticked that on and reflashed and viola! SuperSU sat grinning away in my app drawer.
I can't explain why it had become unticked in the first place. I suspect it was when I uninstalled SuperSU initially by doing full cleanup method in SuperSU settings menu.
Im on Purity Rom latest with twrp 2.6.2.0
carlos67 said:
Make sure you have USB debugging enabled in settings menu. Same happened to me today and it turns out that I only found out that this had become unticked when I flashed v1.55 and tried to run titanium backup and it gave me a message that USB debugging was not enabled. Ticked that on and reflashed and viola! SuperSU sat grinning away in my app drawer.
I can't explain why it had become unticked in the first place. I suspect it was when I uninstalled SuperSU initially by doing full cleanup method in SuperSU settings menu.
Im on Purity Rom latest with twrp 2.6.2.0
Click to expand...
Click to collapse
Yeah I noticed it had become unticked when I tried to use adb to install the new recovery, but turning it back on didn't help either. :/
MildewMan said:
Yeah I noticed it had become unticked when I tried to use adb to install the new recovery, but turning it back on didn't help either. :/
Click to expand...
Click to collapse
Update: I just went to the play store and downloaded SuperSU, and it installed correctly and added the app to the drawer if anyone else has this issue. Opened up Titanium backup, and it was able to get root access.
Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help
First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ
I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade
I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Easily got my root back using Wugfresh toolkit.
Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.
[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.
[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.
If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app
I actually searched this in depth and much to my surprise, I didn't find much. Odd.
I've got an ATT GS4 with the NC1 loaded. I'm rooted and ready to go after downloading a few files following instructions:
Code:
Files you will need on ExtSdCard before starting:
-- Safestrap-JFLTE-3.72-kk-B01.apk from here
-- ROM Install Zip (check ROM notes... may need to replace updater-script)
-- ATT_NC1_Modules.zip from here
-- UPDATE-SuperSU-v2.00.zip from here
ALL 4.4.2 ROM installs starting with rooted NC1:
0. Root and install safestrap v3.72
1. Copy remaining files above to extSdCard
2. Reboot into Safestrap Recovery
3. Wipe... Advanced Wipe... everything except extSdCard
4. Install... 4.4.2 ROM
5. Install... ATT_NC1_Modules.zip (to fix wifi)
6. Install... UPDATE-SuperSU-v2.00.zip (to keep root)
7. Reboot
8. Check APN settings and configure if necessary
I never got to the end because when I installed Safestrap, I chose "install recovery" and it went all the way to 100% and said the install was a success but for "state" it says "not installed".
Not sure what's going on. I do note that on the SafeStrap thread, it only mentions NB1 but I assumed that was the same as NC1 functionally.
I have SuperSU installed and Safestrap is listed in the apps section.
Like I said, I'm surprised I didn't find more info on this upon my searching.
Ive tried:
uninstall safestrap and superSU
reinstall
reboot multiple times in-between
Something odd that happened after I uninstalled superSU - I resbooted and what came up was a warning screen with yellow writing that warned me about installing alternative OS's. It asked if I wanted to install an alternative OS and I chose "NO" and it booted normally. Not sure where that screen came from or what it was. I never saw it again.
You need to set selinux to permissive mode and then you should be able to install safestrap recovery. Use selinuxmodechanger app for that
what's up with this software? anyone got 3.72b working on NB1?
burgertime78 said:
I actually searched this in depth and much to my surprise, I didn't find much. Odd.
I've got an ATT GS4 with the NC1 loaded. I'm rooted and ready to go after downloading a few files following instructions:
Code:
Files you will need on ExtSdCard before starting:
-- Safestrap-JFLTE-3.72-kk-B01.apk from here
-- ROM Install Zip (check ROM notes... may need to replace updater-script)
-- ATT_NC1_Modules.zip from here
-- UPDATE-SuperSU-v2.00.zip from here
ALL 4.4.2 ROM installs starting with rooted NC1:
0. Root and install safestrap v3.72
1. Copy remaining files above to extSdCard
2. Reboot into Safestrap Recovery
3. Wipe... Advanced Wipe... everything except extSdCard
4. Install... 4.4.2 ROM
5. Install... ATT_NC1_Modules.zip (to fix wifi)
6. Install... UPDATE-SuperSU-v2.00.zip (to keep root)
7. Reboot
8. Check APN settings and configure if necessary
I never got to the end because when I installed Safestrap, I chose "install recovery" and it went all the way to 100% and said the install was a success but for "state" it says "not installed".
Not sure what's going on. I do note that on the SafeStrap thread, it only mentions NB1 but I assumed that was the same as NC1 functionally.
I have SuperSU installed and Safestrap is listed in the apps section.
Like I said, I'm surprised I didn't find more info on this upon my searching.
Ive tried:
uninstall safestrap and superSU
reinstall
reboot multiple times in-between
Something odd that happened after I uninstalled superSU - I resbooted and what came up was a warning screen with yellow writing that warned me about installing alternative OS's. It asked if I wanted to install an alternative OS and I chose "NO" and it booted normally. Not sure where that screen came from or what it was. I never saw it again.
Click to expand...
Click to collapse
I've tried everything to load a rom onto this thing even what op replied and still nothing. My version of safestrap is 3.72 beta with NB1 4.4.2
I'm about to suck it up and stay on stock att witch i hate cause I can't use none of my tmobile features oh well. If anyone's got this working please, please let up know step by step how it was done.
Wanabedev83 said:
I've tried everything to load a rom onto this thing even what op replied and still nothing. My version of safestrap is 3.72 beta with NB1 4.4.2
I'm about to suck it up and stay on stock att witch i hate cause I can't use none of my tmobile features oh well. If anyone's got this working please, please let up know step by step how it was done.
Click to expand...
Click to collapse
That worked like a charm - the SELinux change app.
Thanks JmJoyas!
burgertime78 said:
That worked like a charm - the SELinux change app.
Thanks JmJoyas!
Click to expand...
Click to collapse
how are you loading the the roms? Is it threw one of the numbered slots or in the stock one? I don't wanna mess too much with the stock one but if it's the only one that work's then I guess i might give it a try.
Wanabedev83 said:
how are you loading the the roms? Is it threw one of the numbered slots or in the stock one? I don't wanna mess too much with the stock one but if it's the only one that work's then I guess i might give it a try.
Click to expand...
Click to collapse
At the time of this, I had not installed any roms. This thread was because I could not get safestrap installed.
burgertime78 said:
At the time of this, I had not installed any roms. This thread was because I could not get safestrap installed.
Click to expand...
Click to collapse
oh okay, cool. Do you know of a thread that you might link me to where they might be discussing that? If so link me if you can please.
Wanabedev83 said:
oh okay, cool. Do you know of a thread that you might link me to where they might be discussing that? If so link me if you can please.
Click to expand...
Click to collapse
Not sure of a thread for that. However, last night I installed over top of my stock slot. Apparently, KitKat does not allow flashing to "rom slot 1-4" so, I just did a full backup in safe strap, then wiped the stock slot and installed over top of it. worked fine.
Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
kenmacker said:
Downloaded and it's says shield portable android 5.1 not supported...
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
You need to turn on USB Debugging, and then run the app.
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
work great
thanks
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
kenmacker said:
USB debugging is now turned on but it says root access is unavailable
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Look if you have your SHILD's bootloader unlocked, that may be causing the problem.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
I wanted a full restore/clean version of the ROM without waiting for the factory image to be updated.
I flashed the 101 Factory Image from here. I notice that 103 is there now so just skip this step and flash that now.
I noticed that after flashing the latest SuperSU the device would never boot.
So I had to use KingRoot but for me the apk method never worked so I went with the desktop version.
To get Root I went to KingRoot's XDA page and downloaded the Desktop version.
When running the program it is all in Chinese but is thankfully idiot proof with its one big button on it. Just make sure that USB Debugging is turned on and wait for it to finish, it will reboot during the process.
KingRoot installs its own version of a Super User advisor so it will prompt when something needs root access and for most people that would be enough but I prefer SuperSU, Thankfully KingRoot has a set of instructions, follow these to the letter and it will guide you through removing KingRoot and installing SuperSU. During that process you will get a lot of errors saying that files are no longer there, just ignore them, that means the initial uninstall got the files.
Once I was able to ensure that SuperSU and Root where staying after a reboot I re-installed TWRP (for some reason I couldn't get CWM to stick after a reboot but oh well I like TWRP more >_>) and made a backup of my stock rooted device.
I then went to this page and grabbed the Unofficial Xposed 5.1 .zip and went to this page and grabbed the Xposed Installer.
Rebooted and waited for the App Cache to re-build as the Xposed framework nukes it then installed my mods as normal.
Took a little bit longer than normal to update but oh well, Everything is working smoothly and I'm happy with it.
Rooted my Shield two times wth CWM without problems.
astuermer said:
Old recovery is working for me - it's CWM 6.0.4.4.
I had to flash it twice, first time it was reflashed to stock.
PS: TWRP 2.8.5.0 (unofficial) is working too.
Click to expand...
Click to collapse
Which cmw did you use and where did you get it? I tried using flashify with twrp and it says boot failed when booting into recover.
astuermer said:
Rooted my Shield two times wth CWM without problems.
Click to expand...
Click to collapse
Give me a few mins. I will upload my Recovery package...
Here we go. I've flashed and rooted my SHIELD successfully after OTA upgrade - and today again after flashing the clean 103 factory Image.
SHIELD-Portable-Recoveries.zip
Update: I've attached a ZIP file with 4 different recoveries. Simply execute the Batch file I've included (if you're on Windows) and select 1-4.
stock KitKat recovery (from update 101)
stock Lollipop recovery (from update 103)
ClockworkMod recovery (CWM) 6.0.4.4 (somewhere from XDA, but couldn't find the link)
TWRP recovery 2.8.5.0 (from here)
From @Steel01 The TWRP located here may give people problems and we should be using the one in the MultiROM TWRP located here.
Source here.
EDIT: I will test tonight and see what happens when you image with the factory image and just install MultiROM's TWRP and then try SuperSU's latest BETA.
I was trying to use the other TWRP before and could never boot which is why I did the KingRoot method.
If you wanted to change Kinguser to SuperSU all you have to do is download any "Control Rotation App" and set it as Portrait Mode (if it didn't work make sure that the Nvidia Shield Portable is in a sitting position and flip it , It should work , If not try installing other apps), Install "Super-Sume" , Then touch the big blue button , After that wait until the process is done , You should see SuperSU, In the other hand Kinguser has already vanished (I'm not sure if SuperSU will open automatically or not), Install the binary, Reboot, Done.
Have a nice day