Database Info

Using fastboot without ENG or S-OFF

As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.

Thankyou!
Just wanted to say I'm the guy that messed up his phone and needed Jason's help. He got me into a Sense ROM and was able to then get clockwork running again and restore my Nand. Really save my bacon.
Also, I've followed your advice. I now have a rooted AND S-off hero running Gingerbread.
Thanks again!

jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
Really? Thanks for the Info... Helpful, and Good to Know!!
Sent from my Hero using XDA App

wow, this is valuable information. couldnt this be put into the wiki or something? i tend to go to the wiki often, but i dont know how to properly edit a wiki.

jasonmaloney said:
As many of you may know, you are locked out of using fastboot commands unless you have an engineering SPL. But I made a little discovery last night about how the HTC Rom Update Utility actually installs ROMs. Turns out it uses... fastboot!
Here's how it works:
With phone powered on, do "adb reboot bootloader" to enter fastboot.
-OR- With phone powered down, power on phone while holding VOL DOWN. From there press VOL UP to enter fastboot.
Run the command "fastboot oem rebootRUU"
Now you should see a black screen with a silver HTC logo. Look familiar? This is the screen you'll see when using the RUU.
From here you can re-flash an original HTC ZIP, with "fastboot flash zip filename.zip", where filename is the name of your signed HTC image.
As an added bonus, if your phone is S-OFF (even if you're not using the ENG SPL), you can flash ANY fastboot-compatible ZIP from here, signed or not.
When you're done, "fastboot reboot" will boot the device.
Found this by accident trying to help someone on IRC who had screwed up both their ROM and recovery somehow. All they could get into was fastboot/hboot, and they were S-ON.
Click to expand...
Click to collapse
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.

Houndog101 said:
I have a similar problem with my CDMA hero. I tried the "Run the command "fastboot oem rebootRUU" and I get
<bootloader> [ERR] command error !!!
What am I doing wrong ? Probably everything.
Thanks.
Click to expand...
Click to collapse
Which bootloader version do you have, and where did you get the fastboot binary?

jasonmaloney said:
Which bootloader version do you have, and where did you get the fastboot binary?
Click to expand...
Click to collapse
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..

hey Jason here's some background on his problem, I linked him this thread, hopefully you have more patience than me, but you know me, I don't really and I'm a dink http://forum.xda-developers.com/showthread.php?t=984688

Houndog101 said:
HBOOT-1.47.0000 (HERO20000) is this what you mean ?
I got the fastboot off this site with SDK tools Android SDK updater ,revision 10. Is this what you need ?
Thanks for helping me..
Click to expand...
Click to collapse
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.

jasonmaloney said:
Not sure why it would be giving you issue. Make sure you're in fastboot mode and not hboot mode. You should see "Fastboot USB" on the screen if memory serves.
Alternatively, try the copy of fastboot.exe on my site. I pulled this directly from HTC's Rom Update Utility, so it might work better.
Click to expand...
Click to collapse
Jason, Thanks a million times, That was a problem, I d/l your fast.boot and it got me to the Black with silver htc screen. I'll see what I can do from here. Just want to get it to where I can boot into recovery.. Thanks again for helping me.

I've followed all the instructions but with a slightly different problem. I can't get to bootloader at all, but if I plug my hero to my pc and turn it on then it will say "fastboot usb" in a red rectangle at the top left, but is still otherwise the white HTC screen. when I do "fastboot oem rebootRUU" the terminal says okay, but the phone reboots into the same state instead of the black and silver screen I am hoping to see. Is it a brick or is there another option?

I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.

beand1p said:
I get to where I want to load the image and it says "error: cannot load 'HERCIMG.zip'". Is this because it is not signed. I have the zip on the root of my sd card. I'm trying to install just a stock ROM and unroot so I can sell my phone.
Click to expand...
Click to collapse
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Yea It's Me Again With the
Modified Hero

laie1472 said:
If you look in the hero dev section you can find a thread called ruu in zip format. It will take you back to stock all the way no recovery no nothing just like fresh out the box. I've used it myself when I couldn't flash sense roms. And it works great. I would link you but I'm mobile. You might have to dig a little but its worth it. Good luck.
Click to expand...
Click to collapse
I get the same error even with that zip. I am S-OFF also. I have HBOOT-1.47 with radio 2.42.01.04.27.
I've tried almost everything to unroot and get back to stock. I am about ready to throw in the towel.

Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]

