Develop Bugs

Desire stuck on fastboot mode, cannot flash recovery

My desire is stuck on fastboot mode,
it is S-OFF
bravo pvt1 ship s-off
riff: 0.93.0001
microp-051d
radio-4.06.00.02_2
Made goldcard, but all the PB99IMG.zip I put on the sdcard are reported as INVALID.
try via fastboot, but I allways get the same error as it wasnt connected.
when I type: fastboot devices I get the device sn but not the $ to keep sending commands so every command I send reports the same error.
try the android flasher, nothing.
used the search button, read a lot but still cannot get the fastboot flash recovery recovery.img to work
run out of ideas, need some help please.

Please specify exactly which error is given when you execute "fastboot flash recovery recovery.img"(recovery.img being your recovery image).
Because if you've got fastboot commands working you should be able to flash.
Do your hboot say alpharev anywhere?

C:\Documents and Settings\Usuario>fastboot devices
HT05PPL02709 fastboot
C:\Documents and Settings\Usuario>cd\sdk
C:\sdk>cd android-sdk-windows
C:\sdk\android-sdk-windows>cd tools
C:\sdk\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4216 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
I read this means no proper comunication in fastboot.
it is the clockworkmod recovery and the RA recovery...
both give me the same error... I cannot use any fastboot commmands.
they all end as previously shown.
tryed android flasher 1.8.0, selected recovery.img.... got "could not find part of the path data\recovery.img"
everytime, with every recovery.img I use.
this is all the lines on the hboot screen:
BRAVO PVT1 SHIP S-OFF
RIFF: 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
Aug 10 2010,17:52;10

You can flash a recovery with the following command over adb or terminal emulator if your s-off. I know cm7, amonra recovery and rmd recovery support this, others...probably.
su
flash_image recovery /sdcard/recovery.img
I use it all the time.
Sent from my HTC Desire using XDA App

it doesnt work because I am stuck on fastboot.
adb shell do not work for me.
is there anything I should do after "fastboot devices" command?
I am using a xtc clip created goldcard.
should I flash a new hboot or a new radio?

hugmax said:
it doesnt work because I am stuck on fastboot.
adb shell do not work for me.
is there anything I should do after "fastboot devices" command?
I am using a xtc clip created goldcard.
should I flash a new hboot or a new radio?
Click to expand...
Click to collapse
[enter]
fastboot flash radio radio.img [enter] {wait the ok message}
fastboot reboot-bootloader [enter] {wait the reboot}
fastboot flash recovery recovery.img [enter] {wait the ok message}
fastboot reboot-bootloader [enter] {unplug the cable and wait the reboot}
from the bootloader menu go into recovery and flash the rom u want
ensure the img file are in the same directory of fastboot.exe
how u got s-off? with alpharev or an xtc clip? the xtc clip doesn't give u fastboot flash commands i think, then u should try run revolutionary.io i think, after u can flash recovery etc

s-off via xtc-clip.
will try the commands... should I pick any radio.img?

hugmax said:
s-off via xtc-clip.
will try the commands... should I pick any radio.img?
Click to expand...
Click to collapse
first run revolutionary, it will give u a patched s-offed hboot..this hboot will allow commands like "fastboot flash..."
about the radio, u can use the latest in this thread (extract the img from the zip) be careful flashing it..wait it to finish..don't remove battery or something like that

if I run revolutionary all I get is "waiting for device"
D:\Docs\Celulares\htc\desire\revolutionary-0.4pre4>revolutionary
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Click to expand...
Click to collapse
if I am stuck on fastboot and xtc clip doesnt allow any fastboot command... and unrevoke/revolutionary dont recognize my fastboot device...
what am I suppose to do now?
I get FAILED(status malformed.... ) with every single fastboot command.

hugmax said:
if I run revolutionary all I get is "waiting for device"
Click to expand...
Click to collapse
uninstall htc synch at all, and other programs that can interferr
install this fastboot drivers
run revolutionary, plug the phone in fastboot mode

Have you try to unroot with a PB99IMG?
Sent from my rooted and s-offed HTC Desire.

