Working Superuser for TB Sense - Thunderbolt Android Development

This is actually relevant to more than just the Thunderbolt. It fixes Superuser problems with numerous newer Sense releases.
http://forum.xda-developers.com/showthread.php?t=886999
My su binary is already being provided via the root thread but the matching Superuser is not. Without the matching patched Superuser, you'll see FCs when apps request root if the Superuser app itself is open.
Just apply the update zip from the aforementioned thread to fix it. ROM builders should use my patched version as well.

Please update to this, I will be fixing the tutorial as soon as I can, and noting it here.

Rafi, good to see you on the bolt. Looks like we will get a virtuous Rom too. Ran your Rom on the inc till I got run over by the desire z, hd craze.
Sent from my Thunderbolt!

Hmm, not sure if I should do this. I ran fix permissions in Rom Manager and it seemed to take care of all the problems. Everything's been working fine since then. What do you guys suggest?

i see no reason to mess with it if your set up is currently working

jacobk said:
i see no reason to mess with it if your set up is currently working
Click to expand...
Click to collapse
I agree - however, in my case, nothing was solving the FC's - so I put in this SU and all is right with the world.
I think it's worth trying if all other permissions methods are failing - it certainly "feels" more stable.

This fixes su issues while the superuser app is open.
Flash it.

Thank you rmk & jcase

even aftere re rooting fix my su issue i ran this and i feel su runs wayyyyy smoother now for apps that need su.

jacobk said:
i see no reason to mess with it if your set up is currently working
Click to expand...
Click to collapse
There is simply no way any newer Sense ROM works correctly without this patched version. You *will* ultimately encounter issues.
Don't believe me, try this. Open up the Superuser app itself, connect via adb shell, su system, su root. Observe hang. This is just an example, there are numerous other ways to have the issue occur.

RafficaX said:
even aftere re rooting fix my su issue i ran this and i feel su runs wayyyyy smoother now for apps that need su.
Click to expand...
Click to collapse
Good. maybe you can apologize now in the debloat rom thread instead of trying to smear my name.

can you just post it in here...i dont like guessing games...i see 2 links to pull requests on github...i dont know wtf that means. some of us dont speak computer 120% fluently..

MYxdaUSERNAME said:
can you just post it in here...i dont like guessing games...i see 2 links to pull requests on github...i dont know wtf that means. some of us dont speak computer 120% fluently..
Click to expand...
Click to collapse
Haha scroll down the page!! There's a flashable zip
sent from my Thunderbolt

for christ's sake...big blue letters. i thought that was the top of his sig..but he lost me at github.
good to go...i do remember a few force closes that never amounted to anything serious last night...

doodoostains said:
Hmm, not sure if I should do this. I ran fix permissions in Rom Manager and it seemed to take care of all the problems. Everything's been working fine since then. What do you guys suggest?
Click to expand...
Click to collapse
This was working for me until I rebooted. Once I did, everything was back to how it was.
I just applied the patch, restarted. VOILA! SU is working again. Thanks rmk40!

Superuser is acting up after working fine earlier. How can i boot into clockwork without rom manager anyone? thanks

frodsteamin2 said:
Superuser is acting up after working fine earlier. How can i boot into clockwork without rom manager anyone? thanks
Click to expand...
Click to collapse
Turn off phone. Hold volume down when booting up.
Sent from my ADR6400L using XDA App

Was able to get into CWR after a reboot, flashed. Thank you!
Edit * this fixed all my issues. . Thanks again

evilmunkeh said:
Turn off phone. Hold volume down when booting up.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Thank you for the response, my newbness was the problem as there was a file on sd card that keep trying to install when trying what you mentioned above.

Still getting FC's in SU after flashing... Did I miss something?
Never mind, fixed after running a program that required root.
Thanks!
Sent from my ADR6400L using XDA App

Related

Unrevoked not working for OTA?