dpeeps74 said:
Why not just leave it rooted and put a stock rooted rom? Seems at that point you could remove superuser permissions somehow if It's that important for them to not have root. That would essentially take away root for all intensive purposes I would think. I'm just thinking out loud here and definitely you may want another opinion, but having root on the phone won't really cause them any real problems as long as they have a stock rom. They can still activate it, it still has the same menu options for a hard reset...maybe I'm missing the point other than you should be able to do what you're trying?
[dpeeps74]
Click to expand...
Click to collapse
All the stock RUU's I have tried always give me the RUU Error [140]: BOOTLOADER VERSION ERROR
EDIT
I was able to RUU after using this method: http://forum.xda-developers.com/showthread.php?t=843544

I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.

zbach said:
I'm currently hitting a roadblock with this. Whenever i try the fastboot update zip command, and add the filename, i get an error saying that it cannot load said filename. i have no clue what i'm doing wrong.
Click to expand...
Click to collapse
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.

jasonmaloney said:
The zip file should be on your computer, not your phone. Make sure to specify an absolute path for the zip file if the fastboot.exe file is not in the same folder as the zip file.
Click to expand...
Click to collapse
I have the zip file in the android file along with the fastboot.exe program. I still get a "Cannot load" error message

thank you x100000.
I couldnt flash the original ruu because of the weird bootloader issue, but this worked like a charm and i was able to flash with a .zip of the ruu.
Thanks again.

ADB Walkthrough

