Develop Bugs

[Q] Visionary broke my Tmobile G2 phone - PLEASE HELP !!

I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38

boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495

I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.

Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.

tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting

That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.

I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App

I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App

android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App

Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying

omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).

blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.

omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.

Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).

steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.

Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.

steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.

Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.

[Q] Semi-bricked Desire.

Greetings all.
I just recently semi-bricked my Desire, I was uing 'Oxygen 2 RC2' and tried to partition my sdcard through 'AmonRA Recovery' and something went wrong and I ended up with a semi-bricked phone. I couldn't establish any connection with my SIM or SD-card.
I was tipped to install a original RUU which after a few tries worked and I recived a phone with the latest official Sense rom, HBOOT-0.93.0001 and S-ON of course.
After 'fastboot oem enableqxdm 0' is fastboot mode I atleast had connection with my SIM and SD-card and now a I have a semiworking but not rooted phone.
Now I want to root my phone and take back my USB-connectitvity but after reading this I understand that I need root for the USB-brick fix, to work but how do a get root with 'HBOOT-0.93'? Paul O'Brians root method only works for 'HBOOT 0.80' and lower and 'UnrEVOked' only works when having USB connection.
So how do I go about getting root and fixing my USB-Brick on my phone?
Thanks /ZeD

I have found a couple of "downgrade" tools but they haven't helped me much since everyone workd from within a fully booted system with a working USB-link which I have not.
Can a downgrade be done with a simple but old RUU file?

An old RUU file will not work.. I have the same problem, and got the same guide on how to fix it. But I sent it in for repair just hourse before, so I didnt have the chance to try it out. I unrooted my Desire as well with no luck. But as I read the guide, a rootet phone is not necessary?

For me it was, I had a another kind of fault at first my USB-brick happend when installing the ariginal RUU. What I should have done was to install a old RUU with 'HBOOT 0.80', root that and do the USB-brick fix, but I didn't know that I would get one ^^.

Blubba10 said:
a rootet phone is not necessary?
Click to expand...
Click to collapse
From the first step in that guide .
1. Follow this r5 rooting guide to do Step 1 of the rooting.
That will give you a basic ROM to work with, with root capability.
Click to expand...
Click to collapse

Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..

Blubba10 said:
Well, I installed RUU with Hboot 0.80.. And then innstalled updates.... How noob is that?! Just asking..
Click to expand...
Click to collapse
I don't fully understand what you mean but when you have that kind of USB-brick that I have you need a rooted phone to fix it and the old way of rooting a Desire where you don't need it plugged to the computer can only root phones with 'HBOOT 0.80' or lower, the 'unrEVOked' way of rooting a Desire can be used on phones with newer bootloaders but need 'USB Debugging' which can't be used when a USB-brick is in play.
This is what you call a catch22 .
I have now seen a thread where a dude fixed a USB-brick on a non-rooted phone but the exploit that was needed is nowhere to be found. Well, well the hunt is on.

the easiest way to downgrade.
http://forum.xda-developers.com/showthread.php?t=768256

mariosraptor said:
the easiest way to downgrade.
Click to expand...
Click to collapse
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.

if you use a card reader to put the PB99 file on the root of your sd card? boot into hboot it will recognize the PB file and prompt for doangrade.
no need to be rude as no intention were to make you feel offended.
if it is of no help no hard feelings,
cheer up and have nice holidays and a Happy New Year!!!
Freddan80 said:
This might come of as being rude but thats not my intention but I have several thread on diffrent forums out about my issue and most of the answers I recieve is from people that doesn't read my first post.
I cant use that downgrade tool since I don't have any contact with my phone through the usb cable.
Click to expand...
Click to collapse

I'm just a bit tired of working with this **** all weekend and answering in my ' cry for help threads' with I don't have root so I cant do that or I don't have a usb connection so I cant do that.
For the USB-brick fix to work I need root and for the downgrade to work I need a connection, it's just one way around my problem which seem to work but I only get 'permission denied' or 'that location is nonexistent'.
If anyone with more knowhow than me wants to take a look, the only thing that would actually fix my issue is here.

