Device(s): Asus EeePad Transformer - Samsung Galaxy Mini - SE Xperia Arc - SE Xperia Play - Samsung Galaxy SII
Carrier: Not Provided
Thanks: 59
Thanked 1,294 Times in 490 Posts
Desire: All about Rooting - Updated 11 Nov 2011
All useful threads will be added to this global sticky, if you feel a thread is worth of inclusion then please pm me with the details and I'll look it over. Good luck with your fantastic and sexy phone all!
Shipped-ROMs is definitely better than that XDA thread for RUUs. Not only has the XDA list not been updated for more than a year, but I think the CDMA RUUs are for the wrong phone! Shipped-ROMs use HTC codenames, so the Desire CDMA is Bravo_C rather than Desire (which was the codename for the Droid Eris).
Just comparing this to the new sticky, and maybe some of the tools and utilities links are worth preserving (though like you I'm not sure about ROM Toolbox)? Apart from SetCPU, Ti and Root Explorer would be the first 2 root apps that come to mind, so I don't see the harm in linking those - we've recommended them often enough
Anything else I'd add? QSI isn't really a root app, but it's one we've recommended often enough when trying to diagnose problems that maybe it's worth a link? I've had a browse through my own app drawer and don't see so much else.
Did you reckon Scary Alien's "what is root" was too, well, scary?
Do you mean the "what does rooting mean?" Thread? If so thought it was just repeating what was in the rooting faq.
Don't want duplicate info so if you want both, feel free to strip the rooting faq.
I'm just a bit concerned its a bit of a mess right now so I'm having to point people to my signature rather than the sticky until its sorted. It's not ideal so whatever it takes to get it right and not have two guides and general info sections....
Awesome job, much neater, well done,
Is it also worth adding a troubleshooting section?
Ie, things to try if something isn't working? Like linking to terminal emulator, gps test?
Probably not but just wondering?
I've been trying to educate myself about the "standard sticky", and as I currently grok it (sorry, it's late!) I think that a troubleshooting guide added to the guides section would be fine, but an extra section in the sticky would be more controvertial.
Dan, I'm guessing the main motivation for your proposal in post 8 vs post 4 is flattening the structure and removing subsections whose names match the first 2 sections? I think that's completely cool, as well as much neater.
Please, anyone else with ideas do chip in. The purpose of the sticky is to serve the needs of the forum, so we need your thoughts.
Last edited by Hadron; March 3rd, 2012 at 07:25 PM.
The SDK download is a particularly visible difference. I guess it's a trade-off between visibility and duplication. ADB should be obvious from the title "[FAQ] ADB and Fastboot", so that one seems a clearer-cut example of something that can be tidied up.
Google apps is the odd one to me - very necessary for just one ROM, but it's a very widely known ROM. I think that I regard that as an oddity of CM rather than something people need generally, so not so important to include in the sticky (unless we feel that there's a chance that people who flash CM without noticing that it doesn't include gapps would go here without being directed - long shot in my opinion! )
Device(s): HTC One X+
Desire (Retired) Rooted S-Off Custom hboot
Carrier: O2
Thanks: 93
Thanked 181 Times in 158 Posts
Quote:
Originally Posted by shauny13
Hadron, a troubleshooting guide would be an excellent addition, good idea.
I would suggest that a troubleshooting guide should include, or link to, a guide to how to apply a RUU through fastboot including instructions to apply the downgrade hboot if a custom hboot had been applied.
When I had to return my phone for repair (wouldn't boot) I had no idea
Device(s): HTC Desire (depreciated)
Blue Galaxy s3 (international)
Carrier: Not Provided
Thanks: 114
Thanked 1,016 Times in 838 Posts
i like that the revised one looks less intense
its hard to give input into whether or not these changes are sufficient as im not really a user of guides anymore and wouldnt know what it would be like to first come across this guides.
smaller is definitely better as long as it serves the same purpose as the original. in this instance i think it does.
basically i cant see any reason for it not to be the revised version
The Following 2 Users Say Thank You to Rastaman-FB For This Useful Post:
We could link to bortaks troubleshooting guide on xda. Senseless doing all the work again?
I don't think I have the time to do sb SUroot style one....
Although we could list all the scenarios and collaborate on Google docs or something
thats an excellent idea, its a good guide, then maybe add a useful app guide,
like i suggested for apps like gps test, terminal, titanium, sms backup, apn, backup, and any others people feel are a necessary app.
Hadron, could we get this added as is for now please? Then work on what else we want. I really want to start directing people to the sticky rather than my signature.
I left the MD5 verification link in because I figured that was only partially duplicating what we had elsewhere - the Toolbox has the Windows tools, but that link has Android tools and even a Mac solution in it as well. Otherwise it's as in post 8.
The Following User Says Thank You to Hadron For This Useful Post:
I left the MD5 verification link in because I figured that was only partially duplicating what we had elsewhere - the Toolbox has the Windows tools, but that link has Android tools and even a Mac solution in it as well. Otherwise it's as in post 8.
Awesome, thank you...
Edit.. looks very neat
Last edited by SUroot; March 5th, 2012 at 03:20 PM.
Your current hboot is newer, so the ruu won't run.
There are tricks for downgrading. Am on phone so can't easily dig up links, but a forum search for downgrader should bring something up. I expect it needs a goldcard (see the rooting faq, linked from the All Things Root Guide sticky post).
Why do you want to downgrade to something that old?
GSM is a technical standard. If the phone has a SIM card, it's GSM.
HTC have used the name "Desire" for a number of devices: Desire, Desire HD, Desire Z, Desire S, Desire C, Desire X (just announced), and I've probably missed one or two
Visit GSMarena.com and look at the list of HTC phones (from the sidebar). You should be able to recognise yours from the picture. But you should be able to tell from this description:
The Desire (this forum) has 2 physical buttons on the bottom-left (home and menu), back and search keys on a rocker switch on the bottom-right, and a little round optical trackpad in the middle. No physical slide-out keyboard (that's the Z). Oh, and on the HBOOT screen it will say "Bravo" at the top (Desire S is "Saga").
Last edited by Hadron; September 8th, 2012 at 03:59 PM.
However, i wish to go back to my 2.2 froyo Asia RUU, I try to follow teppiz, Alpharez methods, and even direct run the official RUU but it seems that my hboot stuck at between 0.93.0001(CM7 first version, 2.3.7 Gingerbread), 1.02.0001(2.3.3 Gingerbread), 6.93.0001(CM7 second version, 2.3.7 Gingerbread) and after flashing alpharez downgrade hboot file i get 6.93.9999
If you've actually flashed the alpharev downgrader have you tried your preferred RUU after that? That one's intended to let you overwrite it, and bypasses customer id (i.e. region/network) checks, so it may be that it'll work now.
Yes, it is a desire Bravo. Yeap, that is the one I tried. I followed Alpharev steps and installed the RUU too. Both methods doesn't work. I even go all the way to flash the 2.3 upgrade gingerbread rom, hoping I could downgrade from there but it still didn't work. I knew my hboot initially was 0.83, PVT1, the latest radio 5.17.... and S-ON.
hmm in SG, they only accept the official updates from OTA(telecom companies) which is 2.2.1 froyo. As this 2.3.3 update, I got it from the shipped rom website yea so Im not quite sure they accept it.
When I run it, it stuck at verifying signature page shown on my desktop. Thereafter it gives an error 140 bootloader.
You could have got it from HTCdev.com for all they know, but if they really are only going to accept the HTC Asia version we'll have to try that.
So what happened when you ran teppic's downgrader, and what software/hboot did you have when you tried that?
The reason I'm asking is this: the downgrader won't run the RUU you want, but it will let you flash a 0.93 hboot (so a later Froyo). So you could try running another WWE Froyo RUU (RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.0 0.32U_5.09.05.30_2_release_142828_signed.exe is an early Froyo, but I think will work for this). That will I believe leave you with a 0.93 hboot, but I think teppic's downgrader should work on that release (though you'll need a goldcard). And if you can get the downgrader to work you should, according to the thread, be back to hboot 0.83, and that means you ought to be able to run the RUU you want.
A bit convoluted, but the best I can come up with. I should add that I've never used the downgrader or made a goldcard myself, so this is all guesswork based on other people's experiences.
Haven't much time online today, so this will be brief.
I have had one idea that might work. It's very much at your own risk.
There is a way of extracting a PB99IMG.zip from an RUU - one thread in the ATR Guide sticky has this in the title, and the usb unbrick guide refers to it too. Once you have one of those, you can unzip it and it should contain a number of image files (boot, hboot, radio, recovery, system). These are what the ruu installs.
Question is, if you are S-Off (i.e. have a Alpharev or Revolutionary hboot) is there anything stopping you from fastboot flashing these images directly?
You would want Alpharev stock hboot, or maybe the downgrader (don't know what partitions that has - I'd have made it stock myself, but don't know for sure). The stock rom in the ruu won't fit in other hboots.
We use fastboot for updating radio or recovery, so know that's fine (fastboot flash recovery recovery.img for example). We don't use it for rom installation as ROMs aren't distributed as images, but I can't see why it wouldn't work there (fastboot flash system system.img), and boot can be updated that way. And we do this to update hboot. So while the ruu won't let you downgrade hboot, can you just fastboot flash the image? If the hboot itself or the fastboot command doesn't impose the version check it should work.
This is untried territory as far as I'm concerned, and a problem flashing radio or hboot is the end of the phone. So while I think this might work in principle, and as long as the images are intact should be safe, I'm not advocating it. It would be your call.
If you try this, leave hboot to last - when you flash that you will lose the ability to fastboot flash anything else! I would suggest booting the phone before that last step to check it works - as long as you are S-Off we can fix problems with ROM or recovery, but once you flash hboot the only option left if it isn't working is an RUU.
Anyway, not one to rush into, but if the trade in is worth enough to you and you can't run the ruu any other way this might work. It may let you update the ROM anyway!
One other thought before I go offline. Scotty85 knows htc hacking very well. You could ask him whether he sees a flaw in that plan if you were interested in trying?
Desire: All about Rooting - Updated 11 Nov 2011
