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.
Related
To root phone must be in Charge Only mode under USB Connection. If it is still in Motorola Phone Portal you will not be able to root. It took me a couple of Hours to figure this out. And im sure some people who are new to rooting or new to rooting Motorola Android Devices will have the same problem.
Yea umm...are you releasing something? Or just being informative?! Lollololololo..I believe this would be posted in the general section?
Sent from my MB855 using XDA App
pzztgotbagz said:
To root phone must be in Charge Only mode under USB Connection. If it is still in Motorola Phone Portal you will not be able to root. It took me a couple of Hours to figure this out. And im sure some people who are new to rooting or new to rooting Motorola Android Devices will have the same problem.
Click to expand...
Click to collapse
You made a new post for this? cmon dude.
Hey it helped me......never had that issue till I got the photon......the last Motorola I had was a Star-Tac......
pzztgotbagz said:
To root phone must be in Charge Only mode under USB Connection. If it is still in Motorola Phone Portal you will not be able to root. It took me a couple of Hours to figure this out. And im sure some people who are new to rooting or new to rooting Motorola Android Devices will have the same problem.
Click to expand...
Click to collapse
This is helpful, but the issue i was having is that i couldn't get the damn phone out of Phone Portal. I'd hit Charge Only and within in seconds phone portal starts up and i get the connected and i'd recieve an ip address notification on the phone.
I did some reading and saw that it is in the drivers i installed on the computer (64bit), and i was told to uninstall and reinstall and it would work. Well, reinstalling didn't rid the issue and i think it may be due to the 64 bit drivers.
anyways, i eventually got rooted the other day and so far so good running Alien. I was having a noob moment when i was trying to run fastboot commands while the phone was in the OS and not fastboot... almost pulled my hair out, and then i had one of those "what the f*** was i thinking" moments. I tend to forget little things after a few beers, thank god i'm not a vodka drinker, i'd have a mopho-ing brick
I was recently shopping for a knock-around tablet and came across leaderinternationalinc dot com this little guy at Kmart. Yep, I said Kmart. When I asked the price and they told me $129, I said SOLD!.
So far it's been average in performance and had to do some trickery to get some apps installed (Android/Amazon Market, Pandora, Google Talk, etc.) and am still having some difficulty installing other apps. It seems as if they really want you to use their market and apps, some of which are okay, I guess. I got Netflix installed, but the audio/video isn't in sync and everything is a hue of blue. Might be a Flash Player issue - also which I can't seem to update.
Anyway, the bad news is I can't find a way to get in to bootloader or able to root this tab with oneclick. Hopefully they didn't lock this thing down to hard.
Additionally, since the screen is resistive, using a stylus makes it a bit easier to navigate. Worth the money so far!
I'm praying the brilliant dev brains here at XDA will purchase this one and create a simple root/rom that allows me to take this thing to the next level!
Anybody out there?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Sorry... Still a bit of a noob in forums. Where exactly was this moved to? Search provided no results. On a side note, did you buy one of these yet? ;—)
Thanks.
Sent from my i7 using XDA App
Woostyle said:
Sorry... Still a bit of a noob in forums. Where exactly was this moved to? Search provided no results. On a side note, did you buy one of these yet? ;—)
Thanks.
Sent from my i7 using XDA App
Click to expand...
Click to collapse
He's a mod and he already moved it to the correct forum.
Link?
Sent from my i7 using XDA App
i need link too same as my issue ?? Sent from my i7 using XDA App
??????? please give me link
br
We're heeeerrrree
Looks like it's the same, but in a new place.
We're heeerreeee basit....
Were you able to get the standard Market installed on it? I was able to get it along with Pandora, Google Voice and a couple others (Netflix not working well) with a little trickery. Still can't get Google Talk and a few other things like an updated Flash.
If I can get a plain vanilla Froyo on this I would give this cheap little tab a solid B.
#bonus
I know this doesn't have anything to do with my original [Q], but I thought I would share anyway...
I contacted Impression about another AC adapter... 1 isn't enough...
After I registered my device, they shipped me another for free!
Any devs out there for this one?
just return it and get another one, a tablet thats $129 is probably not going to be great at that price.. other than the time hp touchpads were $99
Yeah, it's not the snappiest device I've owned, but makes a great desk-side companion. Mainly use it for Pandora, Weather, IM and a few other things...I'm generally still happy with it although I know it won't replace my primary device. Having the (free) second AC adapter is nice so I don't have to carry that back and forth. 2 hours of streaming music kills the battery dead.
Stay plugged in with this one.
Still hoping, praying that a dev picks one of these up...
Theonew said:
He's a mod and he already moved it to the correct forum.
Click to expand...
Click to collapse
I don't see a mod link. Any help? I just want market. Thanks.
skank_boy said:
I don't see a mod link.
Click to expand...
Click to collapse
Mod link? His post is the 2nd post and as I said, he already moved it to Android Q&A: http://forum.xda-developers.com/forumdisplay.php?f=1236.
You can install the Android Market without any funny business. Just download the apk and install. Still think this device can perform much better if it just had vanilla froyo... Hope someone cracks it.
Sent from my Droid Incredible using XDA App
I have an i7 and I got it rooted, what factory installed .apk's are safe to remove? I prefer my own music/movie players etc....
Thanks in advance
What did you use to root? Superoneclick didn't work for me the last time I tried... Did it unlock the bootloader?
Sent from my Droid Incredible using XDA App
Woostyle said:
What did you use to root? Superoneclick didn't work for me the last time I tried... Did it unlock the bootloader?
Sent from my Droid Incredible using XDA App
Click to expand...
Click to collapse
I used super1click, the newest version. It didnt work the first few times, i ended up doing shell root first, then was able to achieve root as normal. It did seem to take a while.
Edit: I just rooted a 2nd i7.... had the same trouble with it just hanging during root. When it hangs, quickly unplug the usb the replug it in. Once it detects usb debugging again it will root properly and pass the verification at the end.
Hope that helps
sactownsav said:
I used super1click, the newest version. It didnt work the first few times, i ended up doing shell root first, then was able to achieve root as normal. It did seem to take a while.
Edit: I just rooted a 2nd i7.... had the same trouble with it just hanging during root. When it hangs, quickly unplug the usb the replug it in. Once it detects usb debugging again it will root properly and pass the verification at the end.
Hope that helps
Click to expand...
Click to collapse
Just attempted rooting it myself with Superoneclick.
Did shell root first and that went fine. Attempted normal root right after and it hung right at the end when it said the device was rooted and would restart. Unplugged and replugged the usb quickly and then it rebooted.
My i7 was definitely not rooted when it rebooted. Not sure what went wrong. Attempted it numerous times with the same result sadly. Did it hang right at the end for you or at a different point during the root?
sactownsav said:
I used super1click, the newest version. It didnt work the first few times, i ended up doing shell root first, then was able to achieve root as normal. It did seem to take a while.
Edit: I just rooted a 2nd i7.... had the same trouble with it just hanging during root. When it hangs, quickly unplug the usb the replug it in. Once it detects usb debugging again it will root properly and pass the verification at the end.
Hope that helps
Click to expand...
Click to collapse
Can you detail the process that worked for you? soon as I click root it goes to not responding??????
dustomcgee said:
Just attempted rooting it myself with Superoneclick.
Did shell root first and that went fine. Attempted normal root right after and it hung right at the end when it said the device was rooted and would restart. Unplugged and replugged the usb quickly and then it rebooted.
My i7 was definitely not rooted when it rebooted. Not sure what went wrong. Attempted it numerous times with the same result sadly. Did it hang right at the end for you or at a different point during the root?
Click to expand...
Click to collapse
When it hangs at the end it never worked for me. Id suggest trying the different methods to root instead of auto....i just pretty much tried everything until i goot root to stick...if it hangs during root steps thats when to unplug and replug.
Sorry i dont have a more speific solution, but i did get two rooted like this
Oh and obviously double check usb debugging is enabled
Sent from my A500 using xda premium
Alright. Thanks for replying. Assumed if it was hanging at the end then it wouldn't work. Just wanted a confirmation on it.
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.
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.
Hi all! I could use a little help if ya'll don't mind. I'm new to the Amaze but not at all to Android.
I found an Amaze 4g on eBay for $65 that was in pretty good shape with one glaring problem: it wasn't fully functional. The seller explained that it would bootloop after hitting the HTC screen and, knowing what I know about Android, it sounded to me like this should be pretty simple to fix. And if I'm absolutely wrong, then I should be able to sell it for parts (perfect screen on it) to get some of my money back!
Well, it came in and sure enough, it bootlooped at the HTC screen and it was still S-On (yay for hoping nobody trashed its internals too hard!). So I slapped a factory image on the SD Card, loaded it up, and after a slow first boot I heard the T-Mobile jingle! Yay, all is good! Or so I thought...
On stock software, all is good. Everything functions as it should. And if I wanted to leave it stock, I would have never noticed a problem. However, when I went to go unlock it, that's when I began to run into problems. For the life of me, no matter what I do, I absolutely cannot get fastboot to work! ADB works great! I've transferred quite a bit over USB so the port itself seems fine. I've loaded up drivers (started out with universals, then went to HTC, then went to the toolkit stickied at the top of the forums here) and no matter what I use, it simply will not work. I can ADB to it all day, but I just cannot use fastboot.
Just going with the assumption that maybe I had bad/dirty/whatever drivers/conflicts, I actually installed Windows 7 64-bit from scratch, loaded up Windows Updates, and then ran the all-in-one toolkit (which takes care of drivers for me) and alas, absolutely nothing different. ADB works great but I can't get any response from fastboot with the device.
Have I done something wrong/dumb here? Is there something special about this device that could allow something required for fastboot to not work (damaged USB port in a special way) that would allow all other USB operations to function?
Thanks in advance, friends!
Jaxidian said:
Hi all! I could use a little help if ya'll don't mind. I'm new to the Amaze but not at all to Android.
I found an Amaze 4g on eBay for $65 that was in pretty good shape with one glaring problem: it wasn't fully functional. The seller explained that it would bootloop after hitting the HTC screen and, knowing what I know about Android, it sounded to me like this should be pretty simple to fix. And if I'm absolutely wrong, then I should be able to sell it for parts (perfect screen on it) to get some of my money back!
Well, it came in and sure enough, it bootlooped at the HTC screen and it was still S-On (yay for hoping nobody trashed its internals too hard!). So I slapped a factory image on the SD Card, loaded it up, and after a slow first boot I heard the T-Mobile jingle! Yay, all is good! Or so I thought...
On stock software, all is good. Everything functions as it should. And if I wanted to leave it stock, I would have never noticed a problem. However, when I went to go unlock it, that's when I began to run into problems. For the life of me, no matter what I do, I absolutely cannot get fastboot to work! ADB works great! I've transferred quite a bit over USB so the port itself seems fine. I've loaded up drivers (started out with universals, then went to HTC, then went to the toolkit stickied at the top of the forums here) and no matter what I use, it simply will not work. I can ADB to it all day, but I just cannot use fastboot.
Just going with the assumption that maybe I had bad/dirty/whatever drivers/conflicts, I actually installed Windows 7 64-bit from scratch, loaded up Windows Updates, and then ran the all-in-one toolkit (which takes care of drivers for me) and alas, absolutely nothing different. ADB works great but I can't get any response from fastboot with the device.
Have I done something wrong/dumb here? Is there something special about this device that could allow something required for fastboot to not work (damaged USB port in a special way) that would allow all other USB operations to function?
Thanks in advance, friends!
Click to expand...
Click to collapse
Hi,
I think that a USB port may be broken, but that would require soldering another USB port on it, so it might not be worth it.
Did you already try a RUU? If it's a software issue you may be in luck since RUU's fix those 90% of the time!
SuperAfnan said:
Hi,
I think that a USB port may be broken, but that would require soldering another USB port on it, so it might not be worth it.
Did you already try a RUU? If it's a software issue you may be in luck since RUU's fix those 90% of the time!
Click to expand...
Click to collapse
As I said, I recovered the soft-brick with an RUU. So getting to stock is fine, but I don't want to stay stock.
Are you saying it's possible that the USB port is broken even though ADB works perfectly and I can transfer a couple GB of data over it successfully?
Jaxidian said:
As I said, I recovered the soft-brick with an RUU. So getting to stock is fine, but I don't want to stay stock.
Are you saying it's possible that the USB port is broken even though ADB works perfectly and I can transfer a couple GB of data over it successfully?
Click to expand...
Click to collapse
Well that's just a guess... lol
It's probably not a USB problem then.
Yeah, unless there's something different about the Amaze compared to most other Android phones, I don't think this is a USB problem although it acts like it is. I'm really baffled on this. :-/
Jaxidian said:
Yeah, unless there's something different about the Amaze compared to most other Android phones, I don't think this is a USB problem although it acts like it is. I'm really baffled on this. :-/
Click to expand...
Click to collapse
Well good luck, but you at least got it on a stock ROM working fine. You could sell it and make a profit this time!
It could possibly be a hardware issue, but IDK.
What are you trying to fastboot? Make sure your in the correct window I mean you have to be in bootloader.. I forget it almost every time also if adb works it has to work.. Try the correct jbear hboot and see cuz if I'm right jbear hboot are fastboot enable or something like that
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
What are you trying to fastboot? Make sure your in the correct window I mean you have to be in bootloader.. I forget it almost every time also if adb works it has to work.. Try the correct jbear hboot and see cuz if I'm right jbear hboot are fastboot enable or something like that
Click to expand...
Click to collapse
Simply running "fastboot devices" is my litmus test - I'm unable to get it to actually see the device. And yes, I have it booted into the bootloader and I have put it into fastboot mode.
@ Jaxidian
i m not an expert ! just giving advice
May be m completely wrong, just trying to help
have u tried in ubuntu ?
Check your fastboot script?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
So if you hook the phone up to the computer and at a command prompt type, "adb devices" it returns your device serial number; but, if you then type, "adb reboot recovery" and are then in the bootloader fastboot and type, "fastboot devices" it doesn't return the device serial number?