Ok guys might need a bit of help..
Not too familiar with this handset really but flashed my phones a million times without problems...till I set about the missus's phone yesterday.
Its a 3 UK branded desire..was HBoot 0.83
Went through the S-Off/root/Recovery/Hboot upgrade procedures...and all looked good.
Till I came to actually flashing ROMs.. and tried a couple. Just bootlooped on the AlphaRev screen for all.
So decided to drop back to stock through HBoot... the stock ROM flashes with apparently no errors reported, but again fails to boot. And AlphaRev HBoot doesn't get overwritten..although Recovery's gone.
Anyone know how to proceed?
First of all by reading the tutorials carefully before proceed, to avoid any trouble
Get the latest RUU for your Desire (3UK) and save it somewhere.
Before you flash it, download the HBOOT Downgrader from Alpharev.nl.
Flash the Downgrader first, then the RUU.
And what do you mean the recovery is gone? Are you still S-OFF? You can flash a recovery with the Android Flasher tool in the Development secton.
And What ROMs did you try that all failed you?
You probably forget one ot two steps when flashing.
Ain't no noob buddy so need to cut and paste the standard response guys!
Did all them things so that's why I'm asking..and yes despite being over flashed with the RUU s-off is still there. That's what I meant by the alphrev hboot not being overwritten.
However..the downgradues worth a try....
DJW6927 said:
Ain't no noob buddy so need to cut and paste the standard response guys!
Click to expand...
Click to collapse
And that's how being rude will cut the number of replies you get...
No rudeness intended..but RTFM is no help either under the circumstances.
I've been doing this for years since my tytn.
I really appreciate the help I really do..the downgrade suggestion ain't in the guide...and seems a good idea. Will try soon as I'm home.
Ha. It ain't going well... worse in fact.
Downgraded HBoot and flashed RUU...screen won't turn on. But RUU can still just talk to it. Flashing again. But still the same.
Vol down makes it vibrate now...but not much else!!
Edit: Hum...my first brick I think! Think the wife might be gettin an upgrade.
Edit again: Screen blank but the RUU program still sees the phone. Fails to revive it mind you. Only outward sign of life is a pulse vibrate on the power button being depressed after a battery pull. Anyone seen this?
Slcd brick?
Swyped from my CM7.1 Desire using XDA Premium App
timmaaa said:
Slcd brick?
Swyped from my CM7.1 Desire using XDA Premium App
Click to expand...
Click to collapse
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
I gotta go to work..in Holland..but I'll still be checking in here for any information. It may very well be bricked but I'm still interested from a technical aspect.
DJW6927 said:
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
I gotta go to work..in Holland..but I'll still be checking in here for any information. It may very well be bricked but I'm still interested from a technical aspect.
Click to expand...
Click to collapse
Which RUU did you flash? If your phone has a SLCD screen, it might be a possibility that you've flashed an AMOLED RUU to your SLCD. Thus you will get a SLCD brick which makes you unable to view anything on the screen but the phone is working normally. It's reversible by following a SLCD unbrick guide.
Sent from my HTC Original Desire using Tapatalk
DJW6927 said:
Elaborate my friend? The 0.83 bootloader might indicate it has a sLCD... but only might I understand. Is there a history of issues with SLCD screens?
Click to expand...
Click to collapse
This is all basic, well documented stuff you seem to be completely unaware of. Perhaps RTFM is exactly what's needed here.
Thankyou very much indeed to those who who pointed me in the direction of slcd. Now I know what to search on finding the information I need is straight forward. Really good stuff.
Thanks very much too to those who provided the ex-wife service too. Unfortunately I always know where to get advice like that
Related
I unrooted to send my phone back to HTC for a warranty repair. They've sent it back and now my HBOOT is 0.83.0001 - I'm pretty sure it wasn't before I sent it to them...
Is there a root method that works for this version of HBOOT?
If not, what other options do I have?
Lol ? Do you have the new ROM so ?
I wondered if it would, but no, still 2.1-update1
I'm gonna be disappointed if I can't root it for a while now, but if the Froyo OTA does happen this weekend it will be some consolation...
I will add also that at this time, there is no way to root the Desire with the HBOOT 0.83.0001 :/
i had a bad feeling that would be the case... oh well, at least I'm free of the iphone I was stuck using while they were repairing it... those things seriously suck
Does the unrevoked3 method not work? I thought that could root anything!
I couldn't find anything specific to HBOOT versions on http://unrevoked.com/recovery/, but I'm a little hesitant to try it without knowing for sure...
I did rooted two desires with hboot 0.82 (branded for polish provider (ERA) using unrevoked3 without gold card.
I would say, go for it and try, nothing to loose
thanks - I took the plunge with unrevoked3 and had no issues... worked fine now running LeeDroid, it's all good
linshius said:
I would say, go for it and try, nothing to loose
Click to expand...
Click to collapse
Except for a possibility of bricking your phone??
Out of interest, OP, does your replacement phone have an SLCD panel? Or did they repair your actual unit?
bedeabc said:
Except for a possibility of bricking your phone??
Out of interest, OP, does your replacement phone have an SLCD panel? Or did they repair your actual unit?
Click to expand...
Click to collapse
i got over that fear a long time ago... i hope it never happens to me!
I was secretly hoping they would replace the unit, but no they sent it back repaired... it was turning off for no reason when light pressure applied to the back cover.
So no SLCD screen for me
bedeabc said:
Except for a possibility of bricking your phone??
Click to expand...
Click to collapse
You right, don`t try it on ORANGE branded Desire , don`t think u can brick trying to root, if unrevoked is uncompatybile it just won`t work.
Correct me if i`m wrong pls.
linshius said:
You right, don`t try it on ORANGE branded Desire ,
Click to expand...
Click to collapse
Forgive me, why is this?
Dunno why people worry so much about bricking - they're all under warranty for a while yet, so just send it back.
Yes, I know in theory it voids it, but are they really going to turn up to court to try and prove it over a £500 phone? It'd cost em more just to have the meeting to arrange it.
hermand said:
Dunno why people worry so much about bricking - they're all under warranty for a while yet, so just send it back.
Yes, I know in theory it voids it, but are they really going to turn up to court to try and prove it over a £500 phone? It'd cost em more just to have the meeting to arrange it.
Click to expand...
Click to collapse
It could be argued that it's that sort of dishonesty that makes HTC slightly apprehensive about third-party ROMs and mods, and why they make some attempt to prevent you doing it.
Hi.
I've same problem. My device was overheating and i unroot it and sent in for repair. Today i got it back with new mobo and HBOOT v. 0.83.0001 :S I hope that i can root this thing using unrevoked.
Cheers, X.
streetdaddy said:
thanks - I took the plunge with unrevoked3 and had no issues... worked fine now running LeeDroid, it's all good
Click to expand...
Click to collapse
can you PM how did you do it?
kmetek said:
can you PM how did you do it?
Click to expand...
Click to collapse
can you actually get it posted with instructsion, becuase unrevoked does the procedure (using linux version as running ubuntu) and it says it will leave the phone in recovery mode. all i get left with is a black screen. clockworks recovery is not to be seen. infact i think my recovery partition may not have been included as when ever i boot into it its a black screen.
there are a growing number of people who are stuck on 0.83 who would like to know.
Yeah I get the same. Root worked but no recovery!
SavageCore said:
Yeah I get the same. Root worked but no recovery!
Click to expand...
Click to collapse
Does that mean that the phone is still functioning? Nothing when booting into recovery but loads fine in normal boot, plus you have root?
I just got the new Telus Desire and it has HBOOT 0.83.0001.
Hi,
Got my desire yesterday and OTA upgraded to 2.2. Now have a hboot of 0.92 - not sure what is was before upgrade. I didnt realise that this might balls up my chances of getting root.
Looked around these parts and think that it's probably impossible to do. Unless anyone knows different am I just playing a waiting game?
Thanks.
debully.
U can downgrade hboot to 0.82
Sent from my HTC Desire using XDA App
answering my own post:
this helps...
http://forum.xda-developers.com/showpost.php?p=7515614&postcount=9
oh bollo**s - now I have a black screen from following these instructions. Presumably because I have a SLCD screen and downgraded to .80? Now trying to find out how to fix this - please reply if I am wasting my time...
http://forum.xda-developers.com/showthread.php?t=745903
FROYO root sorted folks
http://forum.xda-developers.com/showthread.php?t=748498
could this help you?
bob dylan said:
http://forum.xda-developers.com/showthread.php?t=745903
FROYO root sorted folks
Click to expand...
Click to collapse
for slcd devices ota froyo? am I missing something?
currently going thro:
http://forum.xda-developers.com/showthread.php?t=745903&page=2
RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32U_4.08.00.09_release_137222_signed.exe
anyone have a mirror for this which is not shippedroms?
debully said:
for slcd devices ota froyo? am I missing something?
currently going thro:
http://forum.xda-developers.com/showthread.php?t=745903&page=2
Click to expand...
Click to collapse
""After you've done the steps above you will have the following:
Blank and wiped device
Firmware: 2.1-update1 UNROOTED!
HBOOT: 0.80
Basband(Radio): 32.36.00.28U_4.06.00.02_2
Kernel: [email protected]#1
Build: 1.21.405.2 CL174215 release-keys
With that you can root and flash anything you want""
i had the OTA 2.2 Froyo with hboot of 0.92 and used that guide to downgrade my hboot so i could root and then upgrade to a Froyo Rom that doesnt increase th hboot to 0.92.
its really easy tbh
haha! easy for you! I'm a retard!
EDIT - actually, you dont have an SLCD device do you? Otherwise downgrading to .80 would've given you the blank screen...not so retarded after all.
debully said:
haha! easy for you! I'm a retard!
EDIT - actually, you dont have an SLCD device do you? Otherwise downgrading to .80 would've given you the blank screen...not so retarded after all.
Click to expand...
Click to collapse
well you didnt state that in OP did you, this is the thread you need:
http://forum.xda-developers.com/showthread.php?p=7602850#post7602850
Sorry for the confusion, on a steep learning curve here after 6 years of WM. Thanks for the link Bob, wish I'd found that in the first place.
Hopefullly my phone is flashing now, kinda hard to tell with just a blank screen, but everyone says leave for 20 mins....fingers crossed!
debully said:
Sorry for the confusion, on a steep learning curve here after 6 years of WM. Thanks for the link Bob, wish I'd found that in the first place.
Hopefullly my phone is flashing now, kinda hard to tell with just a blank screen, but everyone says leave for 20 mins....fingers crossed!
Click to expand...
Click to collapse
no worries, good luck, those instructions sound crazy hard to me!
got my screen back - took hours. Take heed if your newbish, on an SLCD with .92 - getting root is a minefield!
debully said:
got my screen back - took hours. Take heed if your newbish, on an SLCD with .92 - getting root is a minefield!
Click to expand...
Click to collapse
But you did it eventually?
Sent from my HTC Desire using XDA App
http://forum.xda-developers.com/showthread.php?t=749915
is the only way I can see of getting root on my phone. As you say this is crazy hard!
I don't like the idea of all that blind working in order to change usb mode. I'll wait until someone makes it reasonably easy. Cop out I know but last night was scary!
Sent from my HTC Desire using XDA App
Innit I would not be trying that either!
Sent from my HTC Desire using XDA App
I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.
ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery
ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery
Anyone? Bueller?
cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.
This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.
Hi folks, I have just joined as a friend of mines told me XDA was the place to look for help in sorting out my HTC Desire.
I will do some reading over the weekend and hopefully sort the problem out myself and not need to look like a complete tosser. There is obviously millions of members and endless amounts of topics to chose from.
A brief description of my problem : I installed the HTC Gingerbread 2.33 RUU a few months back and ran into issues with the storage, which I believe the update warned of. Anyway, that RUU updated the handset no problem, but me being me I decided I wanted to revert to a stock rom so downloaded an older version which failed to install on the phone.
I used Revolutionary method to gain S-Off and created a NAND back up without any problems then I tried to run the old RUU and hit a brick wall so to speak. I am now stuck on the TMobile UK loading screen and although I can boot into HBOOT menu I cant use recovery to gain access to the back up or anything else.
My PC is now wont find my Desire as a phone but just a Android Device.
As I say I will do some searching and hopefully find my way through the maze of information.
If I need anymore help I will give full details of ROM Version , HBOOT and exactly how I got my phone into such a sorry state.
Thanks in advance to anyone who may be able to help me.
Don't Worry.. got you problem..
First of all install latest HTC sync and android UBD drivers..
Then Give me detail of device.. We'll proceed if still faces the problem
DONT FORGET TO HIT THANKS BUTTON AT BOTTOM RIGHT OF THE POST IF THIS HELPS YOU
Someone desperately wants to rise his thanks bar...
Lol
Swyped from my CM7.1 Desire using XDA Premium App
Terepin said:
Someone desperately wants to rise his thanks bar...
Click to expand...
Click to collapse
I hate when someone begs for thanks.
SwiftKeyed from my HTC Desire using XDA App.
I agree, but hey, not everyone can be so intelligent as we two.
Yes Terepin, your mad english skills are a testimony to your insanely high IQ level.
Ned_Stevens said:
Hi folks, I have just joined as a friend of mines told me XDA was the place to look for help in sorting out my HTC Desire.
I will do some reading over the weekend and hopefully sort the problem out myself and not need to look like a complete tosser. There is obviously millions of members and endless amounts of topics to chose from.
A brief description of my problem : I installed the HTC Gingerbread 2.33 RUU a few months back and ran into issues with the storage, which I believe the update warned of. Anyway, that RUU updated the handset no problem, but me being me I decided I wanted to revert to a stock rom so downloaded an older version which failed to install on the phone.
I used Revolutionary method to gain S-Off and created a NAND back up without any problems then I tried to run the old RUU and hit a brick wall so to speak. I am now stuck on the TMobile UK loading screen and although I can boot into HBOOT menu I cant use recovery to gain access to the back up or anything else.
My PC is now wont find my Desire as a phone but just a Android Device.
As I say I will do some searching and hopefully find my way through the maze of information.
If I need anymore help I will give full details of ROM Version , HBOOT and exactly how I got my phone into such a sorry state.
Thanks in advance to anyone who may be able to help me.
Click to expand...
Click to collapse
Have you just tried flashing the 2.3 one again? it should fix it for you..
sachin.02 said:
DONT FORGET TO HIT THANKS BUTTON AT BOTTOM RIGHT OF THE POST IF THIS HELPS YOU
Click to expand...
Click to collapse
lol you're sad
TVTV said:
Yes Terepin, your mad english skills are a testimony to your insanely high IQ level.
Click to expand...
Click to collapse
How can you know how high is my IQ when it is of the chart?
noob-proof guide is the best...
Hi, I'm a complete noob to modifying smartphones and my knowledge is very limited.
I wish to install a custom rom to my HTC Desire.
One of the reasons is that the device is overheating and falling into a reboot loop and I beleive that to be a software glitch and hope this would help (not sure, but could be).
Anyway, I've found a really nice tutorial made by linkslovesandroid, http://forum.xda-developers.com/showthread.php?t=1016084 and have come to a stop at the very beginning since it says:
"**This method only works for users with hboot 0.93 and lower. Sorry 1.06 users, but until unrevoked updates, your stuck on stock htc***"
I've looked up my hboot and it's 6.93.
I presume that it will not work then.
So...can I modify my hboot, if yes how, is there another workaround or another tutorial (understandable for my level of knowledge which is close to 0) I may follow?
Please help!
if you will check hboot(power and vol -)/fastboot(power+back) screen it will say S-OFF
so you don't need to do anything just access recovery and flash any rom you like just keep in mind you have to adhere any developer requirements
RagnarokCosmos said:
One of the reasons is that the device is overheating and falling into a reboot loop and I beleive that to be a software glitch and hope this would help (not sure, but could be).
Click to expand...
Click to collapse
The reason the device is overheating and rebooting is due to a very well known hardware fault with the Bravo. Changing ROMs won't help.
Thanks to the both of you.
Indeed it is S-off..
I've researched the matter further and I fear it is as you say, a hardware error, there are numerous reports about faulty motherboards if that is what you mean.
I got the device 2nd hand so no warranty or anything, hope it's not too expensive to fix it, although if it is a motherboard issue, I'm afraid of the price.
Does anyone know aprox. how much does it cost to fix this?
No idea. Ebay is your best bet.
RagnarokCosmos said:
"**This method only works for users with hboot 0.93 and lower. Sorry 1.06 users, but until unrevoked updates, your stuck on stock htc***"
I've looked up my hboot and it's 6.93.
I presume that it will not work then.
So...can I modify my hboot, if yes how, is there another workaround or another tutorial (understandable for my level of knowledge which is close to 0) I may follow?
Please help!
Click to expand...
Click to collapse
My desire has same hboot. I made S-OFF with revolutionary method (check alpharev webpage).
Once you are S-OFF you can change your hboot just by downloading the hboot image from alpharev. Rename zip to PB99IMG.zip and place it at your sd-card. Reboot on bootloader, zip will be detected and you will be asked if you want to apple update, answer yes. And that's all, enjoy your new hboot.