Database Info

CWM Thread?

http://forum.xda-developers.com/showthread.php?t=850898
Anyone try this and have it working? Suggestions?

Yes. It works as advertised.

droidroidz said:
http://forum.xda-developers.com/showthread.php?t=850898
Anyone try this and have it working? Suggestions?
Click to expand...
Click to collapse
If you have problems with moving files, you can use Root Explorer to move them. Watch out for typos on the last step. Other than that, it definitely works. I have done it many times.

idk..
I did this, and everything worked up to the last step.
It read no errors, but nothing worked.
I figured out that it didn't actually create the directory, so I created it with rootexplorer, copied the file in, and then when i restarted my phone was bricked D:
I've since exchanged it, but I'm gonna hold off for official support before I try again.

vluhd said:
I did this, and everything worked up to the last step.
It read no errors, but nothing worked.
I figured out that it didn't actually create the directory, so I created it with rootexplorer, copied the file in, and then when i restarted my phone was bricked D:
I've since exchanged it, but I'm gonna hold off for official support before I try again.
Click to expand...
Click to collapse
You probably jumped the gun there. These phones are actually pretty hard to truly brick unless you flash something to the "phone" in Odin. What directory were you creating? All of the directories that you are trying to work with are already there. All you have to do is put two files on your sdcard, move one of them to /system/xbin and then flash flash the other. I've done this probably 50 times in the last month and with the exception of a typo the very first time, I haven't had a single problem.

Don't use SuperOneClick... I had problem after problem when I used it to root. "de-rooted" (not sure that's a word) it with SuperOneClick then used Z4root. Everything worked perfectly after that. Also I was making a mistake when trying this step I think - "adb push path/to/recovery.bin /sdcard/recovery.bin" I was stupidly starting adb shell first then trying to run adb push. Hope that helps some.

I am debating rooting also, just a bit hesitant and reading everything i can for now. Which is the best root method so far as i can tell there about 20 different variants.

droidroidz said:
I am debating rooting also, just a bit hesitant and reading everything i can for now. Which is the best root method so far as i can tell there about 20 different variants.
Click to expand...
Click to collapse
Everyone has their own favorite. Personally I use both SOC and Z4, depending on where I'm at. I've never had a problem with either. Good choice, though, reading everything that you can find.

droidroidz said:
I am debating rooting also, just a bit hesitant and reading everything i can for now. Which is the best root method so far as i can tell there about 20 different variants.
Click to expand...
Click to collapse
i dont know what you are reading but with regards to the US Cellular Samsung Captivate there is O N E method and really only 1 method.
SuperOneClick 1.55 which can be downloaded right here at XDA.
its pretty friggin dummy proof really.
And just incase you were thinking rooting gets you everything (like 3 of my coworkers) rooting just unlocks the door, its up to you whether you want to walk thru and start installed and flashing mods but jsut to ROOT the phone allows you to do things not being rooted will not.

v_lestat said:
i dont know what you are reading but with regards to the US Cellular Samsung Captivate there is O N E method and really only 1 method.
SuperOneClick 1.55 which can be downloaded right here at XDA.
its pretty friggin dummy proof really.
And just incase you were thinking rooting gets you everything (like 3 of my coworkers) rooting just unlocks the door, its up to you whether you want to walk thru and start installed and flashing mods but jsut to ROOT the phone allows you to do things not being rooted will not.
Click to expand...
Click to collapse
Actually I SOC didn't work well for me. z4 worked perfectly on my Mesmerize. I had problems with SOC.

icantplay said:
Don't use SuperOneClick... I had problem after problem when I used it to root. "de-rooted" (not sure that's a word) it with SuperOneClick then used Z4root. Everything worked perfectly after that. Also I was making a mistake when trying this step I think - "adb push path/to/recovery.bin /sdcard/recovery.bin" I was stupidly starting adb shell first then trying to run adb push. Hope that helps some.
Click to expand...
Click to collapse
my friend no offense, but if you had problems with superoneclick then you got problems.....
the biggest problem is the creators instructions, he tells you to disable usb debugging then to enable it when it says waiting for device... to bad you cant because the usb cable is plugged in and you cant do anything like that when the cable is plugged in.
i leave debugging enabled because it needs to be on to run the root.
30 seconds later i am rooted,, easy as that.