andQlimax said:
uninstall htc synch at all, and other programs that can interferr
install this fastboot drivers
run revolutionary, plug the phone in fastboot mode
Click to expand...
Click to collapse
I installed the drivers, it says
Android Composite ADB Device
version 2.0.10.12
date: 11/08/2009
Shouldnt it says 3.0?
anyway... it didnt work... I will try to delete/uninstall everysingle htc driver in my pc or try on another fresh laptop with no htc drivers.

Again here,
new pc, Windows XP SP3 with no HTC/Android software.
Intalled the HTC 3.0 and the phone was not recognized
should I try on win7?
that is going to be my next test

follow up: tryed on win7, htc 3.0.0 drivers didnt work. phone is not recognized.
I know it was working fine... tryed to flash it and it died... resurrected with RIFF Box but cannot flashed with any firmware.

i tried to flash a new hboot with android flasher, but it just reboot and nothing happened.

did you check md5 sum btw? just with the error saying invalid and 1 byte...
So you can still access fastboot but cant flash? hmmm...
I would personally delete all your android sdk and redownload it all and set up adb fastboot again, it does sound like a driver problem

timothio said:
i tried to flash a new hboot with android flasher, but it just reboot and nothing happened.
Click to expand...
Click to collapse
What did you expect? Its requires few seconds to flash it..If u saw the success message and u see the new hboot on the bootloader screen, thats all

ok,
now I went to find a PB99IMG.zip with the same radio.
copied it to the sd
power on the phone
and I got this:
Uploaded with ImageShack.us
but it is just sitting there, waiting for something to happen?
I tryed to select something but it doesnt respond to anything... can it be that the touch screen is faulty? because it was working at the beginning.
I did redownload everything again.
java sdk and everything
it doesnt work with the htc 3.0 driver, only with 2.0

[Q] Do I need revolutionary if I am already S-Off?

I bought a desire (used) and upgraded it from official Froyo to official Gingerbread via RUU, now i decided to install any custom rom on it, for this i downloaded all necessary files (revolutionary etc.), following is the information of my desire;
BRAVO PVT4 SHIP S-OFF
HBOOT-1.02.0001
MICROP-051D
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
JULY 22 2011, 16:19:16
I was surprised to see it was already S-OFF, my questions are;
1) why is it already S-OFF? (it was not rooted before upgrade)
2) Tell me the steps for gaining root or installing custom recovery? (in my case where i am already s-off)
3) Do i have to run revolutionary or just start by installing amon-ra recovery by android-win-tools method?
I am new to this thing and never rooted or installed custom rom before, but went through a lot of threads in this forum and did not find any clue relating to my case.
Thanks in advance.

Ashar said:
I bought a desire (used) and upgraded it from official Froyo to official Gingerbread via RUU, now i decided to install any custom rom on it, for this i downloaded all necessary files (revolutionary etc.), following is the information of my desire;
BRAVO PVT4 SHIP S-OFF
HBOOT-1.02.0001
MICROP-051D
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
JULY 22 2011, 16:19:16
I was surprised to see it was already S-OFF, my questions are;
1) why is it already S-OFF? (it was not rooted before upgrade)
2) Tell me the steps for gaining root or installing custom recovery? (in my case where i am already s-off)
3) Do i have to run revolutionary or just start by installing amon-ra recovery by android-win-tools method?
I am new to this thing and never rooted or installed custom rom before, but went through a lot of threads in this forum and did not find any clue relating to my case.
Thanks in advance.
Click to expand...
Click to collapse
I don't think this s-off is as "thorough" as revolutionary. I tried to get someone else who had this but his English was not too good so didn't get very far. It would be nice to know the limitations of this factory S-off though.
Have you got a recovery in mind? As you are PVT4, you need to be aware that you cannot use clockworkmod 2.5.0.7 if you are erase size 40,000. Which means you need to use a newer CWM (Bah) or AmonRA.
To find out, download a terminal emulator from the market:
Code:
cat /proc/mtd
(note space between cat and /)
Then you need to fastboot flash recovery. Follow link in my signature for an adb and fastboot faq. Also be aware adb and fastboot are different things. adb has nothing to do with this.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

