Hi everyone, I've brick HTC One. Now it stuck on fastboot mode but the screen is always black even I try to hold power button or power + volume down. I can use fastboot, but seem like it has relock bootloader so I can't do any thing like RUU or recovery....
Here is fastboot getvar all. All phone info has been changed( like imei...) or missed
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.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: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4207mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also I can't flash unlock token
Code:
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.009s
So anyone know how to put it to QHSUSB_DLOAD mode. I can try linux to unbrick it . Thanks so much
Have you tried the RUU and if so what error did you get? I always run my RUU from fastboot.
Sent from my HTC One_M8 using XDA Free mobile app
legion423 said:
Hi everyone, I've brick HTC One. Now it stuck on fastboot mode but the screen is always black even I try to hold power button or power + volume down. I can use fastboot, but seem like it has relock bootloader so I can't do any thing like RUU or recovery....
Here is fastboot getvar all. All phone info has been changed( like imei...) or missed
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.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: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4207mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also I can't flash unlock token
Code:
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.009s
So anyone know how to put it to QHSUSB_DLOAD mode. I can try linux to unbrick it . Thanks so much
Click to expand...
Click to collapse
It shows it's s-off so flashing an ruu should be possible with or without a relocked boot loader. Do you remember your original CID and MID?
You if you can flash firmware it may be possible to forece QHSUSB_DLOAD but it won't necessarily help and you need to know the cid mid. @nkk71 knows more about this than I do, I've only seen this once before and it didn't get fixed
need more info, how did this happen.... messing around with MID by any chance?
Like I've said, I can't use RUU or recovery
Code:
C:\adt-bundle-windows-x86_64-20140624\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: -1
(bootloader) SD: write failed in CMD25.
OKAY [ 1.068s]
finished. total time: 1.069s
. I didn't do anything, the phone auto turn into black screen with no OS, no recovery, Just can go to Hboot, but now after run some fastboot command like rebootRUU ... when reboot-bootloader, the screen is black too
legion423 said:
So anyone know how to put it to QHSUSB_DLOAD mode. I can try linux to unbrick it . Thanks so much
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2363516
http://forum.xda-developers.com/showthread.php?t=2770684
yatindroid said:
http://forum.xda-developers.com/showthread.php?t=2363516
http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
My question is how to put it into QHSUSB_DLOAD mode, 2 topics you give are only working if your phone is in QHSUSB_DLOAD mode.
Anyway thanks you guys for help. I've sent my phone to store, they can use the RIFF BOX to repair boot
legion423 said:
My question is how to put it into QHSUSB_DLOAD mode, 2 topics you give are only working if your phone is in QHSUSB_DLOAD mode.
Anyway thanks you guys for help. I've sent my phone to store, they can use the RIFF BOX to repair boot
Click to expand...
Click to collapse
I think sending for Riff box repair was probably the best course of action. Forcing QHSUSB_DLOAD as i said probably wouldn't help. In fact would most likely make it worse.
You need to flash firmware to get out of QHSUSB_DLOAD but getting it to that state wouldn't restore you MID, CID IMEI, Version main and so on. So flashing firmware still wouldn't work. :good: That's the reason you didn't get an answer to that question no one wants to help make it worse.
For the record QHSUSB_DLOAD is caused by skipping firmware updates so to do it you would still need to flash firmware. e.g If the device has 2.24.401.1 firmware and you flash a firmware 6.09.401.5 from an OTA that would almost certainly put the device in QHSUSB_DLOAD. The Unbrick project merely repairs the emmc enabling you to get to the bootloader to flash the correct firmware to repair this missing parts of the firmware. In this case it would probably just bring you back to the same problem or simply wouldn't work giving you a "device not found" error
Related
after unlocking bootloader of my inc s via htcdev method and installed many different Roms without problems i accidentally managed to relock it with security warning when i tried to downgrade my hboot version with revolutionary (from hboot 2.00).
then i managed to unlock the bootloader again but this time i cant boot into rom at all. i tried flashing the rom again, the boot.img file but still i was stuck on the black screen with dark blue text : "android". i pull out the battery, i can go into hboot menu, and can get into recovery too but i dont know what to do to boot into the rom itself ??
any help would be appreciated. :crying:
anonymousss said:
after unlocking bootloader of my inc s via htcdev method and installed many different Roms without problems i accidentally managed to relock it with security warning when i tried to downgrade my hboot version with revolutionary (from hboot 2.00).
then i managed to unlock the bootloader again but this time i cant boot into rom at all. i tried flashing the rom again, the boot.img file but still i was stuck on the black screen with dark blue text : "android". i pull out the battery, i can go into hboot menu, and can get into recovery too but i dont know what to do to boot into the rom itself ??
any help would be appreciated. :crying:
Click to expand...
Click to collapse
Output of "fastboot getvar all"?
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.00.000.0
(bootloader) serialno: HT185TD01005
(bootloader) imei: 358000042405843
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
is that what u want ?
anonymousss said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.00.000.0
(bootloader) serialno: HT185TD01005
(bootloader) imei: 358000042405843
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
is that what u want ?
Click to expand...
Click to collapse
OK, as I suspected, when you ran the downgrade script originally, it was able to modify the version-main to 2.00.000.0, so you can now RELOCK the bootloader and then run the downgrade RUU documented in the script procedure.
After that you should be good to run Revolutionary.io to gain S-OFF.
i relocked the bootloader then i ran the ruu file again
this time it waited like two mins, then
error 171, usb connection error
plz make sure my phone is turned on and connected properly
now what??
EDIT: now i am relocked without security warning
do i unlock the bootloader again using htcdev method?
EDIT: security warning reappeared
anonymousss said:
i relocked the bootloader then i ran the ruu file again
this time it waited like two mins, then
error 171, usb connection error
plz make sure my phone is turned on and connected properly
now what??
Click to expand...
Click to collapse
No, the bootloader needs to be RELOCKED to run a RUU.
Do you have HTC Sync running in the System Tray by any chance?
Also sounds like you probably just need to extract the ROM.zip from %TEMP% directory and copy it to your SD card and rename it PG32IMG.zip and let the bootloader flash the RUU/ROM.
ok i really didnt understand what u meant
can u plz explain a little bit more ?
htc sync is uninstalled and no its not there in system tray
anonymousss said:
ok i really didnt understand what u meant
can u plz explain a little bit more ?
htc sync is uninstalled and no its not there in system tray
Click to expand...
Click to collapse
Search this forum for "RUU ROM.zip PG32IMG.zip" and you can read and learn about what I'm talking about.
Here is one of the posts that you should find with that search:
http://forum.xda-developers.com/showpost.php?p=30735775&postcount=16
man u wont believe it
i went to properties of the ruu file and found out that it was blocked by the windows so i unblocked it and ran the ruu file again
and i am waiting
this time i saw a progress bar on my phone under the white htc
anonymousss said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.00.000.0
(bootloader) serialno: HT185TD01005
(bootloader) imei: 358000042405843
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4200mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.009s
is that what u want ?
Click to expand...
Click to collapse
anonymousss said:
man u wont believe it
i went to properties of the ruu file and found out that it was blocked by the windows so i unblocked it and ran the ruu file again
and i am waiting
this time i saw a progress bar on my phone under the white htc
Click to expand...
Click to collapse
OK, so if you had posted the output of "fastboot getvar all" 4 hours ago like I had asked for originally, we probably could have had you going by now...
it worked !!!
thanks a lot for your help man !!!!
I was just done doing an s-off and getting ready to flash to boost when all of a sudden blank...black screen...
didnt panic until adb devices said no devices checked my device manager and it was sill there...
now when i do fastboot devices i get ??????????? fastboot....
tried RUU and i get stuck on checking the information on your pda
tried flashing through fast boot and i get remote not allowed...this is my get var results
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.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: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3418mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
any hope for me ...?
thanx for your help in advance....
yikes
this is scarry....
perfectlywireless said:
I was just done doing an s-off and getting ready to flash to boost when all of a sudden blank...black screen...
didnt panic until adb devices said no devices checked my device manager and it was sill there...
now when i do fastboot devices i get ??????????? fastboot....
tried RUU and i get stuck on checking the information on your pda
tried flashing through fast boot and i get remote not allowed...this is my get var results
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.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: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3418mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
any hope for me ...?
thanx for your help in advance....
Click to expand...
Click to collapse
Not sure I can help you out... but you can help the community out by letting us know what the conditions were when you did this. Such as, were you running a custom ROM? Etc...
mrinehart93 said:
Not sure I can help you out... but you can help the community out by letting us know what the conditions were when you did this. Such as, were you running a custom ROM? Etc...
Click to expand...
Click to collapse
did you check the ruu folder to make sure its the ruu you flash and that it doesn't contain a setup.exe file to run?
I believe the encrypted ruu contains an exe file
conditions
wranglerray said:
did you check the ruu folder to make sure its the ruu you flash and that it doesn't contain a setup.exe file to run?
I believe the encrypted ruu contains an exe file
Click to expand...
Click to collapse
I was rooted and removed sprint security, i was soff running phils recovery and super cid...
the ruu does have a setup...ive installed ruu before without the setup through fastboot but everytime i fastboot a command
i get remote not allowed....im stuck...
perfectlywireless said:
I was rooted and removed sprint security, i was soff running phils recovery and super cid...
the ruu does have a setup...ive installed ruu before without the setup through fastboot but everytime i fastboot a command
i get remote not allowed....im stuck...
Click to expand...
Click to collapse
not stuck.
extract the ruu
run the fastboot command
fastboot oem rebootRUU
run the setup file....
but it disapears...
wranglerray said:
not stuck.
extract the ruu
run the fastboot command
fastboot oem rebootRUU
run the setup file....
Click to expand...
Click to collapse
Ok ill try but when i run that command the adb device dissapears from my device manager...
my battery is low now i, charging even though no lights come on...
ill leave it on the charger for a while then ill try running the command.
thanx
perfectlywireless said:
Ok ill try but when i run that command the adb device dissapears from my device manager...
my battery is low now i, charging even though no lights come on...
ill leave it on the charger for a while then ill try running the command.
thanx
Click to expand...
Click to collapse
adb devices only works while booted to OS or recovery
fastboot devices while in bootloader
update
When i type fastboot oem rebootRUU my device dissappears from the device manager..
i typed oem boot and heres what i got... what can i do..??
C:\18\platform-tools_r16.0.1-windows\platform-tools>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.000s]
finished. total time: 0.000s
Hi, I have been hunting around and cant seem to resolve this problem.
Yesterday my phone locked up (blank screen) and so I hard reset it.
I was not doing anything with it at them time (in my pocket).
It would then only boot into the bootloader, no recovery.
I have been running CM nightlies with no problem up until now.
I have been running custom roms for a number of years, but would still say that I have limited knowledge.
Outline of Issue
ADB returns an error for every command
Fastboot will see the device, and provide a getvar but returns an error when i try to push a recovery image
I think i have been able to get into RUU (reboots and screen goes black) as i can still get basic fastboot command returns.
No other commands seem to work.
I have gone through a number of guides and used a few different tools but to no avail. (best of all im on the other side of the world from home so cant even use my old phone)
This is what Getvar returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.044s
note the failed line at the bottom.
I have also checked drivers, uninstalled them and reinstalled the naked drivers.
Any advice would be appreciated.
LTP88 said:
Hi, I have been hunting around and cant seem to resolve this problem.
Yesterday my phone locked up (blank screen) and so I hard reset it.
I was not doing anything with it at them time (in my pocket).
It would then only boot into the bootloader, no recovery.
I have been running CM nightlies with no problem up until now.
I have been running custom roms for a number of years, but would still say that I have limited knowledge.
Outline of Issue
ADB returns an error for every command
Fastboot will see the device, and provide a getvar but returns an error when i try to push a recovery image
I think i have been able to get into RUU (reboots and screen goes black) as i can still get basic fastboot command returns.
No other commands seem to work.
I have gone through a number of guides and used a few different tools but to no avail. (best of all im on the other side of the world from home so cant even use my old phone)
This is what Getvar returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37BW901827
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.044s
note the failed line at the bottom.
I have also checked drivers, uninstalled them and reinstalled the naked drivers.
Any advice would be appreciated.
Click to expand...
Click to collapse
nvm. I misread your post.
@cr1960 Please remove IMEI from your quote above
LTP88 said:
Outline of Issue
ADB returns an error for every command
Fastboot will see the device, and provide a getvar but returns an error when i try to push a recovery image
I think i have been able to get into RUU (reboots and screen goes black) as i can still get basic fastboot command returns.
No other commands seem to work.
I have gone through a number of guides and used a few different tools but to no avail. (best of all im on the other side of the world from home so cant even use my old phone)
This is what Getvar returns
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d8b0f7651bb88c960f701ae91477674a
getvar:all FAILED (unknown status code)
finished. total time: 0.044s
Click to expand...
Click to collapse
Remove your IMEI/SN from your post!
1) That is normal, adb only work inside the OS or from custom recovery
2) Which error? Is your bootloader locked or unlocked?
3) When in ruu mode there should be a black screen with a silver HTC logo. Btw I can't find any ruu for your version, do you have one?
4) define ''no other commands''
LTP88 said:
I have also checked drivers, uninstalled them and reinstalled the naked driver
Click to expand...
Click to collapse
Your phone should be listed in windows devices manager as Android usb device --> My HTC. If not then your drivers aren't installed correctly.
There is a guru reset rom you could use to restore your phone,
alray said:
@cr1960 Please remove IMEI from your quote above
Remove your IMEI/SN from your post!
1) That is normal, adb only work inside the OS or from custom recovery
2) Which error? Is your bootloader locked or unlocked?
3) When in ruu mode there should be a black screen with a silver HTC logo. Btw I can't find any ruu for your version, do you have one?
4) define ''no other commands''
Your phone should be listed in windows devices manager as Android usb device --> My HTC. If not then your drivers aren't installed correctly.
There is a guru reset rom you could use to restore your phone,
Click to expand...
Click to collapse
2. unlocked
3. no silver logo is seen. Yes I think it is available RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed
4. I tried
Flash recovery ###.img
Erase Cache
reboot-bootloader
(and a few variations of this)
all of them returned error messages
LTP88 said:
2. unlocked
3. no silver logo is seen. Yes I think it is available RUU_M7_UL_JB_50_hTC_Asia_WWE_1.29.707.3_R_Radio_4A.14.3250.13_10.33.1150.01_release_311678_signed
Click to expand...
Click to collapse
No this ruu isn't for your phone, its a .707 you need .980
LTP88 said:
Flash recovery ###.img
Erase Cache
reboot-bootloader
(and a few variations of this)
Click to expand...
Click to collapse
''Flash recovery'' is not a command you must type ''fastboot flash recovery <name_of_recovery>.img'' no capital letters
same for ''Erase cache'' ---> ''fastboot erase cache''
LTP88 said:
all of them returned error messages
Click to expand...
Click to collapse
if you can't be more precise I can't help you! What is the error message?
Edit: better to post a screenshot of your command prompt when you got that error + a screenshot of your adb/fastboot folder will help.
alray said:
No this ruu isn't for your phone, its a .707 you need .980
''Flash recovery'' is not a command you must type ''fastboot flash recovery <name_of_recovery>.img'' no capital letters
same for ''Erase cache'' ---> ''fastboot erase cache''
if you can't be more precise I can't help you! What is the error message?
Edit: better to post a screenshot of your command prompt when you got that error + a screenshot of your adb/fastboot folder will help.
Click to expand...
Click to collapse
Thanks for the help.
I am going to put this on hold until I get home in a week or so.
It's too hard to resolve out of a hotel room with inconstant internet.
So I have an HTC One s-off rooted with cm11.Two days ago it suddenly turned off.Now I can't:
-reboot,it just shows the logo thn turns of
-go to recovery.When I press recovery in bootloader,it just reboots to the bootloader
-cannot flash recovery via fastboot
sending 'recovery' (4336 KB)... OKAY [ 0.391s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.281s
Please help!
Trinity99 said:
So I have an HTC One s-off rooted with cm11.Two days ago it suddenly turned off.Now I can't:
-reboot,it just shows the logo thn turns of
-go to recovery.When I press recovery in bootloader,it just reboots to the bootloader
-cannot flash recovery via fastboot
sending 'recovery' (4336 KB)... OKAY [ 0.391s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 1.281s
Please help!
Click to expand...
Click to collapse
Try to flash a RUU for your original OS version. This should return you back to stock rom and firmware.
majmoz said:
Try to flash a RUU for your original OS version. This should return you back to stock rom and firmware.
Click to expand...
Click to collapse
How can I decide witch RUU is suitable for my phone?
Trinity99 said:
How can I decide witch RUU is suitable for my phone?
Click to expand...
Click to collapse
post your fastboot getvar all without imei and serial number
Seanie280672 said:
post your fastboot getvar all without imei and serial number
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
here it is , thanks for the help.
Trinity99 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
here it is , thanks for the help.
Click to expand...
Click to collapse
You should be able to use this RUU: ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe
There is all so an OTA update you can get if it doesn't automatically down load.
Thanks I try it
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\username\Data>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
(bootloader) SD: write failed in CMD25.
OKAY [ 1.073s]
finished. total time: 1.075s
This is the error I get when trying to get in RUU mode
Any ideas?
Trinity99 said:
Any ideas?
Click to expand...
Click to collapse
just run the exe file in windows with your phone in fastboot USB mode, let the RUU do the rest.
Seanie280672 said:
just run the exe file in windows with your phone in fastboot USB mode, let the RUU do the rest.
Click to expand...
Click to collapse
When the installer restarts the phone and "waiting for bootloader" appears the phone doesent boots.Manual boot does nonthing cause the program cannot see the device
Trinity99 said:
When the installer restarts the phone and "waiting for bootloader" appears the phone doesent boots.Manual boot does nonthing cause the program cannot see the device
Click to expand...
Click to collapse
check the drivers in device manager, does it say MyHTC ? even whilst in the bootloader.
Seanie280672 said:
check the drivers in device manager, does it say MyHTC ? even whilst in the bootloader.
Click to expand...
Click to collapse
Yes
Hi,
I am pretty sure I have permanently bricked my phone, my PC no longer detects it (it used to, and I have tried reinstalling drivers several times)
When I turn on my phone, I see the HTC Logo, then it goes to a black screen, the only way for me to leave this black screen is hold power button and wait for capacitive keys to flash 115 times before it shuts off completely...I have access to Recovery Mode and am not rooted.
Any help is greatly appreciated as I've been trying to fix this for almost 8 hours now
(I have a HTC One M7 running OS~7.19.771.21)
Hutcherino said:
Hi,
I am pretty sure I have permanently bricked my phone, my PC no longer detects it (it used to, and I have tried reinstalling drivers several times)
When I turn on my phone, I see the HTC Logo, then it goes to a black screen, the only way for me to leave this black screen is hold power button and wait for capacitive keys to flash 115 times before it shuts off completely...I have access to Recovery Mode and am not rooted.
Any help is greatly appreciated as I've been trying to fix this for almost 8 hours now
(I have a HTC One M7 running OS~7.19.771.21)
Click to expand...
Click to collapse
Do you have fastboot connectivity when in bootloader mode? what is the output of
Code:
fastboot devices
and
Code:
fastboot getvar all
?
alray said:
Do you have fastboot connectivity when in bootloader mode? what is the output of
Code:
fastboot devices
and
Code:
fastboot getvar all
?
Click to expand...
Click to collapse
Code:
SH38JW903670 fastboot
and
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for your reply, if you're willing to help me out I'd be happy to make a little donation to you when I get paid at Christmas?
~Hutch
EDIT: Relocked device because I am an idiot and now can't unlock...can get into recovery only once (when submitting unlock token, after restart I become RELOCKED again)...also I launch into Clockwork for recovery instead of TWRP for some reason, I think I occidentally flashed it at some point, every time I restart I get warned that I don't have an OS and asked if I would like to root (Y/N - doesn't change anything, still no boot)
Hutcherino said:
Code:
SH38JW903670 fastboot
and
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.771.21
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HIDDEN
(bootloader) imei: HIDDEN
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for your reply, if you're willing to help me out I'd be happy to make a little donation to you when I get paid at Christmas?
~Hutch
Click to expand...
Click to collapse
You can flash the 7.19.771.21 RUU
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
The RUU is at post #2
Instructions how to flash it in post #1
Note that flashing a RUU will wipe the data stored on your phone.
alray said:
You can flash the 7.19.771.21 RUU
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
The RUU is at post #2
Instructions how to flash it in post #1
Note that flashing a RUU will wipe the data stored on your phone.
Click to expand...
Click to collapse
Code:
'FAILED (remote: signature verify fail)
Presumably because my device is RELOCKED? (See my EDIT on first post)
alray said:
You can flash the 7.19.771.21 RUU
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
The RUU is at post #2
Instructions how to flash it in post #1
Note that flashing a RUU will wipe the data stored on your phone.
Click to expand...
Click to collapse
You'll be earning yourself a nice $30 if I can get this sorted ;D
Hutcherino said:
Code:
'FAILED (remote: signature verify fail)
Presumably because my device is RELOCKED? (See my EDIT on first post)
Click to expand...
Click to collapse
The phone must be locked or relocked to flash the RUU. Can you please post a screenshot (or copy/paste) the entire command window so I can take a look?
alray said:
The phone must be locked or relocked to flash the RUU. Can you please post a screenshot (or copy/paste) the entire command window so I can take a look?
Click to expand...
Click to collapse
Well, It looks like it's working!
Thank you so much! I think I get paid 30th/31st so I've bookmarked your profile and will be donating $30 to you then!
You have really helped me and you have no idea how much appreciate it! If I can help you in any way at all, let me know