Hello,
Just started getting an OTA notification a few days ago (like around Jan 15… ?). But I get the err: 0x01117008 every time.
I am rooted, but just stock. No custom ROMs ever. No custom recovery, no TWRP or anything. All previously frozen apps have been unfrozen/defrosted with Titanium Backup. no modifications other than the rooting. Only app that has anything to do with the system is busybox pro. No theming or shell apps.
Tried temp unroot and OTA Survival/Survival Mode in supersu and superuser apps.
Yet when I go to Settings > About Phone >> Status, it says "Rooted" under root status.
I don't want to flash stock. The phone is already stock.
Anyone have any ideas?
daniel178 said:
Hello,
Just started getting an OTA notification a few days ago (like around Jan 15… ?). But I get the err: 0x01117008 every time.
I am rootedx, but just stock. No custom ROMs ever. No custom recovery, no TWRP or anything. All previously frozen apps have been unfrozen/defrosted with Titanium Backup. no modifications other than the rooting. Only app that has anything to do with the system is busybox pro. No theming or shell apps.
Tried temp unroot and OTA Survival/Survival Mode in supersu and superuser apps.
Yet when I go to Settings > About Phone >> Status, it says "Rooted" under root status.
I don't want to flash stock. The phone is already stock.
Anyone have any ideas?
Click to expand...
Click to collapse
Download the kdz and flash it
Anyone have any other ideas?
There must be a way to do it without starting completely over. I've never had to flash to unroot or OTA update.
BTW, root checker basic also says my device is not rooted. I also cant rename system files in Root Explorer (root is needed to do this). The ONLY place where the phone says I'm rooted is under Status in Settings.
Related
this may have been asked, but i'm new to the nexus 7. i rooted it right away, and put TWRP on. probably shouldn't have but i like doing nandroids. i was excited for the OTA and want to just install it since my tab got it, but it won't obviously since i've got a custom recovery (duh i should've thought of that..) and i don't want to go flashing roms yet (i like keeping everything stock right away, it's so smooth)
so my question is, is there a way to go back and flash the stock recovery somehow so i can OTA, then put TWRP back on? i can't find the stock file to fastboot flash or anything
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
kangy said:
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
Click to expand...
Click to collapse
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Alright try this.
Go to SuperSU settings and and click on Reinstall under Cleanup, it will give you a prompt and tell you it will self close and to re-install from the market. (Mine never fully uninstalled which I assume is due to it being flashed to ROM, I checked under the App manager and it only had a downgrade option so) Anywho. If it did uninstall go ahead and redownload it from the market, if it didn't check the market anyway, the Dev published and update for it to help with 4.2 multi users.
Once you get it reinstalled and/or updated from the market go back to the settings and Toggle off Enable Superuser, close the app, re-open and then re-enable superuser. You probably will want to give it a reboot at this point. (Ive restarted my device a hundred times since going to 4.2 from trying to work through the bugs. Once you restart test a root app. I used Adaway for the test. Important, if the app fails or gives an error about not having root, try again. After I went through all of those motions SuperSU was pretty slow for a while with giving root access, usually the second request from the app wakes it up. Since then though it is back to being snappy with zero lag.
Yes, the reason you can't flash TWRP through ROM Toolbox is that requires root. Once you get your SuperSU working try flashing the latest TWRP again, it should only take a few seconds to flash. Let me know how it goes, I'm subscribed to the thread. I may not be the smartest guy on XDA but you are in the same exact boat I was last night!
jayochs said:
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Click to expand...
Click to collapse
First, determine if you have root or not. Open TiBackup, if it opens correctly and you can see all your apps listed, you have root. Otherwise it will say "Failed to obtain root," and quit.
If you have root, then great. If not, you can flash the SuperSU zip in TWRP/CWM: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
I haven't tried flashing superSU, I've always flashed Superuser zip [google "superuser zip"], and then installed superSU from Play store.
Once you have root..
Go to Settings > Security and check allow installation from non-market apps, and uncheck the security feature that checks all apps for being malicious.
Then try it. If you still cannot restore apps, you might have to install them with adb.
I just updated someone's N7 to 4.2, and as usual I backed up everything in TiBackup.
Then I backed up the TitaniumBackup directory [because I had to do a full factory reset].
I then extracted all the .apk.gz files with gunzip. [in linux OR adb: $ gunzip *.apk.gz -- for windows, I suppose you would have to use 7-Zip].
Then I tried to install with pm:
Code:
for i in *.apk; do pm install $i; done
But every one was giving me an error, INSTALL_FAILED_INVALID_URI, I couldn't figure it out. Found a thread said to chmod 755 /data/local, but that did not fix it.
So what I had to do, was on my linux PC:
Code:
for i in *.apk;
do adb install "$i"
done
So I finally was able to batch install my apk files.
after that I restored all apps data.
Nandroid back ups not possible after 4.2 update
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Yordan5 said:
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Click to expand...
Click to collapse
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
mvmacd said:
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
Click to expand...
Click to collapse
NRTK 1.5.5 would not flash the 4.2 custom rom I fed it either. Just kept stalling out with errors that it could not find the zip file.
So I booted into TWRP and flashed it with no problem at all.
I also did backup in TWRP and checked everything but saw no mention that is was a Nandroid backup. How can I be sure?
i'm trying to nandroid back to a 4.1.2 nandroid i have, problem is, twrp has different directories for nandroids in 4.2 than 4.1.2...so it can't find the old nandroids and i can't find the 4.2 dir where twrp stores them now. ugh. such a damn headache for an update that it turns out i didn't want lol
Read my post below, I was having the same problem but got back on 4.1.2. You have to use the twrp explorer and relocate the twrp files since 4.2 moved them.
http://forum.xda-developers.com/showthread.php?t=1992552
Nandroid Downgrade from 4.2 to 4.1.2
Sent from my Nexus 7 using Tapatalk 2
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Just reflash the superSU.zip from here http://download.chainfire.eu/315/SuperSU/UPDATE-SuperSU-v1.25.zip in CWM and you should be rooted again. You will not loose any data so no need to backup. Download OTA Rootkeeper from Play to regain root after installing future OTA`s.
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
AAhrens said:
I'm not using CWM, I'm using TWRP and I can't seem to boot into it.
Click to expand...
Click to collapse
Try cmd and type: adb reboot recovery. If you see the androidian (stock recovery) you have to reflash the TWRP img file in fastboot mode.
Will this reset my phone? Or does only rooting do that?
You will not loose any data.
Sent from my Nexus 4 using xda premium
AAhrens said:
For some reason I seem to have lost root. I think this may have occured when I updated to 4.2.2, it automatically asked to update OTA. That or this occured from updating SuperSU.
When I try to go into recovery mode I see a android laying down with an exclamation point on his belly. I can't get into TWRP recovery.
SuperSU gives the error "There is no SU binary installed and SuperSU cannot install it"
I tried opening up titanium backup, and it says I have no root.
The fastboot states me phone is unlocked.
I have no issues rerooting, but I'm wondering:
a) Why and how this happened? Was it from the OTA update?
b) How I can prevent this in the future
c) Can I still back things up before rooting?
d) Will I lose everything when trying to root again?
Click to expand...
Click to collapse
Let me guess, you used a toolkit to root?
a) You did the full OTA, so you lost your custom recovery.
b) flash images through fastboot and skip the recovery.
c) Only after you flash a custom recovery. If your recovery is sitting in the same folder as fastboot and named "recovery.img, simply cd into the fastboot folder in a command prompt and type
fastboot flash recovery recovery.img
d) Not unless you lock or relock your bootloader.
OP, you need to do some more research and uninstall the toolkit from your computer. You know just enough to cause yourself problems, but not enough to know why they happen or how to fix them.
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Rizy7 said:
Yes the OTA update got rid of the files or partition that is created in order for you to have root access. Your custom recovery was also replaced with the stock recovery (android lieing on its back with red triangle).
To prevent you being unrooted in updates you can try using OTA RootKeeper available on Google play but this is not guaranteed to work.
You can use carbon to back up your data as this does not require root access to work.
And no you will not lose your data if you re root again, this is only done when you unlock the bootloader.
Click to expand...
Click to collapse
Thanks all, was able to get it fixed by re-rooting!
I tried a couple of root apps, they didn't work. F***. Adaway and Music2SD. Both tell me that my rooted S4 isn't rooted. I have prerooted MF9, flashed via TWRP. It included SuperSU, with 1.1.3 binary (I think). Okay, after no search results I decided to do something on my own.
First, I opened SuperSU and told it to install itself as a system app. Then, I installed ChainsDD Superuser. That's when I found out my binary was out of date. I chose to update it via Superuser. For some reason or another, it said it didn't update. I went to app manager, cleared data and uninstalled updates for SuperSU. I updated it in the play store and opened it. Then, it told me my binary was out of date - woo! Wait.. normal method didn't work - "Installation Failed!" Okay, try TWRP/CWM method. It rebooted into recovery, flashed some stuff before I could read it, and restarted. Booted right back up. I opened Superuser and it said I was on v0. Went to ChainsDD's site and downloaded the 3.1.3 ARM to flash in recovery. I did that, still nothing. Now SuperSU and Superuser are permanently installed apps (I now have no root to delete them). Whatever. I ran CF-Auto-Root in Odin. After that, both SuperSU and Superuser were removed. I have nothing now.
My question is, what's the best way to get the latest binary on MF9? If i restore from Nandroid, how should I update? If I start from scratch, what binary will I get from CF-Auto-Root?
UPDATE: I'm back to rooted, with SuperSU. I got the update binary notice and chose the normal method. It updated just fine, but I still can't use Adaway or Music2SD. Superuser by ChainsDD still shows v0.. all of my normal apps have root access just fine.
FIX!: My ignorance is to blame here - XPrivacy blocks root access by default on Adaway and Music2SD... I didn't realize it did that!
So I just tried to take an OTA and it gave me an error on the install screen then rebooted. Upon restart it gave me a message saying my device was suspected of rooting and that no OTA will be taken. All I've done is root, install root Explorer and titanium and hidden a few apps. Recovery is stock so I'm on the stock ROM. I really have no use for root so I don't mind if I lose it.
Should I just uninstall superuser or do I need a factory reset before I can take an OTA?
I have AT&T G2 rooted and stock recovery. I took the OTA update and all went fine and I didn't lose root either. All good on this end other than not knowing what was in the update.
EDIT: I now know what was in the update lol! A quick google search usually answers most question
So after many months i decided to restore my device to stock so i can check for firmware updates and return to stock.
The problem is that every time i restore my apps from google i get auto rooted again... i tried through software restore and delete everything i tryed with stock recovery mode delete/wipe and wipe cashe, nothing im still rooted, then i tried costum recovery with wipe all and davlink cashe still rooted.
I then full flashed firmware from kies and i still get rooted once i return the google apps from my account is this normal? the only way to stay unrooted i think is stop app restore from my google account.
busybox xposed and supersu also get restored from my account.
I installed the latest france firmware ( i had greek EUR ang2) and i get rooted once i restore my apps wtf...
If i quit trying to get official and stay with busybox and xposed will i get the update with the fake official setting from xposed?
Edit i uninstall everything includung supersu,busy box and exposed and im still costun... i quit.
You have used the UNROOT function in SuperSu Settings?
BigBugHmb said:
You have used the UNROOT function in SuperSu Settings?
Click to expand...
Click to collapse
Yes and the supersu gets stuck and force closes...
Only thing i managed to by pass the auto root is create another google account and not log in with mine now i have to transfer the contacts.
Anyway at least now i wont trip knox ever haha .
I Root and have knoledge with roms and flashing since 2009 this is the most weird thing i have ever seen...
Oups, real? :/
Wich version, v2.16?
MfG/best regards
René
(Send with SM-T805)
If you mean supersu version yes its 2.16.
I am rooted again and when the new update comes I will wipe my phone and use a different account to update, and then I will try my account again to see if I'm still rooted with android 5.
Unrooting
You can manually unroot it by
1. Delete /system/app/superuser
2. Delete /system/bin/su
3. And lastly Delete /system/xbin/su
You can also install this the attachments in recovery mode,
SU-Uninstaller-signed.zip removes Superuser and su files,
TeamEpic-RemoveRoot-from-Recovery-signed.zip removes su and busybox files completely but not Superuser.apk
These attachments are taken from other sources, I have no time to find them again sorry