need help [urgent]
here I post command from CMD :
++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
++++++++++++++++
C:\android>fastboot flash hboot vivo_downgrade.img
sending 'hboot' (1024 KB)...
OKAY [ 0.421s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.546s
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.172s]
finished. total time: 0.172s
++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
+++++++++++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.16.0000
(bootloader) version-baseband: 3805.09.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.30.707.1
(bootloader) serialno: HT155TD00844
(bootloader) imei: 355301044806969
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3a3895d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++
I cant access RECOVERY MODE
I cant access My ROM/Stock ROM
Help me
wesly.btm said:
need help [urgent]
here I post command from CMD :
++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
++++++++++++++++
C:\android>fastboot flash hboot vivo_downgrade.img
sending 'hboot' (1024 KB)...
OKAY [ 0.421s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.546s
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.172s]
finished. total time: 0.172s
++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
+++++++++++++++++++++++++
C:\android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.16.0000
(bootloader) version-baseband: 3805.09.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.30.707.1
(bootloader) serialno: HT155TD00844
(bootloader) imei: 355301044806969
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3a3895d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++
I cant access RECOVERY MODE
I cant access My ROM/Stock ROM
Help me
Click to expand...
Click to collapse
What are you trying to accomplish? The vivo_downgrade.img is only used when you have Revolutionary S-OFF HBOOT installed. Also, you will only be able to use the 'fastboot flash' command when the bootloader is in the UNLOCKED state. The fact that you LOCKED it before the attempting the 'fastboot flash hboot' command probably saved you from making a huge mistake.
You have 2 options to get your phone operational again.
1. You need to UNLOCK your bootloader again then flash a custom Recovery and then flash a custom ROM.
2. Since you are now RELOCKED, you can take the 2.30.707.1 RUU and run it to return to stock.
You have 2 options to get your phone operational again.
1. You need to UNLOCK your bootloader again then flash a custom Recovery and then flash a custom ROM.
2. Since you are now RELOCKED, you can take the 2.30.707.1 RUU and run it to return to stock.
+++++++++++
pls advise, the link for Item 1 & 2?
thanks,
how to I get S-OFF,
since I cant load to Menu HTC forgot to check Setting > Developer Option > USB Debug
I cant access recovery mode.
wesly.btm said:
You have 2 options to get your phone operational again.
1. You need to UNLOCK your bootloader again then flash a custom Recovery and then flash a custom ROM.
2. Since you are now RELOCKED, you can take the 2.30.707.1 RUU and run it to return to stock.
+++++++++++
pls advise, the link for Item 1 & 2?
thanks,
Click to expand...
Click to collapse
wesly.btm said:
how to I get S-OFF,
since I cant load to Menu HTC forgot to check Setting > Developer Option > USB Debug
I cant access recovery mode.
Click to expand...
Click to collapse
If you want to gain S-OFF, you first will need to do option 1 and then use the Downgrade script.
If you need links, you should search this forum and read the sticky posts. If you have never unlocked the bootloader, then you need to use the procedure at HTCDEV.com. If you have used that procedure, then you can simply use the same unlock_token.bin again to unlock it.
tpbklake said:
If you want to gain S-OFF, you first will need to do option 1 and then use the Downgrade script.
If you need links, you should search this forum and read the sticky posts. If you have never unlocked the bootloader, then you need to use the procedure at HTCDEV.com. If you have used that procedure, then you can simply use the same unlock_token.bin again to unlock it.
Click to expand...
Click to collapse
I need help
short story:
Error when flashing RUU? ERROR [110]: FILE OPEN ERROR
Now, I know the problem was my Desire was S-OFF.
When pull out the USB cable:
[1]SPLASH 1 – OK
[2]USERDATA - OK
[3]SYSTEM - FAIL-PU
[4]RECOVERY - OK
[5]RADIO_CUST - OK
[6]RADIO_V2 - OK
[7]BOOTLOADER - Bypassed
[8]BOOT - OK
Partition update fail!
Update fail!
HTC logo when I turn on the phone with four figures on the squares
After that I tried to flash recovery with fastboot, but I can’t install my backup and the all custom room was frozen on the first boot.
My nandroid beckup:
system: 254MB
data: 128 MB
cache: 2,6 MB
First I tried to flash bravo_alpharev.img but it dosn’t work. The RUU flash was error as well.
I heard that:
flash- fastboot- bravo_downgrader.img
Now the error massege: RUU? ERROR [132]: SIGNATURE ERROR
http://forum.xda-developers.com/showthread.php?t=2214309
Fastboot flash:
[Q] Fastboot 'FAILED (remote: signature verify fail)
http://forum.xda-developers.com/showthread.php?t=1357625
+++++++++++++++++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
++++++++++++++++++++++++++++++++++++++
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
++++++++++++++++
++++++++++++++++++++++++
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: SetRuuNbhUpdate
(bootloader) serialno: SH0C4PL02400
(bootloader) imei: 355302049055073
(bootloader) product: Bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0 I have no displayed this last line
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++++++++
Now I can’t turn on the phone. I can charging the buttery and if I connect the USB cable and my PC , I can use some base function but I can’t flashing.
So put something on the SD an turn on fastboot mode or any other mode is not working for my phone. If I try to turn on I have no nothing on the screen at the moment. Black screen….
I heard maybe I locked the bootloader so….
bootloader (bootloader lock) I try to unlock and I used HTCdev
Windows fail process stopped ect.
What can I do now?
Is there any solution for me?
GeriW said:
I need help
short story:
Error when flashing RUU? ERROR [110]: FILE OPEN ERROR
Now, I know the problem was my Desire was S-OFF.
When pull out the USB cable:
[1]SPLASH 1 – OK
[2]USERDATA - OK
[3]SYSTEM - FAIL-PU
[4]RECOVERY - OK
[5]RADIO_CUST - OK
[6]RADIO_V2 - OK
[7]BOOTLOADER - Bypassed
[8]BOOT - OK
Partition update fail!
Update fail!
HTC logo when I turn on the phone with four figures on the squares
After that I tried to flash recovery with fastboot, but I can’t install my backup and the all custom room was frozen on the first boot.
My nandroid beckup:
system: 254MB
data: 128 MB
cache: 2,6 MB
First I tried to flash bravo_alpharev.img but it dosn’t work. The RUU flash was error as well.
I heard that:
flash- fastboot- bravo_downgrader.img
Now the error massege: RUU? ERROR [132]: SIGNATURE ERROR
http://forum.xda-developers.com/showthread.php?t=2214309
Fastboot flash:
[Q] Fastboot 'FAILED (remote: signature verify fail)
http://forum.xda-developers.com/showthread.php?t=1357625
+++++++++++++++++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
++++++++++++++++++++++++++++++++++++++
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
++++++++++++++++
++++++++++++++++++++++++
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.80.0000
(bootloader) version-baseband: 4.06.00.02_2
(bootloader) version-cpld: None
(bootloader) version-microp: 051d
(bootloader) version-main: SetRuuNbhUpdate
(bootloader) serialno: SH0C4PL02400
(bootloader) imei: 355302049055073
(bootloader) product: Bravo
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB9920000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3991mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6175d920
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0 I have no displayed this last line
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++++++++
Now I can’t turn on the phone. I can charging the buttery and if I connect the USB cable and my PC , I can use some base function but I can’t flashing.
So put something on the SD an turn on fastboot mode or any other mode is not working for my phone. If I try to turn on I have no nothing on the screen at the moment. Black screen….
I heard maybe I locked the bootloader so….
bootloader (bootloader lock)I try to unlock and I used HTCdev
Windows fail process stopped ect.
What can I do now?
Is there any solution for me?
Click to expand...
Click to collapse
Why do you reply to a thread that is more than a year old?
As well as this, you have posted in the wrong device forum. This is for the HTC Incredible S, not the HTC Desire xD
You may have better luck in the Desire forum
Sent from my Nexus 5
I achieved S-OFF with rumrunner on m HTC 802d (Dual-Sim) variant. Reading around threads I realized that its ok to flash anything with S-OFF so decided to flash RUU Zip M7 HTC Google Edition_3.06.1700.10. However suddenly the phone switched off and I had an error on the fastboot screen. I tried to issue the command again but it did not work. The phone's display did not start no matter what I tried. Prior to flashing I had set supercid 11111111 on my device.
Things I tried:
1. Holding power button for 90 seconds or more, restarting. It only shows connectivity in fastboot. However when I issue command fastboot devices, I get this:
???????????? fastboot
2. Trying to unlock boot loader with fastboot flash unlocktoken Unlock_code.bin. Result:
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.007s
3. I tried to generate a new key and unlock it again at HTCDev but I get an error with the new identifier.
4. Tried flashing custom recovery. Result:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (16383 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.830s
5. Tried to re-run the RUU mode and flash, but the phone restarts and gets struck without returning. Output:
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: -1
OKAY [ 0.035s]
finished. total time: 0.036s
C:\fastboot>fastboot getvar all
< waiting for device >
6. Tried clearing cache: fastboot erase cache. Output:
C:\fastboot>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.001s
7. Tried running stock RUU (exe), but it gets struck on "Verifying information on your Android phone..." forever.
8. Tried flashing the zip directly. Result:
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (428998 KB)...
OKAY [ 21.698s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 21.701s
9. Issued the lock command
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.002s
10. fastboot getvar all commands gives this:
C:\fastboot>fastboot getvar all
(bootloader) version-bootloader: 1.54.0000 <- earlier to attempting the flash this was 2.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: myimeinumber
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
As you can see some fields are blank.
----
Please help me!
juicylife said:
I achieved S-OFF with rumrunner on m HTC 802d (Dual-Sim) variant. Reading around threads I realized that its ok to flash anything with S-OFF so decided to flash RUU Zip M7 HTC Google Edition_3.06.1700.10. However suddenly the phone switched off and I had an error on the fastboot screen. I tried to issue the command again but it did not work. The phone's display did not start no matter what I tried. Prior to flashing I had set supercid 11111111 on my device.
Things I tried:
1. Holding power button for 90 seconds or more, restarting. It only shows connectivity in fastboot. However when I issue command fastboot devices, I get this:
???????????? fastboot
2. Trying to unlock boot loader with fastboot flash unlocktoken Unlock_code.bin. Result:
C:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.007s
3. I tried to generate a new key and unlock it again at HTCDev but I get an error with the new identifier.
4. Tried flashing custom recovery. Result:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (16383 KB)...
OKAY [ 0.828s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.830s
5. Tried to re-run the RUU mode and flash, but the phone restarts and gets struck without returning. Output:
C:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: -1
OKAY [ 0.035s]
finished. total time: 0.036s
C:\fastboot>fastboot getvar all
< waiting for device >
6. Tried clearing cache: fastboot erase cache. Output:
C:\fastboot>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.001s
7. Tried running stock RUU (exe), but it gets struck on "Verifying information on your Android phone..." forever.
8. Tried flashing the zip directly. Result:
C:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (428998 KB)...
OKAY [ 21.698s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 21.701s
9. Issued the lock command
C:\fastboot>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.001s]
finished. total time: 0.002s
10. fastboot getvar all commands gives this:
C:\fastboot>fastboot getvar all
(bootloader) version-bootloader: 1.54.0000 <- earlier to attempting the flash this was 2.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: myimeinumber
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
As you can see some fields are blank.
----
Please help me!
Click to expand...
Click to collapse
I got the same problem here! Did you find how to fix?
pdpascal said:
I got the same problem here! Did you find how to fix?
Click to expand...
Click to collapse
Would you mind posting what you get from "fastboot getvar all" but with your imei and MID removed? I may be able to help you
LightSpeedIII said:
Would you mind posting what you get from "fastboot getvar all" but with your imei and MID removed? I may be able to help you
Click to expand...
Click to collapse
Sure!
fastboot devices:
???????????? fastboot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) meid: 00000000000000 (I tried to change the MID, my is the Chinese model. I used the Europe model MID to be able to apply the firmware)
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 2703mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!./f
Thank you do much!
pdpascal said:
Sure!
fastboot devices:
???????????? fastboot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) meid: 00000000000000 (I tried to change the MID, my is the Chinese model. I used the Europe model MID to be able to apply the firmware)
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 2703mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!./f
Thank you do much!
Click to expand...
Click to collapse
The issue of the original thread starter "juicylife" is LOCKED bootloader, that's why he can't flash stock or custom recoveries and some ADB commands that needs unlocked bootloader will not work!
You are S-Off that's good.
1. Do you remember your original CID# or your software version? it is important to know from what region you belong.
2. Can you still access Fastboot or Recovery Menu?
eyeyousee said:
The issue of the original thread starter "juicylife" is LOCKED bootloader, that's why he can't flash stock or custom recoveries and some ADB commands that needs unlocked bootloader will not work!
You are S-Off that's good.
1. Do you remember your original CID# or your software version? it is important to know from what region you belong.
2. Can you still access Fastboot or Recovery Menu?
Click to expand...
Click to collapse
Hi there!
Mine is
M7C_DUG – Device ID: HTC 802w
Networks: Dual Sim W-CDMA/GSM
MID: PN0771000
Region: China, Russia, Europe
The problem is when I try "fastboot oem rebootRUU" :
...
(bootloader) Start Verify: -1
OKAY [ 0.043s]
finished. total time: 0.043s
If I try "fastboot flash zip room.zip":
OKAY [ 0.850s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.851s
It was HBoot 2.49 as well. Seems that after start the flash firmware process the phone's hardware is no longer recognized, the display for instance is not. Perhaps the eMMC needs a JTAG?
I will start from the beginning. I messed up and wiped my htc one completely. (with no backup done prior)
SO after reading numerous threads/how to I still can not get anything to work.
I have been using toolkit v3.1 but the thing is my computer does not reconize my phone...well it will in fastboot mode but not in bootloader or twrp recovery so I cannot go into recovery to just install a new ROM.
So i have been trying to get it back to stock but I am getting the same error message.
So this is my info.
RELOCKED
M7-UL PVT SHIP S-OFF RH
CID-TELUS001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
openDSP-v26.120.274.0202
eMMC-boot
this is the RUU which I thought might work ,guru_reset_m7_3-22-661-1-zip, from htc1guru but then i get this
< waiting for device >
sending 'zip' (1104738 KB)...
OKAY [ 45.937s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.857s
C:\Users\Home\Desktop\One_All-In-One_Kit_v\data>
only thing i havent tried is using a OTG USB cable, which I dont own, but I am going to get one tomorrow if I can find one in town.
Maybe I am missing something. You mentioned about flashing a RUU not running it off of a zip? How do I do that? I am trying to use the flash factory RUU zip from the toolkit program and thats when I get the error above. Maybe I am not using the right RUU?
should add I tried using the fastboot manually and got this
c:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
c:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (428998 KB)...
OKAY [ 18.467s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 18.955s
c:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (428998 KB)...
OKAY [ 18.464s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 18.954s
c:\fastboot>
after reading some more threads I have this info
c:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxx
(bootloader) meid: 00xxxxxxxxxxxxxx
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
So I tired finding a RUU but cant seem to find a exact one.
So where do I go from here?
The guru reset file you downloaded appears to be the right one, the problem is, you flashing it the wrong way.
You must have TWRP recovery on your phone, the preferred and most reliable version is 2.6.3.3, then you must put that guru reset file on your internal storage and flash it from within TWRP recovery like you would do with a custom rom, select install in TWRP and then select the guru reset file, swipe to install and follow the instructions.
rescue119 said:
I will start from the beginning. I messed up and wiped my htc one completely. (with no backup done prior)
SO after reading numerous threads/how to I still can not get anything to work.
I have been using toolkit v3.1 but the thing is my computer does not reconize my phone...well it will in fastboot mode but not in bootloader or twrp recovery so I cannot go into recovery to just install a new ROM.
So i have been trying to get it back to stock but I am getting the same error message.
So this is my info.
RELOCKED
M7-UL PVT SHIP S-OFF RH
CID-TELUS001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
openDSP-v26.120.274.0202
eMMC-boot
this is the RUU which I thought might work ,guru_reset_m7_3-22-661-1-zip, from htc1guru but then i get this
< waiting for device >
sending 'zip' (1104738 KB)...
OKAY [ 45.937s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.857s
C:\Users\Home\Desktop\One_All-In-One_Kit_v\data>
only thing i havent tried is using a OTG USB cable, which I dont own, but I am going to get one tomorrow if I can find one in town.
Maybe I am missing something. You mentioned about flashing a RUU not running it off of a zip? How do I do that? I am trying to use the flash factory RUU zip from the toolkit program and thats when I get the error above. Maybe I am not using the right RUU?
should add I tried using the fastboot manually and got this
c:\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
c:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (428998 KB)...
OKAY [ 18.467s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 18.955s
c:\fastboot>fastboot flash zip RUU.zip
sending 'zip' (428998 KB)...
OKAY [ 18.464s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 18.954s
c:\fastboot>
after reading some more threads I have this info
c:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxx
(bootloader) meid: 00xxxxxxxxxxxxxx
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
So I tired finding a RUU but cant seem to find a exact one.
So where do I go from here?
Click to expand...
Click to collapse
Got it working. found the thread where you basically change the CID to something else, then add a RUU for that CID then switch it back. Seems to be working now.
I'm trying to RUU a sprint htc one m8, I am htcdev unlocked, and currently running sinless rom 3.4.2, and the latest TWRP, now I know I must relock my bootloader in order to RUU and I already tried that.
here is my output when I run fastboot oem lock
Code:
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.251s
but on the bootloader I see the tampered flag and re-locked flag with "security warning below
now here's my "getvar all"
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.08.20.0612_4
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: **was actually blank**
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **censored**
(bootloader) imei: **censored**
(bootloader) imei2: Not Support
(bootloader) meid: 99000499040678
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d4c3cae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
here is what happened when I tried to flash the full firmware from O.M.J.'s post
Code:
target reported max download size of 1830612992 bytes
sending 'zip' (6598 KB)...
OKAY [ 0.807s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.046s
and here is the output when i try to flash the rom.zip I extracted from htc's newest RUU exe
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s
any help is appreciated
What happened when you tried to run the RUU once you relocked your bootloader?
Magnum_Enforcer said:
What happened when you tried to run the RUU once you relocked your bootloader?
Click to expand...
Click to collapse
I did relocked before running the RUU the out put was this
Code:
./fastboot flash zip rom.zip
target reported max download size of 1830612992 bytes
sending 'zip' (1652270 KB)...
OKAY [ 47.785s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 108.972s
I got the "rom.zip" from htc's RUU exe
Managed to RUU through parallels desktop, here's what I did:
I relocked my bootloader (after doing this I got stucked on the bootloader)
I started parallels desktop on my mac and connected my phone in bootloader mode, assigning the device to the virtual machine
I ran the RUU exe (everything went fine)
profit
Hello,
I've obtained m7 online "with software issue" - looks like it's totally boned now.
****Tampered****
****Relocked****
****Security warning****
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.29.3218.08
version-cpld: None
version-microp: None
version-main: 6.09.401.5
version-misc: PVT SHIP S-ON
serialno: SH3BR********
imei: *******************
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4271mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
I've only got access to boatloader and fastboot. If I try to access recovery - goes back to boatloader immediately.
If I flash anything - recovery etc:
>fastboot flash recovery recovery-clockwork-touch-6.0.4.8-m7.img
target reported max download size of 1507573760 bytes
sending 'recovery' (8758 KB)...
OKAY [ 1.063s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.535s
Always get same error - FAILED (remote: signature verify fail). Is this because s-on? or boatloader issue?
Tried flashing RUUs, OTAs, firmawares, Guru_Reset_M7_**** with no luck.
Am I totally boned and last thing to do is either use m7 as door stopper?
My daily driver is m8. So i can wait for correct RUU (was not able to find with correct radio). Just for sport interests - is there anything else I can do?
Like compiling and pushing whole image to boot on?
dd=if dd=of if correct image obtained?
It looks to me that partitions are corrupt and phone has boatloader issue.
edvinas.bitinas said:
****Tampered****
****Relocked****
****Security warning****
version-bootloader: 1.57.0000
version-baseband: 4T.29.3218.08
version-main: 6.09.401.5
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0710000
cidnum: HTC__Y13
>fastboot flash recovery recovery-clockwork-touch-6.0.4.8-m7.img
target reported max download size of 1507573760 bytes
sending 'recovery' (8758 KB)...
OKAY [ 1.063s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.535s
Click to expand...
Click to collapse
You must unlock the bootloader to flash a custom recovery hence the failed signature verification...
Well can unloack boot loader from fastboot with no recovery?
from forums and other posts looks like I can't with s-on.
edvinas.bitinas said:
Well can unloack boot loader from fastboot with no recovery?
from forums and other posts looks like I can't with s-on.
Click to expand...
Click to collapse
Sure you can just follow the instructions here >> http://www.htcdev.com/bootloader
clsA said:
Sure you can just follow the instructions here >> http://www.htcdev.com/bootloader
Click to expand...
Click to collapse
I've tried multiple times - does not work.
also boot loader was previously unlocked - did not worked also. Tried flashing recovery - did not worked.
Is there any way to reflash boatloader itself?
edvinas.bitinas said:
I've tried multiple times - does not work.
also boot loader was previously unlocked - did not worked also. Tried flashing recovery - did not worked.
Is there any way to reflash boatloader itself?
Click to expand...
Click to collapse
yeah you can update the bootloader with a firmware flash
here >>http://darkforest-roms.co.uk/Firmware/HTC One/6.09.401.5/6.09.401.5 firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
clsA said:
yeah you can update the bootloader with a firmware flash
here >> https://www.androidfilehost.com/?fid=23622183712465451
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Should it work with s-on on:
bootloader: 1.57.0000
baseband: 4T.29.3218.08
main: 6.09.401.5
modelid: PN0710000
cidnum: HTC__Y13
I've tried couple for same modelid and cids - no luck so far.
fw_6.09.401.5_custom.zip
>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.047s
>fastboot flash zip fw_6.09.401.5
_custom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (29595 KB)...
OKAY [ 2.234s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.678s
>fastboot flash zip fw_6.09.401.5
_custom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (29595 KB)...
OKAY [ 2.234s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.687s
Update since link updated:
6.09.401.5 firmware
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.414s]
finished. total time: 0.414s
>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.027s]
finished. total time: 0.027s
>fastboot flash zip "6.09.401.5
irmware.zip"
target reported max download size of 1514139648 bytes
sending 'zip' (44368 KB)...
OKAY [ 2.611s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 10.494s
>fastboot flash zip "6.09.401.5
irmware.zip"
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'zip' (44368 KB)...
OKAY [ 2.604s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,23
(bootloader) [RUU]UZ,boot,34
(bootloader) [RUU]UZ,boot,46
(bootloader) [RUU]UZ,boot,59
(bootloader) [RUU]UZ,boot,72
(bootloader) [RUU]UZ,boot,84
(bootloader) [RUU]UZ,boot,98
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,6
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,28
(bootloader) [RUU]UZ,recovery,38
(bootloader) [RUU]UZ,recovery,44
(bootloader) [RUU]UZ,recovery,49
(bootloader) [RUU]UZ,recovery,66
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,78
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,95
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,28
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,92
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,23
(bootloader) [RUU]WP,radio,46
(bootloader) [RUU]WP,radio,69
(bootloader) [RUU]WP,radio,92
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
OKAY [ 23.065s]
finished. total time: 25.669s
Mate - Where the hell did you found this zip? I was on google for 30 hours - did not achieved this yet!!
Now looks like it's stuck on oemRUU update - progress bar is stuck on 80% for some time, is normal? Should I wait or fastboot reboot?
So after waiting 30 minutes I've rebooted the device.
Tried to update firmware once again - same results - no errors in cmd but progress bar does not complete on phone, stays at 90%.
So next - I've successfully unlocked the boot loader by htcdev site - then tried to install twrp recovery:
>fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11992 KB)...
OKAY [ 1.480s]
writing 'recovery'...
OKAY [ 0.843s]
finished. total time: 2.325s
Looks good - but when I try to access recovery phone enters reboot loop. What to do next?
*****TAMPERED*****
*****UNLOCKED*****
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.29.3218.08
version-cpld: None
version-microp: None
version-main: 6.09.401.5
version-misc: PVT SHIP S-ON
serialno: SH3BR*******
imei: ******************
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4338mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Update:
Also tried http://forum.xda-developers.com/showthread.php?t=2545227 stock recovery - no luck. Same situation
edvinas.bitinas said:
So after waiting 30 minutes I've rebooted the device.
Tried to update firmware once again - same results - no errors in cmd but progress bar does not complete on phone, stays at 90%.
So next - I've successfully unlocked the boot loader by htcdev site - then tried to install twrp recovery:
>fastboot flash recovery openrecovery-twrp-2.8.5.0-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11992 KB)...
OKAY [ 1.480s]
writing 'recovery'...
OKAY [ 0.843s]
finished. total time: 2.325s
Looks good - but when I try to access recovery phone enters reboot loop. What to do next?
*****TAMPERED*****
*****UNLOCKED*****
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.29.3218.08
version-cpld: None
version-microp: None
version-main: 6.09.401.5
version-misc: PVT SHIP S-ON
serialno: SH3BR*******
imei: ******************
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4338mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Update:
Also tried http://forum.xda-developers.com/showthread.php?t=2545227 stock recovery - no luck. Same situation
Click to expand...
Click to collapse
Sorry I had to step out
Flashing the firmware never gets to 100% just reboot when you see finished at the end of the flash
what you need to do is after flashing the firmware, enter stock recovery and do a factory reset (not from the bootloader from stock recovery)
After that flash TWRP 2.6.3.3 from here >> http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
I assume stock recovery should be available after firmware flash?
Update: Flashed FW - rebooted to boot-loader -> recovery -> got reboot loop
Done this 3 times - same results. If I enter recovery -> reboot loop.
edvinas.bitinas said:
I assume stock recovery should be available after firmware flash?
Update: Flashed FW - rebooted to boot-loader -> recovery -> got reboot loop
Done this 3 times - same results. If I enter recovery -> reboot loop.
Click to expand...
Click to collapse
Well I'm not sure what's going on then .. never seen a phone that won't load stock recovery
seems like your partitions are damaged maybe @nkk71 knows a trick you can try
A view days ago I had exactly the same problem.
Only unlocking via htcdev.com worked.
I see you olso have s-on.
Well HTC dev boot loader unlock works for me too. And yes, s-on.
what did you to resolve your issue?
In my opinion you cant flash firmware with s-on.
You only can flash recovery's.
So flash a recovery, TWRP is the best I think.
via ADB push a SMALL supported rom.
try to S-off with Sunshine.
Afterwards try to flash firmware.
You can only try to flash ROMS and Firmware with S-On.
That the big problem I'm in too.
clsA said:
Well I'm not sure what's going on then .. never seen a phone that won't load stock recovery
seems like your partitions are damaged maybe @nkk71 knows a trick you can try
Click to expand...
Click to collapse
maybe he used a wrong version?
nkk71 said:
maybe he used a wrong version?
Click to expand...
Click to collapse
No idea guys, I just blindly followed the link to be honest. And it first firmware which was accepted by my phone.
I believe it's possible to format recovery partition but I need s-off for that.
Since recovery is not working - there is no way to obtain s-off.
Any other ideas what to try? Would be great to restore the phone to official ROM/Recovery - would be able to do rest on my own.
edvinas.bitinas said:
No idea guys, I just blindly followed the link to be honest. And it first firmware which was accepted by my phone.
I believe it's possible to format recovery partition but I need s-off for that.
Since recovery is not working - there is no way to obtain s-off.
Any other ideas what to try? Would be great to restore the phone to official ROM/Recovery - would be able to do rest on my own.
Click to expand...
Click to collapse
Try this firmware >> https://www.androidfilehost.com/?fid=95864024717071877
clsA said:
Try this firmware >> https://www.androidfilehost.com/?fid=95864024717071877
Click to expand...
Click to collapse
I'm using "Minimal ADB and Fastboot" collection for fastboot.exe (not sure if there is any difference in versions or sources if it works)
So: tried with unlocked boot-loader and re-locked - same error (FYI previous FW flashed only with re-locked boot loader [it seemed to])
Unlocked:
>fastboot flash zip 6.09.401.12-FULL_STOCK_WIPE.zip
target reported max download size of 1514139648 bytes
sending 'zip' (550870 KB)...
OKAY [ 20.649s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 20.899s
Locked
>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
(bootloader) Use PSHOLD to reset device.4642044 (0x1FDDFD7C)
FAILED (unknown status code) (after reboot it states - bootloader re-locked)
finished. total time: 1.188s
>fastboot erase cache
>fastboot oem rebootRUU
>fastboot flash zip 6.09.401.12-FULL_STOCK_WIPE.zip
target reported max download size of 1514139648 bytes
sending 'zip' (550870 KB)...
OKAY [ 20.651s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 82.426s
By what do you check the FW which should fit me? in .zips android-info file should contain my modelid, cid HTC__Y13cidnum?
I've been comparing the files you linked me - all should fit if nothing else should be checked (radio, hboot)
edvinas.bitinas said:
I'm using "Minimal ADB and Fastboot" collection for fastboot.exe (not sure if there is any difference in versions or sources if it works)
So: tried with unlocked boot-loader and re-locked - same error (FYI previous FW flashed only with re-locked boot loader [it seemed to])
Unlocked:
>fastboot flash zip 6.09.401.12-FULL_STOCK_WIPE.zip
target reported max download size of 1514139648 bytes
sending 'zip' (550870 KB)...
OKAY [ 20.649s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 20.899s
Locked
>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
(bootloader) Use PSHOLD to reset device.4642044 (0x1FDDFD7C)
FAILED (unknown status code) (after reboot it states - bootloader re-locked)
finished. total time: 1.188s
>fastboot erase cache
>fastboot oem rebootRUU
>fastboot flash zip 6.09.401.12-FULL_STOCK_WIPE.zip
target reported max download size of 1514139648 bytes
sending 'zip' (550870 KB)...
OKAY [ 20.651s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 82.426s
By what do you check the FW which should fit me? in .zips android-info file should contain my modelid, cid HTC__Y13cidnum?
I've been comparing the files you linked me - all should fit if nothing else should be checked (radio, hboot)
Click to expand...
Click to collapse
maybe too much of a jump up you can flash them all in order from 401.5 and up
https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml
18.08.2014 6.09.401.5
http://www.androidfilehost.com/?fid=23622183712458601
01322221a25ad267bcfd328da08e8221 m7_ul Stock
55
28.10.2014 6.09.401.10
https://www.androidfilehost.com/?fid=95784891001603470
fe00c48e3b4864ad4c616d6ec5c9e71c m7_ul Stock
56
03.12.2014 6.09.401.11
https://www.androidfilehost.com/?fid=95832962473396760
7f8ce90cb1f52d1eacddc46c0293340a m7_ul Stock
57
29.12.2014 6.09.401.12
https://www.androidfilehost.com/?fid=95864024717071877
6d742627973c22088803dae931197936 m7_ul Stock
58
17.01.2015 7.15.401.1
https://www.androidfilehost.com/?fid=95897840722644709
d33a4d3f35c2369e133b76c4f3a552bf m7_ul Stock
59
23.02.2015 7.19.401.2
https://www.androidfilehost.com/?fid=95916177934533542
5f594f9b660ba281b2d346c39f654d1d m7_ul Stock
clsA said:
maybe too much of a jump up you can flash them all in order from 401.5 and up
https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml
18.08.2014 6.09.401.5
http://www.androidfilehost.com/?fid=23622183712458601
01322221a25ad267bcfd328da08e8221 m7_ul Stock
55
28.10.2014 6.09.401.10
https://www.androidfilehost.com/?fid=95784891001603470
fe00c48e3b4864ad4c616d6ec5c9e71c m7_ul Stock
56
03.12.2014 6.09.401.11
https://www.androidfilehost.com/?fid=95832962473396760
7f8ce90cb1f52d1eacddc46c0293340a m7_ul Stock
57
29.12.2014 6.09.401.12
https://www.androidfilehost.com/?fid=95864024717071877
6d742627973c22088803dae931197936 m7_ul Stock
58
17.01.2015 7.15.401.1
https://www.androidfilehost.com/?fid=95897840722644709
d33a4d3f35c2369e133b76c4f3a552bf m7_ul Stock
59
23.02.2015 7.19.401.2
https://www.androidfilehost.com/?fid=95916177934533542
5f594f9b660ba281b2d346c39f654d1d m7_ul Stock
Click to expand...
Click to collapse
the "....FULL_STOCK_WIPE.zip" arent signed .. not sure why he/they name them "FULL_STOCK_WIPE.zip" but they arent