hello everyone,i recently bought a used verizon htc one m7 (m7_wlv) in great physical condition but it would not boot into the os and just hung at the white htc android screen.
i have spent nearly 2 whole days trying to fix this, but i finally decided i need some help.:silly:
here is what its doing:
from power off state; press power button for a few seconds till it turns on, vibrates shortly and shows white "htc powered by android screen". after about 20 seconds it will go to a blank screen and the computer will recognize it as QHSUSB_DLOAD and continue to register as that for however long i leave it plugged in. i then have to hold down the power and vol- buttons until i see the bootloader then i can shut it down under the fastboot menu. it will charge when plugged into either usb or wall plug power unless in qhsusb mode
the phone is s-on and bootloader is locked
here is results from fastboot getvar all:
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37WS900240
(bootloader) imei: censored
(bootloader) meid: censored
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.116s
it appears to me that this phone has never been tampered with and may have died from an update?
i have tried doing dexter's revive.sh script in both virtual machine ubuntu and ubuntu installed allongside windows and only get 'device not found aborting' messages (adb and fastboot were installed on both)
it seems to me that if only i could get s-off i could then install a custom recovery and then install a rom and be good to go. or at least unlock the bootloader and get a custom recovery. is there any way to unlock the bootloader with no adb access/ no os bootable? or is jtag my only option now? java card perhaps?
thanks again i look forward to any help:laugh:
persom55 said:
hello everyone,i recently bought a used verizon htc one m7 (m7_wlv) in great physical condition but it would not boot into the os and just hung at the white htc android screen.
i have spent nearly 2 whole days trying to fix this, but i finally decided i need some help.:silly:
here is what its doing:
from power off state; press power button for a few seconds till it turns on, vibrates shortly and shows white "htc powered by android screen". after about 20 seconds it will go to a blank screen and the computer will recognize it as QHSUSB_DLOAD and continue to register as that for however long i leave it plugged in. i then have to hold down the power and vol- buttons until i see the bootloader then i can shut it down under the fastboot menu. it will charge when plugged into either usb or wall plug power unless in qhsusb mode
the phone is s-on and bootloader is locked
here is results from fastboot getvar all:
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA37WS900240
(bootloader) imei: censored
(bootloader) meid: censored
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.116s
it appears to me that this phone has never been tampered with and may have died from an update?
i have tried doing dexter's revive.sh script in both virtual machine ubuntu and ubuntu installed allongside windows and only get 'device not found aborting' messages (adb and fastboot were installed on both)
it seems to me that if only i could get s-off i could then install a custom recovery and then install a rom and be good to go. or at least unlock the bootloader and get a custom recovery. is there any way to unlock the bootloader with no adb access/ no os bootable? or is jtag my only option now? java card perhaps?
thanks again i look forward to any help:laugh:
Click to expand...
Click to collapse
the phone is most likely dead (needs a new Motherboard) no jtag will help you
QHSUSB_DLOAD only happens on a bad firmware flash or a dead motherboard
Oh. From what I've read, I had assumed that since I could still access the bootloader it wasn't completely dead
persom55 said:
Oh. From what I've read, I had assumed that since I could still access the bootloader it wasn't completely dead
Click to expand...
Click to collapse
no that's even worse, with a bad firmware flash the phone is pitch black nothing on screen at all
no lights work nothing
So if I understand correctly, you're saying that since it is not a case of no lights/no response at all that my problem is not firmware related.
Darn I guess it's time to find a good motherboard then.
Well thanks for clearing it up so quickly
persom55 said:
So if I understand correctly, you're saying that since it is not a case of no lights/no response at all that my problem is not firmware related.
Darn I guess it's time to find a good motherboard then.
Well thanks for clearing it up so quickly
Click to expand...
Click to collapse
yes I did mine with a bad firmware flash and was able to fix it with dexter fix .. my phone was completely dead only sign of life was the Q mode when you plugged it into the PC (driver install error). what you have is a dead motherboard that still has a working bootloader
read more here it's only 3 pages >> http://forum.xda-developers.com/showthread.php?t=2599083
Related
hello,
I buyed a htc one m7. Its inner hardware is untouched, the rom is stock 4.3.
It was never rooted or something.
It stucks in a bootloop, vol-down+power for recovery does work, I can do a hard recovery reset, but it doesnt solve the error.
sometimes it starts the rom after 30 minutes bootloop, but not often. Now it does bootloop for 3 hours.
Hboot 1.55
Locked
No warranty because no copy of the invoice.
Any ideas?
http://bayimg.com/iaADaaagB
packyman said:
hello,
I buyed a htc one m7. Its inner hardware is untouched, the rom is stock 4.3.
It was never rooted or something.
It stucks in a bootloop, vol-down+power for recovery does work, I can do a hard recovery reset, but it doesnt solve the error.
sometimes it starts the rom after 30 minutes bootloop, but not often. Now it does bootloop for 3 hours.
Hboot 1.55
Locked
No warranty because no copy of the invoice.
Any ideas?
Click to expand...
Click to collapse
did the phone ever work ?
do you know how to use fastboot to erase the cache ?
have you powered the phone completely off by holding the power button + volume down for 10 - 15 seconds under a bright light?
Thanks for reply.
I tried fastboot erase cache, done. But no change.
I do shutdown with vol down and bright light on sensor. No change.
I dont know, if its worked before, I buied it on ebay.
packyman said:
Thanks for reply.
I tried fastboot erase cache, done. But no change.
I do shutdown with vol down and bright light on sensor. No change.
I dont know, if its worked before, I buied it on ebay.
Click to expand...
Click to collapse
Can you post a fastboot getvar all (excluding imei and serialno)? Maybe, there is a RUU that you can run.
I unlocked now the bootloader and installed twrp recovery. I go into fastboot and select recovery, then it restarts and says: entering recovery. but theres no recovery coming, only old bootlop I only wanted to make an backup.
fastboot erase cache doesnt help
Code:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35EWxxxxxx
(bootloader) imei: 3xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3725mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
So I found the problem. The usb flex was maybe faulty and couldnt charge the accu.
I had another htc one m7 here, so I changed the accu and now all is okay. nicely, the usb flex seems to be okay. But the accu was to empty to charge (I had the htc one day on the wall charger and display showed the charge symbol).
So, its solved!
Hi,
My HTC ONE M7 suddenly stopped working. I had everything stock, no custom firmware or anything else on it. Suddenly it powered off, powered back on again and from that on its in an endless bootloop. I only get the "HTC - powered by android" screen for ca. 10s, then it turns black and starts again. I can get into the bootloader and can enable fastboot, but when i try to start the recovery i'm back in the bootloop. Tried flashing CWM and TWRP recoverys, but non of them are working. I just get the screen "ENTERING RECOVERY" but then it shuts off and powers on again back into the bootloop.
Here are the device datas, it's a german T-Mobile:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.16.111.4
(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: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
S-ON, Bootloader Unlocked.
Hope anybody can help me with this.
dbassix said:
Hi,
My HTC ONE M7 suddenly stopped working. I had everything stock, no custom firmware or anything else on it. Suddenly it powered off, powered back on again and from that on its in an endless bootloop. I only get the "HTC - powered by android" screen for ca. 10s, then it turns black and starts again. I can get into the bootloader and can enable fastboot, but when i try to start the recovery i'm back in the bootloop. Tried flashing CWM and TWRP recoverys, but non of them are working. I just get the screen "ENTERING RECOVERY" but then it shuts off and powers on again back into the bootloop.
Here are the device datas, it's a german T-Mobile:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.16.111.4
(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: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
S-ON, Bootloader Unlocked.
Hope anybody can help me with this.
Click to expand...
Click to collapse
Please remove your imei and serialno in your first post!
While in bootloader, try a factory reset since you are completely stock. Custom recoveries will not work with a locked bootloader. Actually, if the factory reset doesn't work, you might try returning it for repair since it is basically stock.
majmoz said:
Please remove your imei and serialno in your first post!
While in bootloader, try a factory reset since you are completely stock. Custom recoveries will not work with a locked bootloader. Actually, if the factory reset doesn't work, you might try returning it for repair since it is basically stock.
Click to expand...
Click to collapse
Tried everything so far. even Factory Reset brings me to the bootloop. Don't know if i can return it for repair as the bootloader says "Tempered"
dbassix said:
Tried everything so far. even Factory Reset brings me to the bootloop. Don't know if i can return it for repair as the bootloader says "Tempered"
Click to expand...
Click to collapse
I think you need to flash a stock firmware but unfortunately I can not find one for your version 5.16.111.4. This is a long shot and I would not recommend it but you can go to this site and download both OTA files and the nandroid zip file. Open up both OTA files then double click on the firmware.zip if it is similar to the DevEd or TMOUS then the OTA going from 4.11 to 5.11 is the most complete. Extract that firmware from the OTA. We are going to flash that one and hope that it will correct the bootloop. Generally it is not recommended to flash just the firmware out of the OTA because sometimes there are some files missing but in this case you are already in a boot loop and you unlocked your bootloader. If the firmware looks similar to the attachment then it should be safe to flash. Your bootloader needs to be relocked and place the firmware.zip in your fastboot folder. You need to connect your phone to the computer and put the phone in bootloader/FASTBOOT USB mode:
Code:
[B][I]fastboot oem lock[/I][/B]
When complete, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Hopefully, the bootloops have stopped. And you should be completely back to stock with the exception of "Tampered" and "Relocked".
dbassix said:
Hi,
My HTC ONE M7 suddenly stopped working. I had everything stock, no custom firmware or anything else on it. Suddenly it powered off, powered back on again and from that on its in an endless bootloop. I only get the "HTC - powered by android" screen for ca. 10s, then it turns black and starts again. I can get into the bootloader and can enable fastboot, but when i try to start the recovery i'm back in the bootloop. Tried flashing CWM and TWRP recoverys, but non of them are working. I just get the screen "ENTERING RECOVERY" but then it shuts off and powers on again back into the bootloop.
Here are the device datas, it's a german T-Mobile:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.16.111.4
(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: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
S-ON, Bootloader Unlocked.
Hope anybody can help me with this.
Click to expand...
Click to collapse
Hi
I have the same issue now with my One M7UL (Bouygues france).
Have you managed to fix this issue?
Thanks
I would like to update the firmware on my phone as I believe it is preventing my USB port to work and/or charge while it is powered on. I also believe the only way to change the firmware is to have S-OFF so how can I do that if my USB port doesn't work while in the OS. The USB works perfect in fastboot or custum recovery mode. 2.8.3.0 twrp. Can anyone help?? I thought I could flash firmware 6.09.401.12. My phone specs are listed below
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4104mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thanks for any help on this.
Roddyrex said:
I would like to update the firmware on my phone as I believe it is preventing my USB port to work and/or charge while it is powered on. I also believe the only way to change the firmware is to have S-OFF so how can I do that if my USB port doesn't work while in the OS. The USB works perfect in fastboot or custum recovery mode. 2.8.3.0 twrp. Can anyone help?? I thought I could flash firmware 6.09.401.12. My phone specs are listed below
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4104mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thanks for any help on this.
Click to expand...
Click to collapse
It's done with an app on your phone
SunShine S-Off
http://theroot.ninja/
There's gotta be another way without having to pay $25USD. Can I not leave the device S-ON and change the firmware version?
Roddyrex said:
There's gotta be another way without having to pay $25USD. Can I not leave the device S-ON and change the firmware version?
Click to expand...
Click to collapse
I think your on the newest firmware for your phone ? have you searched ?
Is my firmware version not:
(bootloader) version-main: 5.11.661.8
My hboot is the newest I guess but I don't think my firmware is.
I really just want to see if loading a different firmware will fix my USB issue as I believe something in the firmware is disabling it. Phone charges and transfers data in recovery mode and fastboot but as soon as I'm in the OS it stops working and I was stock OS before and now Revolution 84...... still not working.
Roddyrex said:
Is my firmware version not:
(bootloader) version-main: 5.11.661.8
My hboot is the newest I guess but I don't think my firmware is.
I really just want to see if loading a different firmware will fix my USB issue as I believe something in the firmware is disabling it. Phone charges and transfers data in recovery mode and fastboot but as soon as I'm in the OS it stops working and I was stock OS before and now Revolution 84...... still not working.
Click to expand...
Click to collapse
you need to ask @SaHiLzZ he's the resident Telus guy .. i don't think you have a 6.x firmware though
Roddyrex said:
Is my firmware version not:
(bootloader) version-main: 5.11.661.8
My hboot is the newest I guess but I don't think my firmware is.
I really just want to see if loading a different firmware will fix my USB issue as I believe something in the firmware is disabling it. Phone charges and transfers data in recovery mode and fastboot but as soon as I'm in the OS it stops working and I was stock OS before and now Revolution 84...... still not working.
Click to expand...
Click to collapse
Hi,
Your OS is the latest version for Telus. Canadian HTC didn't get 6.x for their phones as far as I am aware.
Your only option is to do S-OFF using Sunshine, and then converting to a Dev edition with higher or lower firmware to root out this issue.
Have you tried a different computer, with new HTC driver installation?
I've tried several pc's and cables. I paid for Sunshine. I've now rooted, custom recovery, installed Rom, S-off and installed the newest 6.xXxX firmware. Still doesn't charge while on or in OS. Usb works normally in recovery twrp. Doesn't make any sense to me and I'm an Electronic engineer, go figure lol.
Roddyrex said:
I've tried several pc's and cables. I paid for Sunshine. I've now rooted, custom recovery, installed Rom, S-off and installed the newest 6.xXxX firmware. Still doesn't charge while on or in OS. Usb works normally in recovery twrp. Doesn't make any sense to me and I'm an Electronic engineer, go figure lol.
Click to expand...
Click to collapse
Do you have any notification about your phone being in USB Host mode?
Try to clean your usb port with alcohol
Try these method, it worked for some users, don't ask me why...
1. Turn phone OFF
2. Let charge for AT LEAST 10mins even if it doesn't look like it's charging (mine DID show the new charging animation)
3. Press and hold POWER + VOL UP + VOL DOWN for AT LEAST 2mins. Anything less will not reset the charge mode.
4. After 2mins release the buttons and the phone should boot as normal.
Click to expand...
Click to collapse
or
I was having the same problem with charging my HTC One. I contacted HTC and they told me to do the following which worked:
Step 1: Power off the device
Step 2: Press the Power button to initiate booting sequence and wait for the HTC logo to appear on the screen
Step 3: Press and hold the Volume Down button until entering OS
Step 4: You will notice that the device vibrates briefly during this process
Step 5: ‘Safe Mode’ wording will appear on the bottom left of the screen to confirm that device has entered safe mode.
After this safe mode start I restarted normally and no longer have issues charging the phone.
Cheers.
B.
Click to expand...
Click to collapse
Yes I've tried all those as well , just don't understand or believe this could be hardware because it works fine in recovery mode.
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
Good Morning Everyone,
first of all, thanks for everything I am a member since the HTC Touch HD times, where XDA enabled me to keep that device until 2015!!
Now I have a problem with the Desire 500 single sim of my wife... I just want to restore the phone to full stock to lend it to her mother so she can stay in contact with 21th-century technology (Whatsapp, ...).
Some time ago a messed a little with this device unlocking the bootloader and installing TWRP recovery, the idea was (as probably all the owners know) to install a light version ROM to have a little more space for applications, time wasn't on my side and therefore I had to leave the phone for a while, but as I can remember in working condition (still with the stock ROM).
I had some time to finish the work and a week ago a took out the phone again having a not very good surprise:
I can access now only the bootloader
Recovery send me in fastboot mode
Factory Reset send me in fastboot mode
Classic boot get me to the HTC green logo on white background without doing nothing
Fastboot commands are correctly taken
I am unable to flash whatsoever
I have to charge the phone with the batch file, but with manual booting in bootloader, otherwise, the script does not work
I am unable to relock the bootloader (the fastboot OEM lock throws a "too many links" error and fails)
The command fastboot OEM rebootRUU reboot the device, but not in RUU mode.
The bootloader is still unlocked 1.03.0001
The phone is S-ON
The OS line in the bootloader is empty
Flashing recovery throws "remote:image updated error"
Bootloader INFO
Code:
*** UNLOCKED ***
Z4U PVT SHIP S-ON RL
HBOOT-1.03.0001
RADIO-14.16.36Q4.22
OS-
eMMc-boot
Jul 8 2014, 19:15:10.0
fastboot getvar all
Code:
C:\Users\xxx>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.03.0001
(bootloader) version-baseband: 14.16.36Q4.22
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH449WE0XXXX
(bootloader) imei: XXX
(bootloader) meid:
(bootloader) product: z4u
(bootloader) platform: HBOOT-8x25Q
(bootloader) modelid: 0P3Z11200
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e9f20193
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I think I almost checked all the internet, any suggestion simply does not work.
I tried to flash different recoveries, ROMs, RUUs... nothing works.
I need to consider the device bricked or do you guys have some other idea to try resolving the problem?
Thanks even if you spend some time for reading...
Bye
NP