I had a rooted S4 running stock ROM. Unfortunately, I STUPIDLY did the MK3 update without really thinking about it or researching it. As expected, it got rid of my root ability. Only after that did I find out that I couldn't reroot yet. So here's my question. I've used root explorer to see if the Superuser apk is still showing in the system/app directory, which it isn't. So I uninstalled the Superuser apk that was still showing in my applications list (do updates automatically move the apk to a non-system directory?) and restarted my phone. Unfortunately, the "Custom" logo is still showing on the boot screen. Does anyone know of a way to get rid of that? I'm sure root will be reestablished sometime in the future, but I'd hate to have something happen to my phone that required repair and me still have the "Custom" thing showing.
Any ideas would be greatly appreciated!
brickjr said:
I had a rooted S4 running stock ROM. Unfortunately, I STUPIDLY did the MK3 update without really thinking about it or researching it. As expected, it got rid of my root ability. Only after that did I find out that I couldn't reroot yet. So here's my question. I've used root explorer to see if the Superuser apk is still showing in the system/app directory, which it isn't. So I uninstalled the Superuser apk that was still showing in my applications list (do updates automatically move the apk to a non-system directory?) and restarted my phone. Unfortunately, the "Custom" logo is still showing on the boot screen. Does anyone know of a way to get rid of that? I'm sure root will be reestablished sometime in the future, but I'd hate to have something happen to my phone that required repair and me still have the "Custom" thinnon-sys
Any ideas would be greatly appreciated!
Click to expand...
Click to collapse
1. make sure you are using superSU and not superuser...
2. are you using geohot's lambda activeroot?
I have the custom icon on my boot screen sometimes,when it does my system settings show custom, and then sometimes it goes away and my systems settings show official.but I have never lost root, and my firmware updaters r renamed. I am curious. and if anybody can point me in the right direction A custom recoveryCWM preferrably, please do.
Related
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Yesterday, I did the same thing you tried and I was successful in rerooting my phone after the OTA update. When you used the 1-click process did you choose option 1 or 2. I tried 2 and it didn't work. I had to chose option 1 (reload everything) to be successful. BTW, remember to make a new recovery backup of the system.
unrooted
xberry said:
I may have missed this in another thread, so please feel free to redirect me if so...
Without thinking, I updated my Droid with the OTA push and my previously rooted Droid 2 is now not rooted.
I did try to run the oneclick and 1-2-3 root processes. Both end with "your device is now rooted", but of course it's really not. I do have the Superuser APK, but my rooted programs are not communicating with it. And I'm not able to uninstall the Superuser program (thought I'd try to reinstall it). No go.
I had Titanium Backup, ad am wondering if I can wipe my phone and restore it, then upgrade, and root after. I'm a newbie with limited knowledge, so wondering if I've backed myself into a corner on this one.
All feedback appreciated!
Click to expand...
Click to collapse
Same issue here - how I fixed
I had already made titanium backups of important stuff - you have to go into applications (that use root) and force stop and clear data. Once this is complete open titanium backup for instance, and you should be asked for super user and then be good to go. Same goes for rest of apps that need root
OTA update Loop?
i have my d2 rooted after the ota 2.2 update. i just received a notification to accept the most recent OTA update ... whatever it is... and assumed it was one of my apps as i didnt read it thru completely b4 tapping 'ok'. now it is stuck in a download, reboot, update, "update unsuccessfully installed", redownload, reboot...........
is there a way to cancel the update? i dont really care if i have it or not
or some way to stop this process aside from the airplane mode i had to set it to so it would stop this madness
So you can do the OTA update without having to unroot and reroot?
Great advice from all - thanks! I'm not sure exactly what fixed it, but I ran DOROOT several times, did the unplug/plug when it hung for a minute, force closed/cleared data from previously rooted items, and also put phone into 'charge only' mode when USB Debugger would not run.
Finally - success! My advice to users with this same issue - try and try again.
Thanks all!
Got the triangle screen and following instructions in guides are not fixing it. Heres my scenario. I got my kindle with 6.2 on it. Got it rooted, installed market and go launcher and was great. Then the update of course came thru and broke root. Still been able to download market apps and use go launcher. So I followed this guide
http://forum.xda-developers.com/showthread.php?t=1417284
to regain root and install twrp. It says root is successful, but superuser force closes everytime trying to open or use it. I can open my tibu and root explorer and everything still gave me root access. Went and changed the MarketIntentProxy.apk to MarketIntentProxy.apk.bak so market links go to market by default. That worked. Noticed that all amazon apps downloaded have a default amazon icon. Thought nothing of it. Went to install twrp anyway. Stuck at triangle now. Followed all instructions to fix and the KFU keeps flashing error device not found constantly and boot status unknown. Not showing up in my devices but I can eject via the safely remove hardware program. What happened? Did everything as guide states and watched the videos as I was doing each step.
After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
jmickel99 said:
After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
Click to expand...
Click to collapse
Not sure, but you may have to unroot first to install the update. What they probably meant by you can keep root is that they didn't patch it to prevent root. So, once you unroot, install update, then you can reroot again. Just my guess.
Sent from my LG-G2 using Tapatalk
jmickel99 said:
After i read that you could keep root with the latest update i gave it a try. Im just rooted with stock recovery. I deleted some bloatware and installed hide soft keys was all i did. I downloaded the update and when it went to install i get an error msg. Message was er: 0x1117008. Then would reboot and a message would pop up saying was a problem during installation, no changes were made. I have since restored all the bloat i deleted thinking that may help, tried again and get same message. Anyone have an idea what it may be?
Click to expand...
Click to collapse
I get the same error. Any update?
You'll need to restore all bloat. Pretty much need to be completely stock before updating. I was rooted with tethering provisions removed and Stock LG Browser installed. I has to fix the provisioning and remove the Browser (also adding any system/app files I removed) before the update was successful.
Kaiken said:
You'll need to restore all bloat. Pretty much need to be completely stock before updating. I was rooted with tethering provisions removed and Stock LG Browser installed. I has to fix the provisioning and remove the Browser (also adding any system/app files I removed) before the update was successful.
Click to expand...
Click to collapse
i'm am getting this same error and i have restored all bloat and even temporarily unrooted using Voodoo's OTA RootKeeper. i dont know what else to do at this point. any thoughts/suggestions?
brianj320 said:
i'm am getting this same error and i have restored all bloat and even temporarily unrooted using Voodoo's OTA RootKeeper. i dont know what else to do at this point. any thoughts/suggestions?
Click to expand...
Click to collapse
Have you restored your hide nav keys? You can also download a completely stock rooted rom somewhere on here and make sure your system apps are the same. I had to do this to find my BrowserProxyProvider.apk/odex I accidentally deleted and pushed them back into system/app.
The difference between "Official" and "Custom" device status was S-Health.
I was freaking out over being unable to get my S5 to show as "Official" in its device status (wanted to update, but was told I couldn't) .Out of paranoia, I copied over all my Downloads to my SD card and removed it, deleted any root apps and even cleaned it up using SuperSU. And I rebooted a lot. After I finished, I still saw
Device Status: Custom
Then, I remembered the S-Health bug. Since i like S-Health, I had switched it over recently from being a System app to being a User one (because S-Health on a rooted device was, well, broken). So I re-rooted with SuperSU, then re-opened Android Tuner Free and moved S-Health back from being a User app to being a System one again.
Device Status: Official
I didn't even have to unroot, remove the SU app, or reboot it; I just checked back in Settings and it was "fixed."
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
verse187 said:
Really and it have you official from what I know custom comes out because the phone is rooted anybody correct if im wrong
Sent from my SM-G900P
Click to expand...
Click to collapse
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
primetechv2 said:
Well, it looks like I spoke too soon. During my OTA update attempts, I had root and it showed as "Official" for a while. Then when I removed SuperSU fully (including the su binaries, making it unrooted), my next attempt to install the update proved futile.
Somehow, when I removed the su binaries with SuperSU, it re-registered my device as Custom. I don't know how, because SuperSU had been specifically told to not attempt to retain itself during OTA updates...
Click to expand...
Click to collapse
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
KennyG123 said:
You did not reinstall stock recovery. You cannot get OTAs if you have a custom recovery still.
Click to expand...
Click to collapse
I never actually installed a custom recovery, though. I did eventually reinstall the fully stock firmware with Kies and then performed the upgrade, something I'm going to guess wouldn't be possible otherwise... But to be specific, I never had anything installed except got XPosed mods and a moved S Health to get it functioning again.
But I'm really sad that, for whatever reason, my device status kept flickering between Official and Custom, especially when it chose Custom after I disabled root.
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
BlackJou said:
I just flashed the stock nd5 firmware through odin in mine and it still show's as ''custom''. Any ideas on how to get it to show ''official''?
Click to expand...
Click to collapse
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
frcollier said:
I ran into the same issue when trying to update OTA for WiFi calling. I wound up (before I had a chance to reset), changing the runtime back to Dalvik from ART, wound up working.
Click to expand...
Click to collapse
It is on Dalvik though :/
well, I did it again.
rooted: Official status
Installed XPosed: Official
Removed S-Health: Official
Reinstalled old S-Health as a user app: Official
Shifted S-Health to System app: Official
Removed XPosed: Custom
Anybody know what permissions SHealth and HealthService (.apk, .odex) should be reinstated with, and in which folder they go, I'd be really happy. Especially if someone got back to me before I downloaded this 1.5GB system file to figure out if it says.
I’m by no means an expert, but I’ve always been tech savvy or at least been able to research and follow directions for things I’d like to do on my devices. I flashed my rom using Odin to fix the bootloop, but I still need a way to successfully move the app to system apps without getting stuck in a bootloop. Here is what I have done or attempted so far:
1. I have a Galaxy Tab 4. I recently rooted this device using Kingo Root.
2. After I rooted the device I confirmed I had root access and everything seemed ok. I have used this app before to root other devices with no problem. I wanted to root this device so I could move Fake GPS Location Spoofer to the system apps folder and make it a system app.
3. I used lucky patcher to move the app to the system apps folder. However when it went to reboot my device, my device became stuck in a bootloop. After trying to repair the os, I successfully used Odin to flash my rom (android 5.1.1) and fix the problem.
4. After attempting to move the app with other file folder systems with root access, I still can’t move this app without it resulting in a bootloop.
What am I missing or doing wrong? Any suggestions, solutions, or insight would be welcome. If you need additional information or detail, just let me know. Thanks!
Update: After some more testing I believe that the rooting with Kingo Root is the problem and not the attempts at moving the app to system app. I flashed the 5.1.1 Rom with Odin then proceeded to to reroot the device with KIngo Root. Once I did that and it showed as successful. I restarted my device and I got the bootloop problem. I've tried rooting the device SM-T330NU using the method in the general section of the samsung tab 4 forum but was not able to boot into recovery and got a different bootloop problem that would go black and then blink repeatedly. I made sure to use the download for the 8.0 so I'm not sure what is going wrong.
Suggestions?
Update 2: I managed to finally root my device with the CF method. I am still not sure why the other methods I used didn't work.