[Q] Rooting Desire HD - Desire HD Q&A, Help & Troubleshooting

Good evening.
I'm new to the forum, so I hope it's ok that I ask a question as the first thing?
(Oh and bear over with my english as it is not my main language)
I'm quite sure you guys get this question quite alot, but it is a bit hard for me to collect the necessary information needed for me to start working on my "problem".
My plan is too root my newly aqquired HTC Desire HD.
As an added information: I already temporary rooted it using the VISIONary+ application and that seems to work as it should. I can get root rights and everything. So far so good - I havn't tried using the permanent root option that this program allows as I want to know exactly what I am doing before doing anything (I heard all the scary stories of bricking and stuff)
So let's start out with the questions:
- How do I check what firmware, kernel, ect ect ect I've got so that I can get the necessary information?
- How do I know if it is branded or not? (Not sure what that even means... I live in Denmark and bought it at the shop, and it is not simlocked. Phone company is Telmore)
- Where the hell should I start?
I looked up this guide: wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide#Flashing_Radio
Would that help me?
Also looked at this: androidpolice.com/2010/04/16/complete-guide-how-to-fully-back-up-and-restore-your-android-phone-using-nandroid-backup-and-clockworkmod-rom-manager/
Could I just perma root with VISIONary+ without worrying and then using rom manager to get the recovery image on and stuff or is it better doing a manual root somehow?
Oh and by the way, I already got adb access to my phone through the pc!
(And please tell me if this is the wrong section of the forum.)
Thanks in advance!

I guess the first question is, did you purchase the telus desire hd in canada per chance?

The firmware /kernel info can be found in the about phone section of the settings menu.
As for rooting I personally favour the manual root specified by the good folks over at CyanogenMod here if you find that a bit daunting there are some automated one click tools over in the Development forums here on XDA, although most require that you have access to a computer running windows.

