Database Users

Who has the most problems??

Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.

The key piece of information to remember is that rooting does't cause the issues we experience. It's the custom ROMs and hacks we install that cause problems
I think most everyone here remembers that we're doing these things at our own risk.
As for the OP, if you don't feel a desire for the features available after rooting or flashing a custom ROM, that's cool. It's not for everyone.
Rooting, flashing, hacking... it's for tinkerers. People who like to find out why something does or doesn't work and then find a fix for it.

I would place a bet on this:
The people who don't have root or don't want to root, and they rarely post their issues in comparision with those who have rooted.
Yes, Most of the issues you see here are self inflicted, but it's what we do. We like a challenge/problem, it gives us something to do. Another reason to stay up till 3 in the morning to find out WHY it's jacked up.
If your issues are so bad, RUU and stick with stock (A whole new set of issues).

We mention our problems so that developers can try and fix them for the next release. In all honesty, Ive had one 1 problem, that was when I installed AOSP 1.6, which btw is/will not supported by our phone officially, I got the dreaded SMS issue that SOME people are experiencing.

Well yea many people post about issues who are rooted, but it is caused by other things they are doing that require it. Simply rooting your device shouldn't cause anything to go wrong.
Roms and other things that require root access tend to be beta, and even if they are not beta they are created by people, and not everything will be perfect.
It is pretty hard to permakill your hero compared to other devices. The only way I know of using the software is through flashing the radio, or messing with ESID and stuff like that.
Which you aren't supposed to do .

Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.

rdisanza said:
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
Click to expand...
Click to collapse
There's not an issue with rooting in and of itself. Take me for instance. I've had some problems with my phone:
1. Apps2SD didn't work...but that was part of a ROM that was being beta tested.
2. Kernel locked up...that was due to an invalid setting I put into the kernel I was building.
3. Lost CPU kernel control...this is something I'm doing wrong in the kernel I am building. I simply restore a control file from a previous build and recompile.
These are things that were expected in testing and needed to be fixed or that I inflicted on my own.
I have a friend who has rooted his Hero, but hasn't applied any of the custom ROMs to his phone (although he has installed applications that require root). He's never had an issue with the phone.
It really depends on what you use it for.

rdisanza said:
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
Click to expand...
Click to collapse
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.

watzone69 said:
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
Click to expand...
Click to collapse
lol I second this my wife hates the fact the I have tis really nice phone and when ever I am at home she can never get ahold of because I am always doing something to it.
to the OP rooting really is not hard I mean if you are hosting a MMORPG server you could surely do it, but if your happy with your phone as is then that is really awesome. I myself when I first got my phone knew ABSOLUTLY NOTHING about android or linux or what in the work a kernel or apk was but with the help of the great community here I have learned so much. Dont get me wrong I am no where near where a lot of the guys on here are but I am learning and helping as much as I can just as those that helped me (i mean I am just happy that I think I could go through and make a theme now lol). if you are happy with the phone as is the only benifit of rooting I would bring up is being able to make backups of everything that way if anything does happen to the phone then you dont have to go trough and redownload apps and set everyhting back up again.
if you do decide to make the leap there are many people here more than willing to help.

Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,

rdisanza said:
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
Click to expand...
Click to collapse
oh please understand I wasnt trying to insult you at all, and yes I understand the control thing. thats why I rooted originally but then I flashed my first rom and got addicted. Now if im not changing my phone in some way on a pretty much daily basis I start to get the DT's lol.

No insult taken my friend. The DT's, lol WORD!

Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.

HeroMeng said:
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
Click to expand...
Click to collapse
You don't have to push the asroot2 exploit!?!?!!?

Kcarpenter said:
You don't have to push the asroot2 exploit!?!?!!?
Click to expand...
Click to collapse
Not if you're flashing a custom rom that already has it.

You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.

gu1dry said:
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
Click to expand...
Click to collapse
I never had to do that when I rooted. Flashed MCR right after I rooted using above method and it worked fine.

Yes the asroot2 exploit is was allows to root the phone, so therefore you had run the exploit initially.

So is this information correct?

