Related
i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
just done the hboot hing and at the top of screen it says
vision pvt ship s-on
hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685
OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1
try wiping all the caches...
Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many
Where is Captain_Throwback to save the day and another evo once again
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium
evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven
You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .
jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.
Hate to say it, my friend, but I think it's the end of the road for that phone
HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.
thanks captain.
capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?
Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?
Recently been looking into purchasing a new HTC One for myself, but after reading up on it, I see that there are a ton of S-Off and stock issues flying around. I guess I have a few clarifying questions then...
If I buy the phone today, is S-Off still possible?
Is S-Off risky?
Can I return to 100% complete stock yet if I need to or not? If yes, how?
Really I'm wondering if it's worth it to even purchase this phone as I don't want to be without flashing ROMs but at the same time, I resell my phones after awhile so I'm going to need to go back to 100% stock eventually. Sorry if these questions have already been asked, my xda search function is a bit broken. Thanks for reading this far.
Edit - Did some more searching and found the HTC One m8 now has the RUU's? Could someone also explain this? I'm new to HTC devices, coming from a nexus 5 here.
Nobody knows at all...?
Sent from my HTC M8
DinoSoup said:
Recently been looking into purchasing a new HTC One for myself, but after reading up on it, I see that there are a ton of S-Off and stock issues flying around. I guess I have a few clarifying questions then...
If I buy the phone today, is S-Off still possible?
Is S-Off risky?
Can I return to 100% complete stock yet if I need to or not? If yes, how?
Really I'm wondering if it's worth it to even purchase this phone as I don't want to be without flashing ROMs but at the same time, I resell my phones after awhile so I'm going to need to go back to 100% stock eventually. Sorry if these questions have already been asked, my xda search function is a bit broken. Thanks for reading this far.
Edit - Did some more searching and found the HTC One m8 now has the RUU's? Could someone also explain this? I'm new to HTC devices, coming from a nexus 5 here.
Click to expand...
Click to collapse
Probably, it will be. But it's not for certain. If your phone comes with the stock 1.12 software, then you can do it. But there's also a possibility of your phone being one of those unlucky "Whelp, this sucks..." phones. If it comes with the latest 1.57 software installed, it won't be possible.
That being said, if it comes with 1.12, which it probably will, and you unlock the bootloader, root, and S-Off, you can always go back to 100% stock with no trace at all of it ever being rooted if you want to return it for warranty, exc.
IF it is one of the unlucky "Whelp, this sucks..." phones, and you unlock your bootloader, root, and try to S-Off, but can't, then you can re lock the bootloader, run the stock RUU, and the only trace of it being unlocked and rooted would be that in the bootloader, it would say "Relocked" instead of "Locked."
Remember that if the phone comes with the 1.12 software, NEVER accept the OTA update. If you do accept the update, you will never be able to S-Off.
But again, chances are you will probably get the 1.12 software and be able to S-Off your phone. Hope this helped.
XxKINGxX2580 said:
Probably, it will be. But it's not for certain. If your phone comes with the stock 1.12 software, then you can do it. But there's also a possibility of your phone being one of those unlucky "Whelp, this sucks..." phones. If it comes with the latest 1.57 software installed, it won't be possible.
That being said, if it comes with 1.12, which it probably will, and you unlock the bootloader, root, and S-Off, you can always go back to 100% stock with no trace at all of it ever being rooted if you want to return it for warranty, exc.
IF it is one of the unlucky "Whelp, this sucks..." phones, and you unlock your bootloader, root, and try to S-Off, but can't, then you can re lock the bootloader, run the stock RUU, and the only trace of it being unlocked and rooted would be that in the bootloader, it would say "Relocked" instead of "Locked."
But again, chances are you will probably get the 1.12 software and be able to S-Off your phone. Hope this helped.
Click to expand...
Click to collapse
Thanks a ton, this is exactly what I was hoping for. Final question - how do I go about getting to stock. I found the RUU and stock files but I don't know at all what to do. After I know that, I'll be ready to root!
Sent from my HTC M8
DinoSoup said:
Thanks a ton, this is exactly what I was hoping for. Final question - how do I go about getting to stock. I found the RUU and stock files but I don't know at all what to do. After I know that, I'll be ready to root!
Sent from my HTC M8
Click to expand...
Click to collapse
Sorry for the late reply,
To get to complete 100% stock, you have to download and run the RUU. It's a simple EXE file. There are a bunch of Youtube videos on how to run RUUs. Before running the RUU, you have to re-lock the bootloader. But, to go to 100% stock, you first have to to reset the tampered flag, LOCK, not re-lock the bootloader (there is a thread on how to make the bootloader say LOCKED, not Re-Locked) and then S-ON. After that, run the RUU file, and it will take you back to complete stock. Like you never unlocked the bootloader or rooted.
But, I would do everything except S-ON. If you go to S-ON and run the RUU, you will not be able to go back to S-Off again. The RUU will install the 1.57 software, and that version isn't supported by Firewater.
The only thing you really have to do is a simple re-lock of the bootloader before running the RUU. But, doing what I said would make the phone look like it was never rooted. Again, I would do everything I said except going back to S-ON.
I just successfully achieved completely stock with S-On. I gave my details here: http://forum.xda-developers.com/showpost.php?p=55374644&postcount=2
Hi all. I recently broke out my old HTC Droid Incredible to set it up as a gaming device. However, it really can't do a whole lot with the VZW bloatware and being an old phone. Figured I would root it to fix that. However, I can't even get HTC Sync to read the phone. Is it too old to do anything with? Any help is greatly appreciated.
Madnapali said:
Hi all. I recently broke out my old HTC Droid Incredible to set it up as a gaming device. However, it really can't do a whole lot with the VZW bloatware and being an old phone. Figured I would root it to fix that. However, I can't even get HTC Sync to read the phone. Is it too old to do anything with? Any help is greatly appreciated.
Click to expand...
Click to collapse
You should still be able to root it. You don't need HTC sync, you just need a new enough bootloader (HBOOT) to be able to unlock the bootloader, and you need to be able to communicate with HBOOT via fastboot commands.
Did you try following one of these guides?
http://forum.xda-developers.com/showthread.php?t=1506258
http://forum.xda-developers.com/showthread.php?t=1600904
You don't need to bother with s-off, just unlock the bootloader and flash the recovery. From there, you can do anything you want with the phone.
I couldnt get fastboot commands to do anything, either. I'll give it another shot but really have no confidence it will work. Thanks for the links.
I figured out that HBoot didn't update when I did this last. Even if the image is the same. Problem is, the HTC RUU stops being able to read the phone once it gets to the bootloader, so I can't even update it. Any ideas?