Develop Bugs

EVO Bricked? Please Help

I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….

Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk

What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw

did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.

@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted

Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com

Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.

Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse

Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...

Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse

Yes your just not rooted anymore. Run whatever process worked for you the first time

Try whitslack's method.
EDIT: Nevermind, no can do.

What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse

xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first

Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse

I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse

latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!

Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!

Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse

I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse

[Q] Boot loop, no USB connectivity and signature verification failed

I have searched for hours and give up finding a workingsolution to the problem.
Long story short - Installed the latest OTA update manually by bypassing signature verfication on a rooted Froyo phone (still not entire sure how I did this, but I'll get back to this later).
The phone currently does boot loops repeatably. I can enter Hboot and menus Fastboot, Recovery, Clear Storage and SIMlock.
Phone info:
Bravo PVT1 ship s-on
Hboot 0.93.0001
Microp 031d
Touch panel-synt0101
radio-5.11.05.27
aug 10 2010, 17:52:18
Rooted with unrevoked 3 (I think)...
I installed Andriod SDK and ADT plugin for Eclipse on my WinXP PC.
USB Connectivity
My USB connectivity have three running USB scenarios
1. Then boot looping the HDD Icon show up momentarily but am unable to access it. In control panel the HDD works fine. I assume the SD Card is dismounted.
2. In Hboot mode, only Unrevoked USB drivers would install for then connecting the phone with a USB cable to the computer.
3. In Fastboot mode, only Google USB drivers (from the SDK) worked.
Though, there should be connectivity then applying the "ADB shell" command it detects no device in either boot mode. Either does the RUU Toolkit or Unrevoke 3.21.
Signature verification failed
I have a micro SD adoptor, so I have tried various ROMs and run recovery mode attempting to flash the phone. Depending on which ROMs the signature verifications make different progress (0-20 %).
What is funny, is that what allowed me to install the OTA in the first place was toggle the verification off. But, I have no idea how I did this. I do not have an alternative recovery manager installed. Though, it seems something from deleted from the update due to the install being an OTA. And that there might have been an alternative recovery mode.
I have been unable to "recovery-windows.bat" trick as no USB connectivity!
The latest PB99IMG file is currupt as that would be my last attempt. If anyone have this working please send it my way. Also, I have downloaded a 168 MB version of this file but I do not know what to do with it!?
I hope someone finds this a challenge and can help out! I have almost given up...
Cheers

Do a search on here for how to apply the PB99IMG.
It is quite a common request and there are lots of posts telling you how to do it
Sent from my HTC Desire using Tapatalk

mikep99 said:
Do a search on here for how to apply the PB99IMG.
It is quite a common request and there are lots of posts telling you how to do it
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up. I know this is a quite common post hence my frustration with nothing working.
I emphasized that the PB99IMG from the server is corrupt (10x download attempts) and if anyone could email a functional file?

Email a 168MB file?? Good luck with that one!!
Download this:
http://www.megaupload.com/?d=N03CIN0U
And then read the Word document I attached to this thread. It explains how to get the PB99IMG file from an RUU:
http://forum.xda-developers.com/showpost.php?p=10509780&postcount=102
The reason you can't 'turn off signature' is because the OTA has flashed the stock recovery back on. Yet another example of why you should NOT FLASH AN OTA ON A ROOTED PHONE!!

[Q] s-off struggle

Having difficulty achieving s-off via alpharev 1.8 with my gsm desire and wondering if anyone has any hints!
Previously 3 network branded desire, to which I have done the following:
Goldcard created via revskills
http://www.addictivetips.com/mobile...gold-card-for-htc-desire-without-hex-editing/
rooted with unrevoked 3.2.1
http://forum.xda-developers.com/showthread.php?t=788044
SU and busybox running, and Clockworkmod recovery 2.5.0.7 installed via rom manager.
So I have burned the Alpharev 1.8 image to CD and am booting from that OK, it is detecting my phone but says it is unsupported or not recognised - all the fields such as CID: etc are empty. The "goldcard" is in the phone..
Tried recreating the goldcard via above, both from original goldcard.img and by starting over completely and retrieving the CID again. Each time the revskills goldcard tool tells me I have a goldcard!
I have not flashed any new ROMs although I intend to - I wanted to goldcard and s-off before doing this
BRAVO PVT1 SHIP S-ON
HBOOT 0.93.0001
MICROP 031d
RADIO 5.11.05.27
So it seems Alpharev is not able to pick up any information from my phone - is it because I have created the goldcard (and thus debranded and unlocked my phone)?
Do I need to flash a stock rom to get s-off to work?
Do I forget about s-off and just flash a new rom?
Should I see a goldcard.img file on my "goldcard" - I don't see any files right now!
Do i need to downgrade in some way?
Any help appreciated as I am a bit lost!

Can't say about the debranding off your phone, but in regards to just the s-off, i did the following and it worked for me with no problems at all..
You probably already saw this: http://forum.xda-developers.com/showthread.php?t=805811
1.flashed stock rom (i used the one i backed up right after first root) Because i came from miui rom version that used 2 partitions (ext3) and alpharev recommends using stock roms instead.. Otherwise the process can hang or crash..
2. S-off via virtualbox method (http://forum.xda-developers.com/showpost.php?p=8590461&postcount=31)
3.Flashed new rom
4.done
Oh and be sure you mount SD Card (mass storage) and in USB Debugging, when connecting USB and watch the phone's screen, because it may ask for superuser rights.
First time with the virtualbox, it gave me same message about unrecognised device, but then i found out i forgot to mount my SD
Hope this helps a little..

00droid said:
Having difficulty achieving s-off via alpharev 1.8 with my gsm desire and wondering if anyone has any hints!
Do I need to flash a stock rom to get s-off to work?
Do I forget about s-off and just flash a new rom?
Should I see a goldcard.img file on my "goldcard" - I don't see any files right now!
Do i need to downgrade in some way?
Any help appreciated as I am a bit lost!
Click to expand...
Click to collapse
Firstly, do you have USB debugging enabled on your phone? It won't be recognised if you don't.
1. You don't need to flash a stock rom although I've seen recommendatiions that a rooted rom as close to stock as possible gives a better chance of sucess.
2. That is what I did at first. S-off isn't necessary if all you want to do is try out different roms. The only thing I've really used it for is changing the HTC spalsh screen on boot up.
3. No you won't see goldcard.img on the sd card. In fact you won't see any evidence that it is a gold card other than it works.
4. No you don't need to downgrade at all. I S-off'd mine from a rooted froyo 2.29 stock rom

00droid said:
Having difficulty achieving s-off Each time the revskills goldcard tool tells me I have a goldcard!
Click to expand...
Click to collapse
what SD card did you use to make. a goldcard? i tried converting my 8HB stick to a goldcard but even though the goldcardtool tells me it was successfull it was not.
if you did not use the SD card HTC gave you, try again with that one. it worked for me...
Sent from my HTC Desire using XDA App

Check that USB debugging is enabled.

Oh and be sure you mount SD Card (mass storage) and in USB Debugging, when connecting USB and watch the phone's screen, because it may ask for superuser rights.
Thanks - I definitely had USB debugging on, but to be quite honest I can't remember if I had mass storage or charge only.
I didn't touch the screen of the phone at all - so it may have been sat there waiting for superuser I guess.
I will try again with these two in mind and then move on to Virtualbox if I have no luck there!

Tyderion said:
what SD card did you use to make. a goldcard? i tried converting my 8HB stick to a goldcard but even though the goldcardtool tells me it was successfull it was not.
if you did not use the SD card HTC gave you, try again with that one. it worked for me...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks it's an interesting point!
I used the Samsung 4GB card supplied with the phone, it had been freshly formatted to FAT32. The only part I wasn't sure about when formatting was when setting the drive size option (a range of options from 32kb to 1024kb were the choices I think), so I just went with default. Maybe that makes a difference?

00droid said:
Oh and be sure you mount SD Card (mass storage) and in USB Debugging, when connecting USB and watch the phone's screen, because it may ask for superuser rights.
Thanks - I definitely had USB debugging on, but to be quite honest I can't remember if I had mass storage or charge only.
I didn't touch the screen of the phone at all - so it may have been sat there waiting for superuser I guess.
I will try again with these two in mind and then move on to Virtualbox if I have no luck there!
Click to expand...
Click to collapse
OK well USB debugging on - check, SD mounted as disk drive (not charge only) - check, no screen asking for su rights - check.
Still the same result so time for a try of Virtualbox.
Thanks again for your input!

Virtualbox runs fine but still returns the same problem, phone is not recognised!
From doing more reading I think my next step should be backup, wipe, flash rooted stock rom, then try again. I am going to use the rom from this thread:
http://forum.xda-developers.com/showthread.php?t=773997
Do I flash rom and radio, or rom without radio? My common sense tells me without but confirmation would be good!
Now running Oxygen rom which rocks...

In order to get s-off create a alpharev bootable usb using universal usb installer.....just search how to create usb using this software...
Sent from my HTC Desire using XDA Premium App

Having read the entire "How to s-off HTC desire" thread, it seems some people followed the procedure and got s-off whilst running oxygen rom, i.e no need to flash stock rom.
Anyone know if that works? Also, should I turn off my screen timeout in case I miss a superuser request? I will be trying the livecd method.
Thank you all!

The live cd method worked fine for me just now, in under 10 minutes I have S-OFF!
I actually just got this to work fine with the CD method - about 8 minutes and I have S-OFF!
The problem must have lain with the stock rom I was left with after creating a goldcard and rooting. Is it possible that this process leaves you with your stock (shipped) rom that has no identity, hence not recognised? Indeed, is that the point of creating the goldcard and I am missing it?
Anyway I post this for anyone else considering the procedure - Alpharev S-OFF 1.8 works fine for a rooted Desire running Oxygen 2.0.1 and Clockworkmod 2.5.0.7. No need to restore a backup - it booted just fine first time after the procedure.
Thanks all for viewing and posting

Leg End
status_six said:
The live cd method worked fine for me just now, in under 10 minutes I have S-OFF!
I actually just got this to work fine with the CD method - about 8 minutes and I have S-OFF!
The problem must have lain with the stock rom I was left with after creating a goldcard and rooting. Is it possible that this process leaves you with your stock (shipped) rom that has no identity, hence not recognised? Indeed, is that the point of creating the goldcard and I am missing it?
Anyway I post this for anyone else considering the procedure - Alpharev S-OFF 1.8 works fine for a rooted Desire running Oxygen 2.0.1 and Clockworkmod 2.5.0.7. No need to restore a backup - it booted just fine first time after the procedure.
Thanks all for viewing and posting
Click to expand...
Click to collapse
Mate, Thank you.
I installed Oxygen, ran Revolutionary and away I went. Less than a Minute. Seems my ROMS were causing the issues. No need for a Gold Card and it is a Class 10 Card.

S-OFF Error

Trying to S-OFF my HTC Desire which is currently running LeeDroid 3.0.5
At the end of the process (USB Method) it says TC-Box:~S
Also says it is unable to enumulate with USB device on Port 1.
Any idea as to why this is happening or what solutions to do?
Thanks

Try CD method, it's the better way to s-off your device There is less bugs
Sent from my HTC Desire using XDA Premium App

Tried that as well. Burnt the ISO to the disk using Magic Iso. EXACTLY the same error :/

robheald said:
Trying to S-OFF my HTC Desire which is currently running LeeDroid 3.0.5
At the end of the process (USB Method) it says TC-Box:~S
Also says it is unable to enumulate with USB device on Port 1.
Any idea as to why this is happening or what solutions to do?
Thanks
Click to expand...
Click to collapse
There was someone else reporting a similar issue. He finally managed to solve it by flashing stock RUU and then going through the whole rooting, s-off-ing and flashing ROM procedure.

I had the same problem.. I used a virtual machine instead of burning a CD!!

Easiest way to do it. Flash stock rooted froyo Rom with no a2sd and s-off.
Had same problem on some other Rom. Used usb, after flashing froyo everything went smooth.
Sent from my HTC Desire using XDA App

I think we are talking about S-OFF with Alpharev?!
Read in a serious german forum this problem could be caused by gingerbread. It is recommended to install a FROYO-Rom for S-OFF with Alpharev.
Detailled instruction:
1.) COMPLETE NANDROID- backup
2.) Download a FROYO- ROM (i used DeFroST)
3.) Copy it on your sd-card
4.) Start your phone in Recovery
5.) Do a FULL Wipe
6.) Flash FROYO- ROM
7.) Reboot your phone completely (to the homescreen of the new ROM)
8.) Download the iso from Alpharev-Homepage, check MD5 if file is complete and burn the ISO on CD
9.) Start your PC with the created disk [eventually u have to change your boot order (disk-drive on first position)]
10.) Follow the instructions on the screen (i only had to connect my Desire with PC in USB-Debug-Mode. Then I waited til i got the message that S-OFF is complete)
11.) After S-OFF is complete, boot your phone into recovery
12.) Restore the constructed backup
13.) Have fun with your previously ROM and S-OFF
Followed these steps tomorrow and it worked properly without any problems.

