Related
I tried the "IDIOT-PROOF Root Guide! NAND Unlock and ADB Update!!".... to no avail.
I had fallowed the instructions to a tee and around step 55 it all went down hill, it was supposed to automatically flash a ROM and it did nothing, and now i have probably screwed it up worse. Phone is still 100% functional but i would like to reset back to factory settings, no root, no nand, no custom rooted ROMS, nothing.
Does anyone know of a way to get my phone back to the way it was when i walked out of Best Buy earlier today?
Thanks for the help and all the great resources here at XDA.
Daugusta.
Search for and run the RUU
Step 55? Thats the idiot proof guide? I followed the original guides and there were like 10 steps max..
Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.
Daugusta12 said:
Haha, could i snag a link to the guide you used? also, where can i find this RUU?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=685835&highlight=RUU
This is not flashed, its an exe so its run while your phone is plugged in. Should go smoothly, but as always know the risks of flashing anything
I've heard toasts method is pretty solid for rooting.
Quick question wouldn't this be in Q & A? Not trying to come off as a jerk. Just my 2 cents
Sent via the Sprint HTC EVO
RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta
I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.
Trust me im not giving up
Try the 1-click Root Method
I looked at the fifty-five step root method and peed my pants, then I hit up jiqqaman's one-click root method. Stable root, and you can flash the stock (rooted) rom.
[forum.xda-developers.com/showthread.php?t=706411
Diesektor said:
I believe you have to use HTC sync when you run it, though I could be mistaken. Search YouTube, there's a video of it somewhere. I wouldn't give up on rooting just yet though.
Click to expand...
Click to collapse
When I have ran an rru from previous HTC phones I have had to have sync up. But then again its never been at a black screen
Sent via the Sprint HTC EVO
Ya, i had the HTC sync running as well, synced up fine with my comp but the RUU still gave me the same error.
Im running this on Win 7 64 Bit, im guessing the 64 bit may be the problem. ill try it on a different comp and see how it goes.
Just tried it on a 32 bit Windows 7 comp, still same issues.
Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.
Daugusta12 said:
RUU Is not working, i get it to start, it restarts my phone and then sits their at a black screen that says "HTC" Then the program says "Waiting for boot loader" and counts to like 75 and then errors saying that it cannot connect to the phone. I then tried to start the process, pull the battery, then manually put it into the boot loader and the program never recognizes it.
Anyone else have another idea, or a way to get this working?
Thanks,
Daugusta
Click to expand...
Click to collapse
It should work. After the program doesn't recognize it, while your phone is at the HTC logo. Close the program on your pc and start it again.
Daugusta12 said:
Just tried it on a 32 bit Windows 7 comp, still same issues.
Click to expand...
Click to collapse
There shouldn't be any problems caused by 64-bit OS. I used Win7 Ult 64-bit and it worked fine. Do you have the HTC Sync drivers? That may fix the problems you have.
EVO'D_OUT said:
Sucks man, coming from the iphone world this rooting stuff seems a hell of a lot more complicated. The last jailbreak I did on my 3GS I downloaded 1 program, plugged by phone into the PC, clicked 1 button and bam!
This andriod root stuff is waaaaay more difficult, NAND this, bootloader that, recovery this, RUU that, adb this, zip and flashing all kinds of stuff. Wish there was a simpler method. Im obviously a noob so Im sure it will get easier with time.
Click to expand...
Click to collapse
I noted this too, only I didn't have an iPhone, just an iPod Touch. Despite this, I am having a lot more fun with Android and how it works. I.E. *.9.pngs which made made jaw drop when I understood how it works. SO AMAZING.
I don't think I will ever be much of a dev, but who knows. I have been digging through a TON of documentation over the past 2-3 weeks.
Thread moved to Q&A.
well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.
EVO'D_OUT said:
well I'm pretty much over this rooting business. Ill wait for the official froyo update from Sprint/HTC and not worry about this crap, no camera, instability, bricking, etc. Guess I'm not much of an android hacker and the phone works pretty well bone stock.
Here are my questions...and please explain this to me like I am mentally retarded haha...
For returning my phone to bone stock, Like Day 1, same as it was when I walked out of Sprint store...
1) download .exe file from post #1 onto my PC
2) plug EVO into USB on PC (run in USB debug mode?)
3) Run .exe file while EVO is in Andriod
4) Select yes, yes, blah, blah and it will do its thing automatically?
Is this correct? Some have mentioned I need to download HTC sync onto PC. Yes - No? Any help would be appreciated. Hopefully someone can comment THAT HAS ACTUALLY DONE THIS and not just guessing/speculation can assist.
Click to expand...
Click to collapse
Great question.. Some of these long winded threads need trimming and a definite answer listed out. Clutter = confusion
I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D
All done!!! :-D now to flash rom... good times!
Thanks all
I'm trying to root an incredible for a buddy of mine and I got the drivers installed and all that but, when I try to run unrevoked3, it runs now (where it didn't do anything before but time out and say no) but hangs at the "installing unrevoked3 process" or something and hangs.
Any ideas?
it was doing that to me when i was first rooting mine. i just tried it again and it worked. i know thats not really a solution, more like dumb luck, but heres a free bump anyways.
give it a really good search for troubleshooting. theres bound to be a good solution out there. hopefully you can get it workin. being rooted is so much fun.
Make sure you have usb debugging checked. Also check out this thread http://forum.xda-developers.com/showthread.php?t=787955 it may help.
I just wanted to split this discussion from the leaked ROM thread. From what I have gathered and understand, this newest update is the US equivalent of the Europe 2.51 update. I know many of you have already upgraded your devices to this, so users like me who are late/slow to the game, aren't there yet. In my case I still had the stock 3.6.160 up until last night. I know many have had the concern about 2.51 and not being able to go back. Has US TMobile done us a favor by releasing this OTA update? It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated. It also seems that if the US and Europe version are the same, any thing that works for 2.51, would work for the US version. Like the 3.4.2 Nandroid backups. It should just be a matter of a simple restore and everything should work, correct? Sorry if I seem a little off. Prior to this device all of mine have been HTC devices which didn't have the locked bootloader. So this concept of of firmware/roms is a little off to me. I haven't had a chance to test any of this yet, I just want to know if the theory is correct. If I'm wrong please point me in the right direction. I'd like to be able to contribute to this forum constructively, especially as I am in charge of deploying DEFYs on our corporate network. The nice part of this is my Director is all for rooting our phones. He looks at in the manner that we need to do what needs to be done. If a phone gets bricked in the process, well we will just buy another. Warranty really isn't a concern.I'd like to get playing on it this weekend, especially with Froyo.
runeblade said:
It would seem to me that this is now a sanctioned update, so anything from here on out would be officially supported and updated.
Click to expand...
Click to collapse
Nope.
The only update for the US DEFY is an incremental one (still 2.1) and it has only been released to 500 or so users according to the offical Tmo forums.
They are testing that one now.
The official froyo for DEFY is probably still a couple/few months away from public release, but let us hope they get it out faster.
More info in this thread:
http://forum.xda-developers.com/showthread.php?t=931212
The Incremental has been released to the wild. Both of my Defy's received it OTA. I also know this is not an OS upgrade. Still stuck at 2.1. But my understanding was that the US update changes the boot loader to the same one as the Europe 2.51 update. If this is indeed true it would mean that we should be able to boot any of the 2.2 Roms out there without using the European update. Thats what I'm trying to confirm/Deny.
I registered for the "testing update", and received it this morning. Overall the phone is so much smoother. I'm now using Blur instead of ADW or LP. As a matter of fact all scrolling is smoother. The homescreens, app drawer, lock screen, widgets. Everything. Before the update if I was on Wi-Fi and sent a MMS I would get a delay, and have both icons in the notification bar for Wi-Fi and 3G, but now they send instantly, and I only have the Wi-Fi icon. Battery seems to be lasting longer today too which is one of the included functions. I'm impressed overall with what they did.
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
darknetone said:
I was on of the very first few to get the Official 3.6.360 and while yes some things have improved. I decided to do a wipe after I had installed it. And I notice something interesting. No more root, Z4Root (using 1.3.0 which is what I used the first time I rooted this phone) no longer works, unexpected failure. So yea the have changed something... I run down the ADB route and see what that turns up.
I will have go the ADB route to get back to rootville.
Click to expand...
Click to collapse
I noticed the same thing. No more root access after the update. I tried to re-root with z4root, super 1 click to no avail. Not familiar with the ADB process. Kinda nervous to be honest. First Android phone and all. Had it 2 weeks. Hopefully a new 1 click method comes from one smarter than I soon.
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
runeblade said:
That's interesting. I noticed right off the bat that Z4Root no longer worked, so I ran Super1click, and that worked fine for me. The only thing I haven't done is wipe the phone, but at this point it doesn't sound like I'm going too.
Click to expand...
Click to collapse
Did you need to do anything special with Super1click, or was it as simple as z4root? Can you just run it, and wait for it to finish? I mean I read some stuff that you may need to do the "turn debug off, turn it on, turn it off" thing with it because some phones give a "waiting for device". If you did certain steps other than just clicking root can you share? Thanks.
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
runeblade said:
Nope. Just downloaded it, ran as admin and let it do its magic. Short and simple.
Click to expand...
Click to collapse
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Mine as well. Just keeps saying waiting. It got further once but stuck in a loop and came back to waiting. I unmount the sd, put it in debug, not sure what usb mode to use or where this admin option is found though. Quite frustrated since the bloatware I froze with Titanium Backup is back and all my root permissions are one. Any help for a newAndroid guy would be awesome.
Make sure when you have it connected to your machine that you are in Portal mode, as well as making sure that your machine is actually picking up the MDB interface. I know with mine it took a couple of plug ins to get it to actually install correctly.
bobbyphoenix said:
How long did it take? I tried it, but it keeps hanging on "waiting for device..."
Click to expand...
Click to collapse
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
This is based on the assumption you are using windows 7 or vista. You right click on the program and in the drop down menu select Run as Administrator. It will then open up the program.
slipknotfn said:
Everyone keeps saying 'as administrator'. There is no option in S1C for that. Nor on my phone. How do I execute this as admin? Am I just being dumb?
Edit: Does this mean as computer admin? Like head honcho on the pc?
Click to expand...
Click to collapse
Exactly, "Head Honcho of the computer"! Do what runeblade said.
cargohook said:
I think your problem might be that you're running it in USB "None" mode (as you would if running ADB). This is a common mistake. With Super1Click, you have to run it in "Portal" mode.
Plug your phone into the computer. You'll get "USB Connection" in your notification bar at the top. Then pull the notification bar down and click "USB connection". Click "Motorola Phone Portal". Then make sure "USB Debugging" is on (in Menu key > Settings > Applications > Development). Now run Super1Click as administrator. Click "Root".
It still takes a while in between steps, especially at the various "Waiting for device" stages. But if you did all the initial steps above, it should work properly. Just BE PATIENT.
Click to expand...
Click to collapse
Yep. That was my problem. Didn't have it in portal mode. As soon as I did, it went fast. It went through a bunch of steps. I see it says "Running psneuter... ROOTED" It should be almost done. It's on "Reading OS Version properties..." now, and it's been there for like 10 minutes now.
cargohook said:
Exactly, "Head Honcho of the computer"! Do what runeblade said.
Click to expand...
Click to collapse
What if one were running, say, XP? Then head honcho would work? I have no computer here that has 7 or Vista. Just my old, trusty laptop. Thanks for all your help.
And which version of S1C? The one for 2.51 or the 1.63 version?
The 2.51 version.
runeblade said:
The 2.51 version.
Click to expand...
Click to collapse
where is that version? I'm using 1.6.3 and it's still stuck on "reading OS" thing.
Ok I'm a HTC noob so please bear with me. I setup adb-sdk environment and windows environment variable. After that I obtained Alpharevx and ran it. Everything went fine and I entered the beta key. But then after
'Beta key accepted - thank you for participating!'
, nothing happens. It just stops. Any idea how to get this thing going?
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
JWhetstone02 said:
Did you run AlphaRevx as an administrator ... given you're on Vista or Windows7?
Is the phone in USB debugging mode?
Is the Android software on your phone 2.2.1? If it's 2.3 then the AlphaRevX will not work :/
Click to expand...
Click to collapse
Thanks
Yes my phone is frogyo.
Yes it's in USB debugging mode.
Yes ran as an admin because I disabled the protection so basically all apps as admin on my windows 7.
I've read in the AlphaRevX thread where some people have had to do it multiple times before it Roots their phone. Maybe try that?
Thank you. I will try more :O I hope this won't brick my phone. I heard HTC devices can't recover from brick. With SGS you could just odin back from whatever mess you are in.
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
4GivenByChrist said:
Is the phone set to charge only? Also is htc sync uninstalled?
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Hey, so I am new to this board. I myself have a Dinc2 arriving soon. My brother just got his. We are both former fascinate owners. After researching and following some how to's, my brother was rooting his phone and he got stuck while attempting to get recovery after S-off. He cannot post, but here is what stated happened:
Hey I'm having a problem with my incredible 2.
Before activating the phone (avoiding the 2.3 update) I tried rooting my phone.
1) I downloaded alpharedex and generated the code
2) downloaded the recovery mode application onto the phone
3) and placed the SU zip folder onto my phone
I was stopped at step 3 because the volume down power button procedure was not working. Instead the phone powered on normally. I attempted it many more times and it would not work.
After spending some time on it, I said screw it, I just want to use the phone. So i activated it and OK'd the 2.3 update. It shut down my phone and began to download the file but it was stopped with a exclamation point in a red triangle. I tried doing a hard reset (volume up and power button) but that did not work. So i was forced to take out the battery. When I powered up the phone again, it continued the download: the phone shut down, it began to download and froze up like last time.
Click to expand...
Click to collapse
Okay, so yes I know he shouldn't have done this. After consulting with me, I was able to get him into recovery by attempting the volume down + power procedure about a dozen more times.
Should he install the super user package and reboot? Or should he do something now to fix the OTA auto reboot problem while he still has recovery?
Edit: Because he is in recovery, could he just factory reset and flash a new rom? Apparently, when he boots the phone normally it gets to the home screen and then instantaneously reboots and attempts to install the OTA. That is where it locks up.
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
k_nivesout said:
If he installs a rom it should block the update. Any custom rom will have superuser built in, and I know at least CM7 has OTA blocking built in as well.
Oh, and it sounds like his trouble booting into hboot with power and volume down is because fastboot is enabled. It can be turned off in settings»power.
Click to expand...
Click to collapse
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
deaffob said:
Yes, set to charge only mode.
Yes, removed everything and used the drivers from alpharevx's site.
Yea, I just got mine as a replacement after a year of use. So far I'm happy because the screen is up to par with SAmoled. People always hype up SAmoled but imho, SLCD on Dinc2 is not far behind.
Click to expand...
Click to collapse
You have it working yet? If not I would uninstall the drivers you got and then download and install HTC sync. Then uninstall just htc sync leaving your drivers. Then try again. That wokred for me when I was unlocking a friends phone.
Sent from my Incredible 2 using Tapatalk
deaffob, you seem to be pretty computer literate, if it keeps giving you issues, boot ubuntu from a flash drive and do it that way. I messed with windows for a couple hours, and it took me all of 20 minutes to install ubuntu to my flash drive, boot into it and root.
bik2101 said:
But the problem is that now he can't get into settings.... damn.maybe a factory reset is best if that's possible.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
I fixed it by going to alpharev IRC and got a great help from attn1! He was very helpful late at night.
To those of who'd like to know, this was my situation:
-Windows 7 64bit with admin control turned off=everything has admin rights.
-Fastboot off(tried on too)
-installed HTC Sync's driver.
-tried HTC driver that's posted on AlpharevX's website.
-HTC Sync was uninstalled.
-It was froyo
-Correct HBOOT(obvious because the whole point of getting the beta key was to prevent someone using the hack with the wrong version of HBOOT)
-Tried 3 different USB ports.
-ADB SDK was installed
-JDK was installed
-environment variable path for ADB SDK was set.
-tried reinstalling the HTC Driver twice, each time uninstalling with Revo Uninstaller to clean up registry.
So even after all these, the hack still did not work. So attn1 suggested that I should try it different computer or download the flash version of Ubuntu and try it in there. I tried it on my old lap with Windows 7 64 installed. I haven't used the laptop that much so the Windows was pretty clean and new.
It worked on that laptop. The lesson is, no matter how much you take care of your windows system, I practically baby my computer and do everything to keep the optimum performance, it will get screwed up after some time. I would've never thought that it'd be my desktop Windows that was the problem.
So if you are having a problem, please try Ubuntu as that's probably the best bet.
PeterGunz said:
That is what I was hoping for, but I don't think there is a factory reset option in Recovery that doesn't wipe the current rom he is on.
I was pretty sure flashing a rom with superuser in it would solve it, and it sounds like that might be the answer.
Only problem now is somehow getting the rom on to the SD card. I might have to have him swap SD cards in my phone, add the rom to the SD card, and then swap back.
Click to expand...
Click to collapse
but there's still the problem of not being able to turn fast boot off, which i think is needed to be able to get into recovery..
get into recovery
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
JWhetstone02 said:
Yea it seems a lot of Fascinated people are coming to an Incredible phone Many many mentionings on here about yall fazzy people making the switch, per choice or replacement
Click to expand...
Click to collapse
+1
Yep! And I'm happy I made the switch, the SLCD screen is not bad and has more accurate color reproduction and plus who uses the SAMOLED at 100% brightness anyways..-nobody really lol.
Also HTC sense imho is waay more useable with good functionalities like the ever so good integration of Facebook compared to TW. I still can't get over that since I was conned into thinking that the Fascinate had in-app pictures but atlas it was a link to the website.. whereas HTC has that and more plus notifications!
Sorry I'm just thoroughly impressed especially since this is my first HTC Device. ^__^
Plus the rotating capacitive buttons is just super cool... :3 Now to make it work when using the camera app... >.> Anybody know if this mod exists yet?
Sent from my ADR6350 using XDA App-Dinc2 switched from a Fascinate.. :3
michaelbsheldon said:
To get into Recovery EVERY time, simply do a battery
pull beforehand. That does it.
Click to expand...
Click to collapse
You can download a program from the Market called quickboot It allows you to reboot into recovery without doing a battery pull. this is what I use right now in replace of the 4-in-1 reboot menu
I just got su on mine. I am an Android beginner so my experience may help. My system is a laptop running Win 7. I had installed synch and then following advice removed it with all drivers. I installed the htc USB drivers, and plugged in the phone in the proper mode. AlphaRevX will not work. So (this may be vital) reinstalled synch with drivers. Then removed synch. Got AlphaRevX to do its thing at once. So the other drivers must be there!