Hey guys, I was hoping somebody could help me out with this. I can't seem to get my identifier token from the One. I've tried in Windows and Ubuntu. In windows, adb and foastboot wouldn't even recognize the phone whether in the fastboot mode or debug while booted normally. In Ubuntu, fastboot devices shows the device, but when I run fastboot oem get-identifier-token all I get is:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
Is there anything I can do?
Edit: I should add, that I wasn't even getting Ubuntu to recognize the device until I added the 99-Android.rules file in udev. I am running Ubuntu 12.10.
Edit 2: Got fed up and switched back to Windows. fastboot devices now shows the phone, but I am getting the same error as above now. This is soooo frustrating. Why does is work so easily for everyone else?
In case it helps, this is what my bootloader screen reads:
*** LOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 18 2013, 18:29:18:-1
Click to expand...
Click to collapse
And when I am trying to run the get-identifier-token command, there is a red box that says "FASTBOOT USB" inside it.
OK, I've officially been crowned dumb-**** of the new millenium. I started thinking to myself, "There is no way that this should be causing so much trouble for you if everyone else is getting it so easily. You must be making a really simple mistake."
Well, I found my assinine error. I was using hyphens instead of underscores in the get_identifier_token command. I could have just deleted this thread, but I'm going to give everyone the chance to laugh at my idiocy and the fact that I spent 3 hours trying to figure this **** out.
Copy and paste is your friend.
Sent from my HTC One using xda app-developers app
That's okay. I spent half an hour making the token paste properly into the box on htcdev
So, my root/unlocked 4.4.2 Droid DNA (dlx HTC6435lvw w/ Viper DNA & iHateSense Kernel) is questionably out of the game. I have been staring at a combination of this laptop, my phone, and my Ubuntu desktop for about 80 or so hours, with little sleep. Anyways I was at a friend's place and the DNA sorta, died, I guess (and not the typical way). I hit the unlock button and I saw the backlight come on and then there was absolutely no display. The phone eventually died (I think) then it was left dead for a little while and then I managed to get my hands on a charger, and then when I plugged my beloved in I didn't see the orange light blinking. Long story short, I took it home, got the light to come back on after a boot into the bootloader (and oh, by the way, I can't see that either, or the RUU interface after the rebootRUU command) and the phone has been absolutely amazing before that. I've tried everything... It gets screenshots (idk how relevant that is, because I'm sure it's software related) but they are at a screen that says "Receiving information from Verizon please wait until this proccess is complete. Still boots up to stock the recent RUU zip flash from fastboot (the 3.06 version) and it's still K.I.A.
hammer280 said:
So, my root/unlocked 4.4.2 Droid DNA (dlx HTC6435lvw w/ Viper DNA & iHateSense Kernel) is questionably out of the game. I have been staring at a combination of this laptop, my phone, and my Ubuntu desktop for about 80 or so hours, with little sleep. Anyways I was at a friend's place and the DNA sorta, died, I guess (and not the typical way). I hit the unlock button and I saw the backlight come on and then there was absolutely no display. The phone eventually died (I think) then it was left dead for a little while and then I managed to get my hands on a charger, and then when I plugged my beloved in I didn't see the orange light blinking. Long story short, I took it home, got the light to come back on after a boot into the bootloader (and oh, by the way, I can't see that either, or the RUU interface after the rebootRUU command) and the phone has been absolutely amazing before that. I've tried everything... It gets screenshots (idk how relevant that is, because I'm sure it's software related) but they are at a screen that says "Receiving information from Verizon please wait until this proccess is complete. Still boots up to stock the recent RUU zip flash from fastboot (the 3.06 version) and it's still K.I.A.
Click to expand...
Click to collapse
Do you think you can blindly get it into fastboot mode? I just posted some ruu exes in the general section
dottat said:
Do you think you can blindly get it into fastboot mode? I just posted some ruu exes in the general section
Click to expand...
Click to collapse
Oh, yea I've been able to get into it every time, luckily I found a picture of it through good ole' google haha.
hammer280 said:
Oh, yea I've been able to get into it every time, luckily I found a picture of it through good ole' google haha.
Click to expand...
Click to collapse
Well...you can try running an exe ruu if the phone is detected in fastboot. Just in the oddball chance it's software related. Fyi...my two ruus will not wipe data
Alright downloading the RUU for .1 now along with hboot
Just completed the download, going to flash now with crossed fingers, lol. :fingers-crossed:
no good shes done. god so disappointing. too bad my friends razr he sent me constantly reboots. like a consistent delayed reboot. doesnt do it in it's fastboot mode though so maybe there's hope with that old brick. thanks anyway ;(
hammer280 said:
no good shes done. god so disappointing. too bad my friends razr he sent me constantly reboots. like a consistent delayed reboot. doesnt do it in it's fastboot mode though so maybe there's hope with that old brick. thanks anyway ;(
Click to expand...
Click to collapse
Did it actually flash?
dottat said:
Did it actually flash?
Click to expand...
Click to collapse
Oh yea, it flashed perfectly. Quick and no errors. Phone booted up and everything, already have a new one one the way. Should be here within the next 24 hrs thanks to insurance, lol. Thanks for all your support, now to make/find a thread related to this razr reboot problem.
I have the same problem but ruu.exe doesnt see phone. and fastboot says
Blazes-MacBook-Pro:~ blaze$ fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3760mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
Click to expand...
Click to collapse
display is black. Thats after change of partitions mmcblk0p4 mmcblk0p5
Hi all,
I am newbie and no developer. I have just severe trouble with my beloved phone.
About 1 month ago it started that way, that the mobile data and cell connection was sometimes there and sometimes not.
One day later it was 95% not able to do calls. Sometimes after rebooting it worked again.
The OS at that time was 4.2.2, stock version.
I found that I have that stuck in airplane mode error. The device says that it is momentarily in shutting off airplane mode, but never gets out ouf that state. Symptoms are also no IMEI in OS available and SIM access seems not to be there
I thought about GSM antenna probs and found some damaged spring contacts and changed that pcb. Also renewed the coax connection cable
from MoBo to GSM antenna pcb. But this didn´t help at all.
After that I worked on changing to Cyanogenmod, as a remedy : post-build=htc_europe/enrc2b/enrc2b:4.3/JRO03C/125529.22:user/release-keys
post-timestamp=1385502720 pre-device=enrc2b
I unlocked it. Put TWRP on it and did S-OFF. Then I flashed the boot.img and then I flashed the ROM and erased cache. Most of the work by direct adb commands, since the toolkit made more problems than solutions.
The result is as that of many other users, the problem is still there. Did also try with emergency calls, it says there is no network in my area.
But with CM it works faster and makes really fun. If only that GSM functionality was there. Wifi and bluetooth and that other crap all works.
After reboot it usually says, that flightmode is on at the moment.
and C:\android>fastboot getvar all says:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 3.1204.171.33
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.3
(bootloader) serialno: FA2ATW104894
(bootloader) imei: 35356--------------
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: low
(bootloader) battery-voltage: 3356mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.438s
so the IMEI is available but not to the OS
It can be, that I did not perfect at flashing boot.img and ROM and doing S-OFF a.s.o. in the best order.
Are there any ideas, how to find out more?
Can catlog help in any way? What other debugging options could help?
Is the missing SIM access a possible root cause, or is it consequence of something else like damaged radio or .... ?
Are there tools, to kick the airplane mode completely off or would this just be a stupid idea?
Could older radio versions help?
Initially, the problem came not through fumbling with ROMs a.s.o. What was the cause at that time?
I read really a lot of topics from very different forums (US and Europe). But it seems still that a few people find solutions (the solutions are different and don´t point to the root cause imho) and a lot of people don´t find a solution.
I would be really happy if there were some answers or ideas.
Best Regards,
ICE
In the next step I will try some radios.
But all of the Links to the zips on dropbox are dead.
Does somebody know where I can get this and maybe also other radio versions: Endeavoru_Radio_2.1204.135.20_CM10
Best Regards, ICE
ICEMAN_77 said:
Hi all,
I am newbie and no developer. I have just severe trouble with my beloved phone.
About 1 month ago it started that way, that the mobile data and cell connection was sometimes there and sometimes not.
One day later it was 95% not able to do calls. Sometimes after rebooting it worked again.
The OS at that time was 4.2.2, stock version.
I found that I have that stuck in airplane mode error. The device says that it is momentarily in shutting off airplane mode, but never gets out ouf that state. Symptoms are also no IMEI in OS available and SIM access seems not to be there
I thought about GSM antenna probs and found some damaged spring contacts and changed that pcb. Also renewed the coax connection cable
from MoBo to GSM antenna pcb. But this didn´t help at all.
After that I worked on changing to Cyanogenmod, as a remedy : post-build=htc_europe/enrc2b/enrc2b:4.3/JRO03C/125529.22:user/release-keys
post-timestamp=1385502720 pre-device=enrc2b
I unlocked it. Put TWRP on it and did S-OFF. Then I flashed the boot.img and then I flashed the ROM and erased cache. Most of the work by direct adb commands, since the toolkit made more problems than solutions.
The result is as that of many other users, the problem is still there. Did also try with emergency calls, it says there is no network in my area.
But with CM it works faster and makes really fun. If only that GSM functionality was there. Wifi and bluetooth and that other crap all works.
After reboot it usually says, that flightmode is on at the moment.
and C:\android>fastboot getvar all says:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 3.1204.171.33
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.3
(bootloader) serialno: FA2ATW104894
(bootloader) imei: 35356--------------
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: low
(bootloader) battery-voltage: 3356mV
(bootloader) devpower: 0
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.438s
so the IMEI is available but not to the OS
It can be, that I did not perfect at flashing boot.img and ROM and doing S-OFF a.s.o. in the best order.
Are there any ideas, how to find out more?
Can catlog help in any way? What other debugging options could help?
Is the missing SIM access a possible root cause, or is it consequence of something else like damaged radio or .... ?
Are there tools, to kick the airplane mode completely off or would this just be a stupid idea?
Could older radio versions help?
Initially, the problem came not through fumbling with ROMs a.s.o. What was the cause at that time?
I read really a lot of topics from very different forums (US and Europe). But it seems still that a few people find solutions (the solutions are different and don´t point to the root cause imho) and a lot of people don´t find a solution.
I would be really happy if there were some answers or ideas.
Best Regards,
ICE
Click to expand...
Click to collapse
hi, my hox+ had the same problem of being stuck in airplane mode.
I solved it by flashing cm11 nightly.
Can u plz tell me how did u s-off your device?! i have been searching like hell for quite some time but in vain.
HTC gives on their webpage the opportunity to send your phone data and they send you a File to Do it. They Have a good explanation of how to do this
Ice
ICEMAN_77 said:
HTC gives on their webpage the opportunity to send your phone data and they send you a File to Do it. They Have a good explanation of how to do this
Ice
Click to expand...
Click to collapse
Hi.
I would flash the boot img after the rom flash. Ensure you are flashing the correct boot.img for your rom version. Should help your no network issue.
Also you are Not s-off.
You are htc-dev unlocked. You can tell this easily as your fastboot command output states your security is on. S-off is not available for this device through software to my knowledge.
If this does not help i would try using an ruu to reflash your devices stock software one last time.
Sent from my LG-D802 using Tapatalk
I have an HTC One M8 on AT&T, and I have twrp installed. It is on KitKat, and twrp will not let me update to Lollipop. I am quite new to Android, and I do not know how to remove twrp, and go back to sense to install the new lollipop update. If you can help, please tell me how to do everything like I am a 6 year old child. I do not even know how to flash a rom. I have searched google as best I can, but I cannot find anything. Thanks for the help!
CyanClay said:
I have an HTC One M8 on AT&T, and I have twrp installed. It is on KitKat, and twrp will not let me update to Lollipop. I am quite new to Android, and I do not know how to remove twrp, and go back to sense to install the new lollipop update. If you can help, please tell me how to do everything like I am a 6 year old child. I do not even know how to flash a rom. I have searched google as best I can, but I cannot find anything. Thanks for the help!
Click to expand...
Click to collapse
To install an OTA update, you need to have the stock ROM and stock recovery installed.
As long as you don't mind having your data wiped and setting up the phone again, it may be less complicated for you to just run the RUU. The RUU is an Windows executable that will update your phone to current OS software. In general, the process would be:
1) Backup your personal data using the method of your choice: to the cloud, PC, etc.
2) Download the Lollipop RUU to PC from the bottom of the webpage: http://www.htc.com/us/support/htc-one-m8-att/news/
3) Connect phone to PC.
4) Relock the bootloader with fastboot command: fastboot oem lock
(this is not required if you are s-off)
5) Run the RUU program on the computer. The RUU is very self explanatory, and will tell you what to do from there. Basically, you just follow the prompts and the RUU will install the update, reboot the phone a couple times, etc.
6) Drink a beer, since you are finished updating the phone.
OPTIONAL:
If you want to root, etc.:
7) Unlock the bootloader again by HTCDev.com
8) Install TWRP with fastboot
9) Flash SuperSU 2.46 to root; or root by other method of choice.
OTA update problem
Thanks redpoint73. As I had the same problem regarding the OTA update, I've tried to do exactly what you and the HTC dev team said, but I got the error 155 (as I was using the wrong ruu). At this point HTC dev cannot help me any longer, so I was wondering if you can. Here's the history of my communication with them:
Bautista (North America Support (HTCDev.com Others)) Please allow me to introduce myself, my name is Luis and I'm with the HTC Special Projects Tier 3 department. I am reaching out to you currently in regards to SPT3 Case S2016001453301 . This case was a result of a ticket you recently had escalated to our department regarding the development trouble you were experiencing on your HTC Device. I would be more than happy to assist you with this. Before we begin, I will need to capture the following information from you in order to be able to provide the most efficient and effective support. *First 6 lines of text on the HBoot screen *Developer and software version of any 3rd party OS flashed to the device *Developer and software version of any 3rd party recovery flashed to the device *Output of 'fastboot getvar all' *Any error messages you have received Once I have the data specified above, I will be able to begin working on a resolution for your issue. Please click the second link below to reply. Until then, best wishes. 2016/03/30 00:39:16
Rodrigo Moreira Dear Luis, thanks for your reply. Well, the HBoot Screen shows: *** Software status: Modified *** *** UNLOCKED *** M8_UL_CA PVT SHIP S-ON HBOOT-3.19.00000 RADIO-1.24.21331147A1.09G OpenDVP-v48.2.2-0564-M8974_FO.1211 OS-4.16.1540.8 eMMC-boot 2048MB Jan 6 2015,00:38:22.0 I bought this phone with the TWRP installed. But apparently this software was preventing the device to be updated. I don't know the version of TWRP but I tried to remove it following, but It didn't work (At that time I probably didn't use the correct RUU). Now when I try to get the system update, as soon as the download is complete and the device restarts, it shows an error screen (attached). Then I have to restart the phone in order to use it normally. Well, that's it, I just want to unroot my device. If you need any other inormation, please let me know. 2016/03/30 01:10:34 IMAG0394-672x372.jpg
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying with that information. Now I'll be happy to walk you through getting the 'fastboot getvar all' information. To make this much easier, please create a new folder on your desktop and name it 'Android'. All files that we download from here on out, will need to go into this folder. Please navigate your browser to htcdev.com. If you do not have a log in, you will need to create one. After logging in, click on 'Unlock Bootloader' and then select the 'Get Started' Button. Select 'All other supported models' in the drop down menu. Click 'Begin Unlock Bootloader'. Read the warranty implication pop ups and if you agree, go ahead and click through them. Now you should see 'Unlock bootloader instructions'. This is the ONLY page we will need right now. At the bottom of the page, you will see fastboot files. Please select the one that matches your computer operating system (First one for Linux, second for MAC, third for Windows). Please ensure that these files are downloaded into the Android folder. You may already have the ADB files, so for now, we will stop downloading here. Minimize the browser window (don't close it), and open the Android folder you created. Take CTRL + Shift + Right Click (on your mouse) and select 'Open CMD Prompt Here'. Now on your phone, completely power the device off, Press and hold the volume down key. Without releasing the volume down key, tap the power button for 2 seconds. Your screen should light up with 3 Android characters. Release the volume down key. Use the volume keys to highlight 'Fastboot'. Once highlighted, tap the power button one time to select it. Your screen will now change. Connect the phone to your computer with the cable provided. Your phone's screen should now read 'fastboot usb'. If your phone does not read 'fastboot usb', stop here and let me know. If it does read properly, type the command 'fastboot devices' into your CMD prompt. You should see a serial number show on the screen. If it does not show, stop here and let me know. If it does show, next type 'fastboot getvar all'. I'll be waiting your reply. Thank you very much for your time. Have a wonderful day. Bye 2016/03/30 02:58:06
Rodrigo Moreira Hi Luis, when I typed 'fastboot devices' into the CMD prompt, an error message appeared (see attachment). What should I do now? Thanks 2016/03/30 06:41:13 Error.jpg
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo Thank you for replying, Let’s try the following: Download the HTC sync manager program from this link This will include the adb file you need. It is normally located in C: Program files>HTC>HTC Sync Manager>HTC sync Copy the AdbWinApi.dll file into the Android folder and try running the command once again. Let me know the results. Thank you very much for your time Sir. Have a wonderful day. Bye 2016/03/30 21:34:14
Rodrigo Moreira Hi Luis, now I got it. The number is: FA491WM02345. What's next? Tks 2016/03/30 23:09:10
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying. That's the serial number of the device. Next step will be to run the command fastboot getvar all. That result is the one that we are needing at this point. Double check the instructions and you will see Sir. Let me know if you want me to send you the instructions in Spanish. I'll be waiting your reply. Have a wonderful day and thank you very much for your time. Bye 2016/03/31 21:04:42
Rodrigo Moreira Good morning Luis. I'm sorry, I forgot to check the instructions. The results of the "fastboot getvar all" command were: C:\Users\Rodrigo\Desktop\Android>fastboot getvar all (bootloader) version: 0.5 (bootloader) version-bootloader: 3.19.0.0000 (bootloader) version-baseband: 1.24.21331147A1.09G (bootloader) version-cpld: None (bootloader) version-microp: None (bootloader) version-main: 4.16.1540.8 (bootloader) version-misc: PVT SHIP S-ON (bootloader) serialno: FA**********5 (bootloader) imei: 3*************1 (bootloader) imei2: Not Support (bootloader) meid: 00000000000000 (bootloader) product: m8_ul_ca (bootloader) platform: hTCBmsm8974 (bootloader) modelid: 0P6B12000 (bootloader) cidnum: BS_US001 (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.082s Tks, Rodrigo 2016/03/31 23:09:52
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying. Wonderful! I am going to review this information and formulate an action plan for you. Thank you very much for your time Sir. Wait for my next interaction. Have a nice day. Bye 2016/04/01 02:45:27
Rodrigo Moreira Hi Luis. I hope you didn't forget about my issue... Tks 2016/04/09 22:08:20
Bautista (North America Support (HTCDev.com Others)) Hello, Rodrigo! I hope you are going awesome! I am working on your case, please, allow me a couple of days. I will contact you back as soon as I have the complete information. Have an awesome day! Luis SPT3 2016/04/09 23:15:40
Rodrigo Moreira Hello Luis. Anything yet? Have a nice weekend. 2016/05/07 06:56:39
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Sorry for all the delay to get back to you Sir. I want you to try to install the RUU for your phone from. You should get the unlocked version for your phone (HTC one m8). with number 6.12.1540.4. First put your device in fastboot mode Remember to completely power the device off, Press and hold the volume down key. Without releasing the volume down key, tap the power button for 2 seconds. Your screen should light up with 3 Android characters. Release the volume down key. Use the volume keys to highlight 'Fastboot'. Once highlighted, tap the power button one time to select it. Your screen will now change to fastboot USB. Connect the phone to your computer with the cable provided. Your phone's screen should now read 'fastboot usb'. Now to put ready the device to take the RUU and start installation you can open a command window in the file that we created and type the following command fastboot oem rebootRUU. Then run the RUU. Please try it and let me know the results. I'll be waiting your reply. Have an amazing sunday and again sorry for all the delay Sir. Bye 2016/05/09 01:34:22
Rodrigo Moreira Hi Luis. Find attached the error message I got when I was trying to update the system. Thanks 2016/05/09 02:47:15 Error155.jpg
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying. I would like to mention that HTC does not support modified software on the phones. And at this point TWRP is not allowing to install the official RUU. Our dev scope will not allow us to walk you through the process. In a typical scenario, you get your phone back into safe conditions (in that case you must install the Android recovery tool once again). Then we go ahead with the process, it is for security reasons and not bricking your phone. All the process must be done from customer’s side. Having said that, I'll be happy to take a look at what's going on and at least point you in the right direction. Currently, you will need to explore third party development support web sites to find a more direct answer to your question. I would recommend starting your research at the following web sites: • XDA-Developers.com • AndroidCentral.com • Developer.android.com I know this limitation in the assistance may cause some delays in the completion of the resolution you desire, and for that we apologize. However I want you to try the following. Put your device in fastboot mode and showing fastboot USB. Then open a command window on the same file that we created previously and type the following command: fastboot oem lock . That will relock the bootloader. Then try to install the RUU again. Please let me know the results. I'll be expecting your next interaction. Thank you very much for your time and for being part of the HTC family. Have a wonderful day Sir. Bye 2016/05/09 22:24:04
Do you think you can help me?
Thanks in advance.
RodrigoMM said:
Thanks redpoint73. As I had the same problem regarding the OTA update, I've tried to do exactly what you and the HTC dev team said, but I got the error 155 (as I was using the wrong ruu). At this point HTC dev cannot help me any longer, so I was wondering if you can. Here's the history of my communication with them:
Bautista (North America Support (HTCDev.com Others)) Please allow me to introduce myself, my name is Luis and I'm with the HTC Special Projects Tier 3 department. I am reaching out to you currently in regards to SPT3 Case S2016001453301 . This case was a result of a ticket you recently had escalated to our department regarding the development trouble you were experiencing on your HTC Device. I would be more than happy to assist you with this. Before we begin, I will need to capture the following information from you in order to be able to provide the most efficient and effective support. *First 6 lines of text on the HBoot screen *Developer and software version of any 3rd party OS flashed to the device *Developer and software version of any 3rd party recovery flashed to the device *Output of 'fastboot getvar all' *Any error messages you have received Once I have the data specified above, I will be able to begin working on a resolution for your issue. Please click the second link below to reply. Until then, best wishes. 2016/03/30 00:39:16
Rodrigo Moreira Dear Luis, thanks for your reply. Well, the HBoot Screen shows: *** Software status: Modified *** *** UNLOCKED *** M8_UL_CA PVT SHIP S-ON HBOOT-3.19.00000 RADIO-1.24.21331147A1.09G OpenDVP-v48.2.2-0564-M8974_FO.1211 OS-4.16.1540.8 eMMC-boot 2048MB Jan 6 2015,00:38:22.0 I bought this phone with the TWRP installed. But apparently this software was preventing the device to be updated. I don't know the version of TWRP but I tried to remove it following, but It didn't work (At that time I probably didn't use the correct RUU). Now when I try to get the system update, as soon as the download is complete and the device restarts, it shows an error screen (attached). Then I have to restart the phone in order to use it normally. Well, that's it, I just want to unroot my device. If you need any other inormation, please let me know. 2016/03/30 01:10:34 IMAG0394-672x372.jpg
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying with that information. Now I'll be happy to walk you through getting the 'fastboot getvar all' information. To make this much easier, please create a new folder on your desktop and name it 'Android'. All files that we download from here on out, will need to go into this folder. Please navigate your browser to htcdev.com. If you do not have a log in, you will need to create one. After logging in, click on 'Unlock Bootloader' and then select the 'Get Started' Button. Select 'All other supported models' in the drop down menu. Click 'Begin Unlock Bootloader'. Read the warranty implication pop ups and if you agree, go ahead and click through them. Now you should see 'Unlock bootloader instructions'. This is the ONLY page we will need right now. At the bottom of the page, you will see fastboot files. Please select the one that matches your computer operating system (First one for Linux, second for MAC, third for Windows). Please ensure that these files are downloaded into the Android folder. You may already have the ADB files, so for now, we will stop downloading here. Minimize the browser window (don't close it), and open the Android folder you created. Take CTRL + Shift + Right Click (on your mouse) and select 'Open CMD Prompt Here'. Now on your phone, completely power the device off, Press and hold the volume down key. Without releasing the volume down key, tap the power button for 2 seconds. Your screen should light up with 3 Android characters. Release the volume down key. Use the volume keys to highlight 'Fastboot'. Once highlighted, tap the power button one time to select it. Your screen will now change. Connect the phone to your computer with the cable provided. Your phone's screen should now read 'fastboot usb'. If your phone does not read 'fastboot usb', stop here and let me know. If it does read properly, type the command 'fastboot devices' into your CMD prompt. You should see a serial number show on the screen. If it does not show, stop here and let me know. If it does show, next type 'fastboot getvar all'. I'll be waiting your reply. Thank you very much for your time. Have a wonderful day. Bye 2016/03/30 02:58:06
Rodrigo Moreira Hi Luis, when I typed 'fastboot devices' into the CMD prompt, an error message appeared (see attachment). What should I do now? Thanks 2016/03/30 06:41:13 Error.jpg
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo Thank you for replying, Let’s try the following: Download the HTC sync manager program from this link This will include the adb file you need. It is normally located in C: Program files>HTC>HTC Sync Manager>HTC sync Copy the AdbWinApi.dll file into the Android folder and try running the command once again. Let me know the results. Thank you very much for your time Sir. Have a wonderful day. Bye 2016/03/30 21:34:14
Rodrigo Moreira Hi Luis, now I got it. The number is: **snip**. What's next? Tks 2016/03/30 23:09:10
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying. That's the serial number of the device. Next step will be to run the command fastboot getvar all. That result is the one that we are needing at this point. Double check the instructions and you will see Sir. Let me know if you want me to send you the instructions in Spanish. I'll be waiting your reply. Have a wonderful day and thank you very much for your time. Bye 2016/03/31 21:04:42
Rodrigo Moreira Good morning Luis. I'm sorry, I forgot to check the instructions. The results of the "fastboot getvar all" command were: C:\Users\Rodrigo\Desktop\Android>fastboot getvar all (bootloader) version: 0.5 (bootloader) version-bootloader: 3.19.0.0000 (bootloader) version-baseband: 1.24.21331147A1.09G (bootloader) version-cpld: None (bootloader) version-microp: None (bootloader) version-main: 4.16.1540.8 (bootloader) version-misc: PVT SHIP S-ON (bootloader) serialno: **snip** (bootloader) imei: **snip** (bootloader) imei2: Not Support (bootloader) meid: 00000000000000 (bootloader) product: m8_ul_ca (bootloader) platform: hTCBmsm8974 (bootloader) modelid: 0P6B12000 (bootloader) cidnum: BS_US001 (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.082s Tks, Rodrigo 2016/03/31 23:09:52
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying. Wonderful! I am going to review this information and formulate an action plan for you. Thank you very much for your time Sir. Wait for my next interaction. Have a nice day. Bye 2016/04/01 02:45:27
Rodrigo Moreira Hi Luis. I hope you didn't forget about my issue... Tks 2016/04/09 22:08:20
Bautista (North America Support (HTCDev.com Others)) Hello, Rodrigo! I hope you are going awesome! I am working on your case, please, allow me a couple of days. I will contact you back as soon as I have the complete information. Have an awesome day! Luis SPT3 2016/04/09 23:15:40
Rodrigo Moreira Hello Luis. Anything yet? Have a nice weekend. 2016/05/07 06:56:39
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Sorry for all the delay to get back to you Sir. I want you to try to install the RUU for your phone from. You should get the unlocked version for your phone (HTC one m8). with number 6.12.1540.4. First put your device in fastboot mode Remember to completely power the device off, Press and hold the volume down key. Without releasing the volume down key, tap the power button for 2 seconds. Your screen should light up with 3 Android characters. Release the volume down key. Use the volume keys to highlight 'Fastboot'. Once highlighted, tap the power button one time to select it. Your screen will now change to fastboot USB. Connect the phone to your computer with the cable provided. Your phone's screen should now read 'fastboot usb'. Now to put ready the device to take the RUU and start installation you can open a command window in the file that we created and type the following command fastboot oem rebootRUU. Then run the RUU. Please try it and let me know the results. I'll be waiting your reply. Have an amazing sunday and again sorry for all the delay Sir. Bye 2016/05/09 01:34:22
Rodrigo Moreira Hi Luis. Find attached the error message I got when I was trying to update the system. Thanks 2016/05/09 02:47:15 Error155.jpg
Bautista (North America Support (HTCDev.com Others)) Hello Rodrigo. Thank you very much for replying. I would like to mention that HTC does not support modified software on the phones. And at this point TWRP is not allowing to install the official RUU. Our dev scope will not allow us to walk you through the process. In a typical scenario, you get your phone back into safe conditions (in that case you must install the Android recovery tool once again). Then we go ahead with the process, it is for security reasons and not bricking your phone. All the process must be done from customer’s side. Having said that, I'll be happy to take a look at what's going on and at least point you in the right direction. Currently, you will need to explore third party development support web sites to find a more direct answer to your question. I would recommend starting your research at the following web sites: • XDA-Developers.com • AndroidCentral.com • Developer.android.com I know this limitation in the assistance may cause some delays in the completion of the resolution you desire, and for that we apologize. However I want you to try the following. Put your device in fastboot mode and showing fastboot USB. Then open a command window on the same file that we created previously and type the following command: fastboot oem lock . That will relock the bootloader. Then try to install the RUU again. Please let me know the results. I'll be expecting your next interaction. Thank you very much for your time and for being part of the HTC family. Have a wonderful day Sir. Bye 2016/05/09 22:24:04
Do you think you can help me?
Thanks in advance.
Click to expand...
Click to collapse
Please edit your post like I did above to remove your imei/serial. Only you, your carrier and HTC should know these numbers. You cannot run an RUU while unlocked. run fastboot command "fastboot oem lock" to relock the bootloader for RUU. Only time you can run one when unlocked if you are s-off which your getvar data shows otherwise.
Uzephi said:
Please edit your post like I did above to remove your imei/serial. Only you, your carrier and HTC should know these numbers. You cannot run an RUU while unlocked. run fastboot command "fastboot oem lock" to relock the bootloader for RUU. Only time you can run one when unlocked if you are s-off which your getvar data shows otherwise.
Click to expand...
Click to collapse
Thanks for the heads up regarding the Serial/Imei number, Uzephi.
I've tried to lock the bootloader again as you said, but I get the same error message. Any other suggestion?
Thanks
RodrigoMM said:
Thanks for the heads up regarding the Serial/Imei number, Uzephi.
I've tried to lock the bootloader again as you said, but I get the same error message. Any other suggestion?
Thanks
Click to expand...
Click to collapse
Try redownloading the RUU or try another one from HTC's site that is the same version as in your getvar all.
Uzephi said:
Try redownloading the RUU or try another one from HTC's site that is the same version as in your getvar all.
Click to expand...
Click to collapse
Here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
Which one RUU should I try?
---------- Post added at 01:26 AM ---------- Previous post was at 01:07 AM ----------
RodrigoMM said:
Here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
Which one RUU should I try?
Click to expand...
Click to collapse
By the way, after I get the error message and disconect the USB cable, the phone shows a new message on the Hboot screen, which is: Loading zip info fail!
I don't know if that helps...
RodrigoMM said:
Here's my getvar:
.....
(bootloader) version-main: 4.16.1540.8
......
I don't know if that helps...
Click to expand...
Click to collapse
4.16.1540.8 ruu. Also, I just read the support ticket. Before you run the ruu, be sure to have HTC sync not running. I ran into ruu failures while that was up. It didn't give a 155 error, but did hang half way through. Crtl shift ESC all at once to load task manager and be sure any HTC process is killed.
Edit: try this ruu: http://www.htc.com/us/support/htc-one-m8/news/ download the "full update" at the bottom of page.
Sent from my HTC One using XDA-Developers mobile app
Uzephi said:
4.16.1540.8 ruu. Also, I just read the support ticket. Before you run the ruu, be sure to have HTC sync not running. I ran into ruu failures while that was up. It didn't give a 155 error, but did hang half way through. Crtl shift ESC all at once to load task manager and be sure any HTC process is killed.
Edit: try this ruu: http://www.htc.com/us/support/htc-one-m8/news/ download the "full update" at the bottom of page.
Sent from my HTC One using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, I've tried that, but still no luck. Any other idea?
RodrigoMM said:
Yeah, I've tried that, but still no luck. Any other idea?
Click to expand...
Click to collapse
What is the file names of the ruus you tried flashing?
Uzephi said:
What is the file names of the ruus you tried flashing?
Click to expand...
Click to collapse
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
RodrigoMM said:
RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4
Click to expand...
Click to collapse
This is the exe, not zip? What error you getting, still 155?
Uzephi said:
This is the exe, not zip? What error you getting, still 155?
Click to expand...
Click to collapse
The extension is exe, and the error I'm getting is still 155. Thanks
RodrigoMM said:
The extension is exe, and the error I'm getting is still 155. Thanks
Click to expand...
Click to collapse
Odd, Error 155 usually implies the bootloader is still unlocked. When you go into bootloader does it say ***RELOCKED***?
If it still says ***UNLOCKED*** go into fastboot USB mode again and from windows cmd prompts (the thing you did with support) type "fastboot oem lock" it should output showing it is sending the command to relock the bootloader.
Uzephi said:
Odd, Error 155 usually implies the bootloader is still unlocked. When you go into bootloader does it say ***RELOCKED***?
If it still says ***UNLOCKED*** go into fastboot USB mode again and from windows cmd prompts (the thing you did with support) type "fastboot oem lock" it should output showing it is sending the command to relock the bootloader.
Click to expand...
Click to collapse
Yes, it does say *** RELOCKED ***
---------- Post added at 08:04 PM ---------- Previous post was at 07:24 PM ----------
There's another information it may be relevant. I've tried to get the OTA update a couple months ago following this video youtube.com/watch?v=PPPT5J8xG6w, and It didn't work. At that time I wasn't sure if I was using the correct Stock Recovery version (I tried to use the "stock+recovery+1.12.1540.17+recovery.img"). Well, I don't know if that has any connection to the issue I'm having now.
RodrigoMM said:
Yes, it does say *** RELOCKED ***
---------- Post added at 08:04 PM ---------- Previous post was at 07:24 PM ----------
There's another information it may be relevant. I've tried to get the OTA update a couple months ago following this video youtube.com/watch?v=PPPT5J8xG6w, and It didn't work. At that time I wasn't sure if I was using the correct Stock Recovery version (I tried to use the "stock+recovery+1.12.1540.17+recovery.img"). Well, I don't know if that has any connection to the issue I'm having now.
Click to expand...
Click to collapse
Hm. Only other thing I can think of is you using a newer version of windows or a USB3 port. HTC ruus can be wonky on Windows 8 and up and need to be connected to a USB 2.x port, not a 3.0 port. Is the port you are plugging into blue or black? Do you know it is for sure a 2.x port?
As far as I know my laptop only has 2.0 USB. I'm using windows 10, by the way.
RodrigoMM said:
As far as I know my laptop only has 2.0 USB. I'm using windows 10, by the way.
Click to expand...
Click to collapse
Try it on windows 7 PC if you can find one available. If you cannot, flash the zip one using a bootable Linux distro CD or USB stick you can download. Windows 10 might be the outlying problem. I know for a long time windows 8.0 and 8.1 gave headaches to every HTC owner.
Let's try the usb stick, as I don't have access to any windows 7 pc... I'm sorry to ask you that, but can you tell me step by step what to do? I'm not an expert...
I installed the latest ruu with relocked bootloader and Windows 10. So first check your drivers if are ok. Run fastboot devices if the m8 is communicating with pc