It's totally cool that it worked for you.
I'm just saying that I followed the instructions of SOC (not that there are any instructions, you just click on the big ROOT button) and then tried to install Clockworkmod.
I could not get anything to work properly. I then used z4 and it worked.
I'm happy to hear that it worked for you though but "I have no problems" not sure why you have to go there.
You realize that there are lots of reasons why something may work on your phone and not mine right? Also if you want to get picky you called it the US Cellular "Captivate". If it's from U.S. Cellular then it's the "Mesmerize". Maybe that's why SOC worked for you and not me...

I also had problems with the SOC method of rooting my Mesmerize... It looked like it worked but the method for flashing CWM wouldn't work. Kept getting access denied errors. Z4root worked like a charm though. Don't know why, don't especially care either way.
Sent from my Samsung Mesmerize using XDA App.

Does z4root install superuser.apk and buysbox? Also with z4root which version of superuser.apk does it install, I noticed the creator has updated the apk recently here:
http://forum.xda-developers.com/showthread.php?t=682828

[Q] Rooting New Galaxy S 4g

Hello All,
I picked up a Samsung Galaxy S 4g yesterday and I have had the intention of rooting it and installing a custom Rom from the get go. Unfortunately I am having problems getting rooted.
I have tried to use the One Click Root, but without much luck. I get the update.zip installed and it reboots into recovery mode, but on 'reinstall packages' it fails with a signature warning. I supect this is because I have the 3e recovery. I have seen some suggestions for other methods but they seem to but somewhat old or unsupported. I would love to get some advice on this.
Details are as follows
Model: SGH-T959V
Firmware: 2.2.1
Basband: T959VUVKB5
Kernel: 2.6.32.9
Build: Froyo.VUVKB5
If someone could point me in the right direction, that would be very helpful.

*sigh* How many times are we going to see this?
http://forum.xda-developers.com/showthread.php?t=966133

I am not terribly sure what you mean by linking. I did actually read this thread along with a ton of others. It seems that it was successful for someone, thats great, but it wasn't for me.
I have followed the instructions, drivers are installed, sd card unmounted, usb debug mode etc. If there is something in that thread that is helpful please point it out. I would love to get this phone rooted.

Happened to me before with rage option on Super One Click Root, what I done was to unroot using same method and restart then use the first option on Super one click and not the rage one then reboot, everything is ok at present with no problem. Hope this help?

It can't hurt to try. I will give it a shot tonight.
Just for other folks I have confirmed that the z4root option does not work on this model. You get through acquiring shell, get a couple of random vibrations and then z4root fails with no root actually happening. There are a couple of other reports of the same result out.
I will try the option the post above suggests and I will see if there are some other approaches to try.

Moved to general as not android development

Just for posterity. One click root 1.7 works just fine as long as you are not trying to do it from a vmware vm.

HTC Hero Rooting Problem

I searched the forums for this issue, but wasn't able to find it. Hopefully i'm posting this to the correct area.
I have an HTC Hero, and when I first got it, I downloaded and installed Beezy's "One Click Rooter" HeroRoot010. Followed his instructions and it worked just as described - no issues.
I started having problems with the phone recently that I was unable to correct on my own and after having done a factory reset which didn't solve the problem, I took the phone to the Sprint store as a last resort.
They decided that the phone needed to be re-imaged. I left it with them for an hour and when I got the phone back it seemed fine. I re-loaded the apps that I had backed up and then decided to again use "One Click Rooter" solution to re-root the phone.
I booted into Recovery and selected "flashzip from sdcard" and then "rootme".
It ran though several steps and gave me a message saying that it was complete.
However, when I re-booted the phone, I don't have superuser authority, the Superuser icon isn't listed among my apps, and I verified that I do not have root access.
So, from my perspective, I'm doing the exact thing I did the first time I rooted the phone, only now it doesn't work.
Not sure what the problem is, but more importantly, I'd like to know what the solution is. What do I need to to in order to get this phone rooted?
Any thoughts or suggestions on how I can correct this would be appreciated.
Thanks!!
RadioActive1

