Database Users

help me get my vibrant to stock

I previously received my vibrant rooted and using this method on the thread http://forum.xda-developers.com/showthread.php?t=734475 and i used the unrooted file on page two. everything worked great but i still have root. I have the superuser permission show up on my app list, i also tested to see if i have root by installing a root only app, and it worked. so can anybody help get to stock?

Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.

ttabbal said:
Did you use the odin flash? That will put the phone back to 100% stock. Sounds like you used the nandroid, it might not remove extra stuff like the root files.
Click to expand...
Click to collapse
yes i used the nandroid. can you point me to the odin flash? and is the odin more dangerous to use than nandroid? thanks for the help.

look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you

vdub804 said:
look in the vibrant development section you can't miss it for god sake search man no one is going to spoonfeed you
Click to expand...
Click to collapse
listen, im new to this and ive already searched the devolpment section and theres a couple similar threads. so, since i dont really know what im doing, i asked for help. all i asked was to point me to the thread that someone who is experienced in this thinks i should use. thanks for the help.

http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.

ttabbal said:
http://forum.xda-developers.com/showthread.php?t=734475
I think the complaint is that it's the same thread you would have gotten the nandroid image from. No, odin is not more dangerous, so long as you are flashing STOCK roms. Don't go flashing euro stuff with it, and you'll be fine. There are step by step directions in that thread, follow them and you'll be back to stock in no time.
Click to expand...
Click to collapse
thank you for the help. i was just confused as to which one to use. hopefully, when im more experienced in this, i wont post stupid questions like this.

You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?

stepinmyworld said:
im in Terminal Emulator and typed
/system/app/Superuser.apk
it says
/system/app/Superuser.apk: Permission denied
any ideas?
Click to expand...
Click to collapse
did u type "su" before typing every other else?
it should be like:
# whatever you type
not $ whatever you type.

If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su

From the sticky at the top of the page (that says to read before asking). If you want to use the links, go to the sticky.
HOW TO UN-ROOT *ie, sending your phone in for warranty work
The following code can be keyed in Terminal Emulator (could also be done in ADB or deleting the files using Root Explorer). If you do use Terminal, change the keyboard to the stock Android KB prior to opening Terminal. Apparently the backspace on swype does not work in Terminal. Each line should be entered separately. bahnburner gave the instructions in this thread, which you should review first.
Quote:
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
* Alternate Method *
TGA_Gunnman in this thread created a one click root/unroot program. Thank him for his effort.

mrxela said:
You dont need to flash, just remove the following with Terminal Emulator or file manager of your choice:
/system/app/Superuser.apk
/system/xbin/busybox
/system/bin/su
Reboot and you will no longer have root access.
Click to expand...
Click to collapse
mrxela said:
If you are using terminal then type this, each line should be entered on its own.
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
Click to expand...
Click to collapse
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?

It is in the sticky.

JEEBUS (10....)

mrxela said:
It is in the sticky.
Click to expand...
Click to collapse
aww shux. smh
thanks

I used root explorer and deleted those files, so that means I'm on stock and I can get warranty service? Thanks a lot guys, you have saved a noob

stepinmyworld said:
this worked! Thank you. This should go into the thread as a sticky or named terminal commands for un-rooting. so hopefully i will receive OTA updates corrects?
Click to expand...
Click to collapse
Haha rooting won't keep you from getting OTA updates.

Issues with ROM Manager and others

Ok bear with me, this is the only the second phone i have rooted. I am having issues with the rom manager and root explorer.
The rom manager works, it does not force close, but when i ask it to do something like backup or install a rom, it does nothing, litterally i can click something else and same thing, it does nothing. I tried uninstalling and even factory reset. Still dont work.
Also the root explorer, it says "Root explorer has not yet manage to obtain root access. " i get that every time i restart it, same issue.
I have froyo 2.2 and used easy root http://www.unstableapps.com/?p=35

You need they droid x bootstrapper from the market to get into recovery, and titanium backup from market, hit problems & download busybox.
Sent from my DROIDX using XDA App

thanks, i'll get them now and report back.
Now do i put the bootstrap in the root of the sd and use a app installer?

ok, titanium backup said it wont work because the root access failed and after i downloaded busybox it wont install

I'd try the one-click root or and root, both have to be downloaded by pc.if u got the free bootstrap use an app installer.
Sent from my DROIDX using XDA App