rootSU said:
I don't think this s-off is as "thorough" as revolutionary. I tried to get someone else who had this but his English was not too good so didn't get very far. It would be nice to know the limitations of this factory S-off though.
Have you got a recovery in mind? As you are PVT4, you need to be aware that you cannot use clockworkmod 2.5.0.7 if you are erase size 40,000. Which means you need to use a newer CWM (Bah) or AmonRA.
To find out, download a terminal emulator from the market:
Code:
cat /proc/mtd
(note space between cat and /)
Then you need to fastboot flash recovery. Follow link in my signature for an adb and fastboot faq. Also be aware adb and fastboot are different things. adb has nothing to do with this.
Click to expand...
Click to collapse
Thanks for your quick reply. Please note some of results for MTD and ROOT Check.
$ export PATH=/data/local/bin:$PATH
$ cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00040000 "misc"
mtd1: 00480000 00040000 "recovery"
mtd2: 00340000 00040000 "boot"
mtd3: 0fa00000 00040000 "system"
mtd4: 02800000 00040000 "cache"
mtd5: 096c0000 00040000 "userdata"
$
It means my erase size is 40,000 and i need latest CWM, or AmonRA recovery?
Root Checker Advanced Root Access Results
Superuser.apk - com.noshufou.android.su - is NOT installed!
The application Superuser is recommended as it provides basic security and is available for free in the Android Market
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your HTC Desire device by Root Checker version 3.7 from joeykrim in the Android Market - http://goo.gl/GgWae
May be you can extract limitations of this factory s-off from above technical data.
Now may i do the following?
1) run revolutionary and do not install recovery from therein.
2) flash fastboot recovery by android-win-tools method.
3) flash su-2.3.6.3-efgh-signed from within custom recovery
4) flash any custom rom.
or may i skip step 1 and follow the rest?
thanks in advance