My meaning was to say that I think i have the same usb-brick as you (phone is now sent in for repair). It was rooted, but I unrooted it to hboot 0.80 and innstalled updates, wich resulted in hboot 0.93 in hope for it to fix itself. It didnt. As you say, you need root to fix brick. The only solution wich seems to work is this: http://forum.xda-developers.com/showthread.php?t=879068.. It seems to work for some people, not for me... And not for you as well, if i understand your latest reply correctly..

Yeah that's one of the fix I have tried.
It's kind of strange that that doesn't work, cause we should be able to write to that folder but for me it's like it isn't there at all. I checked my spelling and checked with 'androlib' that the working folder for 'Android Terminal Emulator' was in fact 'jackpal.androterm.

SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .

Freddan80 said:
SUCCESS!!!!
I finally found a terminal that could give me enough "root" to use the exploit that gave me enough "root" to flash the fix. My phone is fully working now. Time to root the sucker again .
Click to expand...
Click to collapse
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate

godina said:
Woooow man tell me how you did it imediately i have the 100% exact same problem as you did...tried update.zip, signature error, tried exploit with Terminal Emulator, no premissions...pleaaase tell me how you did it i am really desperate
Click to expand...
Click to collapse
I used 'Better Terminal Emulator' never could get 'Android Terminal Emulator' to work.
I then used the commands given in the link I posted but instead of using 'data/data/jackpal.androidterm/*', I used '/data/data/*.
and then I did what the other thread said, made them executableand ran the exploit and then flashed my modified USB-brick fix.

Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app

here it is http://forum.xda-developers.com/showthread.php?p=10058480#post10058480.
godina said:
Omg omg omg this could really be it i will try it asap, will post how it went...and does your bt, radio and usb all work?
Edit: where did you get this "Better Terminal Emulator" and how did you install it? I tried looking in market but didnt found tthis app
Click to expand...
Click to collapse

Ok I give up
Tried to download Better Terminal Emulator Magic, but it has been removed from market, looked for Pro version, cant download because there is no paid app support in Slovenia, so I can not download any paid app...
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?

godina said:
Is there any way for me to get this Better Terminal Emulator or will I just have to send the phone to repairs?
Click to expand...
Click to collapse
You can obtain a copy here, but I'm not to sure about support.

[Q] Desire 2.2

