Hello people,
i've bought a fresh (kinda thought of) HTC M8 blue color from a guy. It looked really nice outside & inside, not a single scratch, not laggy and cool phone so i decided to buy it.
Once i got home i saw that it's broken or something, that guy doesn't answer his phone so i think he lied to me.
About the problems: flashlight doesn't work, phone unlocks after 3 sec~ once you press unlock button, g-sensor doesn't work, and if you turn it off it doesn't turn on without factory reset through recovery mode, that's only thing you can do once phone got shut down or battery drowned. I've tried to install custom ROM's, still the same, can't even back to stock firmware now without Sunshine thing for 25$, but i think it's not even worthy if the phone is broken (?). Maybe some of you have passed through the same or kinda similar problem? Would be nice to hear something, and i could even donate for you if you would decide to help me pass it through. THANKS, community! :good:
Lukitauskas said:
Hello people,
i've bought a fresh (kinda thought of) HTC M8 blue color from a guy. It looked really nice outside & inside, not a single scratch, not laggy and cool phone so i decided to buy it.
Once i got home i saw that it's broken or something, that guy doesn't answer his phone so i think he lied to me.
About the problems: flashlight doesn't work, phone unlocks after 3 sec~ once you press unlock button, g-sensor doesn't work, and if you turn it off it doesn't turn on without factory reset through recovery mode, that's only thing you can do once phone got shut down or battery drowned. I've tried to install custom ROM's, still the same, can't even back to stock firmware now without Sunshine thing for 25$, but i think it's not even worthy if the phone is broken (?). Maybe some of you have passed through the same or kinda similar problem? Would be nice to hear something, and i could even donate for you if you would decide to help me pass it through. THANKS, community! :good:
Click to expand...
Click to collapse
sorry to hear about your mis fortune, well first I think you should name and shame, where did you buy it from ?
next are you able to post the fastboot getvar all of the phone, be sure to remove imei and serial number before posting.
Seanie280672 said:
sorry to hear about your mis fortune, well first I think you should name and shame, where did you buy it from ?
next are you able to post the fastboot getvar all of the phone, be sure to remove imei and serial number before posting.
Click to expand...
Click to collapse
Do i have to get my phone into fastboot mode, because if i will.. I will have to factory reset again.. :crying: But if it would help i'll do tomorrow possibly. By the way, i got it from guy, which i don't really know, so i can't post him.. But shame on him, i got this problem now..
Lukitauskas said:
Do i have to get my phone into fastboot mode, because if i will.. I will have to factory reset again.. :crying: But if it would help i'll do tomorrow possibly. By the way, i got it from guy, which i don't really know, so i can't post him.. But shame on him, i got this problem now..
Click to expand...
Click to collapse
yes you will have to go into fastboot usb mode to get the full info, the command is fastboot getvar all post the info here without imei and serial number please.
Seanie280672 said:
yes you will have to go into fastboot usb mode to get the full info, the command is fastboot getvar all post the info here without imei and serial number please.
Click to expand...
Click to collapse
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4B3******
(bootloader) imei: 357********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
Lukitauskas said:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT4B3******
(bootloader) imei: 357********
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
Click to expand...
Click to collapse
quite an easy one to try and sort out, but backup anything you want to keep first and then follow this post, its the same files for your phone:
ok you have to downloaded this file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease: https://www.androidfilehost.com/?fid=95916177934518148
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do these commands:
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
this will return your phone to full stock and fix any messing about that the last owner did to it.
Seanie280672 said:
quite an easy one to try and sort out, but backup anything you want to keep first and then follow this post, its the same files for your phone:
ok you have to downloaded this file, put it in the same folder as ADB and fastboot files and rename it to RUU for ease: https://www.androidfilehost.com/?fid=95916177934518148
you will need to use the HTC_fastboot.exe to flash it, normal fastboot wont flash Lollipop RUU's, get the htc one from here and put in the same folder as your RUU.zip and other adb and fastboot files: https://www.androidfilehost.com/?fid=95916177934550031
then do these commands:
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
fastboot oem rebootRUU (phone screen should go black with sliver HTC logo)
htc_fastboot flash zip RUU.zip (YOU MUST USE THE HTC_FASTBOOT to flash the zip, the normal fastboot wont work, now leave it alone to do its thing, takes about 10 mins, no need to issue this command twice as its automatic with the htc_fastboot)
now make sure when its finished and you have a command prompt and that it says successful at the end and OKAY
if so then type fastboot reboot-bootloader
now fastboot reboot
this will return your phone to full stock and fix any messing about that the last owner did to it.
Click to expand...
Click to collapse
--
I did that, it went successfully, but all of the problems still remains.. Now i'm starting to think that it's motherboard is faulty or some part, i don't know.. But i know, that i lost money by buying it, that's all.
Related
reposted from wrong forum
What happened: Rooted and installed Cyanogenmod 11 snapshot. Ran for a week just fine though I ****ed up the boot animation trying to change it, in case that matters. After a week, I open my phone that had been on and none of the apps worked or gave any response and then they disappeared and reappeared. Rebooted phone and it kept stopping at my blank boot animation, a blank illuminated screen after the HTC splash screen.
In TWRP, I am unable to format, wipe or do anything that I can think of to /data. Every time: "Unable to mount E:/data" Not totally sure what that means but it sounds quite important. Definitely not sure why. A possible hard drive failure? Any tips or advice?
Related, if my phone is dead: I am having difficulty switching phones through Verizon to my old flip phone. It seems they are waiting for the SIM card on my m7 to turn off, however that doesn't seem like it's happening with my dead phone. They said it would take up to 24 hours, it's been three days. I guess I'll need to take it in to the Verizon store, who might not give any help once they see I voided the warranty. Is there any way to "turn off the SIM card" and get my flip phone to work, even if the m7 is dead?
Thanks in advance
Unsure if this helps vv
"fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: [removed]
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3783mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TWRP version 2.7.0.8
Try to ruu your phone. Be sure to back everything up
Sent from my HTC6500LVW using XDA Free mobile app
no_trace said:
reposted from wrong forum
What happened: Rooted and installed Cyanogenmod 11 snapshot. Ran for a week just fine though I ****ed up the boot animation trying to change it, in case that matters. After a week, I open my phone that had been on and none of the apps worked or gave any response and then they disappeared and reappeared. Rebooted phone and it kept stopping at my blank boot animation, a blank illuminated screen after the HTC splash screen.
In TWRP, I am unable to format, wipe or do anything that I can think of to /data. Every time: "Unable to mount E:/data" Not totally sure what that means but it sounds quite important. Definitely not sure why. A possible hard drive failure? Any tips or advice?
Related, if my phone is dead: I am having difficulty switching phones through Verizon to my old flip phone. It seems they are waiting for the SIM card on my m7 to turn off, however that doesn't seem like it's happening with my dead phone. They said it would take up to 24 hours, it's been three days. I guess I'll need to take it in to the Verizon store, who might not give any help once they see I voided the warranty. Is there any way to "turn off the SIM card" and get my flip phone to work, even if the m7 is dead?
Thanks in advance
Unsure if this helps vv
"fastboot getvar all"
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: [removed]
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3783mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TWRP version 2.7.0.8
Click to expand...
Click to collapse
You are s-off, so just pick an RUU, put it into RUU mode and flash it. I doubt it is dead.
Can't relock my phone to apply the RUU?
C:\Windows\system32>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (No such file or directory))
finished. total time: 1.218s
no_trace said:
Can't relock my phone to apply the RUU?
C:\Windows\system32>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (No such file or directory))
finished. total time: 1.218s
Click to expand...
Click to collapse
you didn't need to relock for ruu
Why would you think you need to lock it? Luckily you are s-off, so unlocking is easy. But for god's sake don't put it to s-on. And you can go ahead and unlock it too.
---------- Post added at 09:45 PM ---------- Previous post was at 09:42 PM ----------
no_trace said:
Can't relock my phone to apply the RUU?
C:\Windows\system32>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (No such file or directory))
finished. total time: 1.218s
Click to expand...
Click to collapse
Here is how to fix it
Download an RUU file, this is an older one but it is signed and you can take otas afterwards to update to newest firmware etc
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"
ccarr313 said:
Why would you think you need to lock it? Luckily you are s-off, so unlocking is easy. But for god's sake don't put it to s-on. And you can go ahead and unlock it too.
---------- Post added at 09:45 PM ---------- Previous post was at 09:42 PM ----------
Here is how to fix it
Download an RUU file, this is an older one but it is signed and you can take otas afterwards to update to newest firmware etc
http://bit.ly/vzwone10
then put the file in your fastboot / adb directory, and rename it to Rom.zip
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip Rom.zip (rename file to Rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip Rom.zip
Then when it finishes, type "fastboot reboot"
Click to expand...
Click to collapse
Hello and thanks.
1)locking the bootloader failed, thankfully... got bad advice from a 4 year old post that I didn't realize...
2) "fastboot oem rebootRUU" has not been sending the phone into RUU mode with the silver HTC logo. It reboots and gives a blank illuminated screen after the HTC splash which is what happens when I try to boot the phone normally. I don't know why. Flashing doesn't seem to take here, got a couple <waiting for device> messages
no_trace said:
Hello and thanks.
1)locking the bootloader failed, thankfully... got bad advice from a 4 year old post that I didn't realize...
2) "fastboot oem rebootRUU" has not been sending the phone into RUU mode with the silver HTC logo. It reboots and gives a blank illuminated screen after the HTC splash which is what happens when I try to boot the phone normally. I don't know why. Flashing doesn't seem to take here, got a couple <waiting for device> messages
Click to expand...
Click to collapse
make sure you are in fastboot usb from bootloader menu. mine would say waiting for device, then i had to power it off then go into fastboot mode when powering off while holding volume down
no_trace said:
Hello and thanks.
1)locking the bootloader failed, thankfully... got bad advice from a 4 year old post that I didn't realize...
2) "fastboot oem rebootRUU" has not been sending the phone into RUU mode with the silver HTC logo. It reboots and gives a blank illuminated screen after the HTC splash which is what happens when I try to boot the phone normally. I don't know why. Flashing doesn't seem to take here, got a couple <waiting for device> messages
Click to expand...
Click to collapse
What?
Does anyone have any kind of advice? I wil GLADLY post any more information if it helps. THANKS
I Was following the guide > http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792 to update my firmware and CID which i successfully did. As per the tutorial, it mentioned that i should copy a ROM on sdcard before procedding. Which i did but amazingly the ARWWizard also flashed my SDCARD (? Not sure but my card was empty).
Anyways, I was able to boot into the OS (old) and i realized i need to install recovery. I issued
Code:
adb reboot bootloader
fastboot flash recovery <recovery_image>
I tried installing TWRP 2.8 but it remains stuck at "Entering Recovery", so i isntalled 2.7 and I was successfully in the recovery. There I wanted to cleaned everything, internal storage, cache, delvik cache etc (not microsd). And went on to menu to install OS from sdcard but it was empty.
I thought lets do the sideload with
Code:
adb sideload rom.zip
and got error Can not read rom.zip.
I changed the location of rom.zip to other location and did adb from that location but still no luck. I was under the impression that since i have installed recovery ... I can reboot ... I tried and now i am stuck at Android Boot loading screen ...
While on that screen, my computer shows that it is trying to install MTP drivers but it fails and hence now i can't use ADB to reboot or do anything.
Any help would be appreciated.
I answered you here!
Forsaked said:
I answered you here!
Click to expand...
Click to collapse
alright .. after struggling so much i am finally able to have my phone running. But i guess the ARUWizard didn't upgraded the firmware. The reason i am saying this is that I installed Viper4.1 ROM and it clearly stats in their FAQ that my WiFi wouldn't work if i don't have proper firmware.
Looking at this guide I am confused which firmware to install.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go
EddyOS said:
If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go
Click to expand...
Click to collapse
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing
..alee said:
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing
Click to expand...
Click to collapse
Very nearly right...
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
[B]fastboot reboot-bootloader[/B]
fastboot flash recovery twrp.img
You missed the dash
The firmware flash might need to be done twice. If it says it's failed and reboots the unit, do the same command again to flash it but if it says complete then reboot the bootloader to flash TWRP
Thanks ...
I got it working but now there are two weird issues.
1. My camera doesn't work. Whenever i click on HTC Camera, it shows a black screen (as if camera view is blocked, I can see on screen buttons and options but black background).
2. My phone doesn't recognize the SD Card which i was using before.
Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?
EddyOS said:
Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?
Click to expand...
Click to collapse
Just want to let you know that the camera issue is before installing this ROM. It was because of the camera that i decided to upgrade from 4.3 to 5.0 Android. The SD card issue has been resolved. Here is my fastboot command details
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now
EddyOS said:
I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now
Click to expand...
Click to collapse
my main version is blank ever since I started upgrading my phone. Even if you look at the posts which posted 3 days before (before upgrading) they all had blank main-version.
True. If you are willing to try putting your phone back to 100% you could use the guide in my signature and then at least you'll be back to a point where it should all work
okay ... from your post it seems like only devices with HTC_* CID's can be restored to stock. Given that I am supercid, I can write whatever CID I Can but my original cid was VODP001. Do i have to worry about that ? Would your method work on my device as well ?
Super CID means you can flash anything so just try it. OK, it'll go back to the unbranded build as opposed to the Vodafone build but that's not a bad thing
HTC One M8
Unlocked and S-off
From UK so with international network
Cyanogenmod 11 i think
Clockwork recovery
Soooo i bought the M8 secondhand with Cyanogenmod installed, however, i couldnt do any updates due to error status 7. i tried the normal fix (delete code which checked authorisation of phone) but to no avail. since then the error came back and i managed to get a different error on reboot: "root access possibly lost. fix?". I've cleared cache(s) and done a factory reset. No matter what i pressed it would be in a boot loop. I can still get to bootloader and recovery. then i tried to change the recovery to TWRP however when i try and fastboot, my device is not recognised by my laptop so i cannot add the ADB driver to the device.
sorry for sounding very vague / idiotic, i have no idea what i have done and no idea what i am doing to try and fix it. that means sadly i will need to be spoonfed the fix. if you need any more details or pictures of the problem let me know
thanks in advance
josborn42 said:
i couldnt do any updates due to error status 7. i tried the normal fix (delete code which checked authorisation of phone) but to no avail.
Click to expand...
Click to collapse
Are you trying to update to CM12.1? If so, the error is for a reason, and not to be bypassed in the way you describe.
If you are on an hboot older than 3.19, I don't think it will work with CM12 and 12.1. You'll need to update hboot (and rest of firmware, preferably) to proceed.
Also, CWM may be too old for CM12 as well.
josborn42 said:
then i tried to change the recovery to TWRP however when i try and fastboot, my device is not recognised by my laptop so i cannot add the ADB driver to the device.
Click to expand...
Click to collapse
Not sure what you mean here. Are you trying to install HTC Sync (and corresponding driver) by connecting the phone?
You can just do an XDA search for "simple adb" and you will find a couple really easy adb/fastboot installers.
how do i see what hboot i am on? and how would i update it?
i've installed HTC Sync but it doesn't recognise my phone being connected (so i cant view any files on the phone) and i've installed a simple ADB/fastboot but i can't see the driver option when trying to add it to my phone on Device manager. i have got to the stage whereby i have the ADB/fastboot folder and have the TWRP file in the same folder, just i cant get any further.
where would i begin getting to cyanogenmod 12.1, or would it be easier to revert back to a basic android os?
i know this is probably incredibly frustrating for you as i am a complete novice, but i greatly appreciate your help
i would post pictures to help but i cant as im a new member, i will when i can
josborn42 said:
i've installed HTC Sync but it doesn't recognise my phone being connected (so i cant view any files on the phone)
Click to expand...
Click to collapse
This in itself does not mean the phone is not connecting by fastboot. And fastboot is the important thing here, so we can update TWRP, etc.
Try rebooting into fastboot mode, and try the command and see if your phone's ID is returned: fastboot devices
If you don't get the phone's ID and just "waiting for device" you do indeed have some type of USB connectivity problem.
josborn42 said:
how do i see what hboot i am on? and how would i update it?
Click to expand...
Click to collapse
Boot into bootloader, andyour hboot number is listed near the top of the screen.
Since you are s-off, its fairly easy to update the firmware (and I would suggest to update all the firmware, not just hboot) by flashing the proper firmware.zip. But let's determine whether that is even the problem, before we worry about flashing firmwares.
hboot is: 3.16.0
also my phone is detected by my laptop so all is well there
i have installed a simple 15 second ADB file but am unsure how to proceed from here
josborn42 said:
hboot is: 3.16.0
Click to expand...
Click to collapse
Your firmware is very old, so will need to be updated to run CM12.1. Also, newer versions of TWRP will not run with your old hboot.
Do a fastboot getvar all, and post the output, but delete your IMEI and serial numbers (as these are private info). Need more details on the phone (particularly CID) in order to know how to proceed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
josborn42 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.107s
Click to expand...
Click to collapse
I'm going to suggest WWE/International firmware. The updates are available way before O2 updates.
Download this firmware (it also includes TWRP2.8.4.0). Rename it to firmware.zip and place it into your fastboot folder.
Next, boot into fastboot and change your CID to superCID (it won't flash with the O2 CID)
fastboot devices to make sure you are connected (a bunch of letters and numbers/your serial# means you are)
fastboot oem rebootRUU (a black screen with the HTC logo means you are in RUU mode)
fastboot oem writecid 11111111 (eight ones) You are now superCID!
Now flash the firmware
fastboot flash zip firmware.zip
If you get "error 90 hboot pre-update" (and you probably will with how old your current firmware is) run the same command again and the firmware will flash properly. The first run only updated your hboot.
The process will stop at 75% to 90%. That's normal and gives you a chance to check your console output. The last few percentage is the reboot.
The bar will fill to 100% after you enter fastboot reboot-bootloader
That's it. Good luck!
thank you both so much! so now do i just download the appropriate cyanogenmod version and flash it over?
josborn42 said:
thank you both so much! so now do i just download the appropriate cyanogenmod version and flash it over?
Click to expand...
Click to collapse
Yes. But there are more ROMs out there as well. Try them out and find the one that suits your needs best.
hi there i have htc one m8 rooted s-on & software status is modified
i got a new update so i flashed the stock recovery then downloaded the update and pressed install
it was loading the update and suddenly the screen frozen on the htc ONE screen without responding
i tried the volume down + power button nothing happened then i tried volume up + power button
it reboots and freezes on the same screen - tried to remove the sim & sd card but nothing happened
what should i do plz ???
cid : htc_j15
build number : 4.16.401.10
I'm having a problem being able to launch apps on my One M8 ATT... I Don't have any apps on my home page and ATT Ready2Go keeps crashing on me. Can someone give me a command line so I can launch SunShine on my device through ADB, that way I can S-Off and go back to a different ROM.
Why would you need s-off to install a different rom ?
Mr Hofs said:
Why would you need s-off to install a different rom ?
Click to expand...
Click to collapse
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.
isutke1287 said:
The phone won't allow me to install anything through an RUU. Every RUU I've tried fails with a 155 Reason (Incorrect RUU) and shows "Loading zip file fail!" in the bootloader. A friend of mine has been working on it, got SunShine installed on the phone. But we want to run it to get the phone in to S-OFF. I'm not too savvy with ABD and that's what he's been using to talk to the phone. I also can't transfer items to the phone via USB even though I have drivers and MTP is running. The phone is a mess and I'm trying to avoid sending to HTC to restore it ($$$$$), or just telling my carrier that I "lost" it and pay the deductible to get a new one. Feels like I'm really close to fixing the phone, just not quite there yet.
If you know of a ROM I could try to flash, I'll give it a shot. I'm running out of options and time. Before I just get a new phone. My friend has helped me out a lot, but it's just not quite there yet.
Click to expand...
Click to collapse
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.
xunholyx said:
You need to relock your bootloader in order to run an RUU while you are S-On.
In fastboot: fastboot oem lock
Then run the proper RUU again.
I'd link you to the proper RUU, but you haven't given enough info.
In fastboot: fastboot getvar all and post the results minus your IMEI and ser# (private information), unless you already know what the proper RUU to run is already.
Click to expand...
Click to collapse
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)
isutke1287 said:
I'm not sure which RUU I need. Again, I'm very new to this, but here are the "fastboot getvar all" results:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *tsk tsk*
(bootloader) imei: *tsk tsk*
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.158s
Android version: 5.0.2
HTC Sense: 6.0
Software Number: 4.28.502.2
HTC SDK API level: 6.55
Not sure what you can tell from this, but I'll wait for a response before I do anything else. I'd also like to get the recent version of TWRP and SuperSU on here as well. Once it's up and running/stable. And.. this may be a dumb question, but I can unlock the bootloader again once I get an RUU to work successfully, right? (getting ahead of myself, I know)
Click to expand...
Click to collapse
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.
xunholyx said:
The RUU you need can be found here.
Scroll down to the Manual System Update Instructions, and read them. The RUU download is at the end of the instructions.
You can unlock the bootloader again through HTCDev.com. After you are unlocked, flash TWRP from here in fastboot, then use that recovery to flash SuperSU from here.
Click to expand...
Click to collapse
I can NOT appreciate and thank you for your assistance in this! I went ahead and locked the bootloader and restored the original image with the RUU you linked me to, yesterday. Couldn't wait to try, haha. I had to sweet talk the HTC Live Chat person to tell me if I could use the RUU for the same software version as I had. Phone has been working like a champ. I'm gonna give it another day or two to settle in, do a few backups just in-case the flash doesn't go well.
I will definitely unlock the bootloader again and flash TWRP and SuperSU. But I imagine going S-OFF is just off the table right now since I'm a bit stripped of funds. I can afford it, haha, but my funds are already allocated towards adulting and such.
Again, THANK you for the support! This has been a learning experience.:good::good::good::good::good:
As a brief overview;
My phone started spitting out errors one day and I tried to turn it off and back on again - It would not get past the htc logo at this point.
I unlocked the bootloader by following one of the guides here and flashed cyanogenmod which took a little effort but I got it done. The problem is that after flashing cyanogenmod, anything to do with sound no longer worked. I can't make or receive phone calls, youtube videos won't launch, spotify WILL launch and will appear to be playing music but there is no sound.
I can receive text messages however and have cellular data and can connect to wifi, browse the internet etc.
I found a backup file for the h3g__001 online and restored it via backup in twrp but it hasn't helped.
Any help would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.771.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
bump
I know nothing about cyanogenmod because I don't use one ..
Have you try reflash htc signed 6.13.771.4 firmware ?
You can get the fw_6.13.771.4.zip from my thread post #5 - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but you need to relock bootloader because your device is S-On
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip fw_6.13.771.4.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_6.13.771.4.zip
fastboot reboot
No guarantee it will fix your problem but worth a try I guess.
You are honestly a rockstar.
Followed your instructions, worked like a charm!
I can't thank you enough.
ckpv5 said:
I know nothing about cyanogenmod because I don't use one ..
Have you try reflash htc signed 6.13.771.4 firmware ?
You can get the fw_6.13.771.4.zip from my thread post #5 - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
but you need to relock bootloader because your device is S-On
fastboot oem lock
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip fw_6.13.771.4.zip
you'll see ERROR/FAILED, repeat
fastboot flash zip fw_6.13.771.4.zip
fastboot reboot
No guarantee it will fix your problem but worth a try I guess.
Click to expand...
Click to collapse
Thank you so much!!! I also had this sound issue and now it's fixed.