rootSU said:
I don't think this s-off is as "thorough" as revolutionary. I tried to get someone else who had this but his English was not too good so didn't get very far. It would be nice to know the limitations of this factory S-off though.
Click to expand...
Click to collapse
Well it is exactly, as s-off as if you did it using revolutionary. So the bootloader won't check signatures(which is the definition of s-off), but you won't be able to use fastboot commands, as those are not included in the stock hboot.
To be able to flash a recovery using "fastboot flash recovery" He must first flash a custom hboot with fastboot commands enabled. Do the following:
1. download this zip file: http://alpharev.nl/PB99IMG_stock.zip
2. Rename it to "PB99IMG.zip"(make sure it's not PB99IMG.zip.zip, as windows may hide the ending)
3. Place this file on the root of your sd-card.
4. Shut down your phone and boot up by holding "vol-down" and pressing power While keeping "vol-down" pressed until you enter hboot.
Your phone should now flash the image, and you should be able to flash a recovery using fastboot commands.
(This means you don't need to use revolutionary, but you cannot just flash cwm before doing the above steps either)

Thanks for the info, I wasn't aware of fastboot.
So the signature checking is also in nvram?
Sent from my HTC Desire using XDA App

mortenmhp said:
Well it is exactly, as s-off as if you did it using revolutionary. So the bootloader won't check signatures(which is the definition of s-off), but you won't be able to use fastboot commands, as those are not included in the stock hboot.
To be able to flash a recovery using "fastboot flash recovery" He must first flash a custom hboot with fastboot commands enabled. Do the following:
1. download this zip file: http://alpharev.nl/PB99IMG_stock.zip
2. Rename it to "PB99IMG.zip"(make sure it's not PB99IMG.zip.zip, as windows may hide the ending)
3. Place this file on the root of your sd-card.
4. Shut down your phone and boot up by holding "vol-down" and pressing power While keeping "vol-down" pressed until you enter hboot.
Your phone should now flash the image, and you should be able to flash a recovery using fastboot commands.
(This means you don't need to use revolutionary, but you cannot just flash cwm before doing the above steps either)
Click to expand...
Click to collapse
Thanks for your reply, please answer these questions ( i am so careful because i m doing it for the first time)
1) what will be my hboot version after flashing PB99IMG.zip? (right now my hboot is 1.02.0001 and i am on stock gingerbread 2.3.3)
2) if i just want to gain root access and dont want a custom rom, do i need to flash hboot and recovery or just flash su-2.3.6.3-efgh-signed?
(i just want to uninstall adobe flash player 10.1 and google maps 5.2 from system preinstalled in 2.3.3 to gain some space for installing latest versions 10.3 and gm 5.10)
thanks in advance

It'll be 6.093 or something. You can't flash su without flashing recovery. You can't flash recovery until you do PB99IMG.zip
Removing pre installed apps just makes space in system, which is not where you install apps so doing that alone will not give you more space.
Have a read of the root memory faq in my signature
Sent from my HTC Desire using XDA App

rootSU said:
So the signature checking is also in nvram?
Click to expand...
Click to collapse
Well not exactly, but the stock hboot allows for skipping signature check if the flag in nvram is set AFAIK.

rootSU said:
It'll be 6.093 or something. You can't flash su without flashing recovery. You can't flash recovery until you do PB99IMG.zip
Removing pre installed apps just makes space in system, which is not where you install apps so doing that alone will not give you more space.
Have a read of the root memory faq in my signature
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
After doing PB99IMG.zip my phone info is as follows;
BRAVO PVT4 SHIP S-OFF
HBOOT-6.93.1002 (it was 1.02.0001 before)
MICROP-051d
RADIO-5.17.05.23
Aug 10 2010, 15:52:18 (it was July 22 2011, 16:19:16 before)
Now please recommed me the recovery (CWM or AmonRA) and a custom rom (fast, stable, more user space, more battery) to flash, thanks again for your kind help and guidance

mortenmhp said:
Well not exactly, but the stock hboot allows for skipping signature check if the flag in nvram is set AFAIK.
Click to expand...
Click to collapse
Yes, alpharev hboots "ignore" the NVRAM flag. But I am unsure how these factory hboots with s-off work. I don't understand why they would implement an ignore via hboot, when they have the flag in NVRAM. I would expect them to turn the flag of at source instead of using the same work around as alpharev, which is what I am confused about.
Thats kind of why I wanted someone to investigate, but the fastboot commands make sense. I suppose the Nexus one haas embeded fastboot commands as it's a developer phone. Although, why HTC would release an S-OFF version of the desire but ommit fastboot is beyond me. I thought the whole reason they did this was due to petition pressure not to lock it down too much

[Q] Making stock backup and unlocking bootloader

I'm reading for few days now and I'm confused in two things:
1) unlocking bootloader
When using Hasoon2000 All-in-one toolkit I get different token, also fastboot oem get_identifier_token gives every time different token :/
Am I doing something wrong or it is normal?
2) making stock backup
Please correct me if I'm wrong
First I have to unlock bootloader, then I have to run custom recovery with: fastboot boot [TWRP or Philz touch recovery.img it will allow me to backup stock recovery and stock ROM (ROM will be cleaned after unlocking bootloader)
Then flash custom recovery fastboot flash recovery xxx.img
and if I want to have stock rooted flash only supersu or flash custom rom.
Am I right?

Globus.gd said:
I'm reading for few days now and I'm confused in two things:
1) unlocking bootloader
When using Hasoon2000 All-in-one toolkit I get different token, also fastboot oem get_identifier_token gives every time different token :/
Am I doing something wrong or it is normal?
2) making stock backup
Please correct me if I'm wrong
First I have to unlock bootloader, then I have to run custom recovery with: fastboot boot [TWRP or Philz touch recovery.img it will allow me to backup stock recovery and stock ROM (ROM will be cleaned after unlocking bootloader)
Then flash custom recovery fastboot flash recovery xxx.img
and if I want to have stock rooted flash only supersu or flash custom rom.
Am I right?
Click to expand...
Click to collapse
I'm not sure about the identifier token, didn't notice if it gives different tokens or not. Have you actually managed to unlock the bootloader though? You should try and do all these things without using all-in-one toolkits, you'll learn a whole lot more that way, especially when it comes to troubleshooting and fixing your device. It's not as difficult as you think it is. :good:
Yes unlock bootloader. Only Philz/CWM makes backup of stock recovery, TWRP doesn't make a backup of it. Rather use adb to make a backup of stock recovery. Boot the custom recovery of your choice and then flash the SuperSU app to get root or you can use towelroot if it works for your device.
Restart your phone(can go into OS) connect to PC, open command prompt and cd to adb folder.
Code:
adb shell cat /proc/emmc - [B]this will give out a list of all patitions on your device.[/B]
On my device it's in mmcblk0p43 , I'm sure it'll be the same for you as well, can just use above command to make sure. You can also type the command in a terminal emulator on your device if you have one installed cat /proc/emmc
So for my recovery block(Yours probably too) continue in command prompt on PC:
Code:
adb shell
su - [B]to gain super user status, just accept on device when prompted.[/B]
dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img - [B]or[/B]
dd if=/dev/block/mmcblk0p43 of=/sdcard2/recovery.img - [B]if you want it on external sd card[/B]
There you made a backup of your recovery partition, you can immediately transfer it to the PC(adb folder) if you want by typing:
Code:
exit - [B]to exit shell prompt and go back into normal adb prompt[/B]
adb pull /sdcard/recovery.img [B](Or of course /sdcard2/ if you used external sd.)[/B]
To pull it to another directory just press spacebar after recovery.img and type in path directory to where you want to pull it.

BerndM14 said:
Have you actually managed to unlock the bootloader though?
Click to expand...
Click to collapse
No, I asked on htcdev why generated token is different every time I use fastboot command,

[Q] HTC Desire Z NOT BOOTING at all and cannot make S-OFF

My Desire Z was previously running official updated Android 2.3.3 Gingerbread. I did the following.
1. unlocked bootloader from official HTCDEV.
2. installed CWM 6.0.4.5 with fastboot from this link http://forum.xda-developers.com/showthread.php?t=2561226
3. According to instructions from this link http://www.teamandroid.com/2013/03/13/update-htc-desire-z-android-422-aosp-jelly-bean-custom-rom/2/, in CWM recovery, I wiped data.
4. Then I installed Custom ROM AOSP 4.2.2 zip and Gapp received from this link http://forum.xda-developers.com/showthread.php?t=2163579
After that, and Now, no matter how I try, my Desire Z cannot boot anymore and hanging only at HTC logo white screen.
-I can only go to fastboot mode and go to CWM recovery 6.0.45.
-I tried wipe data, cache, dalvick cache from recovery, but still cannot boot.
-This is the detail of the bootloader and system:
VISION PVT SHIP S-ON
HBOOT-0.85.0015
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
DEC 20 2010,16:21:13
Carrier: htc Asia WWE
Model: PC1011000
-I saw s-on when I power on at bootloader mode. I don't know how to root and make s-off.
-I cannot use ADB because I cannot boot and my adb cannot find the device in bootloader/fastboot mode.
-In CWM mode, my adb saw it as "SH118RT01215 recovery" with adb devices command.
-So with CWM mode, When I run "adb shell cat /dev/msm_rotator" command, I received "cat: read error: Invalid argument"
-When I run "chmod 777 /data/local/tmp/fre3vo" after "adb push", it shows "no such file or directory"
-I tried to do instructions given as on http://forum.xda-developers.com/showthread.php?t=1178912 but received errors.
-I also tried instructions from http://wiki.cyanogenmod.org/w/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread) but no luck.
I would like to install custom ROM and use Android 4.x on my Desire Z.
What should I do now? Please help. :crying: :crying: :crying:

Being you are s-on, after flashing a custom ROM in recovery you need to boot into bootloader and flash the kernel via fastboot
Unzip the ROM, extract the boot.img
fastboot flash boot boot.img
fastboot reboot
After this when up and running I highly suggest relocking your phone and following the steps to downgrade and root via gfree

demkantor said:
Being you are s-on, after flashing a custom ROM in recovery you need to boot into bootloader and flash the kernel via fastboot
Unzip the ROM, extract the boot.img
fastboot flash boot boot.img
fastboot reboot
After this when up and running I highly suggest relocking your phone and following the steps to downgrade and root via gfree
Click to expand...
Click to collapse
Thanks demkantor. With your instructions and the help from Nipqer at g2root chat. The problem is solved. Successfully S-OFF and now running Custom ROM android 4.2.2.
Thanks again a lot for everybody. :good::good::laugh:

Help a Newbie to rid GPE RUU

Hi folks
I have recently bought a HTC One M8 on ebay which was converted to play edition by the seller using GPE RUU. I know very little about this but would like to attempt to return to stock whilst ensuring no flagged messages are left on.
I have searched and only come across guides that are specific to specific circumstances. Does anyone have or know of a general and safe guide that would work in my case?
Any help greatly appreciated.
Thanks in Advance
Sid

Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?

EddyOS said:
Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?
Click to expand...
Click to collapse
model: OP6B100
No idea what it was running before.

OK, going by that ID we can assume it's an EU unbranded handset. Or we can at least we can treat it as such. So, assuming you want to go back to 100% stock Sense (but keep S-OFF) do the following:
First, download the following to your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249
1.54.401.5 FW ZIP - http://www.androidfilehost.com/?fid=23329332407589439 (rename it firmware.zip)
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (rename it to recovery.img)
HTC Sync Manager (for the drivers) - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it and then uninstall Sync Manager but leave the drivers)
1. First things first, change the CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader to confirm it's showing the Super CID - fastboot reboot-bootloader
3. Once confirmed it's set, we now need to set the right MID in case this was changed by the seller. To do this, we can use TWRP. Flash TWRP (downloaded earlier) - fastboot flash recovery recovery.img
4. Once flashed, boot into TWRP and connect the phone to your PC
5. Once the drivers are installed, make sure the PC sees the phone by typing adb devices
6. So long as it's been shown as a connected device, type adb shell
7. We can now change the MID to the EU unbranded one by using the following command (copy/paste this as it has to be exact)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
8. Once done, we can now 'lock' the bootloader using the following command (whilst still in adb shell)
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
9. And we can also reset the tamper flag at the same time
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
10. Once all that is done, type exit to leave adb shell and then reboot the phone into the bootloader through the reboot menu in TWRP
11. Once back at the bootloader, you should find the phone is now 'LOCKED' and it shouldn't say 'TAMPERED' at the top either but should still have the black bootloader interface that the GPe has. We can now set it all back to Sense
12. Reboot the phone into RUU mode - fastboot oem rebootRUU
13. Once in RUU mode, flash the firmware ZIP - fastboot flash zip firmware.zip
14. The process will fail the first time and reboot. Run the same command again once it's rebooted - fastboot flash zip firmware.zip
15. Once finished, reboot the phone to the bootloader to confirm you now have the white 'Sense' bootloader - fastboot reboot-bootloader
16. Assuming it's correctly flashed, reboot back into RUU mode - fastboot oem rebootRUU
17. We can now flash the RUU using the htc_fastboot package - htc_fastboot flash zip ruu.zip
18. Once finished, reboot back to the bootloader one last time - fastboot reboot-bootloader
19. Once back in the bootloader, change the CID to HTC__001 - fastboot oem writecid HTC__001
20. Reboot the bootloader to confirm the change has been successful - fastboot reboot-bootloader
21. Once back at the boot loader, disconnect the phone and boot into recovery and do a factory reset
22. Once the reset finishes, reboot the phone
That should get it all working but any issues obviously let us know