So I got this help in the CM Q&A but while I've rooted man devices (mostly with oDin and one-click utilities) I've never used ADB and now I'm wanting to go from a sense to AOSP ROM and can't find active links to ADB or tutorials other than (type something here), youtube hasn't been help either, can someone help e out? I had a hboot 1.85 XL so I had it easy when I rooted.
LINKS
3.18 RUU Downloaded
S-Off Thread: http://forum.xda-developers.com/show....php?t=2155071 open in tab but the instructions aren't user friendly
Downgrade Touchscreen: http://forum.xda-developers.com/show....php?t=2159863
TWRP Recovery: http://goo.im/devs/OpenRecovery/evita downloaded
***openrecovery-twrp-2.3.3.1-evita.img or 2.3.3.0 are recommended at the time of this post***
OPTIONAL- Remove red text from splash screen: http://forum.xda-developers.com/show....php?t=2156368
INSTRUCTIONS
Thanks to @InflatedTitan for this breakdown.
While waiting for the RUU to download...
1. Download the 2 files for s-off and place in adb folder.
2. Download the recovery of choice and put in adb folder.
3 (optional) download the remove red text file and put in adb folder.
4. You'll have to downgrade touchscreen if you want to use aosp *SEE NOTE BELOW*. Head to original dev sticky to download files from h8rift. Put those in adb folder
_________________________________________
1. S-off! Make sure you confirm in bootloader (it usually works easier from a sense rom btw.) 4.2.2 roms need updated adb but it may work.
2. When you ruu, it doesn't touch sdcard. But I would quickly mount and backup your pics and whatnot just in case.
3. Enter fast boot. Run the ruu on the computer. It'll bring you back to 100% stock.
4. Once you up and running, enter fast boot again and send twrp. (Instructions below, insert whatever recovery image you're pushing)
Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
5. I recommend to get rid of the ugly ass red text on splash. Follow Liam's thread to rid it.
6. While in fastboot go ahead and downgrade touchscreen following h8rifts instructions.
7. Now you're golden to flash anything you want :thumbup:
*Note as of the 06/26 Nightly, you do NOT need to downgrade your touchscreen. However if you encounter any touch-related problems using TWRP 2.3.3.x, you should flash the downgrade in fastboot to move on. I'd recommend 2.5.0.0 on the latest touchpanel firmware. It works for me but if you run into trouble, downgrade the touchscreen and flash the recommended TWRP recovery.

ADB is a command line shell for accessing your phone remotely using linux commands. So many linux command line commands will work within adb. To become an ADB master, use linux command line.
As for downloading ADB and fastboot...
https://dl.dropboxusercontent.com/u/19685555/fb-adb.zip

I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Edit after hours searching came across helpful info, but after changing the directory and putting int adb reboot bootloader i get "error device not found" when my phone is connected, any clue?

USFguy said:
I guess I'll stick to sense based ROM's because that wasn't helpful but thanks.
Click to expand...
Click to collapse
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?

exad said:
eh? What is it you want to know?
Here's a link to adb breakdown and commands? I googled "adb commands" and it was the first link...............
http://forum.xda-developers.com/showthread.php?t=2141817
Is this what you were looking for?
Click to expand...
Click to collapse
"error: device not found"

USFguy said:
"error: device not found"
Click to expand...
Click to collapse
this is what i got....

USFguy said:
this is what i got....
Click to expand...
Click to collapse
is your phone plugged in with the rom booted and USB debugging turned on?

exad said:
is your phone plugged in with the rom booted and USB debugging turned on?
Click to expand...
Click to collapse
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish

USFguy said:
yeah, i uninstaleld HTC sync then went into device manager and updated the driver and it worked, I'm s-off and now waiting for RUU to finish
Click to expand...
Click to collapse
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'

USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.

exad said:
That means you're typing the filename wrong. Type the first few letters and then press tab. It will auto complete the file name for you.
Click to expand...
Click to collapse
i'm actually getting the no devices connected again since the ruu finished running.

Press and hold power until the phone shuts off then press and hold volume down until the bootloader comes on then try again
Sent from my HTC One X using xda app-developers app

USFguy said:
current issue is in regards to "Quote:
fastboot flash recovery openrecovery-twrp-2.3.3.1-recovery-evita.img
"
I have openrecovery-twrp-2.3.3.1-recovery-evita.img in my c:\fb-adb folder and running the command from there but it's saying "error: cannot load 'openrecovery-twrp-2.3.3.1-recovery-evita.img'
Click to expand...
Click to collapse
Twrp 2.6 works great. No real reason for 2.3.3.1 anymore but nostalgia.
Sent from my HTC One XL using xda premium

[Q] Stuck in the red letters screen on my HTC One X

hello my friends, i need your help to fix my celphone, when i turned on the phone doesnt boot up always saty stuck in the screen with the red letters, i tried changing the kernel, i tried to install another ROM but always stuck in the same point, i wiped the cache, the system even the SD card and doesnt work,
Anyone can help me?
------Updated-----
according with some posts that i read i need to flash the RUU but i tried downloading the stock att ruu 2.20 but doesnt reconize any phone conected exists a way to flash directly over the TWRP?or maybe i missing something and because of that doesnt detect my celphone?

Reboot the phone and hold volume down while it's rebooting, this will take you to the bootloader, from there you can enter recovery and restore a backup or flash ROM.
What ROM were you on and what kernel did you flash?
Sent from my Evita

timmaaa said:
Reboot the phone and hold volume down while it's rebooting, this will take you to the bootloader, from there you can enter recovery and restore a backup or flash ROM.
What ROM were you on and what kernel did you flash?
Sent from my Evita
Click to expand...
Click to collapse
thanks for your help, i tried to flash the JB 4.22 plus sense 5 but i think my problem is the RUU because even if i flash the Rom still stuck in the same point when i tried to turn on the celphone, do you know how i can flash the RUU?

What are your bootloader details please, just the first five lines.
Sent from my Evita

timmaaa said:
What are your bootloader details please, just the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
Tampered
Unlocked
Evita put ship s-on RL
hboot- 1.14.0002
Radio-0.19as.32.09.11_2
openDSP-v29.1.0.45.0622
eMMC-boot

You're s-on so did you flash the boot.img via fastboot after flashing the ROM?
Sent from my Evita

timmaaa said:
You're s-on so did you flash the boot.img via fastboot after flashing the ROM?
Sent from my Evita
Click to expand...
Click to collapse
eehm nop, so how i do that? from where i can get the boot.img and how can flash via fastboot?
Sorry for my noob questions

The boot.img can be found in the root of the ROM zip, unzip it on your pc and you'll see it straight away. You then need to copy the boot.img into the folder where adb and fastboot are. Then open a command prompt from within that folder (shift + right click anywhere in that folder, select open command prompt here), put your phone into bootloader mode and connect it to the pc, then issue this command in the command prompt:
Code:
fastboot devices
It should return your device serial number, this confirms that you're connected properly. If it doesn't return the serial number you need to work out why. If it does return the serial number you can issue this command:
Code:
fastboot flash boot boot.img
Now you can enter recovery on your phone, flash the ROM, and reboot the phone. Now it should boot up.
Sent from my Evita

timmaaa said:
The boot.img can be found in the root of the ROM zip, unzip it on your pc and you'll see it straight away. You then need to copy the boot.img into the folder where adb and fastboot are. Then open a command prompt from within that folder (shift + right click anywhere in that folder, select open command prompt here), put your phone into bootloader mode and connect it to the pc, then issue this command in the command prompt:
Code:
fastboot devices
It should return your device serial number, this confirms that you're connected properly. If it doesn't return the serial number you need to work out why. If it does return the serial number you can issue this command:
Code:
fastboot flash boot boot.img
Now you can enter recovery on your phone, flash the ROM, and reboot the phone. Now it should boot up.
Sent from my Evita
Click to expand...
Click to collapse
Ok, let me try ill keep posted

It works !!!!!1
Thanks so much for your help now i will update the firmware with most recently one

fjej78 said:
It works !!!!!1
Thanks so much for your help now i will update the firmware with most recently one
Click to expand...
Click to collapse
Glad to see it worked
PS. If someone helps you on XDA, press the thanks button :thumbup:
Sent from my Evita

[Q] boot loop cannot get PC to read device

Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?

sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?

sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:

tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?

sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.

tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks

sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard

tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere

sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.

tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111

sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img

tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip

sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.

Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:

Cyanogenmod update problem

After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.

chmiela1991 said:
After update to cm-11-20140413 and instal newest kernel (Sultan-kernel-Pure-v1.4.0) my htc stuck at cyanogen loading screen. I don't know where's the problem. Maybe someone know the solution.
Click to expand...
Click to collapse
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?

rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
Thanks flashing new boot helped

rzr86 said:
probably your kernel is the problem
try to flash the boot.img of the rom via fastboot command
fastboot flash boot boot.img
by the way are you on S-ON or S-OFF?
Click to expand...
Click to collapse
I have the same problem, but i cant find the command in the bootloader

Noam_Nissel said:
I have the same problem, but i cant find the command in the bootloader
Click to expand...
Click to collapse
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter

rzr86 said:
actually you type the command from pc
connect your device to pc in fastboot mode(in the hboot screen should say fastboot usb)
extract the boot.img from the rom and place it in your adb/fastboot folder
then open a cmd window in that folder and type the command
press enter
Click to expand...
Click to collapse
i don't fully understand what to do, can you be more detailed?

Noam_Nissel said:
i don't fully understand what to do, can you be more detailed?
Click to expand...
Click to collapse
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder

rzr86 said:
ok
boot your device to the bootloader and select fastboot
then connect it to pc
now in your pc navigate to the folder where you have adb and fastboot(i assume you have installed sdk tools)
in that folder press shift + right click
you will see an option open a command window here
then a black window will appear
in that window type the command and press enter
but don't forget first to place the boot.img to the adb/fastboot folder
Click to expand...
Click to collapse
i have this problem agian, and it doesnt help this time

Noam_Nissel said:
i have this problem agian, and it doesnt help this time
Click to expand...
Click to collapse
what kind of problem and what did you do now?

rzr86 said:
what kind of problem and what did you do now?
Click to expand...
Click to collapse
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem

Noam_Nissel said:
every rom im installing is getting me into bootloop, i've tried to install from revcovery and from fastboot, and it always the same problem
Click to expand...
Click to collapse
i replied in the other thread

Does S-on and S-off matter for this issue?
Hi,
I am facing the same issue, my Sensation z710e is stuck in Cyanogenmod boot logo. following are the details.
bootloader unlocked
s-on
rooted
cwm recovery installed
tried latest CM10 for pyramid devices
I didnt try 'fastboot flash boot boot.img' command yet but i would like to know if s-on matters, my device is already rooted with cwm recovery.

I am having a similar issue as well. I have followed the instructions in this thread [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 18, 2014]. I have followed all the steps including doing a full wipe, flashed the ROM zip, gapps zip, and the aroma installer for the flash kernel several times with the same result. My screen keeps getting stuck on the white HTC loading screen.
Currently I have restored my phone to my previous ROM using a backup through 4ext recovery (v1.0.0.6 RC2). My HTC Sensation 4G T-mobile is unlocked and rooted with s-on. I have smartflash enabled on 4ext and my ROM is currently stock android 4.0.3. I did search the above mentioned thread for similar issues and a potential solution but none of the things I tried worked.
I would appreciate any help on how to fix this problem. If you need additional information I would be glad to provide it.

Tried another re-install today and everything worked fine, I guess the 5th time is the charm? I still don't know why it didn't work the other times, I did the exact same thing each time.