Develop Bugs

unlocking problem "waiting for device"

Hey guys,
I am trying to s-off my girlfriends Wildfire S.
MARVEL PVT SHIP S-ON RL
HBOOT-1.009.0099
MICROP-041
RADIO-7.57.39.10M
FEB 9 2012 18:29:31
I am following the directions from htcdev.com/bootloader
I got to the point where I am supposed to "get_identifier_token"
Now my phone is connected as it should be, I am in "fastoot usb".
Still, the only thing happens is that I get the following message in command prompt: "waiting for device". Nothing happens. I tried to restart PC and phone again: same problem.
Does anyone have an idea about what I'm doing wrong? I'm stuck.

Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.

szaboagoston said:
Okay. Now I unlocked bootloader. I think the problem was USB-debugging was not turned on.
Trying to run clockworkmod, but keep getting error messages:
"you must root your phone for ROM manager to function. Superuser was not found at "/system/bin/su" or "system/xbin/su".
When I try to flash clockworkmod recovery I get the following error:
"An error occured while attempting to run privileged commands".
My deviced is with unlocked bootloader, buy of course still S-ON. I understood from the threads around that that's not a problem.
http://forum.xda-developers.com/showthread.php?t=1927757&highlight=root
How can I install a custom ROM?
How can I install data2sd?
Can someone help? Thanks a lot.
Click to expand...
Click to collapse
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038

success
Karavasileiadis said:
-------------------------------------------------------------
Hi, what you need to do is go into your bootloader as you usually do, Volume - and Power Button, plug your USB and go into fastboot USB. Then you need to create a file on you C: drive called "fastboot" and put the following files in there "adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe" and your recovery image, I suggest you use the offical clock work mod recovery which is available here,
if you do not have these files you can download them from here,
http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvel.img
http://forum.xda-developers.com/showthread.php?t=1474956
once you do this then open a command dos window by typing cmd in the start search box of windows.... once the command window opens go to the right folder of C:\fastboot> where you saved the files.
Then as your phone is in fastboot USB and you are in the command window C:\fastboot>, type in the command window the following,
fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
Then press enter, what you should see is the below,
c:\fastboot>fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img
sending 'recovery' (2224 KB)... OKAY
writing 'recovery'... OKAY
If you follow the above then you should have clockworkmod recovery, you can then take the USB out and go back to the hboot in you bootloader and choose recovery under hboot by navigating with the volume button and power button.
I do need to inform you though that if you are one of the unlucky WFS owners that get the "Black Screen Recovery" issue where you go into recovery and you only get a black screen and you tactile buttons are on then you need to follow the bellow method to be able to see you recovery on you PC screen than on your phone.
http://forum.xda-developers.com/showthread.php?t=1781105
Also here is a youtube video of what I mean
http://www.youtube.com/watch?v=HgrPctWKW8E
I know all this as I had the same issue and this helped me. Now I feel that I need to inform you about other issues... When you unlock the bootloader you can't flash a ROM and then just switch your phone on and it boots into the new ROM, there is a process you need to follow.
When you choose your ROM, and not all ROMs work with the Wildfire S new batch of phone as I had to find out the hard way, you need to flash your ROM and then open the .zip file of your phone copy the boot.img of the ROM paste it in the c:\fastboot> directory and again in the command window type,
fastboot flash boot boot.img
You will see the below,
c:\fastboot>fastboot flash boot boot.img
sending 'boot' (2224 KB)... OKAY
writing 'boot'... OKAY
Then type,
c:\fastboot>fastboot reboot
And your phone will reboot into the new ROM allow 10 to 15 minutes... BE PATIENT.
I hpe the above helps you.
I am currently having the below problems just for your info if you have the same...
http://forum.xda-developers.com/showthread.php?t=1948038
Click to expand...
Click to collapse
Thanks a lot for the quick and professional answer. By the time I read it, I managed to root.
I used rezo609's all-in-one utility, which I found in at this location:
http://forum.xda-developers.com/showthread.php?t=1697985
I got the advice from this thread:
http://forum.xda-developers.com/showthread.php?t=1927757
I installed the Speeddroid ROM and data2SD as described here:
http://forum.xda-developers.com/showthread.php?t=1932534&highlight=data2sd+install
The result: so far everything working. It looks like a new phone!

stuck to root
Hi,
I have the same situation here.
But Which tool do you run of the [UTILITY]rezo609's All-In-One Utility ? (http://forum.xda-developers.com/showthread.php?t=1697985&page=3)
In the whole topic there is no how to.
I managed to unlock the bootloader, and clockwork recovery is also on there.
I just want to root the phone (not to put an other rom)
Thanks in advance,

Problem Rooting...know this is old but...

