Related
I can't find a solution to this from searching the forums so i'm just gonna ask.
I'm using the gfree method via adb. i'm getting all the way through it without any problems untill i get to the "lock in" root section.
I get the error message that the wiki says should get and then ignore, but i also get another message that says something like
"cp: can't stat '/sdcard/su' : no such file or directory"
any help with this would be appreciated.
also, are all the bad things i've heard about visionary true? should i go ahead and root with visionary, or keep trying this way? thanks
I just checked and it says I'm s-off. I'm very confused.
Sent from my T-Mobile G2 using XDA App
Well first ill tell u Visionary worked for me in like 10 minutes time. Very easy n very fast. Not true what they say. If u got s-off, good. Ur almost there. Have to check out gfree method quik in order to help u. Hold up
G2 with ExtraHotSauce v0.2!!
What guide are you using, the one on the Wiki doesn't have you copy (cp) anything.
is this the command where you run into the problem?
/data/local/tmp/root
Click to expand...
Click to collapse
This is running a script to lock in root, you already ran gfree while you were temp rooted so that's why you are S-OFF.
Do you have the "su" file on the root of your SD card?
You should be able to retry everything but the gfree part.
As for Visionary, some people report success but other have reported big problems. I found the gfree method to work pretty well, even though I used Visionary when I was temp-rooting (when I just got my phone) when I permarooted I used the gfree method.
raitchison said:
What guide are you using, the one on the Wiki doesn't have you copy (cp) anything.
is this the command where you run into the problem?
This is running a script to lock in root, you already ran gfree while you were temp rooted so that's why you are S-OFF.
Do you have the "su" file on the root of your SD card?
You should be able to retry everything but the gfree part.
As for Visionary, some people report success but other have reported big problems. I found the gfree method to work pretty well, even though I used Visionary when I was temp-rooting (when I just got my phone) when I permarooted I used the gfree method.
Click to expand...
Click to collapse
yes, that is the command that is giving me problems. i checked my sd card and superuser.apk is at the root of it.
when you say retry everything what exactly would i retry? i'm at work, and don't have access to adb. do i need adb to "retry"
so, there are two different guides that perm root. the first is the wiki and this is the one that i was following. the other has almost the exact same steps except it has the wpthis file. i guess when i get home i'll try the other method and see if it works. thanks for everone's help
no its a 2 step procedure maybe you should go ahead and unroot and s-on then go ahead and re root. if not you can still re run everything start off with temp root then go ahead and lock in the perma root
thenaut said:
yes, that is the command that is giving me problems. i checked my sd card and superuser.apk is at the root of it.
when you say retry everything what exactly would i retry? i'm at work, and don't have access to adb. do i need adb to "retry"
Click to expand...
Click to collapse
You should have both Superuser.apk and su on the root of your SD card. Either push it from your computer again (first command in the wiki):
Code:
adb push su /sdcard/su
Or just copy it to your SD card (be sure to unmount the card when done). Then re-run the root script in terminal.
that totally did it. I pushed the su file and re ran the script and i got root. it's wierd because i thought i pushed it the first time but i guess not. anyway, thanks
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Arconaught said:
About 3 hours ago, I won a Desire Z (wheeey!) at the HTC London meetup. Naturally, I came straight here after the help I got in January rooting my Desire.
I used the Visionary method and obtained temp root status, and then attempted perm root, which seemed to work. All of the guides I have read include a bunch of steps after this, one of which included deleting Visionary, which I then did. I just turned the phone off, took the battery out for a bit and then turned it back on. I still have the Superuser icon and the Terminal Emulator indicates that I have root access... is that it then? It's that simple?
Please tell me if I've done anything wrong, as I don't want to flash Cyanogen and Clockwork Recovery if it's all going to go to hell on me. Any advice or confirmation on whether or not I've obtained perm root would be lovely.
Oh, my firmware version is 1.34.405... etc. Is this simply the last version which allows for such easy root?
Click to expand...
Click to collapse
Having the SuperUser icon just means the app is installed, open up terminal and type 'su' to see if it throws up any errors
Sent from my HTC Vision using XDA App
I should have mentioned that I did that and got the # symbol, am I good to go?
Arconaught said:
I should have mentioned that I did that and got the # symbol, am I good to go?
Click to expand...
Click to collapse
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
In theory, yes; in practice, no. Visionary (with the G2/Desire Z, at least) is known to be a bit buggy. You shouldn't have any issues installing custom ROMs but, I would recommend using the wiki method to root.
Click to expand...
Click to collapse
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
redpoint73 said:
My understanding, if he already used Visionary to root, and it worked than he should be good to go. Either it works, or it doesn't. The risk with Visionary is that it sometimes corrupts some partitions, which causes the phone to not boot. I haven't read any conclusive reports on Visionary causing long term issues (correct me if I'm wrong).
Click to expand...
Click to collapse
This is my understanding as well, though I'd probably still use GFREE to get S-OFF if I were OP.
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
I used the wiki method myself, those that used other methods (like Visionary) and were told to root via the wiki seem to have all just started at the beginning, from what I've read.
Sent from my HTC Vision using XDA App
Arconaught said:
That's my next question, I'm using this guide ( http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 ) to try and get S-Off to flash Cyanogen and I'm wondering what step to start on, assuming from your replies that I'm rooted already.
I know it's a bit of a dumb question, but I just don't wanna fudge my new phone.
Click to expand...
Click to collapse
Whoa the Wiki method is completely different, looks like it was rewritten on 04/01.
You can completely ignore the temp rooting steps and concentrate on the gfree steps
From the "Necessary Files" section you need gfree, flash_image and ClockWorkMod Recovery
I would use the latest ClockWorkMod recovery rather than the one listed on the Wiki:
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img (of course it's only the latest as of the time of this writing)
From step 2 you need to use:
Code:
$ adb push gfree /data/local/tmp/
$ adb push flash_image /data/local/tmp/
From step 2.a you need to use:
Code:
$ adb push recovery-clockwork-3.0.2.4-vision.img /data/local/tmp/recovery.img
Again note that the file name for CWM will depend on the version of CWM you are using.
Skip to step 4.b you need to use:
Code:
# cd /data/local/tmp
# ./gfree -f
# ./flash_image recovery recovery.img
# sync
Continue on as normal from here.
I skipped the temp root and perm root sections as you are already perm root.
I also skipped the ENG HBOOT parts, since that's not strictly necessary and the most risky part of the whole process (one mistake can result in a brick). If you want to flash the ENG HBOOT you would need to follow steps 4.a instead of 4.b, (you would also need the necessary HBOOT of course) the only command you need to omit from 4.a or 4.b is "# ./root_psn" which is the script which establishes permanent root.
Thanks a lot so far man, but I'm still stuck. I have adb, when I open it in the SDK, it flows for a bit, then closes. This is right, right? I'm meant to do all of these prompts via the cmd window?
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Arconaught said:
OK, I've now sorted adb, but I can't get anything to work past that. Nothing will transfer to my phone and I'm going to kill... somebody.
Click to expand...
Click to collapse
You say you've sorted adb, but can you be more specific please ? What works and what doesn't work exactly ?
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
There is a great write up here about getting adb working. It sounds like either you didn't set up a "path" to use those commands anywhere or if you don't want to do that make sure your files are in the same folder as your adb.
Sent from my HTC Vision using XDA App
Arconaught said:
Ah, yeah, sorry. I got to the point where when I type in "adb devices" in the command window, it shows me my phone, with the serial number and whatnot. However, whenever i try the command:
$ adb push gfree /data/local/tmp/
It just won't work. I have all the files together in my desktop at the moment, having moved them from the downloads folder on my laptop. Is there a specific place I should have the stuff I need to send to my phone?
Click to expand...
Click to collapse
You need to have the files (extracted from the ZIP files you downloaded) in the same folder you run the ADB commands, if your ADB is in your path you should be able to run ADB commands from any folder.
To summarize you need to extract all the zips you downloaded under necessary files, all to the same folder. The open a command prompt and CD to that folder before you start using your adb push commands.
shortlived said:
There is a great write up here about getting adb working.
Click to expand...
Click to collapse
Yeah, steviewevie wrote it:
http://forum.xda-developers.com/showthread.php?t=865685
But it looks like he is willing to give the OP some personalized help.
Right, thanks guys, I think I'm making some progress.
ADB is all set up, and as far as I'm aware, having:
program files > android sdk > platform tools
on my path should mean I can open adb from anywhere right? I have all of the extracted files in platform tools, where adb is, in my program files... is this right, or have I completely missed the point here?
I keep getting "cannot stat 'gfree':: No such file or directory"
Sorry, I seem really stupid concerning this whole thing, but I'm sure it's something equally obvious that I'm just not seeing.
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Arconaught said:
New problem. I worked out what I'd done wrong there, and got everything onto my phone. However, when trying to change the directory to /data/local/tmp, I keep getting "The system cannot find the path specified"
Now what am I doing wrong?
Click to expand...
Click to collapse
Remember you are running those commands (everything in that section) from an ADB shell, not from the Windows command prompt.
Excuse my ignorance, but what exactly do you mean by that? What should I do?
Hi guys. I have a brand new Desire HD, T-mobile (uk) branded.
Running Android 2.2.1
Build number 1.84.110.3 CL334589 Release-Keys
I am trying to downgrade to 1.32 so that i can root. I have made a goldcard, using various methods (HxD, goldcard helper, and goldcard tool)...Following the guides, everything seems to go to plan, no error messages or anything.
I then go through the process of....
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
cd /data/local/tmp
./misc_version -s 1.31.405.6
Again no problems there.....When phone is rebooted into bootloader, it loads the PD98IMG.zip file, and after checking it, I always get the error "update failed, incorrect cid" I don't know where I'm going wrong, the goldcard tools are reversing the CIDs for me.....Any tips ?
Thanks
mrmcox said:
Hi guys. I have a brand new Desire HD, T-mobile (uk) branded.
Running Android 2.2.1
Build number 1.84.110.3 CL334589 Release-Keys
I am trying to downgrade to 1.32 so that i can root. I have made a goldcard, using various methods (HxD, goldcard helper, and goldcard tool)...Following the guides, everything seems to go to plan, no error messages or anything.
I then go through the process of....
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
cd /data/local/tmp
./misc_version -s 1.31.405.6
Again no problems there.....When phone is rebooted into bootloader, it loads the PD98IMG.zip file, and after checking it, I always get the error "update failed, incorrect cid" I don't know where I'm going wrong, the goldcard tools are reversing the CIDs for me.....Any tips ?
Thanks
Click to expand...
Click to collapse
it can be by several thinks...
i would try to format the sd-card and re-do the goldcard again (goldcard tool works well) be sure about you have the correct CID in the sd card
SERGI.3210 said:
it can be by several thinks...
i would try to format the sd-card and re-do the goldcard again (goldcard tool works well) be sure about you have the correct CID in the sd card
Click to expand...
Click to collapse
I have tried the goldcard tool a few times now, with various micro SD cards (8GB samsung that was bundled with phone. 2gb sandisk. and 2gb kingston)
when I run it, selecting "mmc0" I get CID value as....
45010053454D3034479022CD0AA93E10
and it reverses it to...
003EA90ACD22904734304D4553000145 ...
Is that correct ? Then i fill in the details on PSAS and get my image emailed and load/patch the card with goldcard tool. If I try and get cid using "mmc1" I get messgae...
* daemon started successfully *
/sys/class/mmc_host/mmc1/mmc1:*/cid: No such file or directory
------------------------
Could not locate CID in output
And with gold card created, I o through the motions again, and keep getting Update failed, incorrect CID.
u can obtain temporary root???
i checked the commands of the first post and are ok...
really all the issues like this was solved formatting the sd again.. FAT for -2gb and fat 32 for 8gb sd card...
your troubble is weird...
mrmcox said:
when I run it, selecting "mmc0" I get CID value as....
Click to expand...
Click to collapse
Hmm, it might be useful to read the Downgrade guide again, mate Especially the bolded part after goldcard link..
jkoljo said:
Hmm, it might be useful to read the Downgrade guide again, mate Especially the bolded part after goldcard link..
Click to expand...
Click to collapse
Thanks for the reply. I tried to make the gold card again, using mmc2 with the gold card helper tool on the handset.
I get the reversed CID as
00b2003be96a721030303030304d531b Tired making gold card with HxD and with the gold card tool, but each time when I boot into bootloader on the phone, it loads the PD98IMG file and after checking it I get
CID incorrect!
Update fail
Press <power> to reboot
Any idea where I can be going wrong ?
Are you selecting physical disk and making sure write access is ticked in the hex editor?
Sent from my Motorola Startac running Atari 2600 software!
hey, need some help here.. i'm on stock froyo. the software version is 1.84.707.2. i downloaded the 2.36 and 1.32 version . but couldn't seem to flash both RUU at all. its an exe file. my phone entered into BOOTloader and while sending signature, the screen on pc says CID error 131. ask me to get the correct utility. my desire hd is unbranded and unrooted. its still new.. it is still S-ON. I had never rooted it or done anything to it . just wanted to make sure i have a functional RUU in backup in case i want to send for warranty.what should i do? i'm from malaysia btw
Any problems regarding CID Error mean you need a goldcard. If you've made one and you still get this error, your card isn't gold. Try using a different card.
thanks guys for all the help and replies.
I finally got my goldcard to work, ended up buying a new card and using that, and it worked first time.
I now have downgraded to 1.32, have perm root, radio s-off, and eng s-off. I've just upgraded radio to latest version, and I'm about to upgrade to android revolution HD 5.1.7.
Thanks again for all the help
andyharney said:
Any problems regarding CID Error mean you need a goldcard. If you've made one and you still get this error, your card isn't gold. Try using a different card.
Click to expand...
Click to collapse
Thanks. Even if my phone is unbranded and new, I still need a goldcard??
Sent from my HTC Desire using XDA App
dunstan92 said:
Thanks. Even if my phone is unbranded and new, I still need a goldcard??
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
if your phone is unbranded you don't need a gold card
I will repeat what I said just incase there is any confusion.
Any CID related errors while trying to downgrade mean you need a goldcard. No if's no but's, a goldcard will be required. Remember there are unbranded builds that will not have the WWE CID.
One example is builds found in the East. WWE = x.xx.405.x Indian = x.xx.720.x
They are both unbranded, however a goldcard is required to flash from 720 to 405. I hope I've cleared things up.
andyharney said:
I will repeat what I said just incase there is any confusion.
Any CID related errors while trying to downgrade mean you need a goldcard. No if's no but's, a goldcard will be required. Remember there are unbranded builds that will not have the WWE CID.
One example is builds found in the East. WWE = x.xx.405.x Indian = x.xx.720.x
They are both unbranded, however a goldcard is required to flash from 720 to 405. I hope I've cleared things up.
Click to expand...
Click to collapse
Thank you
Sent from my HTC Desire using XDA App
Yes, you have cleared things up. Thank you very much. So if I create a goldcard and flash the ruu 1.32.405.x ,will it cause any problem if I send it for warranty service? Because I can't find the ruu with 1.84.707.2 for my phone. Is there any ruu for Malaysia or Asia yet?
Sent from my HTC Desire using XDA App
Sent from my HTC Desire using XDA App
I'm pretty sure the 405 version WWE (World Wide English) will be Ok to return as it is an official HTC build.
Alright. Thanks. So do I still need to downgrade my stock rom even with a goldcard? Am planning to flash the 2.36.405.x ruu over my current rom.
Sent from my HTC Desire using XDA App
i need some help here, im getting to section B step 23 of the guide to rooting and flashing and then something not so good is happening with my phone.
In getting "process stopped unexpectedly" messages from (android.process.acore)
they are constantly popping up.
i've previously had the problem of incorrect CID as well, but it solve after i format the MMC to FAT 32 and redo the goldcard steps
Hi I have a gsm desire which is usb bricked. I have tried to use the procedure described here:
http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick
but it doesnt provide a solution. I get a message from windows 7 stating usb device not recognised. The desire is rooted, s-off, and has modaco non sense kitchen rom on it.
fastboot oem boot data is as attached.
It seems from above log.. your CID is O2__001 .. try to edit the mtd0.img file attached there and push that to your device
Use another card reader to copy the new mtd0.img with your CID at the root of the sd card. Then plug it to your desire, boot, and launch terminal emulator. Enter this :
Code:
su
cp /sdcard/mtd0.img /data/mtd0.img
reboot
Hi,
I have alreeady tried this, as per the procedure, and it doesnt work for me.
kev94 said:
Use another card reader to copy the new mtd0.img with your CID at the root of the sd card. Then plug it to your desire, boot, and launch terminal emulator. Enter this :
Code:
su
cp /sdcard/mtd0.img /data/mtd0.img
reboot
Click to expand...
Click to collapse
Hi I tried this but nothing changes.
if you are S-OFF
simply go into fastboot mode and do:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
and that is is, of course you must have ADB set up on your PC
USB BRICK RESOLVED - Thanks DZUMAGOS
Hi,
This has WORKED!! Thank you. I cant tell you how many hours I have spent trying to fix this. I want to be a little wary because I tried the USB fix detailed in the original thread and it seemed to work temporarily, but this has been working for a couple of hours now and I have tried rebooting the desire, laptop, using usb in recovery, all scenarios, and it seems to have fixed the problem. Thank you. My wife and kids will be happy to see me again!!
One plus point is that I have learnt much in trying to solve this problem, but I wish I had found this solution quicker.
I hope you dont mind but I have a couple of extra questions. I am keen to learn and you never know I may know enough to help someone else on the forum one day.
Can I ask how it works? I understand the first fastboot line, but what does the fastboot oem eraseconfig bit do?.
Do you know why this problem was caused in the first place?
Will this solution work for all USB Bricked S-OFF desires? If so I think it may be worth mentioning in the main USB Brick thread before others spend hours on it.
Also, where I have been performing the fastboot oem enableqxdm 0 via adb previously to try to fix this I have numerous files that have been written onto the sd card like "qxdm_20110607_125733_1.dm". Is it safe to remove these, or do I need to keep them on the sdcard?
Thank you so much again. The will to live has returned, and I can now find other ways of messing my desire up.
you can delete the files from SD, these are just some log files (qxdm logs)
how this works ? well i THINK that this formats the misc partition with mtd0 which makes it re-do itself with default settings (however this is just me guessing, i can be faaar away from truth right now)
also this method is not mention in the USB-Brick 1st post, it is somwhere later on mentioned a few times.
this should work for all S-OFF USB-Bricked desires
why does it happen?
something to do with recovery obviously, they didnt figure that out exactly, it just happens randomly, you can have it after flashing 10 roms or 10.000... or never. i got it after switichng to AmonRa 2.0.1 and restoring a GB nandroid. fixed it and everything is OK ever since.
also i dont mind you hitting 'thanks' button
i dont know if it is possible to do S-OFF while usb-bricked (for S-ON users), this was sometimes adviced to the S-ON users who experienced usb-brick. however i dont know if it was possible to do S-OFF.
anyway this is another good reason to S-OFF, it makes usb-brick totally fixable whereas the other method with mtd0 etc doesnt often work and is seriously more complicated
Hi,
thank you very much for this info. I understand a little better. Hit the thanks button, so thanks should be official now..
I'll try to re-title my original thread to add S-OFF. It may help others to find your answer quicker.
dzumagos said:
if you are S-OFF
simply go into fastboot mode and do:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
and that is is, of course you must have ADB set up on your PC
Click to expand...
Click to collapse
Thanks a million !!! I thought my phone will never be useful , but this post saved my phone.
Please help I tried everything I could.
My Android Version is: 2.3.5
My software version is: 3.12.405.1
When I bought it was with Froyo and from the automatic updates it became to Gingerbread version.
And is open not locked branded to a provider (like vodafone etc)
I first tried the: aahk-13012012 but the phone stays on the white screen with the message : pd98img.zip wrong image. and after 1 1/2 hour returns to the reboot menu.
After I tried the downgrade method with the following commands:
adb push misc_version /data/local/tmp
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
but at the end it doesn't return the # symbol. ( I am attaching captures from the procedures & results below)
Is there a problem with my phone or I am doing something wrong?
PLEASE HELP!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hmmm ... i also bought dhd ... which was via Vodafone ... i also had it in froyo (in stock) ... and later updated to ginger bread (2.3.5) ... don't remmeber the exact software version ... but mine was a bit different from yours .... coming to the point ... i also used aahk ... the latest version available ... and i had my dhd rooted with no problems ... are you sure u read the manual carefully .. and did everything perfectly .. there were a number of things ... usb debugging mode . uninstalling htc sync ... installing adb drivers ... etc etc .... did you follow it accurately ... i can't say what the problem can be , but it worked perfectly for me .. !! i even eng s-off it later , to make it work with arhd 6.3.1 ...
well the first thing I might think of right now is quite simple.
You'll need to make the same steps but beforehand you'll need to make your Micro SD card into a GoldCard.
To create your GoldCard you can follow the following link
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Does your dhd go into bootloop?. if it does then the gold card will get out and will enable you to flash a stock rom.
No it doesn't go to bootloop
mrfaisal007 said:
hmmm ... i also bought dhd ... which was via Vodafone ... i also had it in froyo (in stock) ... and later updated to ginger bread (2.3.5) ... don't remmeber the exact software version ... but mine was a bit different from yours .... coming to the point ... i also used aahk ... the latest version available ... and i had my dhd rooted with no problems ... are you sure u read the manual carefully .. and did everything perfectly .. there were a number of things ... usb debugging mode . uninstalling htc sync ... installing adb drivers ... etc etc .... did you follow it accurately ... i can't say what the problem can be , but it worked perfectly for me .. !! i even eng s-off it later , to make it work with arhd 6.3.1 ...
Click to expand...
Click to collapse
Yes I read it very carefully & I did exactly as the manual instructs more than 3 times actually.
the only prob i had was i had prev used the htc unlock prog, so i re-locked then all was fine.
sharps said:
the only prob i had was i had prev used the htc unlock prog, so i re-locked then all was fine.
Click to expand...
Click to collapse
I do not clearly understand what you did?
earthbrother said:
well the first thing I might think of right now is quite simple.
You'll need to make the same steps but beforehand you'll need to make your Micro SD card into a GoldCard.
To create your GoldCard you can follow the following link
....../mobile/how-to-make-gold-card-for-htc-desire-hd/
Click to expand...
Click to collapse
One of the links inside the link you sent me for the gold card is dead
I've re-rooted mine today using the Ace Hack Tool..
I know you've tried it already, just try it again from scratch using a different pc. uninstall all HTC drivers and reinstall the one included in the package. make sure you have USB debugging on, and just follow the instructions.
I have the same problem. There is no way to root DHD with 3.12. Also i tried to install 3.13 from USA but it is also unable.That's why we must wait for instruction or send phone to HTC and they can make dwongrade.
I used AAHK (Advanced Ace hack Kit) on my DHD and it worked great.
Anyone who wants to use it MUST read ALL the documentation.
If the bootloader was unlocked through htcdev, you must lock it back before using AAHK. There is a command you must use, to re-lock the bootloader.
Anyway the conclusion is not to unlock the bootloader using htcdev:
http://forum.xda-developers.com/showthread.php?t=1456749
Do it from the start with AAHK.
agoustel said:
Please help I tried everything I could.
My Android Version is: 2.3.5
My software version is: 3.12.405.1
When I bought it was with Froyo and from the automatic updates it became to Gingerbread version.
And is open not locked branded to a provider (like vodafone etc)
I first tried the: aahk-13012012 but the phone stays on the white screen with the message : pd98img.zip wrong image. and after 1 1/2 hour returns to the reboot menu.
After I tried the downgrade method with the following commands:
adb push misc_version /data/local/tmp
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
but at the end it doesn't return the # symbol. ( I am attaching captures from the procedures & results below)
Is there a problem with my phone or I am doing something wrong?
PLEASE HELP!
View attachment 866284
View attachment 866285
Click to expand...
Click to collapse
For me i had problems using fr3evo to return to stock and if u had ENG Hboot u need to put an additional command line in to restore the original bootloader.
as for when it says it should return "#"
usually the adb shell shuts down, it says that this might happen in the fr3evo instructions.
if ur Command prompt on ur PC has ">" in the end (X:/xxx/xxx>), type "adb shell"
it should come up with "$" sign
If the command prompt has "$" or u just restarted the adb shell
type "su" and u'll get "#"
the "#" just means ur in the superuser command mode
AAHK does gold card on its own so don't even try doing that yourself since it will mess with AAHK. Uninstall HTC Sync, disable antivirus, firewall blah blah. Read the effen manual and run AAHK. Let it do its thing. Once done it WILL let you know. Just read.
Sent from my Desire HD using XDA App
I have the same problem trying to root my DHD. Once an upgrade to Gingerbread is done, I think HTC has blocked the exploit points used by the rooting software. I tried several times yesterday but no luck
oladipomd said:
I have the same problem trying to root my DHD. Once an upgrade to Gingerbread is done, I think HTC has blocked the exploit points used by the rooting software. I tried several times yesterday but no luck
Click to expand...
Click to collapse
I rooted several DHDs on Gingerbread using AAHK without a single issue.
Sent from my Desire HD using XDA App
addictivetips . com/mobile/how-to-downgrade-htc-desire-hd-to-root-it-after-ota-update/
HTC released the 1.72.405.3 OTA Android update for HTC Desire HD in December 2010 that included enhanced security, making it impossible to gain permanent root access on the device after the update. It also removed the permanent root and S-OFF access users had already obtained prior to the update. While there still isn’t a way to gain permanent root and S-OFF on the updated version, you can however downgrade your phone to an earlier build in order to be able to do so.
it worked just fine
thank you
zero_ap said:
For me i had problems using fr3evo to return to stock and if u had ENG Hboot u need to put an additional command line in to restore the original bootloader.
as for when it says it should return "#"
usually the adb shell shuts down, it says that this might happen in the fr3evo instructions.
if ur Command prompt on ur PC has ">" in the end (X:/xxx/xxx>), type "adb shell"
it should come up with "$" sign
If the command prompt has "$" or u just restarted the adb shell
type "su" and u'll get "#"
the "#" just means ur in the superuser command mode
Click to expand...
Click to collapse
Well, while we are on the topic, I tried to root my Desire Hd with Aahk.
As I'm using gingerbread release, it downgraded it for me.
As I tried to root it, it came up with a couple of errors, including something like I-Normal Error Here-I.
Have anybody seen this before? As that message appeared and phone was stiuck on it, I had to disconnect it. After which I was stuck in bootloop. In a panic, I tried to flash a custom Rom without realising that I'm still S-On. Didn't know what to do, found this forum with tutorial for bootloop and thanks to one of the Xda members I've managed to put the stock Rom back in.
I would like to have another go this weekend, I'm also in process of reading different posts and understanding how everything works etc. I would be very grateful if some one could guide me on the right direction. I'm planning on flashing cyanogene ? 7.1 and if I'm understanding correctly I will be able to use aahk to downgrade my room, root my phone , turn s-off and then use room manager to download room of my choice and flash it? I've still got a lot to read through before I'll do it.
Am I going in to right direction?
Cheers,
Luke
Sent from my HTC Desire HD A9191 using XDA App
lukass1984 said:
Well, while we are on the topic, I tried to root my Desire Hd with Aahk.
As I'm using gingerbread release, it downgraded it for me.
As I tried to root it, it came up with a couple of errors, including something like I-Normal Error Here-I.
Have anybody seen this before? As that message appeared and phone was stiuck on it, I had to disconnect it. After which I was stuck in bootloop. In a panic, I tried to flash a custom Rom without realising that I'm still S-On. Didn't know what to do, found this forum with tutorial for bootloop and thanks to one of the Xda members I've managed to put the stock Rom back in.
I would like to have another go this weekend, I'm also in process of reading different posts and understanding how everything works etc. I would be very grateful if some one could guide me on the right direction. I'm planning on flashing cyanogene ? 7.1 and if I'm understanding correctly I will be able to use aahk to downgrade my room, root my phone , turn s-off and then use room manager to download room of my choice and flash it? I've still got a lot to read through before I'll do it.
Am I going in to right direction?
Cheers,
Luke
Sent from my HTC Desire HD A9191 using XDA App
Click to expand...
Click to collapse
The "normal error here" is, well,normal lol.. But you shouldn't get such on it.
What i advise you to do is to check the MD5 checksum of the downloaded files ( AAHK and the custom ROM, in your case CM7.1) before running them.
Also, uninstall all htc drivers from your pc; install the drivers included in the AAHK package.
Disable your antivirus software, and close any programs running.
Re-read the AAHK manual (seriously, sometimes a tiny step makes a huge difference)
Make yourself a nice cup of coffee.
Be patient, and if you come across any complications ask for help here.
Good luck, and hopefully it will work out for you this time
Sent from my Desire HD using Tapatalk