Fastboot folder? I did say i was a newbie! thanks

OK, perhaps it might be worth reading up on fastboot/adb before doing anything as the above isn't for the faint-hearted!
EDIT: I've attached my 'fastboot' folder. Extract it to the root of your C: drive so it's easy to get to. All the commands in my guide are done through a command prompt in Windows starting in that folder, e.g. C:\platform-tools\fastboot oem rebootRUU
https://drive.google.com/file/d/0B8L4pkbzdlR3Z3dsNGZfSWhCeTA/view

ok, I have installed fastboot adb andi have a folder called adb in my c:. I am now downloading all the items listed above and renaming as appropriate and moving to the folder named adb. am I on the right track?

Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK

i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.

tonytdc1000 said:
i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.
Click to expand...
Click to collapse
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running

I know your getting help here, but...Can I ask..
When you bought the One M8 on eBay, did the ad or photos say you were buying an M8 unlocked and Converted from Sense to GPE.
If Not, you do know youve been sold an incorrect product and you have a case against the seller for false advertising, so save yoursewlf the issues, exersize your rights and send it back.
Plus, you say you are new to flashing / unlocking, so if you brick this M8, you dont have any returns room.
Just wanted to say that and hope it helps. Good Luck

EddyOS said:
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running
Click to expand...
Click to collapse
Ok i will... thanks

EddyOS said:
Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK
Click to expand...
Click to collapse
Hi Eddy
Thanks for all your support, i have successfuly completed step 1, 2 and 3. Now I need some assistance in flashing TWRP. How do i do this and what do i use?
regards

3 was flashing TWRP so if you've done that you now enter recovery via the bootloader.