Ok i came here from here http://forum.xda-developers.com/showthread.php?t=1751796
Droid Incredible 2 runnig GB 2.3.4 -- 6.01.605.05 710RD
TACOROOT
(TCR)
Versions: 6.01.605.05 firmware
Tacoroot is a temp root method discovered by Justin Case that will allow those on the newer firmware to flash an older version and root with Revolutionary. Before you begin, download this zip containing all the files you'll need:
http://d-h.st/yJQ
Extract this zip to C:/Android. You can extract it somewhere else, just replace C:/Android with the path to the wherever you extracted it wherever it comes up. Now, connect your device to your computer with a USB cable, turn on USB Debugging under Settings>Apps>Development, and disable fastboot under Settings>Power. Make sure your phone is fully charged. Open a command prompt by opening the start menu, typing "cmd" and hitting enter. Type in everything that is in black text. Notes and extra instructions will be written in blue. It is reccomended that you copy/paste the code to avoid typos, to do this, copy by highlighting the line and hitting Ctrl+C as usual; to paste, go to your command prompt and click the small black icon in the upper left corner. A menu will pop up, go to Edit>Paste. Make sure you have not highlighted any spaces before or after the line or any of the blue text. Now, begin copying the code:
cd C:/Android
md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip Remove the space in the middle of the word radio before hitting enter, I don't know why it won't let me remove it. Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip.
md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip Result should be ea6b98be48210d7797e62362f49ff751
md5sums tacoroot.sh Result should be 6ec06d776feb212d8b2a55817eddf76d
md5sums misc_version Result should be 050f55d34ddbcc860efa5982491437de
adb devices Result should be your phone's serial number. If it isn't make sure drivers are properly installed and USB Debugging is enabled.("Its all good till i reach this step, i cant see my serial number, i have installed the drivers, the new ones from htc sync, i have reinstalled the drivers but it not work at all...)"
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup This will reboot your phone. When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue.
adb shell /data/local/tacoroot.sh --root
adb wait-for-device Running the step before this will reboot your phone again, this time it will be bootlooping, meaning it will not boot fully and get stuck on the boot animation. Once your prompt comes back after this step, you're good to continue even though the phone isn't fully booted.
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb shell /data/local/tacoroot.sh --undo This will reboot your phone one more time, this time fully stable and will boot completely. Continue once fully booted.
adb reboot bootloader This will reboot your phone to a white screen with a few options. Once you are at this screen, continue with the instructions.
fastboot devices Result should be your phone's serial number, again.
fastboot getvar mainver The result should be 2.18.605.3. If it is not, something was not done correctly, you'll need to restart from the beginning.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip This will take a bit of time without giving any indication as to when it will be done, be patient and do not interrupt it.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )
fastboot reboot

Make sure you have USB debugging enabled, I think it's under Apps>Development.
Sent from my SCH-I535 using Tapatalk 2

It is enabled and the drivers are installed.
I had installed the HTC sync but it never recognized the phone so it make me think that is a problem with the drivers.
Sent from my HTC DROID Incredible 2 using Tapatalk

Killerin said:
It is enabled and the drivers are installed.
I had installed the HTC sync but it never recognized the phone so it make me think that is a problem with the drivers.
Sent from my HTC DROID Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Don't install htc sync, that can mess it up. The drivers from the OP should work, nobody else has had problems with them.
Sent from my SCH-I535 using Tapatalk 2

I also tried that but the drivers of the OP doesn't work for me, I can't even install it. Will upload the screen shots.
I'm using windows 8 could it be a problem?
Sent from my HTC DROID Incredible 2 using Tapatalk

This is what i get when im trying to install the OP's Drivers

Killerin said:
This is what i get when im trying to install the OP's Drivers
Click to expand...
Click to collapse
Translation?
Sent from my SCH-I535 using Tapatalk 2

prototype7 said:
Translation?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The assistant has been interrupted before finishing installation of the HTC Driver Installer.
Your system has not been modified. To install this program another time execute the installer program again.
Click on finish to leave the assistant.

gtdtm said:
The assistant has been interrupted before finishing installation of the HTC Driver Installer.
Your system has not been modified. To install this program another time execute the installer program again.
Click on finish to leave the assistant.
Click to expand...
Click to collapse
+1, dont know what appeared on spanish lol
Will Install windows 7, probably is W8 the problem with the drivers

thats it!! the problem was Windows 8! now in windows 7 could do everything but got stucked on last step " fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )"
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.401s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.195s
the phone is stucked on HTC logo... now what?
Edit: Had to remove the battery and unplug the usb from the phone to get out of the htc logo screen. now is rebooted and running 2.3.3 the version downgraded i guess is all fine. now will continue with the Revo!

Killerin said:
thats it!! the problem was Windows 8! now in windows 7 could do everything but got stucked on last step " fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )"
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.401s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.195s
the phone is stucked on HTC logo... now what?
Edit: Had to remove the battery and unplug the usb from the phone to get out of the htc logo screen. now is rebooted and running 2.3.3 the version downgraded i guess is all fine. now will continue with the Revo!
Click to expand...
Click to collapse
I am having the same problem. It sounds like this last step is supposed to take as long as the previous step. The fact that it comes up with the "FAILED (12 signature verify fail) response worries me. If I reboot and continue on with installing revolutionary, will this brick my phone? Or is it supposed to do this (12 signature verify fail)?

I've read a lot of people have that problem. Just move on with rev and go back later and update the radio. A quick search will give you LTS of threads with the instructions to install a new radio. Hint:it's done in boot loader not recovery.
Sent from my Incredible 2 using xda app-developers app

Toolkit Rooting Question FAILInvalid Command"

I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick

put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058

I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.

is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img

It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.

waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2

I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?

crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.

[Q] RUU failed. Now stuck on htc logo. Dead?

Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks

gmdiesel05 said:
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
Click to expand...
Click to collapse
did you flash the ruu.zip 2 times .. the first flash only updates the hboot

clsA said:
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
Click to expand...
Click to collapse
yes the second time it said device not found! In cmd window, i type adb devices and none there
This is what happens, and hangs there
C:\Users\Desktop\platform-tools>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.072s]
finished. total time: 0.073s
C:\Users\Cedrik\Desktop\platform-tools>fastboot flash zip RUU-HTC_One_M8_GPE_5.0
.1-3.11.1700.5.zip