With this TuT, it´s worked for me...
I was trying about 5 hours to S-Off it... Hours of read threads, google und the questions was here...
Thank you very much
MatDrOiD said:
I think we are talking about S-OFF with Alpharev?!
Read in a serious german forum this problem could be caused by gingerbread. It is recommended to install a FROYO-Rom for S-OFF with Alpharev.
Detailled instruction:
1.) COMPLETE NANDROID- backup
2.) Download a FROYO- ROM (i used DeFroST)
3.) Copy it on your sd-card
4.) Start your phone in Recovery
5.) Do a FULL Wipe
6.) Flash FROYO- ROM
7.) Reboot your phone completely (to the homescreen of the new ROM)
8.) Download the iso from Alpharev-Homepage, check MD5 if file is complete and burn the ISO on CD
9.) Start your PC with the created disk [eventually u have to change your boot order (disk-drive on first position)]
10.) Follow the instructions on the screen (i only had to connect my Desire with PC in USB-Debug-Mode. Then I waited til i got the message that S-OFF is complete)
11.) After S-OFF is complete, boot your phone into recovery
12.) Restore the constructed backup
13.) Have fun with your previously ROM and S-OFF
Followed these steps tomorrow and it worked properly without any problems.
Click to expand...
Click to collapse

MatDrOiD said:
I think we are talking about S-OFF with Alpharev?!
Read in a serious german forum this problem could be caused by gingerbread. It is recommended to install a FROYO-Rom for S-OFF with Alpharev.
Detailled instruction:
1.) COMPLETE NANDROID- backup
2.) Download a FROYO- ROM (i used DeFroST)
3.) Copy it on your sd-card
4.) Start your phone in Recovery
5.) Do a FULL Wipe
6.) Flash FROYO- ROM
7.) Reboot your phone completely (to the homescreen of the new ROM)
8.) Download the iso from Alpharev-Homepage, check MD5 if file is complete and burn the ISO on CD
9.) Start your PC with the created disk [eventually u have to change your boot order (disk-drive on first position)]
10.) Follow the instructions on the screen (i only had to connect my Desire with PC in USB-Debug-Mode. Then I waited til i got the message that S-OFF is complete)
11.) After S-OFF is complete, boot your phone into recovery
12.) Restore the constructed backup
13.) Have fun with your previously ROM and S-OFF
Followed these steps tomorrow and it worked properly without any problems.
Click to expand...
Click to collapse
Interesting. I had problems (device not recognised / supported at this time) trying s-off with rooted stock froyo sense, after making a goldcard.
Never got to the bottom of it but as soon as I flashed oxygen (gingerbread) it worked fine!
CD method best, virtualbox kept crashing for me!

