Related
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
moose&beer said:
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
Click to expand...
Click to collapse
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
sfobrien said:
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
Click to expand...
Click to collapse
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
sfobrien said:
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
Click to expand...
Click to collapse
No worries. And yeah, I did the OTA, but held off until Google pushed a notification to my N10 for the update. I'll give goomanager a try. Appreciate the replies. Thanks.
This is normal behaviour in a OTA update. Installs a couple of files that, if a custom recovery is installed, reflash stock recovery on reboot. This doesn't happen if you flash a factory image.
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
three west said:
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
Click to expand...
Click to collapse
Thanks - I'll give goomanager a try.
beekay201 said:
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I assumed the same, but I got the same situation as OP, I'll try reinstalling TWRP using Nexus Root Toolkit, or does goomanager have a special functionality for those conditions?
Update: Used NRT to install TWRP in the advanced settings, worked beautifully.
The latest Google OTA's are not successfully installing unless you restore stock recovery fist and some are failing if you are rooted as well.
Best bet if you are running as rooted or custom recovery is to backup first, un-root, restore stock then sideload the OTA. This will save you lots of frustration and heartburn.
It's easy enough to restore stock and to re-root so just make it part of your ota routine.
I have set my SuperSU to automatically update. It was all fine and working on the previous versions, but when I checked now it gives me the error below.
"There is no SU binary installed, and SuperSU cannot install it. This is a problem."
Please help.
Gilkauss said:
I have set my SuperSU to automatically update. It was all fine and working on the previous versions, but when I checked now it gives me the error below.
"There is no SU binary installed, and SuperSU cannot install it. This is a problem."
Please help.
Click to expand...
Click to collapse
download this, boot into recovery, then flash it. its the latest supersu binaries http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip
Or simply boot into twrp, reboot it and it's gonna give you the option to do so.
Twrp should have told you that you lost root and gave the option to repair it.
I tried to boot into recovery but it just showed me an android icon with red exclamation.
Also I dont have TWRP installed.
Gilkauss said:
I tried to boot into recovery but it just showed me an android icon with red exclamation.
Also I dont have TWRP installed.
Click to expand...
Click to collapse
So reflash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.4.4.0-mako.img in fastboot and then superSU http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in TWRP.
It seems that many users have had issues with the last few SuperSU updates in one way or another. Some get errors trying to update the binary. Some say Titanium Backup will no longer work unless you use the paid version of SuperSU. The latest installable zip doesn't work on all devices and needs a fix according to the first post on the official SuperSU thread...
http://forum.xda-developers.com/showthread.php?t=1538053
I decided to switch to the new Superuser by Koush.
sos
I tried but seems like i have to get the paid version of supersu in order to continue to use it so. can i go back from the beginning and re-root it with Clockworkmod ?
luubutmucxanh said:
I tried but seems like i have to get the paid version of supersu in order to continue to use it so. can i go back from the beginning and re-root it with Clockworkmod ?
Click to expand...
Click to collapse
flash the supersu su binaries in your recovery and reboot, download it here http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
simms22 said:
flash the supersu su binaries in your recovery and reboot, download it here http://download.chainfire.eu/333/SuperSU/UPDATE-SuperSU-v1.34.zip
Click to expand...
Click to collapse
Thank, n sorry wrong section, my phone is htc one m7. But i did flash the 1.34 version, still getting the message that supersu stopped working.
luubutmucxanh said:
Thank, n sorry wrong section, my phone is htc one m7. But i did flash the 1.34 version, still getting the message that supersu stopped working.
Click to expand...
Click to collapse
well, im not familiar with rooting it, heres a link http://www.xda-developers.com/andro...one-m7-and-install-recovery-xda-developer-tv/
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
nickf123654 said:
I was having this same issue on my Note 2 (4.3). I seem to have found a way to restore root that may help you as well.
I think this issue may be caused by the SU app & binary updates. Uninstalling the updates has restored root for me.
Go to:
Settings > More > Application Manager > All > SuperSU > Uninstall updates
(menu options may be slightly different on other devices)
This will roll back SuperSU and hopefully restore your root access.
Let me know if this helps.
Click to expand...
Click to collapse
again.. or just grab the latest supersu and flash it in recovery. thats all.
ALSO.. THE LAST POST IN THIS THREAD IS OVER A YEAR OLD. WHY BRING THIS THREAD BACK? LOOK AT THE DATES BEFORE YOU POST IN A DEAD THREAD.
simms22 said:
again.. or just grab the latest supersu and flash it in recovery. thats all.
ALSO.. THE LAST POST IN THIS THREAD IS OVER A YEAR OLD. WHY BRING THIS THREAD BACK? LOOK AT THE DATES BEFORE YOU POST IN A DEAD THREAD.
Click to expand...
Click to collapse
Yes, it would be nice if that worked ever time, but for me it didn't.
I tried flashing the latest SU many times and still ended up without root.
I am just trying to offer a solution that me be helpful to others experiencing the same issue I did.
If you are interested in the details, you can check out my thread here:
http://forum.xda-developers.com/note-2-tmobile/help/4-3-custom-roms-losing-root-t2817114
To your point of this being an old thread, I just want to make the information easy to find. I searched all over the place and could not find a solution to my problem. Hopefully I can help someone else who is facing the same issue.
nickf123654 said:
Yes, it would be nice if that worked ever time, but for me it didn't.
I tried flashing the latest SU many times and still ended up without root.
I am just trying to offer a solution that me be helpful to others experiencing the same issue I did.
If you are interested in the details, you can check out my thread here:
http://forum.xda-developers.com/note-2-tmobile/help/4-3-custom-roms-losing-root-t2817114
To your point of this being an old thread, I just want to make the information easy to find. I searched all over the place and could not find a solution to my problem. Hopefully I can help someone else who is facing the same issue.
Click to expand...
Click to collapse
you are also missing that its a completely different device. of all my time ive spent in the nexus 4 and nexus 5 forums here, not once has an issue like that been reported. this would better be posted in the note 2 forums.
Thank u very much
gee2012 said:
So reflash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.4.4.0-mako.img in fastboot and then superSU http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in TWRP.
Click to expand...
Click to collapse
Thanks a lot.........your suggestions helped me a lot...... :good:
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
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
Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy
Well dang. I tried installing LINEAGE OS rom again and hoped for some strange reason it would boot into it. TWRP just keeps loading. I try the Reboot command in TWRP then choose SYSTEM and it still just goes to TWRP.
Well sometimes it just helps to air your frustration. As is true with many things in life. Say it out loud. Etc...
I was sure I had THE latest version of TWRP installed when this was happening. I rechecked to make sure. I didn't. I was 1 version away. Fastboot flashed that and it's booting normally . For now. Now, to see if I can get those apps to show up in the play store.
Things like Snapchat, Facebook messenger, etc... would just not show up.
Nope. That's still a problem . I wonder why this is happening?
Try clearing dalvik cache and sync you data for your mail account. I think those app wil show up. As for snapchat, you can't install it via playstore you can't pass safetynet.
FuzzyFone said:
Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy
Click to expand...
Click to collapse
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.
darkeyes22 said:
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.
Click to expand...
Click to collapse
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:
FuzzyFone said:
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:
Click to expand...
Click to collapse
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.
darkeyes22 said:
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.
Click to expand...
Click to collapse
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy
FuzzyFone said:
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy
Click to expand...
Click to collapse
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.
darkeyes22 said:
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.
Click to expand...
Click to collapse
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.
FuzzyFone said:
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.
Click to expand...
Click to collapse
Through Fastboot? Try through TWRP, flash removal, then flash Systemless SuperSU (not the one you have now).
Here is the link to systemless SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.
RonakRonak said:
Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.
Click to expand...
Click to collapse
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs
darkeyes22 said:
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs
Click to expand...
Click to collapse
Yes.i already mentioned model name.