Since there is no resource thread for this variant, I decided to create this one for the little community using this on XDA.
First of all, some warnings:
- Custom ROM and kernel do not work so do not attempt to try, it would just be a waste of time. Even if the ROM work, you will not have signal and there will be bug. So if you are not a ROM developer looking to support this variant, I suggest staying away.
- Debranding to unlocked/international variant is not possible. At best you will only soft brick, at worst you could brick your device.
- Since there are no RUU and none will be available in the near future, always have a stock back up at the ready.
- Root is only achievable with Sunshine through temproot and S-Off. So if you are not prepare to pay or for the risk, stay away as well.
Now, on to the main disk
Here is the link to the most recent OTA:
http://fotadl-az.htc.com/secure/OTA...1.28.970.6_release_485495lwhgdc5g85j4uwwh.zip
Contain in here is the stock recovery and other image if you need.
Guide to root. As mention above, will S-off your phone.
Guide to receive OTA after root.
can i get the radio.img for this device on au? im trying to get my US unlocked edition to work on au, i flashed verizon radios, and it does work, but i only get 3g data.
Quadrider10 said:
can i get the radio.img for this device on au? im trying to get my US unlocked edition to work on au, i flashed verizon radios, and it does work, but i only get 3g data.
Click to expand...
Click to collapse
Extract from firmware.zip and see. Report back.
The problem is I can't find and firmware for the Japan variet.
If the first post is the au OTA, it has radio.img
andybones said:
If the first post is the au OTA, it has radio.img
Click to expand...
Click to collapse
i tried it, but for some reason, it did not work...
I think it can be converted to Unlocked one after s-off, you may try
Quadrider10 said:
i tried it, but for some reason, it did not work...
Click to expand...
Click to collapse
What was the error?
No signal, or unable to get the radio.img from post1
No signal or data. For some of reason, the only radio that works is Verizon's. but I only get 3G data and it registers as no signal even though I have data, make calls and texts.
thanks so much, im from japan and my phone was root, im looking for this.
Can you upload the stock room off AU or stock back up here?
Quadrider10 said:
No signal or data. For some of reason, the only radio that works is Verizon's. but I only get 3G data and it registers as no signal even though I have data, make calls and texts.
Click to expand...
Click to collapse
Did you try wiping modems?
In download mode using ADB issue the commands:
Fastboot erase modemst1
Fastboot erase modemst2
Fixed my 3g issue. But this was from a Different issue.
Won't hurt to try..
Thanks. I'll give that a shot
those ADB command will not work. says failed partition erase not supported
EDIT: nvm i ran it in the bootloader and they seemed to work, however i am still not receiving signal on my 10 with us unlocked. it seems the only way to receive the KDDI au signal at all is to flash verizon's radio.
au has a funky system authenticating the phone with an ID system which is embedded within the stock ROM. I don't know whether it is possible to have signal with an unlocked model. That's the only thing keeping me from flashing a custom ROM on the phone. Maybe some ROM developer could take a look into that?
I did notice that if u flash the Verizon radio, then install a ROM while choosing unlocked dev edition, as the provider, you get signal and bars, but this breaks my 5ghz wifi capability for some reason and I only received 3g at speeds of 1.5mpbs download. So not really worth it. Is there an ruu for the Japanese HTV32 out there that would flash in my 10?
Quadrider10 said:
I did notice that if u flash the Verizon radio, then install a ROM while choosing unlocked dev edition, as the provider, you get signal and bars, but this breaks my 5ghz wifi capability for some reason and I only received 3g at speeds of 1.5mpbs download. So not really worth it. Is there an ruu for the Japanese HTV32 out there that would flash in my 10?
Click to expand...
Click to collapse
There are no RUU yet, have you tried flashing the radio from the OTA?
nerodarknight said:
There are no RUU yet, have you tried flashing the radio from the OTA?
Click to expand...
Click to collapse
yes, it didnt work... lol
Can some one upload a stock or stock backup for HTC 10 Japan please!
http://hanpenblog.com/4640/
Good news guys, I just found this website with links to download the RUU for the original firmware and all OTA up to date if anyone needs them.
nerodarknight said:
http://hanpenblog.com/4640/
Good news guys, I just found this website with links to download the RUU for the original firmware and all OTA up to date if anyone needs them.
Click to expand...
Click to collapse
Did you in japan and did you success with it?
Anyway, check your inbox. thanks !
Related
Is it possible to extract the radio image? I have converted my M8 to a GPe and when I did I remove the radio image from the RUU since it's a swedish phone with other LTE bands than the original GPe.
After a few days of testing it I seem to have problem connecting to LTE most of the times, but not always. I've read that people still can connect to LTE with the radio image from the GPe RUU and now I want to try that image instead. As a backup I want to be able to return to my stock radio again.
So, is this possible and how is it done? Or can I get the stock radio image in any other way?
djr83 said:
Is it possible to extract the radio image? I have converted my M8 to a GPe and when I did I remove the radio image from the RUU since it's a swedish phone with other LTE bands than the original GPe.
After a few days of testing it I seem to have problem connecting to LTE most of the times, but not always. I've read that people still can connect to LTE with the radio image from the GPe RUU and now I want to try that image instead. As a backup I want to be able to return to my stock radio again.
So, is this possible and how is it done? Or can I get the stock radio image in any other way?
Click to expand...
Click to collapse
Mind sound a little simplistic but couldn't you:
1) do a full backup
2) Download the GPE RUU
3) Extract the radio.img from it
4) Flash the radio.img "fastboot flash radio radio.img"
If it squirrels your reception up just do a restore from the backup?
grentuu said:
Mind sound a little simplistic but couldn't you:
1) do a full backup
2) Download the GPE RUU
3) Extract the radio.img from it
4) Flash the radio.img "fastboot flash radio radio.img"
If it squirrels your reception up just do a restore from the backup?
Click to expand...
Click to collapse
Hmm yeah, that could work. How do I do a complete backup? And how do I restore it if I need to?
djr83 said:
Hmm yeah, that could work. How do I do a complete backup? And how do I restore it if I need to?
Click to expand...
Click to collapse
I'm using philz recovery but twrp is similar. To back up press on back up and select location for back up.
Reboot when finished. I always store the backups on the laptop as a safety precaution.
To restore, just click on restore and go to backup location on phone to restore.
I prefer TWRP but it gave me issues with OS disappearing ! (possibly)
As far as I know, the gpe has the same version of radio as the sense one.
I have the sense version and I am having issues with LTE, I would root and flash the gpe radio if thats going to fix the problem
mm79k said:
As far as I know, the gpe has the same version of radio as the sense one.
I have the sense version and I am having issues with LTE, I would root and flash the gpe radio if thats going to fix the problem
Click to expand...
Click to collapse
+1
As you know I am using the Gpe RUU and love it.
Radio works great for 3G/4G. The issue is 4G coverage is crap both here and where I work I do get it on the drive home lol.
grentuu said:
+1
As you know I am using the Gpe RUU and love it.
Radio works great for 3G/4G. The issue is 4G coverage is crap both here and where I work I do get it on the drive home lol.
Click to expand...
Click to collapse
It is not about the coverage here. I live in Saudi Arabia and I used to have a very good, consistent LTE connection using the M7, LG G2, Lumia 1020, Xperia Z1 & Xperia SP. But not the M8. This device only connects to LTE when the signal is very strong. And I am not the only person here with this issue. I have seen many people complaining about the M8 ability to connect to LTE network.
I hope its a radio issue as I really like this phone and I don't want to replace it anytime soon
mm79k said:
As far as I know, the gpe has the same version of radio as the sense one.
I have the sense version and I am having issues with LTE, I would root and flash the gpe radio if thats going to fix the problem
Click to expand...
Click to collapse
But the GPe only exists in the US, so the frequencies are different in that and the European. Couldn't that be a problem if I flash GPe radio?
mm79k said:
It is not about the coverage here. I live in Saudi Arabia and I used to have a very good, consistent LTE connection using the M7, LG G2, Lumia 1020, Xperia Z1 & Xperia SP. But not the M8. This device only connects to LTE when the signal is very strong. And I am not the only person here with this issue. I have seen many people complaining about the M8 ability to connect to LTE network.
I hope its a radio issue as I really like this phone and I don't want to replace it anytime soon
Click to expand...
Click to collapse
Compared to the Nexus 5 my M8 seems to have worse coverage. But my problem is that it's not connecting data at all when trying LTE. If I limit it to 3G it seems to work all the time.
djr83 said:
But the GPe only exists in the US, so the frequencies are different in that and the European. Couldn't that be a problem if I flash GPe radio?
Click to expand...
Click to collapse
I'm in the UK and it works fine for me. When I am in a 4G area it locks on quickly.
grentuu said:
I'm in the UK and it works fine for me. When I am in a 4G area it locks on quickly.
Click to expand...
Click to collapse
And you use the GPe radio? What frequencies are your carrier on? 800 MHz and 2600 MHz?
djr83 said:
Is it possible to extract the radio image? I have converted my M8 to a GPe and when I did I remove the radio image from the RUU since it's a swedish phone with other LTE bands than the original GPe.
After a few days of testing it I seem to have problem connecting to LTE most of the times, but not always. I've read that people still can connect to LTE with the radio image from the GPe RUU and now I want to try that image instead. As a backup I want to be able to return to my stock radio again.
So, is this possible and how is it done? Or can I get the stock radio image in any other way?
Click to expand...
Click to collapse
To extract your radio image, do the following commands.
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p20 of=/sdcard/mmcblk0p20
exit
You'll find the radio image on the internal sd card.
djr83 said:
And you use the GPe radio? What frequencies are your carrier on? 800 MHz and 2600 MHz?
Click to expand...
Click to collapse
Yes re Gpe radio
Vodafone UK
800 (Band 20) & 2600 (Band 7) for 4G
djr83 said:
But the GPe only exists in the US, so the frequencies are different in that and the European. Couldn't that be a problem if I flash GPe radio?
Click to expand...
Click to collapse
I believe that LTE frequencies are hardware related, not software. Someone correct me if I'm wrong
Thanks, I'll try this later today.
mm79k said:
I believe that LTE frequencies are hardware related, not software. Someone correct me if I'm wrong
Click to expand...
Click to collapse
Yes they are, but couldn't it mean that it needs specifik software too?
guyd said:
To extract your radio image, do the following commands.
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p20 of=/sdcard/mmcblk0p20
exit
You'll find the radio image on the internal sd card.
Click to expand...
Click to collapse
So the file mmcblk0p20 is the radio image? It's 75 MB.
How do I flash the GPe radio? I tried fastboot flash radio radio.img but I get FAILED: remote not allowed.
IMO, you simply need to edit the ril settings in build.prop to match what was on your sense Rom and lte connectivity will be restored. These are the lines that need changed:
ro.ril.hsdpa.category=
ro.ril.hsupa.category=
ro.ril.hsxpa=
Gpe sets these pretty low for some reason..
Sent from my HTC One_M8 using XDA Premium 4 mobile app
HolyAngel said:
IMO, you simply need to edit the ril settings in build.prop to match what was on your sense Rom and lte connectivity will be restored. These are the lines that need changed:
ro.ril.hsdpa.category=
ro.ril.hsupa.category=
ro.ril.hsxpa=
Gpe sets these pretty low for some reason..
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do I know what was set there on Sense? And LTE works sometimes, just has a hard time connecting most of the times. But when it has connected it works great.
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Tritan84 said:
Hey everyone,
new here and to rooting/flashing in general.
I've somewhat successfully converted my verizon M8 to work on Tmobile by using weaksauce 2.0 to root, then Sunshine to gain S-off. Flashed TRWP custom recovery with flashify, backed up my stock vzw setup (4.4.4), then flashed ViperoneM8 with tmobile extras to the phone. The phone works great 90% of the time on Tmo, with 4gLTE, mms, sms, wifi all working. But I will get random dropped general mobile service (no data, can't make calls, text won't go through). This is easily fixed with airplane mode toggle.
Sooo, I wanted to see how other roms work on my phone with Tmobile service, specifically ARHD 34.0 and/or change phone to developer edition and upgrade to Lollipop. But both roms require prerequisite upgrading of firmware. My phone won't let me change the firmware via ADB or RUU. I've tried changing to superCID and going back to relocked mode, but still won't work. I get error 155 when attempting to upgrade via RUU and cannot find firmware.zip when using adv/fastboot.
I came across an old thread about other rooted models that suggest upgrading the HBOOT. Can anyone verify this suggestion and guide me toward which specific HBOOT software to change to?
Thanks for the help,
-Ant
Click to expand...
Click to collapse
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
xunholyx said:
If your stock was 4.4.4, your firmware and hboot should be fine to run ARHD. I don't think that WWE firmware (x.xx.401.x) is compatible with T-Mo (x.xx.531.x). The firmware you have now (3.32.531.2?) will be fine.
Click to expand...
Click to collapse
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Tritan84 said:
I'll go ahead and try to flash ARHD 34 and see how it goes on TMo. It does say that firmware upgrade should be done prior. Think I'll run in to the wifi/network issues?
Click to expand...
Click to collapse
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
The ARHD thread does recommend a full wipe with the non-matching firmware/ROM base though.
xunholyx said:
You shouldn't have wifi issues. ViperOne is building a Lollipop version right now, and 4.4.4 firmware works fine with it.
Click to expand...
Click to collapse
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Tritan84 said:
OK cool. I'll give it a shot. I really like the Viperone rom, but it's just annoying to have a random loss of network a couple times a day and having to toggle airplane mode. Any thoughts on why that would be happening?
Click to expand...
Click to collapse
Probably because of the conversion from Verizon to T-Mo.
xunholyx said:
Probably because of the conversion from Verizon to T-Mo.
Click to expand...
Click to collapse
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Tritan84 said:
EMERGENCY!! stuck in bootloader/fastboot loop! Won't allow me to go into recovery. Won't allow factory reset. The ROM said it installed succesfully. Banner says modified/Relocked. trying to unlock via htcdev unlock code but fastboot says cannot load 'Unlock_code.bin'
Please help
Click to expand...
Click to collapse
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
xunholyx said:
Oh man, what did you do? In your bootloader under OS is your firmware number. Is it still your old firmware? I don't know how you re-locked.
If you are in fastboot, type fastboot reboot-recovery and see if that works.
Click to expand...
Click to collapse
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Tritan84 said:
OS-3.28.605.4 (4.16.1540.8)
when i put in fastboot reboot-recovery, just a long list of commands show up
Click to expand...
Click to collapse
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
possible progress?? I wasn't in the correct file to fastboot flash files. I moved the unlock code download to the correct file as flashboot, then flashed it. It says "unlock token check successfully." but now it seems the phone is stuck in white htc screen. Is it ok to power down the phone when in this screen? maybe loading the software from new ROM?
so I went ahead and powered down the phone. Still S-off. Now has UNLOCKED banner, but behaving the same. Stuck in bootloader loop. Won't allow me to get into recovery
Tritan84 said:
I was relocked previously trying to update firmware. I completely forgot to unlock it before the ROM flash. I would assume the ROM wouldnt flash though if the phone was relocked. I'm still S-off. Fastboot isn't recognizing the files i want to flash. Won't flash the unlock code. Wouldn't flash a zip file before when trying to update firmware. Can I somehow fix why fastboot isn't flashing files, then try to use unlock code?
Click to expand...
Click to collapse
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
xunholyx said:
Okay. Being S-Off you don't need to lock your bootloader to flash firmware. But since you were trying to flash Developer Edition firmware, you would have to flash a stock Dev Ed backup first, and change your MID and CID.
Leave your phone plugged into your PC.
Go here and follow the option 2 instructions. You want the APP/EXE version to download. It should fix you up.
Click to expand...
Click to collapse
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
nitephlight said:
where do you people come from..you're a self proclaimed noob who has executed an unsupported carrier switch, which ends up with a half functional device as a result.. and then you decide to crank the up the hilarity to warp drive stupid by flashing ANOTHHER unsupported ROM combination on top.
the random signal dropping is most certainly a result of this conversion as I have a couple of related support tickets saying the same.
you should be thankful that unholy is so patient and willing to help.. and that we know he has nothing better to do
Click to expand...
Click to collapse
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Tritan84 said:
I truly do appreciate Unholy's help. He's been great.
I've definitely been humbled by this experience.
Click to expand...
Click to collapse
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
Tritan84 said:
I Got ERROR [130]: Model ID Error
The firmware update utility cannot update your android phone.
Please get the correct Firmware update utility and try again.
I should note that when I got to the prompt to upgrade current firmware to new firmware.....the new firmware was not a sequence of numbers. It looked like random symbols.
Click to expand...
Click to collapse
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
xunholyx said:
I'm not going to be able to come up with a solution tonight. Sorry. I'm going to have to consult with someone who is more of a firmware expert than I am. And the guy whom I will be talking to is probably just waking up (lives in Germany). I'll get back to you as soon as I can. Crappy, I know.
---------- Post added at 11:00 PM ---------- Previous post was at 10:44 PM ----------
You probably just have to change your MID back to M8_VZW. There are tutorials on xda. It's 11pm here and I get up at 4:30. I'm tired and need to sleep. Like I said, sorry. I'll give you more help tomorrow if you don't figure it out before hand on your own.
Click to expand...
Click to collapse
I think you're right. I've tried to search how to change modelid via fastboot since I can't boot the phone to run adb, but all the tutorials seem to be based on using adb. Is their a way to change via fastboot only?
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Tritan84 said:
SUCCESS! Well, I was able to reinstall TWRP via the appropriate adb/fastboot commands and flash my nandroid backup.
Unholy, I know you mentioned doing this command, but I did not know I had to put the .img file name within that command....result of being such a noob. You were awesome and I greatly appreciate you help.
Click to expand...
Click to collapse
Cool. I glad you got everything sorted. :good:
Yeah and the guy from Germany doesn't have the time to look into this anyway...
hi there, I have no back up of stock, and flashed the viper rom with no luck, won't show imei or baseband even though fastboot getvar all shows that information.
1. phone is rooted and unlocked
2. used sunshine to get s off and unlock bootloader
3. supercid 11111111 activated
4 full wipe/clean several times , different roms with no luck
5 tried to flash the newest firmware maybe that will activate it with no luck, I get error stating name does not match in the android info file, tried to edit with notepad++ and entered correct information, re zipped, still giving me errors
6 tried downloading stock image files several times for my service provider, but because the file is so big, it somehow cancels when it reaches 90% network error, and dl won't restart, gotta start all over and same thing happend, cannot get a complete package to try that.
the phone works great with viper rom, its just that I can't use it because of no imei or baseband, I am guessing the previous owner erased the efs partition of the phone while trying new roms, and with backup on hand, I have no idea what to do - my guess IMEI repair or generating a new esf partition with the correct information will work, but how do I do that ?
I am not an expert, just did enough reading and spend some money to get this phone working.
If you have a better idea, or would like to help me I can compensate you for your time.
Thank you so much
it's actually not that easy to erase the efs partition (if it's there on htc devices) without much knowledge...
which operator do you have and which main_version is the original one? i noticed that superCID doesn't work with all firmware.zip don't know why, somehow i wasn't able to flash all and for some i needed to change t he cid to the one matching the firmware, even if it's x.xx.401.x firmware
DeeZZ_NuuZZ said:
it's actually not that easy to erase the efs partition (if it's there on htc devices) without much knowledge...
which operator do you have and which main_version is the original one? i noticed that superCID doesn't work with all firmware.zip don't know why, somehow i wasn't able to flash all and for some i needed to change t he cid to the one matching the firmware, even if it's x.xx.401.x firmware
Click to expand...
Click to collapse
thanks for writing
I had problems flashing firmware as you stated, even though I am supercid , tried once more to flash the latest firmware by changing my id's to the file, almost crashing/bricking my phone, errors, I accidental unplugged phone and it stopped, there was a don't power off warning too, but that stopped once the phone was unplugged from pc, tried again, flashed a NO WIPE firmware M9_3.35* DEV edition and after that flashed the viper rom, worked smoothly the process didnt take as long like before , and it worked, had my imei and baseband. Now it might not be perfect, because I am not getting full reception (3-4 bars at all times) but it works which is great! I will leave it like that unless I can flash a radio that is suitable for this firmware/phone (rogers/canada)
My signal indoors is 3 bars in a high signal area so you probably fixed it.
Sent from my HTC One M9 using Tapatalk
Sorry to resurrect this few month old thread, but I'm currently experiencing the same issue as the OP.
What firmware file did you flash to get things working again?
Cheers
Hi,
Same issue here.
I flashed the Bell firmware for my phone and I still have no IMEI...
zzzer51 said:
Hi,
Same issue here.
I flashed the Bell firmware for my phone and I still have no IMEI...
Click to expand...
Click to collapse
So you are completely bell mobile stock and it's still not working or are you flashing a custom rom?
Sent from my 0PJA2 using XDA-Developers mobile app
thicklizard said:
So you are completely bell mobile stock and it's still not working or are you flashing a custom rom?
Sent from my 0PJA2 using XDA-Developers mobile app
Click to expand...
Click to collapse
I was completely bell mobile stock.
version 1.xxx?
the system downloaded the update for version 2.xxx? and now I got my network back wooohoo!
It wants to download another update but I am afraid to do so! I'm scared I would lose network again...
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Update:
Here are some videos I made showing the issue:
Part 1
Part 2
I will add another one using the stock ROM to further prove the issue exists on both the unlocked firmware, and T-Mobile one.
You root your phone, mess it up and then send it back? Kinda messed up.
Did you try flashing the latest modem?
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
iamtimmah said:
You root your phone, mess it up and then send it back? Kinda messed up.
Click to expand...
Click to collapse
No, I stated the issue was there before then. I only unlocked it and flashed updated firmware in an attempt to fix the issue which it didn't. Clearly we all need to read thoroughly before responding to an OP so we don't look arrogant in the end.
Now, on another note I mentioned this issue was already present from the moment I started using the phone 100% stock. It will sometimes still get LTE, but it only sticks for 10-30 seconds then drops to H/H+ immediately. My S7 Edge and Nexus 6P do not have this issue whatsoever therefore I'm certain something with the firmware is not right.
geoff5093 said:
Did you try flashing the latest modem?
He said this happened before, and he tried rooted and flashing a ROM to see if it made a difference.
Click to expand...
Click to collapse
Thank you, for reading the OP , and no I don't have just the modem files, although I do have the RUU so I know it's in there
Pilz said:
When I first got my HTC LTE was working fine then it suddenly stopped. I called T-Mobile who was clueless, so I popped the sim back into my S7 Edge and Nexus 6P age LTE worked perfectly. I decided to try unlocking s-off etc to flash a more current firmware since mine was on a really old one. I flagged 1.30xx stock then LeeDroid rom being sure to not decrypt data during the process. LTE still won't won't, I'm only getting HSPA+ which sucks. I have another sim card I could activate, but I want to know if there's another way to fix this? My APN seems fine, as does the preferred radio mode. Any suggestions/additional troubleshooting that I can do before sending the phone back
Click to expand...
Click to collapse
Did you try 1.53 us unlocked ruu that's worth a try
bbell101584 said:
Did you try 1.53 us unlocked ruu that's worth a try
Click to expand...
Click to collapse
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Mine has been extremely inconsistent in sticking to LTE. Sometimes I have to force it to LTE only and then when I switch back to GSM/WCDMA/LTE auto, it ****s the bed for a few minutes before correcting itself.
Pilz said:
No, I can't get it to flash, but I'm going to try another method for updating it to that version
Click to expand...
Click to collapse
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
bbell101584 said:
Did you try downloading the ruu.exe on the computer and then running it as administrator also make sure you have either changed your cid to the US unlocked one or to supercid I used the exe version of the ruu it went fine on my end I hope you get your situation worked out
Click to expand...
Click to collapse
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
frankcck said:
I don't know your phone model, but since you are in the US. I would suggest you run US unlocked RUU for eliminating any software issues.
If you have an unlocked device, then you can simply download from @Behold's thread about us unlocked RUU.
If you have a T-mobile device, I would suggest you to get s-off and then run RUU.
Send back your modified phone is likely the least preferred option to do/recommend.
Click to expand...
Click to collapse
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Boot into download mode and run RUU again.
frankcck said:
Boot into download mode and run RUU again.
Click to expand...
Click to collapse
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Pilz said:
I changed my CID/MID to the unlocked model, but the RUU app keeps giving me an error code 155 (I think that's what it was).
If you read the OP I do have S-Off and an unlcoked BL, but the RUU will not flash, what steps are you using to do it? I may have made a mistaken given how I normally flash my Shied or Nexus which are both really easy to do.
Click to expand...
Click to collapse
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
---------- Post added at 02:10 PM ---------- Previous post was at 02:09 PM ----------
Redownload the ruu or just try from a whole different computer if you have access to one
bbell101584 said:
Did you right click the ruu.exe and choose to run as administrative that's the only thing else I can say maybe a more experienced person can help you further sorry
Click to expand...
Click to collapse
Yep, following the instructions to the t (so to speak), it ran fine, booted into whatever that weird screen is with the % on it then after about 15 seconds gave me the error
I just gave the extSD method again, now it is saying
Code:
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 22 RU_HEADER_ERROR
Pilz said:
That's exactly what I did, and I just confirmed the error code was "155 unknown error"
Click to expand...
Click to collapse
I did not boot into download mode. Left it on the home screen, Just made sure USB debugging was on. The RUU handled everything after that.
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Pilz said:
Quick update:
I changed my CID to 111111 and it flashed via the RUU .exe file (surprisingly). I still cannot get LTE other than a ran moment where it might connect for a second before dropping back to H+. I even made a new APN (copied from my S7 Edge) and it still won't get LTE. Could this be some bizarre sim issue despite it working on every other phone I own (4 other phones work fine with LTE and my sim)?
Click to expand...
Click to collapse
Have them re register the device on the network? The US unlocked base should work fine on TMOUS, I know as I have used it and both LTE, VoLTE, and WiFi calling fully work.
Mikee4fun said:
Looks like a sim issue. Try re seating the sim and if that does not work have TMO give you another sim from the store.
Click to expand...
Click to collapse
I have another sim, and I've reinserted it s few times now without success. I might call them and activate the other sim. It's just odd how it works flawlessly with LTE on every phone but this one.
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
How do you have fastboot when fastboot comands are done from download mode? Dont you have a stock system image that you made?
He means bootloader mode, the white screen. I think OP is SOL. That's why it's important to make backups, especially for exotic devices. I'm not sure if it's possible, but since he's s-off his best bet would be to convert to an unlocked or Verizon device if at all possible just to get the device working again and wait for either an ruu or backup.
If he is soffed he can flash an international ruu
Sent from my HTC 10 using XDA-Developers mobile app
Android The Greek said:
If he is soffed he can flash an international ruu
Click to expand...
Click to collapse
Cid and mid still needs to match
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
I remembered the case of failure to entering Download Mode in M9 which solution is flashing the hosd image (extract from firmware), you can give it a try
androg said:
How did you go with this, OP? I just got the HTV32 (HTC10) here in Japan, and unlike previous HTC's I have owned here (Desire, M7), there seems to be no RUUs for Japan anywhere (or am I not looking hard enough...). Website HTCsoku seems very short on info on this model, and the former repository for all things HTC in Japan for modders and tinkerers, 'Scottish Vinegar', has disappeared. Will be getting Sunshine then flashing TWRP and SuperSU soon, but I always like to have the option of stock images, etc., handy, just in case things go tits up.
Click to expand...
Click to collapse
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Many domo's, DarkRazorZ!
I read that twrp-3.0.2-6-pme.img is the one to go for - that what you used?
Good you had no grief from HTC Japan. I actually sent back my M7 for the purple camera issue a few years back and did very little to disguise the fact it was unlocked and S-Offed. I think they are all fellow modders there and don't give a damn what we do. One reason why HTC is awesome.
I am now waiting for Nougat on the HTC10 (they (AU) just did a press release that it will be pushed soon), and as soon as that is on my phone, I shall be going the Sunshine route and installing aforementioned TWRP and so on. Getting fidgety, though... Xposed, Amplify, ad blocking... lemme at 'em.
DarkRazorZ said:
Unfortunately was not able to get a hold of the stock RUU. I took my phone to my carrier and they gave me a new one free of charge despite the unlocked bootloader, S-OFF and TWRP being installed. Was just more careful on the replacement phone.
I actually am still looking for a stock RUU though.
Personally I made a TWRP backup before installing SuperSU. That way I can update with OTAs later on. (once we get an OTA we'll be able to pull the stock recovery img from it and update without issue).
Trying to convert this model to an international model was a terrible mistake. Au KDDI does not play well with these types of things. My Butterfly 3 is permanently SIM locked on AU's network for attempting the same thing (was trying to get Marshmallow at the time, which coincidentally is being released for the device next week).
I have been running Xposed and SuperSU with no issues at all though. If you get any "device encrypted" error after S-OFFing, just factory reset the data in TWRP.
Click to expand...
Click to collapse
Hey I was wondering if you could help me on how to get a replacement device, I ran into the same problem as you did. Thanks
Hello DarkRazorZ.
I'm curious about your attempt to convert HTV32 to international.
It couldn't be done because of hardware compatibility issue among HTV32 and international?
Or because of just your own mistake in the process?
Did you try a method like this?
http://forum.xda-developers.com/htc-10/help/convert-htc-10-to-unlocked-t3384460
I'm in Japan and considering to buy HTV32, and I want to use it with international firmware.
I know this is your thread, but I can't find any information about this on web.
So could you share me your knowledge. Thanks.
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Quadrider10 said:
the us unlocked version can be used on KDDI Au but the verizon radio has to be flashed for it to work and even then, you will only get 2g speeds.
Click to expand...
Click to collapse
No, I'm considering to buy HTV32(= HTC10 for Japan region), not other.
Well I'll make a new thread about this issue.
Thanks for replying Quadrider10, and sorry for disturbing DarkRazorZ.
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. , which I believe you need in order to flash a stock or RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
DarkRazorZ said:
Made a series of mistakes that led me to only have access to fastboot and recovery. It appears I'm capable of flashing things in fastboot. I can't access download mode at all (gives me an error saying it's unable to boot into download mode), which I believe you need in order to flash RUUs in the first place.
If anybody has a TWRP backup of system and boot that'd be awesome, but really need an img of download mode or a RUU or something to help me recover everything to normal. I am S-OFF and bootloader is unlocked.
Checked HTCdev and nothing was there for this device. All help appreciated.
Click to expand...
Click to collapse
hii can u help me how to unlock bootloader on HTC 10 AU version
aSSikn said:
hii can u help me how to unlock bootloader on HTC 10 AU version
Click to expand...
Click to collapse
follow this tut:
https://www.htcdev.com/bootloader/
s2kaka said:
follow this tut:
htcdev
Click to expand...
Click to collapse
i already follow that tutor yesterday.. but when i insert token number the site always says error 170 "CID not allowed"