HP246 said:
With this TuT, it´s worked for me...
I was trying about 5 hours to S-Off it... Hours of read threads, google und the questions was here...
Thank you very much
Click to expand...
Click to collapse
No problem. I would really appreciate it if u press the "Thanks- Button" for this.

MatDrOiD said:
I think we are talking about S-OFF with Alpharev?!
Read in a serious german forum this problem could be caused by gingerbread. It is recommended to install a FROYO-Rom for S-OFF with Alpharev.
Detailled instruction:
1.) COMPLETE NANDROID- backup
2.) Download a FROYO- ROM (i used DeFroST)
3.) Copy it on your sd-card
4.) Start your phone in Recovery
5.) Do a FULL Wipe
6.) Flash FROYO- ROM
7.) Reboot your phone completely (to the homescreen of the new ROM)
8.) Download the iso from Alpharev-Homepage, check MD5 if file is complete and burn the ISO on CD
9.) Start your PC with the created disk [eventually u have to change your boot order (disk-drive on first position)]
10.) Follow the instructions on the screen (i only had to connect my Desire with PC in USB-Debug-Mode. Then I waited til i got the message that S-OFF is complete)
11.) After S-OFF is complete, boot your phone into recovery
12.) Restore the constructed backup
13.) Have fun with your previously ROM and S-OFF
Followed these steps tomorrow and it worked properly without any problems.
Click to expand...
Click to collapse
Thank you for that, I will most likely try this at a later date I was trying to get iNsertCoin flashed but of course needed S-Off and hit problems. So sticking with Reflex at the moment which looks exactly the same