equlizer said:
I guess the first question is, did you purchase the telus desire hd in canada per chance?
Click to expand...
Click to collapse
Nope. It was bought in denmark.
Dunno if it's a telus model or anything (As I have no idea what a telus is lol)
Some Information about my device: (Btw I'm trying to translate from danish. So ask if something sounds wrong)
- Android Version
2.2
- Basebandversion
12.28b.60.140eU_26.03.02.26_M
- Kernelsystem
2.6.32.21-gf3f553d
[email protected] #1
Thu Oct 28 13:24:11 CST 2010
- VersionNumber
1.32.405.6 CL278359 release-keys
- SoftwareNumber
1.32.405.6
- Browser version
WebKit3.1
As far as I can see my VersionNumber (I guess that is my firmware??) matches the one that the cyanogenmod guide (As In I dont need to downgrade yay!):
wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
Asks for.
Is there anything else I should check for before I begin, or would that be the guide I should follow?

Plus I forgot to say:
I'm pretty good with computers in general. So I don't care using an "advance" manual method as long as it is descriped well so I don't end up saying "Wait what? Where the hell should I go now?"
So no need to doing some noobish way (Not saying One click methods are noobish) I just need to know what to do and how it should be done.

ok for starters, dont worry about bricking, it's impossible to brick your device trying to root, infact there are only 2 ways you can brick your device, and thats flashing a radio or hboot you have the 1.32 software version and that can be easly permrooted using visionary, after you root, you may want to s-off aswell

AndroHero said:
ok for starters, dont worry about bricking, it's impossible to brick your device trying to root, infact there are only 2 ways you can brick your device, and thats flashing a radio or hboot you have the 1.32 software version and that can be easly permrooted using visionary, after you root, you may want to s-off aswell
Click to expand...
Click to collapse
First off, thanks for the quick help! *thumps up*
So I don't have to use the CyanogenMod guide? (would it be better if I did it that way?)
Or is it enough with a perm root with VISIONary?
Then after that I'm thinking of doing a backup (It's called Nandroid as far as I've read?)
Doing a perm root with VISIONary, followed up by flashing the recovery image using the one click option that ClockWork ROM manager allows.
Would I have to worry about doing that, or does my information say that my model should work perfectly fine with that?
I think it's quite important to say that I'm thinking of doing a Custom Rom later, but my first job is to get it rooted and backed up incase anything happens.
Oh and, how would I manage to do a s-off after I've got it rooted? Would that have to be done BEFORE doing the flashing of the recovery image and doing a backup?

you can use the Cyanogen method, thats just a manual way, i used visionary, and have had no problems at all, just click the permroot option and wait after you root, before you flash a custom recovery you need to s-off, this is because the nand chip has write protection, check out this thread http://forum.xda-developers.com/showthread.php?t=855403 jkoljo tool is awsome and although flashing a hboot is dangerous, no1 has bricked there device using his tool yet, thats how safe it is once you are s-off, you can download rom manager and flash a custom recovery

I can see that the tool is called "One click ENG s-off" as in ENGLISH.
Does it matter that my phone is bought in denmark and is in danish?? (Does the language matter at all? :O)

virtual-aidz said:
I can see that the tool is called "One click ENG s-off" as in ENGLISH.
Does it matter that my phone is bought in denmark and is in danish?? (Does the language matter at all? :O)
Click to expand...
Click to collapse
the ENG means engineering, there are two types of s-off, engineering s-off and Radio s-off, the engineering one allows you to issue fasboot commands though and the radio one dosent, either one will security unlock your bootloader though

Ah I see
I just noticed in the s-off guide: "tick "I have Radio S-OFF" in the tool"
Why do I have to tick that? I don't have Radio S-OFF? :O
And right now I can't even test out what we are talking about *sadface* I just noticed a dead pixel right in the center of the screen, so before I start messing around, I'm gonna take it to the shop and see what they say (God I hate dead pixels)
I know it's a bit (well alot) besides the subject, but I was just crossing my fingers that you were a dead pixel specialist and could answer a simple question: Would a dead pixel on a 1 month old phone (I think the pixel is red, but it could be black as in completly dead) have any chance of spreading or something?
Cause I could live with a single dot.. but if it has a chance of spreading, I would really wanna get it fixed before it's too late (And sorry for the off-topic in my own thread xD)

Notice the big OR in the requirements part? As you are not using a custom ROM, and you do not have Radio S-OFF, you should not tick it.
Dead pixels do not spread, and there are apps in market to revive dead pixels, you should try one of them.

jkoljo said:
Notice the big OR in the requirements part? As you are not using a custom ROM, and you do not have Radio S-OFF, you should not tick it.
Dead pixels do not spread, and there are apps in market to revive dead pixels, you should try one of them.
Click to expand...
Click to collapse
Haha... My bad.
As I mentioned in my first post, my main language is not english. So I misunderstood what it said
I think I'm ready now.
Just need to talk with the shop before I void the warranty for good.
Thanks for the help guys, and I will return when I get it working (or **** it all up.. who knows)

By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to

Odd. There has been multiple cases where they did not fix phones that were just rooted.

jkoljo said:
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Click to expand...
Click to collapse
Oh and by the way. I see you're the creator of the s-off and radio s-off tools?
Is it true that you recommend Radio S-off (forum.xda-developers.com/showthread.php?t=857537)?
And how do I check if I meet all the requirements?

jkoljo said:
By the way, root, S-OFF and custom ROMs do not void warranty. It says nothing about software in the warranty terms, check it out yourself if you want to
Click to expand...
Click to collapse
actually it does............. "use of products, equipment, systems, utilities, services, parts supplies, accessories, applications, installations, repairs, external wiring or connectors not supplied or authorized by HTC" ........ custom bootloader, and software can come under the systems, applications and installations

Ah yay. I thought so
As far as I can see on the Radio S-Off (Again, is it recommended over s-off?)
System requirements:
Windows XP SP2 or higher
.NET Framework 4.0
HTC Sync (or ADB drivers)
Desire HD with stock kernel (or Apache14's 1.0.7 / 1.1.4 Sense)
It will not work on 1.72.405.3 or higher build, or new radio. Downgrade first!!
I got the 3 first ones covered.
But I'm not sure about the two last.
My Phone has HTC sense, but I dunno what version to be honest.
And I guess I got the last one covered too as I got the 1.32.405.6

You meet all the requirements
AndroHero said:
actually it does............. "use of products, equipment, systems, utilities, services, parts supplies, accessories, applications, installations, repairs, external wiring or connectors not supplied or authorized by HTC"
Click to expand...
Click to collapse
Please take a picture for me, that is not included in the warranty statement that came with my phone. I rang HTC about it, and they said that unless the hardware is modified, software does not matter. Also mike1986 sent his phone to be repaired with ENG S-OFF and everything, and nobody complained.

jkoljo said:
You meet all the requirements
Please take a picture for me, that is not included in the warranty statement that came with my phone. I rang HTC about it, and they said that unless the hardware is modified, software does not matter. Also mike1986 sent his phone to be repaired with ENG S-OFF and everything, and nobody complained.
Click to expand...
Click to collapse
How did you know I met the requirements with the HTC sense?
(I need to learn too)

Related

Quick rooting question

Now uh, go easy on me, my first time posting here.
I may seem like a total idiot here, but the amount of conflicting information I've seen is quite confusing. I've searched and searched and the more I read the less I seemed to be sure of.
My question:
Can I do the unrevoked method of rooting ('theunlockr.com - how to root htc desire unrevoked method' 20.9.10) [cant post links] on my specific device?
My handset information is
Bravo PVT3 SHIP S-OFF
HBOOT- 0.87.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.09.00.08
Android version: 2.2
Software number: 2.06.832.1
The 0.87 HBOOT seems rather rare on the forums, I don't know why. All I've read is that at one point the 0.87 version could not be rooted, but I don't know if that is still the case (this was information from April-July) and the unrevoked tutorial states that 'At this time, unrevoked3 works on all versions of the supported phones', which my phone would come under the CDMA Desire (BravoC) I'm pretty sure. Just would like some quick confirmation from you lot before I go and do something stupid.
Thanks!
it was mentioned that hboot version doesnt matter when using new unrevoked
If you've got S-OFF then you don't need to root do you? It should already be done...CDMA phones when rooted with unrEVOked get S-OFF
Sounds like you're already rooted, check to see if you've got Superuser Permissions in your program list
Nope, no superuser permissions, and the phones unused.
The fact that the phone supports WCDMA as well as GSM makes it the CDMA 'Bravo' model right?
Well if what you have written is indeed what it says in hboot, then you are s-off and it should be easy to flash or install super user to the phone
My phone supports WCDMA and GSM - it's not the same as CDMA...
Do you use a SIM card in your phone? If so, it's a GSM phone
Just double checked it, it definately says S-OFF, everything in the first post was 100% correct.
Strange, the phone is actually a Hong Kong model that I ordered, saving me quite a bit of money being in Australia. Seems a bit iffy that it was unlocked from the start, actually makes me think it's a used model, even though everything else looks and works flawlessly. Probably shouldn't complain, even though they've caused me a bit of confusion.
So these rooted ROMs that people are developing all contain the superuser permissions application, I can't seem to find that individual application for download though. Hmmm.
edit: found the application, installing.
Ah, so I have the GSM model.
When did you get the phone? The S-OFF 'hack' has only just come out so unless you're on an engineering Desire (which is highly unlikely) then someone cracked it before selling the phone...
If I were you, I'd follow this guide:
http://forum.xda-developers.com/showthread.php?t=768256
and go back to a stock WWE ROM and then root it using unrEVOked 3.14 and then you can flash whatever ROM you want...easier than faffing about with S-OFF and the like (you don't really need it unless you wanna change the initial splash screen or you're a developer)
I got the phone about a week ago.
Cheers for the advice.
EddyOS said:
When did you get the phone? The S-OFF 'hack' has only just come out so unless you're on an engineering Desire (which is highly unlikely) then someone cracked it before selling the phone...
Click to expand...
Click to collapse
Well the hboot version he is mentioning is not the same as the one patched by ieftm, so he might just have recieved a developer device? Sounds strange though.
And as eddyos is saying, you could just flash a ruu and go the traditional route, if you cant figure it out using the s-off hboot. It's pretty cool though.
edit: if it is an actual s-off device, wouldn't the flag for s-off be set and flashing a ruu would not help it? Just like unrevoked forever on evo?

[Q] A few questions before rooting

Hey guys, first time poster here and a bit of a newb to rooting, Android and smart-phones in general.
I've been hanging on these forums the past 3 months researching the rooting process for a Desire and all the relevant stuff that goes along with it. So please go easy on me. I've also read all the 'similar threads' suggested to me at post-time.
I'm almost ready to begin the process but there's a few bits of information that's got me pretty scared before I go ahead. I wasn't able to find much of a concrete answer/s to these questions, from Googling around.
Well without further ado.
What is the difference between GSM & CDMA and do I need to know which my phone is before proceeding?
If I DO need to know, how do I find this out?
My phone is branded (Orange splash-screen at boot) and locked to Orange network (Newly recieved contract phone).
I've heard that I may need a goldcard to proceed with the Unrevoked process due to the branding. Is this correct?
Another guide on the net (can provide link if necessary), mentions upgrading the radio on Orange phones can permanently break the wifi OR permanently simlock your phone.
Will I need to worry about this during the Unrevoked rooting process? And will this be avoidable after installing a custom rom. (If I get that far )
I read somewhere on these forums (I forgot where exactly), something about the newest Orange OTA update causing problems with the rooting process. Is this still the case or has Unrevoked been updated to avoid that now? Also, how can I check if I have that update?
I can provide all the information about my Hboot, radio and kernel versions etc, if you need it (I guess you will), but for some reason, I keep getting a spam warning as this is my first post. I can only assume the version numbers are being interpreted as IPs...
Well sorry for the wall of text, but I greatly appreciate any help I can get regarding these issues. I'm so scared of bricking my Desire and not being able to return it, if bricking does occur.
Yours a worried root newb!
1. We use GSM phones in the UK as we use SIM cards. CDMA phones don't use SIM cards and are locked/released to one network
2. You don't need a gold card to root, no. As there isn't an Orange RUU available to go back to stock for warranty you will need one to flash a non-Orange RUU. Best to make one before starting
3. This was the case a while back but I'd wait for confirmation before changing it
4. No as the radio isn't flashed during a ROM (unless stated in the ROM thread that it does)
5. Shouldn't be an issue, just get the latest version of unrEVOked from their website before starting
Great, that's most of my questions/concerns answered. Although the below answer has brought a new question to the front
EddyOS said:
2. You don't need a gold card to root, no. As there isn't an Orange RUU available to go back to stock for warranty you will need one to flash a non-Orange RUU. Best to make one before starting
Click to expand...
Click to collapse
Unfortunately my knowledge of RUU is almost non-existant, other than that it stands for Rom Upgrade Utility and is used to upgrade the software on my phone? Right?
And forgive me if I'm being dumb here but, if
EddyOS said:
there isn't an Orange RUU available to go back to stock for warranty
Click to expand...
Click to collapse
and yet I
EddyOS said:
will need one to flash a non-Orange RUU
Click to expand...
Click to collapse
then how can I do this? Or am I totally misunderstanding you?
Do I somehow use an application without root permission to perform a procedure similar to hdd ghosting?
Basically, if you wanted to return to stock for any reason you wouldn't be able to go back to the Orange ROM as the RUU doesn't exist so you'd have to go to a generic ROM. To flash any ROM other than the originally on the phone you need a gold card
It's the same for me, if (for some strange reason) I'd want to flash a branded ROM on my Desire I'd need a gold card. Thankfully, I have an unbranded handset so I can get the stock RUU and use it without a gold card
EddyOS said:
Basically, if you wanted to return to stock for any reason you wouldn't be able to go back to the Orange ROM as the RUU doesn't exist so you'd have to go to a generic ROM.
Click to expand...
Click to collapse
So basically if I were to screw it up, which I hopefully won't, I'm buggered as far as getting my phone fixed cos they'll see the Orange rom is no longer installed? Not too fussed about that, as I'm super-careful with my phone.
I guess my next issue would be, after rooting using Unrevoked, I'd need to gain S-OFF right? Which I understand is done via AlphaRev. Only issue there would be related to this
"Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files." If I'm reverting to a stock rom, while gaining S-OFF presumably there's a high chance that'd upgrade my radio - a potentially very bad thing.
THEN I go about choosing a rom to flash. Then Nandroid backup. Then flash the rom, hopefully love it and voila?
Also, what would you suggest as a good rom for someone like me just starting out with a fully rooted phone? I was thinking one of the official builds to lose all the crap, but then the above issue of the radio creeps up again...
I have been flashing ROM's since I got my phone rooted last year and I have never bothered to S-OFF. It's not a requirement.
I have tried a number of ROM's (it becomes a bit addictive!) there is not normally a need to flash a new radio, just leave it be. If you are worried about it and the ROM requires a new radio don't flash it. There are plenty to choose from.
As for recommendations, everyone has their own tastes and likes. That's the beauty of modding. Just flash a few ROM's and see which you like. I have tried most of them, stuck with MIUI for ages, but am now on Cyanogenmod 7 Nightly's.
There is nothing to really worry about. There is a remote chance of bricking your phone for a start, like 0.0000000001% chance. Only way of doing it is disconnecting during say an S-Off.
As for the Orange issue. I had a locked, Orange Desire with 2.2 on it (the first update) and when I rooted and S-Off'd I had no problems. I also have updated my radio to 5.14.05.17 and have no issues at all. To be honest, I found issues to do with signals and Wi-Fi are to do with the ROM you install and the kernel as well which can be frustrating but fun as well.
As for choosing a ROM, choose one, flash it then see what it's like. It's purely down to what you like most about each ROM. I've been through so many ROMs in the past few months but now I am sort of staying with 1 ROM. I will say that when I installed a custom ROM, I had to pay to unlock my sim because it was being gay and Orange wanted £20 of my hard earned cash to unlock it and send it off. So be prepared.
thetasigma3 said:
So basically if I were to screw it up, which I hopefully won't, I'm buggered as far as getting my phone fixed cos they'll see the Orange rom is no longer installed? Not too fussed about that, as I'm super-careful with my phone.
I guess my next issue would be, after rooting using Unrevoked, I'd need to gain S-OFF right? Which I understand is done via AlphaRev. Only issue there would be related to this
"Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files." If I'm reverting to a stock rom, while gaining S-OFF presumably there's a high chance that'd upgrade my radio - a potentially very bad thing.
THEN I go about choosing a rom to flash. Then Nandroid backup. Then flash the rom, hopefully love it and voila?
Also, what would you suggest as a good rom for someone like me just starting out with a fully rooted phone? I was thinking one of the official builds to lose all the crap, but then the above issue of the radio creeps up again...
Click to expand...
Click to collapse
Don't bother about S-OFF at the moment, you don't need it. Just get rooted and then look into custom ROMs for now
Ok I've taken a tiny step further forward. I'm at the point of making a goldcard but one thing concerns me... http://forum.xda-developers.com/showpost.php?p=6710085&postcount=3 According to that it won't work with the 2.2 OTA update from HTC.
I know, I have 2.2 installed but this was already on the phone when I received it, so I've no idea if this was an OTA or not... So I guess I need a different method to make a goldcard now?
Use this:
http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
Probably need to register to get the file, though
Hmmm tried using that tool and no joy... Get my img file downloaded, but then the tool refuses to recognise my phone, despite doing the appropriate change over to 'disk drive'. I tried re-plugging the un-mounting and re-plugging the usb cable. Still no joy.
I'm beginning to lose hope here... That tool won't work and the tutorial here says it's incompatible with 2.2...
**edit**
Been Googling around a fair bit and I can't find any information at all on downgrading a branded 2.2. Only information on people with branded handsets wanting to update to 2.2.
After a bit more searching, I found someone else with the exact same issue as me. http://forum.xda-developers.com/showpost.php?p=10370443&postcount=977
Only one difference though. He doesn't mention if he managed to flash a custom rom after his root. I'm guessing he probably wouldn't have been able to going by your post:
EddyOS said:
To flash any ROM other than the originally on the phone you need a gold card
Click to expand...
Click to collapse
A gold card is only needed to flash a STOCK ROM different from your original - it's not needed to flash a custom ROM. The gold card isn't even needed to root. It's just handy to have in your case as you'd need it to go back to stock due to the lack of an Orange RUU
I'm out of ideas I'm afraid, never had to deal with a gold card as I'm unbranded
Use this:
http://android.modaco.com/content/so...-goldcardtool/
Probably need to register to get the file, though
Click to expand...
Click to collapse
Does that work a lot better then?
I used the method posted by thetasigma3 and I can't get OTA 2.29.405.5 but I can get 2.29.405.2. To get round the problem I installed the 2.29.405.5 RUU and rooted
Anyone who's debranded will need to use the RUU as the OTA won't go through
GoogleJelly said:
I will say that when I installed a custom ROM, I had to pay to unlock my sim because it was being gay and Orange wanted £20 of my hard earned cash to unlock it and send it off. So be prepared.
Click to expand...
Click to collapse
Call me crazy, but why the heck would flashing a custom rom require you to unlock and send off? Presumably the sending off thing would've been for Orange to perform the unlock procedure?
Anyway, back to my main issue, I know I've probably tread the same ground a few times now, but I really don't wanna end up bricking, cos I overlooked a tiny element, or something.
Could someone confirm I have these points all correct please?
Goldcard NOT needed for rooting.
Goldcard NOT needed if/when I flash a custom rom.
Goldcard needed if I wanted to go back to a STOCK rom.
Only reason to flash a STOCK rom is if I need to send back to Orange for repairs etc.
Oh and thanks for the clarification on your earlier post EddyOS. About goldcards not being needed for custom roms as opposed to stock etc.
Think I'm ready to go ahead with the process now, but if I go ahead and something goes wrong, what's my safety net, so to speak? Presumably my battery would die on me long before I get a response here
What you have there is correct (point 2-5)
The unlocking issue was down to some radios causing Orange handsets to become SIM locked. If you're using an Orange SIM this isn't an issue but others who got an Orange handset but use a different SIM card found they wouldn't work.
This was earlier in the Desire's life and I don't think it's applicable now
Try using "GoldCard Helper" app from Android Market, in case you want to try and make a goldcard (as the other methods did not work for you).
As mentioned as EddyOS, all your points from 2 - 5 are correct.
Ok finally got the guts together to go ahead and run unRevoked. (Already had done the driver steps etc).
I've checked with an app from the Android Market, called 'Root Check' to verify root access. That's saying I do have it and it also asked for Root permissions on start-up, which it never did before root. So I assume that's a good sign. I also checked for the 'Superuser Permissions' app in my apps menu. Found it was present and clicked it. Started without any problems. So I guess that's another good sign.
So I guess my next set of questions are reasonable simple.
Does this seem like my phone is now 100% rooted? I think it is, but I could be wrong.
Do I need to install Busybox? Root Checker seems to like seeing it there.
Does it matter if I use Titanium Backup Pro or free? I'm guessing it won't but I'd like to be certain.
If I backup my current Orange rom with Titanium Backup will I be able to go back to that without a goldcard? My guess is no. I didn't make or use one for the root process.
1. Yes
2. For Titanium Backup, yes
3. No
4. You don't backup the ROM with TB, you boot into Recovery and do it there
kvphani said:
Try using "GoldCard Helper" app from Android Market, in case you want to try and make a goldcard (as the other methods did not work for you).
As mentioned as EddyOS, all your points from 2 - 5 are correct.
Click to expand...
Click to collapse
Hey man, I downloaded that app and found a fairly easy looking guide on the Unlockr http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ . Just wanted to check, if I use that app plus this guide. I skip steps 1-6 right?
Ok gone ahead and done that now. Just having some trouble finding instructions on backing up my Orange rom.
Oh and now that the forum won't grumble at my phone info, here it is. Hopefully that'll shed some more light on my situation, if I need further help.
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.10.05.30
Aug 10 2010, 17:52:18
Android Version
2.2
Baseband Version
32.48.00.32U_5.10.05.30
Kernel Version
2.6.32.15-g29e526b
[email protected] #1
Build Number
2.17.61.3 CL274424 release-keys
Softare Number
2.17.61.3
Browser Version
WebKit 3.1
Model Number
A8181

[Q] Some information needed concerning rooting/flashing

Hey there guys, This is my first post on the forums, i have been reading some stuff unregistered and today i decided hey lets register.
so, what i wanted to ask you guys is the following.
I have been interested in whether i should root my HTC Desire HD so i could flash a custom ROM, i found many reasons why i should do this as most reasons appeal to my Desire of the phone( LOL, My Desire of My Desire HD ).
But i cant help noticing after reading quite alot of posts on different forums/sites that most people tend not to think befor they do this.
So basically, my question really is; What do i need to do should there be a reason in the near future for me to have the original Vodafone software on the phone?
Although i have read some stuff about how-to go back to your stocks but i couldnt find anything related specifically to the Desire HD, i read that you will need a RUU, which will be english, and i was also wondering will this work for a Vodafone Branded device from the Netherlands? Could any one tell me what i should do about this aswell?
Here is some information i have noted just incase it might be needed;
KERNEL VERSION 2.6.32.2
BUILD NUMBER 1.75.161.2 CL301245 release-keys
SOFTWARE NUMBER 1.75.161.2
I hope you guys understand that i take this quite serious and therefor i wanted to ask you rather than do and think afterwards!
P.S. if you need more information, let me know!
Thanks in advance!
/ENZ-
To root and S-OFF properly I recommend to follow only the guides in XDA-Developers. I have made a few myself, you can start with my downgrade guide.
My radio S-OFF tool's thread contains information on how to go back to stock. You will need a RUU, follow this link to get it. The Vodafone UK RUU should be just fine.
The only reason why you would want to go to stock is a warranty case. It is not completely necessary though, as there is nothing about software mods in warranty terms. In simple english, rooting and custom ROMs do not void your warranty. It is still best to make your device stock if you intend to return it.
jkoljo said:
To root and S-OFF properly I recommend to follow only the guides in XDA-Developers. I have made a few myself, you can start with my downgrade guide.
My radio S-OFF tool's thread contains information on how to go back to stock. You will need a RUU, follow "******* to get it. The Vodafone UK RUU should be just fine.
The only reason why you would want to go to stock is a warranty case. It is not completely necessary though, as there is nothing about software mods in warranty terms. In simple english, rooting and custom ROMs do not void your warranty. It is still best to make your device stock if you intend to return it.
Click to expand...
Click to collapse
Thanks for the reply mate, yes ofcourse the only reason i could think of why i should go back to stock is indeed for warranty issues, but still its nice to know how-to even though it might not be needed, i'd rather be prepared for it.
So basically rooting is the first phase, but i read on some guides here at XDA that i should delete HTC Sync and HTC Driver, i did uninstall sync but i cant find HTC driver, how can i uninstall HTC driver?
P.S. why advice the UK one above the WWE? does it matter whether im from The Netherlands in this case?
/ENZ-
Because Vodaphone might think something is wrong if they find a WWE ROM from a phone with their own branding.
Ok.. What exactly have you been reading?? You are definitely not supposed to delete the driver and sync, you have to have those. I have to make a correction to my last reply, you should only read the guides in Desire HD section, I thought that it was obvious..
Ah yeah i just read that on xda but i think it wasnt related to the DHD.. so i actually made a crucial error, i didnt delete the driver though but i did delete sync, i think the only thing i could do now is to reset the phone to factory defaults to get it back, right?
P.S. dont blame your self mate, its my fault, i should have waited for your reply befor doing research of my own.
EDIT:
I can use sync from the computer after i connect it with my USB cable, everything works so far
But will i be able to root/flash my device in this state?
/ENZ-
jkoljo said:
Because Vodaphone might think something is wrong if they find a WWE ROM from a phone with their own branding.
Ok.. What exactly have you been reading?? You are definitely not supposed to delete the driver and sync, you have to have those. I have to make a correction to my last reply, you should only read the guides in Desire HD section, I thought that it was obvious..
Click to expand...
Click to collapse
Oke i got HTC sync back and working again, so im over that problem now.
Next is S-OFF and rooting, right?
/ENZ-

Question about hboot, downgrade fron 6.93 to lower

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.

[Q] Trouble achieving S-Off

Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???
smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).
Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!
Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2

Categories

Resources