Hey Guys,
I just tried to unroot my HTC Desire cause of warranty.
So I tried a ruu but it doesn't worked.
So i crated a PB99IMG an went to bootloader.
The bootloader made all but suddenly it said:
Main version is older / update failed !
Now I can't do anything than go to recovery
And at bootloader top those is standing:
BRAVO UNKNOWN SHIP S-ON
HBOOT-0.75.0000
MICROP-031d
TOUCH PANEL-SYNT0101
Radio-4.05.00.11
Ma 5 2010,21:12:15
Someone is able to tell me,what I can do that my phoen will work again (equal if rooted or unrooted)
tried my guide? I bet you haven't, and I bet this thread was pointless
bortak said:
tried my guide? I bet you haven't, and I bet this thread was pointless
Click to expand...
Click to collapse
Didn't tried it yet.
But I tried teh same RUU which you told. and there I'm getting the error that Main version is older !
So I'm actually s-on cause of an otehre ruu which i used before which amde me s-on but didn't flash a rom.
EDIT:
I downloaded your RUU again.
Made a PB99IMG and went to bootloader.
now it ask if I want to run update !
BUT my vol. up butten is broken (the reason why i want warranty)
so i cant confirm,any way to confirm without vol up ?
The error it's giving is impossible since you're flashing a RUU that is MUCH newer than what you appear to have there.. try the 2.3.3 RUU (since a WWE RUU won't cover warranty), that HAS to work.. and even if it gets stuck on the HTC screen or something it doesn't matter since you're getting it fixed anyway.
Related
Hi foks,
friend of mine has a HTC Desire, The phone had a T-Mobile ROM on it and I flashed the 1.21 on it using a goldcard (did not root it).
Now he got the notification of the froyo update and he updated his phone.
Now whenever I try to flash a rom, I get signature error.
And I found out why.
Bootloader:
Bravo UNKNOWN ship S-on
HBOOT 0.75
Radio 4.05.00.11
Here my own desire:
Bravo PVT1 ship s-on
HBOOT 0.80
Radio 5.09.00.20
The phone does work. But It is always waiting for a process and after like 1 min, it reboots all the time.
I think it has to do with the UNKNOWN thing in bootloader. But feel free to correct me if i'm wrong.
xmoo said:
Hi foks,
friend of mine has a HTC Desire, The phone had a T-Mobile ROM on it and I flashed the 1.21 on it using a goldcard (did not root it).
Now he got the notification of the froyo update and he updated his phone.
Now whenever I try to flash a rom, I get signature error.
And I found out why.
Bootloader:
Bravo UNKNOWN ship S-on
HBOOT 0.75
Radio 4.05.00.11
Here my own desire:
Bravo PVT1 ship s-on
HBOOT 0.80
Radio 5.09.00.20
The phone does work. But It is always waiting for a process and after like 1 min, it reboots all the time.
I think it has to do with the UNKNOWN thing in bootloader. But feel free to correct me if i'm wrong.
Click to expand...
Click to collapse
Mine also says UNKNOWN and works fine! Just turn off signature checking in clockworkmod and try again
AdamLC said:
Mine also says UNKNOWN and works fine! Just turn off signature checking in clockworkmod and try again
Click to expand...
Click to collapse
The phone is not rooted.
The signatue check error is what the RUU is saying.
He has tried to upgrade to froyo without a goldcard. You will need to flash the Froyo RUU with a goldcard. If you get a signature error try downloading the RUU again.
teppic74 said:
He has tried to upgrade to froyo without a goldcard. You will need to flash the Froyo RUU with a goldcard. If you get a signature error try downloading the RUU again.
Click to expand...
Click to collapse
Did this couple of times. Even tried several sd-cards. Gives me 401 Signature error....
Which RUU exactly are you trying to use on the phone? (full filename)
teppic74 said:
Which RUU exactly are you trying to use on the phone? (full filename)
Click to expand...
Click to collapse
Tried:
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed
RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed
Ok, the first one should work fine. Did you download it from here?
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
Try running it with the phone in fastboot mode (press back key and power to start up)
teppic74 said:
Ok, the first one should work fine. Did you download it from here?
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
Try running it with the phone in fastboot mode (press back key and power to start up)
Click to expand...
Click to collapse
Yes got the roms from conflipper's server. Already tried that method....
I think it's something with the goldcard. I had a hard time debranding it back in the days...
No one?????
He returned it for warrenty and got a brand new one.
Thread can be closed now.
I got a replacement phone from Sprint because my phone screen cracked. I'm trying to return it to stock, but now it won't boot past the fastboot/bootloader screen. I can't even get into recovery - when I choose that, it just sits there on the white startup screen. I used the unrevoked forever radio S-OFF/S-ON tool to get it to S-ON, and that's as far as I got.
Here's what it says at the top:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.93.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Jul 23 2010, 16:41:47
suggestions?
summerblink said:
I got a replacement phone from Sprint because my phone screen cracked. I'm trying to return it to stock, but now it won't boot past the fastboot/bootloader screen. I can't even get into recovery - when I choose that, it just sits there on the white startup screen. I used the unrevoked forever radio S-OFF/S-ON tool to get it to S-ON, and that's as far as I got.
Here's what it says at the top:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.93.0000
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.09.01
Jul 23 2010, 16:41:47
suggestions?
Click to expand...
Click to collapse
Use a RUU File thats the easiest way to do it bro...
Sent from Point A to Point B
unrevoked forever should work fine for hboot .93....i had to do mine 3 times before it removed the s-on to s-off hope that helps
luckylui said:
Use a RUU File thats the easiest way to do it bro...
Sent from Point A to Point B
Click to expand...
Click to collapse
i tried that and partway through it, i get:
ERROR[140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
summerblink said:
i tried that and partway through it, i get:
ERROR[140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Click to expand...
Click to collapse
What base are you trying to get to? Cause if your trying to flash a rom w a older hboot it wont allow that so ull need to flash into a hboot .93 , 2.02 or 2.10, ive had success that way... does it make sense? Lol
Sent from Point A to Point B
Thread moved to Q&A.
luckylui said:
What base are you trying to get to? Cause if your trying to flash a rom w a older hboot it wont allow that so ull need to flash into a hboot .93 , 2.02 or 2.10, ive had success that way... does it make sense? Lol
Sent from Point A to Point B
Click to expand...
Click to collapse
Yes, this is what you need to do. Download the RUU for 3.70... Use that one. If you are returning the phone anyway it doesn't matter if it is difficult to root. Is the S back on now though? Or still S-Off?
If S is still on try 3.29 ruu, if that does not work try 3.30...
After RUU there will not be custom recovery anymore so if S is still OFF after that you need to install custom recovery and keep flashing s-on until it says on and then run ruu again.
leenypost said:
Yes, this is what you need to do. Download the RUU for 3.70... Use that one. If you are returning the phone anyway it doesn't matter if it is difficult to root. Is the S back on now though? Or still S-Off?
If S is still on try 3.29 ruu, if that does not work try 3.30...
After RUU there will not be custom recovery anymore so if S is still OFF after that you need to install custom recovery and keep flashing s-on until it says on and then run ruu again.
Click to expand...
Click to collapse
the phone was rooted . . . i'm trying to UNROOT it. will that work? the only 3.70 i see on search is a rooted version . . . and a zip. would i rename that zip to PC36IMG.zip and put it on the root of the sdcard or something?
i tried renaming the 3.7 RUU zip file to PC36IMG.zip, loaded it through the bootloader, no dice. i also found an EXE version of the 3.7 - it started running and then i got an error:
ERROR[170]:USB CONNECTION ERROR
weird - it makes a usb connecting sound when i plug it in, and from my command prompt it responds to fastboot (but not adb commands) . . .
next steps?
Good day to all
Yesterday i get a bricked desire, that was only loading to bootloader. It is CID locked and not rooted. So i decided after some googling to find a suitable RUU, but i tryed aroud 15 and no luck. Flashing stops at radio upgrade and wont move. Now the phone is in a diferent state. It starts in a black screen with HTC sign and danger signs in corner. It still react on flashing, but now i cant do anything else. It just dont want to flash the radio. I found many advices and manuals, but they are for rooted and CID unlocked devices. So my question is... What now???
This screen appears.
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
Aug 10 2010, 17:52:18
RUU
Use the search. There are so many threads here from users who had the same problem.
man for this problem i have a solution ive descovered on my phone)
Hi guys I had this problem yesterday and I managed to bring back to normal just reinstall the stock hboot after you instal stock hboot restart the phone and install RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release_159811_signed 100% worked for me and others
verry simple don't panic for more question [email protected]
Original there where HBOOT 0.8.0001, but when i flashed RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release_159811_signed, during flashing phone 5x vibrate and stopped on 35%. He upgraded HBOOT to 0.93.0001 and now on start is this black screen.
did you tried what ive sayd up ???
How can i install stock HBOOT in this state? The normal stock ROM wont flash.
elegant047 said:
How can i install stock HBOOT in this state? The normal stock ROM wont flash.
Click to expand...
Click to collapse
Why would it not?
Swyped from my HTC Desire using XDA App
MatDrOiD said:
Why would it not?
Swyped from my HTC Desire using XDA App
Click to expand...
Click to collapse
As i said in my very first post... It freezes when he flash radio at 35%. And the question is... what now.
you can try to flash a recovery with android flasher and then instal a costum rom
Device is not rooted and not CID unlocked.
Any new ideas?
Would be nice to get some new hint i am nearly at end of possibilities.
why you tried to use ruu when you are on stock rom with branded device?
and did you bricked your device before flashing ruu.exe or after flashed it?
hey you can create a goldcard if your phone is recognised in fastboot in pc..
that will solve all your problems.
PHONE IS ALIVE Refridgerator trick worked. But still its overheating. Radio upgrade will be enough or its really damaged?
What about some giant active cooling :-D
I opened thedevice and inserted a piece of metal between processor and procesor cover with heatsinkin white pasta. For now no overheating. Posting from the desire
Ok so here goes, hoping you guys can help... I've searched and found a few threads related to a similar issue, tried everything suggested, and still nadda....
Being the forgetful fool I am, I flashed the most up to date official RUU on my rooted Desire with Oxygen HBOOT without flashing the downgader HBOOT first... The idea was to do a simple unroot back to stock...
Needless to say things didn't go well. I now have a silver HTC logo with the 4 warning triangles in each corner
Read that flashing the downgrader then the RUU again would work so...
Flashed the downgrader HBOOT using fastboot... success!
Ran the RUU again... ERROR! 140 wrong bootloader version.
Tried flashing and running various recoveries, boots, etc. using fastboot... all give ERROR remote 12 signature verify fail
Cannot get to vol down+power
Cannot get to back+power
When I have the silver HTC and unplug USB I get the following:
BRAVO PVT1 SHIP S-ON
HBOOT-0.80.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
Mar 29 2010,21:34:33
RUU (in orange box)
Any ideas if there's anything I can do to get the phone booting again??
Thanks a lot for any help you can give!!
cjacko said:
Ok so here goes, hoping you guys can help... I've searched and found a few threads related to a similar issue, tried everything suggested, and still nadda....
Being the forgetful fool I am, I flashed the most up to date official RUU on my rooted Desire with Oxygen HBOOT without flashing the downgader HBOOT first... The idea was to do a simple unroot back to stock...
Needless to say things didn't go well. I now have a silver HTC logo with the 4 warning triangles in each corner
Read that flashing the downgrader then the RUU again would work so...
Flashed the downgrader HBOOT using fastboot... success!
Ran the RUU again... ERROR! 140 wrong bootloader version.
Tried flashing and running various recoveries, boots, etc. using fastboot... all give ERROR remote 12 signature verify fail
Cannot get to vol down+power
Cannot get to back+power
When I have the silver HTC and unplug USB I get the following:
BRAVO PVT1 SHIP S-ON
HBOOT-0.80.0000
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
Mar 29 2010,21:34:33
RUU (in orange box)
Any ideas if there's anything I can do to get the phone booting again??
Thanks a lot for any help you can give!!
Click to expand...
Click to collapse
You are supposed to flash stock hboot, then flash hboot downgrader before RUU. This is because hboot downgrader only downgrades the hboot to allow RUU to s-on the phone. Technically now you are still on oxygen hboot. Are you able to fastboot flash hboot?
Sent from my HTC Original Desire using Tapatalk
Hmm ok so I'm even more stupid than I originally thought...
Don't think I can flash HBOOTs in fastboot
Whenever I try 'fastboot flash hboot ...' with the stock alpharev hboot I get the 'remote 12 signature verify fail' error...
Thanks for the quick reply
Well screw me sideways... I fixed it...
For anyone who lands in the same (stupid) position as my idiot self, I just flashed the official 2.3 Gingerbread update RUU...
Flashed first time, booted first time, now boots every time...
No idea how or why... but yay
My Desire has some issues, it can no longer detect either the SD or SIM cards.
Fortunately it's insured through my bank account so I want to send it off to get fixed.
Problem is that even after flashing RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe, the latest official ROM downloaded from Shipped ROMs, it's still showing as :
Code:
[COLOR="Magenta"]-Revolutionary-[/COLOR]
[COLOR="SeaGreen"]Bravo PVE3 SHIP S-OFF
HBOOT-6.93.1002
MI CROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Aug 10 2010 17:52:18[/COLOR]
I really would like it S-ON before returning it and have spent some time searching on how to do this with no success.
What am I doing wrong ?
first - u have to change hboot. download from alpharev bravo downgrade hboot, put it in sd card and flash, after this run RUU
if ur bravo don't detect sd card, choose fastboot, and flash hboot by this
Thanks - I'll have a look
I have to say I was a little confused by (bottom of first post) :
"If one day you want to S-ON your phone again, just reflash an original RUU rom !"
dik23 said:
Thanks - I'll have a look
I have to say I was a little confused by (bottom of first post) :
"If one day you want to S-ON your phone again, just reflash an original RUU rom !"
Click to expand...
Click to collapse
It will definitely work after downgrade.
Reflashing over revolutionary and alpharev hboot doesn't do the stuff, cause their hboots are write protected. It works only with downgrade, that's what it's made for.
Yes, that worked. Thank you neownc
Perhaps that guide I linked to needs altering. It is a bit misleading.