I ve read that those replacement new vibrants with hardware keys disabled wont get in to download mode once you are stuck on that computer and the phone icon screen. There is no way to get out of it am i right?

anyone?....

I replaced my phone because of that and I couldn't get it back to download mode.
Sent from my SGH-T959 using XDA App

redwolf313k said:
I replaced my phone because of that and I couldn't get it back to download mode.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
were you rooted and what rom did you have on? and does tmobile care if you have custom rom and if the phone is rooted?

wow you guys are jerks.... why cant you reply

flameinthefire said:
wow you guys are jerks.... why cant you reply
Click to expand...
Click to collapse
I guess you just answered your own question.
Really, though, this question has been answered a hundred times on this very forum. Maybe people are tired of new threads popping up constantly asking other people to take time to do research for people that obviously can't be bothered to do it for themselves. Search first, then ask if you can't find an answer...preferably in a relevant existing thread instead of creating 10 new ones. The other users of this forum aren't here to be your free research monkeys.
...and again, insulting people isn't going to make them want to help you. If you want people to be friendly and considerate you need to give that back...it's a 2-way street. Nobody here is being paid.
*prepares to be flamed by the OP...again*

If you have root then you can use adb to get into download mode by typing "reboot download mode", if you don't have root then you can't use adb.
Sent from my SGH-T959 using XDA App

AustinKnight45 said:
If you have root then you can use adb to get into download mode by typing "reboot download mode", if you don't have root then you can't use adb.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yea i have root but the phone is stuck on the computer screen and my computer wont recognize it

AustinKnight45 said:
If you have root then you can use adb to get into download mode by typing "reboot download mode", if you don't have root then you can't use adb.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
are you retarded???
you obviously share the same sickness as the OP "cantgoogleshitaphobia"
you can too use adb without root, how do you think people locked out of hardware recovery are even getting rooted in the first place? (and dont say one click root cause if you knew anything then youd also know that program uses adb as well)
the only thing you have to do to get adb to work is turn on usb debugging and have good drivers installed.
to the OP just cause you ask a question dont mean crap, you dont come in demanding a response to a question that has been answered time and time again in this very forum. I usually find posts like these and still help out with a link if its already on my subscribe list but your just an ass for the way youve gone about it, sorry not everyone works within your mighty time frame

p()()pypants said:
are you retarded???
you obviously share the same sickness as the OP "cantgoogleshitaphobia"
you can too use adb without root, how do you think people locked out of hardware recovery are even getting rooted in the first place? (and dont say one click root cause if you knew anything then youd also know that program uses adb as well)
the only thing you have to do to get adb to work is turn on usb debugging and have good drivers installed.
to the OP just cause you ask a question dont mean crap, you dont come in demanding a response to a question that has been answered time and time again in this very forum. I usually find posts like these and still help out with a link if its already on my subscribe list but your just an ass for the way youve gone about it, sorry not everyone works within your mighty time frame
Click to expand...
Click to collapse
ok i get your point but just tell me this is there anyway to unbrick my phone? i have tried all the methods

flameinthefire said:
ok i get your point but just tell me this is there anyway to unbrick my phone? i have tried all the methods
Click to expand...
Click to collapse
So how many phones have you messed up now?

Chalup said:
So how many phones have you messed up now?
Click to expand...
Click to collapse
only this one

flameinthefire said:
only this one
Click to expand...
Click to collapse
If your phone is on the phone != computer screen and you can't enter download mode via the volume keys - you're bricked. You can't fix it unless you can enter download mode, and some versions of the phone you can't enter download or recovery modes via any keypresses. Since you're on the phone != computer screen, you also can't connect to the phone with ADB - so you're boned like a few other people here.
See this other thread: http://forum.xda-developers.com/showthread.php?t=764360
And this one: http://forum.xda-developers.com/showthread.php?t=771247
And next time, be patient and don't act like a **** when people don't reply. Not everyone knows your particular situation or can give you a solution on a silver platter.

The irony in this is that the junior member has better forum manners than the senior member. Just thought i would point that out. lol

