Alright guys....Need help. How do I unroot from Super OneClick. I have the official TMobile 2.2 ROM as OTA..however it's failing because its checking to see if its rooted. Pleasant. So If someone could point me in the right direction it would be appreciated.
you sure its 2.2? OTA?
Yup. 100% Sure. 112MB file download. File is called Blur_Version.3.6.360.MB525.T-Mobile.en.US.zip with a Blur_Version.3.6.360.MB525.T-Mobile.en.US.crc file as well. Build.prop indicates that it is 2.2.1 /3.4.2-107-JDN-9/34.4.9. Getting completely hung up on this Status 7 error though. It is picky as hell, and I don't have a out of the box backup I can use to try as stock. It is definitely checking files though. It's like christmas and staring at your presents knowing what it is, but you can't unwrap it. Uggh!!
Root can't be your problem. I've updated to that release; Android 2.2.1, Blur 34.4.9, Build # 3.4.2.107_IDN-9, while my system was rooted. My phone was quite customized (Go Launcher with some "foreign" widgets and no Blur apps/widgets except for the Email app to get at my work e-mail) and everything came up OK. I was rather surprized how smoothly it all went. All my data (seemed to be mostly e-mail) had to be re-synched (this happened automatically), and it took one reboot to clear a message about non-Moto battery that was displayed after the first boot. Basically it all is where it was, except, of course, for root (I tried the latest, 1.7, SuperOneClick but it's looping no matter what I do).
Good luck.
[Added]
Well, well. It turned out that even though it seemed that SuperOneClick was failing (looping at trying to mount a partition R/O) it actually it did it's job! I just fired up RootExplorer and lo and behold a confirmation from Superuser for root popped up, got accepted, and I can start renaming the bloatware again. Woo hoo!
For me it ended up being the root. I was able to unroot with Z4root, and as soon as I did no more issues. I ended up saying screw it and wiped my phone all the way back to factory. Figure it's just better to rebuild it all cleanly and be done with it. I'm just happy its an official rom now.
mind posting a nandroid back up please?
It's really insane to sanction against rooting a phone. I can't image a computer denying me administrator's rights.
runeblade said:
How do I unroot from Super OneClick.
Click to expand...
Click to collapse
You can simply do it manually using Root Explorer. delete followings AS ROOT USER and reboot. that's all!
1. /data/data/com.noshufou.android.su
2. /system/app/superuser.apk
3. /system/bin/su & busybox
Also, it can be done via adb connection.
adb shell
$ su
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# rm -r /data/data/com.noshufou.android.su
# rm /system/app/superuser.apk
# rm /system/bin/su
# rm /system/bin/busybox
# reboot
I second this.
jboogie3 said:
mind posting a nandroid back up please?
Click to expand...
Click to collapse
Related
Root Explorer doesn't work. Root manager does. If you want to save the $2.55 use ADB
EDIT: Titanium back up is free and also works for removing files although the backup portion seems a little wonky at times. That is an easier way to remove apps the rest of this is obsolete but keeping it here for reference.
/**
YOU MUST ALREADY BE ROOTED TO DO THIS
This is very easy. It assumes you have rooted thus you have the SDK / ADB drivers already installed.
Your phone should be booted up and in android
Connect to your pc and open your command window and do the following:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Adam>cd..
C:\Users>cd..
C:\>cd androidsdk (your directory may be named differently)
C:\Androidsdk>cd tools
C:\Androidsdk\tools>adb shell
$ su (notice the echo on successful command and the change to # meaning you have root access now)
su
# mount -t rfs -o remount,rw /dev/block/stl9 /system
mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /system
cd /system
# cd /system/app
cd /system/app
Once here you can do a "ls" which is LS but all lower case and that will give you a list of what is in the current directory.
The "rm" command is used to remove items. What follows is the file name which is case sensitive.
# rm TouchWizCalculator.apk
rm TouchWizCalculator.apk
# rm TouchWizCalculator.odex
rm TouchWizCalculator.odex
#
*/
Click to expand...
Click to collapse
What can be removed? Some sites with info and lists of apps:
http://forum.sdx-developers.com/android-2-1/(list)-apk's-and-odex's-safenot-safe-to-delete/
http://androidforums.com/samsung-moment/112896-guide-removing-stock-apps.html
I dont suppose their will be a youtube video for rooting the Epic will there?
or is gaining root access the same on all android 2.1 phones?
Im new to Android & want to get rid of some sprint apps but I dont want to brick my phone at the same time..
Great post. Personally, I just use Root Manager. It is really easy and only costs a couple of bucks in the market. Plus it has the added advantage of backip up the apps as you remove them, and you can restore them if you wanted to, like say you wanted to take your phone back to the store and you wanted it more "factory" before you go.
chris5h said:
Great post. Personally, I just use Root Manager. It is really easy and only costs a couple of bucks in the market. Plus it has the added advantage of backip up the apps as you remove them, and you can restore them if you wanted to, like say you wanted to take your phone back to the store and you wanted it more "factory" before you go.
Click to expand...
Click to collapse
So what you're saying is that I can download Root Manager from the market having done nothing else to my phone and delete some Sprint apps?
Although the SDX App Removal Tool was written for the Samsung Moment, but it works to remove any unwanted stock apps from the Epic.
Here's a download.
Is there anything unsafe to remove like Samsung widgets ect?
pjree said:
Although the SDX App Removal Tool was written for the Samsung Moment, but it works to remove any unwanted stock apps from the Epic.
Here's a download.
Click to expand...
Click to collapse
this didn't work for me..
WhiteWidows said:
Is there anything unsafe to remove like Samsung widgets ect?
Click to expand...
Click to collapse
I deletes all the samsung widgets and the touch wiz launcher without problems. lost all the colorful wallpapers that come with the phone thought, oh well I don't really use them anyways
Sent from my SPH-D700 using XDA App
I was able to finally remove amazonmp3.apk using Root Manager, but I selected the apps I wanted to remove and had it back them up first, it said it completed, but no files show up when I try to restore... any ideas?
I am sorry if this has been covered someplace. ive searched for a while but cant find any answers that help me out.
also, i would like to thank the android developer community. you guys stinking rock. i love looking at all the stuff you have worked on and released. its cool that android users are willing to put in a lot of hard work and help other users out.
Problem: any app that requires super user to work has stopped working. my wireless tether wont start. shoot me wont work. type fresh wont either.
it worked about an hour ago. i did a nandroid. flashed a font. realized i couldnt use my root apps. restored just now and still cant use them. it seems odd that it suddenly stopped. could messing with the fonts damage something someplace?
i am thoroughly confused. i am a relative noob with all this developing stuff, but i have worked thru some problems on my own, with the help of guides and searches on here. i am comfortable with adb and all, but this confuses me pretty good.
any help or suggestions?
thanks in advance!
edit: ok, i did this
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
in adb. that restored wireless tether and shootme, but i still cant use type fresh. have i done something weird? and did flashing a font cause all that?
When you restored did you wipe everything first? it may have saved permissions that were changed when you installed the font... I would try a complete wipe and then restore (assuming you have a nandroid backup or something like it).
I got my replacement phone and need to return the original, I already asked for help here - http://forum.xda-developers.com/showthread.php?t=827229 but didn't find mch luck
My issue is that I unrooted and the Superuser app is still there on my phone and I tried to follow the instructions
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
I downloaded Terminal app but I type "su" it says invalid command
I also have downloaded the Stock Rogers ROM
Can someone please please either tell me how to
1) Remove Superuser app form the Phone
OR ( better yet in your opinion )
2) Put the stock back ( but have no clue how to do this )
I have tried googling, searching but there is no simple answer and since this will be returned, I ave limited time
So any kind soul can help a fellow Captivator
Have you tried a factory data reset??
You can do that by going to settings>Privacy>Factory Data Reset.
Edit to add: How did you un-root?
Also, how did you root?
2nd edit: Per the Wiki page for your model, you can download the stock rom Here.
Hope that helps
- Factory Data Reset does not remove the Superuse App from the Phone
- I rooted the phone via SuperOneClick 1.5.3
- I unrooted via the App One Lag Fix
I already have the ROM but how do I put it back? or any other way to remove the Superuser APP
Your best option at this point is to flash the rom...
Unfortunately I don't have the file, or a rogers captivate so I can't tell you exactly how to do that.
If you have a .pit file you most likely should use odin.
If not you may need to use clockworkmod.
One of the two should work.
I just have the Rogers Stock Rom downloaded and don't see .pt file in there, I am confused all over. Will Odin3 ask me to choose a rom or it does something else
Dont use -r.
Just use rm system/app/Superuser
inningsdefeat500 said:
I got my replacement phone and need to return the original, I already asked for help here - http://forum.xda-developers.com/showthread.php?t=827229 but didn't find mch luck
My issue is that I unrooted and the Superuser app is still there on my phone and I tried to follow the instructions
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
I downloaded Terminal app but I type "su" it says invalid command
I also have downloaded the Stock Rogers ROM
Can someone please please either tell me how to
1) Remove Superuser app form the Phone
OR ( better yet in your opinion )
2) Put the stock back ( but have no clue how to do this )
I have tried googling, searching but there is no simple answer and since this will be returned, I ave limited time
So any kind soul can help a fellow Captivator
Click to expand...
Click to collapse
Root your phone again, and this time remove superuser.apk first.
Not sure how the Rogers captivate is, but you will probably have to use either this method:
http://forum.xda-developers.com/showthread.php?t=797397
or this method:
http://forum.xda-developers.com/showpost.php?p=7561524&postcount=1
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
after that i tried to mount the system from shell command but failed... then the phone got hanged and when i removed the USB cable it rebooted straight into recovery...
since the ive tried to check directory listing with adb ls /system command but it returns nothing... adb ls /data also shows only 3 files... i had taken a backup of /system using adb pull but i dont knw how much that'll help...
i did not take any backups before that... was trying to install CWM so that i could take rom backup....
im not able to boot the phone normally...
i would like to know if i can go back to original state?? if not is ther any other solution like flashing a new ROM or something...??
i would like to extract contacts nd messages if possible...
System config:
- Samsung Galaxy S 4G... everything stock
- Rooted!!
thanks in advance...
chi_visor said:
Hi,
i was trying to change the /system permissions using adb shell... commands shown in the attached screenshot
my main purpose was to install CWM for which we need to push modified recovery into /system/bin which requires rw permissions....
to do that i used the command chmod 6 /system from root and then tried to mv recovery file from sd root to /system/bin but that failed
when i checked the /system attributes using stat -c %A /system it returned "d------rw-"
Click to expand...
Click to collapse
'chmod 6 /system' did what you asked it to do. chmod, on a basic level, uses three (3) sets of permissions: global, group, and user. What you effectively did was set the user permissions to rw but blanked out everything else (like chmod 006).
If you can get into the shell, do this:
chmod 755 /system
That should put it back the way it was (7 = rwx for global, 5=rx for group, 5=rx for user)
See if that helps. Report back and let me know.
Real quick; I had my permissions backward. Although you still want 755 it should've read like this:
rwx for user
rx for group
rx for global
I had them backward.
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
chi_visor said:
Thanks stephen_w for ur reply...
I cant get into shell when i enter adb shell it throws this message
- exec '/system/bin/sh' failed: Permission denied (13)
any idea??
Click to expand...
Click to collapse
I was worried about something like that. My guess is that your best bet is to see if you can get into download mode and flash a new ROM. Were you on Froyo or GB before? If you were on Froyo & you're trying to get to GB you'll need to insure you flash a ROM with the right boot loaders first, like chadster's KG4 (http://forum.xda-developers.com/showthread.php?t=1183413).
Let me know if I can be of help.
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
chi_visor said:
I was worried that I would have to flash a new ROM. Not that i mind doing it but ive not backed up anything!! I'd atleast like to see my contacts somewhere... let me know if that's possible...
So there's no other way to come out of this deadlock??
Im on Froyo... If its possible to roll back to stock Froyo it'll be great... If not i'll go for GB... Ive nothing against GB but i'd like to be sure everything works the way it was b4...
Its great to know you have and understanding of my problem... thanks mate...
Click to expand...
Click to collapse
If your contacts were set to sync with Google or your carrier, then they will sync back to your phone after you flash. Given you were on Froyo, you can grab one of the Froyo ROMs from the bible (http://forum.xda-developers.com/showthread.php?t=1117554). Those will likely be rooted, deodexed, or something along those lines. If you want pure stock, you can grab that from samfirmware.com. You'll have to register to navigate to the firmware, though. I'd post a link but it wouldn't work right. Just go to the 'mobile' link and look for the SGH-T959V stuff. Either way, KD1 was the latest Froyo out there from Samsung.
Yup... I'll check on samfirmware.com..
sad abt contacts cuz dint sync the latest ones with google...
anyway i'll try the other method...
thanks..
Sorry man. Best of luck to you. Let me know if you get it fixed.
hi stephen_w,
I downloaded the T959VUVKD1 firmware from samfirmware.com....
I used odin to flash it...
after switchin on the phone in download mode... i flashed the firmware by browsing the file in PDA and leaving PIT, BOOTLOADER, Phone and CSC blank...
the process started and after cache.fs... below it was message:Complete(Write) operation failed.... it stopped nd showed fail in red...
i held the power key for a long time but then it started to show a phone linked to the computer with a yellow exclamation sign...
what does this mean?? im not able to boot into either recovery or download mode now...
please help...
ODIN will still see it when it looks that way, so don't fret! I had similar issues before but mine was a faulty download. Try using this one. It's not 100% stock as it's been deodexed, but it should work:
http://www.multiupload.com/7L5YDG8X8V
Ya im downloading tat one... Odin is detecting nd working... so i guess re-flashing should do the trick...
Jus to confirm I should leave fields other than PDA blank rite?
Yes, PDA only & let ODIN decide what should be checked.
Sent from my SGH-T959V using XDA App
Up and running jus like b4...
Thanks bro...
No worries; glad you're working again!
Hello guys! the instructions are very easy if you do the steps correctly.
This is my first post in the development section.
First, go to market and download OTA Rootkeeper
Second, open the app, Select Create SU Backup.
Third, Select Temp UnRoot(with backup)
Fourth, uninstall Superuser, if you have superuser elite uninstall it also! and uninstall OTA Rootkeeper(dont worry it will not delete UR Backup!)
Fifth, Download and install the OTA.
After it is done and reboot, do a power cycle.
and the last step, go to market, install superuser and ota rootkeeper.
Launch OTA Rootkeeper and Select RestoreRoot, accept the superuser permission, and reboot!
AND ur back with rooted 2.3.6!
Michael
Alternate method! This is Jim's method(Thanks jim for this other way)
To do the 4ever root hack do the following:
1) open root explorer or ew file manager etc...
go to /system/bin
find the file named mount_ext3.sh
touch and hold the file name until the menu appears, go to open in text editor.
Add the following line to the VERY bottom of the file, after the fi
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
2) SAVE!!!! the file.
3) Do the OTA update.
4) You should still have root after the update, now.
Jim
Enjoy, Hope this helps!
I missed step 3 and 4 this is why it did not work for me
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
I don't know but as soon as I get home I'm going to check and see... Just got another A2 today, its going to be a good lil Guinea Pig... (insert evil grin here)
Sent from my MB865 using XDA App
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 644 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root. but if you did not do the update maually, and you used the one-click you might need to add the following line as well....
chmod 4755 /system/xbin/su
Jim
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
cant tell you, i didnt had a custom rom on it while i tried but if i am correct the update will work with stock only. wait till Iggis Pop do the test before attempting.
I just used OTA Rootkeeper normally and it worked fine for me. Backed up root, temp un-rooted, downloaded and applied the update, then restored root from OTA Rootkeeper after the update finished. I have root back just fine...
Did this not work for others?
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
tmease1 said:
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
can you tell me step by step what ou did so i can help you!
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
Michael443 said:
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
Click to expand...
Click to collapse
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
09CarreraS said:
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
Click to expand...
Click to collapse
I'm not Jim but I do have the answers to your questions!
You should flash the fkz's (sbf) files before you update, just a good idea to remove any oddities or potential problems. Also most modifications do relay on a deodexed ROM , so my guess is that it won't work with the new update yet. My personal recommendation would be to wait until lfaber06 incorperates this update into a nice little cwm flashable zip (around this weekend, or next), that will already contain root, as well as the 1 percent mod and the updated theming!
Thanks for the answer! Hey I'm from Ma as well.
well that's what i get for not reading here first. My coworker was demo-ing an app to our CEO and the update notification came in. A few minutes later he comes back and says he hit download then install when it came up. When i got it it was flashing in recovery already
extide said:
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
Click to expand...
Click to collapse
Well, this definitely bricked my phone.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
Are you sure you followed the instructions and put the files in the right directory? I havn't had any problems using this exact method as for a few others.
No way if it was done correctly that it bricked your phone.correctly can be accomplished by navigating to the proper file then copy pasting the code in order.the only thing you are modifying is superuser.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
extide said:
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
Click to expand...
Click to collapse
Not sure, I just pasted those two lines under "fi" or whatever was on the last line. Checked it. Saved it. Rebooted. Boot loop.