I've asked a couple questions in the stickied threads, but no one seems to look at those. Anyways trying to unlock my phone and I get to where I enter the code from the email from HTC and according to the cmd prompt it works, but my phone just sits there. Any help would be great.
Sent from my PG86100 using xda premium
Really? Nobody has any suggestions?
Run the RUU and try again. I know I've said that a handful of times. Good thing you searched before asking a question that's been answered more than once.
I already have the same software version as the ruu so I figured it wouldn't make a difference. I did search, believe me I know how cranky people on here can get when you don't search first. I've been around for a while I know the process I just don't have a whole lot of time to spend reading through multiple threads. I work 50+ hours a week and have a family. I don't want to run the ruu and wipe my phone just to find out it was a waste of my time.
The unlock will wipe ur phone too. But yes, run the RUU and try Htcdev again, it should solve ur problem
Sent from my PG86100 using xda premium
I ran the ruu and got it unlocked, but when I go to push the recovery it says device not found.
OK I got it, I didn't have usb debugging checked. I feel like an ass now. It's been a while since I rooted a phone and adb has always stumped me.
Related
Just as title says. Ive tried all the fixes for it with no luck.
I dont really care for the trackball anyway, but I cant load roms without being able to scroll down.
Any suggestions xda community.
i had that problem like a week ago,didnt find any answers, i went to verizon and told them my trackball wasnt working and they were going to try and make me pay for another under my warranty,i told them that I read on many forums that it was a hardware issue and after they researched it they exchanged my phone for free.thats the only thing i can tell you to do. hopefully they can do it for you also.
It's the infamous trackball issue. I had ignored it until my came down with it a few months ago, it was around 6 months old. I called Verizon and got a replacement phone, they shouldn't charge you for anything. I couldn't see any other way around it, since I too am a rooted user. Good Luck!
i agree. its a known crappy trackball issue. call verizon and they should sent a replacement. there was an ruu that was an exe ran from your computer that should (someone correct me if i'm wrong) allow you to go back to stock on your eris if you are worried about the verizon people asking about your root. it was posted here, but i just looked and couldn't find it. trying to reup now. will edit this post with a link.
uploaded file http://www.multiupload.com/0B4EAQE25I fyi i'm not responsible if you brick your phone blah blah blah. i actually had nothing to do with writing the file, i just couldn't find it so i reposted it. it is an exe to run on a windows based computer with your eris attached via usb.
gthirty6ptime said:
Just as title says. Ive tried all the fixes for it with no luck.
I dont really care for the trackball anyway, but I cant load roms without being able to scroll down.
Any suggestions xda community.
Click to expand...
Click to collapse
Here is a brutal hack from the Eris Root forum on AF.
I works, but you need to use adb from a PC, and be comfortable working at the command line.
bftb0
I actually sent my phone rooted with KaosFroyo on it and Verizon didn't say anything! I've heard of a handful of people that have done the same.
People have sent it back no problems, but if you're worried run the RUU.
I'm hoping someone can help me, and I may need led thru steps.
I came from an x2, which I had managed to root, install recovery, and flashed and changed several ROMs, all successfully.
On my rezound however, I'm kinda stuck. I unlocked it, using the htc instructions and links, and rooted using zerg. I apparently don't have, and never have had recovery. Originally I just couldn't go any farther as far as gaining recovery or flashing roms, would get an error message and it would go to reboot. I don't know what I did 2 nights ago, but how whatever I do from the boot screen, I get an immediate haptic response, and it goes right to the white htc screen, where it is locked until I pull the battery. I've even tried to do factory resets, and it asks the prompt questions, but eventually it just reboots to the locked htc screen, until I pull the battery. Then it will reboot normally, but nothing was wiped.
I'm not totally inept, on the phone or the computer, but I'm definitely still a noob, but I really want to learn this stuff, the customization possibilities are the main reason I got the rezound.
I would appreciate some patient assistance from some of you knowledgeable folks!
Thanks in advance! Scott
Try using scott's cleanflash tool. It will flash recovery for you. It will also flash the boot.img (kernel) when you flash a custom ROM.
Sounds like you have fastboot checked in the settings.
If you really want to learn more about flashing, do yourself a huge favor and read up on ADB and fastboot. There's a few really good guides on them you can find by searching the forums, and knowing the basic commands will save you quite a bit of hassle vs. constantly doing battery pulls.
update..getting worse
thanks to the 3 of u who tried to help so far, i have tried some of your advice, but now my phone is basically non-functional, with constant reboots. it wont even allow me to do a hard reset. i tried it thru settings, when i could access them, and thru the "battery pull and buttons method". it confirms the reset, and goes thru the motions, but when i reboot it...everything is the same...including my problem. i need a functioning phone, does anyone know how i can go about putting my x2 back into service?
i know a lot of people on here probably figure i'm getting what i deserve, but if it comes down to it i will run over it with my car and get an insurance replacement. i really want to learn how to do this stuff, but without the background or any help, maybe i AM too "stoopid" Thanks Scott
Are you able to connect to your pc with it so you can use adb or RUU?
Not that I'm going to be the one with the answer to your problems, but maybe you can post exactly what you did that got you messed up in the first place because your post is a little confusing and it would help people who really know this stuff figure out what happened and how to fix it. Looks like you rooted and then did you ever flash a recovery?
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
i appreciate it!
pwnwolf117 said:
ifyou would like hell free to shoot me your gtalk if you have one and I'll gladly help you out, got no plans tonight so I can help at whatever point you see this that also goes for anybody else having issues!
Sent from my sexy otterboxed ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
Ty wolf...and I very likely will take you up on your kind offer very soon! I was away all afternoon and evening today.
I did get out of the bootlooping mess I had earlier, I found a related post on droid forums, posted by malkavian under the title "continuous rebooting". The fix involved removing the sim card and typing in a code, and it fixed my most pressing problem.
I still have big problems though, I can't do anything from the boot/recovery screen, it goes right to the white htc screen and locks until I pull the battery. Also, I have tried several times to do hard resets, and those don't work either. I hope to talk to you soon...and thanks in advance! Scott
I just bought this device a few days ago not a big fan of the locked bootloader. Anyways i was just messing around and opened a fastboot window and sent the command. It just gave me results saying it would void my warranty and enter my device specific code. So bear with me as i havent done too much reading through the threads for this device. Im sure i havent been the first person to try this command. Im just curious if the users that have done this have gained any further access. Like say trying to boot a recovery image via fastboot and maybe getting past motorolas digital signatures? I have no problem unlocking mine since im using it on metro anyways so no warranty. And trying out some things to try to get past it. Just posting this for some feedback i guess.
Unfortunately people have tried it. I've tried it, but nothing comes of it. So nothing to report :/
Sent from my MB870 using XDA App
Figures. This is my first motorola they didnt play around as far as locking this thing down goes from what i can see so far. After unlocking it what all did you try to do?
I guess i should sent the unlock code before posting. lol
mteezey said:
I just bought this device a few days ago not a big fan of the locked bootloader. Anyways i was just messing around and opened a fastboot window and sent the command. It just gave me results saying it would void my warranty and enter my device specific code. So bear with me as i havent done too much reading through the threads for this device. Im sure i havent been the first person to try this command. Im just curious if the users that have done this have gained any further access. Like say trying to boot a recovery image via fastboot and maybe getting past motorolas digital signatures? I have no problem unlocking mine since im using it on metro anyways so no warranty. And trying out some things to try to get past it. Just posting this for some feedback i guess.
Click to expand...
Click to collapse
Requested moved to general thread. Doesnt really belong here
I tried to root my phone using the regawmod process on my PC. i followed the steps until the first reboot…i put the debugging option on the phone when it rebooted because everything got wiped as it said it would and then the phone went completely black as if it was rebooting as it should..but never reloaded..i cant turn my phone on or anything..phone was charged to 65%..so i know it couldn’t have died that quick..What happened?? please help!
hmmmm....
not sure what to tell you man.
hold power button for a while, until you see it reboot... IF you see it reboot. should happen within ten seconds....
if you have root access..... download quickboot and try to boot into recovery.
we'll go from there.
also, plug device into comp and see if it detects it.
assuming you installed all drivers necessary and software packages from that thread, correct?
I did everything to the T...I tried to connect to the PC again and it did not detect the phone, and still wouldn't turn on..so i took it as a loss and took the phone back to the store and they gave me a new one because it wouldn't turn on...I appreciate the reply back.:good:
probably wasn't bricked, btw
This kind of makes me worry..... with what everybody has used, which would be considered the "best" to use? This is my work phone and I'm ok to root it and what-not; heck, I root my co-workers phones all the time so I'm no noob at all to this. Thanks!
I don't know what happened but I tried again, started with fresh files and it worked..I'm thinking one of the files got corrupted our wasnt being recognized by my PC...but now I'm enjoying my rooted phone!
Sent from my EVO using xda app-developers app
pogibry said:
This kind of makes me worry..... with what everybody has used, which would be considered the "best" to use? This is my work phone and I'm ok to root it and what-not; heck, I root my co-workers phones all the time so I'm no noob at all to this. Thanks!
Click to expand...
Click to collapse
Regaw is the best to use, I would say. This is the only case of this I've heard and I've followed the thread from day 1. A few did have it fail part way thru, but then just reran it and all went fine.
If you want S-off, there is the lazy panda method now. But I've seen way to many bricks on that thread to recommend it to anyone. But I guess they're also working constantly on a fix for those bricks and have had measured success (from what I've read).
Sent from my EVO using xda premium
Every one of your 4 posts have been negative on regaw's process and your experience...
Here is a little tip of advice for you that MIGHT lead you to getting actual valuable answers to your problem...
PM Regaw....I'd say post in his thread but you dont have 10 posts...
Regardless I can promise you that creating a new thread each time you try is NOT going to help your situation at all.
OK. I just wanna say that this has got to be the MOST difficult device to unlock & root. I just spent the past 2+hrs trying! I was trying to unlock & root my girlfriend's phone but it is just not happening. I watched a million videos on youtube and even read all the tutorials. Its just not working. I am stuck at the part where my command says "waiting for device"...I would LOVE for someone to help me with this...message me...or whatever. I know this thread will probably be deleted anyway..so send me a message because I am SUPER frustrated!
I have a Galaxy Nexus and it took 5 minutes to do everything I wanted to do!
Fix you install the drivers onto the computer?
Read, Search, Read again, ... Then Ask with Tapatalk 2
If U read my post.. I said I have read everything and watched every YouTube video about it and I cannot do it. That is why I made this post to get answers. If not, that's fine... Not my phone anyway.
Thanks for your "help"... NOT.
filmusikat said:
Thanks for your "help"... NOT.
Click to expand...
Click to collapse
This attitude won't get you far in this community so if you would really like help from others start behaving like a decent man and not just like some "too cool gangsta for this forum".
Try unlocking and rooting your girlfriend's phone on some other computer available to you.
I followed this tutorial and i unlocked mine in matter of minutes.
http://androidforums.com/3892643-post2.html
Good luck.
So you tried a couple of hours...
I actually tried for days. Weeks went by and still could not get the wire trick to work. Same thing... it said: "Waiting for device".
Finally, I read in a forum to try a different computer and that's what I did. Made sure that HTC Sync and stuff like Double Twist were not installed. Re-installed the adb and usb drivers. And still did not work the first time I tried it. So, I went into Device Manager and deleted the Android Phone entry. The computer then re-installed adb by itself. After that, I finally got the "Do the wire trick" message!!!!
It took me three or four tries before finally getting it.
Now I am S-Off and downgraded to Eng hboot. Installed Team Dirt's AOKP Rom and could not be happier. It is so smooth that I have kept it as my daily driver, even though it is still missing a couple of things.
So, definitely try using another computer. Even better if it has never been connected to an android phone and you can install the drivers from scratch.
Hope that helps.
So as you can see, others agree that it might be a driver issue since "waiting for device" usually means the phone is not being seen by the computer due to the drivers not being installed.
But I don't know what I'm talking about because it took me only one hour to root and s-off my phone just by reading the directions. I must be a moron. :banghead:
Read, Search, Read again, ... Then Ask with Tapatalk 2
I had that "waiting for device" problem before (am using Desire S tho), and to my surprise, the solution to that was to change my data cable. I used the one from HTC, and solved by using a generic one.
and yeah, that attitude needs a chmod..
coal686 said:
So as you can see, others agree that it might be a driver issue since "waiting for device" usually means the phone is not being seen by the computer due to the drivers not being installed.
But I don't know what I'm talking about because it took me only one hour to root and s-off my phone just by reading the directions. I must be a moron. :banghead:
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Or USB debugging might be disabled.