Related
I'm pleased to present my ClockworkMod recovery for the HTC Desire HD (aka HTC Ace / HTC Spade). This recovery has been built and setup by me and is in no way endorsed buy Koush, so please don't ask him for support! I am still testing this recovery, so caution is advised and you use it at your own risk!
You will need the ENG HBOOT installed on your device to flash this recovery!
You can load recovery by powering on the device with 'Volume Down' pressed and selecting the 'recovery' option, by using 'adb recovery', by installing 'Quick Boot' from the Market or by installing 'ROM Manager' from the market.
Navigation in the recovery image as follows:
Volume Up / Down to move between options
Power key to select an option
Select 'go back' option to go back
Step by step install instructions
Download 2.5.1.2 r1 ClockworkMod Recovery for Desire HD - DOWNLOAD
Download fastboot if you do not have it already.
Turn off your phone and take out the battery. Unplug the phone from the PC / charger.
Replace the battery and turn the phone back on with 'volume down' held, then select 'fastboot' (using the power button).
Plug the phone into the PC.
Extract the fastboot zip file.
From a command prompt (at the directory containing these new files!) run 'fastboot-windows flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r2.img' (subsituting 'fastboot-mac' or 'sudo fastboot-linux' as required)
When this finishes, from the command prompt run 'fastboot-windows reboot' (again substituting 'fastboot-mac' or 'sudo fastboot-linux' as required)
Done!
The changelog is in the next post.
P
Changelog
18/Nov 2.5.2.1 r2
Updated to fix mounting /sdcard and /sd-ext via shell
17/Nov 2.5.2.1 r1
Initial Release
GJ, work fine
looking forward to trying this out when I get home from work.
Yeeeey, gonna try asap
can we flash straight over test recovery? No extra steps needed?
Same as above+ if not, could someone linux-literate explain us how to remove the test recovery please?
Ohh Thats sounds good to me.
I have the German hboot version, how can i flash this recovery?
Thanks
Works like a charm, no more 3 time scrolling to activate the power button.
Recovery seem to be working ok just like the test. But I still find it strange that I cant mount the SD card if I boot to the recovery using the Volume down and power method. The only way I can mount is to boot using the ROM manager. (By the way, I have the S-OFF and root).
That's weird, i'll look into that.
P
easier, than the RaiderX303 recovery, as it is not needed to go down 3 times to get back menu option and power selection.
I just flashed in fastboot, and it works perfect.
just flash it as you flashed the test recovery!
paulobrien said:
That's weird, i'll look into that.
P
Click to expand...
Click to collapse
The only thing you can mount is the system, data, and cache. Well the sd-ext (I dont think work, since I dont have ext partition on my SD card yet). I dont even know if we need to partition Ext with the HD rom? (Personally I dont think we need)
Anyway Paul...thanks heaps man...you are the man
Another Feedback:
Both Backup and restore tested working just fine....even restoring from the backup created by the test recovery just fine.
paulobrien said:
That's weird, i'll look into that.
P
Click to expand...
Click to collapse
'fastboot-windows.exe flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r1.im'
Shouldnt this be .img?? Edit post #1 plz.
xmoo said:
'fastboot-windows.exe flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r1.im'
Shouldnt this be .img?? Edit post #1 plz.
Click to expand...
Click to collapse
Obviously. Damn typos!
P
Don't we need S-OFF device in order to use fastboot commands?
That's the ENG hboot, and yes, it is needed.
jkoljo said:
That's the ENG hboot, and yes, it is needed.
Click to expand...
Click to collapse
I asked because it's not mentioned in the first post Some people might be confused...
How do I remove the test recovery please?
forelli said:
How do I remove the test recovery please?
Click to expand...
Click to collapse
Just overwrite with this one.
Or extract the original recovery from rom.zip (of the stock rom you using)
I recently unlocked my bootloader and rooted my phone leaving s-on cos of my hboot being 2.0002 or whatever. And need a step by step to installing a custom rom with s-on. I have installed cwm recovery but cannot access it. I spent 4 hours searching on Saturday, can some kind person explain how to do it?
Sent from my HTC Desire S using XDA App
Put the ROM in SDcard. Turn off fastboot and switch your phone off. Then, hold Vol down button and without releasing it, press and hold power button. Hold till you see a white screen, You'll be in Bottloader mode. Press Vol down to highlight RECOVERY and press power to enter recovery. You'll be in CWM (if you flashed it correctly)
In CWM,
Backup your current (stock) ROM in Backup and restore > Backup. It's not necesary, but recommended, as you may want to come back later
Go to Wipe/Format
Wipe Cache
Wipe Dalvik Cache
Format System
Format Data
Wipe Data/Factory Reset
Then, go back and select Install ZIP from SD Card > Choose ZIP from SD Card and choose your ROM. The ROM is flashed.
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen. Extract the boot.img from the ROM and do this - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Reboot. You're done
shrome99 said:
Then, go back and select Install ZIP from SD Card > Choose ZIP from SD Card and choose your ROM. The ROM is flashed.
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen. Extract the boot.img from the ROM and do this - http://forum.xda-developers.com/showpost.php?p=19071114&postcount=37
Reboot. You're done
Click to expand...
Click to collapse
Excellent. Couldn't have put it better myself.
Thank you so much!
However I installed cwm recovery from the rom manager but it doesn't show up when I go into recovery, I get a red exclamation point, I press volume up and power and it says something about e something recovery not found?
Also where do I put that command? That kinda stumped me too lol. Sorry for being a noob
Sent from my HTC Desire S using XDA App
OK, first you need to setup adb and fastboot. Use this guide - http://forum.xda-developers.com/showthread.php?t=1272595
Next, get CWM recovery and instruction on how to flash it here - http://forum.xda-developers.com/showthread.php?t=1122694
You'll be flashing it via fastboot. Instructions are there in the second thread. The command will be in fastboot too, along the same lines.
Feel free to ask if you have any other doubt. Everyone is a noob at some point
Sent from my iPod touch using Tapatalk
Thank you so much. I will be doing this as soon as I can access my laptop again. Lol.
Sent from my HTC Desire S using XDA App
How'd it work out? Flashed succesfully?
Sent from my iPod touch using Tapatalk
Currently working at the other side of the country. I'll have to wait until thursday to flash it.
Thank you for the follow up though. It's very appreciated.
Sent from my HTC Desire S using XDA App
Sorted thanks guys.
Uppy said:
Hi again, i'm really sorry for being annoying but i dont get this bit.
I extracted android-win-tools to C and put the recovery image in the android-win-tools folder but what am i navigating to? c:\android-win-tools? Its specifically 4. that I'm stuck on.
This is slightly embarrassing!
this was so much easier on my Blade lol.
Click to expand...
Click to collapse
No need to be embarrassed buddy.
What point no. 4 means is that you need to move the file you want to flash (recovery.img in this case) to the folder that contains your adb files (android-win-tools, or whichever folder that you have extracted the android-win-tools that you downloaded). The rationale behind this is that when you enter the command fastboot flash recovery recovery.img, the fastboot will look for recovery.img in its default folder (android-win-tools, or whichever folder you've extracted the adb files to).
So here's what you need to do. For example, if you downloaded the adb files and extracted them to a folder named, let's say, xxxx, which is located in your C: then you need to take the recovery.img file and copy-paste it to the folder xxxx.
Before starting any of the procedures outlined here, first make sure adb can detect your device. (adb devices... sound familiar?)
Now boot phone into fastboot.
Now enter the following commands at the cmd prompt:
C:\Users\UPPY(or whatever)>cd\
Now you'll get the following:
C:\>
Next, you need to enter:
C:\>cd xxxx
You'll now get:
C:\xxxx>
Finally, enter the following:
C:\xxxx> fastboot flash recovery recovery.img
You should be done. I know the above looks over simplified... but i'm just trying to be extra nice here
I hope that clears your doubts.
Done! Thank you for all your help, you made it so much easier for me. its all up and running now.
Uppy said:
One last question though, where do i extract the boot image, do i put it in the root of my sd card and finally if thats the case what is the exact thing i type?
Click to expand...
Click to collapse
After you've flashed your custom recovery, boot into recovery and choose install from sd card, select zip from sd card, then navigate to your rom.zip file, and confirm to flash it using the recovery (on your phone)
But since you've unlocked using HTCDev, this will not flash the kernel as the boot is still locked. You have to bypass this by flashing the kernel manually using fastboot, otherwise you'll be stuck at the white HTC splash screen (Oh! how i hate that screen!!)
The kernel is contained in the boot.img.
The boot.img is contained within the zip file of the ROM you want to flash. So when you open up a ROM.zip (for example Reaper_v1.6.zip) with winrar, you'll see various files inside. Extract the one called boot.img. This is your kernel. Copy-paste this boot.img in your adb folder (like in the previous post)
To flash it, since you've already set up fastboot, just do what you did for flashing recovery.img, and follow the instructions i gave you exactly the same way, except the last part, where instead of recovery.img, you need to type:
fastboot flash boot boot.img
now type adb reboot, and boot into your shiny new custom ROM!!
You're done.
I'm getting an error when i try to connect to wi-fi, it just says error, what have I done wrong? grrr.
I think i didnt register the 3.4 boot image, will report back in a minute.
-edit- yeah i typed the command wrong thats all.
Uppy said:
Done! Thank you for all your help, you made it so much easier for me. its all up and running now.
Click to expand...
Click to collapse
Happy to help
shrome99 said:
Since you are hboot 2.00.002, you have to go through an additional step after that, you need to flash the kernel that came with the ROM, or you'll be stuck on the white HTC Screen.
Reboot. You're done
Click to expand...
Click to collapse
I have first read the install instructions from MIUI (saying: full wipe, flash rom) and now I have exactly what you have warned: Phone doesn't proceed, it ist stuck on the white HTC Screen.
UPDATE:
I was afraid of taking out the battery, as this may cause problems, and vol up + vol down + power just rebootet into white htc screen. The only way was indeed pulling the battery (after the vol up vol down power-reboot-gap). Then I could enter into the bootloader the regular way (vol down + power), and change to fastboot, and flash boot.img. Everything is fine now!!!
No-New-Phone said:
I have first read the install instructions from MIUI (saying: full wipe, flash rom) and now I have exactly what you have warned: Phone doesn't proceed, it ist stuck on the white HTC Screen.
UPDATE:
I was afraid of taking out the battery, as this may cause problems, and vol up + vol down + power just rebootet into white htc screen. The only way was indeed pulling the battery (after the vol up vol down power-reboot-gap). Then I could enter into the bootloader the regular way (vol down + power), and change to fastboot, and flash boot.img. Everything is fine now!!!
Click to expand...
Click to collapse
Was already typing a solution for you, but if you can solve a problem by yourself it's even better ;-)
Sent from my Desire S using XDA App
I'm glad this thread is helping more people than just myself. I'm not exactly a Technophobe but this was far more complicated than rooting my blade, Europa or racer or indeed writing the CSS files I used back on windows mobile 6.5 on my old touch 2.
I certainly needed my hand held through the first time doing this.
Sent from my HTC Desire S using XDA App
My first post here so go easy on me
Anyway, I got an Evo Shift, I do not know its history, but its stuck in some sort of a boot loop, on the white screen with green HTC logo.
Things I know:
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT -0.99.0001
RADIO - 1.08.01.0111
Clockwork Recovery v5.0.2.0
I did not get an SD card with it, no recovery image.
RUU says version is 2.77.651.3
I know the S-on is a problem.
I have tried all 4 of the RUU versions - failed.
Tried RUU with Gold Card - failed.
Tried rom.zip from each RUU renamed to PG06IMG.zip - failed.
I have tried custom roms of all sorts, every methoud I found - failed.
Where do I go from here? Is there a way of manually flashing all the partitions from a ROM.zip file via fastboot? Is there a way of disabling a version check in RUU? Or is there a way of disabling MD5 sum in Clockwork so I can try flashing a restore image from another Shift?
I have spent 3 days on this phone, and I would hate to admit defeat, so I am reaching out to the genius minds here. Thanks in advance!
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
gzetski said:
Okay, I fixed it. Please delete the thread. Unless someone wants me to do a write up on how I did it in case someone else fubars their phone.
Click to expand...
Click to collapse
Did you unlock the bootloader with htcdev tool?
The bootloader was already unlocked when I got the phone.
Thanks for this. I will test it and add it to my guide.
VICODAN said:
Thanks for this. I will test it and add it to my guide.
Click to expand...
Click to collapse
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Place misc.img and PG06IMG.zip on sdcard using windows explorer or "adb push /sdcard/file.xxx" via usb
Click to expand...
Click to collapse
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
And BTW, I am now rooted, but with S-ON... Grrr. Superuser works, rom manager works, pretty much anything requiring root access works. I have rebooted the thing like 20 times to see if it goes away, and its sticking just fine, but I am afraid of trying to flash a custom rom with the S-ON.
All attempts to flash ENG bootloader fail, both by flashing via fastboot (all my MD5 sums match, the process is flawless from start to finish, when I reboot, still same bootloader with S-ON), or using ShiftRR.
Any ideas?
gzetski said:
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
Click to expand...
Click to collapse
shift-rootkit.rar
Read the prereqs.
Okay, got it.
Too many things floating through the intertubes with similar filenames.
gzetski said:
Okay, got it.
Too many things floating through the intertubes with similar filenames.
Click to expand...
Click to collapse
Yep, I've finally got the thread pinned, and I created 2 videos on how to do it the right way. They are uploading to youtube now.
S-off?
Did you ever figure out how to get S-Off? I seem to be right where you were a few days ago with the phone appearing to have root, but S-on still there. I'm also running HBOOT -0.99.0001 and unlocked via the HTC Dev tool. Is there anyway to downgrade to .93 or to turn S-Off. My ultimate goal is to get Cyanogenmod on this Shift.
Thanks in advance!
I have not messed with the phone for a few days. I am gonna try to go back to 2.3.4 then downgrade again. Most likely what I ended up having is a bunch of borked files, hopefully the latest RUU will fix that. This was really intended as a brick fix and not a legitimate 2.2 downgrade. When I mess with it, I will post the results for you though.
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
MTsol said:
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
Click to expand...
Click to collapse
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
drob311 said:
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes Sir . Been there done that. Had a HERO that somehow got " water damaged " after it was BRICKED .
signature verify fail
gzetski said:
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
Click to expand...
Click to collapse
First, I want to thank you for posting this even though it hasn't yet worked for me. I'm in essentially the same position you started in. Phone will not boot past the green-on-white HTC logo. I boot to recovery and can get to fastboot mode with USB detected. I flashed recovery.img and boot.img with no problems, but trying to flash dzdata onwards gives me the same error every time: "(bootloader) signature checking... FAILED (remote: signature verify fail)" and will not flash the other components from ROM.ZIP.
Any thoughts on how to proceed? This thing is rapidly approaching permanent brick status.
You need to unlock your bootloader and then flash the rom. zip files through fastboot
The "failed" message means that your bootloader is locked
to get S-off the easiest method is to downgrade your device from 2.3.4 to 2.2 and then FOLLOW THE SAME INSTRUCTIONS AS OBTAINING S-OFF ON 2.3.4. i had the same issue when i first unlocked my Shift bootloader.
please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000
taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Malybru, i do have a router but my wifi wont turn on so i cant connect to it.
T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves
ta gane shp, this is a good place with good people
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.
Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.
malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though
Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Hi,
i came to the screen install form zip on sdcard
but then it starts installation
and shows : installation aborted
now i cant start the phone i always get tothis screen
with the red text this build is for ....
what can i do?
edit: now i am again there where i can install zip from sdcard, but now it doesnt recognize the sdcard. What can I do, because i the phoen does not take a microsdcard where I could put a new rom.
how can i get access to the internela storage now wihtour a os?
How did this happen ? Selecting a ROM to flash in recovery cant really cause so much damage if it fails. They usually fail because of a md5 mismatch or something.
try to mount the sd card and you can use adb to push files to it..
you could also try a full wipe..
I did several things. I rooted and unlocked the device
and now it does not boot.
Everytime I tired to flash leedroid or stock rom with choosing install form zip
installation get aborted.
I am only able to get into the boolloader and into the recovery.
how can i restore the phone?
wipe and recovery is not possible i always end in this screen
with the red text.
edit: i think i try to get into booloader and copy another file version with adb to the sd card and hope it was a download error.
but why the hell then did both the leedroid 'AND the stock rom fail?
did you flash the boot.img BEFORE flashing leedroids ROM ??
If not i suggest trying that, If that fails, Just run an RUU and start from the beginning
Thanks for the Idea,
my problem is that i cant get access to the memory wihtout a working rom
on it And now i also dont get into the recovery CWMS.
I thouzhg power+vol up would do it but it doesnt work
I think i destroyed my brand new phone.
but thanks for helping.
It's not broken.
Try Power + Vol. down. Possibly you need to retry this several times to get into the bootloader.
its not destroyed dont worry..
Run an RUU and all will be good again. Whats your CID ?
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Click to expand...
Click to collapse
You run it from your Windows desktop. Download your appropriate RUU here for example (as it takes a loooooong time).
Connect your phone to your computer via USB.
Double Click the RUU-file.
Answer the Questions and the update will start.
Remember: Your device will be reset to factory default and your data on sd card will be gone so.
Edit: You will still have to start it with power + vol. down buttons pressed (as far as I remember).
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
Click to expand...
Click to collapse
To get into the bootloader try this.
Press and hold volume down, then power. Hold both down together for 5 secs, let go of the power button then press the power button several times. This always works for me.
If this works then your phone is easy to fix.
Maybe you could try to reflash the boot.img from leedroid via fastboot.
Then flash a proper recovery.img via fastboot (I use clockworkmod)
As I heard you could then push the rom.zip via Adb the sdcard while in recovery. Last step would be install zip from sdcard.
Sent from my HTC One S using XDA
Have you installed supersu via install ZIP from sdcard? I think this needs go be installed before installing the Rom. I Don't Know it exactly. But like this it worked for me when coming from stock rom. Thats how it worked for me:
1. Unlock bootloader via HTCDev
2. flash recovery image via fastboot
3. Install SuperSU from zipfile in recovery
4. Flash boot.img from Leedroid
5. Install Leedroid from sdcard
So maybe you missed one of the steps.
Sent from my HTC One S using XDA
to get CID go into fastboot and type in cmd window ''fastboot getvar cid''
If your phone is branded, you will need that branded RUU, So i assume you will need o2 Germany RUU
Reflash recovery in fastboot, should give you access to sdcard back.
Sent from my HTC One S using xda premium
i did the same thing to my one s yesterday... followed all the steps for leedroid n got same frustration u have...
theres a nandroid file in the dev section... fastboot the boot.img and the recovery.img
ya phone WILL boot back up
ok guys ty for cheeering me up.
i wil try it with a ruu, where can i find a ruu for my htc one s.
the link in the previuos post ist offline.
i think it was 1.78.407.x when i looked the last time in my handy.
thanks
so my cid is
C:\Android\android-sdk\platform-tools>fastboot.exe getvar cid
cid: O2___102
finished. total time: 0.003s
Like i said it is a O2 i hope this helps finding the ruu
well check the Shipped ROM thread.. If its not there you can ask the OP Football if he has it or can get it..
Some RUU's cost $13 so if you know someone else who wants it, you could split the cost ?
so far, now am in the recovery flash but it is the same
count mount /sdcard
how can i put a file onto the sdcard when i have no access?
partionoing sdcard doesn't help
i was looking for this boot.img and recovery.img which was posted before
i dont find it can someone link me to it if he knows what was meant?
thanks
edit: i was desperate and tried:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
but the second order was not successful
ist there another way to fix this usb brick
and to get access to /sdcard
new edit: now i write also in the help thread (noob friendly) i hope that is ok.
Did you already try this
http://forum.xda-developers.com/showthread.php?t=1667929
Or this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using XDA