RadioActive1 said:
I searched the forums for this issue, but wasn't able to find it. Hopefully i'm posting this to the correct area.
I have an HTC Hero, and when I first got it, I downloaded and installed Beezy's "One Click Rooter" HeroRoot010. Followed his instructions and it worked just as described - no issues.
Any thoughts or suggestions on how I can correct this would be appreciated.
Thanks!!
Click to expand...
Click to collapse
consider to read this useful post I'm sure about

Delete me please - Phone on 1.85 is impossible to root/unlock?

I've been trying for the last hour to unlock the device and then root it (and vice versa since different instructions have told me different things). Nothing is clear as to if it works for 1.85 or was made for an earlier software version. Also, I have no idea if the problem might just be my computer(s). I've tried on multiple computers in my house for adb to recognize my device but it never does and nothing ever happens. I've been working for an hour and nothing has worked at all. This is easily the hardest Android device that I've ever rooted/unlocked. So, does anyone who had similar issues have a method to go about doing this that I'm apparently missing? If so, please let me know. I wouldn't have started a new thread, but I've searched everywhere and nothing is working. Thanks!

jtc276 said:
I've been trying for the last hour to unlock the device and then root it (and vice versa since different instructions have told me different things). Nothing is clear as to if it works for 1.85 or was made for an earlier software version. Also, I have no idea if the problem might just be my computer(s). I've tried on multiple computers in my house for adb to recognize my device but it never does and nothing ever happens. I've been working for an hour and nothing has worked at all. This is easily the hardest Android device that I've ever rooted/unlocked. So, does anyone who had similar issues have a method to go about doing this that I'm apparently missing? If so, please let me know. I wouldn't have started a new thread, but I've searched everywhere and nothing is working. Thanks!
Click to expand...
Click to collapse
I was about to break the phone trying to do it but finally got it today man. I can walk you through if youd like. [email protected] is my google talk. Let me just tell you what I did. I uninstalled SDK Manager and reinstalled it. I reinstalled 1.85 RUU and finally followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1709296. Then I immediately used the one click bootloader unlock and now just installed custom recovery. Whooo!

kt086 said:
I was about to break the phone trying to do it but finally got it today man. I can walk you through if youd like. [email protected] is my google talk. Let me just tell you what I did. I uninstalled SDK Manager and reinstalled it. I reinstalled 1.85 RUU and finally followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1709296. Then I immediately used the one click bootloader unlock and now just installed custom recovery. Whooo!
Click to expand...
Click to collapse
I just got it! I had to use a really complicated method but for some reason it decided to work. I swear I had even tried that method before and it hadn't worked. But I'm good now. Rooted, unlocked, and officially ready to take on AOKP

jtc276 said:
I just got it! I had to use a really complicated method but for some reason it decided to work. I swear I had even tried that method before and it hadn't worked. But I'm good now. Rooted, unlocked, and officially ready to take on AOKP
Click to expand...
Click to collapse
I'm glad bro. Always good a feeling when root is gained, especially if it made you work so hard, it feels especially good

[Q] Updating to Android L on Rooted Nexus 5

Hey guys.
I have a rooted, unlocked bootloader, custom "recoveryed" Nexus 5, on stock 4.4.4 and stock kernel.
My question is, when Android L comes around, what should I do to update. Doing an OTA update is probably not the best idea right? Since I am rooted and have a custom recovery. So, what would be the steps to take to update. I don´t mind loosing root or making a fresh install.
Anyway just a noob question about something that I never had to do, since I rooted it on 4.4.4.
Thanks for your attention.

Flash a factory image.

Where can I get those?

J.Diogo said:
Where can I get those?
Click to expand...
Click to collapse
On the Google site. Google "nexus factory images"
Sent from my Nexus 5 using Tapatalk

You can OTA update fine. It will just remove root is all.
Get the wugfresh toolbox and reinstall root after. This is what I do every time.

Don't use toolkits.
Sent from my Nexus 5 using Tapatalk