still having the same issue, maybe its 2.2? is there a Root ROm?

Yeah, in rom manager. You have to be rooted 2.1. Have you ever flashed a sbf. I'd try unrooting with easy root then using another method
Sent from my DROIDX using XDA App

Almost sounds like the root didn't take properly
Sent from my DROIDX using XDA App

hey guys, I flashed back to stock and rerooted. Everything works now. Thanks guys,
My only gripe is i dont have flash anymore T_T

Are you on 2.1 or 2.2, you can find flash apk. right here on xda.
Sent from my DROIDX using XDA App

ahh cool. Now what if i use the 2.2 guide on here? Is it the 2.2 or do u think it was the root?

I'd say it was the root. Easiest way to get back to 2.2 would be Rom Manager. Look in download rom,2.1 to 2.2 root. Just make sure you flash the latest recovery in rom manager & the current boot strap which is 1.0.0.3
Sent from my DROIDX using XDA App

ok i redid everything, went back to 2.2 using all the methods, and i am still having issues, i dont know whats up with this

What method did you use to root. I messed up theming yesterday, had to sbf. Reroot & went back to 2.2 through rom manager. It went fine. What's it doing now?
Sent from my DROIDX using XDA App

dbl post sry

i used one click root. its doing the same thing as last time.
edit-----
I did a google search for a good 15 minutes and found this
1.) Run "adb shell"
2.) Run "/system/xbin/su"
*****Watch your screen for Superuser app to prompt for permission and click "allow" (if you go from $ to # without being asked for permission, continue with the next step
3.) Run "mount -o remount,rw /dev/block/system /system"
4.) Run "cp /system/xbin/su /system/bin/su"
5.) Run "chmod 4755 /system/bin/su"
[optional] Run "mount -o remount,ro /dev/block/system /system"
Click to expand...
Click to collapse
Everything works like a charm! If you root at 2.1 then go to 2.2, this will fix your problem

(Q) Root with Super User

So I'm rooted and downloaded Super User app from market. I have a bunch of root apps but the only app listed in the super user app is Titanium. Any reason why the other rooted apps (Set Cpu, Minfree Manager, etc.) aren't listed?

Have they asked for superuser?
Via EVO on 4G with XDA App

awenthol said:
Have they asked for superuser?
Via EVO on 4G with XDA App
Click to expand...
Click to collapse
No it doesn't
Sent from my CM6 powered device

krazyflipj said:
No it doesn't
Sent from my CM6 powered device
Click to expand...
Click to collapse
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.

