Have a very strange problem with my Sprint HTC One m7. Hoping it is software related only. I appear to be stuck in RUU mode. Whenever the phone boots, I am met by the black screen with silver HTC logo in the center and triangles with exclamation points inside in all four corners. Here is my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3773mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
After replacing the battery inside the phone, as well as the front housing with digitizer and screen and back housing, I booted up and was met by a boot loop. Prior to installing new hardware mentioned, I had been using CM12 Android L. I booted into bootloader menu and tried to boot up recovery. Got stuck at the screen which tells you the phone is booting into the recovery. No dice. Recovery never loaded. Rebooted into bootloader and fastboot relocked in anticipation of running either of the two most recent RUUs that matched my HBOOT version (1.57).
Both RUUs have failed me. Both of the two most recent RUUs fail with the incorrect image error (though these are the correct images).
I've also tried flashing firmware. I always get the '12 signature verify failed' message. When I go through the recovery process after the RUU fails, the phone always reboots back into RUU mode. I unplugged it to find the following info displayed on my phone itself:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Makes me wonder what [12] CIR stands for.... Google has turned up zip on this.
So, as you can see, I've tried it all basically. Nothing will get the damn thing out of RUU mode. Now I'm wishing to all ends that I would have just s-offed this stupid thing so I could try to roll back to some old firmware or something.
Of course, I have no access to ADB. I can send fastboot commands and can successfully unlock/relock the phone. I have installed the HTC One driver for my device, as well as the HTC Sync application, but the device is still showing up as Android 1.0 in my 'Devices and Printers' folder on Windows 7 (32-bit).
This is pretty much where I am at for the moment. I would love any ideas my fellow XDAers may have. Maybe the Android L release will result in an RUU that will help, though I have little confidence in that considering the 5.05.651.2 firmware and RUU was of no help.
This luckily is no longer my daily driver. I moved on to a Samsung Galaxy Note 4 on a different network. I thought about using my old One as a fancy coaster that lights up when plugged into the wall or a computer, but when I sat my beer on it, it didn't really seem stable because of the curved back housing.
The scariest thing of all about this is that my problem has even stumped @clsA. It's pretty bad when someone who has literally helped fix 1000s of HTC One m7 Brick Editions can't figure out WTH is going on.
To make this interesting, I promise a respectable donation to whomever offers the piece of advice that gets the device working for me (if it is indeed a software issue). If it's my motherboard, I'm gonna be broke from slapping down 130 bucks or so for a new one (though I really believe it is software related because I was beyond careful when transferring everything to the new housing).
Let the 45th HTC Hunger Games Begin!
Because you are S-on, don't you have to relock your bootloader before running an RUU!
Edit: I see the relocked on the screenshot now. I was just reading the text
There's no easy answer like that, for sure. Haha. I am able to unlock bootloader and push boot image and recovery image via fastboot, but have been unable to push a Nandroid system image and my data image for some reason. The backups were made in TWRP when it was working for me before the hardware changes. Anyone know where I can find a good stock system image and data image to push?
System image should be of the 5.03.651.3 variety. Since TWRP splits my backup into two images, I used copy /b command to combine, but I am still getting sparse header mismatch error.
I am not convinced that if system is accepted via fastboot flash that it would work.
Couple of things if you can access fastboot. Try sudo fastboot erase cache and have you tried super CID? not sure if soff is required for the latter.
Sent from my HTC One using Tapatalk
Tried the fastboot erase cache before to no avail. Not sure what super CID is. Will look into it.
It's a fastboot command to change the Cid... It allows us3rs to flash ruus made by other carriers. Generally means nothing for sprint since we are tied down to cdma however may help the signature verification problem you are having
Sent from my HTC One using Tapatalk
Gotta be s off to use it. Blah.
I'm positive it has something to do with the CIR.img that is in the latest RUU when decrypted. I can flash basically any img to the phone manually except that CIR.img file. The same CIR that is mentioned as reason for failure in the RUU readout above no less. WTF is the CIR?
MarkBell said:
I'm positive it has something to do with the CIR.img that is in the latest RUU when decrypted. I can flash basically any img to the phone manually except that CIR.img file. The same CIR that is mentioned as reason for failure in the RUU readout above no less. WTF is the CIR?
Click to expand...
Click to collapse
Why are you using the decrypted RUU?
Because I am trying everything, including pulling the system image files, boot image files, etc. out of firmware packages that may be relevant and flashing them via flashboot.
MarkBell said:
Because I am trying everything, including pulling the system image files, boot image files, etc. out of firmware packages that may be relevant and flashing them via flashboot.
Click to expand...
Click to collapse
Decrypted won't work since you are s-on.
I understand. I am just trying everything. Even if it doesn't make sense. Desperate.
I'm just stumped. I believe I've tried every possible remedy. Maybe time to send it off to HTC.
Contacted HTC looking for info on CIR Failed-PU. They have been good to me in the past so hopefully they will have some advice. If not, then I'll just send it back for repair.
I am now in contact with HTC about this issue. A tier 3 escalation professional will be coming here to XDA to research the problem with my phone. I recently tried flashing the new Lollipop RUU provided by HTC for Sprint devices. The image failed, again with the same error (CIR - PU). Hopefully something fruitful will come of this that will benefit anyone in the future with this type of issue.
Your s- on , have tried to unlock the boot loader with htcdev.com method and s-off and try flashing a custom recovery, I've been stuck like this before , try using fastboot oem unlock ,see if it will reunlock it with out htcdev.com if u gain s-off u can also use ruu ,make sure your using the right one for your hardware,or if u gain unlock change to supercid
As stated before, I can freely unlock and relock bootloader no problem. But the device won't even boot to the bootloader menu. I can flash fastboot commands from the black screen with silver HTC logo (RUU mode), but in order to flash the fastboot command for supercid I need to get s off. In order to be s off on my hboot version, I need to be able to flash commands thru adb, which I cannot in its current state. I can successfully flash a custom recovery but since I can't boot into bootloader menu, I have no way of getting the device to boot into recovery mode. It is literally stuck in RUU mode.
What firmware are you on it doesn't say ?
Related
HI ALL
MY HTC ONE AT&T UNLOCKED
MY HTC ONE hade a problem with battery
three days back i replace the battery but my device keep rebooting :crying:
i can enter bootloader menu but not revcovery
i try to flash boot.img from cmd its don completely but device same
i try to run ruu rom its don completely but device same
there on different in one case the htc screen come with wirning "This build is for development purposes only do not distribute outside of HTC without HTC's permission ..."
- Device details -
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
openDSP-v31.120.274.0617
OS-3.17.502.3
eMMc-boot 2048MB
sep 10 2013,01:32:23.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3562mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
hope you can help guys
best regards
fastboot flash recovery recovery_name.img
fastboot erase cache
First off, remove your IMEI and Serial Number from the post above. That's sensitive information.
Second, normally the "Development Purpose" message should disappear once you flash back to stock with RUU. are you positive that flashing finished successfully?
Anyhow your problem should be solved - as BenPope has said - by reflashing your recovery. Just pick a suitable revocery image, enter Bootloader in FastbootUSB mode and give it a try:
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
i did this guys and my device still same
supermagic49 said:
i did this guys and my device still same
Click to expand...
Click to collapse
Which recovery exactly did you flash? Are you absolutely positive it was a suitable version for your device?
How by the way did you change the battery yourself? Did you disassemble the phone? If so you might perhaps have broken something?
Gesendet von meinem SM-T705 mit Tapatalk
- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
- i changed battery in maintenance center but u think it can start bootloader accept flashing an there is something broken
do u advice to disassemble n see
regards
supermagic49 said:
- I had tried all recovery files CWS__001 in this link http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Those are Stock Recoverys if I'm not mistaken. So even if you flashed those you wouldn't recognize any difference as they don't change anything compared to stock.
But first there's something else I oversaw. In your OP you stated your details. It seems you haven't yet unlocked your bootloader? Or did you just leave out that information? That would be the reason why flashing anything does not work - AT ALL.
Unlock your Bootloader (use seach, there are lots of tutorials on how to do that). Second, please don't temper with the boot.img right now. There is no reason for you to change or overwrite a working bootloader. In fact the chances are you would mess up things even more. So leave the boot.img alone for now.
My suggestion is:
- Unlock your Bootloader (with HTCDev)
- Flash a Custom Recovery (e.g. TWRP - http://forum.xda-developers.com/showthread.php?t=2173870)
- Take it from there. See if recovery works and if so, go ahead an flash a Custom ROM, a Nandroid Backup or get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON. So although you theoretically should be able to flash a (newer) RUU even with S-ON, you can make sure it works by being S-OFF first. SInce only then can you also downgrade your Device via RUU plus it then does not matter if you're locked / unlocked / relocked / tempered. Thing is you need a working Android to get S-OFF. That's why I suggested flashing a Custom ROM. Just about any suitable M7 ROM will do, for example: http://forum.xda-developers.com/showthread.php?t=2334294. Give it a try and tell me how it went, will you? Best of luck. But if you're unsure about anything, ask first. Don't mess things up even more
Ok nosmint
thnx for ur kind following
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
-flash zip and flash recovery is not allowed i think if i clear this problem every thing will be fine
one more thing i open my device i found to cable not fixed i fix bu no changes
that,s the cable was not fixed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.ytimg.com/vi/S5KNmDeJ4Ww/maxresdefault.jpg
nosmint said:
... get yourself S-OFF (Firewater or Rumrunner) and flash back a stock RUU.
RUUs can be a bit tricky with S-ON.
Click to expand...
Click to collapse
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF
nkk71 said:
the OP says:
(bootloader) version-misc: PVT SHIP S-OFF
Click to expand...
Click to collapse
Any advice dear
supermagic49 said:
Any advice dear
Click to expand...
Click to collapse
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
- my device is unlocked
-i flash one of the recovery u refer to with the order " fastboot flash boot" because "flash revocery" return to me with "remot no allowed"
Click to expand...
Click to collapse
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.
How can i clear the message of " remote not allowed so i can flash recovery
Regards
supermagic49 said:
How can i clear the message of " remote not allowed so i can flash recovery
Regards
Click to expand...
Click to collapse
you would need to unlock bootloader (it's pretty easy with S-Off), but please first tell us what you want to achieve
nkk71 said:
Well first of all please explain what your goal is.... do you want custom ROM, stock ROM, etc.
Second, we are talking about bootloader unlocked not SIM-unlocked, this
indicates your bootloader is either LOCKED or RELOCKED
look at the first line of the attached screenshot.
So please explain what your goal is, and i'll try and help from there.
Click to expand...
Click to collapse
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that
supermagic49 said:
Fine
my goal to see my device working with custom ROM or stock ROM
my bootloader unlocked i just forget to mention that
Click to expand...
Click to collapse
use this RUU: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
that will wipe your phone completely and install stock ROM and firmware.
i had tried this too but no change
ruu info
When looking for ruu.exe I went through 6 or 7 different ones. 1 way to know if u have the right ruu is by searching your android and sense version also provider currently on your phone otherwise the ruu won't work s-off dosnt matter I never turned it off on my phone and still got the ruu to work
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(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: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(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: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
Did you do a factory reset? If so you will need to reflash the rom.
zelendel said:
Did you do a factory reset? If so you will need to reflash the rom.
Click to expand...
Click to collapse
i have tried doing factory reset but it stops giving a red triangle with an exclamation mark.
i would be glad if you can guide me to the steps regarding reflashing the rom.
hammaad110 said:
I am having problem with my htc one. It continuously reboots. Displays HTC Logo then O2 then Beats audio and then restart.
The things which I have tried doing are
after volume down and pressing power button factory reset, in fast boot rebooted the boot loader. When I go into the recovery it gives red triangle with an exclamation mark in the middle.
I tried connecting it with adb but it says
List of devices attached and then empty no device
adb shell gives
error: device not found
I tried fastboot devices -> this displays
W910109 fastboot
D:\adb>fastboot getvar all
(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: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA386W910109
(bootloader) imei: 357864053760359
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.117s
Can anyone help me in the matter. My device warranty is void. All I want it to go back to factory reset.
thanks
Click to expand...
Click to collapse
waiting for assistance
hammaad110 said:
waiting for assistance
Click to expand...
Click to collapse
Search the site. Everything you need has already been posted.
zelendel said:
Search the site. Everything you need has already been posted.
Click to expand...
Click to collapse
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.
hammaad110 said:
I have downloaded the RUU file
htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_o2_uk_4-20-206-16_radio_4a-23-3263-28_10-38r-1157-04l_release_353143_signed_2-exe
for modelid: PN0710000
cidnum: O2___001
I executed the file while in Fastboot usb mode. The file gave different messages and told me that going to urgrade the ROM to 4.xx. Then it asked me to press next. When I pressed next it restarted the phone and it again went into the infinite loop on restating. while the PC screen was saying waiting for the bootloader and then after 2 or 3 min it said that error in the USB connection.
the phone says MY HTC in Android USB devices when its in Fastboot mode while in normal boot loader mode its not detected. Also adb does not gives anything when i give command adb devices. However Fastboot devices gives serial number if the device.
Click to expand...
Click to collapse
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.
zelendel said:
I would remove all the drivers and start from scratch. FIrst thing you will need to get working is your adb drivers on your PC. Make sure to be running windows 7, uninstall all android drivers, reboot PC, then plug in the android in bootloader mode and let the OS install the needed drivers.
Click to expand...
Click to collapse
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
Then something is wrong with your driver set up. Check the threads in this section of other ways to get it working. I know that if you had HTC sync installed that it would cause these issues. I have never had this issue where what I discribed above didnt fix
hammaad110 said:
Done that. it only detects a hardware in fastboot mode and no device is detected in bootloader mode.
Click to expand...
Click to collapse
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device
nkk71 said:
could you define the difference between "fastboot mode" and "bootloader mode"?
if you are in bootloader and it says FASTBOOT USB (in red), it will detect your device
Click to expand...
Click to collapse
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
you should redo all the unlocking procedure try that
hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
not sure what you mean, but:
fastboot commands work in bootloader (FASTBOOT USB on the phone screen), adb does not
adb commands work in custom recovery
adb commands work in booted up phone with USB debuggin enabled
hammaad110 said:
Yes my device is detected in FASTBOOT USB but is not detected in ADB devices even in BOOTLOADER
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
As I explained in our pm's you need to be on hboot 1.55 to use that ruu.
To get your phone unlocked I think you need to flash firmware to refresh your hboot. But unfortunately there isn't any available any where unless @nkk71 knows where you might find it.
With your phone in its current state there is no way for you to use adb, since it won't work in stock recovery. I'm considering going out of my way to help you out here but let's see if nkk71 has anything first.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
hammaad110 said:
since my bootloader is LOCKED. I had tried unlocking it through htcdev procedure but after the procedure and pressing ok on device it again says LOCKED
so I cannot UNLOCK the bootloader and thus cannot install custom recovery.
What should I do now
Click to expand...
Click to collapse
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.
nkk71 said:
I haven't looked much, but didn't see any 2.24.206.7 or higher firmware.zip in the usual places... it may be out there but i didn't see it.
wait, i guess i misunderstood, are you saying HTCdev bootloader unlock is no longer working?? (can you copy/paste command prompt output of that, don't forget to get a new token)
can you also copy/paste the command prompt output of "fastboot oem rebootRUU", do you actually get to ruu mode:
if you can get to RUU mode, you should try to get the RUU to work.
the 4.xx RUUs are OK, but are very picky about PC configuration, USB ports, etc.
Click to expand...
Click to collapse
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
Hi nkk71, I had the same problem with my friends O2uk m7, When it comes helpful files there doesn't seem to be anything for O2.
The bootloader unlocking goes fine up untill the the point he selects "yes" to unlock on the phone. The phone reboots but is still locked.
The RUU in question is an exe I used it myself after many hours of of failing with error 12 signature verification failed, with hboot 1.57. it's the same with this situation. Eventually my friend decided to pay for the sunshine app so I could s-off the device and I finally got the ruu to work by, changing the cid to HTC__001 I then manipulated the firmware using 401 WWE firmware to bring the phone to hboot 1.55. I then changed the cid back to O2__001 and the RUU worked.
So I think he needs the 3.xx.206.x firmware to run the ruu.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)
nkk71 said:
ah, yes, i think you're right, HTC did change some "stuff" between earlier releases and later ones, so that would explain the signature fail.
but how did the OP end up in this situation? could very well be a hardware problem... do you have any info on that? considering he's S-On / LOCKED (ie never messed with his phone), and a "semi-successful" HTCdev unlock (ie token is fine, but unlock doesn't unlock) does sound awfully familiar to a hardware problem
* what's the command output of "fastboot oem rebootRUU"? does it go to ruu mode?
* how did this happen?? (is it one of those "it happened suddenly" things?)
Click to expand...
Click to collapse
From our pm's
Then it may be because you need to update hboot first.
Are you running the ruu to fix a bootloop problem?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
From our pm's
Yes exactly. I want to clear the boot loop problem. The cellphone is of my client and I dont know exactly what he has done wrong with it. As far as he says that he only cleared some junk files and phone is in this condition.
Click to expand...
Click to collapse
I'll be honest I was considering converting my phone to O2 stock and capturing the ota's and making a few stock nandroids. A lot of trouble to help one person especially as you think it could be hardware. But it would help the O2 community as a whole so maybe worth the effort.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe
nkk71 said:
Well not knowing the background is a real problem.
Do you happen to know the colour of the bootloader? is it a GPE bootloader... this could be another badly done Sense to GPE back to Sense conversion... therefore missing the necessary files/partitions for htcdev unlock to work (even if it's a HTC bootloader)
There is a 4.xx firmware that he could flash (has hboot 1.56 dd Nov 29 2013), though I will not recommend it, as chances of unlocking bootloader will be slim if the O2 RUU fails.
and yeah, capturing all those OTAs for O2, is going to be a bit of work... don't wanna sound selfish, but i'm in no mood for that atm... maybe if i have time on weekend i might consider it, though that is a big maybe
Click to expand...
Click to collapse
I don't know the bootloader color sorry maybe @hammaad110 can post a picture for us?
I may have a go at capturing the otas if I can make time for it. I won't be capturing them all though may be just the 2.xx and 3.xx with Stock nandroids that would be enough for using the RUU at least and possibility of a reset zip.
Besides I already have the necessary files to make the change to O2. So I wouldn't trouble yourself with that. It was my idea so I wouldn't expect you to go to the trouble of making it happen
As for the bootloader unlocking problem I remember a similar case, although weather we came to a solution is sketchy in my memory. I seem to remember flashing the current firmware fixed the problem. I'll look through my posts and pm's to try to find it so I can clarify it. If that was the case I'll probably capture the ota's to help this guy out and maybe a few others.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
I require your help fixing my HTC One M7. The phone hangs at the black screen with the Google logo. I have access to bootloader only. I cannot flash any recovery image or any other image.(please see the attached pics). When I push the power button on recovery or factory reset in bootloader, it returns to previous screen very quick.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3692mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
Click to expand...
Click to collapse
Thanks,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
behzad756 said:
I require your help fixing my HTC One M7. The phone hangs at the black screen with the Google logo. I have access to bootloader only. I cannot flash any recovery image or any other image.(please see the attached pics). When I push the power button on recovery or factory reset in bootloader, it returns to previous screen very quick.
Thanks,
View attachment 3364397
View attachment 3364398
View attachment 3364399
Click to expand...
Click to collapse
You can access fastboot I see. My computer refused to flash a custom recovery to my HTC one once and it turned out that it was a driver issue.. are you on full android sdk or minimal adb tools? I use the latter and it works flawlessly. What version of Windows are you on? You need to install HTC sync manager which will take care of any driver issue.
Right now your best bet would be using a nandroid backup. Also since you're on s-off you can use a ruu. You can find many here but you need one that'll work with your device. If you end up struggling to find one let me know.
monrokhoury said:
You can access fastboot I see. My computer refused to flash a custom recovery to my HTC one once and it turned out that it was a driver issue.. are you on full android sdk or minimal adb tools? I use the latter and it works flawlessly. What version of Windows are you on? You need to install HTC sync manager which will take care of any driver issue.
Right now your best bet would be using a nandroid backup. Also since you're on s-off you can use a ruu. You can find many here but you need one that'll work with your device. If you end up struggling to find one let me know.
Click to expand...
Click to collapse
I'm using windows 8.1 and I also installed HTC sync manager. Please give me a nandroid or ruu that works with my device.
Thanks
@behzad756 Was able to find this:
http://graffixnyc.com/development/m7/RUU-HTC_One_GE-5.0.1-5.11.1700.3_rooted.zip
Hope it works!
In case you face a drivers problem:
http://forum.xda-developers.com/showthread.php?t=2232799
monrokhoury said:
@behzad756 Was able to find this:
http://graffixnyc.com/development/m7/RUU-HTC_One_GE-5.0.1-5.11.1700.3_rooted.zip
Hope it works!
In case you face a drivers problem:
http://forum.xda-developers.com/showthread.php?t=2232799
Click to expand...
Click to collapse
Thank you, but it didn't work. The problem is that it hangs after every flash installation even recovery flash.
@behzad756 Not being able to flash anything is a serious problem. Maybe your hboot is corrupt? You're on s-off so fixing this should be possible.
Alright, calling for help.. @Seanie280672 knows a lot about hboot.
Can you access recovery? Try wiping everything then retry installing the ruu. It's compatible with your device so it should work. You know how to do that right?
I don't have access to recovery and also cannot flash any recovery too.
behzad756 said:
I don't have access to recovery and also cannot flash any recovery too.
Click to expand...
Click to collapse
That's because you locked the bootloader, highly not recommended on gpe edition, lots of reports of people not being able to unlock on the newer gpe roms, I suggest you try and unlock first. There's no need to lock it ever if your s-off.
I'm not really upto speed with gpe roms, don't like it myself, just personal preference, but what you need is an ruu really of your current version or any really as your a-off, just to get you up and running, I'll have a look around. Whatever you do, don't go s-on or you'll be in lots of trouble, and try and get that boot loader unlocked again.
---------- Post added at 08:21 AM ---------- Previous post was at 08:15 AM ----------
Soz, you are unlocked, I mis read it, thought it said relocked
@Seanie280672 @behzad756 the bootloader appears to be unlocked. I've already linked a ruu maybe you can check it out seanie if you can't find another one?
The issue that he can't flash anything is really baffling. did he relock the bootloader or something? never happened to me thankfully.
a ruu appears to be the only possible solution, maybe the one I linked to is corrupt? but it's not the first time someone uses it.
---------- Post added at 11:04 AM ---------- Previous post was at 10:55 AM ----------
[/COLOR @behzad756 I once flashed a inappropriate img file and wasn't able to access recovery.. try flashing these, one should work if flashing is possible but accessing the recovery afterwards is the real problem:
https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
the first one is more likely to work.
If you still can't flash anything maybe it's a driver issue? Can you post what the command prompt returns when you try flashing a recovery img file?
monrokhoury said:
@Seanie280672 @behzad756 the bootloader appears to be unlocked. I've already linked a ruu maybe you can check it out seanie if you can't find another one?
The issue that he can't flash anything is really baffling. did he relock the bootloader or something? never happened to me thankfully.
a ruu appears to be the only possible solution, maybe the one I linked to is corrupt? but it's not the first time someone uses it.
---------- Post added at 11:04 AM ---------- Previous post was at 10:55 AM ----------
[/COLOR @behzad756 I once flashed a inappropriate img file and wasn't able to access recovery.. try flashing these, one should work if flashing is possible but accessing the recovery afterwards is the real problem:
https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
https://dl.twrp.me/m7vzw/twrp-2.8.6.0-m7wlv.img.html
the first one is more likely to work.
If you still can't flash anything maybe it's a driver issue? Can you post what the command prompt returns when you try flashing a recovery img file?
Click to expand...
Click to collapse
First I have to ask, how are you trying to flash the GPe rom.zip that @monrokhoury linked you too ? what errors is it giving you ? you don't flash this one in recovery.
And 2nd as its a Lollipop RUU.zip you will probably need the use the HTC_fastboot.exe, below is the instructions on how to flash it:
1. Once downloaded rename file to RUU.zip
2. Place it in your adb & fastboot folder
3. Reboot phone to fastbootUSB mode
4. as you are S-Off there is no need to lock the bootloader
5. Also use the htc_fastboot.exe not the normal fastboot.exe
get the htc_fastboot.exe here : https://www.androidfilehost.com/?fid=95916177934539737
Run the following commands from your adb folder:
6. htc_fastboot oem rebootRUU
7.htc_fastboot flash zip RUU.zip
8.htc_fastboot reboot-bootloader
9. fastboot reboot
@monrokhoury the 2nd recovery img you posted is for Verizon branded phones, it cant be flashed on GSM devices, will cause big problems M7_WLV
@Seanie280672 edited my post.
Thanks for providing the instructions bud. I think the ruu should flash regardless of the phone's state assuming he doesn't have any problems with the drivers.
I tried all the steps, but it doesn't accept any flash. Looks like a hardware problem. Do you know anywhere to fix it in USA?
behzad756 said:
I tried all the steps, but it doesn't accept any flash. Looks like a hardware problem. Do you know anywhere to fix it in USA?
Click to expand...
Click to collapse
You can try a local mobile shop, other than that you'd be looking at a HTC repair Centre, but to be honest the M7 is that old now, you could probably pick up a 2nd hand working one off eBay cheaper than getting yours repaired.
As the Title suggests this is the root problem of why I have gone through all the stuff I have. I have an HTC One that doesnt have any data (when I say data in this instance I also mean no cell service too).
My father-in-law has given me this phone to see if I can do anything with it. Data shows it is unavailable. Every once in a while bars will be full but will be on either G or E network, and if a text message is waiting to be sent or delivered, it will eventually come through. When I say eventually I mean after an hour or so--I guess when it hits that exact moment I get cell service, but then bars are gone and nothing. So cell service and data are pretty much shot and do not work at all. Only thing is said that has happened just recently is he had it in his back pocket and sat on it very briefly and noticed it immediately. But he didnt notice any problem until about a few days later when all of a sudden no data at all--couldn't make phone calls or browse the internet unless on WiFi. Wifi by the way works perfectly.
So I am approaching it from both Software and Hardware side. I approached Software first mainly because I saw videos on how to open this and it looks like a nightmare that only ends in a cracked screen. Here is what I did
1. Unlocking Bootloader
2. Installing TWRP and rooting
3. Different Roms (No roms seem to help)
So I have a HTC One that is fully rooted with recovery. The only thing I don't have is S-Off which I will be willing to try if it will help with Sunshine S-Off.
I figure Hardware could be a problem, because maybe when he sat on it, it just so happened that he pulled an antenna away from the connection. I noticed from the videos that there are 3 antenna located on the back. And I was just thinking maybe one of these got pulled away and is barely making a connection.
So my questions before I try to open this thing is as my last resort are:
1. Does this sound like a Radio Issue? I was always under the impression that the Radio is flashed with the Rom, but I could be mistaken? If it isn't flashed with a Rom, do I have to be S-Off to flash the Radio? Or is it a simple zip that you install from fastboot or Recovery.
2. Would S-Off help me in this problem maybe by doing something else. I know I read that reflashing the boot.img helped some, but for the life of me, I cannot get it done. I have extracted the boot.img from the rom I am using but I cannot get it flashed. It just stops on <waiting for device> when adb devices show that the phone is recognized and authorized. When I tried moonshine s-off everything is being recognized but it errors out at the rom is incompatible.
Any help is greatly appreciated in this problem. Thanks a lot for any replies
beeson76 said:
As the Title suggests this is the root problem of why I have gone through all the stuff I have. I have an HTC One that doesnt have any data (when I say data in this instance I also mean no cell service too).
My father-in-law has given me this phone to see if I can do anything with it. Data shows it is unavailable. Every once in a while bars will be full but will be on either G or E network, and if a text message is waiting to be sent or delivered, it will eventually come through. When I say eventually I mean after an hour or so--I guess when it hits that exact moment I get cell service, but then bars are gone and nothing. So cell service and data are pretty much shot and do not work at all. Only thing is said that has happened just recently is he had it in his back pocket and sat on it very briefly and noticed it immediately. But he didnt notice any problem until about a few days later when all of a sudden no data at all--couldn't make phone calls or browse the internet unless on WiFi. Wifi by the way works perfectly.
So I am approaching it from both Software and Hardware side. I approached Software first mainly because I saw videos on how to open this and it looks like a nightmare that only ends in a cracked screen. Here is what I did
1. Unlocking Bootloader
2. Installing TWRP and rooting
3. Different Roms (No roms seem to help)
So I have a HTC One that is fully rooted with recovery. The only thing I don't have is S-Off which I will be willing to try if it will help with Sunshine S-Off.
I figure Hardware could be a problem, because maybe when he sat on it, it just so happened that he pulled an antenna away from the connection. I noticed from the videos that there are 3 antenna located on the back. And I was just thinking maybe one of these got pulled away and is barely making a connection.
So my questions before I try to open this thing is as my last resort are:
1. Does this sound like a Radio Issue? I was always under the impression that the Radio is flashed with the Rom, but I could be mistaken? If it isn't flashed with a Rom, do I have to be S-Off to flash the Radio? Or is it a simple zip that you install from fastboot or Recovery.
2. Would S-Off help me in this problem maybe by doing something else. I know I read that reflashing the boot.img helped some, but for the life of me, I cannot get it done. I have extracted the boot.img from the rom I am using but I cannot get it flashed. It just stops on <waiting for device> when adb devices show that the phone is recognized and authorized. When I tried moonshine s-off everything is being recognized but it errors out at the rom is incompatible.
Any help is greatly appreciated in this problem. Thanks a lot for any replies
Click to expand...
Click to collapse
First can you tell us a little more about your phone (post the output of "fastboot getvar all" except your imei and serialno). That will help determine what you can try on the software side.
Also make sure that your IMEI isn't blacklisted (shouldn't happen if the phone isn't declared lost/stolen or linked to unpaid bills). You might also want to try another sim card and check if its better or not (also try your sim card in another phone).
alray said:
First can you tell us a little more about your phone (post the output of "fastboot getvar all" except your imei and serialno). That will help determine what you can try on the software side.
Also make sure that your IMEI isn't blacklisted (shouldn't happen if the phone isn't declared lost/stolen or linked to unpaid bills). You might also want to try another sim card and check if its better or not (also try your sim card in another phone).
Click to expand...
Click to collapse
Thanks Alray for the reply. I guess I should of mentioned that my father-in-law is on ATT. After the loss of network, he tried his wifes sim card in his phone. It didnt work. So he tried his sim card in his wife's phone and it worked fine. So he went to the ATT store and got another sim card just thinking something happened to the sim card and that new sim card didn't work as well in his phone. So when I got it, I put in my sim card which is off the Straight Talk Network which is using the ATT network and it didnt' work. So after troubleshooting it with the Sim Cards, I feel the Sim Cards are not the problem.
This is where I am having a problem. Whenever I type anything fastboot all I get is <waiting for device>.
ADB recognizes the phone being connected and I can do anything ADB.
Any other way of using "fastboot getvar all" to get the information.
Thanks again for the help. Keep it up I really appreciate it.
This is what I am getting when I type "fastboot getvar all"
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>fastboot getvar all
< waiting for device >
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>
X's are what I put in there. "adb devices" was used before and after the fastboot getvar all command. So it is seeing the device. Just not doing anything fastboot. I know this is probably something simple. What I do is make a platform tools folder that I keep everything in and I keep that on my Desktop of my computer. For me it keeps everything organized for the project I am working on. Would that mess anything up with Fastboot.
beeson76 said:
This is what I am getting when I type "fastboot getvar all"
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>fastboot getvar all
< waiting for device >
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>adb devices
List of devices attached
HT36XXXXX720 device
C:\Users\XXXX\Desktop\XXXX platform-tools HTC One>
X's are what I put in there. "adb devices" was used before and after the fastboot getvar all command. So it is seeing the device. Just not doing anything fastboot. I know this is probably something simple. What I do is make a platform tools folder that I keep everything in and I keep that on my Desktop of my computer. For me it keeps everything organized for the project I am working on. Would that mess anything up with Fastboot.
Click to expand...
Click to collapse
fastboot commands only works from the bootloader as opposed to adb commands which are working from the OS or from a Custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome Alray. Thanks for your help and for the nice chart your provided. Here are the results of the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
all: Done!
finished. total time: 0.094s
Thanks for the help and I hope this can help getting the problem solved
beeson76 said:
Awesome Alray. Thanks for your help and for the nice chart your provided. Here are the results of the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
all: Done!
finished. total time: 0.094s
Thanks for the help and I hope this can help getting the problem solved
Click to expand...
Click to collapse
Maybe you should try to flash the latest AT&T RUU (7.23.502.1). If the problem persist after flashing the RUU and setting the correct AT&T APN, its probably an hardware problem since the RUU will flash everything (software and firmware) back to stock.
The 7.23.502.1 RUU can be found in this thread at post #1: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944. Instructions how to flash the RUU in the same post. BUT you'll need to follow instructions at the end of post #2 before flashing the RUU (downgrading the version-main from 7.23.502.4 to 7.23.502.1).
Hi. Everyone I just bought a second hand HTC One M7 and the phone has software issues. I already researched hours into it and tried to fix it by my self but it seems that HTC phones are the hardest phones to fix... So when I start the phone it goes into a infinite bootloop, if I start the bootloader by holding volume down + power, the phone goes into hboot and shows this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So it looks like the phone's bootloader is Locked and S-ON.
Now going deeper into the rabbits hole, the phone appears to be SuperCID 11111111, but who knows? Maybe the previous owner changed its CID...?
(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.401.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA416W901137
(bootloader) imei: 3594050*******
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3795mV
(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
Anyway I tried, Factory Reset, NOTHING, I tried Recovery, nothing, still infinite bootloops. I tried making the phone S-OFF with rumrunner_HTC_0.5.0 and damn I can't even do that. It says "Failed"....
I tried flashing this zip RUU with fastboot: PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip
And it says FAIL file too large or something... the file is about 1.56GB
I even tried copying the RUU archive on a memory flashdrive and connect it via OTG cable. I saw on many threads on this forum suggestions that if the phone can't be flashed through a computer + fastboot, then it must be flashed via "SD card method". What in the world does this even mean? I don't understand?? M7 does NOT have a SD card slot.
Maybe the previous owner accidentally flashed a wrong rom? I don't know, all I know is that this phone consumed at least 12 hours of my time and all for nothing, I still haven't fixed it.
Can someone help me fix this phone? I would be very grateful!
Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!
myrunes said:
Ok, forget all of that. I finally managed to flash the ROM PN07IMG_M7_U_L50_SENSE60_MR_hTC_Asia_TW_7.18.709.1 51_Radio_4T.35.3218.16_10.33Q.1718.01D_release_458 881_signed_2_4.zip, I was stunned when I was greeted with a "Success!" message in fastboot, I rebooted the phone but the phone is still not repaired. I still get bootloops, same behavior, any ideas? Should I try a different ROM? What do you recommend? The phone behaves as if I didn't flash anything....
Thanks!
Click to expand...
Click to collapse
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)
alray said:
7.18.709.151 is a M7_U ruu (for the non-LTE variant).
Try with the 7.19.401.51 version and post results (a screenshot or cpoy/paste of your cmd window)
Don't forget that you must use htc_fastboot.exe to flash the ruu (not fastboot.exe form google)
Click to expand...
Click to collapse
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks
myrunes said:
I also tried this:
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.5 1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_4588 03_signed.zip
and this
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed_2_4.zip
and it didn't work! I even unlocked the Bootloader, its all good it says "unlocked tampered" now, then installed both TWRP and CWM the phone said "OKAY" after installing but then when I go to recovery, NOTHING! It says "Entering Recovery..." then the phone goes into endless restarts. Perhaps my phone has hardware damage such as a failed NAND chip? At this stage I'm really leaning towards believing that the hardware part, (motherboard) is defective, not just software issues...
There's also a possibility that the phone was flashed with a wrong RUU and this is why its behaving like this however, no matter how wrong the RUU might have been, its still strange that with a unlocked bootloader I cannot properly install a custom recovery such as TWRP.
If Im doing something wrong then please let me know. Thanks
Click to expand...
Click to collapse
When you phone is S-ON it must have a locked or re-locked bootloader to flash RUU. Only with S-OFF you can flash a ruu with an unlocked bootloader. TWRP should flash fine if your bootloader is unlocked. Try MDMower's universal version of twrp: https://android.cmphys.com/twrp-m7/
Try flashing this 7.19.401.51 RUU.zip file.
https://androidfilehost.com/?fid=24369303960689843
Don't forget to relock the bootloader and use htc_fastboot.exe to flash the zip