Anyone else having this problem?
I'm using Unrevoked 3.1 on Windows XP.
I've got USB debugging on and the drivers installed.
The phone reboots into HBoot but then never goes into recovery. Just reboots.
Anyone else having this problem? It is definitely screwing me over for 2.2 haha.
andrewzpsu said:
Anyone else having this problem?
I'm using Unrevoked 3.1 on Windows XP.
I've got USB debugging on and the drivers installed.
The phone reboots into HBoot but then never goes into recovery. Just reboots.
Anyone else having this problem? It is definitely screwing me over for 2.2 haha.
Click to expand...
Click to collapse
Is superuser permissions installed? And if so what do u get when u open terminal emulator and type Su?
Sent from my ADR6300 using XDA App
tcberg2010 said:
Is superuser permissions installed? And if so what do u get when u open terminal emulator and type Su?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Superuser will not install. Unrevoked just reboots the phone it seems... never going into the custom recovery or flashing SU.
Which is my problem haha. I want 2.2 but can't flash it without root.
If I lose root because of this and am the only one I'm not going to be a happy camper lol
Possible
After reading 700+ pages of the other thread I have decided to steer clear from the buggy-beta and wait for the OTA, but I have had trouble with v3.1 and a regular reboot, so I wanted to chime in with 1 question:
Is your phone hot while this is happening?
I returned my Incredible due to excessive heat triggering reboots. When the phone was in the warm-to-hot zone, I could NEVER get into recovery. I could get into HBOOT, choose recovery, and then it would do 2 reboots, the second one being a regular.
Only way i could get into recovery was with a fully charged overnight battery, first thing in the morning (phone nice and cool).
Just got into it. used the custom image... the new 2.5.0.4 (if I'm not mistaken).
It was weird, and it may not be the image... it may have just taken like 10 tries to do it.
I'm not even wasting my time loading the OS... just putting on Froyo right now while in clockwork.
Crossing my fingers that it loads!
andrewzpsu said:
Just got into it. used the custom image... the new 2.5.0.4 (if I'm not mistaken).
It was weird, and it may not be the image... it may have just taken like 10 tries to do it.
I'm not even wasting my time loading the OS... just putting on Froyo right now while in clockwork.
Crossing my fingers that it loads!
Click to expand...
Click to collapse
Create nandroid backup before u do anything else, just in case.
Sent from my ADR6300 using XDA App
tcberg2010 said:
Create nandroid backup before u do anything else, just in case.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I have backups pre-OTA.
andrewzpsu said:
I have backups pre-OTA.
Click to expand...
Click to collapse
As long as u have extra protection in case the first layer fails you'll be alright
Sent from my ADR6300 using XDA App
WARNING!
Ask your questions in correct thread. If a new thread must be started, and a question is asked, use the General section. Thanks
seemed to work for me
having trouble after i got the new ota loaded. I get to the reboot phone reboots then unrevoked says waiting for phone to reboot any ideas didn't have this problem before?
edit: never mind got restarted computer life is good now
I am having the same issue. I have installed the drivers, then when I run the reflash tool it reboots my phone after about 3 seconds and loads up HBOOT and then from there it reboots my phone and the reflash tool either says "waiting on phone to reboot" or "installing image" or something like that but it just sits there for hours and doesn't progress. I have debugging enabled.
To add a little history, I already rooted using the hard method awhile back and then unrooted. Now I am trying to root again and can't.

Trouble with root

Ok, so I ran the superoneclick and it says it was successful and I have superuser on my phone but if I try to use any root programs like titanium backup it says I'm not rooted, any suggestions?
Super oneclick only gives you temporary root, so after you reboot you loose root. On most phones it gives you permanent root but the way the kernel is designed on the intercept it doesn't work. There is an app in the intercept 2.2 development thread at sdx-developers that gives you permanent root and flashes cm recovery to allow you to flash zips to install mods roms and themes!!easy to use!!
Sent from my SPH-M910 using Tapatalk
Jstew83 said:
Ok, so I ran the superoneclick and it says it was successful and I have superuser on my phone but if I try to use any root programs like titanium backup it says I'm not rooted, any suggestions?
Click to expand...
Click to collapse
Would highly recommend you click over to the dev section - link posted that will give you perma root. Quite simple to do.
b_randon14 said:
... the way the kernel is designed on the intercept it doesn't work. There is an app in the intercept 2.2 development thread at sdx-developers that gives you permanent root and flashes cm recovery to allow you to flash zips to install mods roms and themes!!easy to use!! ...
Click to expand...
Click to collapse
I was wondering why my Intercept wasn't holding root... one thing about that app: you have to change the .ch (or is it .sh) files to use stl5. They're written for stl9.
Also, I've used this app about 50 times on my Intercept and it's not working. Its just adding more files to my phone, causing it to slow down more. If it doesn't work and you want a break, use adb shell to delete the files added. I tried using SuperOneClick in combination with the SDX app and that didn't work either. My suggestion is to use SuperOneClick for temp root and flash a rooted kernel and ROM, which is what I'm going to do at some point.
Sent from my SPH-M910 using Tapatalk
caderyn19 said:
I was wondering why my Intercept wasn't holding root... one thing about that app: you have to change the .ch (or is it .sh) files to use stl5. They're written for stl9.
Also, I've used this app about 50 times on my Intercept and it's not working. Its just adding more files to my phone, causing it to slow down more. If it doesn't work and you want a break, use adb shell to delete the files added. I tried using SuperOneClick in combination with the SDX app and that didn't work either. My suggestion is to use SuperOneClick for temp root and flash a rooted kernel and ROM, which is what I'm going to do at some point.
Sent from my SPH-M910 using Tapatalk
Click to expand...
Click to collapse
Hmmmm sounds like you are making things more complex then they actually are - took me about 5 seconds to gain perma root without any file name changes.
entropy.of.avarice said:
Hmmmm sounds like you are making things more complex then they actually are - took me about 5 seconds to gain perma root without any file name changes.
Click to expand...
Click to collapse
That's me! I did that with my Wii also lol!
The OneClickRoot program just isn't working for me. I only mentioned the stl5 thing because someone else mentioned it in the SDX thread hosting this program, figured I'd mention it because it's several posts in. I changed mine because SuperOneClick said my mount point was /.../.../stl5 (the ...s are directories I don't remember).
[EDIT] Instead of doing all that, try the post below me. if that doesn't work, just break it down and do it manually... Flash a rooted kernel, then recovery, make your backups, then flash custom roms. I was using all stock when I first wrote the post, but now I'm using SlapKernel, bROM, and CM01 recovery. I WAS making it too complicated lol!
caderyn19 said:
That's me! I did that with my Wii also lol!
The OneClickRoot program just isn't working for me. I only mentioned the stl5 thing because someone else mentioned it in the SDX thread hosting this program, figured I'd mention it because it's several posts in. I changed mine because SuperOneClick said my mount point was /.../.../stl5 (the ...s are directories I don't remember).
Click to expand...
Click to collapse
So strange. Try this: worked for me, all you need to do is check allow non market programs in your settings, download and install this apk - run it and gain perm root. Does this work for you?
http://forum.xda-developers.com/showthread.php?t=1135825
yes that may work
caderyn19 said:
That's me! I did that with my Wii also lol!
The OneClickRoot program just isn't working for me. I only mentioned the stl5 thing because someone else mentioned it in the SDX thread hosting this program, figured I'd mention it because it's several posts in. I changed mine because SuperOneClick said my mount point was /.../.../stl5 (the ...s are directories I don't remember).
[EDIT] Instead of doing all that, try the post below me. if that doesn't work, just break it down and do it manually... Flash a rooted kernel, then recovery, make your backups, then flash custom roms. I was using all stock when I first wrote the post, but now I'm using SlapKernel, bROM, and CM01 recovery. I WAS making it too complicated lol!
Click to expand...
Click to collapse
damn glad you got it running - you are further then me now on my Intercept - all I have is root so I can use my 3g as a wifi hotspot for my Acer Iconia a500 tablet need to look into custom roms for the intercept, the Virgin Mobile stock 2.2 is so slow :-(
Stock is somewhat slow. Make sure you read the directions though with rom flashing. I messed up my phone for a few hours from not doing the steps correctly with a certain rom. All sorts of fun! I flashed a rooted stock kernel from sdx, as well as stock rom (idk if roms are rooted? Its depends on the kernel right? Ill google it...) and a kernel package that has some tweaks to the stock (or any) kernel. I gotta say, adding Zeam launcher to a rooted and tweaked stock is running quite well for me.
Sent from my SPH-M910 using Tapatalk

New superuser update fouled up my phone

So, I was excited to see a new version of SuperUser available yesterday. I updated and much to my surprise it screwed things up on my atrix pretty good.
Now it doesn't even prompt me to allow permissions for some apps, and just auto denies them the perms. In SuperUser app it self those apps dont show up, so I cannot manually allow them ( even though they are being logged as denied).
Im no idiot.. I can usually work around most problems I encounter.. so I go into preferences and set it to "auto-allow " everything SU permission. The apps STILL get denied. I have uninstalled and reinstalled those apps. No luck there. I guess I could try uninstalling and reinstalling SuperUser but I'm not sure that will work either.
Normally I wouldnt even care, but it just so happens the apps its screwing up on are Adfree and LBE privacy guard. I am not pleased. Looks like I may have to restore this month old nandroid backup I have.
Anyone else had any of these issues with the update??
i got the update (and also an updated su) and everything is working fine.
Everything is working fine for me... (Stock Froyo) *knock on wood*
Sent from my MB860 using xda premium
i dont rly like the update either but it is working but it dont show the apps in the app list
no problems here
I had a problem the other day regarding a binary update with superuser and gave up and reloaded my Rom, works fine now. Luckily backup worked better than I thought and back to normal already.
Sent from my MB860 using XDA App
Also no prob with su.
Instead of reinstalling your old backup, just uninstall the update in the app manager.
If you update it'll say at the bottom "Was that cool Do it again?" Click do it again and it will then prompt you for SU access. I haven't had any issues yet.
Im aquired a copy from CWM Rom Manager and I am on a stock 2.2 rooted/unlocked rom. It works fine.for me and with Super User Elite from the market it really works lovely.
Sent using the phone with the biggest balls....Atrix 4G
No problems for me.
JasonRand1 said:
I had a problem the other day regarding a binary update with superuser and gave up and reloaded my Rom, works fine now. Luckily backup worked better than I thought and back to normal already.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I had a problem with SU Binary as well. RE-Rooting the device worked for me.
Mine is fine but the apps dont show in the app list it is the free ver does anyone else have this prob

ICS ROM's break root

I've been messing with my phone for about 2 days now since I've gotten it. I haven't had any issues and have installed a ton of ROM's. However I keep having one issue. Every time I flash an ICS rom I keep getting denied root access. I've tried every ICS ROM available and every one does it to me. None of the gingerbread ROM's have broken it. It installs just fine, but any time I try to do anything that requires superuser permissions they get denied, but if I flash back to a 2.3.x ROM I'll have complete root access.
It doesn't seem to be an issue for anyone else from what I've been reading. I'm permanently rooted with gfree and have the good eMMc chip. Is this just normal with ICS ROM's or is there a fix I am too blind to find? Sorry if this is a dumb question. I've come from the Motorola Triumph from Virgin Mobile that's practically rooted out of the box.
Sounds like your not fully wiping everything. The ics roms had root problems when they updated to 4.0.4 but was fixed and shouldn't have that problem now. Use 4ext recovery if your not already using it. use the "wipe everything but sd" option and try a ROM again.
Sent from my HTC Glacier using Tapatalk
Well I'm not sure if this would help but when you flash an ics rom go to your apps through the settings, find superuser, click force stop then clear the cache...then try opening up terminal emulator and tryping SU and hit enter and press allow.
Hope this works for you, I remember a long time ago it was a problem with one of the miui roms for the mytouch.
Don't forget to hit thanks if it worked
Sent from my HTC Glacier using xda premium
mustk1ll20 said:
Sounds like your not fully wiping everything. The ics roms had root problems when they updated to 4.0.4 but was fixed and shouldn't have that problem now. Use 4ext recovery if your not already using it. use the "wipe everything but sd" option and try a ROM again.
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
This was actually the first thing I tried. I use 4ext and I have always used the wipe all (but sd card) option. I also didn't use Titanium backup to restore apps or anything like that so I'm not sure what it could be.
707BeastMode707 said:
Well I'm not sure if this would help but when you flash an ics rom go to your apps through the settings, find superuser, click force stop then clear the cache...then try opening up terminal emulator and tryping SU and hit enter and press allow.
Hope this works for you, I remember a long time ago it was a problem with one of the miui roms for the mytouch.
Don't forget to hit thanks if it worked
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
After doing this I have the same issue I have every time I've tried to check my root status through the terminal emulator. It always says "Permission Denied" and it won't even bring up the superuser box.
(Superuser is still in my applications though, and when I open it up it has been logging the denied attempts in terminal emulator.
This happened on Ice Cold Insomnia.
Huh, idk what the problem is, maybe try re-rooting the phone with a different method? What method did you use?
Sent from my HTC Glacier using xda premium
gfree
Try changing su app to automatically allow su permissions instead of prompt to see if su is even granting access.
Sent from my HTC Glacier using Tapatalk 2
707BeastMode707 said:
Huh, idk what the problem is, maybe try re-rooting the phone with a different method? What method did you use?
Click to expand...
Click to collapse
The rooting method has absolutely nothing to do with root privileges on custom ROMs flashed through custom recovery.
Actually, the rooting method doesn't even matter. All that matters is S-OFF. And since the OP has S-OFF, no re-rooting will possibly do him any good.
OP, many of ICS ROMs moved to SuperSU instead of Superuser app. Maybe that causes you problems.
eqjunkie829 said:
Try changing su app to automatically allow su permissions instead of prompt to see if su is even granting access.
Sent from my HTC Glacier using Tapatalk 2
Click to expand...
Click to collapse
Same problem, Permission Denied.
Jack_R1 said:
The rooting method has absolutely nothing to do with root privileges on custom ROMs flashed through custom recovery.
Actually, the rooting method doesn't even matter. All that matters is S-OFF. And since the OP has S-OFF, no re-rooting will possibly do him any good.
OP, many of ICS ROMs moved to SuperSU instead of Superuser app. Maybe that causes you problems.
Click to expand...
Click to collapse
So would I just install SuperSU then? I downloaded it but it didn't make a difference.
EDIT: I flashed Zips Creamed Glacier and SU is working fine. I guess I'll just stick with this one. Thank you to everyone for your suggestions.

I'm not rooted and I keep getting Custom Status...why?

I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
polish_pat said:
I really don't understand this phone. I've been on a quest of 2 weeks to be rooted and on official status, finally i gave up everything because i was not able to have both. Finally i flashed factory rom through odin, formated a couple of time the phone, and i got back official status. I much rather gave up a few rooting benefits then OTAs, at least until they fix the phone's problems.
Well, this morning, i wake up, and that DAMN custom status is back....WHY????????? I'm not rooted, i'm 100% stock, i checked with rootchecker and my phone doesnt have root....then why does that damn status keep coming back??? There is obviously something else that triggers it......man i'm so deperate! Please help!
Click to expand...
Click to collapse
It's really not as big of a deal as you are making it. The way I see it you have 2 choices.
1. Exchange the phone for another (that might do the same thing)
2. Ignore it.
Just like every other Galaxy phone out there (you remember the skyrockets, right?) not all of them react the same way. Some get custom, some do not. Others switch back and forth.
I've noticed you have made many posts about this same thing. If someone hasn't provided a concrete answer that has worked for you by now it just doesn't exist yet. No matter how frustrated you are over it, making new posts about it are not going to change anything.
Its up to you if you keep wanting to post about it (I'm not complaining about it), I just don't think it's going to get you any more information at this point than what already has been said. Maybe I am wrong and someone will tell you exactly what to do to make it "official", but I haven't seen anything yet.
Good luck and try not to let it get to you so much.
euhhh no, they are not about the same thing, one was about retaining officiel while rooted, and now that i've given up on that, i still have a custom status, the reson why i dont report there is becuase poeple have seen the thread and will not go back, so in order to attract new poster i create a new thread. And no, i dont want to ignore anything because i want OTAs. If you have a problem with that, dont answer
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
peoples_flip said:
You need to re-root (motochopper method) and then using a file browser such as "root explorer" go to:
/System/Xbin
Once you have navigated to the above path, delete these two files:
"su" and " busybox"
Once you've deleted the two files, uninstall SuperSU and reboot your phone twice.
You'll notice that after the second reboot the "custom" will revert back to "official"
Sent from my SGH-I337M using Tapatalk 2
Click to expand...
Click to collapse
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
I went through what you have, I completed a full stock restore via Odin and these two files I mentioned were still there. Use a file explorer and go to the path I suggested and you'll see them there
Sent from my SGH-I337M using Tapatalk 2
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
I don't believe the current Odin contains a pit...or whatever it is that formats the phone...
So all Odin is going to do is reinstall everything...so replace missing or corrupted files - it will not delete your new files
Formating from the phone itself won't delete everything...its just going to delete your apps, app data, and cache
Therefore doing multiple factory resets and odins likely will not remove all traces of root...someone correct me if I'm wrong but that's what I believe is the case...
Sent from my HTC PH39100 using Tapatalk 2
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
AT&T software update push or download will not work for your phone if it is showing custom. People like to be getting these stock updates as soon as they are published by the provider, not when some good heart packages a new ROM using them.
polish_pat said:
correct me if i'm wrong but these 2 files, should not even exist if you install a firmware thru odin and format the phone a few times...
Click to expand...
Click to collapse
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Thanks.
TheAxman said:
Good info here, I did this procedure as you described, and yes, official is showing, but you can NOT delete su, it will unroot. I just renamed the 2 files, and root was gone. renamed su back, re-installed su superuser, and reboot, root is back with official status.
Click to expand...
Click to collapse
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Same here
CAG-man said:
I tried this procedure and still have custom after 2 reboots. I renamed su and busybox then verified root was gone. Then renamed su back. I guess the part I was confused at was reinstall super user. Do I uninstall then re-install from play store?
Thank you.
EDIT: Followed my thought of uninstalling and re-installing through play store and still get custom.
Click to expand...
Click to collapse
Correct. the one from the playstore updates the binaries. then uninstall.
---------- Post added at 07:11 PM ---------- Previous post was at 07:10 PM ----------
XGhozt said:
Is there a reason why it showing custom is a bad thing?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Good answer, why does it matter if it says custom? whats the big deal here. If you are wanting the update, why not just wait until a dev does what they need to do to it, and flash it later. I updated 1 time in a year on my GS3, and never did it again. When a new rom is developed, it usually is a base from the update...so....
Had a posting. Could not delete
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
Mr. Q said:
Well, you do not have to install the ZIP, but instead, do the following:
- Install SuperSU from the market
- Grant SuperSU root access
- When asked to update su-binary, please do
- Remove SuperUser from your device
- Reboot (I read two reboots are needed to make the icon disappear again.)
Click to expand...
Click to collapse
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
CAG-man said:
Did some digging in the forums and I am rooted with OFFICIAL.
This is how to do it. Taken from this thread.
http://forum.xda-developers.com/showthread.php?t=2252248&page=42
My process completely.
Remove Busybox from system/xbin (or your busybox backup)
Install SuperSU by Chainfire from playstore.
Open SuperSU and Grant SU root
Update the binary
Say yes to try to remove other root apps. This will remove superuser.
reboot
reboot
On second reboot you will notice the Galaxy S4 logo returns and Official Status has returned.
If it has not returned then some other issue is causing the custom status.
Click to expand...
Click to collapse
I was able to get official and root, the problem is it comes back after 2-3 days, please report back on sturday and tell me if its still official, also this logo you are talking about, i never see it because im in canada and my bootloader is unlocked already
EDIT: Ok, so once i was rooted and installed SuperSU and got superuser out, i deleted busybox, i then rebooted ONCE and got official just like that. I also took out SD card because i know this screwed me up last time. I'm happy because i'm rooted and official, but i'm not convinced this will last very long because it has never lasted more than 2 days. I will report back in a few days. Thanks Cagman, you've been very helpful and what you told me to do did the best results for me, i just hope they last
so far so good!!!:fingers-crossed:
polish_pat said:
so far so good!!!:fingers-crossed:
Click to expand...
Click to collapse
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
joeybear23 said:
Try rebooting a few more times.
For about a week i was getting the custom status every 2nd or 3rd reboot, and then eventually it just went away...
Click to expand...
Click to collapse
Hahaha, i did it!! earlier this afternoon i sort of challenged my phone by rebooting it constantly, ive rebboted probbaly 20-30 times and its still official, i guess deleting busybox sealed the deal!!
Polish_pat I am glad I was able to help. You are welcome. Congratulations.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Categories

Resources