Related
Hi,
I'll only get my fist Android phone (HTC Desire) in a few days, so I'm fairly new to this, and have a fews questions :
What does a GoldCard do? Does it only disable the CID check, or also the signature check, or more? And if it also disables the signature check, isn't it enough to root the phone (just make a system image that contains the su utility)?
About unlocking : I've seen that other HTC phones can be unlocked by sending an [email protected] command to the radio from the SPL. What prevents us to do the same on the Nexus and Desire? My guess here would be the lack of a physical serial port on these devices ... and this is my next question.
Do someone have info about a possible access to a serial debug port on the Nexus and Desire?
About the security: I've had a quick look at the SPL, and it seems that the security byte is located in memory right after the IMEI and CID. So my guess is that the security is also controlled by the IPL & radio chip. And in the SPL, there is a reference to an [email protected] command ... I haven't looked deeper, but my guess is as good as yours
About the SPL: I think I have found a few interresting things:
- among the different modes (RRU, Fastboot, hboot ...), there is one called SIMLOCK, which seems to read the SD card, and uses the different files it contains to update the phone (MCC & MNC, IMEI, cid.txt ...). I think it might be used to send AT commands to the radio chip, to update those info, or am I wrong ?
- there seems to be one function that reads the security byte and check if its LSB is equal to 0, at offset 0xFC080 of what might be a SRAM. We could just replace the body of this function by a "MOV R0, #0", to bypass the security check, and have the SPL behave as if security were off. But then, the signature check would fail, wouldn't it? Or could a GoldCard prevent this signature check?
So in the end, if I got it right, I think there would be at least two ways to disable security on both the Nexus and Desire, given that their "logic architecture" (hardware, firmware, memory map ...) is extremely similar :
1/ find the serial debug port on the device, send the correct AT commands to the radio chip, that would make it flip to security=off.
2/ use an exploit to gain root privileges from android userland, then write a patched SPL to the correct /dev/mtdblock device with security check disabled. SPL should then behave as if security were off.
3/ maybe disassemble a bit more of this SD card update mode and learn how to craft one that would turn security off. My latest guess is that this mode might for instance take the content of "cid.txt", prepend "[email protected]=" to it, and send the whole string as a command to the radio chip. But I'm not sure yet if a security update is possible in this mode.
Also, for reference : when using a debugger/disassembler, the SPL should be loaded at 0x8E000000, and the entry point is at offset 0x1000. I haven't looked at the IPL/radio yet, any hints ?
So, do you have any (helpful) thoughts about this, or am I completely wrong ?
Edit: Ok, it seems to work now, I modified the above message. Please ignore (or delete, if you can) this post.
Pleast note that the "(AT)" in the above post should be replaced by the "@" sign. Seems I need a moderator to validate my account.
pipomolo42 said:
Do someone have info about a possible access to a serial debug port on the Nexus and Desire?
Click to expand...
Click to collapse
It seems I haven't searched well enough, as access to the Nexus serial port is described here : http://forum.xda-developers.com/showthread.php?t=625434
I just ebayed a CP2102 board, and I'll try it when I get my Desire.
I know that many people are having this problem and I hope we can find a solution here together.
I've already tried many things to restore my IMEI, a little background:
- Lost my IMEI when I flashed stock rom to unroot the phone.
- Tried flashing different firmwares (LATAM, RETBR, I think they are the same).
- I don't have an EFS Backup.
When I dial *#06#* my IMEI is shown as "0", when I use "mfastboot getvar all" or "mfastboot getvar imei" I can still see my correct IMEI (as shown on the phone box).
On CQATest the only error that I can see is right on the IMEI tab:
Phone ICCID Compare with SIM ICCID: ERROR
Anyone can suggest something that might correct this problem? I don't think anything could make it worse and I'm willing to try everything...
EDIT: Obviously, I can't connect to my mobile network.
This is why I didn't even unlock mine so far.seems many have had this issue
I've seen some people saying that this can occur after flashing fsg and modem plus erasing modemst1 and modemst2.
If I knew that before I could have flashed the stock rom without touching on this images, I don't think it would make any difference.
rfameli said:
I've seen some people saying that this can occur after flashing fsg and modem plus erasing modemst1 and modemst2.
If I knew that before I could have flashed the stock rom without touching on this images, I don't think it would make any difference.
Click to expand...
Click to collapse
From my past moto experience always avoid flashing bootloaders & modems, system files can be flashed without any issues in most circumstances. The only change would be if there's a major update that requires bootloaders and modem images.
As a rule, wait before flashing firmware on a moto phone, I've witnessed people hard bricking their devices flashing bootloaders, downgrading from a updated bootloader is playing with fire in my past experience.
Sent from my XT1635-02 using XDA-Developers Legacy app
flashallthetime said:
From my past moto experience always avoid flashing bootloaders & modems, system files can be flashed without any issues in most circumstances. The only change would be if there's a major update that requires bootloaders and modem images.
As a rule, wait before flashing firmware on a moto phone, I've witnessed people hard bricking their devices flashing bootloaders, downgrading from a updated bootloader is playing with fire in my past experience.
Sent from my XT1635-02 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've flashed the entire room including the bootloader and modems more than a hundred times (no joke here) trying to fix my problem, only to realize I had lost my IMEI.
What make me think that I can still recover my lost IMEI is that on the fastboot if I write "mfastboot getvar imei" it's still there with the same number that came on the box.
rfameli said:
I've flashed the entire room including the bootloader and modems more than a hundred times (no joke here) trying to fix my problem, only to realize I had lost my IMEI.
What make me think that I can still recover my lost IMEI is that on the fastboot if I write "mfastboot getvar imei" it's still there with the same number that came on the box.
Click to expand...
Click to collapse
Obviously something went wrong, my past experience with flashing the full firmware package you are playing with fire.
Sent from my XT1635-02 using XDA-Developers Legacy app
Did you fix it?
IMEI 0
My phone also stucked at imei 0, wat to do is there any solution
Solution for IMEI 0 caused by broken efs partition is easy: Restore your backup of efs partition.
For the case not the efs partition is damaged but the reading process does not get the efs contents right, do a backup of current efs before any further action if there is any small chance the contents is not damaged.
If you don't have a backup of efs and it is still empty/broken after flashing a standard stock rom, you can contact Lenovo for help. May get expensive, they usually replace the mainboard. They should have the possibility to generate a new key for the efs partition, but my guess is that they are afraid doing so may harm security of that key. It probably is cheaper to replace the mainboard than buying a new device, but not by much. You may consider using the device with IMEI 0 as mediaplayer/small tablet without mobile functionality, and buy a new one.
Are you aware of any change you did to the efs partition?
My imei is 0 but still i can connect to mobile data. Hmmm i dont know what is happening here
Same problem here!
Any solution?
I think without the EFS Backup the only way to restore is send to authorized assitance to change the mother board. Sorry for bad news
I have been doing some research lately and discovered some interesting things that may help you in a way or another, the imei value state is written at efs partition, value which can be located from RV_NV_Manager tool (this one is part from QPST suite from Qualcomm), since this tool is known for having the IMEI changing property, i can't post the link, but Google maybe is a good place to start looking for it.
Here are the steps you can do to recover your imei:
-Write down your imei.
-Start some computer with internet, using windows.
-Find, download and install QPST and Qualcomm HS-USB Drivers.
-Once installed, you must turn off your phone and restart it in the bootloader
-Select QCOM tab and select, then wait until it boots completely, then plug your phone at your computer, some drivers must be starting to install, let it finish (it isn't necessary to reboot after this).
-Open QPST Configuration and go to Ports > Add new port...
-Open Device Manager and look for Qualcomm COM ports connected, then in QPST Ports screen write the COMXX in both fields and close, you should see a connected unknown phone and some ? At some fields, that's just normal.
-Open RV_NV_Manager without closing QPST Configuration, some downloading bar should appear with a screen, just let it finish, and then head down to line number 5xx, it says some IMEI_NV or something like that, if you press 9 text fields in boxes should appear at right hand, select hex values at some checkbox there.
-Look to where you written the imei and now it's the tricky part:
Your imei looks like 874356324678338 (just an example), then you must split them by pairs in this way:
x8 | 74 | 35 | 63 | 24 | 67 | 83 | 38 (since imei has 15 numbers, the first one will go alone with an unknown value)
Then just switch numbers by pairs:
8x | 47 | 53 | 36 | 42 | 76 | 38 | 83
Then start filling the boxes in this way:
1st.- 8 (always)
Then put the numbers in pairs in order and replace the 'x' with an 'a':
2nd.- 8a
3rd.- 47
4th.- 53
And so on...
I hope this can help you, let me know if you recover your imei.
xaskasdf said:
I have been doing some research lately and discovered some interesting things that may help you in a way or another, the imei value state is written at efs partition, value which can be located from RV_NV_Manager tool (this one is part from QPST suite from Qualcomm), since this tool is known for having the IMEI changing property, i can't post the link, but Google maybe is a good place to start looking for it.
Here are the steps you can do to recover your imei:
-Write down your imei.
-Start some computer with internet, using windows.
-Find, download and install QPST and Qualcomm HS-USB Drivers.
-Once installed, you must turn off your phone and restart it in the bootloader
-Select QCOM tab and select, then wait until it boots completely, then plug your phone at your computer, some drivers must be starting to install, let it finish (it isn't necessary to reboot after this).
-Open QPST Configuration and go to Ports > Add new port...
-Open Device Manager and look for Qualcomm COM ports connected, then in QPST Ports screen write the COMXX in both fields and close, you should see a connected unknown phone and some ? At some fields, that's just normal.
-Open RV_NV_Manager without closing QPST Configuration, some downloading bar should appear with a screen, just let it finish, and then head down to line number 5xx, it says some IMEI_NV or something like that, if you press 9 text fields in boxes should appear at right hand, select hex values at some checkbox there.
-Look to where you written the imei and now it's the tricky part:
Your imei looks like 874356324678338 (just an example), then you must split them by pairs in this way:
x8 | 74 | 35 | 63 | 24 | 67 | 83 | 38 (since imei has 15 numbers, the first one will go alone with an unknown value)
Then just switch numbers by pairs:
8x | 47 | 53 | 36 | 42 | 76 | 38 | 83
Then start filling the boxes in this way:
1st.- 8 (always)
Then put the numbers in pairs in order and replace the 'x' with an 'a':
2nd.- 8a
3rd.- 47
4th.- 53
And so on...
I hope this can help you, let me know if you recover your imei.
Click to expand...
Click to collapse
I have only RF NV [Items only] and COM3 and COM 5 is connected. I select port 5 and read all items but I can't find NV_IMEI only under "read supported RF NV Items" at Number 550 is a NV_UE_IMEI_I ... but is this the right?
Have Moto Z
Hi!
Does anyone know about a tool to check (and maybe also fix) a bad NAND/EMMC? This is my story:
This Friday I was sitting in my couch and browsing the web on my M9 (HTC__Y13, Europe version) and suddenly it just reboots itself.
This is normal behavior (at least with my phone, happens now and then), but this time it just kept rebooting itself.
I can boot to FASTBOOT but not to "Download Mode" or "Recovery Mode". If I choose Download/Recovery-Mode, it starts to load but just to reboot itself
again.
Pressing VolUp+VolDwn+Pwr takes me to the FASTBOOT menu.
Choosing "Download Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Choosing "Recovery Mode" takes me to a black screen with HTC logo in silver. After a couple of seconds it reboots itself.
Pressing VolDwn+Pwr takes me to a black screen with HTC logo in silver. After a couple of seconds, it reboots itself.
Trying to boot to RUU-mode (fastboot oem rebootRUU) gives me the same behavior.
S-ON: YES
Relocked: YES
Thanks in advance!
From getvar-command (looks pretty strange to me)
Code:
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:HT**********
I modified the value on row "(bootloader) serialno:" for this post, value is proper.
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.
shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like it may have been slowly dying over time.
If you live in the USA or taiwan, or have a warranty you can get a replacement from HTC free of charge.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you so much for your response!
As I suspected
Unfortunately I'm live (and has bought the phone) in Sweden, so I think an unlocked/relocked bootloader = f*cked. But I will contact HTC support anyway.
shivadow said:
I can tell you from the getvar output that the emmc is kaput. It's forgotten what it is. Looks like, from my sherlock skills, it may have an m8 software on there as the serial starts HT where as I'm sure m9's are FA..
Beamed in by telepathy.
Click to expand...
Click to collapse
I agree with you that the EMMC is probably broken. However, the "HT" has nothing to do with the model of the device. (How to read Serialnumbers)
Very creepy. I'm having the same exact bootloop issue as the OP. Friday evening, got stuck on the bootloop. Earlier in the week, I thought I was stuck but hooked it up to my pc and was able to reboot fine. Now I'm most certainly screwed.
I'm ***software status: Official*** ***UNLOCKED*** ***S-OFF***.
Now I'm not sure my phone is even showing up when connected to my PC. When I'd run "adb devices" no devices would show up, but if I did "htc_fastboot getvar all" I had an output similar or same as the OP. I tried to uninstall/re-install HTC Sync Manager, and install the latest Minimal ADB, and now I can't even get that output as seen above.
Where do I go from here? I had the hardest time putting ViperOne on my phone a year ago. I spent three or four weekends studying the forums here. I need detailed instructions or I'll get lost. Thank you all for your work so far here in the forums. If you want to experiment on my phone to get it functional again please feel free to point me in the right direction. I had hoped this post would help, but like I said, I can't see my phone in task manager. (Also, I'm not sure about step 4., I don't see an MAF32 file in what I extracted from the latest minimal adb files.). Please help!
Download mode and then htc_fastboot getvar all.
Qualcomm makes publicly available software that controls the raw hardware so that the manufacturer can upload their firmware. I can't remember where I saw it but it was only a short google search to find it.
It may help. It may not help.
Beamed in by telepathy.
I left the phone on the bootloader screen, plugged in to the PC. I think it got a solid charge overnight, and I am now able to boot normally. In the interest of making my phone more stable, I've tried the No wipe.zip method as seen here to go from 3.35.401.12 to the M9_4.14.401.7_NoWipe_TWRP3030.zip, followed by a TWRP wipe. My Venom ROM would still be based on the older firmware. Also, download mode screen shows the older firmware OS version. Will this cause problems? What can I do to make my phone stable again?
Joining the flock
Hello all. My first post here. I have the same issue on my m9
Status modified, s-on, locked, security warning.
Can't access download mode or recovery. It gives me the green logo on white background with red warning text ('failed to load... This build is for...').
Adb can't see device.
Issue appeared after cracked display started ghost touching all over. Changed system language and such before I turned it off. I went to unofficial service to replace display/frame set and they said it's locked on bootloader.
From what I see here, others with screwed up NAND experience bootloop and can't access download mode..
I just want to be 100% shure it's bricked forever before selling it for parts. I want to fight for my 'baby' to the very end.
So how can I test this or are there any there any tricks I can use to make it boot/get to download mode?
Thank you!
Later edit: don't know if this means anything, but if I select Reboot to Bootloader, the security warning is missing. It just appears if I user the other options.
Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.
groxack said:
Well I see that im not the only one, same model, same problems, I was able to boot twrp using "fastboot boot twrp.img", but it shows 0 mb for internal storage, also trying to repair any partition using e2fsck results on "proces ended with ERROR: 8 unable to reapir data", I also was able to adb push the whole bad_boys custom rom zip without a problem but unfortunately i just recive errors while trying to install it.
Click to expand...
Click to collapse
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?
ludemon said:
It seems that I have the same problems as you. Also booted into TWRP and tried to restore various 401 back-up options but without success; partly restores then get lots of red text about unable or failed to mount.....etc.
Did you find a solution to the problem?
Click to expand...
Click to collapse
Further to the above, whilst in TWRP I used the command adb shell getprop and in the result noticed that there are references to OmniROM. The main one being [ro.modversion]: [OmniROM-6.0.1-20171209-hima-HOMEMADE]. I assume that someone has previously flashed OmniROM and this has caused the brick.
As far as I know HTC devices are not supported by OmniROM.
Does anyone know if the phone is recoverable from this condition?
Hi,
I have just discovered that I can hear no sound when I use my HTC M8 dual sim phone for phone calls (I don't use it for calls very often so it could have been like this for a while?).
It seems this is a common problem but I have not managed to find what the solution is so any advice would be very welcome.
I have resetting to factory defaults, clearing the cache, plugging headphones in and out, turned blue-tooth on then off but still the same.
I have LineageOS v15.1 on it with no Google apps but I have tried going back to v15.0 (it definitely used to work ok with this version) but no change.
btw - sound works ok with through the headphones or on speaker but nothing from the inbuilt ear piece speaker.
Adnl info:
I have installed some software which records phone conversations but this records silence which I think confirms my suspicion it is a software problem (if it were a faulty speaker this would still record the audio being sent to it)
I have also tried an app which sends all audio to the earpiece but still no sounds comes from it
Anyone got a solution to this?
It seems a very common problem so I am guessing there is a fix
I have ordered a replacement speaker but I am reluctant to fit it as it is a difficult task and I am pretty convinced it is a software problem but at the moment this is the only option I can think of before consigning this phone to land fill.......
Did you try going back to stock Sense to see if the issue persists? Did it work correctly (sound when on calls) when on stock ROM?
redpoint73 said:
Did you try going back to stock Sense to see if the issue persists? Did it work correctly (sound when on calls) when on stock ROM?
Click to expand...
Click to collapse
I did consider that but wasn't confident I knew how to do it and hoped someone somewhere would know a simple fix (with it seemingly being a very common problem).
This morning I gave it a try, but I proved myself right in that I failed - lol
When I try to install the stock foirmware (with the command "fastboot flash zip xxx.zip") after a few mins it returns the error "FAILED-remote: 32 header error".
alanes said:
When I try to install the stock foirmware (with the command "fastboot flash zip xxx.zip") after a few mins it returns the error "FAILED-remote: 32 header error".
Click to expand...
Click to collapse
Not enough detail to know what you did wrong here. Always give exact file names (and where you got it from); since the term "stock firmware" can literally mean dozens of different things, and we have no idea what you flashed if you are not specific.
Also, if it is an RUU, using the "generic" fastboot is likely not going to work (need htc_fastboot). But given the header error, I don't think you even have the right file for your device.
---------- Post added at 09:28 AM ---------- Previous post was at 09:20 AM ----------
Did you put Lineage on the device, or was it already on there when you got the phone? Since you never answered my question whether calls worked correctly when on stock ROM. Always do your best to answer all questions posed to you, if you want us to try to help.
If you flashed Lineage, you should know how to go back to the stock ROM. Best practice and a basic golden rule of modding phones (whether it be flashing custom ROMs, root, etc.): never do anything you don't know how to reverse. Always have an escape plan. You should know how to go back to stock, before doing any mods. If you don't know, ask. But waiting until there is a problem, to try figure out how to return to stock.
Did you make a TWRP backup before flashing Lineage? Again, another basic golden rule of phone modding: always make a nandroid (TWRP) backup of the stock ROM before root, custom ROM, etc.
Thanks for your replies. Sorry for not giving enough info., I think I am getting too frustrated with the whole thing....I could write a novel about the stress I have had with this phone.
I decided I wanted LineageOS but it was not available for the phone I had so after much research I decided the HTC M8 was the only phone supported with most of the features I wanted (especially dual sim) so I bought one and set about putting Lineage on it. Turned out to be much more difficult than the instructions suggested and I estimate I spent something like 200hrs on it before finally getting it working (with much help from this forum) - This included having to take the phone apart as it turned out a coax cable was missing for the GPS and then had to replace a button.
I finally had it all working and pretty pleased with it then suddenly after a month or so it stops working as a phone and so is now pretty much useless
When I had it all set up and updated with the HTC stock rom I did a TWRP backup but after installing Lineage I realised I had backed it up to the wrong place and so lost the backup
I took notes when I installed the stock rom and kept all the files (or so I though) so I had a backout plan but had never tested it and knowing the problems I had had always suspected I would have trouble if I tried it.
Calls always worked correctly with all the firmwares I have had on this phone, although I can't say for sure it ever worked when I upgraded to LineageOS v15.1 from 15.0
I thought I had seen this problem before but referring to my notes this was a different problem I had hanging up calls with LineageOS 14.
The RUU I used is the one I used when I first set up the phone:
0P6BIMG_M8_DUGL_L50_SENSE60_MR_HTC_Europe_4.30.401.15_Radio_1.24.30336021.13G_30.69.336021.00_F_release_428493_signed.zip
from https://easy-firmware.com/home/browse/category/id/7825/
I did not use the HTC Fastboot so this may well be the problem. I will give it a try and let you know...........
I don't think I used it originally but could be wrong.
Can you please do fastboot getvar all, and post the result (delete IMEI and serial number before posting)? I'd like to see more info about the phone.
To be clear, I don't have the dual SIM M8 (just the single SIM one). So my assistance may be limited. But some things are same/similar, so I'll try to help as much as I can.
Some comments below in red font:
alanes said:
This included having to take the phone apart as it turned out a coax cable was missing for the GPS and then had to replace a button.
I finally had it all working and pretty pleased with it then suddenly after a month or so it stops working as a phone and so is now pretty much useless
So the phone (earpiece sound) worked after you did the hardware repairs? But then stopped working about a month later? I'm suspicious of a hardware issue related to the repair. But flashing the stock RUU (if we can do it) will help determine whether it's a hardware or software problem.
When I had it all set up and updated with the HTC stock rom I did a TWRP backup but after installing Lineage I realised I had backed it up to the wrong place and so lost the backup
What does that mean "wrong place"? You backed up to internal storage, then wiped internal storage, thinking the backup was on SD card?
I did not use the HTC Fastboot so this may well be the problem. I will give it a try and let you know...........
I don't think I used it originally but could be wrong.
You definitely need to use htc_fastboot. The "generic" Google fastboot can't handle the large file size of an RUU. But in that case, it will usually give you an error message to that effect (file size too large); and not "header error". I have a feeling the error may have to do with the version number, but the getvar data will tell me more
Click to expand...
Click to collapse
redpoint73 said:
Can you please do fastboot getvar all, and post the result (delete IMEI and serial number before posting)? I'd like to see more info about the phone.
:
Click to expand...
Click to collapse
Yes, I thought I had backed up to SD card but was wrong
I have just discovered the microphone doesn't work either. I have software which records phone conversations but this now just records nothing, if it were a wire off the speaker or something I think this would still work.
I spent all this morning trying again but still getting the same error. I am wondering if it is because my phone was upgraded(via the HTC automatic updates) to version 6.16.401.101 and so now doesn't like going back to the older version?
Would it be a bad idea to try the file "0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.101_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465002_signed.zip"?
- although if this worked I guess it wont install the updates which is what I am hoping will get the phone working again as I keep reading that HTC released an update for what sounds like the problem I have.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.30336021.13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.401.101
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxx
(bootloader) imei: xxxxxxx
(bootloader) imei2: xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
alanes said:
I spent all this morning trying again but still getting the same error. I am wondering if it is because my phone was upgraded(via the HTC automatic updates) to version 6.16.401.101 and so now doesn't like going back to the older version?
Click to expand...
Click to collapse
Since you have s-off, it should be okay to flash an older version; as long as it is the proper RUU for your CID and MID, which it appears to be. Unless HTC imposed some limitation on the M8s, that isn't present on M8 (meaning, at least on the M8, flashing older RUU is okay as long as you are s-off).
alanes said:
Would it be a bad idea to try the file "0P6BIMG_M8_DUGL_M60_SENSE70_MR_HTC_Europe_6.16.401.101_Radio_1.24.30336021.13G_30.69.336021.00_F_release_465002_signed.zip"?
- although if this worked I guess it wont install the updates which is what I am hoping will get the phone working again as I keep reading that HTC released an update for what sounds like the problem I have.
Click to expand...
Click to collapse
That should be the perfect RUU for you to flash, given the current main version you show in getvar. Verify it is a full RUU (>1 GB).
The RUU will include all partitions updated to version 6.16.401.101, including whatever was updated. And you should get any updates after that, if there are any. So I'm not sure what you are saying, that you don't think you will get updates.
Thanks, I will give it a try tomorrow (It won't let me download it as it says I have hit my daily limit for the site)
I was told when I first set up the phone that there are lots of partitions which I am not aware of which HTC updates will modify etc., which is why I had to do the official HTC updates to the latest version before I was able to install LineageOS (but I may well have misunderstood).
Gave it a try this morning but same error message as before
I even tried it on a different computer but no change
Just in case I am doing something wrong, what I do is:
First wipe all the partitions using TWRP (apart from sd card) then use htc-fastboot to try and send the RUU zip file
I have not removed TWRP although I did once try first uploading the HTC recovery file corresponding to the RUU version I was about to upload.
I have seen some instructions which say you have to re-lock the phone first but I don't think this is the case (I don't want to do this unless I have to as it is a pain to unlock again).
i.e. fastboot oem lock
Been experimenting with the phone and it turns out the other person can hear me but I can't hear them, but if I switch it to speaker phone then I can hear them but they can't hear me - lol
I guess this proves it is software related though.
--------------
Latest news: I have downloaded TWRP backups instead of using the RUU, this seems to be installing and I will let you know how it goes........
alanes said:
Gave it a try this morning but same error message as before
Just in case I am doing something wrong, what I do is:
First wipe all the partitions using TWRP (apart from sd card) then use htc-fastboot to try and send the RUU zip file
I have not removed TWRP although I did once try first uploading the HTC recovery file corresponding to the RUU version I was about to upload.
I have seen some instructions which say you have to re-lock the phone first but I don't think this is the case (I don't want to do this unless I have to as it is a pain to unlock again).
i.e. fastboot oem lock
Click to expand...
Click to collapse
Strange, I don't know what you are getting header error. Really, from what I can tell, either RUUs you tried should work.
No need to wipe anything in TWRP, nor install stock recovery, in order to RUU. But doing those things won't hurt anything, either (such as the header error).
Also, no need to relock the bootloader since you are s-off. Again, unless the dual SIM M8 has some difference from the "regular" single SIM M8. At least on the single SIM, I'm absolutely positive the RUU will flash with either bootloader locked/relocked or unlocked, as long as you are s-off.
Hi,
I spent much of today on it and managed using TWRP to install the stock HTC rom (6.16.401.101) and do the updates but still the same so tried 4.30.401.15 but still no joy.
Guess my only hope now is to try replacing the earpiece speaker but I still think it is software rather than hardware related.
I finally decided it is not a hardware problem so will consign this phone to the trash and I will give a Willeyfox phone a try, see if this works out any better (can't be much worse - lol)
Hi,
I read a couple of other threads with similar symptoms but I do not know if I have the same problem. So I think it's better to start a new thread. In any case I hope some expert here can help me.
About 1,5 years ago I bought a secondhand HTC One M8 and it has been working fine up to last Tuesday. I use it to hike (to follow downloaded tracks and record my hike, using GPS, and when I do this I put it into flight mode to not use any more battery than necessary). I keep it in a pocket in my shorts when I hike. Last Tuesday, I was simply walking (not climbing, running or anything of that kind) and it had just started raining, but my phone was in my dry pocket, when I felt it vibrated. It had powered off by itself. I powered it on again, tried to reactivate my hiking application (Alpine Quest) but it didn't register my location nor track my moves. I didn't have any connection and it was stuck in flight mode.
At home, powering off and on, it all of a sudden asked me for a PIN code (I've never secured my phone with a code, and I've never seen this screen before) and it only lets me make emergency calls. I tried 0000 but that didn't work (using 1 of the 3 PIN code attempts... I've 2 left now). Powering it off and on a couple of times, it sometimes gives this screen, but sometimes it also allows me to access my phone without the code (the normal home screen). In doing so I was able to get rid of the flight mode (when it is powered it freezes when powering on or off flight mode, which than becomes greyed out). Sometimes it powers on and off by itself. But I have no connection, no baseband, EMEI is unknown, phone number is unknown.
If any of you has any idea as to solve this porblem, I would appreciate the help !
Thanks !
Judith
Ps Oh and by the way, I'm quite illiterated when it comes to phones... I may understand computers but because with phones the software is hidden and can only be accessed when the phone is rooted (and I already "bricked" my previous unlocked Samsung by trying to root it when it had a problem) I cannot learn and I'm scared I may do something wrong this time too . I find it ridiculous that when you BUY a (unlocked) phone you cannot access the software installed on it (and get rid of xxxxx MB of bloatware that fills up the memory, to name one thing...).
Phone: HTC One M8
Android version: 6.0
HTC Sense: 7.0
Software number: 6.12.401.4
Kernel version: 3.4.0-perf-g708019f
[email protected] #1
SMP PREEMPT
Baseband version: unknown
IMEI: unknown
IMEI SV: unknown
Phone number: unknown
IMSI: unknown
Judiver said:
Ps Oh and by the way, I'm quite illiterated when it comes to phones... I may understand computers but because with phones the software is hidden and can only be accessed when the phone is rooted (and I already "bricked" my previous unlocked Samsung by trying to root it when it had a problem) I cannot learn and I'm scared I may do something wrong this time too
Click to expand...
Click to collapse
What do you mean "I cannot learn"? Anybody can learn! But it requires you to take the time and effort to learn the proper info and methods.
If you don't understand enough to root a phone, then you don't know enough to be messing with the phone's software. This is the main reason they don't let users easily access the operating system (more likely to cause damage then do good).
Judiver said:
Software number: 6.12.401.4
Click to expand...
Click to collapse
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number, if they appear).
It appears you obtained the info from the phone settings (within OS) which is not a reliable way of obtaining this data.
If you don't know how to do fastboot getvar, at least go to bootloader screen, and confirm OS number, and tell us whether baseband number is listed as well.
Hi Redpoint,
Thank you for your reaction. Sorry for my slow reaction. I've been doing some reading and also finding out how to make a back-up without a connection. I ended up downloading HTC Sync Manager, which didn't want to connect my phone at first, and sometimes still doesn't. I am apparently not the only one who has this problem with HTC Sync Manager but I noticed that since my phone disconnected last week, that when I plug it to my pc with a USB cable (not an original HTC as that was not delivered with my 2nd hand phone...) I get the message that the driver doesn't install. I now sometimes I can connect my phone and sometimes not. This must be related to the problem with the phone, as formerly this never happened, I could always connect my phone to my pc with USB and never got a message about drivers not correctly having been installed. Also my phone powers off and on by itself now.
Off course I can learn ! I wouldn't have asked for help here if I didn't want to learn ! What I meant is that, opposed to computers, a normal user with an unrooted phone (like me) doesn't see nor can he/she access any software on a phone. When I had a problem with my previous phone (a Samsung), I asked for help on this forum but I didn't get any reaction. So I tried to figure things out myself and downloaded a file from the internet to (easily) root the phone. But the program appeared to be crap, it bricked my phone (I think my EMEI was stolen ?). That wouldn't happen on a pc, which is much more fool proof : you can see your system files, run malware and other scans, lots of security facilities are built in, lots ways to get back to a previous state from before messing up, etc. Everything I learnt about computers is done by reading & trying and I am much less afraid of doing something wrong because it is like walking in a city where I've been wandering around many times, seeing things that are either familiar or weird. With the experience of my Samsung in mind, I am afraid of doing something wrong with my HTC now, and especially afraid of downloading from websites that have not been recommended by a trustworthy source. That's all.
I just installed the Minimal ADB and Fastboot (https://forum.xda-developers.com/showthread.php?p=42407269#post42407269) and got this result :
(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.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: *****
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
I bought it from Second-hand Phones in the UK in April last year.
Thanks for your help. I appreciate it.
Judith
Ps learned something already
Oh I forgot,
It says
***Software status: Official***
Judiver said:
When I had a problem with my previous phone (a Samsung), I asked for help on this forum but I didn't get any reaction. So I tried to figure things out myself and downloaded a file from the internet to (easily) root the phone. But the program appeared to be crap, it bricked my phone (I think my EMEI was stolen ?).
Click to expand...
Click to collapse
I don't know what Samsung phone (your info is too vague, maybe intentionally so) but there is plenty of info on XDA on how to root all the common Samsung phones. You may have been asking for an old device, where the forum is not very active anymore (the M8 forum itself is pretty quiet, only a few of us "helpers" left anymore. Or maybe asking a question that has already been answered too many times ("how to root" is one of those).
If you downloaded a random root program from websites outside XDA, that is a mistake. My advice would be to stick to XDA, and advice/files from reputable XDA members, and you won't go wrong.
---------- Post added at 09:41 AM ---------- Previous post was at 09:38 AM ----------
Judiver said:
Off course I can learn ! I wouldn't have asked for help here if I didn't want to learn ! What I meant is that, opposed to computers, a normal user with an unrooted phone (like me) doesn't see nor can he/she access any software on a phone.
Click to expand...
Click to collapse
This is a false statement. Linux systems are both computers and PCs. And Linux has root privileges just like Android.
If you are talking Windows specifically, I can tell you having tinkered with both Windows PCs and Android Phones, that phones are far easier to manipulate and restore, than PCs. You just know your way around PCs, than phones.
There are plenty of ways to restore an Android device. You just haven't learned them yet.
---------- Post added at 09:53 AM ---------- Previous post was at 09:41 AM ----------
Judiver said:
I've been searching for fastboot getvar all, but it looks like I need to download a program for that (?) and, as I said, I am a bit afraid of downloading from the wrong websites.
Click to expand...
Click to collapse
By installing HTC Sync, you already have fastboot installed. There are also fastboot/adb installers available on XDA (reputable and used by many) if you use the XDA search function and search "easy fastboot install" or similar search phrase. Also "fastboot guide" will help you find threads on the basics.
Fastboot is mandatory not just for the info I asked for, but also the recovery option I will suggest. So you need to learn how to use fastboot, at least on a basic level. Fastboot is handled through PC's command prompt interface. So if you are experienced with PCs, it really shouldn't be a problem for you to learn.
And when I say "recovery option I will suggest" keep in mind, it is just a clean install of the stock software/firmware. It sounds like your issue may or may not be a hardware failure. But in the even it is, my forthcoming suggestion won't fix your issue. But it's worth trying, to at least see if the problem is in the software/firmware.
redpoint73 said:
I don't know what Samsung phone (your info is too vague, maybe intentionally so) but there is plenty of info on XDA on how to root all the common Samsung phones. You may have been asking for an old device
Click to expand...
Click to collapse
It was indeed a bit of an old device. I didn't mention the model because it isn't relevant for this thread, but it was Samsung Galaxy i9003 S SCL, bought in 2012 (in Spain). It got a problem last year, but, if I remember well, as the software was outdated (and apparently not updated to anything newer?) I wanted to root it to be able to put something more recent on it (hoping to fix the problem at the same time).
redpoint73 said:
If you downloaded a random root program from websites outside XDA, that is a mistake. My advice would be to stick to XDA, and advice/files from reputable XDA members, and you won't go wrong.
Click to expand...
Click to collapse
I fully agree! It was a stupid action and I should have known better. I have enough experience with pc's to know the risks of downloading executable files from shady sources...
redpoint73 said:
You just know your way around PCs, than phones.
Click to expand...
Click to collapse
Well, I'm no expert in pc's but I try and learn, and stuff becomes easier on the go. But I am a blank page when it comes to mobiles phones !
redpoint73 said:
By installing HTC Sync, you already have fastboot installed. There are also fastboot/adb installers available on XDA (reputable and used by many) if you use the XDA search function and search "easy fastboot install" or similar search phrase. Also "fastboot guide" will help you find threads on the basics.
Fastboot is mandatory not just for the info I asked for, but also the recovery option I will suggest. So you need to learn how to use fastboot, at least on a basic level. Fastboot is handled through PC's command prompt interface. So if you are experienced with PCs, it really shouldn't be a problem for you to learn.
And when I say "recovery option I will suggest" keep in mind, it is just a clean install of the stock software/firmware. It sounds like your issue may or may not be a hardware failure. But in the even it is, my forthcoming suggestion won't fix your issue. But it's worth trying, to at least see if the problem is in the software/firmware.
Click to expand...
Click to collapse
I am glad that you think it's a software issue. So now that I have HTC Sync and the Minimal ADB and Fastboot, is that sufficient for what you (I hope) suggest I do next or do I need the full ADB?
Judiver said:
I am glad that you think it's a software issue. So now that I have HTC Sync and the Minimal ADB and Fastboot, is that sufficient for what you (I hope) suggest I do next or do I need the full ADB?
Click to expand...
Click to collapse
I never said I thought it was a software issue. I said it may or may not be a hardware issue. It's worth a try (and probably won't hurt) restoring the full stock software image (RUU). Sometimes this fixes the problem with no connection, sometimes not (such as with a hardware issue).
Just about any fastboot installation will do. In fact, you will need to download the htc_fastboot to flash the RUU file in the following post:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note that you do not need to lock the bootloader (first 2 bold type lines in the above guide) since your bootloader is still locked.
Also note that the RUU will wipe all data from the phone. So backup/move anything you want to keep from the phone (photos, personal data, etc.).
redpoint73 said:
I never said I thought it was a software issue. I said it may or may not be a hardware issue. It's worth a try (and probably won't hurt) restoring the full stock software image (RUU). Sometimes this fixes the problem with no connection, sometimes not (such as with a hardware issue).
Just about any fastboot installation will do. In fact, you will need to download the htc_fastboot to flash the RUU file in the following post:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Note that you do not need to lock the bootloader (first 2 bold type lines in the above guide) since your bootloader is still locked.
Also note that the RUU will wipe all data from the phone. So backup/move anything you want to keep from the phone (photos, personal data, etc.).
Click to expand...
Click to collapse
I'm sorry, I was reading fast and apparently did some 'wishful reading' concerning the software/hardware issue.
In bootloader mode there are a couple of options, like Recovery mode and Factory reset. Couldn't I try this first before loading on a new RUU?
Judiver said:
In bootloader mode there are a couple of options, like Recovery mode and Factory reset. Couldn't I try this first before loading on a new RUU?
Click to expand...
Click to collapse
Those options won't do anything. If they had any possibility to help, I would have mentioned those options. The stock recovery is pretty useless. It will give you options to factory reset (see more info on that, next paragraph), and wipe cache. You can try to wipe cache if you like (won't harm anything) but it won't help your issue, I can guarantee.
In regards to factory reset, many folks have a misunderstanding of what that means. The term "factory reset is somewhat of a misnomer. It won't magically restore the OS. The only way to do that, is to re-install the OS from somewhere, like an RUU. The only thing the factory reset option in bootloader/stock recovery does, is wipe user data.
redpoint73 said:
Those options won't do anything. If they had any possibility to help, I would have mentioned those options. The stock recovery is pretty useless. It will give you options to factory reset (see more info on that, next paragraph), and wipe cache. You can try to wipe cache if you like (won't harm anything) but it won't help your issue, I can guarantee.
In regards to factory reset, many folks have a misunderstanding of what that means. The term "factory reset is somewhat of a misnomer. It won't magically restore the OS. The only way to do that, is to re-install the OS from somewhere, like an RUU. The only thing the factory reset option in bootloader/stock recovery does, is wipe user data.
Click to expand...
Click to collapse
Hi Redpoint,
I downloaded the htc_fastboot.exe and the RUU, but couldn't find a download for the 1.4.3 version of the ADB Installer last night. So today, still no luck, I tried 1.3 and followed the instructions on the links you gave me. At first I thought it hadn't changed anything as it was asking for a PIN again and when connecting to my pc with a USB cable the drivers didn't install correctly (i.e. same 2 symptoms that had occurred when I found myself without a connection). But this time the standard 0000 of my operator worked for the sim card PIN and it appeared I had a connection! But it wouldn't call. After re-installing my wifi connection I started updating all of the software. That took a while. And then restore from HTC Sync Manager back-up and getting all my apps and settings back that the back-up hadn't adressed (the HTC back-up was not very exhaustive... no ringtones, no Whatsapp history...).
During all the updates the first sms I received was spam and this telephone, for some reason, can blacklist calls but not sms. Lots of bloat ware you cannot get rid of but no sms blocker! And I forgot which sms blocker app (free, no ads) I had downloaded previously. Hmmm... I'll keep looking for something suitable...
But that aside, all seems to work as it should now (fingers crossed) !
So thanks a lot for your help. It helped me greatly :good::good:.
And I learned, although I still think it is a bit of a drastic procedure to do every time a phone has a problem. You have no idea what the problem is, severe or minor, and have no clue where to look! If every time I have a problem with my pc I need to re-install Windows, I wouldn't be doing much other than just that! Mobile phones (at least as far as I know) seem to lack a system where you can do a scan and repair system files, or a way to find out where the problem is and replace just a part (leaving your stuff in tact). All I read everywhere on android websites is about flashing and rooting, hardly ever less drastic solutions... But then... that's the opinion of someone you just made her first steps in the Android world ...
Judiver said:
I downloaded the htc_fastboot.exe and the RUU, but couldn't find a download for the 1.4.3 version of the ADB Installer last night.
Click to expand...
Click to collapse
You already has adb installed when you installed HTCSync. And again when you used the minimal fastboot/adb installer. I mentioned as much earlier. Any of these would work. Not sure why you tried installing adb yet again (3rd separate installation).
In any case, it sounds like you sorted it out, so glad the RUU helped.
Judiver said:
And I learned, although I still think it is a bit of a drastic procedure to do every time a phone has a problem.
Click to expand...
Click to collapse
What you experienced was probably a pretty serious issue, and not that common. I used the M8 as my daily driver for over 3 years, and never had to use the RUU to recover from such an issue.
redpoint73 said:
You already has adb installed when you installed HTCSync. And again when you used the minimal fastboot/adb installer. I mentioned as much earlier. Any of these would work. Not sure why you tried installing adb yet again (3rd separate installation).
I wasn't sure whether the minimal fastboot / HTC Sync was enough to install a RUU.
redpoint73 said:
What you experienced was probably a pretty serious issue, and not that common. I used the M8 as my daily driver for over 3 years, and never had to use the RUU to recover from such an issue.
Click to expand...
Click to collapse
We will never know what the problem was, but I'm very happy it is gone Thanks for helping me out Redpoint.
Click to expand...
Click to collapse