Database Info

[Q] I don't think my root worked!

Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?

TomB985 said:
Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?
Click to expand...
Click to collapse
I don't think that package is rooted, or at least it didn't root you when flashed (which happens sometimes).. use odin to flash CWM, boot straight into it and flash the superuser apk, when you boot up update the superuser app in the market and update the binary, after that you'll be rooted no problems
http://db.tt/4b3IK0C <--- superuser
blazing through on my 4G Droid Charge

Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!

TomB985 said:
Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!
Click to expand...
Click to collapse
this: http://forum.xda-developers.com/showthread.php?t=1160580 is a pretty good info thread on how to flash and what everything is though it's a little dated and most of the roms/CWM files are older, everything else like drivers and Odin versions are fine... CWM is short for ClockWorkMod recovery and along with Odin is what we use to flash roms/kernels/etc. to our phones, and yes in Odin it goes in the same PDA spot as a rom and flashes like normal... however since you don't have a custom kernel to make CWM 'stick' in your system its one time use after you flash it in Odin and you will have to Odin flash it again every time you want to use it, making it perfect if all you want to do is simply root the phone

Please use the Q&A Forum for questions Thanks
Moving to Q&A

THANKS!!!
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!

TomB985 said:
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!
Click to expand...
Click to collapse
nice glad to hear it, its a piece of cake after you do it once and learn it
blazing through on my 4G Droid Charge

gain root after odin back to stock

I need to root. After bricking and using odin to get back to stock, my phone wont root again. why, you ask? well, because the phone will not connect to the computer via adb interface. I have usb debugging on, I connect my phone, it installs to the computer, but adb wont work for me. neither will super one click. is there a way to root without using a computer? maybe through terminal emulator? or an app that will work? I know z4 wont work i tried it. someone please give me some advice here. im on xp, i have tried different drivers, tried rebooting the phone, nothing works. please help.

