hello guys i have an AT&T rooted htc one m8 with android 4.4.4, I once got my phone with s-off and updated to an official rom but now is s-on (still rooted) but i want to try an OS that can make a use of the band (3G 900MHz and 4G 1800MHz) because the rom i have from AT&T doesn't have the 3G 900MHz so my phone is either "4g" and "E" i don't have any 3g or h+
so can i install another (EMEA or ASIA OS) so i can get this bands working and all this by S-ON
(I live in venezuela so i can't buy the 25$ sunshine thing even if i have money because the government wont give us a dime to buy things in usd *sigh*)
You should update your firmware/OS to 4.28.502.2 first before you try other thing.
You can read How-To and link to RUU 4.28.502.2 here : http://forum.xda-developers.com/showthread.php?t=2751432
Then after, you can install TWRP 2.8.7.0 and make backup of your current ROM then try install other ROM and see whether you'll get what you want.
I remember I tried AT&T radio on my Asia WWE ROM, I don't have problem with 3G
i think i cant because I need to flash a different radio and i need to be S-OFF
This is a direct continuation of the thread you started here: http://forum.xda-developers.com/htc-one-m8/help/modify-set-band-htc-one-m8-att-t3286190
You should not have started a new thread. This just confuses those trying to help, and will lead to you getting confused also.
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
mabf000 said:
but i want to try an OS that can make a use of the band (3G 900MHz and 4G 1800MHz) because the rom i have from AT&T doesn't have the 3G 900MHz
Click to expand...
Click to collapse
OS has nothing to do with band support.
You are confusing the term "firmware" with OS. Please erase from your brain that these 2 things are the same. On this device, "firmware" refers to specific partitions, separate from the OS (ROM). Firmware (specifically the radio baseband, which is contained in firmware) has nothing to do with the OS (ROM). Changing the OS will not change your band support.
I already told you how to change the firmware in your other thread. Now it sounds like you are trying to do something different. Although its not clear, since you have jumped to a new thread.
---------- Post added at 10:09 AM ---------- Previous post was at 10:05 AM ----------
mabf000 said:
I once got my phone with s-off and updated to an official rom but now is s-on (still rooted)
Click to expand...
Click to collapse
The only way the phone would have been made s-on again (after being s-off) is if you changed it manually.
Something doesn't make sense here. Are you sure it was s-off?
Do a fastboot getvar all, and post the output (delete IMEI and serial number before posting, as these are personal info).
mabf000 said:
so can i install another (EMEA or ASIA OS) so i can get this bands working and all this by S-ON
Click to expand...
Click to collapse
I already stated in your other thread, that s-off is required to change band support. Why are you asking if you can do it s-on? Obviously, the answer is NO.
This is one of the reasons you need to stick to one thread, and not make new ones for the same exact questions/issue.
mabf000 said:
(I live in venezuela so i can't buy the 25$ sunshine thing even if i have money because the government wont give us a dime to buy things in usd *sigh*)
Click to expand...
Click to collapse
What does the government have to do with making a small credit card purchase?
When you make a credit card purchase, it gets automatically converted to your local currency. Currency is currency, the purchase doesn't have to be made in US dollars.
One note - if the phone was ever S-off'ed via Sunshine, it may still have a valid device license. You might just try running Sunshine again and see if it asks for payment.
redpoint73 said:
This is a direct continuation of the thread you started here: http://forum.xda-developers.com/htc-one-m8/help/modify-set-band-htc-one-m8-att-t3286190
You should not have started a new thread. This just confuses those trying to help, and will lead to you getting confused also.
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
OS has nothing to do with band support.
You are confusing the term "firmware" with OS. Please erase from your brain that these 2 things are the same. On this device, "firmware" refers to specific partitions, separate from the OS (ROM). Firmware (specifically the radio baseband, which is contained in firmware) has nothing to do with the OS (ROM). Changing the OS will not change your band support.
I already told you how to change the firmware in your other thread. Now it sounds like you are trying to do something different. Although its not clear, since you have jumped to a new thread.
---------- Post added at 10:09 AM ---------- Previous post was at 10:05 AM ----------
The only way the phone would have been made s-on again (after being s-off) is if you changed it manually.
Something doesn't make sense here. Are you sure it was s-off?
Do a fastboot getvar all, and post the output (delete IMEI and serial number before posting, as these are personal info).
I already stated in your other thread, that s-off is required to change band support. Why are you asking if you can do it s-on? Obviously, the answer is NO.
This is one of the reasons you need to stick to one thread, and not make new ones for the same exact questions/issue.
What does the government have to do with making a small credit card purchase?
When you make a credit card purchase, it gets automatically converted to your local currency. Currency is currency, the purchase doesn't have to be made in US dollars.
Click to expand...
Click to collapse
yeah im sorry to open a new thread to this i was very confused,
now this is what i get to the fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
i think my phone never was S-OFF i was thinking about it and i never did it before, i think the only way to get all my bands working is getting the phone s-off and flash it anothe radio version, and i dont know what happens when im trying to install the AT&T rom from htc website cuz RUU always gives me an error, I cant get supercid it gives me an error so i think all my problems are because im s-on =(
and i want to buy the license to sunshine but in venezuela that's almost impossible, you should read more about venezuela government right now its insane
mabf000 said:
i think my phone never was S-OFF i was thinking about it and i never did it before
Click to expand...
Click to collapse
This isn't something you should "think" or not. It either was s-off by sunshine, or it was never s-off. You need to get your facts straight, and provide the correct information, otherwise nobody here can do a thing to help you.
mabf000 said:
i think the only way to get all my bands working is getting the phone s-off and flash it anothe radio version,
Click to expand...
Click to collapse
I've already stated definitively and emphatically, that you can only change band support (flash another radio) with s-off.
I don't understand why you continue to question this, or say "I think". Its irrelavent what you "think", what I've told you is fact.
I'm sorry if I sound annoyed; since, well . . . I am annoyed. But I have little patience for folks that can't follow instructions, or accept simple advice given to them.
mabf000 said:
i dont know what happens when im trying to install the AT&T rom from htc website cuz RUU always gives me an error, I cant get supercid it gives me an error so i think all my problems are because im s-on =(
Click to expand...
Click to collapse
RUU runs fine with s-on. Its designed for stock devices.
On the bootloader screen, does it say LOCKED, UNLOCKED, or RELOCKED near the top of the screen?
Although the RUU will just update the OS version, it is not going to change the band support.
mabf000 said:
and i want to buy the license to sunshine but in venezuela that's almost impossible, you should read more about venezuela government right now its insane
Click to expand...
Click to collapse
I'm not interested in the details. Either its possible or not possible to buy a sunshine license. I don't know what "almost impossible" means.
The sunshine devs are usually willing to accept alternate payment methods (such as buying a gift card); due to difficulties paying in some countries. If you want to change band support, I'd suggest contact the sunshine team, and see what they can do with you.
Otherwise, stop fantasizing there is a way to change band support with s-on; since its not possible.
redpoint73 said:
RUU runs fine with s-on. Its designed for stock devices.
On the bootloader screen, does it say LOCKED, UNLOCKED, or RELOCKED near the top of the screen?
Although the RUU will just update the OS version, it is not going to change the band support.
Click to expand...
Click to collapse
it says *** UNLOCKED ***
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
i downloaded the latest RUU from htc website to my at&t and I always get error 155
mabf000 said:
it says *** UNLOCKED ***
i downloaded the latest RUU from htc website to my at&t and I always get error 155
Click to expand...
Click to collapse
As you should. With s-on, you need to relock the bootloader in order to RUU. Relock the bootloader with fastboot command:
fastboot oem lock
After you RUU, you can unlock the bootloader again (if you wish) either by using the unlock bin code from the first time you unlocked; which doesn't always work, so many folks have had to just go through HTCDev.com to get a new bin code.
Then install TWRP, root, etc.
Also, there was no need to post your getvar data again. It wasn't asked for, it doesn't contain the bootloader status (which is why I asked for it separately) and unless anything has changed (doesn't appear so) its just redundant. Most folks here are actually good at reading what has already been posted.
thank you so much and Im really sorry if I annoyed you, im really a noob with all of this
mabf000 said:
thank you so much
Click to expand...
Click to collapse
There' s a button for that.
mabf000 said:
Im really sorry if I annoyed you, im really a noob with all of this
Click to expand...
Click to collapse
No worries. Just try to post more carefully in the future. Take a moment to think if its really necessary to create a new post, ask the same question you just asked, or post the same info you just post. In most cases, the answer will be NO.
I can understand wanting to be sure about things, or wanting more opinions. But the way you went about it was all wrong.
redpoint73 said:
There' s a button for that.
No worries. Just try to post more carefully in the future. Take a moment to think if its really necessary to create a new post, ask the same question you just asked, or post the same info you just post. In most cases, the answer will be NO.
I can understand wanting to be sure about things, or wanting more opinions. But the way you went about it was all wrong.
Click to expand...
Click to collapse
hi there again, ok i got my device s-off and change the cid to supercid and the mid to the at&t what is the next step to flash the radio to get all my bands working, you already say that the emea or the asian but i got lost there where i can find them and how can i flash it? need some help with that
mabf000 said:
hi there again, ok i got my device s-off and change the cid to supercid and the mid to the at&t
Click to expand...
Click to collapse
What do you mean you changed the MID to AT&T? It was already the AT&T MID, since you have the AT&T device.
redpoint73 said:
What do you mean you changed the MID to AT&T? It was already the AT&T MID, since you have the AT&T device.
Click to expand...
Click to collapse
yes i did notice that, so i didnt change the mid but i actually flash this ruu (RUU_M8_UL_L50_SENSE60_MR_HTC_Europe_4.16.401.10_Radio_1.25.214500021.06G_20.68.4196t.01_F_release_417003_signed)
thats the europe version (i think) but i cant get my at&t device to get 3g or h+
You're hopping back and forth between this thread, and the other one you started: http://forum.xda-developers.com/htc-one-m8/help/modify-set-band-htc-one-m8-att-t3286190/post64980222#post64980222
Makes it super confusing what the sequence of the steps you tried, latest current condition, and what is working and what is not.
Pick one thread, and stick to it. Do not bounce back and forth.
And here is another one that related - http://forum.xda-developers.com/htc-one-m8/help/red-triangle-trying-to-update-firmware-t3301484
Related
Yesterday I decided to convert my Htc One M8 into the google play edition using the method provided by the people here in xda. The process was very long but I was successful in converting my Htc. However there is one problem that i need help with. My baseband version is unknow. Most of the option in the about is also unknow. I can function the phone normally but because of this unknow problem i cannot get my phone to read my sim. I bought this Htc here in Thailand. I don't know what to do to fix this. Before all of this i was able to use this sim. By the way i just went and change my sim today but that didn't help.
mapringg said:
Yesterday I decided to convert my Htc One M8 into the google play edition using the method provided by the people here in xda. The process was very long but I was successful in converting my Htc. However there is one problem that i need help with. My baseband version is unknow. Most of the option in the about is also unknow. I can function the phone normally but because of this unknow problem i cannot get my phone to read my sim. I bought this Htc here in Thailand. I don't know what to do to fix this. Before all of this i was able to use this sim. By the way i just went and change my sim today but that didn't help.
Click to expand...
Click to collapse
theres a radio thread here in general. i think theres a thai radio. you can flash that instead of gpe radio
edit sorry theres no thailand radio, you can try wwe radio or dev edition also
rbouza1 said:
theres a radio thread here in general. i think theres a thai radio. you can flash that instead of gpe radio
edit sorry theres no thailand radio, you can try wwe radio or dev edition also
Click to expand...
Click to collapse
Hi,
I seem to face the same problem.. Not finding threads to get the radios.. Help please..
thedrunkpretorian said:
Hi,
I seem to face the same problem.. Not finding threads to get the radios.. Help please..
Click to expand...
Click to collapse
Give some more info...what version, do you know?
BerndM14 said:
Give some more info...what version, do you know?
Click to expand...
Click to collapse
Version as in.. Sorry didn't get u..
I stay in dubai .. Local carrier is DU
thedrunkpretorian said:
Version as in.. Sorry didn't get u..
I stay in dubai .. Local carrier is DU
Click to expand...
Click to collapse
Software/Firmware version, like mine for international is 1.54.401.10 ...?
I almost thought you're from South Africa "pretorian"
Edit: You're on GPE now so I take it that perhaps you didn't take note of your original CID/MID and Main-Version #. Unless you perhaps made a backup of your device? =o/
BerndM14 said:
Software/Firmware version, like mine for international is 1.54.401.10 ...?
I almost thought you're from South Africa "pretorian"
Click to expand...
Click to collapse
Don't have the phone at the moment.. But surely shall post..
No thts just a gaming tag I was using few years back.. I live in dubai..
And just to understand it says baseband unknown.. In general this is something tht can be made right yea?
thedrunkpretorian said:
Don't have the phone at the moment.. But surely shall post..
No thts just a gaming tag I was using few years back.. I live in dubai..
And just to understand it says baseband unknown.. In general this is something tht can be made right yea?
Click to expand...
Click to collapse
It should show the baseband info again when you flash/reflash the radio. Similar to main-version etc it got lost after I unlocked, flashed, flashed back etc. It returned all the info again with the first OTA I updated device with.
Thing is I don't know if GPE radios will work for anyone outside of the US as it's probably build for US carriers and maybe some EU since it can be sold there too. A lot of people had to flash back their original radio.img that came with the device in order to connect to the network.
BerndM14 said:
It should show the baseband info again when you flash/reflash the radio. Similar to main-version etc it got lost after I unlocked, flashed, flashed back etc. It returned all the info again with the first OTA I updated device with.
Thing is I don't know if GPE radios will work for anyone outside of the US as it's probably build for US carriers and maybe some EU since it can be sold there too. A lot of people had to flash back their original radio.img that came with the device in order to connect to the network.
Click to expand...
Click to collapse
i suggested the wwe radio or dev edition radios. for me in michigan the dev radio on gpe is better than att or gpe
Here is a link to GSM radios thread. WWE and Dev edition would be the ones to try first.
Too51oll said:
Here is a link to GSM radios thread. WWE and Dev edition would be the ones to try first.
Click to expand...
Click to collapse
Hi,
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.000
(bootloader) version-baseband: 1.14.2133193
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT459WM07709
(bootloader) imei: 358716053240981
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Hope this helps you better understand the device. any help wud be helpful
Hi all,
So I have my old M8 doing nothing (switched to Note 4)...
It's running a custom venom rom, and basically I want to put it completely back to factory state.
If you could help a guy that's moderately good at this stuff, I would be greatly appreciated.
Thanks!!
Post the output from fastboot getvar all and we'll tell you what to do
Thanks for that, err - I haven't got the tools installed any more, could you point in the direction of the tools again sorry!
Ok, getvar just sits at waiting for device...?
Ok sorry, turns out I'm just rusty!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Done, and thanks!
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Shozuki said:
Sorry to be a pain, is there another way to achieve S-Off without paying sunshine?
Thanks
Click to expand...
Click to collapse
No other way, only sunshine.
But you don't need S-Off to revert to stock with that thread guide, you need to relock bootloader then follow all the steps.
The only thing is without S-Off, your bootloader will show RELOCKED instead of LOCKED.
Ah cool, minor.
Thanks
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
EddyOS said:
S-OFF would probably add a bit to resale value so might be worth doing - up to you of course!
Click to expand...
Click to collapse
Indeed, but I'm literally giving it my uncle and let him use it.
If I may ask one more thing though, when sending the ruu.zip
I get:
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 3(s)
Any ideas??
Thanks for your help sirs.
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
EddyOS said:
That seems to come up randomly and doesn't really appear to point to anything in particular. You've definitely got a locked bootloader and are using the htc_fastboot?
Click to expand...
Click to collapse
Unfortunately it's still unlocked, but I can't seem to change that either. I'm using minimal adb and fastboot, but the htc_bootloader is in the folder.
Am I supposed to use that from the start, as I only see reference in the final stage.
Apologies, if I'm misreading!
EDIT, I followed the guide starting with recovery which kept failing... That must be the issue...
from your guide EDIT: Thread I meant:
"Well lord knows what's going on here...
I started by flashing the recovery to the one linked here. It won't boot into recovery at all it just sits at "entering recovery..."
I was using a venom custom rom and TWRP 2.8.5.0 touch recovery.
I can boot into the phone, use fastboot and adb - but can't go any further in restoring the handset back to factory... All help appreciated."
ckpv5 said:
1. remove the imei no. & serial no. in your above post.
2. check EddyOS thread : http://forum.xda-developers.com/showthread.php?t=2735235
You have everything that you need there. The guide will put your device back to stock but updated to the latest lollipop stock ROM
Click to expand...
Click to collapse
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
Yeah, That guide is for EU M8's only...
really struggling getting mine back to factory...
crazyandroider said:
does it matter which region it's from? I am using a canadian Carrier (rogers). And I can't really find ruu for Canadian carrier. Any help/ guidance would be appreciated thanks.
Click to expand...
Click to collapse
That depends. Are you s-off? If so, you can run a WWE RUU, and go back to basically stock. WWE is compatible with Rogers. You won't get OTAs though. You'll have to update firmware manually, but with s-off, that's easy to do.
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Shozuki said:
My apologies, I failed to use my eyes.
All solved. Many thanks!!
Click to expand...
Click to collapse
What was it?
EddyOS said:
What was it?
Click to expand...
Click to collapse
Well basically I was following the instructions as if I were S-Off.
Instead I just to use: fastboot oem lock and completely skimmed over the text failing to read it!
My uncle is happy now and thats fine with me!
Thanks for your help!
I need a Little help regarding identifying my version of M8
I have looked up the imie number on IMIE Data website and found that its a AT&T US Unlocked Phone.
Now when i try to flash the latest firmware for AT&T through RUU file it gets stuck at sending file stage 1/6 .... ( I have waited about 15 minutes, nothing happened)
Then I have also tried to flash unlocked version firmware and this time i have recieved ERROR 155 - IT says the device is not matching with firmware.
After that i have downloaded some apps from play store related to phone info search.
All these apps are suggesting that its a Sprint_WWE phone.
My phone does not have any logo on it or any bloat ware from the career.
I am confused now, which version of M8 i am using and which firmware RUU should i flash?
Please note: My Bootloader is in locked state and official recovery installed. Never rooted or CWM installed.
I am using this phone in Bangladesh right now so OTA is not coming to my phone.
fastboot getvar all without serial & imei no. will tell your device version.
where should i type it in?
G:\Android\Nexus 7 Wifi\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499076047
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: b9f91aef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.027s
Click to expand...
Click to collapse
This is what i got which version is it?
tpteam6 said:
This is what i got which version is it?
Click to expand...
Click to collapse
It might be AT&T branded, but, according to the CID#, your device is completely unlocked and you can basically flash anything. However, you can't flash an AT&T RUU unless you change the CID# back to the default AT&T CID.
(bootloader) product: m8_whl
Click to expand...
Click to collapse
isnt this is for sprint?
and how do i get back to the default CID?
i have tried AT&T, SPRINT & Unlocked Version RUU nothing worked.
AT&T RUU Stucked at sending files,
Sprint RUU Gave ERROR 155
Unlocked RUU Gave ERROR 155 As well.
tpteam6 said:
This is what i got which version is it?
Click to expand...
Click to collapse
First, remove serial & imei no.
m8_whl is a sprint device.
Don't ever install any GSM firmware on your device, it'll brick the radio
but i am using gsm network here. its not a CDMA device..
tpteam6 said:
but i am using gsm network here. its not a CDMA device..
Click to expand...
Click to collapse
Yeah I know you're on GSM network. My advise was never install a GSM firmware like AT&T, Intl GSM & etc. Only Sprint firmware.
then should i set the CID to default Sprint CID? and what is that?
i need help here.. how can i update to lollypop or marshmellow? i have downloaded sprint RUU file but getting error 155. Should i reset the CID to some thing other than "11111111"? please advice.
tpteam6 said:
i need help here.. how can i update to lollypop or marshmellow? i have downloaded sprint RUU file but getting error 155. Should i reset the CID to some thing other than "11111111"? please advice.
Click to expand...
Click to collapse
The Sprint RUU should run fine with SuperCID (11111111).
Error 155 typically means your bootloader is unlocked (which will block RUU). Relock it with the command (run the same way you did fastboot getvar all):
fastboot oem lock
---------- Post added at 10:45 AM ---------- Previous post was at 10:43 AM ----------
tpteam6 said:
but i am using gsm network here. its not a CDMA device..
Click to expand...
Click to collapse
The Sprint version supports CDMA and GSM networks. It doesn't matter whether you are using CDMA or not, its still the "CDMA" (supports CDMA) version of the M8.
But on fasboot im seeing "Botloader status is locked"
Ragarianok said:
It might be AT&T branded, but, according to the CID#, your device is completely unlocked and you can basically flash anything. However, you can't flash an AT&T RUU unless you change the CID# back to the default AT&T CID.
Click to expand...
Click to collapse
1) The product name (m8_whl), model number (0P6B70000), and version number (x.xx.651.xx) all point to this being the Sprint version. The IMEI search coming up with AT&T is odd, and almost certainly incorrect.
2) SuperCID doesn't quite mean you can "flash anything". As ckpv5 pointed out, you can't flash GSM firmware to the Sprint (or Verizon) device, or the result is a radio brick. More commonly, even for the GSM version, you will often need to change the MID to run other version RUUs.
3) The proper version RUU will run fine with SuperCID.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
tpteam6 said:
But on fasboot im seeing "Botloader status is locked"
Click to expand...
Click to collapse
What is the exact file name of the RUU you are trying to run?
Link the source, if you can.
D:\Android\Nexus 5\AndroidSDKSlim Nexus 5\android-sdk-windows\platform-tools>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
(bootloader) Input CID is super CID
(bootloader) Start Verify: 0
OKAY [ 0.028s]
finished. total time: 0.028s
D:\Android\Nexus 5\AndroidSDKSlim Nexus 5\android-sdk-windows\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.012s]
finished. total time: 0.012s
D:\Android\Nexus 5\AndroidSDKSlim Nexus 5\android-sdk-windows\platform-tools>
tpteam6 said:
But on fasboot im seeing "Botloader status is locked"
Click to expand...
Click to collapse
On the hboot screen, what does it say near the top LOCKED, RELOCKED or UNLOCKED?
lollypop:
RUU_M8_WHL_L50_SENSE60_SPCS_MR_Sprint_WWE_4.25.651.14_Radio_1.09.20.0209_NV_SPCS_1.52_003_release_426232_signed_2
http://www.droidviews.com/restore-sprint-htc-one-m8-to-stock-rom-with-ruu/
I have downloaded it from a third party site.
Marshmellow
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3
http://www.htc.com/us/support/htc-one-m8-sprint/news/
I Have dowloaded it from HTC Site
redpoint73 said:
On the hboot screen, what does it say near the top LOCKED, RELOCKED or UNLOCKED?
Click to expand...
Click to collapse
Its Saying "Locked"
redpoint73 said:
1) The product name (m8_whl), model number (0P6B70000), and version number (x.xx.651.xx) all point to this being the Sprint version. I don't see why you think its AT&T.
2) SuperCID doesn't quite mean you can "flash anything". As ckpv5 pointed out, you can't flash GSM firmware to the Sprint (or Verizon) device, or the result is a radio brick. More commonly, even for the GSM version, you will often need to change the MID to run other version RUUs.
3) The proper version RUU will run fine with SuperCID.
I understand and appreciate you are trying to be helpful. But please try to verify the information, before passing them along. Especially in this case, the advice could have resulted in permanent damage the OP's device.
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
What is the exact file name of the RUU you are trying to run?
Link the source, if you can.
Click to expand...
Click to collapse
When i search my imie on Imie data site i get that its a AT&T device
Do i need to root or custom recovery to update via RUU?
Hello guys,
Months ago i bought an HTC One M8 on Aliexpress, it worked fine for a few days but suddently refused to detect my sd-card, so i managed to install a new rom (Android_Revolution_HD-One_M8_50.2_76b56b). Everything worked fine until a few days, when my phone was seemingly unrooted. So i decided to update to a newer version.
Then here we are, i downloaded dozens of roms but was unable to boot any rom i installed, im by far not an expert but i managed to use abd and fastboot to install twrp 3. I finally managed to install Cyanogen (cm-13.0-20151228-NIGHTLY-m8) but it didnt detecter either my SIM, IMEI and crashed all the time.
Now i'm running a nandroid backup with a Marshmallow Sense 7 rom i downloaded here: androidsage.com/2016/03/08/update-verizon-htc-one-m8-to-marshmallow-using-custom-files-ruu-ota using their firmware (m8MfirmwareTWRP3_0_0_1)
But it does not detect my sim card neither my IMEI
The phone is S-OFF with TWRP-3, supercid, modified MID (from 0P6B20000 to 0P6B10000) and Official HBOOT
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA45XXXXXXXX
(bootloader) imei: 3587180XXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 99000499686942
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
At my point i'm willing to install any rom as long as it works..
Thanks.
phoeniiiix said:
The phone is S-OFF with TWRP-3, supercid, modified MID (from 0P6B20000 to 0P6B10000) and Official HBOOT[/B]
(bootloader) version-main: 1.54.401.5
(bootloader) product: m8_wlv
Click to expand...
Click to collapse
MID 0P6B20000 and product ID m8_wlv are for the Verizon version (supports CDMA, in addition to GSM, but we call it the "CDMA version" here).
You flashed a Euro firmware 1.54.401.5 and bricked the radio. This is a known result of trying to flash non-CDMA firmware to the Verizon or Sprint M8 variants, which should never have been done.
The damage may be permanent. The most you can do is change back to the Verizon MID, and flash Verizon RUU, and pray it fixes the radio issue. http://forum.xda-developers.com/verizon-htc-one-m8/general/vzw-m8-master-ruu-firmware-collection-t2946473
If not, the radio is permanently bricked.
Thanks for the awnser
I can still flash the radio, does that mean its not bricked ? (im not familiar with android internal filesystem)
In case the phone is bricked, is changing the main motherboard a good idea (50€ on ebay), i also eard of jtag unbrick services
Back
So as you recommended, i installed a verizon rom, and this time it actually show my IMEI in settings :good:, and i launched adb shell to change my MID
Now it seems to "detect" my sim card, it ask for it but says "no service" and does not ask for the pin, does that mean the phone is carrier locked (some boxes are greyed out when i try to add APNs) ? In case it is, how can i safely unlock it, i'm from France and my carrier is Orange
phoeniiiix said:
Back
So as you recommended, i installed a verizon rom, and this time it actually show my IMEI in settings :good:, and i launched adb shell to change my MID
Now it seems to "detect" my sim card, it ask for it but says "no service" and does not ask for the pin, does that mean the phone is carrier locked (some boxes are greyed out when i try to add APNs) ? In case it is, how can i safely unlock it, i'm from France and my carrier is Orange
Click to expand...
Click to collapse
You'll have to buy an Unlock code.
Also, the IMEI on your phone has been changed.
Verizon and Sprint IMEIs start with 99x, yours is starting with 35x to try and make it look like an international model.
Notice the meid still starts with 99, as the seller probably didn't bother or forgot to change it.
Sent from my HTC One_M8
phoeniiiix said:
So as you recommended, i installed a verizon rom, and this time it actually show my IMEI in settings :good:, and i launched adb shell to change my MID
Click to expand...
Click to collapse
Try not to use the term "ROM" interchangeably with "RUU", as doing so may add unnecessary confusion to the discussion. They are different things. The RUU re-images all partitions, something like 41 partitions. Of which, the ROM is just one.
phoeniiiix said:
Now it seems to "detect" my sim card, it ask for it but says "no service" and does not ask for the pin, does that mean the phone is carrier locked (some boxes are greyed out when i try to add APNs) ? In case it is, how can i safely unlock it, i'm from France and my carrier is Orange
Click to expand...
Click to collapse
The Verizon version is unlocked from the factory. So I'm suspicious whether a SIM unlock will actually work, or if its a function of the radio brick (improper firmware flash). I suppose trying to unlock is low risk, as long as you use a service that does not charge money if it doesn't work (as many of them have that policy).
I'm also not sure if a SIM unlock will work, if the IMEI has been hacked (as the previous user pointed out).
---------- Post added at 09:39 AM ---------- Previous post was at 09:35 AM ----------
phoeniiiix said:
In case the phone is bricked, is changing the main motherboard a good idea (50€ on ebay), i also eard of jtag unbrick services
Click to expand...
Click to collapse
Either may be an option. But changing the motherboard yourself is not that easy, and I don't personally recommend it unless you are very experienced and comfortable doing such things. I've seen more than a few reports of such repairs go badly on this device. Its fairly common to break something else while trying to "fix" the mobo.
A paid mobo or JTAG may be a better option.
Thanks a lot, using the RUU update you provided (0P6BIMG) i was able to fix it, you saved my phone i'm so glad =)
I have a 'new in the box' M8 that appears to be an AT&T UK model
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
OTA does not show any updates available (I am in the USA), and none of the RUU or ROM.zip files I can find for AT&T, unlocked, sense, Google, etc will run without failing.
Can anyone please walk help me find the necessary files, fix any settings already in the phone and walk me through updating/changing the phone to US AT&T or, preferably, Sense Marshmallow.
Thanks.
dale_j said:
I have a 'new in the box' M8 that appears to be an AT&T UK model
Click to expand...
Click to collapse
I think you mean "US model" as there is no AT&T UK model.
dale_j said:
(bootloader) version-main: 3.28.401.9
(bootloader) modelid: 0P6B63000
OTA does not show any updates available (I am in the USA), and none of the RUU or ROM.zip files I can find for AT&T, unlocked, sense, Google, etc will run without failing.
Click to expand...
Click to collapse
I think your main problem is that your firmware number (3.28.401.9) doesn't jive with your model ID (0P6B63000), therefore preventing any OTA updates, or RUUs from being run.
dale_j said:
Can anyone please walk help me find the necessary files, fix any settings already in the phone and walk me through updating/changing the phone to US AT&T or, preferably, Sense Marshmallow.
Click to expand...
Click to collapse
Is AT&T your carrier. And do you want the AT&T branded stock ROM, or no?
---------- Post added at 10:06 AM ---------- Previous post was at 10:05 AM ----------
You should also delete your IMEI and serial number from your post, as these are private info.
redpoint73 said:
I think you mean "US model" as there is no AT&T UK model.
I think your main problem is that your firmware number (3.28.401.9) doesn't jive with your model ID (0P6B63000), therefore preventing any OTA updates, or RUUs from being run.
Is AT&T your carrier. And do you want the AT&T branded stock ROM, or no?
---------- Post added at 10:06 AM ---------- Previous post was at 10:05 AM ----------
You should also delete your IMEI and serial number from your post, as these are private info.
Click to expand...
Click to collapse
According to HTC's warranty site, the serial belongs to an AT&T phone from the UK/Europe.
My carrier is US AT&T through NET10, so I need the AT&T APN info, but would prefer either plain vanilla android or HTC's SENSE version, and can edit that info once the phone is running Marshmallow.
Following another thread here, I tried using adb shell to change the MID to 0p6b61000. The shell went to a $ prompt and not the # prompt the instructions called for. I tried 'us' as suggested and got a 'not found' response. I still tried the lengthy command listed, and got a restricted/locked/no permission/etc. (can't remember exact wording) response.
I joined HTC's DEV, so I could unlock the bootloader, and tried everything above and all the ROM files I have both as RRU and as ROM.zip on the SD card with the bootloader locked, unlocked and again with it relocked.
I did try editing out the serial and imei yesterday. I will try again after replying here.
I have an email into HTC's tech and so far no response from them.
Thanks again,
Dale
dale_j said:
According to HTC's warranty site, the serial belongs to an AT&T phone from the UK/Europe.
Click to expand...
Click to collapse
Probably a mistake. No AT&T in UK or Europe. And your product code m8_ul_ca signifies AT&T US or US Developer's Edition.
Doesn't really matter, in any case.
dale_j said:
My carrier is US AT&T through NET10, so I need the AT&T APN info, but would prefer either plain vanilla android or HTC's SENSE version, and can edit that info once the phone is running Marshmallow.
Click to expand...
Click to collapse
Based on that description, I'd suggest the US Developer's Edition RUU (6.12.1540.4). It is unbranded Sense, but already has the proper radio bands and APN setup for AT&T.
dale_j said:
Following another thread here, I tried using adb shell to change the MID to 0p6b61000. The shell went to a $ prompt and not the # prompt the instructions called for. I tried 'us' as suggested and got a 'not found' response. I still tried the lengthy command listed, and got a restricted/locked/no permission/etc. (can't remember exact wording) response.
Click to expand...
Click to collapse
Is the phone rooted? It needs to be, to change the MID. I'm guessing that is why you aren't getting the # prompt.
dale_j said:
I joined HTC's DEV, so I could unlock the bootloader, and tried everything above and all the ROM files I have both as RRU and as ROM.zip on the SD card with the bootloader locked, unlocked and again with it relocked.
Click to expand...
Click to collapse
If using the SD card install method, did you rename the RUU to 0P6BIMG.zip
With s-off, the RUUs will work whether the bootloader is locked or not. So it's kind of a waste of time changing it back and forth. I'd suggest leaving it unlocked, as that gives you the most options.
Also, most the Marshmallow RUUs for the US versions, have a weird requirement, where the firmware (hboot, radio, etc.) need to be updated, before the RUU will work.
So my suggestion would be:
1) Root and fix the MID to be AT&T/US Dev Edition
2) Flash the 6.12.1540.4 firmware from here: https://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
3) Flash the 6.12.1540.4 RUU
What is the easiest/safest way to root my M8?
Thanks,
Dale
dale_j said:
What is the easiest/safest way to root my M8?
Click to expand...
Click to collapse
With bootloader unlocked, flash TWRP 3.1.1 using fastboot. Then flash SuperSU 2.82 in TWRP.
https://twrp.me/devices/htconem8gsm.html
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Thank you for all the help.
I have Marshmallow DEV running on the new M8, but still have a couple questions and possible help issues.
Current getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Should the bootloader version still be the same and not a newer version?
Is there a newer DEV version? AT&T ver is 6.2.................. DEV is 6.1...............
Will there be any connection issues with the baseband not matching the 4.0.U605................... version in my original AT&T M8?
Will it matter that the security patch level on the original AT&T M8 is 2016-13-01 and the new (now DEV) M8 is 2015-12-01?
What is the best free app to transfer everything between the phones?
I tried HTC's builtin app, but custom ringtones, alarms, WiFi connections and PWs, custom wallpapers and about 60% of my phone contacts did not transfer. I ran the app twice.
I also could not get the NFC transfer to work. WiFi, BT and NFC were all on on both phones, however following the instructions on the screen (tap and hold backs together until sound signals) did nothing with several tries and holding them together in excess of 5 minutes.
Thanks again for all the help,
Dale
My responses below, in red font:
dale_j said:
Is there a newer DEV version? AT&T ver is 6.2.................. DEV is 6.1...............
No newer Dev Ed version. 6.12 is the last (final) one. I wouldn't have suggested it, if there was a newer one.
The difference in the numbering between Marshmallow AT&T versus Dev Ed is probably not too significant. Probably based on the same software base, just that AT&T takes so darned long to test and approve the updates (plus adding their branding and bloat), so it was one of the last MM updates to be released. In other words, not really a newer "version" in any significant way. Just released later.
Will there be any connection issues with the baseband not matching the 4.0.U605................... version in my original AT&T M8?
I wouldn't expect any. AT&T and Dev Ed are supposed to support the same bands. I've often wondered why AT&T version uses the strange baseband numbers (most other use 1.25, 1.29, etc.). But again, I suspect the actual differences are minimal or none.
Will it matter that the security patch level on the original AT&T M8 is 2016-13-01 and the new (now DEV) M8 is 2015-12-01?
Not sure if the patch date for the Dev Ed is correct. It would mean the patch level was almost a year old (when the RUU was released Dec. 2015), which is a bit excessive.
In the big picture, we are using Android versions with patch levels that are over a year old (unless you run an AOSP based custom ROM). So technically, there are more vulnerabilities (newer patch level is better). But how much difference this actually makes in practice is debatable.
In any case, I wouldn't personally run the AT&T stock ROM, just because it has a newer patch level (if that is what you are thinking). I personally hate the AT&T branding and crappy bloatware, it just wouldn't be worth it to me.
What is the best free app to transfer everything between the phones?
I tried HTC's builtin app, but custom ringtones, alarms, WiFi connections and PWs, custom wallpapers and about 60% of my phone contacts did not transfer. I ran the app twice.
I would recommend storing your contacts via Google. This way, it's on the cloud, and always backed up (automatically, and requires no additional action by you), and easily accessed. When you setup a new Android phone, and login to your Google account, your contacts will automagically just sync to the phone. It's one of the great things about Android. Doing it this way, might not be for everyone (for instance, you might have work and personal contact you like to keep separate). But I personally love it.
Files such as ringtones and wallpapers can be easily migrated. Literally, you can just copy and paste them. But you'll need an intermediary place to put them. Whether that be on a computer, cloud, etc. is up to you. It can be as simply as connected the "old" phone to a PC, copy/paste the desired files. Then connect the "new" phone to PC, and drag/drop the files to the correct locations.
WiFi connections and passwords, I don't usually migrate. I don't have that many of them, so I literally just enter them in again, when migrating to a new phone. Titanium Backup (requires root) and some other apps can migrate such data (as well as apps and app data).
Click to expand...
Click to collapse
Thanks again.
That is largely what I was thinking/hoping.
I also hate bloatware, and wanted the DEV edition instead of a branded AT&T (or anyone else's) version.
Unrelated to this thread:
For what I do, I really like the M8, plus it is within my price range now that it is a few years old. Have you tried any of the custom Android 7 ROMs? If so, is there one you would recommend for the M8. I thought I would play around with the old phone and Nougat now that I have a good running phone again.
I love tinkering and challenges, so I am also going to try replacing the battery and charging port in the old phone. According to the couple YouTube videos I watched., it looks like it is well within the scope of my skill set.
Many thanks for your help with my M8, and any future help.
Dale
dale_j said:
Have you tried any of the custom Android 7 ROMs?
Click to expand...
Click to collapse
I haven't. I have been mostly a Sense user on this device, therefore it's stuck on Marshmallow.
There is a thread in the M8 General forum section, discussing ROM recommendations. You might check that out.