Develop Bugs

Rooting with Visonary 14 killed me phone

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.

[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

How do I get S-Off

I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.

ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.

What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z

steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside

I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z

steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...

schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App

Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul

Can anyone help me put original ROM back on my DHD

Hi, and thanks in advance for anyone who can help.
I have a desire hd phone, witch I love anyways I had it rooted a few months ago by a local phone shop, but I didn’t really see the benefit from it, in fact it caused problems so I performed a full factory reset within a few days, and thought that was the end of it.
Anyways my phone received the option to update to the 2.3 gingerbread on Monday, it downloads fine, and then when the install starts it freezes at about 20% of the way thorough.
I have contacted HTC several times about it, they say the phone will not update if it’s been rooted and I have to send it back to them to have it re-flashed, one person said it would cost £30, another said £200 so I would rather not send it to them. the last guy I spoke to was very helpful, he said it was possible for me to reflash the phone to its original ''shipped'' state, and if I joined a help forum I could possibly get some help, but he was unable to advise me on this., so here I am!!!
I received the phone new in January and it has had no updates until the one on Moday, and it was rooted using visionary a few months ago, I have performed several factory restores since then.
Current software is:
android version 2.2
baseband version 12.28b.60.140eU_26.03.02.26_m
build number 1.37.771.3 CL290190
software number 1.37.771.3
im in the uk, and on the 3 network
Many thanks,
Jamie

Jamie.Desire.HD said:
Hi, and thanks in advance for anyone who can help.
I have a desire hd phone, witch I love anyways I had it rooted a few months ago by a local phone shop, but I didn’t really see the benefit from it, in fact it caused problems so I performed a full factory reset within a few days, and thought that was the end of it.
Anyways my phone received the option to update to the 2.3 gingerbread on Monday, it downloads fine, and then when the install starts it freezes at about 20% of the way thorough.
I have contacted HTC several times about it, they say the phone will not update if it’s been rooted and I have to send it back to them to have it re-flashed, one person said it would cost £30, another said £200 so I would rather not send it to them. the last guy I spoke to was very helpful, he said it was possible for me to reflash the phone to its original ''shipped'' state, and if I joined a help forum I could possibly get some help, but he was unable to advise me on this., so here I am!!!
I received the phone new in January and it has had no updates until the one on Moday, and it was rooted using visionary a few months ago, I have performed several factory restores since then.
Current software is:
android version 2.2
baseband version 12.28b.60.140eU_26.03.02.26_m
build number 1.37.771.3 CL290190
software number 1.37.771.3
im in the uk, and on the 3 network
Many thanks,
Jamie
Click to expand...
Click to collapse
Hey dude, this link should help. I'm currently downloading it so that I can help you further when you get it also.
I would think twice about reverting everything back to stock though. You are now in the right place, the shop you went to, to get your phone rooted was the wrong place! We are a friendly bunch for the most part so do some reading in the desire HD general section and you'll find some nice ROMs that are close to stock firmware but perform better. If they're not for you then feel free to flash the official ROM from your provider that I have linked to above.
Oh yeah, Welcome to XDA!

Thanks for that, How do i go about installing it, and will it completely revert the phone back to its original state so i can use the ota update and get the 2.3 gingerbread?
And thanks again for your help

Damnit, what I've linked to is actually someones backup of a stock 3 ROM so it won't be quite back to factory fresh. Let me do some digging, I'll be back.
EDIT: What exactly did the shop do, other than use visionary? You could try AMT tools from here and query the device info, that should at least let us know what they have and haven't done to the phone. I suspect that they have set a super CID hence why the update won't go through. Try AMT and report back.

Thankyou very much your help is appreciated.

Should i try the link you posted earlier??

Just use AMT tools that I linked to above in one of my edits and check the CID, If it is just the CID that has been altered, then you can use this tool to reflash a 3UK CID which is H3G__001

when i use AMT it says AMT is designed for use with Desire HD and Dsire z / G2 ONLY But i have a desire HD ????

Strange, is there an option to click OK or ignore?
EDIT: Weird, I just booted into windows and I get the same thing with AMT tools. Now I'm really confused. Try using the other tool that I linked to and see what that displays.
EDIT 2: Just had a thought. Pull your battery then put it back in. Hold 'down' on the volume rocker then press the power button. Your phone should start in the bootloader and we should be able to get some more info. Once you've done this, list everything that it says in the bootloader screen.
Sorry, my brain is a bit slow today for some reason.

Ok ill do that now, i have also just rooted my phone again using visionary (i followed the link in your earlier message. so its rooted again now. cant believe i paid £20-00 to have that done, it took me less than 5 minutes to do it

ace pvt ship s-on
hboot-0.85.0007
microp-0438
radio-26.03.02.26_m
emmc-boot
oct 11 2010, 12:47:02

Jamie.Desire.HD said:
ace pvt ship s-on
hboot-0.85.0007
microp-0438
radio-26.03.02.26_m
emmc-boot
oct 11 2010, 12:47:02
Click to expand...
Click to collapse
OK, so it would seem as though all they did was root it and leave most things intact, I think they must have changed your CID though probably using the jkoljo's radio S-OFF tool.
Run that tool and try to change your CID to whatever it was that I said before H3G__001 I think it was, or you could equally use that tool to get radio s-off super-CID and sim-unlock, then install ROM manager from the market, flash Clockwork Mod Recovery and then flash a custom ROM after making a backup of course.
The world is your lobster at this point and flashing new ROMs can be fun. I might have to re-flash my current ROM myself as I think I've screwed something up with it from messing around too much earlier today

i dont understand the open "Desire HD easy radio tool.exe'' where is that??
Please remember i am a complete noob when it comes to this, lol
i had to download the visionary app using my phone as my laptop kept saying it had a virus.
i have downloaded the premium rom manager app, can you recomend and good roms, or where i can get a list of them? also could you explain in noob terms how to change my phone so i can get the 2.3 update? the cid bit!!!
Thank you, you have been very helpfull.

Jamie.Desire.HD said:
i dont understand the open "Desire HD easy radio tool.exe'' where is that??
Please remember i am a complete noob when it comes to this, lol
i had to download the visionary app using my phone as my laptop kept saying it had a virus.
i have downloaded the premium rom manager app, can you recomend and good roms, or where i can get a list of them? also could you explain in noob terms how to change my phone so i can get the 2.3 update? the cid bit!!!
Thank you, you have been very helpfull.
Click to expand...
Click to collapse
I'm gonna point you to this thread as it has everything you could possibly want or need to know in it. There is a link there to a thread all about how to flash a ROM, what tools you need on your PC etc..
With regards to how to get 2.3 onto your phone pretty much every ROM you'll find in the DEV section is based on 2.3. That thread I've linked also has links to pretty much every ROM currently available for the DHD and everything is explained far better than I would be able to explain things.
The tool to get Super-CID, which really only helps when it comes to flashing Radio's (which is something I would avoid until you've found your feet a little, however it's worth doing now, as it is simple and relatively worry free) is at the bottom of this post.
Happy reading and just remember that as long as you read all the instructions for something before starting it and you feel comfortable with what the instructions are explaining, then you will succeed with your end goal.

The tool to get Super-CID, which really only helps when it comes to flashing Radio's (which is something I would avoid until you've found your feet a little, however it's worth doing now, as it is simple and relatively worry free) is at the bottom of this post.
I have downloaded this, but i have no idea how to use it! i extracted the files to my desktop, it has a few different applications in there, one says start here but when i open it a command prompt comes up on my pc screen, i dont know where to go from there

Jamie.Desire.HD said:
The tool to get Super-CID, which really only helps when it comes to flashing Radio's (which is something I would avoid until you've found your feet a little, however it's worth doing now, as it is simple and relatively worry free) is at the bottom of this post.
I have downloaded this, but i have no idea how to use it! i extracted the files to my desktop, it has a few different applications in there, one says start here but when i open it a command prompt comes up on my pc screen, i dont know where to go from there
Click to expand...
Click to collapse
You should extract them into one folder, then from there you should be able to double click the only thing that looks like a program icon. If nothing is happening it would suggest that you need to update your .NET framework. Do that by running windows update or going here.
Honestly....... the best thing to do would be to go here and read the basic setup bit so that your PC is ready for everything, and then read the rest of that little guide and it should hold your hand through the whole process.

im going to attempt a custom rom form the link you gave me (everything desire hd) do you have any recomendations??

Cyanogenmod is interesting as it more like stock Android, MIUI is similar to iOS and then you have the sense ROMs with tweaks and whatnot. Have a look at the options available in the screenshots and see what you like the look of, it's a very subjective thing as some like one thing and others like something else.

the link you gave me for the rado code was missing the important bit!
i managed to find it somewhere else
http://igyaan.in/2011/01/how-to-root-htc-desire-hd-included-downgrade-from-1-72-405-3-to-1-32/
have a look at the link you gave me, it is missing the main programme.
do you have to go through the root procedure every time you use the radio tool, or will it work every time after the phone is rooted. the reason i ask is that i just tried to do it and it said ''operation failed, probably connection'' ill try it again now

Jamie.Desire.HD said:
the link you gave me for the rado code was missing the important bit!
i managed to find it somewhere else
http://igyaan.in/2011/01/how-to-root-htc-desire-hd-included-downgrade-from-1-72-405-3-to-1-32/
have a look at the link you gave me, it is missing the main programme.
do you have to go through the root procedure every time you use the radio tool, or will it work every time after the phone is rooted. the reason i ask is that i just tried to do it and it said ''operation failed, probably connection'' ill try it again now
Click to expand...
Click to collapse
It usually fails the first time, I don't know why. After a reboot it worked for me, keep your phone screen on though as the package will request superuser permission.
That link is definitely not missing anything as I've downloaded and run it from that link several times, but maybe your download got corrupted.
Glad all seems well now anyway.

GB 2.3.3 almost rooted

So I was reading a post about someone who was potentially able to downgrade hboot 2.16 hw4 2.3.3 to hboot 2.10 via bootloader and a PC63IMG.zip that had 3.70 in it. So I tried on my 2.3.3 s-On evo and sure enough it failed. It wouldnt work because it was an older version. So, I extracted the PC63IMG.zip and replaced the hboot 2.10 with hboot 2.16 (renaming hboot 2.16 to hboot 2.10) from the post in the dev section. I used winrar and with normal compression rezipped the files and signed in android kitchen. it actually loaded the files and went through checking them, but once check it kicked me back to the main menu of the bootloader with no error or messages. I tried the same with the file with no compression when zipped and signed and i got an error stating that it was a wrong file. and didnt even pass the check. So have I stumbled upon something simple and useful? Can someone help me look into this further and maybe it will get us somewhere. Or am I a dumb?

Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.

androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.

Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked

androidsupra said:
Sweet. I'm sure you are the first one to get this ROM ported, I know others have tried but they haven't had much success.
Click to expand...
Click to collapse
You do know the dev section is for more than ROM's. Moron. This is a post from someone attempting to find root and you show your true intelligence level.
Sent from my PC36100 using Tapatalk

spotopolis said:
What? I never said anything about porting. I was trying to find a simple way to Root my Evo running 2.3.3. Still no luck but I was hoping what I found may be something someone has not yet tried. Its simple but I was suprised that it looked like it passed the bootloader check. I did not receive any errors, but at the same time could not downgrade.
Click to expand...
Click to collapse
He wasn't serious about porting anything, common thing to do when someone posts in the wrong section (especially in development).
On my main note, any modification of an "official" PC36IMG.zip would break HTC'S signature and the bootloader would not accept the update.
Sent from my PC36100 using XDA Premium App

He's attempting to Flame I believe. Due to a lot of mis placed posts. However, I do not find this to be mis placed. It is valid, and just the fact that it tried to run is great. farther then most have gotten, and the way I see it, any good inputs/thoughts should be welcomed warmly.
Sent from my Xoom using XDA Premium App

So now what I am trying to do is download, extract, and replace the hboot from http://www.megaupload.com/?d=VSFLE9CD with the 0.76 hboot, repack, resign, and test in the bootloader. This is all really simple stuff and thats why I am wondering if it will work. Because its so simple something like this was overlooked.

HipKat said:
Once you got back to the hboot menu, what version did it say you have?
If 2.10, I would think your next bet is try and run unrevoked
Click to expand...
Click to collapse
as far has my bootloader says for now it has the latest everything unfortunately. hboot 2.16 hw4 and all that. I was surprised that I was able to get passed the check without an error doing this though and its why I posted. I have 4 minutes left on the new PC63IMG.zip downloading before I can try to mess with it.

I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?

sivarticus85 said:
I tried this exact same thing just last night. It did the same thing to me as well, with it returning to the bootloader menu with no error msgs. If somehow we are able to edit the PC36IMG.zip file to match the hboot version 2.16 with the 3.70 update to pass security check then we may be on to something. But I'm not sure how to resign an IMG zip with HTC's signature to pass security. Thoughts?
Click to expand...
Click to collapse
I am about to attempt now after signing the zip with kitchen.

spotopolis said:
I am about to attempt now after signing the zip with kitchen.
Click to expand...
Click to collapse
You will be my hero if this works.

Damn! Same thing. I loaded up the latest update with the older hboot renamed to match the new one it replaced. rezipped with normal compression, signed PC63IMG.zip with latest kitchen, it loaded the modded PC63IMG all the way in the bootloader and passed that, then started checking the file and then just went to the main menu again with no errors.

Is it possible that it is not doing anything because it thinks im loading up the same version it is running? Could I simply change another file to make the bootloader think Im uploading a newer version so it would take the update?

I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.

That sucks. Oh well can't hurt that you tried.

Otta way to think out of the box. I hope u get somewhere with this buddy. I would love to help but I know nothing. Lol. I can make lock rings. That's bout it. Good luck
Sent from my PC36100 using Tapatalk

androidsupra said:
I guess you guys haven't heard the news, but you can't resign the damn thing with HTC's key because we don't have HTC's keys. As many have stated the focus should be temp root, then the bootloader shall fall. Cart before the horse kids.
Click to expand...
Click to collapse
I know that but if you don't sign with the kitchen it wouldn't have even gotten this far correct? So its something right? Even if it doesn't work, its another thing on the list that has been tried and maybe it will lead to something else. You never know with electronics. A single random chip could be made slightly different from others and it changes everything. No way to know until you try.

Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of tricking the bootloader. And the cycle continues.

androidsupra said:
Do I really need to link every post where someone has tried to mod these files, I mean really...
There is a post about every three days on this same subject, it goes on for two days and then gets locked like this one will. And on the next day somebody else posts their marvelous idea of pricking the bootloader. And the cycle continues.
Click to expand...
Click to collapse
Is that not the point of this community? Someone trying to use some other persons idea and expand on it? Who cares if it ultimately doesn't work? Its information.