richse said:
We managed to fix this problem the other night on the irc channel. I didn't post anything because it doesn't seem like many people are using superuser.apk. The problem is that superuser needs to install it's own version of the su program to run properly. The current root method replaces su every reboot. When you lose the su that superuser.apk installs it can't control root access anymore and basically any program can request root without a prompt to you. The fix is to just replace the jk-su file in /system/bin/ with the superuser su. Then every reboot it will just use the one that works with the superuser app. I did this a few days ago and haven't had any problems.
The procedure is as follows (you need to use adb):
Go into the superuser app, go to the "settings" tab and at the very bottom choose to update su (it should change from saying original to something like "su v2.3.1-ef").
Plug the phone into usb and make sure you have USB debugging enabled.
Open a command prompt on the computer and goto your android sdk tools folder to run these commands (IMPORTANT NOTE - Make sure you have the phone screen on and unlocked when you run the su command below because superuser will ask you for permission and you need to click yes. It wont prompt if the screen is off or locked and the adb shell will just sit there waiting for a response. As soon as you click yes on the phone you should get a # in the adb shell):
adb shell
su
mount -t rfs -o remount,rw /dev/block/stl9 /system
cp /system/bin/su /system/bin/jk-su
exit
Now you should just reboot the phone and check that it worked by running any program that needs root access that isn't already listed with superuser. I suggest shootme or wifi tether. tether asks when you start or stop tethering and when you allow a mac address in the access control.
Click to expand...
Click to collapse
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...

krazyflipj said:
Hmmm cp /system/bin/su /system/bin/jk-su didn't work. I ls /system/bin and don't see jk-su listed just su...
Click to expand...
Click to collapse
What root did you use? I did mine manually so there may be some differences if you used a one click.
Edit: I just looked at noobnl's one click root and it uses the same script that contains the line:
#copies busybox su
cat /system/bin/jk-su > /sdx/su
so it should definitely be there even if you used his one click.
When you run the command "ls -l /system/bin/jk-su" what do you get?
I get this:
ls -l /system/bin/jk-su
-rwsr-sr-x root root 26264 2010-09-18 06:10 jk-su

Please delete

krazyflipj said:
Please delete
Click to expand...
Click to collapse
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.

richse said:
Did you get it working? After you updated su through the superuser app then it started working so that is why it asked you for permission when you were in terminal. The problem is that if you reboot without applying the rest of the fix to replace jk-su then you will lose the updated su and it will stop working.
Click to expand...
Click to collapse
Hey Richse, I'm trying to get this to work but it isn't.

rose1 said:
Hey Richse, I'm trying to get this to work but it isn't.
Click to expand...
Click to collapse
can you give me more information, what errors are you getting or what exactly is happening?

richse said:
can you give me more information, what errors are you getting or what exactly is happening?
Click to expand...
Click to collapse
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.

rose1 said:
Okay, I did the one click root method that is stickied. Then I did
adb shell
su
after doing su, I initially saw on the phone that unknown user was asking for superuser access. Of course, "unknown user" is me so I granted it. Then I saw the # then I went ahead and did
mount -t rfs -o remount,rw /dev/block/stl9 /system
That worked fine . The line repeated itself which indicates that it worked. When I do
cp /system/bin/su /system/bin/jk-su
it then says cp: not found.
Just to give you a little more info, I just restored my phone with odin to factory defaults, then I updated to the DI07 update. Then I installed the final clockwork mod recovery, then I did the one click root method. Then I installed superuser in the system/app folder.
Click to expand...
Click to collapse
I'm not sure why cp doesn't work, it just means copy. An alternative to try is to delete jk-su and replace it with the su you updated. Use these commands in place of the cp command:
rm /system/bin/jk-su
cat /system/bin/su > /system/bin/jk-su
Make sure you do this after updating su in the superuser app and without rebooting in between. Let me know if you have any problems.

followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"

spdwiz18 said:
followed instructions. no errors but i still have no programs asking for permission. i had wifi tether downloaded before and it worked. I downloaded shootme to see if it would ask for permission and it didnt - but it works. neithe one is lited in superuser either.
listed is:
adfree / quickboot / root manager / startup manager ( 3 of them) / super manager / unknown ( spawned right after i followed instrution)
any ideas
uninstall supersuser and reinstalled:
listed apps now:
adfree / busybox installer / root explorer / rootmanager / sufbs / tit backup
again not sure is it is correct. but seems to work "I THINK"
Click to expand...
Click to collapse
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?

richse said:
When you go to update su in the superuser app does it say "original" and then change or does it stay updated after you reboot?
Click to expand...
Click to collapse
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!

spdwiz18 said:
what i have:
cwm 2.5.1
root 2.1.1
di07
now for the long and skinny:
i checked. went to superuser and it told me 2.3.1 -ef i then HARD rebooted, came back with no root.and superuser told be original, hard reboot again, still no root. So one more time- third time is a charm - i have root and superuser told me 2.3.1 -ef
thanks again for the help.
i think my phone might not be total stable.. lol
any ideas.
also - i thought about upping root to most recent but unsure if i need to unroot or if i can install over it. your thoughts on this matter!!!!
Click to expand...
Click to collapse
I doubt you need to update root. The root I used was the original manual method by joeykrim. The one click just automates that method. There is no reason why you should have to reboot multiple times to get this working. You basically just replaced a file with a similar file and the script that was installed when you rooted uses that file to create a new su every time you reboot. Personally, I would wipe to stock with Odin and then use the manual root method to make sure nothing funny is going on with your phone. When you rebooted and the su was "original" you didn't lose root, it just meant that superuser wouldn't work. For now, as long as the 2.3.1 -ef sticks around superuser will work just fine. As an alternative you could try noobnl's newest stuff. Looks like he made it compatible with superuser, so I think that would negate the need to use this type of fix. I'm not sure what he did to add the compatibility but you could probably ask him.

if you flash noobnl's latest kernel, it includes superuser and it works perfectly.

rose1 said:
if you flash noobnl's latest kernel, it includes superuser and it works perfectly.
Click to expand...
Click to collapse
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.

richse said:
The only issue I see with that is you have to use a DG27 kernel. If you want to use a DI07 kernel you still need to use this fix.
Click to expand...
Click to collapse
Very true. I didn't think about that.

I have latest Noobls kernel flashed on top of DI07 and this fix did not work.First thing that dint work is i never got SuperUser prompt after i typed su in adb shell,i got su in windows but no prompt on the phone.
To make it short i did the whole procedure from BetterTerminal(now i got su prompt) rebooted and back to same problem.Man,this been bugin me for two days now,sometimes i reboot the phone and i have root permissions then i reboot again and they are gone!
Big question is:is everybody on Epic have same issue or is it just on certain phones,kernels or roms?

[Q] Unable to ADB Remount XOOM...!!

Hi..!! Everyone I tried everything, I was going to unlock and root my xoom but I got stuck at this step:
7. fastboot flash boot rootboot.img
I get this error: "can't load rootboot.img"
I run fastboot reboot command and works, after reboots I try adb devices and my xoom shows but if I run adb remount I get this error:
"remount failed: Operation no permitted"
I tried everything search everywhere, update everything and NADA, I'm on a Windows 7 64bit.
Thanks and I hope somebody can direct me to the right path..

You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App

diablo2224 said:
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
I get stuck on step 7 of this guide below, so I think I never get to the point of getting root, but if I'm doing something wrong and I have to run some other commands please let me know.
1. Download the Motorola Xoom Root Zip file and unzip it. Download
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
And thanks for making some time to reply, I try to get some help on other threads with no response.

dumb question: is rootboot.img in the same directory as everything else?
It sounds to me like your flashboot can't find it.

That's a good point from the poster above. I had trouble at the start with this and the SDK tools folder because I never messed with the adb shell too often because there never really has been a need for me to do so up until I got the Xoom.
OP... like this reply says above me, I am agreeing to as well. It looks like it might not be finding your rootboot. Make sure all root files are located in the very root of the SDK tools folder, and make sure all root files are not inside a folder. If they are please drag them into the tools folder and slap them all in there. It looks like a mess but it works. Do the same type of thing if you plan on flashing an overclock kernel. Always make sure that all files are NOT in folders when flashing something like this, and that they are always placed in the very root of the tools folder located within the SDK folder. Hope this helps.
About my above post... woops. I wasn't paying attention totally. It was late. I was thinking about when you are trying to install an overclock kernel and run into this problem that says that you cannot remount in adb. It does have to do with root access though.

Thank you very much guys I found what was my problem, I was running ADB straight from CMD window without navigating to my tool folder and always worked so I thought running step 7 will work, but NO I had to cd c:.....bla bla navigate to tool folder and do step 7.
Now I'm happily Rooted thanks again for your time guys, now to set up again my beautiful screens.

I'm having that problem where i'm trying to flash Tiamat Kernel on my Xoom and when i get to the remount i'm getting - remount failed: Operation not permitted . When you say grant root access again you talking about pointing it to the platform folder ?.

It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App

jase33 said:
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .

jawonder said:
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
Click to expand...
Click to collapse
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App

lokko21 said:
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Yes i'm trying to flash a kernel but at the remount step it's telling that : remount failed : operation is not permitted .

ROM Manager problem

Hi, when I tried to flash a rom using ROM Manager, it said that I don't have ClockWork mod, which I do. Also when I try to flash the ClockWork Mod it says
"An error occurred while attempting to run privileged commands".
Any ideas why that happened? Thanks.

Have u rooted it?
Sent from my HTC click using XDA App

i guess andynroid is right... sounds, as if the root wasn't done... just check this possibility
my description in this thread also gives you a brief overview about the steps to flash your rom

I'm having a similar issue:
Any apps state that i don't have root access, but the adb shell starts in # and i'm able to navigate in /system and so on.
RomManager is apparently not able to install the recovery, allthough the 1-click thingy did finish successfully.
the root checker app complains about /system/xbin/su which i can't seem to find in the adb shell
any suggestions?

wolf.thalian said:
I'm having a similar issue:
Any apps state that i don't have root access, but the adb shell starts in # and i'm able to navigate in /system and so on.
RomManager is apparently not able to install the recovery, allthough the 1-click thingy did finish successfully.
the root checker app complains about /system/xbin/su which i can't seem to find in the adb shell
any suggestions?
Click to expand...
Click to collapse
try typing in a root shell: ln /system/bin/su /system/xbin/su