sidekick_fanatic said:
I bricked my sk4g due to bad rom flash. I wanted to try one click unbrick, but couldnt get it to work on my computer. So my only other option was to odin it back to stock. before bricking, i had rooted it with superoneclick. i immediately tried superoneclick after odin. several different things would happen. one, it would go through the whole process and say i was rooted, but root checker pro would say i didnt have root. two, superoneclick would tell me my device was unreadable. i would ignore it and it would go through, but still not rooted. three, superoneclick would hang after killing the adb server. I then attempted to root manually. I downloaded rageagainstthecage and atempted to push it through a command prompt. I have sdk installed and all the other necessary things for a manual root. but when i typed adb devices in command prompt, the list came up empty. i deleted all the drivers, plugged the phone back in, and let the drivers reinstall several times, but my device still will not connect to the adb interface. the drivers are installing, and the usb is connecting through storage mode and firmware update mode, but not through adb no matter what i do. i am on windows xp and i do not have another computer to use. someone please tell me how to root another way or possibly flash a rooted rom through odin. thank you.
Click to expand...
Click to collapse
Try this and post results:
ODIN
Get KD1 or KG2 Firmware
Then visit..
-x]Trunks[x- said:
HERE and HERE
Click to expand...
Click to collapse
And now you should successfully rooted on stock firmware

some of those pages I have already been to. the stock rom you linked is the rom I used to odin my phone. some of those pages were confusing to me, and as far as cwm recovery goes, need root to change recovery binary. before bricking, I had root and cwm. what i need (sorry to sound like such a noob) is a step by step in this thread. please dont post links to me unless they apply to my particular situation. superoneclick, odin, cwm, these are all things i already know how to do. my question is how can i root if my phone wont connect to my pc through adb?

also, odin still recognizes my phone. i can still brick my phone and odin it all day long if i want to. I used the tutorial in one of the links you posted and downloaded the odexed stock rom and followed the tutorial exactly. the phone works, but i cant root it. there has to be someone who can help me figure this out.

bumping this thread hoping someone out there has some useful info for me. thanks

Did you turn on USB debugging?
settings->applications->development->USB Debugging

yes I did. adb is not connecting.

basically what I need is a way to flash a rooted rom through odin or another way to root without using adb. possibly without connecting to the computer, like through terminal emulator or something?

what if I added superuser, busybox, and su to my stock odin rom that I have and just odin again? would that give me root?

what if I added superuser, busybox, and su to my stock odin rom that I have and just odin again? would that give me root?

You can root the phone fine do it after the odin
Sent from my SGH-T839 using XDA App

I think I should start a new thread so I can be a little more concise. I can see that at least one person here completely does not understand what I am talking about.

No just edit the og post
PM FOR PSN NEED THE RUN PSN

xtrem88, do you understand what I am saying? I bricked my phone and had to use odin to get it back to stock. now my phone will not root. superoneclick runs, but for some reason doesnt configure root properly. i end up with superuser installed, but no root. when i try to root through command prompt, i type in adb devices and the list comes back empty. what I think I want to do at this point is odin a rooted rom.

Ohhh ok now i get it you got to. Odin it again and do not connect storage
PM FOR PSN NEED THE RUN PSN

I am updating the firmware through kies mini right now, since the firmware i odin'd wasnt the latest. I just unmounted and removed the sd card. are you saying that was the problem before?

Yeah dont use the sd card
PM FOR PSN NEED THE RUN PSN

I got it rooted. Im on KD1 firmware, but at least I am rooted. I feel like a simpleton, though. Wait till I tell you what the problem was. I was using superoneclick the whole time, and it wasnt working. I re-read the tutorial for the umpteenth time to see if I had missed anything, and it finally dawned on me that each time root had failed, I hadnt rebooted my device after running superoneclick. I just ran superoneclick, it did its thing, I disconnected and rebooted, and voila, I have root. I verified root by going to superuser and updating the su binary. thats how i knew it failed before. each time i would try to update su, it would say obtaining root access and it would fail. this time when it said obtaining root access, superuser asked for permission and i knew I had root. I am so ticked at myself for spending so much time doing it wrong, but so happy that I finally did it right lol. the whole time I thought odin was causing the problem, but im glad to know it wasnt. now i know if i brick my phone again, i can just odin and root and the phone will be back to running and rooted in like 10 minutes.

Lmao
PM FOR PSN NEED THE RUN PSN

sidekick_fanatic said:
I got it rooted. Im on KD1 firmware, but at least I am rooted. I feel like a simpleton, though. Wait till I tell you what the problem was. I was using superoneclick the whole time, and it wasnt working. I re-read the tutorial for the umpteenth time to see if I had missed anything, and it finally dawned on me that each time root had failed, I hadnt rebooted my device after running superoneclick. I just ran superoneclick, it did its thing, I disconnected and rebooted, and voila, I have root. I verified root by going to superuser and updating the su binary. thats how i knew it failed before. each time i would try to update su, it would say obtaining root access and it would fail. this time when it said obtaining root access, superuser asked for permission and i knew I had root. I am so ticked at myself for spending so much time doing it wrong, but so happy that I finally did it right lol. the whole time I thought odin was causing the problem, but im glad to know it wasnt. now i know if i brick my phone again, i can just odin and root and the phone will be back to running and rooted in like 10 minutes.
Click to expand...
Click to collapse
Soo.....this entire time the process I posted didn't work due to a simple reboot after superoneclick....*crickets*....
LMAO!!!! Glad you got your problem solved
Sent from my SGH-T839 using XDA Premium App

Droid 2 Global Can't connect to any wifi HELPP

I am a complete noob with this stuff. So i wanted to root but i read that i had to downgrade my firmware to do it. So i do some sbf-ing with rsdlite 5.7 and it says that it PASSed but on my phone it had an error and wouldnt let me leave bootloader. so i did a ton of research to fix it and i end up getting it to work.. im not sure of it downgraded but im just happy that the phonee turned on. I rooted it with superoneclick and it was a success. after i rooted it i realized that my wifi wasnt working so i wiped all my data and everything and unrooted it and it still wouldnt work. I have verizon fios and it is secured with WEP. i tried other wifi networks and i wasnt able to connect to any of them. it would just say obtaining ip address and then it wud disconnect and scan for other wifi networks and that would keep repeating. I have no idea what is going on and did research for over 24 hours and still cant find the solution. My phone is not activated so i cant call or text or use 3g data. My system version is 4.5.608.A956.Verizon.en.US and my android version is 2.3.3. PLEASE HELP I CANT FIGURE THIS OUT! Thanks in advance

SOMEONE PLEASE REPLY I REALLY NEED TO FIX IT
:crying:

Your problem is that you are still on Android 2.3.3
You have to take the OTA update in order to get WIFI working again.
If you already have root, you can install Voodoo OTA rootkeeper (look for it in the play store, there is an alternate download link there). After installing rootkeeper, you can open it and protect root, then temp unroot.
After that, you need to get the OTA update, and put the zip file on your SD card, and install it from recovery.
Then, restore root with Rootkeeper.
All those files should be available at
http://forum.xda-developers.com/showthread.php?t=1660713
Or, an alternate option is to flash back to Android 2.3.4, and use the direct root method now available.
A combined SBF and Root CD is at
http://forum.xda-developers.com/showthread.php?t=1701862
Or there is a Root only CD there, for if you are on 2.3.4

Thanks SOOO much.. Im going to try it out right now with the first option you gave me and post the results later tonight

the ota rootkeeper app doesnt say temp unroot.. do i use the superoneclick to unroot it.. im not sure if temp unrooting is the same as unrooting? im sorry im just new to android

Rootkeeper doesn't root, just saves a copy of the files.
So, you need to root with super1click, then protect root with rootkeeper.
Then temp unroot, and update in recovery
Sent from my DROID3 using Tapatalk 2

nvm i figured it out. I just unrooted with superoneclick, rerooted again, and then temp unroot showed up.

SWEET after i rebooted (from installing 629 OTA) i restored root and checked if the wifi worked and it did! THANKS SO MUCH! i literally tried for a couple of days to do this. never going to miss with this phone again.. ahaha thanks a ton!

You are welcome, glad you got it back up and working.

Hi;
Had the same problem, with the same specs.
Did as you advised' and have WiFi working!
Thanks loads for your kind input!!
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
bhigham said:
Your problem is that you are still on Android 2.3.3
You have to take the OTA update in order to get WIFI working again.
If you already have root, you can install Voodoo OTA rootkeeper (look for it in the play store, there is an alternate download link there). After installing rootkeeper, you can open it and protect root, then temp unroot.
After that, you need to get the OTA update, and put the zip file on your SD card, and install it from recovery.
Then, restore root with Rootkeeper.
All those files should be available at
http://forum.xda-developers.com/showthread.php?t=1660713
Or, an alternate option is to flash back to Android 2.3.4, and use the direct root method now available.
A combined SBF and Root CD is at
http://forum.xda-developers.com/showthread.php?t=1701862
Or there is a Root only CD there, for if you are on 2.3.4
Click to expand...
Click to collapse

2.3.4/4.5.629 is directly rootable now
Magic MD5 Root 2.3.4 for D2, R2D2, D2G, DX and 2.3.5 for DX2

[Q] Limbo Root Issue - please help!

EDIT: Apologies, I've just noticed I've posted this in the wrong section - though not sure how to move it!?!
Hi all, I’m in need of some help!
I recently rooted my N7100, using CF Auto root – great instructions, easy to follow, and it rooted perfectly
All was good, except that it would not of course, run SkyGo. After downloading voodoo and superuser, I managed to get the phone to temporarily disable root, but Sky Go still wouldn’t work. So, I un rooted, and Sky Go worked - and then re-rooted, with the aim of trying to temporarily disable root again.
Noooooow, my binary su counter has gone to 3, root checker says it’s not properly rooted, Sky Go won’t work because it says it IS rooted, Titanium Backup and Triangle Away won’t work because they say it’s not rooted – and I’m stuck!
Tried re-rooting yet again, via the same method, and it seems to work, but again, root checker says it’s not rooted ‘properly’, and no apps requiring root will work. Also, in spite of supersuer and superSU not being installed (as far as I can see anyway), superSU doesn’t get installed during the root process, as it did the first time I did it.
I seem to be stuck on some sort of root limbo – does anyone have any ideas?
Thanks for reading.

You might want to try the megawipe option from zoot's wipe script you will need to flash clockworkmod though. Hope I helped you out! Good luck
Sent from my GT-N7100 using xda app-developers app

Flash a rooted recovery using Odin. then flash a rooted rom. good set of instructions can be found here along with a video
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-easiest-method/

Getting to 4.3...got past 402 error!

Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!

doncaruana said:
Apologize in advance if this is intuitively obvious to other but after searching and reading a better part of the day, I can't figure it out...
In any case...I rooted my 4.1.2 phone a while back with the casual root. Didn't unlock the bootloader or install a custom recovery, just rooted. So that puts busybox and supersu on my phone. Later on, I installed a custom sound thing to get some decent volume out of this thing.
Now I tried taking the OTA and it failed. I thought it would just wipe out the root stuff and be on it's merry way (like other devices I've had in the past). So, I used the one touch unroot in SuperSu and tried again. Still failed. And it still showed me busybox in the app drawer.
So, here's my question...
Do I need to remove my custom volume thing as well as do the unroot?
And do I need to uninstall busybox before doing the unroot via supersu? Or do i just go to the apps and install it there after the SuperSu unroot?
And, if none of those work right, do I fall back to flashing 4.1.2 directly - or maybe better to flash 4.3 directly? I plan on using saferoot once I'm up to 4.3.
If anyone can help me sort this out, I'd greatly appreciate it. I'm rerooted for the moment.
Thanks!
Click to expand...
Click to collapse
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.

