Related
After getting assert_failed errors since forever on 2.3.2, I finally downgraded my radio to fix them and without even thinking installed 2.3.4 OTA. The install went fine but I lost my root.
Now, I haven't unlocked my bootloader. To root, I have to unlock the bootloader which will wipe my phone clean. To take a nandroid/full backup of phone I need root. So, kinda stuck in a catch-22 here.
I still have ROM Manager installed and when I used backup feature in it, it created a new backup. However I am not sure if its a full phone backup or just the ROM. Is there anyway to verify?
Also, any solution to gain my root back with all my data? I am fine with unlocking the bootloader as long as my data is safe.
Edit:
This just struck my mind. If I modify the update file and put in su binaries repackage it and reinstall it on my phone, would it work? Can I even reinstall an update?
Edit2:
Can I just create my own update.zip containing su binaries, sign it and install it?
dpacmittal said:
Edit2:
Can I just create my own update.zip containing su binaries, sign it and install it?
Click to expand...
Click to collapse
You can create it, of course, but I doubt you could install it with a locked bootloader, since you are unlikely to have the private key google uses to sign its updates.
How much can I back-up without rooting my phone? I'll backup the SD partition. I just want all my application settings (eg; Angry birds data) with all the applications, messages and contacts. Is it possible to back all these up without root?
I have titanium installed, if its any good?
[Guide] Install ClockworkMod Recovery image after updated to 2.3.4 (GRJ22).
I hope this will able to help you
http://forum.xda-developers.com/showthread.php?p=13800735#post13800735
My bootloader is locked, mate. Your method won't work for me. Thanks, anyways
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 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
Been on Mahdi forever on my VS980 and wanted to try the new KK so I tried to use TitaniumBackup and it says that I don't have root.
That is weird.
It looks like after upgrading on one of the last updates, I lost root along the way.
I tried to flash the latest SuperSu in recovery and it didn't work.
What else can it be?
i can get into recovery fine.
Lost root..
illyfilly said:
Been on Mahdi forever on my VS980 and wanted to try the new KK so I tried to use TitaniumBackup and it says that I don't have root.
That is weird.
It looks like after upgrading on one of the last updates, I lost root along the way.
I tried to flash the latest SuperSu in recovery and it didn't work.
What else can it be?
i can get into recovery fine.
Click to expand...
Click to collapse
So, if you havent already done it, first make sure root is enabled at all in developer options (it can be disabled).. if it is enabled, and you still dont have root. Back your stuff up with titanium backup or the like. Wipe/clean flash the rom/gapps/superSu. If that doesn't fix it, it is a problem with the rom file itself
Got it by flashing SuperSU from the play store
Sent from my g2 using Tapatalk
My objective is to find a way to regularly apply updates without having to rebuild each time. I know there is TiBu, but it is still a lot of work to rebuild my setup. Titanium does not restore some settings, frozen apps, widgets, or blocked broadcast receivers/services. They take a long time to reestablish.
Ideally, I can simply restore from a FlashFire /data backup after an update. Unfortunately, it has not worked out. While on PF1, I made a full backup. After updating to PF2, re-root, and restoring /data with FlashFire, the phone boots, but IMS and other core processes FC while the CPU stays at near 100% constantly. I don't know why.
I am looking for a way to either 1) update without wiping the /data partition, or 2) restore from FlashFire and have the phone boot/work properly afterwards.
Any ideas??
On a related note--I know I can 'go back to stock' and take the OTA. Question is--how 'stock' do I have to be? Do I have to flash the stock package or is removing root from SuperSU enough? I was thinking that if I can somehow take the OTA while keeping my /data partition intact, I can then just re-root.
I would appreciate any input.
Thanks.
You can always try it yourself... I have returned to pf2 via the guide in the Verizon forum then ota'd from there, then rerooted. No issues until playstore auto updated supersu on me.
twizt3d said:
You can always try it yourself... I have returned to pf2 via the guide in the Verizon forum then ota'd from there, then rerooted. No issues until playstore auto updated supersu on me.
Click to expand...
Click to collapse
I have tried every combination, but nothing panned out. The last thing I tried was to use FlashFire to flash the PF2 update package. The phone boots, but constant IMS Service Stopped error, no radio, etc.
Updating via OTA or Odin and rerooting is not the problem. The problem is you need to rebuild the phone. TiBu is not a sufficient solution for me. Unless I can dirty flash (or restore from FlashFire after an update), it is unsustainable.
I believe I have done what you're asking before. You'll have to flash the kernel and system partitions back to stock any way you'd like, take the OTA, and then reroot. You may need to uninstall superSU before doing that also, I don't think just turning it off works.
DeadlySin9 said:
I believe I have done what you're asking before. You'll have to flash the kernel and system partitions back to stock any way you'd like, take the OTA, and then reroot. You may need to uninstall superSU before doing that also, I don't think just turning it off works.
Click to expand...
Click to collapse
Are you saying that I would:
1) Leave the current apps, data, and config in place
2) Flash /system back to stock and uninstall SuperSU
3) OTA will work
4) Re-root
Thanks.
snovvman said:
Are you saying that I would:
1) Leave the current apps, data, and config in place
2) Flash /system back to stock and uninstall SuperSU
3) OTA will work
4) Re-root
Thanks.
Click to expand...
Click to collapse
Yup. I have not tested that on this phone, but I have done this on the S4. Make sure you also restore the original kernel too since I doubt OTAs will work with the engboot kernel. If you've disabled any system apps you may have to unfreeze those as well
DeadlySin9 said:
If you've disabled any system apps you may have to unfreeze those as well
Click to expand...
Click to collapse
Thank you. I've read something like this--that there are implications related to frozen system apps. Why does that matter?
For me, instead of taking the OTA, I was able to FlashFire the updated /system with /data intact, but upon reboot, I kept getting IMS process stopped error and no radio service. I wonder if this had something to do with frozen system apps. Mind you, I did not freeze IMS, I only froze all the bloat.