n00bish said:
If your phone is on the phone != computer screen and you can't enter download mode via the volume keys - you're bricked. You can't fix it unless you can enter download mode, and some versions of the phone you can't enter download or recovery modes via any keypresses. Since you're on the phone != computer screen, you also can't connect to the phone with ADB - so you're boned like a few other people here.
See this other thread: http://forum.xda-developers.com/showthread.php?t=764360
And this one: http://forum.xda-developers.com/showthread.php?t=771247
And next time, be patient and don't act like a **** when people don't reply. Not everyone knows your particular situation or can give you a solution on a silver platter.
Click to expand...
Click to collapse
ok thanks. i was just frustrated and nervous but tmobile is sending me another one. this phone was on vibrant rom and rooted if they find out is there going to be a issue? i am thinking that only way to get back is flashing stock odin again and once they do that it wont be rooted again. so i should be good. what do you think.

Yes should flash the original rom cuz if Tmo find out they are going to make u paid the original price of the phone not the discount or insurance price either. Reason I know cuz I know several people that work with Tmo corporate store not affiliate stores.

flameinthefire said:
ok thanks. i was just frustrated and nervous but tmobile is sending me another one. this phone was on vibrant rom and rooted if they find out is there going to be a issue? i am thinking that only way to get back is flashing stock odin again and once they do that it wont be rooted again. so i should be good. what do you think.
Click to expand...
Click to collapse
I am fairly new here but how can you flash with odin if you can't get in DL mode? And if you could flash stock, why didn't you in the first place and start over? Just tossing out some ideas.

flameinthefire said:
ok i get your point but just tell me this is there anyway to unbrick my phone? i have tried all the methods
Click to expand...
Click to collapse
IF you had got the point you would have done your research there and then instead of asking another question.

1 Click root brick?!

So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.

Stop using one click crap. If you don't know what you're then you should not be messing with your device.

Sent from my DROIDX using XDA App

I can. Just won't.

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.

albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for

The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.

csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.

Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.

Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App

Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process

After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.

@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.

In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?

[Q] (HELP) Rooting 4.2.2 Nexus 7

Hi, now most people here are smart with this type of thing soooo i wanted to ask you how i can root the nexus 7 running 4.2.2. I tried to use the wugfresh NRT but when I was installing drivers a problem occurred. Instead of having ADB drivers or something like that I had ADB Composite drivers installed even though i followed the guide completely and I have tried several times to correct this but i havent found a solution. Also i attempted to carry on the rooting process but it said i did not have the correct drivers installed and etc. So can someone give me a fool proof way of getting the right drivers for this thing so i can root so i can finally install some kernels and use the sixaxis controller app! sorry for the essay and all help is appreciated

hrsedJe Something
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.

How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.

phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.

Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
Dude, most commands for doing stuff on the N7 manually are four words. It really isn't a lot to remember. Also I don't think you understand the purpose of this site/forum.
..That being said.
Use Wug's toolkit and update the adb files in its install directory. Then just use the 4.2.1 settings if 4.2.2 doesn't show.
Here is a post with the files: http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650

sucks that the toolkit is only for windows, sucky windows

Kaaji1359 said:
Because:
a) It's not necessary.
b) I have been rooting using the manual way, like you described, on every Android phone I've had for the past few years. And every single time I forget how to do it. I always have to look up what I'm doing to refresh my memory.
Spending 2 hours on something won't make you a master, and unless you plan on consistently refreshing your memory and playing around with your phone (when most JUST want root), then there's no ****ing reason to manually learn how to do it.
Click to expand...
Click to collapse
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk

http://forum.xda-developers.com/showthread.php?t=2019519

had the same problems
Just google fastboot files for n7, get sdk and pack files AND the recovery into the sdk tool folder.
Shift+right click -> start command here
Fastboot flash recovery recovery.img
Start tab abd sideload the SU.zip (google superuser)
Flash
Done ))
Did it yesterday no issues!

