Blank screen, s-on, RUU not working. Help please - Desire Q&A, Help & Troubleshooting

Hi,
Please can someone help.
I have a desire which was originally Vodafone. I rooted, s-off, clockwork recovery etc and have been running custom roms for ages (Though I don't flash at all often.
I tried to bring it back to stock and flashed an original Vodafone ROM through RRU. It seemed to work but errored at the end. Now I am stuck.
I have no screen display at all. If I press power the phone vibrates once but nothing else. no splash screen, nothing. Pressing "back+power" doesn't do anything either.
If I load a stock RRU it used to run through but give me a Cust ID doesn't match error 131. I have now made a goldcard and now I get a bootloader 140 error. I have tried to use androidflasher but that reports I am now s-off so fails.
RUU reports I have image 2.33.161.2 now trying to change to 1.0.2.10 (although I have tried a number of wwe and vodafone RRUs
rru goes through bootloader. erasing user data and sending signature but then fails to the 140 bootloader version error
Is it the conflict of coming from custom roms or just that it will not downgrade to a lower rom? does anyone have a higher rom? Please help. I can't even get anything on the screen to know I am in bootloader although RRU obviously thinks I am
Please help. What are my next steps. I am now totally lost!
Thank you

Did u flash alpharev downgrader before flashing the ruu?
Sent from my HTC Desire

jmcclue said:
Did u flash alpharev downgrader before flashing the ruu?
Sent from my HTC Desire
Click to expand...
Click to collapse
No, That was the big stupid move! and I think what trashed it. That and the not having a Goldcard.
I have however finally solved it. I put in the goldcard and flashed rru from the HTC developers site.
http://forum.xda-developers.com/showthread.php?t=1772499
That fixed it. I guess it was complaining that the Vodafone version I had flashed badly was of a higher version number than the other one I was trying to fix with.
Took all day but finally got there.
Thanks for the reply

Cool, glad it works now
Sent from my HTC Desire

First off all you flashed amoled ruu to slcd device, or the opposite.
Once more, nobody wants to search the forum to see experience of other people ans simply use 2.3 RUU.
Sent from my HTC Desire using Flashes and Thunders

Related

RUU 1.15 wont flash - waits for bootloader

Hi
I've downloaded an HTC Europe 1.15 RRU that I used before and worked.
Now, however, it wont flash. I just get to the "waiting for bootloader" and then a "connection error". I tried rebooting into bootloader but then the RRU just counts upto 100 and then tells me there is a connection error.
The difference between now and last time is that I've updated my bootloader to Alpha-Rev bootloader and Clockwork Mod Recovery is installed. The phone is rooted and S-OFF as well.
I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair.
I guess I need to resintall some bootloader and recovery mod?? or is that in the RUU?
Any ideas/advice?
Android version 2.2
Baseband 32.47.00.32U_5.10.05.23
Kernel 2.6.32.15-gf5a401c
Build 2.29.405.2 CL263770 release-keys
Software: DJ Droid v1.8 (but also tried latest MoDaco, Pinky, CM6 and LeeDroid)
Browser: WebKit 3.1
HBOOT 0.93.0001
BRAVO PVT3 SHIP S-OFF
MICROP-051d
TOUCH PANEL-SYNW0101
Clockwork Recovery v2.5.0.7
Why do you want to put the FIRST ever RUU back onto your device? Just download the latest RUU (2.29.405.2) by clicking on my signature. This is assuming your phone in unbranded from the start, if not you'll need to get the RUU for your operator
Er, because I said ...
"I'm trying to restore the phone to factory condition in preparation for a return to HTC for repair"
Factory condition means ANY ROM that was meant for the unit - you don't need to go back to the first!!! So long as you're on an x.xx.405.x ROM you'll be fine!!! LMAO!!!
If you just flash the 2.29.405.2 RUU then you're back to stock so the factory will accept it
bloody hell.
saved me a ****ty weekend there pal.
nice1
cheers
will do this tonight and report back.
My HBOOT is 0.93.001 (flashed using alpha-rev clockword mod install utility). Some older RUUs refuse to load (waiting for bootloader and a reboot to bootloader whilst the RRU is still running - doesnt fix the problem). Appears to be waiting for a special signature from the bootloader. Is your link (RRU) likely to work do youo know ??
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Yeah S-OFF.
I'm okay with the PB99 - used that when creating gold card and downgrading.
The N1Table stuf is new to me. I'll google that now.
Thanks for the tip and link.
Cheers pal.
**EDIT:
Okay, so N1table is the partition table for sram/nvram chips.
I have not knowingly modified these, but in any event will grab
the stock HTC table just in case. I can only assume the hangup
is generated because the partition table is hardcoded in the RRU
rather than being read in by the RRU - or something like that.
Anyway, thanks once again pal.
[Q] The phone was purchased on the UK Orange network although no branding on the phone (orange square logo and orange applications). The phone was locked to the Orange network and the settings SLIGHTLY different than the unbranded phone my bro has. Will I need to get hold of the Orange RRU before sending to HTC for repair (as in will the IMEI number be registered to Orange or something)?
If it had the Orange ROM on it then you will need that before sending it back...now, an Orange RUU has never surfaced BUT I might know someone getting one today so if I hear anything I'll post back on here.
If you needed a gold card to flash the stock RUU then you will need the Orange RUU
With regards to S-OFF, unless you downloaded and flashed a new table you will still be on the stock Desire one
I used alpha-rev' s-off utility (cant recall the link and didnt save it) but unsure whether the table has been modified. I'll just download the HTC one. Simples.
DAMM. I thought I may need the Orange RUU. Yes, the stock RRU wouldnt install I recall; required a gold card and a bootloader downgrade as I remember. ****!
I've been searching for Orange RUU for months to no avail.
As I said, hold out a day or so as I think someone might be getting it from Orange
Leave it with me...
Acknowledged
My gracious thanks in advance.
Good luck!
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
ste1164 said:
Eddy if you get a stock Orange RUU you will be god . Hope you get it.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
+1 for Eddy being God
EddyOS said:
It won't be me but apparently someone is getting an Orange techie to debrand his phone and he's getting the RUU in case he needs to go back to stock...as soon as I hear something I'll update
Click to expand...
Click to collapse
Hang on; dya mean its possible to create an RUU or backup of a branded Orange phone - as indeed I had before I rooted et.al. ? Oh no, could I have created one - surely not ?
EddyOS said:
If you're currently S-OFF, which I assume you are, then get this file instead:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.zip
It's the same RUU but in ZIP form. Once downloaded remove everything from the name except PB99IMG (so the file is effectively called PB99IMG.zip) and copy it to the root of your SD card. Then boot into HBOOT and it will read the ZIP and ask you to continue. Say yes and once done reboot and you'll be back to stock. Then just remove the ZIP from the SD card and away you go!
Word of advice: I was S-OFF and using the N1Table and the first time I ran this it failed on the System partition and got stuck on the white HTC screen. I left it an hour, ran the PB99IMG again and it completed so if you are on anything other than the stock table I'd go back to that first using the file from AlphaRev before running the ZIP
Either way you should be fine
Click to expand...
Click to collapse
Nice1 Eddy. The ZIP did the trick. The RRU method didnt work but I expected that as it was looking for an original HBOOT signature.
So, back to HTC stock. Not sure whether they would accept it for repair though given that it was sold as a branded Orange handset. Can they check?
Well, I will give this a go. The reason for the repair is that I've installed god knows how many custom ROMs and:
1. wifi doesnt always work.
2. Data connection errors.
3. Random reboots.
4. 90% reboot when navigating in the car.
5. Failure to answer some incoming calls.
6. Sometimes outgoing calls carry no voice modulation (they cant hear me)
different problems depending on ROMs.
So, lets see how the stock does before I decide to send back/or not.
Thanks again Eddy.
No, the bloke at Orange is going to give the guy getting it debranded the Orange RUU so he can go back to stock if he needs to...
HTC can tell, and my still fix it and put the Orange ROM back on it, but they may also turn around and refuse to fix it due to having a different ROM to the original
You can get to stock Orange with a very complicated method. After debranding you would root the phone. Then apply the backup on my thread. You then remove the superuser.apk with adb. You then flash the two updates orange released this unroots your phone back to stock.
Sent from my HTC Desire using XDA App
Nice1 Ste, however, mine is SLCD not Amoled. The nandroid is from an Amoled handset. Wont work with mine. Nice idea tho.
Anyone have a nandroid from an Orange set??

[Q] HTC Desire boot problem

Ok, before you guys all start flaming, I read all the topics on Desire boot problems.
A friend of mine has a Desire which suddely rebooted and came into a bootloop. Sometimes it even got till the unlock screen, but most of the times it rebooted in the HTC Quitely brilliant screen.
Now ive tried to "fix" this:
I first tried to install the latest RUU:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed
It gave either connection error [170], or went into bootloader and gave another error (signature error)
next option was to extract rom.zip from the RUU from the %TEMP% folder, rename this PB99IMG.zip (3x checked that it wasnt zip.zip was), put this on my goldcard (http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/). after that boot into bootloader and let it flash.
This flash gave no errors/fail, after that rebooted my phone. Than there is a green circular arrow logo with the middle arrow pointing down.. After that the phone reboots one last time (without vibrating) and is stuck at the HTC logo.
Also tried recovery factory reset.. to no avail
About the phone:
HTC Desire
HBoot 0.93.00001
S-ON
Not rooted
EDIT POST: Just switched from english to dutch, lol, was interrupted while writing (sorry lordvoldemort).
english please..cant understand your language
Sent from my HTC Desire using Tapatalk
check the guide in my signature
I Dont see any options in your thread that I didnt point out above, and didnt work... As im still S-ON, the options are limited...
Sent it back to HTC and use your warranty.
Try to use 2.3 update. It worked on my desire with same problem
name.vic said:
Try to use 2.3 update. It worked on my desire with same problem
Click to expand...
Click to collapse
as much as I hate advising to use that particular RUU it MAY help you.. or just make it worse..
since you have a goldcard try other RUU's maybe
Dont think I can use any other RUU's because it might be an SLCD desire, which means any RUU lower than 2.xx will brick the screen..
BTW Ive tried the gingerbread RUU, one time it went flashing but stayed like that for 1,5 hour... pulled the plug...
Most of the times it gives a verification error..
I suggest u S-OFF/root ur Desire and install a custom ROM.
See these: http://revolutionary.io/
www.alpharev.nl
Afer u`ve successfuly S-OFFed, search for a suitable pre-rooted ROM for ur SLCD Desire, on xda-developers, there`s plenty to choose from
i_cs_u said:
I suggest u S-OFF/root ur Desire and install a custom ROM.
See these: http://revolutionary.io/
www.alpharev.nl
Afer u`ve successfuly S-OFFed, search for a suitable pre-rooted ROM for ur SLCD Desire, on xda-developers, there`s plenty to choose from
Click to expand...
Click to collapse
have you even read anything? he can't boot - therefore can't run revolutionary. THEREFORE he can't use it..

[Q] Phone stuck in bootscreen, no answer in troubleshoot

After breaking my previous desire i got a new one from insurance past friday. I s-off and rooted it with revolutionary and ran the alpharev cm7 r2 partition table. All went fine and i installed the CM 7.2 RC rom and started downloading all my apps and stuff.
All seemed fine untill i shutdown my phone last night and when booting it up this morning it doesn't boot up into anything. I can only get into Hboot and fastboot. I've tried booting into recovery but it gets stuck on the boot screen again.
Now i've read the Q&A troubleshooter posted above here and i have already tried reflashing recovery, which sadly still didn't boot after the reflash.
Now i'm completely stuck on what to do and have been searching for over an hour now.
I've read i could do a RUU for my phone, but seeing as alpharev has protection against that i'm not certain that would even help. What would be the best solution here to get my phone working again. (and if possible with the current data on it , i hadn't made a backup of the full install yet)
Edit: some extra info
Hboot 6.93.1002
Bravo PVT3 S-off
radio 5.11.05.27
CM 7.2 RC
clockwork, not sure newest version for desire afaik
Did you try to remove battery?
yes, seeing as that is the only option right now to turn my phone off .
I also ran fastboot oem gencheckpt to force boot into recovery. The phone got stuck at htc splashscreen. I posted the cmd image information in this post.
when i pulled the battery to shut down the phone, the cmd gave and "error, to many links"
edit:
i ran the alpharev downgrade image to overwrite my hboot and see if i could get into recovery after reflashing that aswell. Sadly this didn't work and after flashing both it still gets stuck at the htc splash screen
i ran the downgrade hboot again and will not try to fix it with a RUU
hmm, the phone is still recognized by the pc, but i have a black screen and can't get it to display anything. did i use a bad ruu or? I"m really confused now :|
after looking in the troubleshoot again i tried to flash the bravo stock from alpha rev, but i'm getting a FAILED <remote: signature verify fail>
well seeing as i most likelly need a goldcard now and don't have another android device laying around i will have to continue this tomorrow or tonight.
if ANYBODY has any advice everything is really appriciated!
what RUU did you flash?
if it was under 2.xx that means you did slcd brick have look here
flash bravo stock from alpharev, then run (if you have a goldcard) the 2.2 WWE RUU, or your carriers RUU (make sure it's the latest one)
Check shipped-roms.com
i think i ran this RUU
RUU_Bravo_HTC_Europe_1.15.405.3_Radio_32.30.00.28U _4.05.00.11_release_121865.exe
which i got from this post, which i now see is terribly out-dated xD.
I got my phone from vodafone in Holland, and i just saw an RUU for bravo that was shipped by vodafone UK which also supports the same radio as mine. Is it a safe bet to use that one for the recovery process?
I wasn't able to run any images right now from fastboot for some reason so i will indeed need to make a goldcard. Will do so tomorrow and report back if i've had any succes.
Thanks for the advise!
OK, so i'm a bit confused by that guide i'm afraid...
I've noticed that in step 4 that i'm unable to enter recovery (no surprise seeing as i was unable before the RUU).
I can boot in to fastboot and hboot i think seeing as i get the "device connected sound" in windows. When i then enter ADB devices or fastboot oem gencheckpt it gives me some information, which can be seen in the screenshot.
What i'm now confused about is, do i still need to make a goldcard, and if so how? I tried running that goldcard creater software but it couldn't pull a CID. Should i create a goldcard by just using a phone of my friend (desire s :|)? Or is it possible to just run the right RUU straight away seeing as i can connect to hboot and fastboot, let that run and when that is finished use revolutionary to root my phone agian.
Attached is the cmd for fastboot oem gencheckpt and adb devices, although normally the fastboot oem gencheckpt finished with a "FAILED <status read failed<too many links>>
Gimme bootloader information, also what state is the phone in now, and what have you tried so far. (quick summary)
My bad just read you last posts.
Try the Vodafone RUU, it should work, don't see why it shouldn't. If that fails, make a goldcard with your friends Desire S, and flash the 2.2 WWE RUU.
If that fails then use the 2.3 RUU.
Ah great!!! I ran the vodafone ruu and atleast now i'm getting fastboot and hboot displayed again.
I'll see how far i can get on my own now. Thanks alot for all your help
Darn, aren't there yet...
I can now get into fastboot and hboot WITH it being displayed so that is already a big plus. However i'm still on a off partition format so i need to flash that back to the original partition format.
I'm S-ON right now so i can't do it through fastboot.
So i made the goldcard through my friends phone and place a PB99IMG.zip containing the alpharev bravostock on the goldcard.
When i then boot into HBOOT it gives me the reading PB99IMG.zip but doesn't give me an option to run the update afterwards. I then checked with the RUU i ran from my pc and created an PB99IMG.zip of that and let it run from HBOOT thus checking if the goldcard was functional. This worked perfectly apart from the partition table being screwed.
How can i now either install recovery from my goldcard while being S-ON or how can i succesfully run the bravo_stock image from my goldcard?
edit: I know i could use the old s-off trick from alpharev but i would prefer to use revolutionary instead seeing as it's more up to date...
k i think i know what to do.
i'll just create a bootable USB with the 1.8 hboot from alpharev on it. S-off my device and restore the partitions to stock.
Then run the RUU again so that my phone returns to stock sense and S-on.
After that i should be the basic root process all over again by running revolutionary etc right?
If you're S-ON. You DO NOT need to touch the hboot, and you can't anyway.
If you've got a goldcard just try the WWE RUU. And if that doesn't fix it then the 2.3 RUU.
That's all you need to do. NOTHING else.
The 2.3 RUU (the vodafone one i downloaded) doesn't work.
I don't think any RUU will work for my seeing as i'm still on the CM 7 r2 partition layout instead of the original sense layout (a little mistake i made when running the first faulty RUU). I'll try to run the WWE RUU first, but i don't think it'll achieve anything.
If i would now run the alpharev 1.8 hboot from a bootable USB it shouldn't put my device at risk right? :|
Edit:
i'm actually getting CID incorrect from the WWE RUU from the troubleshoot thread and from another WWE RUU i downloaded from shipped-roms.com
edit2:
alright, i tried 2 WWE RUUs, which when ran from my PC give me ERROR[131]: customer-ID error and a CID incorrect when done from my goldcard... i also tried alpharev hboot 1.8 but that didn't work either for the obvious reason that you need to boot into android and enable usb debugging and the WWE RUUs for i do not know what reason .
Damn i thought i had figured it out before going to college but aparently i was wrong >.<
i don't know if it's relevant but when i try to boot normally i get the HTC splash screen and it vibrates 7 times in a row...
So i think my goldcard might not be as golden as it should be. Should i try it with my other microSD, the one that i actually use in my phone, an 16 gb kingston?
If so can i use the same goldcard.img or should i create a new one?
bortak said:
If you're S-ON. You DO NOT need to touch the hboot, and you can't anyway.
If you've got a goldcard just try the WWE RUU. And if that doesn't fix it then the 2.3 RUU.
That's all you need to do. NOTHING else.
Click to expand...
Click to collapse
Dear god how many times do I just need to repeat myself.
Just download http://www.htcdev.com/process/legal_download/152 , boot into fastboot mode, then run RUU.exe
There is no vodafone 2.3 RUU, there is only one, and it is unbranded.
Elightos said:
So i think my goldcard might not be as golden as it should be. Should i try it with my other microSD, the one that i actually use in my phone, an 16 gb kingston?
If so can i use the same goldcard.img or should i create a new one?
Click to expand...
Click to collapse
If you still get CID error - you do not have a goldcard. Simple as that.
Elightos said:
The 2.3 RUU (the vodafone one i downloaded) doesn't work.
Click to expand...
Click to collapse
The 2.3 RUU always does something, if not for better than for worse.
ah right i'm sorry, i was a bit confused about that ruu because of some of the information displayed on shipped-rom.com. Prolly read it wrong or something.
Anyway the 2.3 RUU did indeed fix it! quite surprised after all this really didn't expect it! Thanks out a load and i'm sorry for touching a nerve there, it's just the first time doing anything like this so it was all a tad bit confusing!
Elightos said:
ah right i'm sorry, i was a bit confused about that ruu because of some of the information displayed on shipped-rom.com. Prolly read it wrong or something.
Anyway the 2.3 RUU did indeed fix it! quite surprised after all this really didn't expect it! Thanks out a load and i'm sorry for touching a nerve there, it's just the first time doing anything like this so it was all a tad bit confusing!
Click to expand...
Click to collapse
Lol don't worry about it, everyone starts of a newb I remember posting some scare stories of mine a while back of when I first started messing with my phone

Installing Stock Rom doesn't work

Hi there,
as I recently bought the HTC One X, I wanted to reinstall a Stock Rom to my old Desire. Unfortunately it won't work for some reason, as I always get an Error [110].
I have tried the following releases from this thread: http://forum.xda-developers.com/showthread.php?t=695667 :
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
(the phone used to be branded by o2 Germany, but I wanted to install a branding-free rom).
When I try to start the boot loader of the Desire now, I just get the HT screen with warning signs in all 4 corners. Please find attached a photo of the screen + a screenshot from the error message (for some reason it's in German, but you'll get the idea).
As I cannot access the actual hboot (CM7rev2 hboot was installed) I can't even install a "normal" rom.
As I don't necessarily need the phone right now it's not that urgent, but I hope you can help me anyway.
Cheers!
did you change hboot back to stock? I haven't done it first time and got the same problem. there is a solution but can't remember where.. try googling..
Sent from my HTC Desire using Tapatalk
No, forgot about that, but now it seems like it's too late to do this, isn't it?
From my understanding, that state your phone is in is fastboot. That means you can probably flash the hboot downgrader from alpharev and run a RUU again.
via xda app
your phone is in fastboot mode at the HTC logo with 4 "!". Download hboot downgrader from alpharev and flash it before rerunning RUU.
Sent from my HTC Original Desire with Android 4.0.4 ICS using Tapatalk
but if you dont have S-Off, cant access to anything instead of fastboot.. from which i can only flash stock ruu's but no one of ruu's are installing successfuly.
so i cant flash hboot, recovery or anything else... that means that the only solution is to reach nearest JTag service...
hm... but if he forgot to downgrade then I assume that he was s-off. so it's doable. I was there... scared the p*ss out of me... ;-)
Sent from my HTC Desire using Tapatalk
me to have some problems in this thread
http://forum.xda-developers.com/showthread.php?p=25349685#post25349685
heraSK said:
hm... but if he forgot to downgrade then I assume that he was s-off. so it's doable. I was there... scared the p*ss out of me... ;-)
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
He should still be S-Off if he's still on CM7r2 hboot.
Sent from my HTC Original Desire with Android 4.0.4 ICS using Tapatalk 2
It won't work with revolutionary / alpharev, it's always stuck at "Waiting for device".
I really don't know what to do now. Any other ideas?
EDIT: I also tried unrevoked just to see if it recognizes my phone, but its the same there: "Waiting for device".
Its late and I'm tired so sorry if you've already tried this...
Install HTC software on your pc and android sdk (to get the drivers and fastboot)
Plug in your phone when its on the 4 !'s screen
fastboot flash alpharevs bravo_downgrade.img
unplug the phone, pull the battery, put it back in, turn it back on then plug it back in (or just reboot the boot loader with fastboot)
then try running this RUU http://www.filefactory.com/file/b4a4027/n/RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
If that doesnt work see what version it says you're when the ruu says what version you're on and what you're updating to and download the ruu with the same number as the one you already have and see if that helps.

error 131 using RUU

Hi, i am aware of fact that this propably happened to someone else before, but search wasnt much of use (i tried it for almost hour)
Got slighter problem, i need to unroot desire for warranty purposes, so I used RUU (download RUU, connect phone and run ruu.exe)
i got error 131 in procces (while using several roms from shippedroms, first branded TMO RUUs since phone was originaly branded by tmo, then ww ruu) and now i cant load bootloader, phone only vibrates when i try to turn it on, dont you have any help/links for guides to solve my problem? any help would be really appreciated.
Id try goldcard method with PB99IMG.zip, but i cant load bootloader :/
P.S. I can see phone in windows device manager
myusernamewastoken said:
Hi, i am aware of fact that this propably happened to someone else before, but search wasnt much of use (i tried it for almost hour)
Got slighter problem, i need to unroot desire for warranty purposes, so I used RUU (download RUU, connect phone and run ruu.exe)
i got error 131 in procces (while using several roms from shippedroms, first branded TMO RUUs since phone was originaly branded by tmo, then ww ruu) and now i cant load bootloader, phone only vibrates when i try to turn it on, dont you have any help/links for guides to solve my problem? any help would be really appreciated.
Id try goldcard method with PB99IMG.zip, but i cant load bootloader :/
P.S. I can see phone in windows device manager
Click to expand...
Click to collapse
I'm preety sure that you installed amoled RUU and you have slcd device so the screen doesn't turn on.
Try Bortak's guide.
Sent from my HTC Desire using flashes and thunders
will do... it didnt occured to me that this could be a problem
myusernamewastoken said:
will do... it didnt occured to me that this could be a problem
Click to expand...
Click to collapse
But it is. If you install amoled related RUU and you have slcd device you will end up with screen not working. In my opinion the best choice ti install is 2.3 RUU because it is made for all screen versions plus you won't get 131 error which is CID incopatibility cause it's the same for all regions. And you won't destroy the warranty.
Sent from my HTC Desire using flashes and thunders
sounds more than logical, thanks for that, but its giving me error 131 even with RUU downloaded from slcd brick part of bortak's guide
myusernamewastoken said:
sounds more than logical, thanks for that, but its giving me error 131 even with RUU downloaded from slcd brick part of bortak's guide
Click to expand...
Click to collapse
If I'm right in that part of guide you should do reinstall using a .zip file on your sd card.
Sent from my HTC Desire using flashes and thunders
part 5, slcd brick (my problem), step 3, plug USB and run RUU... i cant flash it from sd card since i dont know what am I doin
myusernamewastoken said:
part 5, slcd brick (my problem), step 3, plug USB and run RUU... i cant flash it from sd card since i dont know what am I doin
Click to expand...
Click to collapse
I'm sorry I forgot to ask you one question, which hboot did you have prior flashing of RUU?
0.93
Are you sure you have bootloader drivers on your PC?
I'm sorry for not reading carefully, do not use WWE RUU from slcd brick guide use 2.3 RUU that can be obtained from htc dev site.
I got ADB, not sure if I need something else, long time ago I registered at htcdev.com ... but tbh I dont know what I need to DL there
edit: tryin htc ruu now
myusernamewastoken said:
I got ADB, not sure if I need something else, long time ago I registered at htcdev.com ... but tbh I dont know what I need to DL there
Click to expand...
Click to collapse
I've just opened a thread about it.
http://forum.xda-developers.com/showthread.php?t=1772499
EDIT: Just give me a word if it worked.
there was some progress, but not as much as I think it would be... phone restarted itself in middle of update several times in row (or i think, it vibrated several times in few seconds, it has happened before, its one of reasons it goes to warranty service) and RUU gave me unknown error (forgot number, but it was labeled as unknow error).
screen is working now, after turning on, if USB is plugged, i see htc logo with exlamation marks in corners, if I unplug usb, i can see bootloader with only option, RUU (instead of usual 4 ones when phone is ok). tried to run HTC RUU again, but it fails after system update part, giving me error 152: image update error
after disconnection of usb, phone gives me table where everything is ok, except radio_v2, where is instead of OK some "fail-PU", after phone restart, i am stuck at htc logo with 4 trinagles in corner, pluging/unpluging usb gives me white screen with that RUU option only
Something went wrong try to remove battery and try once more with RUU. If no luck try goldcard method with WWE .zip.
Also try to extract rom.img from RUU and try to run it from goldcard.
some guys on xda says you should try RUU over and over and over... and most of them says this is baaad situation, will GC work?
You can try with GC and WWE RUU you may be lucky. Everything sounds lie you have some issue with flash memory of you phone.
And of course, try as many time as you want you may have success.
I put phone into Freezer, then performed RUU and it works now gotta love that piece of mashinery btw any idea about TMO branded ROM for slcd desires, so i dont do any funny shiet again?
btw i really apreciate your will to help, these kind of ppl are rare these days, thank you man
You're welcome, I totally forgot about that s**t with freezer, sometimes it gets overheated so nothing works.
Forget about branded RUUs, you never know what will you get at the end. Now try revolutionary, get s-off and root, and there's a plenty of roms you can try. Go here and you have it all:
http://forum.xda-developers.com/showthread.php?t=809328
Plus hboot change is recommended (why don't you get more space when you can).
alpharev.nl
I had s-off and root and I will have it again, but still, need to put phone in service for warranty purpose and in our country, it isnt any simple, thats why branded rom :/
btw that **** with freezer doesnt surpise me, i am giving it to service partly for overheating problems... and leaving phone without battery for a while to cool down was my standart phone starting procedure, but I had no idea that even harder temperature decrease has such influence on performance (while using RUU, phone was at standard room temp.).
Anyway, thank you again, you helped really lot

Categories

Resources