I wanted to bring this in here, as I found a way to enable fastboot to flash recovery!
Quick device info update:
HBOOT-1.33.0010
Radio-3.22.26.17
Ok, first put the phone into fastboot mode. Then execute the command:
fastboot oem rebootRUU
Wait for it to reboot in RUU mode. Then, when I execute fastboot flash recovery recovery-RA-dream-v1.6.2R.img, I get the following:
sending 'recovery' (4568 KB)... OKAY [ 1.721s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 3.036s
So, is there a signed recovery we can launch?
As an update, booting recovery:
downloading 'boot.img'... OKAY [ 1.647s]
booting...
hangs here
i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
gawgaw said:
i have problem in my sensation ,when do unlock for bootloader then make lock bootloader i forget and do lock bootloader twice ,and now apeear to me <relocked bootloader> with <s-on>and now i make unlock bootloader toooooo much times and bad result and when install recovery write it <<<<FAILED (remote: signature verify fail)>>>>please help me to unlock it again
Click to expand...
Click to collapse
did you try to use unlocked bin code again?if not then do it again
i do it tooo much,and using many tools
now i can think only one thing.flash the specific ruu.exe for your device and start from the beginning
see here
http://forum.xda-developers.com/showthread.php?t=1672425
otherwise if you have patience wait for someone else to provide you a solution
i do all of this and install <RUU FILES>and the problem not fixed ,i copy this information to help you and indicate my problem
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\george>cd C:\Program Files\Android\android\platform-tools
C:\Program Files\Android\android\platform-tools>Unlock_code.bin
C:\Program Files\Android\android\platform-tools>fastboot flash unlocktoken Unloc
k_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.160s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.192s
C:\Program Files\Android\android\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 3.243s]
finished. total time: 3.250s
C:\Program Files\Android\android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
(bootloader) erase sector 130560 ~ 131071 (512)
OKAY [ 3.190s]
finished. total time: 3.195s
C:\Program Files\Android\android\platform-tools>fastboot flash zip PG58IMG.zip
sending 'zip' (23984 KB)...
OKAY [ 4.164s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 9.370s
C:\Program Files\Android\android\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.431s]
finished. total time: 0.435s
confirm something
when you use the ruu.exe did you have successful result for flashing it?
yes,the result successful but the problem not fixed ,bootloader relocked
gawgaw said:
yes,the result successful but the problem not fixed ,bootloader relocked
Click to expand...
Click to collapse
ok then
the only thing that i can tell you is to follow the whole process for unlocking the bootloader
start from the beginning.if that don't work too then i am out of ideas
best wishes
if i think something else i will tell you
thank you tooo much ,im sorry to tired you
Can you boot the phone now?
Also did the phone came from a repair with motherboard replaced?
Sent from my HTC Sensation using xda premium
Hi there.
I've got an unbranded htc sensation device (manufactured for india). lat week i updated to cm9, and accidentally got a 1.29 hboot. after that I tried to flash the stock ICS for my pyramid. so, the situation is:
cid HTC__038
hboot version 1.29.0000
radio 11.24A.3504.31_m
openadsp v05.6.0.2226.00.0418
pyramid pvt ship s-on locked.
working adb, fastboot connection
i've got no working rom on the device, stuck in fastboot-loop.
there is no possibility to use revolutionary s-off because of hboot version 1.29, and because the non-working system (cannot put in debug mode)
i tried to flash the lastest 3.33 firmware, bit it still uses a previous version of hboot. (something messed up with signature check fail)
i cannot flash a non-official rom befause s-on.
do i have any possible steps to make my phone working with ics+sense?
all the answers will be "thanked" & btw sorry for my bad english
palomatE said:
Hi there.
I've got an unbranded htc sensation device (manufactured for india). lat week i updated to cm9, and accidentally got a 1.29 hboot. after that I tried to flash the stock ICS for my pyramid. so, the situation is:
cid HTC__038
hboot version 1.29.0000
radio 11.24A.3504.31_m
openadsp v05.6.0.2226.00.0418
pyramid pvt ship s-on locked.
working adb, fastboot connection
i've got no working rom on the device, stuck in fastboot-loop.
there is no possibility to use revolutionary s-off because of hboot version 1.29, and because the non-working system (cannot put in debug mode)
i tried to flash the lastest 3.33 firmware, bit it still uses a previous version of hboot. (something messed up with signature check fail)
i cannot flash a non-official rom befause s-on.
do i have any possible steps to make my phone working with ics+sense?
all the answers will be "thanked" & btw sorry for my bad english
Click to expand...
Click to collapse
Unlock via htcdev unlock then flash 4EXT recovery and enable smartflash then flash a ROM
flashing issue
Jonny said:
Unlock via htcdev unlock then flash 4EXT recovery and enable smartflash then flash a ROM
Click to expand...
Click to collapse
I've got the Unlock_code.bin, flashed with fastboot (fastboot flash unlocktoken Unlock_code.bin), and nothing happens, i mean no prompt is hiven for me to choose neither yes or no. command line says
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.162s
Click to expand...
Click to collapse
bootloader is still locked.
is it supported for hboot v1.29?
palomatE said:
I've got the Unlock_code.bin, flashed with fastboot (fastboot flash unlocktoken Unlock_code.bin), and nothing happens, i mean no prompt is hiven for me to choose neither yes or no. command line says
bootloader is still locked.
is it supported for hboot v1.29?
Click to expand...
Click to collapse
Hi,
Yes, 1.29 is supported.
Keep trying.
Sometimes ,it takes more than one go to work.
still no success
malybru said:
Hi,
Yes, 1.29 is supported.
Keep trying.
Sometimes ,it takes more than one go to work.
Click to expand...
Click to collapse
after a few attempts, i've got the following four different responses:
Code:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.162s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (remote: loading custom splash failed)
finished. total time: 0.001s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.069s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.079s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... OKAY [ 0.008s]
finished. total time: 0.160s
palomatE said:
after a few attempts, i've got the following four different responses:
Code:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.162s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (remote: loading custom splash failed)
finished. total time: 0.001s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.069s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.079s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... OKAY [ 0.008s]
finished. total time: 0.160s
Click to expand...
Click to collapse
fastboot reboot-bootloader
and then check the bootloader status
still locked
ganeshp said:
fastboot reboot-bootloader
and then check the bootloader status
Click to expand...
Click to collapse
I actually did this, with the same results. Is it a possible way if modify the partitions by a partitioning software running on pc, and manually edit the partitions' files, changing them to the correct ones, came from the official rom.zip file? I think (dont hit me if i was wrong), this way I can bypass all the s-on and locked bootloader stuff, maybe I can downgrade from hboot 1.29 without wire tricks, and install the stock ICS for pyramid.
what about the PG58IMG stuff? I can modify the removable sd card's files, so i can insert PG58IMG things to root, the phone is actually reads it. what if I somehow inject the Unlock_code.bin into some kind of PG58IMG, and apply this way the unlocking?
could be anything of these upper is working?
palomatE said:
I actually did this, with the same results. Is it a possible way if modify the partitions by a partitioning software running on pc, and manually edit the partitions' files, changing them to the correct ones, came from the official rom.zip file? I think (dont hit me if i was wrong), this way I can bypass all the s-on and locked bootloader stuff, maybe I can downgrade from hboot 1.29 without wire tricks, and install the stock ICS for pyramid.
what about the PG58IMG stuff? I can modify the removable sd card's files, so i can insert PG58IMG things to root, the phone is actually reads it. what if I somehow inject the Unlock_code.bin into some kind of PG58IMG, and apply this way the unlocking?
could be anything of these upper is working?
Click to expand...
Click to collapse
Nope can't/won't work
We could try one thing... Try changing cid
fastboot oem writecid HTC__001
Then ignore errors and reboot
fastboot reboot-bootloader
And check cid again
fastboot getvar cid
If it changed then you can very well flash European unbranded ruu and then boot to a working rom
If it not worked.. Then send a PM to FOOTBALL and ask for Indian ruu.. He might charge some minimal amount based on the scarcity of the ruu.. But if you got proper Indian ruu then you will come out of the boot loop fine
Sent from my Nexus 7 using xda premium
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
You have working adb when in boot loop?
Then you can try my temp-root and then jb SOFF process.. Link in my signature
Have slim chances of working.. But worth a try
Sent from my Nexus 7 using xda premium
ganeshp said:
Nope can't/won't work
We could try one thing... Try changing cid
fastboot oem writecid HTC__001
Then ignore errors and reboot
fastboot reboot-bootloader
And check cid again
fastboot getvar cid
If it changed then you can very well flash European unbranded ruu and then boot to a working rom
If it not worked.. Then send a PM to FOOTBALL and ask for Indian ruu.. He might charge some minimal amount based on the scarcity of the ruu.. But if you got proper Indian ruu then you will come out of the boot loop fine
Sent from my Nexus 7 using xda premium
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
You have working adb when in boot loop?
Then you can try my temp-root and then jb SOFF process.. Link in my signature
Have slim chances of working.. But worth a try
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
cid change is done, now it's HTC_001.
i tried to flash RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed's rom.zip from the temp, renamed to PG58IMG, copied to sdcard's root.
phone said: "lower hboot version"
is there any stock htc ROM with hboot 1.29?
if no, is it a possible way to change the zip to contain a 1.29 hboot version?
edit: i've got no bootloop, but at power-on I'm suddenly passed to fastboot screen without any boot process
but fastboot usb connection is always working, fastboot devices responses are always positive.
palomatE said:
cid change is done, now it's HTC_001.
i tried to flash RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed's rom.zip from the temp, renamed to PG58IMG, copied to sdcard's root.
phone said: "lower hboot version"
is there any stock htc ROM with hboot 1.29?
if no, is it a possible way to change the zip to contain a 1.29 hboot version?
Click to expand...
Click to collapse
Awesome... That will solve our issue now
Do this copy the New PG58IMG zip file to your fastboot folder
And try these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed stop there and don't do any thing else and simply paste back the output here)
fastboot reboot
Done
Edit: if the fail at third step is.. Something like.."Hboot pre update... Please flush the rom immediately again"] then repeat the third step again. (i.e this one fastboot flash zip PG58IMG.zip)
Sent from my Nexus 7 using xda premium
---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------
palomatE said:
edit: i've got no bootloop, but at power-on I'm suddenly passed to fastboot screen without any boot process
but fastboot usb connection is always working, fastboot devices responses are always positive.
Click to expand...
Click to collapse
Now that we have successful cid change adb change is not required
Sent from my Nexus 7 using xda premium
ganeshp said:
Awesome... That will solve our issue now
Do this copy the New PG58IMG zip file to your fastboot folder
And try these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed stop there and don't do any thing else and simply paste back the output here)
fastboot reboot
Done
Edit: if the fail at third step is.. Something like.."Hboot pre update... Please flush the rom immediately again"] then repeat the third step again. (i.e this one fastboot flash zip PG58IMG.zip)
Sent from my Nexus 7 using xda premium
---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------
Now that we have successful cid change adb change is not required
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
faced into error again here is the output:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 3.121s]
finished. total time: 3.121s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.267s]
finished. total time: 3.267s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (436283 KB)... OKAY [ 58.448s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 129.037s
C:\Android>fastboot flash zip PG58IMG.zip - here i didn't hit enter
palomatE said:
faced into error again here is the output:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 3.121s]
finished. total time: 3.121s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.267s]
finished. total time: 3.267s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (436283 KB)... OKAY [ 58.448s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 129.037s
C:\Android>fastboot flash zip PG58IMG.zip - here i didn't hit enter
Click to expand...
Click to collapse
hit enter ..if it fails again
reboot to bootloader using this command
fastboot reboot-bootloader
then can you give me the output of this command ?
fastboot getvar all (post everything except IMEI and serial number )
ganeshp said:
hit enter ..if it fails again
reboot to bootloader using this command
fastboot reboot-bootloader
then can you give me the output of this command ?
fastboot getvar all (post everything except IMEI and serial number )
Click to expand...
Click to collapse
i've made several attempts, all of them came out with the same results as I posted previously.
getvar results are the following:
Code:
C:\Android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: *** sent you via PM ***
INFOimei: *** sent you via PM ***
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4064mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.494s
hope this might help :angel:
hmm this has some weird combination (modelid indicates that the phone is normal sensation ..but firmware version says that the phone is xe!!!) ..but lets see
download the XE version of the same RUU you've downloaded earlier (will have LE in its Name) and get the rom.zip and flash the rom.zip manually using the fastboot commands ive given you earlier
ganeshp said:
hmm this has some weird combination (modelid indicates that the phone is normal sensation ..but firmware version says that the phone is xe!!!) ..but lets see
download the XE version of the same RUU you've downloaded earlier (will have LE in its Name) and get the rom.zip and flash the rom.zip manually using the fastboot commands ive given you earlier
Click to expand...
Click to collapse
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
palomatE said:
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
Click to expand...
Click to collapse
To change MID you need S-OFF. The RUU checks MID so if the 3.33.401.153 RUU fails try the 3.33.401.53 one
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
palomatE said:
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
Click to expand...
Click to collapse
Ahh as suspected
What happened is you have somehow flashed sensation xe hboot and rest of them have normal sensation counterparts...
I need you to do something now... Download the universal 3.33 firmware from kohr-ah firmware thread in sensation development section..
Then extract the zip
Open android-info.txt file and replace version-main with 3.33.401.53
And save it
Also you have the rom.zip of the normal sensation 3.33.401.53 right.. Get the hboot.nb0 (the name will be big but the extension remains same) and replace the hboot.nb0 present in the firmware zip with this one..
Then remake the firmware.. PG58IMG.zip
Then try to flash this... Obviously it will fail.. But if that replaces the hboot you are having then all is well
So after the above exercise.. You need to try flashing normal sensation rom.zip again
Hopefully it works
Sent from my HTC Sensation using xda premium
so i had to give back the phone to its owner, if the main htc service fails im goin to do the rest you suggested me. anyway i want to say thanks to all of you guys out there, i'll be back for more info, in case of fail. have a nice day
Sent from my GT-I9000 using xda app-developers app
I got home from work plugged my phone in and went to sleep. When I woke up the phone was on the bootloader screen. It wont do anything but switch screens from bootloader to hboot. I have trying installing the stock rom from here http://forum.xda-developers.com/ver...zip-ruu-m8vzw-5-0-1-s-off-onlynewest-t3047103 it fails to load from an micro sdcard.
This is a Verizon One M8 phone that has been rooted since release. I have been running Venom http://forum.xda-developers.com/showthread.php?t=2715225 4.3.0 for verizon users.
On the hboot screen it says:
** software statusffical ***
*** Unlocked ***
M8_mlv pvt ship s-offf
cid-vzw__001
hboot-3.19.0.0000
radio-invalid_ver_info
opendsp-invalid_ver_info
os-4.17.605.5
emmc-boot 2048mb
(time and date)
Also when it reboots it shows the android guy in the middle of the screen. It never show the HTC logo.
Try flashing a kernel http://forum.xda-developers.com/showthread.php?t=3152454
Kernels for One M8 AOSP Roms Discussion
Sent from my One using XDA Premium 4 mobile app
How do I flash a kernel? I can only get into fastboot.
I tired this:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Shannon>cd\
C:\>cd Android
C:\Android>cd com
C:\Android\com>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 5.035s
C:\Android\com>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
C:\Android\com>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.003s
C:\Android\com>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 10.075s]
finished. total time: 10.075s
C:\Android\com>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 10.071s]
finished. total time: 10.071s
C:\Android\com>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 0
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.081s]
finished. total time: 10.081s
C:\Android\com>fastboot flash zip rom.zip
target reported max download size of 1826336768 bytes
sending 'zip' (1726320 KB)...
OKAY [ 47.915s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 47.920s
It does not work
I tried this http://www.droidviews.com/restore-verizon-htc-one-m8-to-stock-rom-with-ruu/
It never gives me the HTC logo screen.
C:\Android\com>fastboot flash recovery twrp-2.8.6.1-m8.img
target reported max download size of 1826336768 bytes
sending 'recovery' (17006 KB)...
OKAY [ 1.573s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 11.713s
C:\Android\com>fastboot flash boot boot.img
target reported max download size of 1826336768 bytes
sending 'boot' (10066 KB)...
OKAY [ 1.001s]
writing 'boot'...
FAILED (remote: image update error)
Sorry I've been busy all day,but try to reboot your phone
Sent from my One using XDA Premium 4 mobile app
That brings me back to the fastboot screen
tjamscad said:
That brings me back to the fastboot screen
Click to expand...
Click to collapse
Ok try a dirty flash of a different rom
Sent from my One using XDA Premium 4 mobile app
I can't flash anything. Everything fails.
tjamscad said:
I can't flash anything. Everything fails.
Click to expand...
Click to collapse
What ROM did you have installed when this happened?
Sent from my One M8 using XDA Premium 4 mobile app
Venom 4.3 for Verizon
SD card method should work always as long as you are using fat32 and have the file name exact. If it's not working too aren't doing one of the two above correct.
Sent from my HTC6535LVW using Tapatalk
Like this?
tjamscad said:
Like this?
Click to expand...
Click to collapse
Does it do that everytime you flash it? The same exact output?
Sent from my HTC6535LVW using Tapatalk
Yes
I get this when I do factory reset from the hboot screen. I never see the HTC logo like I should.
Like thi
Please help!!
I have messed up my oneplus one bacon
I was using lineageos 16 and all was fine. For some dumb reason like getting 'Screen mirroring' feature, I decided to go back to lineageos 15.1. Somewhere in the instructions I [mis]read, a clean wipe is recommended to go back to previous release.
I wiped all my partitions from twrp. That's why, my system partition is gone.
I tried a bunch of things after searching on these forums for similar symptoms, but no luck as of yet.
I tried to flash the stock recovery and stock ROM
Recovery flash was successful and so I am on CWM, but the ROM failed as the system partition could not be mounted/unmounted
Now, my phone's state -- I have Cyanogen recovery
ADB devices does not work.
> adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Fastboot works, but am unable to unlock my bootloader, not sure how it got locked.
>fastboot oem unlock
OKAY [ 0.009s]
Finished. Total time: 0.019s
It simple reboots to the recovery without unlocking
>fastboot oem device-info
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.021s]
Finished. Total time: 0.028s
I tried sideload to upload files like stock ROM, I get verification errors.
I was hoping this thread would help me. But not sure how to apply this fix
I am unable to flash or boot as I get the following error
> fastboot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9968 KB)...
OKAY [ 0.317s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.318s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.339s
Please help!!!