I was waiting to root my continuum until I got the new upgrade, which I expected months ago. Anyway I got the upgrade (froyo 2.2) and everything works great. I would like to root the phone, so I can tether it to my laptop.
I have seen older videos for other phones, but I was not sure they would work for the continuum, or if there is a newer easier way, as I am not tech savvy. I just want to work on my laptop as I run my kids to their after school activities.
Finally, which app works best for turning the phone into a hotspot.
Thanks in advance
The easiest way is to find superoneclick 2.3.3 That roots, nothing else.
The slightly more complicated way, is to flash a rooted version in Odin. And there are tutorials all over. You can also swing into IRC, and we can get ya going.
webchat.freenode.net
#samsung-continuum
Or....manual root
Sent from my SCH-I400 using Tapatalk
rooting problem
I was originally having problems tethering, but I figured it out. Too bad there is not an option for deleting posts, but I am excited that I can now tether.
abby_nitewolf said:
Or....manual root
Sent from my SCH-I400 using Tapatalk
Click to expand...
Click to collapse
How is that done? I've dabled with Linux on my PC so I'm familiar enough to be dangerous, but this question has been bugging me for a while now.
LGartrell said:
How is that done? I've dabled with Linux on my PC so I'm familiar enough to be dangerous, but this question has been bugging me for a while now.
Click to expand...
Click to collapse
adb devices
adb push psneuter /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 777 psneuter
$ ./psneuter
adb kill-server
adb devices
# mount -o remount,rw -t rfs /dev/block/st19 /system
# exit
adb push busybox /system/bin
adb push su /system/bin
adb install Superuser.apk
adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19 /system
# exit
adbreboot
There you go, you need a few files:
psneuter
su
busybox
Superuser.apk
Adb
But its easier and faster with SuperOneClick,
Sent from my SCH-I400 using Tapatalk
The kernel I included with the CWM recovery file will install the su binary for you. Get busybox and then install Superuser from the market and you'll be rooted.
Sent from my Galaxy Nexus
imnuts said:
The kernel I included with the CWM recovery file will install the such binary for you. Get busybox and then install Superuser from the market and you'll be rooted.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks. I've been playing with my Continuum now for several months with everyone's mods. Love the work you're all doing!
Question about installing ClockworkMod Recovery on Continuum.
Hi,
I am trying to figure out which version of CWM recovery is the appropriate, and most recent one for the continuum.
Can anyone point me to the correct file for the Samsung Continuum SCH-i-400.
Also, after I root the phone, how do I install CWM. Should I use a ROM manager, or do it manually?
Someone please help.
Thank you!!
You should try reading through the forums. I believe there is a thread that will have all necessary files.
Sent from my SCH-I400 using XDA
I used imnuts froyo rom.flashed with no problem.its not 100% stable,but it got the job done.
Sent from my SCH-I400 using Xparent ICS Blue Tapatalk 2
I figured I'd post in this thread instead of making a new one since it seems to be a similar issue. I rooted my phone ages ago right when I got it using the super one click program. Everything was working fine as far as I could tell, until I had a app on my phone tell me that it wasn't in fact rooted. I assume it was because my phone updated to 2.2.2 by it self one evening causing me to lose root. I checked with a few other apps that used to work fine (Titatium Back being one of them) which also told me my phone wasn't rooted.
I downloaded the newest version of SuperOneClick (2.3.3) and tried to re-root my phone. The program said my phone was already rooted and asked if I wanted to continue. I clicked no and then tried the 'Unroot' option. The program hung up and stopped responding so I did a factory reset and tried again. When I tried to root it again the program still said my phone was rooted and Superuser was still in my app list with no option to uninstall. I went to the market to try and uninstall that way but there wasn't an option either. I tried the un-root option again and SOC still would ended up not responding at a certain point (Installing BusyBox Step 2).
I pulled my battery and just tried to root again, it gets to the point of installing Superuser and freezes. I tried downloading an uninstall root app which didn't even show superuser. I also downloaded root explorer and tried to delete the superuser.apk from the system/apps folder and it failed to DL.
I am at a loss for what to do and would really appreciate any help in getting my phone rooted. I am in USB debugging and never installed any ROMS or anything previously. If there is any other information that would help troubleshooting this please let me know.
Vsoup25 said:
I figured I'd post in this thread instead of making a new one since it seems to be a similar issue. I rooted my phone ages ago right when I got it using the super one click program. Everything was working fine as far as I could tell, until I had a app on my phone tell me that it wasn't in fact rooted. I assume it was because my phone updated to 2.2.2 by it self one evening causing me to lose root. I checked with a few other apps that used to work fine (Titatium Back being one of them) which also told me my phone wasn't rooted.
I downloaded the newest version of SuperOneClick (2.3.3) and tried to re-root my phone. The program said my phone was already rooted and asked if I wanted to continue. I clicked no and then tried the 'Unroot' option. The program hung up and stopped responding so I did a factory reset and tried again. When I tried to root it again the program still said my phone was rooted and Superuser was still in my app list with no option to uninstall. I went to the market to try and uninstall that way but there wasn't an option either. I tried the un-root option again and SOC still would ended up not responding at a certain point (Installing BusyBox Step 2).
I pulled my battery and just tried to root again, it gets to the point of installing Superuser and freezes. I tried downloading an uninstall root app which didn't even show superuser. I also downloaded root explorer and tried to delete the superuser.apk from the system/apps folder and it failed to DL.
I am at a loss for what to do and would really appreciate any help in getting my phone rooted. I am in USB debugging and never installed any ROMS or anything previously. If there is any other information that would help troubleshooting this please let me know.
Click to expand...
Click to collapse
Here's the problem. SOC see's the superuser.apk in your app drawer, so it thinks you are still rooted. You aren't because you no longer have the su.bin (which is the reason none of the apps you have - including the 'unroot' app will work.). The fix for this is easy. When SOC says 'you are already rooted, would you like to root again', or whatever that message is, click yes. The worst thing that will happen is it will overwrite existing files with the same one (Have you ever opened a word document, and when you close it, it asks if you want to save, even though you haven't made any changes? Same thing). In this case, the files you need (su.bin and busybox) AREN'T there. So you don't even overwrite anything.
For the most part, rooting this phone is a pretty failsafe, and innocuous process. You can do it over and over again, and you won't hurt the phone in the slightest.
Txwolf1980 said:
Here's the problem. SOC see's the superuser.apk in your app drawer, so it thinks you are still rooted. You aren't because you no longer have the su.bin (which is the reason none of the apps you have - including the 'unroot' app will work.). The fix for this is easy. When SOC says 'you are already rooted, would you like to root again', or whatever that message is, click yes. The worst thing that will happen is it will overwrite existing files with the same one (Have you ever opened a word document, and when you close it, it asks if you want to save, even though you haven't made any changes? Same thing). In this case, the files you need (su.bin and busybox) AREN'T there. So you don't even overwrite anything.
For the most part, rooting this phone is a pretty failsafe, and innocuous process. You can do it over and over again, and you won't hurt the phone in the slightest.
Click to expand...
Click to collapse
Are there any other programs to use than SOC? When the dialog window pops up saying my phone is rooted I click yes, it goes through the process until it tries to install SuperUser. Once it get to that point it just freezes and is flagged as not responding by windows. Is there anything I should double check settings wise on my phone other than USB Debugging that could be causing the problem?
Vsoup25 said:
Are there any other programs to use than SOC? When the dialog window pops up saying my phone is rooted I click yes, it goes through the process until it tries to install SuperUser. Once it get to that point it just freezes and is flagged as not responding by windows. Is there anything I should double check settings wise on my phone other than USB Debugging that could be causing the problem?
Click to expand...
Click to collapse
As far as straight rooting programs, soc is the only one I know of that works. You said a factory reset didn't remove superuser from your app drawer? It should have. I spills try a factory reset in recovery, as opposed to the privacy section of settings.
The other option is to flash a pre rooted rom. A little more dangerous, if you don't know what you are doing, but gaurunteed to work. I have a territorial in this section that seems to with for everyone that's tried it. Our, if you want I can meet you in irc tomorrow evening, and we can look at it.
Sent from my SCH-I400 using Tapatalk 2
Txwolf1980 said:
As far as straight rooting programs, soc is the only one I know of that works. You said a factory reset didn't remove superuser from your app drawer? It should have. I spills try a factory reset in recovery, as opposed to the privacy section of settings.
The other option is to flash a pre rooted rom. A little more dangerous, if you don't know what you are doing, but gaurunteed to work. I have a territorial in this section that seems to with for everyone that's tried it. Our, if you want I can meet you in irc tomorrow evening, and we can look at it.
Sent from my SCH-I400 using Tapatalk 2
Click to expand...
Click to collapse
That's why I'm getting frustrated, after two factory resets through the privacy menu superuser is still in my app drawer. I think because it's flagged as a system file it isn't really touched when the phone restores it self. Are there any programs that would give me root folder access through my PC?
I really don't know much about doing anything with these phones, so I'd be a bit apprehensive about flashing new ROMs or anything that could brick my phone if I mess up. How can I reset it through the recovery menu? That at least sounds like something has a low chance of causing any irreparable damage.
I'm not sure if I think I'll be around later this evening, I'm on the east coast and don't think I'll be available until after 9pm.
Vsoup25 said:
That's why I'm getting frustrated, after two factory resets through the privacy menu superuser is still in my app drawer. I think because it's flagged as a system file it isn't really touched when the phone restores it self. Are there any programs that would give me root folder access through my PC?
I really don't know much about doing anything with these phones, so I'd be a bit apprehensive about flashing new ROMs or anything that could brick my phone if I mess up. How can I reset it through the recovery menu? That at least sounds like something has a low chance of causing any irreparable damage.
I'm not sure if I think I'll be around later this evening, I'm on the east coast and don't think I'll be available until after 9pm.
Click to expand...
Click to collapse
To reset in recovery, power down completely. Then hold the vol up, vol down, and power at the same time, until samsung logo comes up. It will color you into stock recovery (3e)
Using volume down to scroll, and camera button to select, choose wipe data/factory reset.
Next, scroll to yes, and select. Not sure if that will work to get rid of super user, but it's worth a shot.
If that direct with, let new knits, and I'll walk you through flashing a custom recovery, then a deodexed rom, if you'd like.
Sent from my SCH-I400 using Tapatalk 2
Txwolf1980 said:
To reset in recovery, power down completely. Then hold the vol up, vol down, and power at the same time, until samsung logo comes up. It will color you into stock recovery (3e)
Using volume down to scroll, and camera button to select, choose wipe data/factory reset.
Next, scroll to yes, and select. Not sure if that will work to get rid of super user, but it's worth a shot.
If that direct with, let new knits, and I'll walk you through flashing a custom recovery, then a deodexed rom, if you'd like.
Sent from my SCH-I400 using Tapatalk 2
Click to expand...
Click to collapse
I tried the wipe from the recovery menu to no luck, superuser is still in my app drawer. I'll probably have time tomorrow afternoon to jump on IRC. I really appreciate all your help so far, thank you.
Vsoup25 said:
I tried the wipe from the recovery menu to no luck, superuser is still in my app drawer. I'll probably have time tomorrow afternoon to jump on IRC. I really appreciate all your help so far, thank you.
Click to expand...
Click to collapse
I'll be around. Just pm me, when you know what time you will be on
Sent from my SCH-I400 using Tapatalk 2
Related
I have an AT&T Atrix on the 1.5.7 firmware. I do have all drivers installed, USB debugging enabled, and am using Windows 7 (dual booted on a macbook 2011).
I believe my problem is that I originally rooted it on the old firmware and then i installed the 1.5.7 OTA update. I now have the Superuser app on my phone but it does not give anything root permission. I've attempted to root again via Superoneclick but it gets hung right after pushing pneuter or gingerbreak to the phone. I have also tried unrooting but that gets hung up as well.
Can anyone give me some things to try or even walk me through something?
Thanks so much!
search the dev forum for gladroot as to why it doesn't work...
and you can try to re-root using gingerbreak, which is also in the dev forum.
basically updating without following the proper steps will not keep your root. and also.
NEVER USE SUPERONECLICK!
spend some time in the dev forums. you'll learn a lot.
Thanks! I'll look into the gladroot issue.
I have tried Gingerbreak but when I run the program with my phone connected, the spinning loading cursor displays for a second then nothing happens. I've ran as administrator but that doesn't do anything different.
It's worth noting, on 1.8.4 Gingerbreak 1.2 worked fine. I know recovery wasn't playing nice unless plugged in. That could also help. Obviously it won't hurt.
notanatheist said:
It's worth noting, on 1.8.4 Gingerbreak 1.2 worked fine. I know recovery wasn't playing nice unless plugged in. That could also help. Obviously it won't hurt.
Click to expand...
Click to collapse
There is no 1.8.4
Meh, 1.8.3 I means. Although I just noticed Greyblur takes it down to 1.5.7
CaelanT said:
There is no 1.8.4
Click to expand...
Click to collapse
Update to 1.83 and use gingerbreak. You'll need an external SD card though. It works great.
Not sure if this is the place to put this, but I'm having a similar problem, even if I got here differently.
I tried superoneclick, and I tried gladroot. In each case, the program seemed to run successfully, did everything I expected from the directions, no error messages. Claimed success at the end of the run. The superuser app is installed, but no apps are listed. When I try to run an app that needs root, like Root Explorer, it just complains that my phone isn't rooted.
I used the directions and downloads here: http://forum.xda-developers.com/showthread.php?t=1016060
Build number was OLYLA_U4_0.37.4
My phone is on Bell, so I used the Bell directions. Anyone else have or overcome this problem?
i am rooted, all root apps work.
my problem is android commander says am not rooted (windows xp)
and adb dont work
any solution?
Use gingerbreak and report back
Sent from my GT-I9100 using XDA Premium App
So I tried doing the webtop hack anyway, and when I got to this step:
Code:
adb shell
su
my phone prompted me to allow root access. Finished the process and it's working fine. Ran Root Explorer, it asked for permission, and now it works fine, too.
Maybe doing something as explicit as 'su' in adp shell was the kick in the pants it needed. Either way it's working now...
I thought maybe I'd added superuser to auto-end list, for whatever reason, but when I checked it wasn't there...
tjjensen23 said:
Use gingerbreak and report back
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
my sig says i used gingerbreak m8
Since Asus seems to have fixed the issue for the c4 serial numbers but not the few of us on c3, I'm assuming we're somewhat on our own. I don't expect asus or any devs to solve this issue(fingers crossed none the less). So I started calling asus phone support on a regular basis, I explain I'm stuck on the .17 firmware and I don't receive any ota updates. This usually leads to them telling me to update manually, to which I play the dumb computer user, "I shouldn't have to do all this complicated stuff just to get regular updates" or sometimes I said I bought this tablet instead of a computer. Mind I avoided mentioning that I tried to unlock. I always mention that I know that the issue goes beyond myself and asus solved it for the c4 users. Just today they finally caved and offered to repair it. All I have to do is pay for one way shipping to the service center. I assume they will simply exchange it though I could be wrong.
tl;dr: If you can't update and you get a network error when trying to unlock, call tech support, if they don't help, politely ask for a supervisor to show you're serious.
I also want to ask for some advice, I rooted the tablet and obviously installed the unlock apk. So if I factory reset will it be noticed? I would hate to send it in for nothing.
Factory reset should get rid of all traces of root, and since the Asus factory reset erases the SD card, the unlock app will be gone, too. Just to be sure, after the reset, use the Asus file explorer, and check /system/bin and /system/xbin for a file called "su". I think factory reset erases everything, though.
EndlessDissent said:
Factory reset should get rid of all traces of root, and since the Asus factory reset erases the SD card, the unlock app will be gone, too. Just to be sure, after the reset, use the Asus file explorer, and check /system/bin and /system/xbin for a file called "su". I think factory reset erases everything, though.
Click to expand...
Click to collapse
No it doesnt get rid if root it just deletes superuser which you must download again from market
Sent from my Optimus 2X using xda app-developers app
He's not trying to reroot. He wants to unroot, in which case he just needs to get rid of /system/bin/su.
Yep I know but I just mentioned that factory resets do not unroot
Sent from stock, rooted tf300t
If I'm rooted without superuser installed will they notice? I always thought rooting was essentially getting superuser properly installed in the root directory. But I'm certainly not the expert.
Dunno :-\
Sent from stock, rooted tf300t
marksman34 said:
If I'm rooted without superuser installed will they notice? I always thought rooting was essentially getting superuser properly installed in the root directory. But I'm certainly not the expert.
Click to expand...
Click to collapse
If there is a someone checking the tablet they will find out. If not then they wont. I don't know if they check though so it's worth a try. but if you want to be certian you can always reflash the stock rom or unroot using the supersu app (or something like it).
marksman34 said:
If I'm rooted without superuser installed will they notice? I always thought rooting was essentially getting superuser properly installed in the root directory. But I'm certainly not the expert.
Click to expand...
Click to collapse
You also need to remove the su binary from either /system/bin/su or /system/xbin/su.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Finally, i have solved it !!! A couple of days ago, i forgot my pattern and clicked on forgot pattern, but i didn't get a prompt to turn on wifi. So basically, i was stuck, unless i wanted to do a factory reset and lose all of my data. Here's my unique solution to this problem, :
First of all, you need to be rooted and to have usb debugging ON. Otherwise, it won't work.
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Here's what i did:
First, i booted the modified boot image and by using either adb or the toolkit, i pulled /data/data and /data/app to my pc.
Second, I made a full wipe and set up my N7 as usual. At this point, you need a good root file explorer in order to get to the /data folder. I installed colornote (from the app backup i made, because i wan't sure that there was a new version and,if there was, it could be a possible failure, because i wasn't sure how it would behave with the last version's data) and rebooted (in order for colornote to get into the dalvik cache).
Third, i opened up colornote's folder in /data/data and just replaced the databases folder with the one from my backup and i went to /data/dalvik-cache and deleted the corresponding color note dalvik file. Afterwards, i just rebooted and voila, all my stuff that i had written in color note was staring at me.
Now, i want to mention that i've only tried this with colornote (as it was my foremost priority to get to the essays that were stored there) and i've tried this on only 4.1.2. I can't guarantee that it will work on other apps or that you won't get damage to your precious Nexus 7, so please, proceed with caution, and don't blame me if something unexpected comes up. Good luck !!!
P.S. If you get more than one device or emulator, it's because you have bluestacks, disable or uninstall it, and you're good to go !!!
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
iAndroidOS said:
Second, you need to install wug's nexus toolkit, because it gives you an option to boot with a modified boot.img which has root privileges, go to advanced, you'll see it (if you know of any other way to boot up such an image, use it, because when you get locked out with the ,,forgot pattern'', your root won't work, that's why you need this boot image).
Click to expand...
Click to collapse
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
NIMBAH said:
If you have USB debugging enabled you can just use adb to delete the pattern file and then unlock the tab.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I tried that and it didn't work
bftb0 said:
Did you try any of the suggestions offered to you in the other thread you started on this topic?
They seem like way less effort and some of them don't involve any wiping.
BTW when you do an adb pull you lose all file ownership and mode information; it is important to restore those correctly.
You can do whatever you want with the custom recovery - it is unaffected by the lock condition. You are complicating things by using a toolkit.
good luck
Click to expand...
Click to collapse
Thank you for reminding me, it is imperative to restore the permissions
iAndroidOS said:
I tried that and it didn't work
Click to expand...
Click to collapse
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
NIMBAH said:
Weird I've done it a few times and its always worked. How did you do it ?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
I dunno, i went into adb and used the adb shell rm /data/system/gesture.key
command and as soon as it finished, i unplugged my N7 and rebooted it, and the login prompt was still there.
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
So I've read and read and read and read. Put phone in USB debugging, uninstalled antivirus, uninstalled my samsung drivers and kies, and start Casual, hit Do It and I'm stuck at
Waiting for ADB device connection. When Windows 7 recognizes the device, we will continue. Don't touch anything
Click to expand...
Click to collapse
I've been at this point for 15 minutes now, how long does this usually take or is there some issue why Casual doesn't recognize my galaxy?
Wittyusernametaken said:
So I've read and read and read and read. Put phone in USB debugging, uninstalled antivirus, uninstalled my samsung drivers and kies, and start Casual, hit Do It and I'm stuck at
I've been at this point for 15 minutes now, how long does this usually take or is there some issue why Casual doesn't recognize my galaxy?
Click to expand...
Click to collapse
I believe casual needs the drivers for the phone so I would reinstall them and start over. And you are not on MF3 correct?
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
I'm MDL on ATT. I thought Casual specifically said to delete the Samsung drivers. Or I've read so many different rooting threads I've merged them together in my head.
Install the drivers provided by Samsung on their website
Wittyusernametaken said:
I'm MDL on ATT. I thought Casual specifically said to delete the Samsung drivers. Or I've read so many different rooting threads I've merged them together in my head.
Click to expand...
Click to collapse
The drivers are required for Windows to access your phone properly so you need them.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Okay, that worked, now I seem to be way in over my head. When it finished it said to make sure I install Super User after I reboot into Android. I don't even know what I'm looking at on my phone tbh. Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot? I missed the tutorial that explained all this somehow? What next? I'm lost. Sorry to sound like a dumb noob. I really did do tons of reading before I started.
Windernametaken said:
Okay, that worked, now I seem to be way in over my head. When it finished it said to make sure I install Super User after I reboot into Android. I don't even know what I'm looking at on my phone tbh. Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot? I missed the tutorial that explained all this somehow? What next? I'm lost. Sorry to sound like a dumb noob. I really did do tons of reading before I started.
Click to expand...
Click to collapse
Go ahead and install the SuperSU app from the play store and then check out this guide.
http://forum.xda-developers.com/showthread.php?t=2314494
Read up. Understand. Enjoy.
Cheers
Wittyusernametaken said:
Okay, that worked, now I seem to be way in over my head. When it finished it said to make sure I install Super User after I reboot into Android. I don't even know what I'm looking at on my phone tbh. Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot? I missed the tutorial that explained all this somehow? What next? I'm lost. Sorry to sound like a dumb noob. I really did do tons of reading before I started.
Click to expand...
Click to collapse
Okay first go to the play store and het SuperUser or SuperS.
2 what you are looking at is twrp recovery. Install is where yoyo will install Roms/kernels and such.
Wipe will WIPE DATA/FACTORY RESET.
Advanced is none menus of things to do.
Reboot will give a couple options like reboot system etc.
Sorry I am having a hardboiled right now typing with one hand/arm so hopefully the rest you can figure out
Sent From RockRatts Work Phone
Wittyusernametaken said:
Okay, that worked, now I seem to be way in over my head. When it finished it said to make sure I install Super User after I reboot into Android. I don't even know what I'm looking at on my phone tbh. Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot? I missed the tutorial that explained all this somehow? What next? I'm lost. Sorry to sound like a dumb noob. I really did do tons of reading before I started.
Click to expand...
Click to collapse
You are in TWRP which is a custom recovery. Never perform an internal wipe in twrp, it will require you to type in "yes" and will require you to Odin your phone back to stock. Also, never flash a non loki'd kernel if you have a I337. When you boot back into your ROM you will need to see if super user is installed but if not you need to download the one by ChainsDD in play store. This will be the final step to having root access. To exit twrp just go to reboot and click system. To manually enter two you hold down the power button, home button, and the volume up button at the same time. If I were you I would read more about the flashing guides in the general section. But on AMDL the phone is just about unbrickable but be careful and take your time and read read read.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Tylorw1 said:
You are in TWRP which is a custom recovery. Never perform an internal wipe in twrp, it will require you to type in "yes" and will require you to Odin your phone back to stock. Also, never flash a non loki'd kernel if you have a I337. When you boot back into your ROM you will need to see if super user is installed but if not you need to download the one by ChainsDD in play store. This will be the final step to having root access. To exit twrp just go to reboot and click system. To manually enter two you hold down the power button, home button, and the volume up button at the same time. If I were you I would read more about the flashing guides in the general section. But on AMDL the phone is just about unbrickable but be careful and take your time and read read read.
Tylorw1
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for the replies, feeling less panicky. When I hit reboot and click system I get "Fix Superuser Permissions? Root permissions apear to be lost. Fix root permissions now? (Fixes Permissions on su binary and app)" and then gives to options to Do Not Fix or Swipe to Fix Root.
Which is the right one to get me rebooted to I can download the super user thing in the Play store?
TY