I've tried flashing the cwm .img file as the guide says on the other thread, only leaving out the superuser file on the SD card, in my command window it says its installed ok but it don't actually install on my phone as the recovery doesn't change. Am I missing something here? This is definitely a pita lol
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Rooting and upgrading Rom
- Thread starter stevohd
- Start date
-
- Tags
- htc desire hd
I'm not sure if its the stock one but it says 4ext recovery touch by madmaxx82 when booting it up. When I flashed the recovery the green bar came up at top right of the screen but that was it.
Actually, reading other threads it looks like Im better off staying with 4ext, seems to be better than cwm from what I can see. Though it doesn't explain why I can't flash a different recovery in its place. My only problem is putting the superuser file on my SD card to flash it in recovery as my dhd doesn't like SD cards at the min.
Sorry for all the hassle with this :'( I'm learning fast and the phone is being a bit of a nightmare. Hopefully my next project will be more straight forward
Sorry for all the hassle with this :'( I'm learning fast and the phone is being a bit of a nightmare. Hopefully my next project will be more straight forward
scotty85
Extreme Android User
Hmm I wonder if the inability to read the sd is related to the inability to flash a new recovery. Did some poking around,it seems you may have a "usb brick".
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1077985
Try the commands on the first page,and see if that helps.
You may also try a couple other sd cards if you haven't allready.
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1077985
Try the commands on the first page,and see if that helps.
You may also try a couple other sd cards if you haven't allready.
Thanks for doing some research scotty, ive had a go at another sd card and got the same problem, just tried that command and got this........
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Carrie>cd c:\android\sdk\platform-tools
C:\Android\sdk\platform-tools>fastboot oem enableqxdm 0
...
OKAY [ 0.141s]
finished. total time: 0.141s
C:\Android\sdk\platform-tools>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Android\sdk\platform-tools>
beginning to think im doing something wrong or i got a duff dhd.
attached my hboot screen if that is of any use.
Attachments
I've looked into updating my ruu aswell as it says in the xda thread which sorted that usb brick problem but when i tried to update my ruu it didnt work. when it said update rom from image version: 3.13.161.5 , under the, to image version: is blank, no version shown. and when running the update as id expect i get an error [156]:image error.
scotty85
Extreme Android User
not sure why youre getting the command error. typically its becasue youve typed something that fastboot doesnt recognize. try this,and post the results:
fastboot oem ?
make sure you get the "?"
on the ruu,while s on the phone is doing many,many security checks wich prevent you from running any old ruu. youll need to find one for your exact build number or newer(numerically higher) in order for it to work.
ill see ifn i can find anything else out about the no sd card situation.
also,sorry for the late responses,was a busy weekend
fastboot oem ?
make sure you get the "?"
on the ruu,while s on the phone is doing many,many security checks wich prevent you from running any old ruu. youll need to find one for your exact build number or newer(numerically higher) in order for it to work.
ill see ifn i can find anything else out about the no sd card situation.
also,sorry for the late responses,was a busy weekend
not sure why youre getting the command error. typically its becasue youve typed something that fastboot doesnt recognize. try this,and post the results:
fastboot oem ?
make sure you get the "?"
on the ruu,while s on the phone is doing many,many security checks wich prevent you from running any old ruu. youll need to find one for your exact build number or newer(numerically higher) in order for it to work.
ill see ifn i can find anything else out about the no sd card situation.
also,sorry for the late responses,was a busy weekend
Thats ok, i totally understand
only managed a bit of time to have a look. heres my results from fastboot oem ?
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Technician>cd c:\android
C:\Android>fastboot oem ?
< waiting for device >
... INFOcommand list
INFOget_identifier_token
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOheap_test
INFOlock
INFOrtask
INFOtask
INFOenableqxdm
INFOgencheckpt
INFOlist_partition_emmc
INFOload_emmc
INFOcheck_emmc
INFOcheck_emmc_mid
INFOread_emmc
INFOget_wp_info_emmc
INFOsend_wp_info_emmc
INFOget_ext_csd_emmc
INFOget_sector_info_emmc
OKAY [ 0.016s]
finished. total time: 0.031s
looks like that command isnt there?
from what i could see on the xda post, he was having the same/similar trouble and the same result from fastboot commands, the error from fastboot oem eraseconfig which he fixed with the ruu update but he would be using a different ruu from mine as i used a different ruu for htcdev to work. If thats right?
Im learning so dont worry about telling me im completely wrong lol.
Thanks again for putting the time in for helping me sort this. so frustrating when everything ends up in an error
scotty85
Extreme Android User
Thats ok, i totally understand
heres my results from fastboot oem ?
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Technician>cd c:\android
C:\Android>fastboot oem ?
< waiting for device >
... INFOcommand list
INFOget_identifier_token
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOheap_test
INFOlock
INFOrtask
INFOtask
INFOenableqxdm
INFOgencheckpt
INFOlist_partition_emmc
INFOload_emmc
INFOcheck_emmc
INFOcheck_emmc_mid
INFOread_emmc
INFOget_wp_info_emmc
INFOsend_wp_info_emmc
INFOget_ext_csd_emmc
INFOget_sector_info_emmc
OKAY [ 0.016s]
finished. total time: 0.031s
looks like that command isnt there?
from what i could see on the xda post, he was having the same/similar trouble and the same result from fastboot commands, the error from fastboot oem eraseconfig which he fixed with the ruu update but he would be using a different ruu from mine as i used a different ruu for htcdev to work. If thats right?
Im learning so dont worry about telling me im completely wrong lol.
Thanks again for putting the time in for helping me sort this. so frustrating when everything ends up in an error
exactly! that command is not there,hence the error
the prollem with running the ruu is the fact that one doesnt exist
let me do some more digging and see what i can find...
scotty85
Extreme Android User
Oh you mean my ruu doesn't exist? Do you think someone has been messing around with this phone before I had it? Would it be a matter of installing a ruu that works? Thanks for all this
well,not so much that it doesnt exist,but moreso that it was never leaked and/or officialy released to the public,so we cannot find it.
the prollem is that without the ability to add root access,we cannot change some of the factors that prevent the phone from being able to run an older ruu. to complicate this matter,i couldnt even find an older ruu with your carrier number(the 161 in your build number) so the only option to run an ruu is:
1)lower main version
2)create gold card so we can run a different regional/carrier ruu
we may be able to find a temp root solution to accomplish #1 without the sd card,but even if you successfully create a gold card using another device,im not sure if the card will serve its purpose since the phone isnt reading it. the "gold card" simply tells the phone its ok to ignore the carrier id and model id checks the phone normally does.
if you have anotehr phone that you can use to make the gold card,then we can certainly give it a shot. otherwise,we are somewhat stuck unless we can find any ruu that has a build number x.xx.161.x
Well judging by the hassle were having to sort it, maybe an idea to pick up another dhd anyway (one with a broken screen etc) and swap the internals around, and trying again.Typical of me having one that's got a dodgy ruu lol. Although I'm still happy to carry on sorting this one out to find out how to get around this problem if u want to? As a guineapig. Wouldn't matter if it went wrong then.
Just to understand where the problem is, it wouldn't matter about the software number 3.13.161.5 if my phone wasn't usb bricked or whatever the fault is? It would just be a straight root? Just think after all the time, u especially, have spent on it, would be a waste not to see how far we have to go to get this problem sorted, for future reference if anything.
Scrap my last messages, I've sorted the ad card problem and I imagine the other problems are solved too. I pulled the phone apart earlier and pressed all the connections together, the felx motherboard connections and sd card/sim card board connections and put back together and put my sd card in and all works ok. Reads sd card without mounting or formatting so must've been a bad connection somewhere. Now where was I lol.
scotty85
Extreme Android User
awsome! glad you got the sd thing figured out.
just holler if you have more questions on the process. when we are done,you will be able to use any ruu to fix your phone if something happens I carried on last night, installed the supersu and did the aahk so now I'm rooted with s-off so glad I got it sorted. Now I suppose its installing a Rom next? Just one question, I used my SD to make the gold card, do I need to keep that safe? Or can I wipe it now? I took everything off it before I did the goldcard.
so glad I got it sorted. Now I suppose its installing a Rom next? Just one question, I used my SD to make the gold card, do I need to keep that safe? Or can I wipe it now? I took everything off it before I did the goldcard.
scotty85
Extreme Android User
you can do anything you with to the card now. you should now be supercid,so the gold card is un-needed. also- wiping the gold card wont make it a non-gold card. the part of the card that is written to with htc's image is not wipded when you formate it.I carried on last night, installed the supersu and did the aahk so now I'm rooted with s-off
when flashing a rom,you typically wipe data/factory reset in recovery. ral has one of the best rom flashing guides ive ever seen: http://androidforums.com/desire-hd-all-things-root/631481-4ext-recovery-how.html
congrats on getting it all sorted!
scotty85
Extreme Android User
while i do like sense 4,im realy not a sense fanatic,i generally prefer AOSP based roms. they have a smaller footprint in phone memory,and dont have the general complexity of stock sense based roms.
id look at the jellytime roms,and unoffical cm 10.1 nightlies,both of wich will be 4.2,and should be fairly stable.
other than that,just read the features,look at screenies,browse the last few pages of the dev thread,and see wich ones you might find interesting