phonic said:
There is a big difference between memorizing commands and actually understanding what they mean. Your post made it very clear that in the "years" you've been doing it, you never possessed the latter.
It is not a complicated process. Unlock bootloader, run custom recovery, flash su zip. Voila. In the amount of time it took you to make your original post you could have been done. If it takes you two hours then you are doing something seriously wrong.
This is a developer forum geared towards people who want to learn how things work, not just look for quick one click tools, and then get upset when things don't work out for them using said tools and people tell them to spend some time educating themselves. If people here spent more time actually learning instead of relying on quick fixes, then we would have to deal with hundreds of posts complaining on how OTA updates were failing because of asserts every time a new one came out.
And your last sentence makes no sense. Obviously there is a reason isn't there?
Sent from my Nexus 7 3G using Tapatalk
Click to expand...
Click to collapse
Well said phonic. I prefer the manual way as well. It is always good to know what you are doing, but knowing how it works and learning something is always better.
I would much rather learn something than to have someone do it for me. If ever I need help and ask someone, they say I'll do it for you I say no, please show me how to do it!
Sent from my Nexus 7 using Tapatalk 2

kidujp said:
Use the THE GOOGLE NEXUS 7 TOOLKIT at : http://forum.xda-developers.com/showthread.php?t=1809195 and then use the files from here : http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650 and then start the tool and root. easiest solution I know.
If 4.2.2 doesn't show up in the device list, pick 4.2.1, worked fine for me.
Click to expand...
Click to collapse
You may receive an error message "ABD" is offline, in this case download the latest Android SDK manager and upgrade all USB drivers before using the toolkit again.
Sent from my Nexus 7 using xda app-developers app

phonic said:
How about instead on relying on a tool you know nothing about, you learn how your device works and how to root it manually? This way you aren't stuck dealing with problems like this in the first place.
I could understand the need/desire/etc. for special tools/kits on some branded and locked down devices. But the N7 is as open as it gets. If you have the SDK installed on your computer and a flashable SU zip, you could have your device unlocked and rooted in about 2 minutes.
Click to expand...
Click to collapse
Never ceases to amaze me how many pretentious pricks use XDA.... Reminds me of Apple snobs.

command line is the way to go
command line is the way to go m8!!
cheers,
geek endangered

Rooting The T-Mobile V20

Trying to get my V20 rooted I figured since it's been awhile I'd try and ask hopping not to get my head ripped off about rooting this beast. I would greatly appreciate some help. Tried in the past failed miserably.

ice5192 said:
Trying to get my V20 rooted I figured since it's been awhile I'd try and ask hopping not to get my head ripped off about rooting this beast. I would greatly appreciate some help. Tried in the past failed miserably.
Click to expand...
Click to collapse
I am coming from the Note 7 and Samsung background. I was apart of the Tekhd team. When the note 7 starting exploding and I had to turn it in I got the v10 to test then I prefer ordered the v20.
I just need some pointers on what I need to do the rooting process on this phone is very different from what I have been used to...

how have you failed ? what methods have you used? .. ill help you out as much as i can. i had trouble rooting before so i feel your pain

Just updated to lastest version.

xDEMON87x said:
how have you failed ? what methods have you used? .. ill help you out as much as i can. i had trouble rooting before so i feel your pain
Click to expand...
Click to collapse
Which version should I use? I have the lastest update now.

Hey,
Just follow the Recowvery thread, then install whatever ROM you want after you have TWRP.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594

I'll try I do have the newest build. December release.

ice5192 said:
I'll try I do have the newest build. December release.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=fZEL96MPLvY , follow this guide..

xDEMON87x said:
, follow this guide..
Click to expand...
Click to collapse
O tried this but when I got to type the dirtycow commands it simply doesn't find it it says no such file directory exist

egren58 said:
O tried this but when I got to type the dirtycow commands it simply doesn't find it it says no such file directory exist
Click to expand...
Click to collapse
Before copy twrp.img to internal storage, make sure the name is exactly twrp.img (it MUST be all lower case).
SuperSU file must be copied to memory card.

Anyone free this Saturday willing to help me root I have tried every method... I do where I have done wrong

