Database Info

Captivate no longer rooted after JH7 update

has anyone else found that there phone is no longer rooted after the AT&T JH7 update??? I noticed that the USB tether is no longer on the phone and went to use Barnacle Wifi Legacy and it told me that it only worked on a rooted phone. I checked BusyBox and indeed, the phone is no longer rooted. It looks like I have to start over. Has anyone seen any problems with re-rooting, lag fix or anything else after the update??

GaryS1004 said:
has anyone else found that there phone is no longer rooted after the AT&T JH7 update??? I noticed that the USB tether is no longer on the phone and went to use Barnacle Wifi Legacy and it told me that it only worked on a rooted phone. I checked BusyBox and indeed, the phone is no longer rooted. It looks like I have to start over. Has anyone seen any problems with re-rooting, lag fix or anything else after the update??
Click to expand...
Click to collapse
Samsung kies did the update for me when i plugged the phone into the computer. After it updated, it also broke my root and added all the att crapware again. I re rooted with no problems, and removed the bloatware. Phone is working great. I havnt really noticed any difference.

GaryS1004 said:
has anyone else found that there phone is no longer rooted after the AT&T JH7 update??? I noticed that the USB tether is no longer on the phone and went to use Barnacle Wifi Legacy and it told me that it only worked on a rooted phone. I checked BusyBox and indeed, the phone is no longer rooted. It looks like I have to start over. Has anyone seen any problems with re-rooting, lag fix or anything else after the update??
Click to expand...
Click to collapse
How did you do the update? I did it fine and root wasn't removed.

AW794 said:
Samsung kies did the update for me when i plugged the phone into the computer. After it updated, it also broke my root and added all the att crapware again. I re rooted with no problems, and removed the bloatware. Phone is working great. I havnt really noticed any difference.
Click to expand...
Click to collapse
Has anyone updated with the Voodoo lagfix in place? I can always reflash the stock JF6 and then look for the update, but i am lazy.....

I updated through kies as well. Lost my root. used one click to root again and have had no issues.

I can't re-root! I want to re-root and install Unleash the Beast... I've downloaded it, renamed to update.zip... Put it in the internal SD, went into recovery and hit re-install packages and it no longer recognizes the update. I'm going nuts here trying to re-root... comes up... E:can't open /sdcard/update.zip (no such file or directory) Installation aborted ............... Grrrrrrrrrrrrrrrrr... Help here..

That's odd. I did the OTA update by going into the system menu and selecting check for updates (I never installed the Kies software). I got the failed update message but the version showed it was JH7 after the restart, I'm still rooted and the bloatware did not reappear.
Also I never changed from the stock rom, I just rooted to get rid of the bloat and be able to sideload. I suspect those that did flash a new rom may have replaced the bloatware when they re-flashed to stock?
Hope this is helpful info for someone.
Sent from my SAMSUNG-SGH-I897 using XDA App

JasonCL said:
That's odd. I did the OTA update by going into the system menu and selecting check for updates (I never installed the Kies software). I got the failed update message but the version showed it was JH7 after the restart, I'm still rooted and the bloatware did not reappear.
Also I never changed from the stock rom, I just rooted to get rid of the bloat and be able to sideload. I suspect those that did flash a new rom may have replaced the bloatware when they re-flashed to stock?
Hope this is helpful info for someone.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I too am running the stock rom and it still killed my root.

JasonCL said:
That's odd. I did the OTA update by going into the system menu and selecting check for updates (I never installed the Kies software). I got the failed update message but the version showed it was JH7 after the restart, I'm still rooted and the bloatware did not reappear.
Also I never changed from the stock rom, I just rooted to get rid of the bloat and be able to sideload. I suspect those that did flash a new rom may have replaced the bloatware when they re-flashed to stock?
Hope this is helpful info for someone.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Same exact thing happened to me; Still rooted; Also have the JH7 suffix. Very weird, but all in all there are no changes to my phone.

How do you tell if your phone is still rooted?
(Yeah, still new to Android.)

My phone would not update...50% only whether I do it or ATT sends me the Update...Wife updated fine but was not rooted because I could not get into recovery mode until the update....then rooted hes...I Odin mine back to stock was on the phone with ATT for 2 hours.....Getting new phone