gmdiesel05 said:
yes the second time it said device not found! In cmd window, i type adb devices and none there
Click to expand...
Click to collapse
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?

clsA said:
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
Click to expand...
Click to collapse
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd

gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. now i cant flash a 2nd time
Click to expand...
Click to collapse
are you s-off ? is your phone a GSM M8 ?

Did you try the other method, just renaming the RUU to 0p6bimg.zip (<a 0 (Zero) not a capital o (O), naturally...)
What error do you get when the flashing of the RUU fails?
Like mentioned by clsA said, adb devices won't work in fastboot mode, it should be "fastboot devices" to check if it's connected
---------- Post added at 06:20 AM ---------- Previous post was at 06:18 AM ----------
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
Click to expand...
Click to collapse
You changed CID and MID I take it?
CID - GOOGL001
MID - 0P6B17000
Would have helped a bit if we had an idea what the error was.

clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.

clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
Yeah he said his phone is S-OFF in OP
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Click to expand...
Click to collapse

gmdiesel05 said:
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
Click to expand...
Click to collapse
just use the fastboot flash zip ruu.zip command again

clsA said:
just use the fastboot flash zip ruu.zip command again
Click to expand...
Click to collapse
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....

gmdiesel05 said:
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
Click to expand...
Click to collapse
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?

clsA said:
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
Click to expand...
Click to collapse
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?

ok heres the latest
FAILED <command write failed <No such device or address>>

gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything. Sorry you lost me here
maybe im not waiting long enough?
Click to expand...
Click to collapse
you have the file renamed just copy it to your Ext - sdcard and let the bootloader flash it
don't forget to delete or rename it on the sdcard before you reboot again or it will flash it again

ok heres the latest
FAILED <command write failed <No such device or address>>

gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
Click to expand...
Click to collapse
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Method 1
No computer required. Everything else still required. s-off, super CID/gpe CID etc..
1. Rename the RUU zip file 0p6bimg.zip (if your hboot is looking for a different name then rename it to whatever it's looking for)
2. Place the zip on your external SD card
3. Power off your phone
4. Boot into Hboot (hold down vol down as you power on the device)
5. it will load the zip and ask you if you want to proceed
6. Say yes
7. Wait
8. Profit
Click to expand...
Click to collapse
Didn't say anything about flashing it in RUU mode.

BerndM14 said:
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Didn't say anything about flashing it in RUU mode.
Click to expand...
Click to collapse
i used
Method 2
ADB/FastBoot Method
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
you will the following message:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
Code:
fastboot reboot

[Q] TIFU going from GPE5.1 Back to Sense, Please help :)

So, the instructions are below pulled out of the Back to Sense thread.(http://forum.xda-developers.com/showthread.php?t=2733523) got to the end of what i've pasted no problems......
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Everything went well until the after that... I stuffed up royally.. my failure is below...
PS C:\adb> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
PS C:\adb> fastboot flash recovery TWRP_Recovery_2.8.6.2_M8_CPTB.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16804 KB)...
OKAY [ 1.515s]
writing 'recovery'...
OKAY [ 0.940s]
finished. total time: 2.455s
fastboot boot TWRP_Recovery_2.8.6.2_M8_CPTB.img
I realize i skipped the below steps...
Boot into stock recovery
Factory reset
Reboot into bootloader
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever.... one thing worth noting, i can see the internal storage(well some of it) the device is recognized in windows and then internal storage is 10.5gb free out of 10.6gb, Navigating to the internal directory shows 3 directories: 0, obb, and TWRP. 0 is a neverending folder. every 3rd layer deep click it shows the root directory again...
Help would be very very much appreciated!
cheers!
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!

Cameltoemcgee said:
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever....
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Click to expand...
Click to collapse
If the bootloader was overwritten, damaged or corrupted, the phone would be bricked, and the screen would not come on at all.
This is the second post on the first page where the OP solved their own issue. You guys are getting good at fixing your own problems.