egren58 said:
Anyone free this Saturday willing to help me root I have tried every method... I do where I have done wrong
Click to expand...
Click to collapse
I & a few others used this a few times,the still pics might be better since it gives you time to reread any step. I put some tips in the comment section. It's basically be the manual dirtycow way (thread with the 120+ pages).
http://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/

2muchspl said:
I & a few others used this a few times,the still pics might be better since it gives you time to reread any step. I put some tips in the comment section. It's basically be the manual dirtycow way (thread with the 120+ pages).
http://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/
Click to expand...
Click to collapse
I figured it out. It turns out that I was using the smaller portable version of adb I went ahead and install android sdk n all the files again n it worked perfectly!! ????

egren58 said:
I figured it out. It turns out that I was using the smaller portable version of adb I went ahead and install android sdk n all the files again n it worked perfectly!!
Click to expand...
Click to collapse
Congrats & welcome to the club!!!:good:
Don't forget not to do a factory reset from inside Android,only in TWRP.

2muchspl said:
Congrats & welcome to the club!!!:good:
Don't forget not to do a factory reset from inside Android,only in TWRP.
Click to expand...
Click to collapse
I formated data bia twrp when I first booted. But one thing is.. I cant figure out how to boot into twrp is it power and volume up?

egren58 said:
I formated data bia twrp when I first booted. But one thing is.. I cant figure out how to boot into twrp is it power and volume up?
Click to expand...
Click to collapse
Power and Volume down

2muchspl said:
Power and Volume down
Click to expand...
Click to collapse
Yeah.. Doesn't do anything but take a screenshot than it just sits there.. Wtf

egren58 said:
Yeah.. Doesn't do anything but take a screenshot than it just sits there.. Wtf
Click to expand...
Click to collapse
Sorry should have added this is during the boot up stage..here is a copy & paste I keep handy:
While the device is powered off, press and hold Vol - and Power button. When you see the LG logo quickly release only the power button and re-press and hold the power button (Never let go of the Vol - button) This will boot you into the LG Factory reset screen. ONLY USE THIS METHOD IF YOU HAVE TWRP INSTALLED!!!!! OTHERWISE YOU WILL FACTORY RESET YOUR DEVICE!!!!! Choose yes to both options and you will be rebooted into TWRP. TWRP intercepts this command and ignores the factory reset part.

xDEMON87x said:
https://www.youtube.com/watch?v=fZEL96MPLvY , follow this guide..
Click to expand...
Click to collapse
When you state follow this guide ( i have to say the LG dev community is kinda of rude and does not even explain anything to new comers from other devices...) Do you mean i need to follow every step or some steps this is why i say the LG Dev community is all over the place nothing is set in stone there is not one way to do like most Samsung users are used to. I would hope that you could elaborate a little more if you are offering to help.
I am not trying to be a jerk i'm just use to nicer dev community. I have done dev work... I have not had any other device besides Samsung for the longest time and i and will be switching back once the S8 or note 8 comes out.
To get me but i would like to root this device and i would like more then a point here to do it because you don't have some time to explain what needs to be done....
Again i am not trying to be rude just trying to learn the process on the LG dev side... Do not want to brick my device if i can prevent it.

ice5192 said:
When you state follow this guide ( i have to say the LG dev community is kinda of rude and does not even explain anything to new comers from other devices...) Do you mean i need to follow every step or some steps this is why i say the LG Dev community is all over the place nothing is set in stone there is not one way to do like most Samsung users are used to. I would hope that you could elaborate a little more if you are offering to help.
I am not trying to be a jerk i'm just use to nicer dev community. I have done dev work... I have not had any other device besides Samsung for the longest time and i and will be switching back once the S8 or note 8 comes out.
To get me but i would like to root this device and i would like more then a point here to do it because you don't have some time to explain what needs to be done....
Again i am not trying to be rude just trying to learn the process on the LG dev side... Do not want to brick my device if i can prevent it.
Click to expand...
Click to collapse
Yes every step i am new as well and i got to say this was the most complex toot i have ever done. But every single comand bust be typed.. Ignore the $ sign. Install sdk not the smaller version of adb.