Never mind I used mini k I e s and the install went fine on both phones
No issues anymore.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

Shival said:
How do you tell if your phone is still rooted?
(Yeah, still new to Android.)
Click to expand...
Click to collapse
Open busybox, it will tell you.
Sent from my SAMSUNG-SGH-I897 using XDA App

JasonCL said:
Open busybox, it will tell you.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Wasn't sure how to just open Busybox so I just has Titanium Backup Reinstall it to make sure haha.
Thanks!

D2G 2.4.330 won't root

So, i was rooted before the update and it unrooted me. I saw a lot for people used z4root to reroot but for me it isnt working. I have ran it probably 8 or 9 times just to be sure. I says that it is accessing the shell, the the screen goes white for a few seconds and it reboots. Once it reboots i am still unrooted. I tried the temporary root just to be sure and that doesn't work either. Anyone else? The first time i rooted it via the android terminal. I havn't tried that again yet...
Thanks in advance!

make sure you are using the newest apk for Z4root which I think it is 1.3.0 and make sure usb debugging is checked in the phone settings, and also do a battery pull and put it back in and then try it again.
It worked for me after the update.

Definitely am using the newest z4 and made sure debugging was on. I just said "screw it" like 15 minutes ago and did the whole thing through the terminal again. What a pain, but at least it works. Rooted.

Z4root worked for me after the update, weird.
Sent from my DROID2 GLOBAL using XDA App

Yeah i even tried installing the app through the browser and both the official and beta releases of the sideload wonder machine. Then, just to cover all of my bases, i tried older versions of z4. I guess this thread may help others who have the same issue as me but it doesn't sound like anyone else is?

Although I had to reboot after installation before it would work.
Sent from my DROID2 GLOBAL using XDA App

Installed the update while crossing my fingers. It removed root. Just reran Z4root and then rebooted. Fine and dandy.
Sent from my rooted DROID2 GLOBAL using XDA App

[Q] update 2.1.0-2.2.3 LOST ROOT??

I did the update just now and thought everything went well. This is my first time. Someone else put infused 2.1.0 on phone and everything that goes along with that. I followed the directions in beginning of post to manually do the update. Now all my root apps are telling me i'm not rooted. I rebooted, took battery out and back in. I have read entire Infused post and no one has had this issue? Before i started i went into ROM manager and made a back up first.
Not sure what to do now??
i APPOLOGIZE if i posted this originally in wrong place.

First all, are you sure you're running the Infused.v2.2.3?? Beacuse if you are, then you're rooted.
If not, then you can simply root your phone again.
Sent from my SGH-I997 using XDA App

Yes, under setting>about phone i was running 2.1.0 and now says the update worked and i am running 2.2.3 infused. I was rooted before update now all my root apps are being denied by SU. SU was in app drarer before update and all was well. SU still in app drawrer but now not working. I installed Root Checker from mkt and it does see SU 3.0 on phone but says i never got rooted or it was done wrong. I can get a log from that app if you will be able to make heads or tails of it. I tried to install busybox and it just fails causes it says i'm not rooted. so i'm confused...i uninstalled updates to SU, that didn't work...i have looked at all the SU settings and as far as i can tell i have it set right...
as far as rooting again?? I didn't do it the first time...someone did it for me..can someone give me a link for the best way to do that...and if i have to do that..can i just do it on top of what i have now and not lose anything? I read that rooting an infuse running GB is not or close to not possible? am i wrong? I hope so.

[Q] HTC Desire S MIUI 1.11.25 - Root Access Suddenly Gone?