rootSU said:
Don't use toolkits.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
why Ive been using the wugfresh forever now. On my nexus 5 and 7 with no issues.

tevil said:
You can OTA update fine. It will just remove root is all.
Get the wugfresh toolbox and reinstall root after. This is what I do every time.
Click to expand...
Click to collapse
I've been away from the Nexus 5 forum for a while, I come back and this is still happening. Please don't recommend rootkits for people who are clearly new to android modification. As said a million times on these forums, rootkits are fine if you know what you're doing but not for beginners. Beginners need to do things manually because they need to be able to fix their own mistakes if they're simple. Instead of going back here and asking very basic questions which they could have answered themselves if they didn't use a rootkit.
OP: Please do as @rootSU said and flash a factory image. His sig contains all the threads and information you need. It's a very handy tool which can fix your phone's software problems in almost any situation. Especially in the case of Android L (an update with HUGE internal changes), I highly recommend flashing factory image. This is what I will be doing. The factory image completely replaces your OS with stock.

PsychDrummer said:
I've been away from the Nexus 5 forum for a while, I come back and this is still happening. Please don't recommend rootkits for people who are clearly new to android modification. As said a million times on these forums, rootkits are fine if you know what you're doing but not for beginners. Beginners need to do things manually because they need to be able to fix their own mistakes if they're simple. Instead of going back here and asking very basic questions which they could have answered themselves if they didn't use a rootkit.
OP: Please do as @rootSU said and flash a factory image. His sig contains all the threads and information you need. It's a very handy tool which can fix your phone's software problems in almost any situation. Especially in the case of Android L (an update with HUGE internal changes), I highly recommend flashing factory image. This is what I will be doing. The factory image completely replaces your OS with stock.
Click to expand...
Click to collapse
Okay but thats a fine answer over "dont use rootkits"
That made me think they were bad or something.
Technically like myself he is all stock he said, so aside root hes already pretty much stock OS.
Not sure where the animosity is. Also he obviously knows how to root and install custom Bls if hes done it before.
I very rarely pop in here anymore myself unless there is a major issue but doing things the way Ive been has pretty much eliminated those (jinx). Im still more on the Nexus S forum since I tinker with that more as my mp3 player.
He could always just take a backup before updating and dive in. Ive done that in the past with fine results.
Also even IF you do everything manually first and down the line screw up something theres a pretty BIG chance youll be here asking wtf happened. It happens to the best of us at one point or another.

tevil said:
Okay but thats a fine answer over "dont use rootkits"
That made me think they were bad or something.
Technically like myself he is all stock he said, so aside root hes already pretty much stock OS.
Not sure where the animosity is.
Click to expand...
Click to collapse
they are bad if you dont know what you're doing
the animosity comes in to play when you read the forums daily and you see threads saying "HELP i tried to use such and such toolkit and now my phone doesnt work"

tevil said:
Okay but thats a fine answer over "dont use rootkits"
Also even IF you do everything manually first and down the line screw up something theres a pretty BIG chance youll be here asking wtf happened. It happens to the best of us at one point or another.
Click to expand...
Click to collapse
Yeah, but that's why we ask people to read all the threads before starting to mess with the device first. If you understand how the basic things work and what you're actually doing to achieve root, it's alot easier to troubleshoot very basic problems yourself. Of course for bigger issues people can feel free to post and get help. Also, if they did read everything and still messed up, when they post they're able to list the steps they've taken in the post so people can help them better. Otherwise, it becomes "help I messed up, I don't know what to do, I pressed the start button on the toolkit and my phone doesn't turn on."
Regarding the first part of your post, I still think it's just better to start fresh. Yeah, you can do a backup and try it but I honestly think it will be wasting time. It's always good to start fresh once in a while even if you don't use xposed/rooted apps. Eventually, your phone gets cluttered with apps and sometimes they conflict and you have battery issues, and other issues, etc. Since L is the biggest update to android since even I've been involved in it (I only started getting involved in XDA around 4.0), I would highly recommend everyone flashes the factory image and starts fresh. That way you will also know if there are bugs with L itself, or if's the fact that you installed on top of kitkat and all your prior data that's causing the issue. Anyway, no hard feelings. You said you don't spend a lot of time here so it's understandable.