buhohitr said:
OTA will look for any rooted app and fail so you best bet is just Odin the full 4.3 then root with saferoot. This is you also have a nice clean install.
Click to expand...
Click to collapse
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?

doncaruana said:
Thanks!
Been a looong time since I messed with Odin...this will just be firmware - no data or store apps will be touched, right?
Click to expand...
Click to collapse
Sorry but flashing the full firmware will wipe everything bring it back to factory stock phone, so you need to backup all your stuff.

Well, just to share with everyone, I did not flash back to stock. For a number of reasons, that wasn't really an option.
My first step was removing viper4android. That actually got rid of the "custom" screen with the open lock on boot.
Then I uninstalled busybox from within itself. Unfortunately, as noted elsewhere, that leaves several hundred symlinks in xbin, so I removed all of those (I was only left with dexdump and su there). After that, I actually uninstalled busybox via the app manager.
Then I used the unroot option in supersu to clean up the rest and remove it.
At this point, I should be completely unrooted, but still got the 402 error when failing to upgrade with the OTA.
So...I plugged the phone in and ran the software upgrade assistant that shows up on the "CD" that presents itself from the phone when you plug it in to USB to the computer. And, actually, that successfully completed the upgrade to 4.3!
Haven't embarked on re-rooting yet (using saferoot) but that's the plan at least.