Related
Hi xdaers
4 days i am bizzy to find a solution to fix my bricked slcd htc desire
i downloaded 7 RUU'S to fix my slcd, but when i start the RUU, it gives me a USB error some of found my desire but gave me an bootloader error
i can't even see anything on my device
PLEAS SOMEONE HELP ME what i am i doing wrong...?
I WILL DONATE to the man(or woman) who help me out with my problem
1. This is in the wrong forum
2. What ROM was your phone originally on when you first got it?
can you enter recovery? ( while phone is turned off, turn it on keeping pressed the back button..
Thnx for the reply
1. This is in the wrong forum
yea im sorry kinda new to xda
2. What ROM was your phone originally on when you first got it?
It was on Froyo 2.2 then i rooted my phone and installed CM and did the s-off from aplharev
4 days ago i ran a RUU that bricked my phone..
erto90:
i can't see anything on the, but when i press the power button, it vibrates
and if i hold power+voldown and wait 5 sec or something and i press power+voldown it vibraten again so....
when i press power+back from scratch nothing happens
eraser43 said:
erto90:
i can't see anything on the, but when i press the power button, it vibrates
and if i hold power+voldown and wait 5 sec or something and i press power+voldown it vibraten again so....
when i press power+back from scratch nothing happens
Click to expand...
Click to collapse
It sounds like the HBOOT has been corrupted somehow. There is no way of fixing this yourself.
You will have to return it to HTC and see if they will fix it for you.
You could try this http://forum.xda-developers.com/showthread.php?t=768256
I had a similar problem when I first got my SLCD. I installed a different HBOOT which showed a blank screen all the time. This process might work for you.
Just as a matter of interest, what exactly did you flash before it bricked?
_thalamus said:
It sounds like the HBOOT has been corrupted somehow. There is no way of fixing this yourself.
You will have to return it to HTC and see if they will fix it for you.
Click to expand...
Click to collapse
are you serious? i think there is a solution that is cant find, need some help
Like _thalamus said, if you could tell us what you did it could be easier to help you.
Did you flash an old clockworkmod recovery that was meant for the Amoled version ?
Did you try to S-Off your device ?
schwags said:
You could try this http://forum.xda-developers.com/showthread.php?t=768256
I had a similar problem when I first got my SLCD. I installed a different HBOOT which showed a blank screen all the time. This process might work for you.
Click to expand...
Click to collapse
i can't
"Enable USB debugging on your phone. Ensure 'ask me' is set under 'Connect to PC' setting with 'charge only'. Plug in your phone."
i think i got hboot 0.93, how do i check this?
eraser43 said:
are you serious? i think there is a solution that is cant find, need some help
Click to expand...
Click to collapse
Deadly serious.
You get a bootloader error when trying to flash a RUU. This means that the computer can't talk to the bootloader.
You say it vibrates every time you click power and vol down, which suggests that the bootloader isn't initialising at all.
Can you please answer my question regarding what you flashed before it bricked?
eraser43 said:
i can't
"Enable USB debugging on your phone. Ensure 'ask me' is set under 'Connect to PC' setting with 'charge only'. Plug in your phone."
i think i got hboot 0.93, how do i check this?
Click to expand...
Click to collapse
turn on your phone on and then try installing this ruu
eraser43 said:
i think i got hboot 0.93, how do i check this?
Click to expand...
Click to collapse
You can't check it if you can't boot into the bootloader.
stoned99 said:
Like _thalamus said, if you could tell us what you did it could be easier to help you.
Did you flash an old clockworkmod recovery that was meant for the Amoled version ?
Did you try to S-Off your device ?
Click to expand...
Click to collapse
i did flash an ruu, and it gave me a warning and said something like bootloader like that
before that i had cyanogenmod6.1rc2 s-off with alpharev's method, i flashed the ruu and it "bricked" no display
eraser43 said:
i did flash an ruu, and it gave me a warning and said something like bootloader like that
before that i had cyanogenmod6.1rc2 s-off with alpharev's method, i flashed the ruu and it "bricked" no display
Click to expand...
Click to collapse
Which RUU did you try to flash and at which stage did it give you the error?
_thalamus said:
Deadly serious.
You get a bootloader error when trying to flash a RUU. This means that the computer can't talk to the bootloader.
You say it vibrates every time you click power and vol down, which suggests that the bootloader isn't initialising at all.
Can you please answer my question regarding what you flashed before it bricked?
Click to expand...
Click to collapse
i did flash an ruu, and it gave me a warning and said something like bootloader like that
before that i had cyanogenmod6.1rc2 s-off with alpharev's method, i flashed the ruu and it "bricked" no display
VLADSLAYER said:
turn on your phone on and then try installing this ruu
Click to expand...
Click to collapse
i'm downloading it, will try..
eraser43 said:
i did flash an ruu, and it gave me a warning and said something like bootloader like that
before that i had cyanogenmod6.1rc2 s-off with alpharev's method, i flashed the ruu and it "bricked" no display
Click to expand...
Click to collapse
turn on your phone on and then try installing this ruu
ShirazSuleman said:
Which RUU did you try to flash and at which stage did it give you the error?
Click to expand...
Click to collapse
it stopped at the ERROR [140]: BOOTLOADER VERSION ERROR then my phone stopped giving my a display .just black.
My incredible because the system hard case set screen flash tip error caused ID131 I tested all the oe ROM is the problem now Fboot model machines can enter the gold using flash machines are S - everyone please god to help me this is my mailbox
Wow. Not sure I understand the question.
lolwut?
zhaowenbiao said:
My incredible because the system hard case set screen flash tip error caused ID131 I tested all the oe ROM is the problem now Fboot model machines can enter the gold using flash machines are S - everyone please god to help me this is my mailbox
Click to expand...
Click to collapse
Boot into recovery and flash a new rom.
I tried to replace the ROM, but still the same case of machine error ID131 S-ON HBOOT-0.79.0000 RADIO-2.15.00.08.88 phone back or given the same screen you ask what are the solutions
Whether the information is lost inside the phone Thanks for your reply trickster2369
zhaowenbiao said:
I tried to replace the ROM, but still the same case of machine error ID131 S-ON HBOOT-0.79.0000 RADIO-2.15.00.08.88 phone back or given the same screen you ask what are the solutions
Whether the information is lost inside the phone Thanks for your reply trickster2369
Click to expand...
Click to collapse
Which Rom are you flashing most roms require hboot 92. Try updating hboot.... and I'm having a hard time understanding what you are writing bro lol
Sent from my Incredible using XDA App
zhaowenbiao said:
I tried to replace the ROM, but still the same case of machine error ID131 S-ON HBOOT-0.79.0000 RADIO-2.15.00.08.88 phone back or given the same screen you ask what are the solutions
Whether the information is lost inside the phone Thanks for your reply trickster2369
Click to expand...
Click to collapse
Your radio number does not make sense. Was that the radio on the phone or did you flash it? The link below will give you d/l links to 4 different Inc radios. Also, as already suggested, you should update your HBOOT.
http://wiki.cyanogenmod.com/index.php?title=Support_Downloads#HTC_Incredible
Also, I am not sure what you are trying to do. Did you flash a gold card to use the Incredible on a different network than Verizon?
Check this link out.
http://android.modaco.com/content/general-discussion/305672/creating-a-goldcard/
Also, when all else fails RUU back to stock:
http://dougpiston.com/
S-ON HBOOT-0.79.0000 RADIO-2.15.00.08.88 This is my mobile phone into HBOOT content. I tried to updateHBOOT, but do not load into the HBOOTPB31IMG.zip file.
Spence341 Thank you for your reply spence341.
zhaowenbiao said:
S-ON HBOOT-0.79.0000 RADIO-2.15.00.08.88 This is my mobile phone into HBOOT content. I tried to updateHBOOT, but do not load into the HBOOTPB31IMG.zip file.
Spence341 Thank you for your reply spence341.
Click to expand...
Click to collapse
I missed that your phone is not rooted. You can't flash custom roms over an Incredible that is S-on.
To root your phone:
http://unrevoked.com/
I want to unlock the S-ON, but my phone can not enter the system can only enter HBOOT mode unrevoked3 can not connect to phone
Use the RUU as suggested then on doug piston's site.
hi
i just downgraded my desire hd and then did a radio s-off but then i wanted to do a S-OFF.
i used the easyS-off but then it said bootloader corrupt do not reboot.
i already tried without "I Have Radio S-OFF" then it just says connection problem
i have charged only and debugging turned on
what now?
thnx
hmm what about Easy Radio Tools?
i used that for radio s-off
it worked now!! thnx to this guy
http://forum.xda-developers.com/showthread.php?t=999219
second post!!
I would be hesitamt to reboot though, haven't used the easytool as I personally prefer to know what steps are being carried out, but if it warns that the bootloader is corrupt I wouldn't reboot until I knew the situation is corrected.
Hello guys (I suppose most of the visitors are in fact guys ),
I downgraded my DHD to 1.32 this week and managed to get root-access and did a successful Radio S-OFF using the One click Radio S-OFF.
However; this morning I tried the One click ENG S-OFF but the first time I tried to run the tool I got an error stating "Connection error (SD)". Rebooted my phone and tried again.
This time I got the error "Bootloader corrupt, contact XDA".
After I almost crapped myself I started to search for a solution; someone on this forum stated to go to application settings - superuser - and clear data. Did it and then I got a bunch of applications which did a forced close.
Tried the One click tool again and got the same error (Bootloader corrupt).
In the meanwhile I got all this popups regarding android.process.acore needed to close which finally resulted in an unusable phone so I rebooted...
Thank god this went alright and my phone is up and running again but...
I think the last failure was probably caused by the One click app that doesn't have root access (didn' t get a popup though), but I'm a little afraid to try it again.
Does anyone know if it's save to try it again?
enz0123 said:
Does anyone know if it's save to try it again?
Click to expand...
Click to collapse
Why not do it longhand? Concise instructions are available here, I realise you already have root but even if you follow the instructions from the begining they aren't gonna do any harm.
Thanks, that could be a solution however I found out that I didn't check the box "I have Radio S-OFF
Tried again with the checkbox checked but got the same error again.
The files that were copied to my SD-card at the first attempt are still there.
Is it safe to remove these files?
Maybe that solves it...
It is very important, that you agree the super user request while the tool does its job.
I had the same problems some weeks ago (bootloader corrupt), because during the flash my display timeout was reached and the super user request failed (black locked screen).
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.
KaseDesire said:
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.
Click to expand...
Click to collapse
Which is one reason I favour doing it long hand at least then youd know it's failed to flash the bootloader
Hmm, strange.
When I boot into the bootmenu (vol. down + power) it states the I'm already ENG s-OFF and hav CID 111111...
Something must have gone right....
However I can't find the line anymore that states that I have Radio S-OFF, is this normal behaviour?
KaseDesire said:
It is very important, that you agree the super user request while the tool does its job.
Click to expand...
Click to collapse
Exactly! The instructions don't mention it, but when you run the easy s-off exe, it goes through a few steps and then your phone will ask you to allow superuser access. So have your screen on and be ready, and THEN run the easy s-off utility. That's all it was for me. I hit "OK" on the error message, tried it again but this time watched my phone and allowed SU access, and it worked fine.
Hi,
I'm posting here because i had the same problem ( Bootloader corrupt etc ... ).
First I rooted my DHD, and made it Eng s-off and installed a rom a few month ago.
Today I wanted to install another rom, and flash the radio.
But I did not remenbered if I already had the radio s-off, so i installed the 1.32 stokified rom, used the easy radio tool ( v2.2 ) and when i wanted to use the easy s-off tool ( v05 ), the program gave me the error message concerning the bootloader corrupt and stuff. I tried it with "I have radio s-off" ticked, and when I try it with unticked, I have a connection error message.
I tried to delete the data from SU, but it didn't help, and then I noticied ( remenbered ) that SU did not asked me the authorizations when I used easy radio tool ans easy s-off.
Anyone have an idea how I can fix that ? Maybe unistall/reinstall SU ?
HTC Desire HD radio S-OFF steps
http://www.youtube.com/watch?v=dTFphGbgqbQ&feature=player_embedded
Yes I did that after reinstalling the 1.32 rom, excepted the Visionary steps.
The root is permanent no ? I did it on my previous rom, so I don't have to root it again when I install another rom ?
Anyway, my DHD rebooted when I tried to secure the battery compartment, the bootloader wasn't corrupted, it's fine.
So I checked the bootload, I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?
HornAdama said:
I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?
Click to expand...
Click to collapse
Yes, you can install custom roms and flash radios now.
So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
papercutout said:
So I've been trying to root my dads old Desire for a while now, with no success - it is locked to o2 and I'm on Orange. I didn't really want to pay to unlock it, and rooting it would have been nice. I've done two phones before, so I figured it shouldn't be too bad. Eventually I discovered it was HBOOT 1.03, and this was the problem, so the solution was to backdate the software to an earlier version (the phone is still S-ON and I cannot get this thing to take ANYTHING)
I was trying to roll back from Froyo to 2.1.
The current problem is that now the phone will not boot. With a simple turn-on it just sits at the white HTC screen, or if you go into Hboot it tries (what I assume is) 'fastboot' and checks the PB99IMG.zip file on the SD card. If I say I don't want to update and go to 'recovery' it loads the screen with the exclamation mark in a triangle in it. The problem here is that pressing up+power does nothing. I've tried a quick press, and a long hold multiple times, and with no result except the first time. Unfortunately I didn't go through the proceedure the first time, assuming it'd work again. Damn!
If I start the update it says 'can not roll back the hboot version'. It also fails on the radio_v2.
Any help will be much appreciated, and if you need any details (I've probably missed something) please ask!
Thanks
Click to expand...
Click to collapse
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
abaaaabbbb63 said:
If it fails with Radio_v2, then it's a radio brick, and that's the reason it won't boot. I'm afraid you can't do much, due to the hboot version.
Click to expand...
Click to collapse
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
papercutout said:
I'm not too worried about getting a different rom on it, or rooting it or anything any more, currently I'd like to just put it back into a working state, as it was, probably locked to o2, if you've any suggestions on how to do that?
Click to expand...
Click to collapse
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
abaaaabbbb63 said:
First, try this:
http://forum.xda-developers.com/showthread.php?t=1564644
Click to expand...
Click to collapse
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
papercutout said:
The one step here I'm halted by is producing a Goldcard - the link to the website on the tool doesn't work any more (I've scoured t'internet, and that's the general consensus). Any idea where else I can input the CID to get a Goldcard Image?
Also how do I run the RUU on my computer? What file is it in the HTC Desire Android Upgrade folder I need to run? Afterall, there's no file titled 'RUU.exe'
Thanks
Click to expand...
Click to collapse
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site :http://www.htcdev.com/bootloader, and then try installing a custom recovery.
abaaaabbbb63 said:
Just realized that it wouldn't work, because you have to boot your phone for the downgrader tool.
You could try something else. Unlock your bootloader using the HTC Dev site and then try installing a custom recovery.
Click to expand...
Click to collapse
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
papercutout said:
I've unlocked the bootloader (although obviously I'm still S-ON and HBOOT 1.03), so how would I go about installing a custom recovery?
Everything I can find online implies I need to do it starting with the phone up and running...
Thanks
Click to expand...
Click to collapse
You download this:
http://forum.xda-developers.com/showthread.php?p=28277117
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
abaaaabbbb63 said:
You download this:
http://forum.xda-developers.com/attachment.php?attachmentid=1631968&d=1357780284
You extract the recovery.img from it.
You then use fastboot to flash it:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
papercutout said:
That worked spot on! Have you got anything you'd recommend I put on there now? (factory reset didn't do anything, didn't really expect it to)
I tried cyangenmod7 for the desire, but with no luck. File 'BAD' or somethign when tried to read it from the SD card.
Click to expand...
Click to collapse
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
jmcclue said:
Can ya post the link to the thread and not just post the PB99IMG file? Thanks
Click to expand...
Click to collapse
Sorry jmc. Will do
abaaaabbbb63 said:
Try a MildWild ROM. Maybe the CM7 download was somehow faulty.
Click to expand...
Click to collapse
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
papercutout said:
You're getting good at this
So, that's on and working, but it's still locked to the carrier, o2. I've just tried 'HTC Desire unlock v0.9.5' but that didn't work (despite the program telling me it went flawlessly).
Any more suggestions?
Click to expand...
Click to collapse
Try using a different USB port.
abaaaabbbb63 said:
Try using a different USB port.
Click to expand...
Click to collapse
Nope, nada. I tried v0.94 too. Nothing again. I guess I'll need to get a key. Damn that hboot 1.03!
At least the phone is actually WORKING now though, thanks to you, appreciated.
Ok so real quick….I'm not tech savvy. I usually get the new HTC One, watch a youtube tutorial, and install ViperROM. This time around I get to the finish line and I keep getting the same "set_perm failed" …..I tried twrp hima 2.8.6.4 …still the same problem. I'm ready to give up. Please help me
We need more details.. Is your phone s-off? Also did you flash the correct firmware? And is your bootloader unlocked.
Sent from my HTC One M9 using XDA Free mobile app
NjEcTi0N said:
Ok so real quick….I'm not tech savvy. I usually get the new HTC One, watch a youtube tutorial, and install ViperROM. This time around I get to the finish line and I keep getting the same "set_perm failed" …..I tried twrp hima 2.8.6.4 …still the same problem. I'm ready to give up. Please help me
Click to expand...
Click to collapse
What exactly is "the finish line"? Like @bigp951 said, we need more details. Please list everything you've done to this point and exactly what you're doing that returns that error.
I'm no expert but the process i used was.
- Get phone, Unlock bootloader via htcdev, (hadnt realise the sunshine apk does both unlocking bootloader and s-off at the time >< doh!), then s-off using sunshine, flash custom recovery via fastboot, flash superSU and install superSU apk for root, flash 1.40.401.x firmware with fastboot, flash viper rom (i had to do this twice as the first time an error came up which was helpfully listed in the troubleshooting section of the dev's post for viper, boom, it was all done. Backed up for safety
hope that helps you get to the source of the error.
when you say you flashed supersu and then installed supersu apk, what does that mean? I ask because when you flash the beta-superSu it installs the apk for you. But then again you had to be rooted to get s-off (someone correct me if I am wrong). Also, did you check the md5 before you tried to flash? Did you file a ticket with team viper? What was the error that showed up on the first failed attempt? Did you post on the viperonem9 thread and ask them for help? what is your cid and mid? supercid may help... and what is the current state of the phone? Is it still working?? Can you go into recovery? Still lots of questions.
If you want a clean slate to start over with find the CORRECT RUU and run it. Then you will be stock all over again (disclaimer--Find the RUU thread and follow instructions completely).
Obviously I am no expert either. I just run through the troubleshooting list when problems arise. But I try to help or point you in the direction of someone who can.
EDIT- there is also a newer official version of twrp for the m9. As @jollywhitefoot asked, you did not state what the finish line is nor what you were doing to return the error. If you installed the rom and made a backup than it sounds like the phone was working...
bigp951 said:
when you say you flashed supersu and then installed supersu apk, what does that mean? I ask because when you flash the beta-superSu it installs the apk for you. But then again you had to be rooted to get s-off (someone correct me if I am wrong). Also, did you check the md5 before you tried to flash? Did you file a ticket with team viper? What was the error that showed up on the first failed attempt? Did you post on the viperonem9 thread and ask them for help? what is your cid and mid? supercid may help... and what is the current state of the phone? Is it still working?? Can you go into recovery? Still lots of questions.
If you want a clean slate to start over with find the CORRECT RUU and run it. Then you will be stock all over again (disclaimer--Find the RUU thread and follow instructions completely).
Obviously I am no expert either. I just run through the troubleshooting list when problems arise. But I try to help or point you in the direction of someone who can.
EDIT- there is also a newer official version of twrp for the m9. As @jollywhitefoot asked, you did not state what the finish line is nor what you were doing to return the error. If you installed the rom and made a backup than it sounds like the phone was working...
Click to expand...
Click to collapse
Seems like this was a waste of time drive by. For someone "screaming for help" you would think they would reply when someone tries to help them.
maybe he's asleep...lol
jollywhitefoot said:
Seems like this was a waste of time drive by. For someone "screaming for help" you would think they would reply when someone tries to help them.
Click to expand...
Click to collapse
yeah, I know what you mean they ask a question and disappear for 2 days LOL
or he's thrown the phone under a bus and hates us all!!!! >< either way, there is a lot of helpful tips and tricks to be found in these forums. I think as mentioned above a good idea may be to try to return fully to stock and start again.... carefully following each step to the letter.
tomorio said:
or he's thrown the phone under a bus and hates us all!!!!
Click to expand...
Click to collapse
Is that an "uh-oh" moment? lol gotta love that uh-oh protection
bigp951 said:
Is that an "uh-oh" moment? lol gotta love that uh-oh protection
Click to expand...
Click to collapse
RIP OP