Zepius said:
they are bad if you dont know what you're doing
the animosity comes in to play when you read the forums daily and you see threads saying "HELP i tried to use such and such toolkit and now my phone doesnt work"
Click to expand...
Click to collapse
Well my bad, Ive never seen that. But toolkits (mainly this one) have very detailed instructions. Let alone the same issues happen when using ADB and push.
Its a double edged sword. I get the , go the long route first, which even I did (but also pre root kits), but In my own defense reading the OP he already did root and BL his phone (to my assumptions) so I didnt think my input was that bad.
---------- Post added at 04:49 PM ---------- Previous post was at 04:47 PM ----------
PsychDrummer said:
Yeah, but that's why we ask people to read all the threads before starting to mess with the device first. If you understand how the basic things work and what you're actually doing to achieve root, it's alot easier to troubleshoot very basic problems yourself. Of course for bigger issues people can feel free to post and get help. Also, if they did read everything and still messed up, when they post they're able to list the steps they've taken in the post so people can help them better. Otherwise, it becomes "help I messed up, I don't know what to do, I pressed the start button on the toolkit and my phone doesn't turn on."
Regarding the first part of your post, I still think it's just better to start fresh. Yeah, you can do a backup and try it but I honestly think it will be wasting time. It's always good to start fresh once in a while even if you don't use xposed/rooted apps. Eventually, your phone gets cluttered with apps and sometimes they conflict and you have battery issues, and other issues, etc. Since L is the biggest update to android since even I've been involved in it (I only started getting involved in XDA around 4.0), I would highly recommend everyone flashes the factory image and starts fresh. That way you will also know if there are bugs with L itself, or if's the fact that you installed on top of kitkat and all your prior data that's causing the issue. Anyway, no hard feelings. You said you don't spend a lot of time here so it's understandable.
Click to expand...
Click to collapse
I hear ya.
I ran the L beta a while so honestly Im not that worried. JINX, Im sure you will be answering my HELP thread in 4 weeks! lol

There was no animosity from me. I simply said "don't use toolkits" and that was for good reasons which have been well written in the (General) sticky threads that all new users should read
The problem is we have to waste our time trying to explain what fastboot is to someone who broke their phone after only having used a toolkit. This is why we prefer people don't use them or recommend them.
On top of that,many toolkits are multi-device and this can cause bricks when faced with uneducated users.
Sent from my Nexus 5 using Tapatalk

Yhea. I also remember, when I was first serching for ways to root the Nexus 5 on stock 4.4.4, I saw many warnings saying to not use toolkits.
I ended up usung CF-Auto-Root, wich is not a toolkit right? :-/

J.Diogo said:
Yhea. I also remember, when I was first serching for ways to root the Nexus 5 on stock 4.4.4, I saw many warnings saying to not use toolkits.
I ended up usung CF-Auto-Root, wich is not a toolkit right? :-/
Click to expand...
Click to collapse
Its not but it still sort of removes some of the manual steps we hope you would learn doing it all manually.
Best place to start is the general sticky thread. My adb and fastboot thread is designed to be a good start for people looking for basic info. Then anyone looking to actually root can move on to the rooting guides which employ much of what was learned in the former thread.
Sent from my Nexus 5 using Tapatalk

Right. I was checking the guide from the thread in your signature and saw the way you did the root. I've done the fastboot and bootloader unlock and all those thing, but when I got to the root part I used the CF-Auto-Root. Is this going to give me problems?

J.Diogo said:
Right. I was checking the guide from the thread in your signature and saw the way you did the root. I've done the fastboot and bootloader unlock and all those thing, but when I got to the root part I used the CF-Auto-Root. Is this going to give me problems?
Click to expand...
Click to collapse
No no. As a root method it works fine. Just not as an educational piece
Sent from my Nexus 5 using Tapatalk

@rootSU your point being? I mean, isn't rooting with the CF Auto Root easier.

larwindcunha said:
@rootSU your point being? I mean, isn't rooting with the CF Auto Root easier.
Click to expand...
Click to collapse
you clearly didnt read.

good god look what I started lol.