[Q] Can't Root HTC Desire

Im stuck on rooting..
First when i try to install the HBOOT drivers it installs them as "HTC Serial Interface (COM4)" after the Android 1.0 thing (windows automaticly installs them and cannot abort that, and if i want to update it with the custom ones it says the current drivers are up-to-date.
So i dont have the "Android Bootloader Interface" option at the device manager.
Got the HTC Driver and HTC BMP USB drivers installed and removed HTC Sync.
Second, whatever Revoked version (i used 3.21-3.32, it keeps hanging on "waiting for Bootloader, make sure drivers are installed"
I've been repeating the process like 100x each step and still.
Additional info:
OS: Windows 7 64-Bit
Android 2.2.2 Original Stock (SoftwareNr: 2.29.405.15)
4GB SD Card (class 10)
Bravo PVT4 SHIP S-ON
HBOOT 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
Radio-5.11.50.26
Aug 10 2010, 17:52,18
I have used various methods from different forums none seem to work and i'm really clueless.
I've flashed Samsungs, Sony's, even MTK's flawlessly and this particular HTC device is a pain in the ass.
Ive used XDA guide: http://forum.xda-developers.com/showthread.php?t=1275632
and: http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
and: http://androidforums.com/desire-all...ked-windows-updated-11th-november-2011-a.html
and: http://androidforums.com/desire-all-things-root/503471-desire-all-things-root-guide.html
Is there anyone with a sollution because i really need more app space (or a bloatware free rom) and based on various comment on the sites mention didn't work as well as it should.

You'll want to gain s-off first before rooting. To do this you can use revolutionary.
First I'd suggest removing any drivers (and HTC sync) that you have already installed. Then setup adb/fastboot as it may be useful later. Finally install these fastboot drivers. Now to test if its being detected put the phone into the bootloader (turn off, then boot up using volume down + power). Next plug the phone into the computer via usb and open up a command prompt window. Run "fastboot devices" and the phones serial number should be shown. Let me know once you've done this.

Chromium said:
You'll want to gain s-off first before rooting. To do this you can use revolutionary.
First I'd suggest removing any drivers (and HTC sync) that you have already installed. Then setup adb/fastboot as it may be useful later. Finally install these fastboot drivers. Now to test if its being detected put the phone into the bootloader (turn off, then boot up using volume down + power). Next plug the phone into the computer via usb and open up a command prompt window. Run "fastboot devices" and the phones serial number should be shown. Let me know once you've done this.
Click to expand...
Click to collapse
Thanks i will try that and report back.
It would've been nice if any of those tutorials mentioned S-OFF needed before hand!
Edit: okay the phone is S-OFF, i will now proceed with the ADB thing but its downloading the SDK files as we speak...

@Chromium
Okay ive installed the adb files and set it all up. But i'm stuck on "fastboot devices" on the cmd command line saying it cannot find "fastboot devices"
If i run C:/adb fastboot devices i get a bunch of commands while the phone was booted into HBOOT (S-OFF ofc)
Also tried C:\adb\platform-tools>fastboot devices but nothing is shown
For some strange reason my device manager says SAMSUNG ANDROID PHONE > Android Bootloader Interface when i hit "Bootloader" in HBOOT (was testing this)
Ignoring the adb step: I rerun every step again but it's still stuck on "waiting for Bootloader, make sure drivers are installed" after running Unrevoked3
additional info:
Revolutionary S-OFF
HBOOT-6.93.1002
Edit: question; I installed Revolutionary CWM v4.0.1.4 through revolutionary after the S-OFF process (which is weird since installing a custom recovery needs root access).
Is it possible to install 'custom rooted roms' through "update from sdcard", without root access?
I ask before hand because i dont want to brick my phone..
I have done a backup in CWM, so i'm going to try and flash a rom...

Ok i succesfully flashed my htc with CM7.2 without rooting my htc in the first place.
I've been struggling with the rooting process for 2 days, but as i mentioned in my previous post i just flashed through revolutionarys CWM.
thank god!

(Even though your best ROM thread was closed, I did mention s-off and revolutionary and the guides...the ones you found are old)
You don't technically need root access to install custom recovery as you have found out.
You are already s-off, that's the hardest bit, rest is easy.
To root your existing ROM if you need to, flash superuser thru recovery
Don't know why fastboot devices didn't show, driver issue somewhere or not set up correctly.
Anyway if you can boot into the os, install 4ext recovery via app from 4ext,net.
Backup your sd card and use 4ext to partition your sdcard.
Then yes you can install a stock rooted ROM or any custom ROM of your choice, check for individual a2sd features or requirements

eddiehk6 said:
(Even though your best ROM thread was closed, I did mention s-off and revolutionary and the guides...the ones you found are old)
You don't technically need root access to install custom recovery as you have found out.
You are already s-off, that's the hardest bit, rest is easy.
To root your existing ROM if you need to, flash superuser thru recovery
Don't know why fastboot devices didn't show, driver issue somewhere or not set up correctly.
Anyway if you can boot into the os, install 4ext recovery via app from 4ext,net.
Backup your sd card and use 4ext to partition your sdcard.
Then yes you can install a stock rooted ROM or any custom ROM of your choice, check for individual a2sd features or requirements
Click to expand...
Click to collapse
I know and i've seen the link, but i started with the ROOT part from that website as i thought the S-OFF part came after the rooting process.
I just installed CM7.2 and everything worked fine.
I partitioned the SD card in the CWM menu but i didn't knew what size to pick so i went with 1024mb and 256mb cache.
Im glad cm works and my app space is 151mb however on first boot there was 148mn available and now after a reboot & googleplay store only 56mb is left????
Well atleast i can move apps to SD (i guess)
edit: I flashed Beanstalk 4.4 (release 4.5) with jmcclue's 250/5/182 hboot & 4EXT Recovery. Everything works perfect.

JMailuhu said:
I know and i've seen the link, but i started with the ROOT part from that website as i thought the S-OFF part came after the rooting process.
I just installed CM7.2 and everything worked fine.
I partitioned the SD card in the CWM menu but i didn't knew what size to pick so i went with 1024mb and 256mb cache.
Im glad cm works and my app space is 151mb however on first boot there was 148mn available and now after a reboot & googleplay store only 56mb is left????
Well atleast i can move apps to SD (i guess)
edit: I flashed Beanstalk 4.4 (release 4.5) with jmcclue's 250/5/182 hboot & 4EXT Recovery. Everything works perfect.
Click to expand...
Click to collapse
You've rushed into it without following instructions or understanding how things work................
- You shouldn't partition with cwm as it often makes badly aligned partitions (they don't work)
- You don't need to partition with cache as the ROM needs to be programmed use it, and has limited benefit anyway
- You're not actually using your partition if you don't flash an a2sd script or use an app to actually move things to the partition of the sdcard. Your 'move to sd' is moving part of the app to the original fat32 part of your sdcard, exactly the same as before you even rooted/s-off i.e no gain...
- You should have flashed a different hboot before you flashed the ROM as you're wasting space on /system, which is also why your seeing low memory already. Again you have exactly the same amount of internal space as before you rooted/s-off....
So....
- please flash 4ext recovery as instructed
- completely backup and re-partition your sdcard from scratch with that recovery, no swap or cache
- learn to flash cm7r2 hboot with fastboot, instructions in the earlier guide you found
- full wipe and reinstall cm7 ROM again
- flash a2sd script or use an app such as s2e to move future apps to your sd partition (sd-ext)
- Keep apps on internal to trick them to sd-ext, your memory won't necessarily appear expanded, but your partition is working
- install an app like DiskUsage to understand how all your memory is being used in the first place...
Seems a lot but you should have read and done this in the first place you can do it correctly now or run into trouble later when you have no idea why...
EDIT: only saw your edit after my initial reply.
Some of my points still stand...please at least understand how your memory is being used (DiskUsage)