Hey,
EDIT!: I restored one of my backups with ROM Manager (Which still could restore ROMs? ) and i got my root access back! =)
Sorry if theres already a thread about this somewhere which Google haven't been able to find.
About a month ago i successfully rooted my phone using revolutionary. I tried out a few ROMs and ended up with MIUI 1.11.25, and suddenly i lost root access. Im not sure when this happened, it might have been when i updated from MIUI 1.11.18 to 1.11.25, which i did a couple of days ago,(I wiped dalvik cache and flashed with ROM Manager since the buildt in updater didn't work) or when i tried to update Busybox with an app from the market... :/
Weird thing is, Superuser runs perfectly normal, while almost every other root app i have tells me i need root access to use the application. I tried updating and installing the Su zip file (Binary?) and updating Superuser, but it didn't work .
Another weird detail is that root checker says "Congratulations! You have root access!" While ROM Manager can't run fix permission.
Should i reflash my ROM or a backup? Or is there some weird simple fix to this (Please!)?
Im not a wiz at rooting so if your able to, please put it in simple words
Thanks,
Mikkel

try tools>superuser>menage permissions

Adidas108 said:
try tools>superuser>menage permissions
Click to expand...
Click to collapse
I already tried to look around in the apk and it's settings, but with no luck. As I said earlier superuser runs perfectly : /
Thanks tho

[Q] OTA to 4.3 with OTA Rootkeeper worked but not really?

I have searched the forums and can't find anyone with this problem. (Although I am also having similar problems to others who took Verizon OTA to 4.3.)
I was rooted, using CWM/TWRP. I backed up my ROM, temporarily unrooted with OTA Rootkeeper, which actually worked. I got the OTA update to 4.3. Sadly, this was before word was out about all the problems. (The rootkeeper is what apparently worked because VZ pushed this update out several days ago and my prior rooted ROM would not accept the update.)
I initially got stuck on the yellow triangle "go to Verizon now" screen but managed to get past that. What is troubling me is this: When I open Super SU, I get the "binary needs to be updated. Continue?" I click "continue" but then it asks to update "normal" or "TWRP/CWM." If I click TWRP/CWM, my tries to boot into recovery but then just goes to the yellow triangle of death page again and I get stuck until I can trick past that screen again. If I click to update "normal" it tries to update but then I get "Installation failed!"
Anyone know the problem with updating the SU binary?
What is super weird, though, is that my Supermanager app is working just fine, even the root only functions such as superlauncher.
My App Quarantine application also works just fine and it is root only. But when I try to open Titanium Backup, it won't grant superuser permission. So, it seems my phone is still rooted but not really?
I also cannot boot into recovery either using hardware buttons or using ROM manager.
This is very frustrating for me.
Does anyone know how to figure out my rooted or not rooted issue?
Thanks for any help!

nessa23 said:
I have searched the forums and can't find anyone with this problem. (Although I am also having similar problems to others who took Verizon OTA to 4.3.)
I was rooted, using CWM/TWRP. I backed up my ROM, temporarily unrooted with OTA Rootkeeper, which actually worked. I got the OTA update to 4.3. Sadly, this was before word was out about all the problems. (The rootkeeper is what apparently worked because VZ pushed this update out several days ago and my prior rooted ROM would not accept the update.)
I initially got stuck on the yellow triangle "go to Verizon now" screen but managed to get past that. What is troubling me is this: When I open Super SU, I get the "binary needs to be updated. Continue?" I click "continue" but then it asks to update "normal" or "TWRP/CWM." If I click TWRP/CWM, my tries to boot into recovery but then just goes to the yellow triangle of death page again and I get stuck until I can trick past that screen again. If I click to update "normal" it tries to update but then I get "Installation failed!"
Anyone know the problem with updating the SU binary?
What is super weird, though, is that my Supermanager app is working just fine, even the root only functions such as superlauncher.
My App Quarantine application also works just fine and it is root only. But when I try to open Titanium Backup, it won't grant superuser permission. So, it seems my phone is still rooted but not really?
I also cannot boot into recovery either using hardware buttons or using ROM manager.
This is very frustrating for me.
Does anyone know how to figure out my rooted or not rooted issue?
Thanks for any help!
Click to expand...
Click to collapse
When you accepted the update, you're not supposed to do anything that has to do with CWM or TWRP. This is because the Knox bootloader has taken over.
Try rooting through the saferoot method and then use titanium backup again.
As for the binary, can't really answer that since I'm not on the Android 4.3 update (can't accept official updates because of my micro SIM card). Go to the official 4.3 discussion thread and then ask about this.
Here's a link to the thread.
http://forum.xda-developers.com/showthread.php?t=2575661