I bought an unbranded/unlocked Desire a few days ago, and it had Froyo preinstalled.
It REFUSES to connect to HTC Sync, and it seems impossible to root using unrevoked too (i've tried Vista, Win7 and Ubuntu). All without success. I have tried EVERY method/guide/tutorial out there.
So my question is this. HOW DO I ROOT?!
I'm thinking of using this: http://forum.xda-developers.com/showthread.php?t=768256
And then using unrevoked on the stock 2.1, but in that thread it says
Update:
The new version of unrevoked3 (3.21) can now root froyo ROMs directly, and a downgrade is no longer necessary if you just want to root and install custom recovery, although there appear to be a few issues with this new release. If you want to rebrand/debrand your phone, rooting won't achieve this and you can use this method instead. If you cannot get the new version of unrevoked3 to work you can also run this and use the older version (3.14) that works with Android 2.1.
Click to expand...
Click to collapse
So i have no garauntee that unrevoked will work on 2.1 either, and i'm not downgrading for no reason.
Does anyone have any ideas, cause i'm running out of ideas here.

DannyDrama said:
I bought an unbranded/unlocked Desire a few days ago, and it had Froyo preinstalled.
It REFUSES to connect to HTC Sync, and it seems impossible to root using unrevoked too (i've tried Vista, Win7 and Ubuntu). All without success. I have tried EVERY method/guide/tutorial out there.
So my question is this. HOW DO I ROOT?!
I'm thinking of using this: http://forum.xda-developers.com/showthread.php?t=768256
And then using unrevoked on the stock 2.1, but in that thread it says
So i have no garauntee that unrevoked will work on 2.1 either, and i'm not downgrading for no reason.
Does anyone have any ideas, cause i'm running out of ideas here.
Click to expand...
Click to collapse
Does it have a new H-boot that unrevoked cant do yet? What is the H-boot on the phone?
Does unrevoked come up with any errors? Have you instaleed the correct drivers, adb for it?

What is your hboot #?
Power off, press down volume and power on should tell you at the top.
Then check the sticky topics, at the top of dev section, as they have solved newest hboot problems.
Ps this is best for the q&a section, good luck, and sure we'll all try and help.
Desire is the source of all suffering.

HBOOT number is 0.93, take it this is too new?
The non-connection to HTC Sync worries me, if it wont connect to the manufacturers software, what is there to make me think it will work with anything else?

Don't quote me on this but unrevocked should work on 0.93,
Best is to get suck into this:
http://forum.xda-developers.com/showthread.php?t=709146&highlight=unrevocked
And see how you do.
Goes through the whole deal with drivers etc.
Do you have ADB yet? because you can use adb devices to check to see if your desire is connecting to your computer, but as cjm1979 said you need to get latest drivers from the adb, but seem to remember you have to uninstall htcsync anyway to use unrevocked. But it should all be there in that guide.
But getting adb and drivers is important.

> Uninstall HTC sync 3.x version from your windows box and install 2.x version and then try it ( Important: Disable any firewall/antivirus tools when doing it)
The latest version of unrevoked should work.

Just found this in the unrevocked topic:
http://forum.xda-developers.com/showthread.php?t=725738&highlight=solved&page=36
My HBOOT version is 0.93.0001
Follow the instruction to unrevoked,f after installed the HBOOT driver and enable USB debug, run unrevoked as administrator and connection "charging only",
the unrevoked still not start as follow, any idea?
Solved: I never install HTC sync.
Read all post found similar situation and I install and uninstall HTC sync. Problem resolved.
Never used htcsync for myself anyway.

Ok guys, i found the problem.
This is embarassing, But i forgot to uninstall DroidExplorer which unknown to me, was cocking it all up silently. Uninstalled that, ran unrevoked and it looks to be working, i'm currently on the ClockworkMod recovery screen. Yeah, all working now, and i should be rooted now.
Am i correct in saying that since the phone was unlocked/unbranded, i can now just whack an update.zip on my SD and flash it? Or is there anything else to be done before that (I know enough to do a Nandroid backup before that step)?
Thank you all for helping an idiot solve his non-problem!

I've uninstalled Sync, moved the drivers to system32, ran unrevoked as admin, ran it in compatibility mode, nothing. All required drivers/softwares/fairy dust is present. I really have tried nearly everything listed on tutorials. I've damn near broken googles servers just searching for a fix!

You don't copy any drivers, HTC sync installs in 2 parts - the program and the drivers.
Once installed, go into Add/Remove Programs and uninstall the program but leave the drivers. This works fine
Then make sure unrEVOked is running BEFORE you connect your phone, and make sure USB Debugging is enabled on the phone

One of the tuts i read said movng the drivers to system32 might help, but did it hell. I'm all rooted now, just installed TitaniumBackup, is it meant to ask for permissions 2000 times every time i do something? It just asked me about 20 times O.O

DannyDrama said:
One of the tuts i read said movng the drivers to system32 might help, but did it hell. I'm all rooted now, just installed TitaniumBackup, is it meant to ask for permissions 2000 times every time i do something? It just asked me about 20 times O.O
Click to expand...
Click to collapse
Once, when you've ticked the box,
Unless your talking about superuser notifications which you can turn of in the superuser app
Desire is the source of all suffering.

You mean the 'remember' box? Yeah, done that too but it keeps popping up asking for permissions anyway.

DannyDrama said:
You mean the 'remember' box? Yeah, done that too but it keeps popping up asking for permissions anyway.
Click to expand...
Click to collapse
Yes meant the remember box, is the box always the SU box or is it a grey notification box saying SU access has been granted.

Its always the SU box, asking me to give permission, but the remember box is always ticked.
Sent from my HTC Desire using XDA App

[Q] Screen dead, need to RUU to stock and S-ON.

Everything works except the screen. I can even make calls and use navigation/music with voice commands.
I plan on taking it back to Verizon for a replacement. Obviously, for this to work, it has to be stock.
I have all the appropriate files (3.26.605.1 RUU and Unrevoked S-ON tool). But have no idea how to run them without control of the phone. ADB maybe?
Any advice would be awesome. If I can't figure it out I'm just going to nuke the phone with an industrial electromagnet.
Edit: This is not an SLCD/OLED problem. I did not flash anything to screw up the screen. It's physically dead and I can't take the phone apart to check the screen connections without destroying the warranty stickers. If Verizon is a pain about replacing it, I'll fix it myself.
Edit 2: See below for final questions before I pull the trigger. Thanks!

Download the ruu in PB131IMG.zip format from Doug pistons website here: http://dougpiston.com/files/RUU/bui...and-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
Put it on your SD card using adb push and then restart your phone into hboot and then press up after waiting a little bit (this triggers the update) and then wait while it overwrites everything
Sent from my HTC Incredible
Sent from my HTC Incredible

You could also download the stock ruu.exe. With your phone plugged into the pc run it and it will return you to stock. Then run Unrevoked S-ON tool to relock your bootloader.

But you have to run S-ON in CWM right? So if you ran the RUU it would put you back to stock recovery, and you couldn't run S-ON. So how does one go about flashing S-ON in recovery blind?

I think the s-on tool is ran via your pc, w/ your phone plugged in. The only issues being that if you ruu to stock you may have to reenable USB debugging.

tcberg2010 said:
I think the s-on tool is ran via your pc, w/ your phone plugged in. The only issues being that if you ruu to stock you may have to reenable USB debugging.
Click to expand...
Click to collapse
no, you must have clockwork mod installed to s-on, I sugest doing it before RUU other wise ur stock with root S-OFF still....

Thanks for the ideas and suggestions guys. I'm about to start trying this out.
I'm using androidscreencast and the ddms in the SDK to control the phone. I just don't want to do the steps in the wrong order and not be able to finish.
As it stands, I'm going to flash the Unrevoked S-ON .zip first, then reboot and flash the stock PB31IMG.
Anyone have any objections? Pretty sure I'm only going to get one shot at this. I won't be able to tell if it worked because I won't be able to re-enable USB debugging blind.
Thanks so much.

xaronax said:
Thanks for the ideas and suggestions guys. I'm about to start trying this out.
I'm using androidscreencast and the ddms in the SDK to control the phone. I just don't want to do the steps in the wrong order and not be able to finish.
As it stands, I'm going to flash the Unrevoked S-ON .zip first, then reboot and flash the stock PB31IMG.
Anyone have any objections? Pretty sure I'm only going to get one shot at this. I won't be able to tell if it worked because I won't be able to re-enable USB debugging blind.
Thanks so much.
Click to expand...
Click to collapse
Follow this it show you how to get s-on again...
http://forum.xda-developers.com/showthread.php?t=969973

[Q] USB brick problem

Hi everybody!
I tried downgrading a friend of mine's Desire from Gingerbread to Froyo via official RUU. The problem is that everything is working except the USB connection, but only when the o.s. is running. I can access the hboot and recovery.
The problems are:
- the phone is not rooted and I can't root using unrevoked or revolutionary
- flashing another root doesn't solve the problem (hboot is 0.93 and I can flash only the latest RUU)
- no terminal root access from the phone (obviously)
- Windows can't recognize properly the phone (Qualcomm drivers request)
I followed many guides on this forum and on the web, new and old, but anything worked. Do anyone have any idea?

there's a section on my guide for that, try it. It's only been tested on 2.2 S-OFF but it's worth a try.

bortak said:
there's a section on my guide for that, try it. It's only been tested on 2.2 S-OFF but it's worth a try.
Click to expand...
Click to collapse
Hi!
Does not work for unrootet, S-ON, official GB and HBoot 1.02.

dexterm1 said:
Hi!
Does not work for unrootet, S-ON, official GB and HBoot 1.02.
Click to expand...
Click to collapse
well the guide gets temproot, and that's the best you can get with usb brick if you're on a stock ROM (if you're on 2.2 anyway) was worth a try though.
try calling htc and get their opinion on this matter and whether they'd fix it for you. Just tell them you did the update and now usb doesn't work (don't call it usb brick, make yourself sound like a total retard [not calling you one obviously] who doesn't know what he's doing and they should pity you)

bortak said:
well the guide gets temproot, and that's the best you can get with usb brick if you're on a stock ROM (if you're on 2.2 anyway) was worth a try though.
try calling htc and get their opinion on this matter and whether they'd fix it for you. Just tell them you did the update and now usb doesn't work (don't call it usb brick, make yourself sound like a total retard [not calling you one obviously] who doesn't know what he's doing and they should pity you)
Click to expand...
Click to collapse
I´ll have a try