Related
Hi,
I know Rogers doesn't have an RUU for the M8, but when I had my M7, I was using an RUU that was for Brightstar (decrypted) and it worked great. It turned my M7 into a WWE Dev Edition with Sense and the OTAs worked. All i had to do was change my CID to BS_US001 and RUU away. I needed to install a LOT of OTAs afterwards but who doesn't like updating, right?!
Would anyone know what RUU I could use on my Rogers M8 that would be the equivalent of that? Doesn't need to be rogers specific, it could be a world wide edition, I'd bu happy with that. I think that AT&T is the US carrier that uses the same type of network so I'm not sure if there is an AT&T RUU out there. Searched XDA and Google and I haven't found an RUU that I am confident would work.
Thank you.
This is the closest thing I could find and it looks like it could work, but it's an EXE RUU, I've never used that before.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Nic2112 said:
This is the closest thing I could find and it looks like it could work, but it's an EXE RUU, I've never used that before.
http://forum.xda-developers.com/htc-one-m8/development/ruu-m8-developer-edition-sense-1-54-t2884777
Click to expand...
Click to collapse
All "official" RUUs are released as Windows .exe files. If you used something else before (RUU that was not an .exe), it was modified by a XDA user.
---------- Post added at 10:25 AM ---------- Previous post was at 10:18 AM ----------
Nic2112 said:
I think that AT&T is the US carrier that uses the same type of network so I'm not sure if there is an AT&T RUU out there. Searched XDA and Google and I haven't found an RUU that I am confident would work.
Click to expand...
Click to collapse
Latest AT&T RUU:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Modified bootable (no PC required) version:
http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
I think you are right, that Rogers uses a similar or same network to AT&T. Rogers was in fact partially owned by AT&T at one point. But you should confirm the network is the same. Be aware that the radio is included on the RUU, so if there are any network differences, using the wrong RUU can impact reception.
In particular, the international WWE firmware/radio is known to not work well in North America. Although you won't find an RUU for WWE anyway. For the most part, only US carriers have RUUs.
Other than that, the RUUs I linked are fine. You will need to change CID (or s-off may be necessary) otherwise it will install fine. Hardware on all GSM M8s (but not CDMA versions) are essentially the same aside from some cosmetic differences. The RUU you posted is also fine, as the US Dev Edition is designed to support AT&T's network (and likely also Rogers).
EDIT: Fixed the link to bootlable RUU above.
redpoint73 said:
Other than that, the RUUs I linked are fine. You will need to change CID (or s-off may be necessary) otherwise it will install fine. Hardware on all GSM M8s (but not CDMA versions) are essentially the same aside from some cosmetic differences. The RUU you posted is also fine, as the US Dev Edition is designed to support AT&T's network (and likely also Rogers).
Click to expand...
Click to collapse
That is great information, thank you very much. I'm S-OFF with GOOGL001 as CID, all I need to do is change it to one that matches the text file in the RUU, or I think BS_US001 will work.
Thanks again!
redpoint73 said:
Latest AT&T RUU:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Modified bootable (no PC required) version:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Click to expand...
Click to collapse
Did you mean to link to the same file twice?
Interesting, I have 3 EXE RUUs and they all have the same behavior, I click them ,the installer starts, I accept the agreement, and then it closes completely.
I would like to know the outcome as well. I did the GPE conversion and now want to go back to stock Rogers or the Developers Edition Sense but can't find a Rogers RUU and the Dev one is an exe.
Sent from my HTC One_M8 using Tapatalk
Elisha said:
I would like to know the outcome as well. I did the GPE conversion and now want to go back to stock Rogers or the Developers Edition Sense but can't find a Rogers RUU and the Dev one is an exe.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I managed to get the RUU to go further but it tells me it can't update my device. Maybe I put the wrong CID or have the wrong MID
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BS_US001
Try changing CID back to Rogers maybe?
Where did you get the RUU?
Sent from my HTC One_M8 using Tapatalk
Elisha said:
Try changing CID back to Rogers maybe?
Where did you get the RUU?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I don't remember what the original CID was. The RUU is the one from this thread.
You mean the Develepor edition one?
Elisha said:
You mean the Develepor edition one?
Click to expand...
Click to collapse
I tried both, none work. On my M7, I had a RUU in ZIP format and the CID I needed was BS_US001, but I tried that and BS_US002 and neither work.
Maybe my MID doesn't match but I don't know. It's easy with a ZIP, there is a text fire that tells you what it looks for but I never used an EXE before.
Nic2112 said:
I tried both, none work. On my M7, I had a RUU in ZIP format and the CID I needed was BS_US001, but I tried that and BS_US002 and neither work.
Maybe my MID doesn't match but I don't know. It's easy with a ZIP, there is a text fire that tells you what it looks for but I never used an EXE before.
Click to expand...
Click to collapse
That sucks. I kinda want to for back from Sense from my GPE conversion and can't find the proper RUU to flash via fastboot to get back to it.
The one linked in this thread is dead: http://forum.xda-developers.com/showthread.php?t=2733523
When I run the Dev RUU exe, it says do you want to update from a 2.X.X.X version to a 1.x.x.x. version which didn't make sense so I quit it.
Between the instructions here here, and then the HBOOT from here, the Brightstar RUU is installing.
I'll probably RUU back to GPE when it gets released for the HTC M8
Update: The Brightstar RUU worked but no APNs were discovered, had to configure one manually. Since Redpoint said that WWE editions don't work as well here, I'm giving the AT&T RUU a try right now. It's installing, I'm curious to see if it will set the Rogers APN automatically this time. It's also 4.4.3 instead of 4.4.0 so I might not need to download as many updates.
Update 2: AT&T is a bit worse, it's very AT&T flavored and seems even more out of place on Rogers. I think the only way would be to flash the HBOOT, then a custom recovery, restore a Rogers backup, set the CID and Recovery back to stock, and then factory reset.
I've decided to RUU back to GPE and stick to it. If L is released November 1st, it should be available as an OTA shortly after and I know that when that comes out, I'll want it so for a month's worth of usage, I'll stick to GPE.
Nic2112 said:
Did you mean to link to the same file twice?
Click to expand...
Click to collapse
Nope. My bad, bootable RUU is here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
---------- Post added at 12:01 PM ---------- Previous post was at 11:54 AM ----------
Nic2112 said:
Update 2: AT&T is a bit worse, it's very AT&T flavored and seems even more out of place on Rogers. I think the only way would be to flash the HBOOT, then a custom recovery, restore a Rogers backup, set the CID and Recovery back to stock, and then factory reset.
Click to expand...
Click to collapse
Yes, AT&T stock ROMs suck, with all the bloat and gimped features.
Really, if you decide you want a Sense experience, I would just recommend flashing a custom ROM of your choice and the radio that is friendly with your network.
The first link goes nowhere and the second one is one I was having trouble with as the 1.54.401.5-W_Splash.zip leads to a dead link as well.
Nic2112 said:
I don't remember what the original CID was. The RUU is the one from this thread.
Click to expand...
Click to collapse
ROGER001
Nic2112 said:
I managed to get the RUU to go further but it tells me it can't update my device. Maybe I put the wrong CID or have the wrong MID
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.12.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
Ok might be a bit outdate info seeing as you already decided to stick to GPE but yes the MID was wrong. MID for AT&T, Unlocked Version and Developer Edition are 0P6B12000 not 16000
BerndM14 said:
Ok might be a bit outdate info seeing as you already decided to stick to GPE but yes the MID was wrong. MID for AT&T, Unlocked Version and Developer Edition are 0P6B12000 not 16000
Click to expand...
Click to collapse
Thank you for the information. Since we might be a few short weeks from L, I figured no point in risking a brick at this time but I might change the MID anyways because I think the developer edition gets OTAs first.
Nic2112 said:
Thank you for the information. Since we might be a few short weeks from L, I figured no point in risking a brick at this time but I might change the MID anyways because I think the developer edition gets OTAs first.
Click to expand...
Click to collapse
Yeah they do, I also already downloaded all the necessary things to convert my device to a Developer Edition. :good:
Hello all,
I just got a refurbished M8 from China and after many hours reading tons of documents I am still struggling to figure out if it is a EU model as advertised or a US one.
On the back of the phone it says Model 0P6B100 but the MID (0P6B120), the model string M8_UL_CA and probably more important the IMEI point to an AT&T version. Now the OS/firmware seems to be the stock EU one (version 3.28.401.6), there is no AT&T logo or app anywhere.
Since you can pretty much change everything in software I'm not sure which of the above information I can really trust.
Is there any way to tell for sure if the device is EU or US?
If it is US is it by design limited to the US 4G bands or will using an EU firmware make it use all the EU bands?
I can post the full bootloader information if it helps.
Edit:
Forgot to mention: the CID came set to 11111111
Thanks
My responses below in red font:
Gnondpom said:
On the back of the phone it says Model 0P6B100
This means little. We've seen a lot of M8 devices that have had their back covers replaced; usually to remove the US carrier logos - which reinforces the notion that it was originally ATT. Its what is inside the phone that matters, so we need to go by the getvar data.
but the MID (0P6B120), the model string M8_UL_CA and probably more important the IMEI point to an AT&T version. Now the OS/firmware seems to be the stock EU one (version 3.28.401.6), there is no AT&T logo or app anywhere.
MID number is easy to change with s-off, but the product ID (M8_UL_CA) I've never seen changed, and is reliable to go by.
Likewise, OS number is easy to change with s-off. First can you confirm where you got the OS number, is it from the bootloader screen (which is the correct place to get it)? If so, former owner or the reseller probably flashed Euro 401 firmware/software in order to "convert" it to Euro, and remove all ATT branding, give it the proper Euro band support, etc.
Since you can pretty much change everything in software I'm not sure which of the above information I can really trust.
True that CID, MID and OS number can be changed. But as mentioned, I've never seen the product ID (M8_UL_CA in this case) changed. So that should be reliable to go by, making it the ATT version, or much less likely the US Developer's Edition.
Is there any way to tell for sure if the device is EU or US?
If it is US is it by design limited to the US 4G bands or will using an EU firmware make it use all the EU bands?
If the OS number you gave was taken from the bootloader screen, its already had Euro firmware flashed. Does it work on your carrier's LTE network currently?
I can post the full bootloader information if it helps. If you know how, do fastboot getvar all, and post the results (delete IMEI and serial numer before posting). But I'm pretty sure this is an ATT version that has been modified, and back cover replaced.
Is the phone s-off?
Click to expand...
Click to collapse
Thanks, I suspected that phone to be a US model with EU firmware.
Here's the getvars output:
(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.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Note about version-main: the phone came with 3.28.401.6 (same in bootloader and information from phone) but it refused to install OTA updates so I flashed a stock 3.28.401.7 after changing CID and MID to EU values. This allowed OTA to process all the way up to Lollipop and this is where problems started: the Apps store decided that the device is not compatibe with applications which I was able to install on KK without problems and the MM OTA does not show up when I check for updates.
I just got my nano SIM and initial tests shows the phone connecting to 4G but I have no clue which band it uses (any way to check???)... it also switches back and forth between 3G and 4G a bit too much for me but I am in a rural area so it might be normal. I will have to do some side by side comparison with my wife's Wiko which I know to be working fine.
Right now I'm in the middle of bringing the phone back into the state I received it, just have to flash to 3.28.401.6 firmware. Or would it make more sense to get a stock MM right away (I don't care about the data)?
Gnondpom said:
Note about version-main: the phone came with 3.28.401.6 (same in bootloader and information from phone) but it refused to install OTA updates so I flashed a stock 3.28.401.7 after changing CID and MID to EU values. This allowed OTA to process all the way up to Lollipop
Click to expand...
Click to collapse
Something is strange here. The MID isn't for Euro version now. It should be 0P6B10000.
And the fact its not, should prevent the Euro OTA from installing (possibly even from giving the update notification and downloading).
Further, if you did OTA update to Euro Lollipop, the main version would say 4.16.401.10 (or .13).
Something doesn't add up here. I think you did something wrong, or may have some of the steps confused.
Gnondpom said:
I just got my nano SIM and initial tests shows the phone connecting to 4G but I have no clue which band it uses (any way to check???)...
Click to expand...
Click to collapse
It would probably make the most sense to find out what LTE band(s) your carrier uses. From there, I can see if your firmware version supports that band(s).
Gnondpom said:
Right now I'm in the middle of bringing the phone back into the state I received it, just have to flash to 3.28.401.6 firmware. Or would it make more sense to get a stock MM right away (I don't care about the data)?
Click to expand...
Click to collapse
My recommendation would be to properly change to the Euro MID using this guide (is this how you changed the MID before?): http://forum.xda-developers.com/showthread.php?t=2708581
Then RUU to Marshmallow using this post: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
RUU will wipe the phone. But as you said, you don't care about that. And since you are having other issue (with Play store), the RUU may fix that.
RUU is a complete stock Euro image; re-writes every partition. Nice clean install, and the best way to update (as long as you don't mind the phone being wiped).
redpoint73 said:
Something is strange here. The MID isn't for Euro version now. It should be 0P6B10000.
Click to expand...
Click to collapse
This is because I started to bring the phone back to the weird "China config" having the AT&T MID with an Euro FW.
To get the OTA to work I did set it to 0P6B10000 with a CID of HTC__203 but seems there is an additional check somewhere which disabled the MM upgrade from showing up.
redpoint73 said:
Further, if you did OTA update to Euro Lollipop, the main version would say 4.16.401.10 (or .13).
Click to expand...
Click to collapse
Right, but as said I reverted back to KK for now due to the store issues in Lollipop.
redpoint73 said:
It would probably make the most sense to find out what LTE band(s) your carrier uses. From there, I can see if your firmware version supports that band(s).
Click to expand...
Click to collapse
700, 1800 and 2600 Mhz
Does your statement imply that the EU and US versions use the same hardware and that the used frequencies only dependent on the installed firmware?
Because at the end it all boils down to: can I use the phone reasonably well in Europe or should I ask for an exchange / refund.
redpoint73 said:
My recommendation would be to properly change to the Euro MID using this guide (is this how you changed the MID before?): http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Didn't use that guide but the same method
Do I need to change the CID as well to flash the RUU or can I leave it as is?
redpoint73 said:
Then RUU to Marshmallow using this post: http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
Ok, I will give it a try as soon as possible (likely over the week-end) and report back.
Gnondpom said:
This is because I started to bring the phone back to the weird "China config" having the AT&T MID with an Euro FW.
Click to expand...
Click to collapse
You should always describe all the exact steps, and what you have done to the device (in detail, be specific), in order for folks to help you. Otherwise, its really confusing. You want to make it easier for folks to help you, not harder!
Gnondpom said:
To get the OTA to work I did set it to 0P6B10000 with a CID of HTC__203 but seems there is an additional check somewhere which disabled the MM upgrade from showing up.
Click to expand...
Click to collapse
I've never seen such a check, and don't believe this assumption is correct. There are lots of glitches that can happen in the system, that can prevent an OTA. That is likely what happened.
Gnondpom said:
Right, but as said I reverted back to KK for now due to the store issues in Lollipop.
Click to expand...
Click to collapse
You did not state such a thing. The only mention I see of such a thing is the following:
Gnondpom said:
This allowed OTA to process all the way up to Lollipop and this is where problems started: the Apps store decided that the device is not compatibe with applications which I was able to install on KK without problems and the MM OTA does not show up when I check for updates.
Click to expand...
Click to collapse
Which to me does not say you downgraded to KK. And even if you said so, you'd have to be specific that you downgraded both the firmware and OS (by RUU? Or by flashing firmware.zip and a Kitkat TWRP backup?). Again, I'm just saying you should always try to provide the proper and complete details about what you have done, in order for us to help you. Otherwise, its confusing and makes it harder for us to help you. Already wasted time trying to figure out what you did, and asking you about it.
Gnondpom said:
Does your statement imply that the EU and US versions use the same hardware and that the used frequencies only dependent on the installed firmware?
Click to expand...
Click to collapse
That is correct. The hardware is the same in this case (ATT and EU) and the band support is set in radio baseband firmware. Meaning, if you have a Euro radio firmware installed, it should support the bands specified for the Euro version.
Gnondpom said:
700, 1800 and 2600 Mhz
Click to expand...
Click to collapse
Based on the specs here, the Euro firmware does not support LTE 700 MHz.
You may have better results with the Asia radio firmware, which supports all the LTE bands you stated. But that would be assuming its the 700 MHz LTE band that is being used in your area, and the missing support is what is causing the problem (which may or may not be true).
Gnondpom said:
Because at the end it all boils down to: can I use the phone reasonably well in Europe or should I ask for an exchange / refund.
Click to expand...
Click to collapse
Hard to say for certain, but again, you may flash the Asia radio, and see if that helps.
Gnondpom said:
Do I need to change the CID as well to flash the RUU or can I leave it as is?
Click to expand...
Click to collapse
SuperCID 11111111 is fine. SuperCID basically "passes" any CID check by the RUUs and OTAs, that is what makes it super!
I got an update from the factory but it wan't work tell i unroot my phone , how can i do that??
guys the problem is more then unroot the device if you have the time read the comments and post any help
thanks
"Themes and apps" is a really weird section to post your question in. I'll ask the mods to move it to "Q&A, Help" where it belongs.
To unroot, you need to restore a stock TWRP backup. Either one you made before rooting, or get one from here (and restore with the instructions):http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can relock the bootloader and RUU (RUU will wipe the phone).
redpoint73 said:
"Themes and apps" is a really weird section to post your question in. I'll ask the mods to move it to "Q&A, Help" where it belongs.
To unroot, you need to restore a stock TWRP backup. Either one you made before rooting, or get one from here (and restore with the instructions):http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Alternately, you can relock the bootloader and RUU (RUU will wipe the phone).
Click to expand...
Click to collapse
Sorry man it was a miss click , how can I move it to other section?
jonasess said:
how can I move it to other section?
Click to expand...
Click to collapse
You don't have the ability to move threads, after they are created. The mods can, and have already moved it to the right section (Q&A). It usually takes someone else to report the thread (which I did), and I don't think you can report your own thread.
But back to the topic at hand, I hope the info I posted was useful to you. Let us know if you have further questions.
redpoint73 said:
You don't have the ability to move threads, after they are created. The mods can, and have already moved it to the right section (Q&A). It usually takes someone else to report the thread (which I did), and I don't think you can report your own thread.
But back to the topic at hand, I hope the info I posted was useful to you. Let us know if you have further questions.
Click to expand...
Click to collapse
Thanks men but there is one thing , the bootloader is already locked I didn't unlock it before , so I was wondering whether I have to unlock the bootloader and install CM13 room or not doing that and unroot the phone because may be there is a chance that the company send an update for 6.0
I only have two questions
Is there is an official update to 6.0 from HTC company?
Or should I go with CM13
Also is there are any risks in bootloader unlock?
I successfully unlocked the bootloader in lg g2 mini before and it was very easy without any big risks
And now with HTC one m8 I don't know if it is the same or not.
My responses below in red font:
jonasess said:
the bootloader is already locked I didn't unlock it before
How did you root? Was it kingroot, or similar root app?
so I was wondering whether I have to unlock the bootloader and install CM13 room or not doing that and unroot the phone because may be there is a chance that the company send an update for 6.0
Is there is an official update to 6.0 from HTC company?
Android 6 came to this phone a really long time ago, about a year ago (Dec 2015) for most M8 versions. If you didn't get the update, it may due to being rooted, which typically prevents OTA update.
Alternately, depending on what version M8 you have, you can just RUU to Marshmallow (Android 6) without unrooting (although it will wipe all data on the phone). Do you know your phone's CID, or at least provide the OS number on the bootloader screen? From that, I can possibly tell you if there is an RUU.
Or should I go with CM13
You're talking about 2 completely different things, unrooting to OTA, or installing a custom ROM. I can't make that decision for you, you need to do it yourself.
Also is there are any risks in bootloader unlock? Not really. The bootloader can still be relocked, and you can restore to stock. I don't recall seeing any brick reports from unlocking the bootloader. The critical "brick" partitions (hboot and radio) aren't accessed by unlocking the bootloader, and any partitions that are accessed (system, recovery, etc.), can be easily rewritten/repaired if anything goes wrong.
Click to expand...
Click to collapse
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
It wasn't me because i got the phone from a friend , anyway the phone is rooted but the bootloader is locked because when i reboot to the bootloader mode i find it locked
about cid it's 11111111
OS-1.29.708.4
anyway how to unroot the phone , i'm going to try if it is possible to get the official 6.0 from the factory or not
if not i will unlock the bootloader and try to install ROM
so if it is possible i need the way how to unroot the phone and also how to unlock the bootloader
thanks
jonasess said:
anyway the phone is rooted but the bootloader is locked because when i reboot to the bootloader mode i find it locked
Click to expand...
Click to collapse
This doesn't tell me anything, you didn't already post before.
jonasess said:
about cid it's 11111111
OS-1.29.708.4
Click to expand...
Click to collapse
I don't recognize that OS version number. I Googled it, and I think you have the M7, not the M8.
redpoint73 said:
This doesn't tell me anything, you didn't already post before.
I don't recognize that OS version number. I Googled it, and I think you have the M7, not the M8.
Click to expand...
Click to collapse
i didn't get it , because there is a different between m8 and m7
m7 contain only one camera in the back
m8 contain 2 camera in the back
also the m7 doesn't support Card slot , m8 does
and a lot of other different
how could m8 phone contain an os of m7?
This all the information from bootloader mode
*** software status : official ***
*** locked ***
M8_UL_CA PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
[email protected]
openDSP-V47.2.2-00564-118974_F0.1024
OS-1.29.708.4
2MMC-boot 2048MB
mar 20 2015,03:01:11.90025771
Also when i use an app to get the information it gives the CID CWS_001
and the OS version is LRX22C
Also the app shows that the bootloader version is 3.19.0.0000
jonasess said:
This all the information from bootloader mode
*** software status : official ***
*** locked ***
M8_UL_CA PVT SHIP S-OFF
CID - 11111111
HBOOT-3.19.0.0000
[email protected]
openDSP-V47.2.2-00564-118974_F0.1024
OS-1.29.708.4
2MMC-boot 2048MB
mar 20 2015,03:01:11.90025771
Also when i use an app to get the information it gives the CID CWS_001
and the OS version is LRX22C
Also the app shows that the bootloader version is 3.19.0.0000
Click to expand...
Click to collapse
post the result of ( fastboot getvar all ) after removing seialno and imei
this output info will be useful to identify the right path you should take
and the info you already posted is a little mixed up NOT CORRECT
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
post the result of fastboot getvar all after removing seialno and imei
this output info will be useful to identify the right path you should take
and the info you already posted is a little mixed up NOT CORRECT
Click to expand...
Click to collapse
What should I do , where can I get these information? From an app or..?
jonasess said:
What should I do , where can I get these information? From an app or..?
Click to expand...
Click to collapse
*get a working adb&fastboot by going to this thread
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
after installing it with success
*reboot to fastboot and connect your device to pc
*open cmd window
* type ( fastboot getvar all ) and press enter
*post the result here after removing serialno and imei
Sent from my HTC M8 using XDA Labs
ahmed.ismael said:
*get a working adb&fastboot by going to this thread
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
after installing it with success
*reboot to fastboot and connect your device to pc
*open cmd window
* type ( fastboot getvar all ) and press enter
*post the result here after removing serialno and imei
Click to expand...
Click to collapse
Thank I will
This is all the informations
(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: 1.29.708.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.021s
This phone is a mess. Its the AT&T version (m8_ul_ca), but its been rooted, s-off, SuperCID, and some other firmware installed, or partially installed.
Reason I say "partially installed" is that the firmware number (version-main) 1.29.708.4 isn't one I recognize. But 1.xx main versions typically correspond to KitKat on this device. Which doesn't correspond to hboot 3.19 (which is for Lollipop or Marshmallow), nor the radio number [email protected] which is for AT&T Lollipop firmware.
You should re-baseline this device by RUU. But which RUU is the question. Since you have s-off and SuperCID, you run most RUUs.
The main version "708" corresponds to the Hong Kong version. Is that where you are located? What bands does your carrier use for 3G, and for LTE? These things will determine with RUU to use.
redpoint73 said:
This phone is a mess. Its the AT&T version (m8_ul_ca), but its been rooted, s-off, SuperCID, and some other firmware installed, or partially installed.
Reason I say "partially installed" is that the firmware number (version-main) 1.29.708.4 isn't one I recognize. But 1.xx main versions typically correspond to KitKat on this device. Which doesn't correspond to hboot 3.19 (which is for Lollipop or Marshmallow), nor the radio number [email protected] which is for AT&T Lollipop firmware.
You should re-baseline this device by RUU. But which RUU is the question. Since you have s-off and SuperCID, you run most RUUs.
The main version "708" corresponds to the Hong Kong version. Is that where you are located? What bands does your carrier use for 3G, and for LTE? These things will determine with RUU to use.
Click to expand...
Click to collapse
َAm not sure but i guess it's not AT&T version because i can use any SIM card i want , AT&T version use specific SIM card i guess !!
Any way i'm not from Hong Kong , i use MOBILS SIM card (From the company MOBILIS) for 3g and LTE .
Also i forgot to motion that when i go to software update i find that there is a system update (Software update :4.16.401.13 (57.45 MB)) when i download it , it wan't install because it says (We determine that your phone maybe running a modified version pf its system software . for your protection , we cannot update your phone . please revert your phone to the official htc system software to update your phone.
My responses below in red font:
jonasess said:
ÙŽAm not sure but i guess it's not AT&T version because i can use any SIM card i want , AT&T version use specific SIM card i guess !!
You shouldn't be "guessing' anything, and your guesses would be wrong, anyway. As I've already stated, the product ID m8_ul_ca means its US variant AT&T (that product ID also US Developer's Edition, but ATT is much more common). That much is an absolute fact, and not a guess on my part. Being SIM locked or not, has little bearing on what version you have. Any of these versions can be SIM unlocked with the proper code. So stop guessing at answers, as its not particularly useful.
I'll also guess that the back cover has been replaced. As the AT&T version has the AT&T "globe" logo on the back. We've seen a good number of devices "debranded" by having the back covers replaced to remove carrier logos. I'll guess it has a model/carrier number on the back cover, that also doesn't match any of the getvar info.
Any way i'm not from Hong Kong , i use MOBILS SIM card (From the company MOBILIS) for 3g and LTE .
None of this tells me anything useful. What country are you actually from? More importantly, what specific band (or bands) number does your carrier use for 3G, and what band(s) do they use for LTE?
Also i forgot to motion that when i go to software update i find that there is a system update (Software update :4.16.401.13 (57.45 MB)) when i download it , it wan't install because it says (We determine that your phone maybe running a modified version pf its system software . for your protection , we cannot update your phone . please revert your phone to the official htc system software to update your phone.
The carrier version of the OTA is Euro (401) so it won't install on a phone what has firmware for the Hong Kong version (708). Additionally, you have to install the OTAs sequentially, without skipping. So if you currently have 1.xx version, you can't skip 2.xx and 3.xx and go straight to 4.xx. In other words, there is no way you will get that OTA to install in your current configuration.
Which is why I am suggesting RUU. The RUUs do not need to be installed sequentially. Its a complete re-image, and it would also fix the mismatch you have between the main version (HK) and the hboot, radio (AT&T Lollipop).
Click to expand...
Click to collapse
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
I'm from Algeria , i guess my country is not supported from the HTC company .
Also as i said i use MOBILIS sim (http://www.mobilis.dz/) i didn't try the 3g or 4g because i use wifi to connect to the internet
Another qeustion : is that mean i can't unlock the bootloader and install the recovery to install CM rooms
In other word there is a risk for that?
++
thanks for the help
jonasess said:
Also as i said i use MOBILIS sim (http://www.mobilis.dz/) i didn't try the 3g or 4g because i use wifi to connect to the internet
Click to expand...
Click to collapse
Again, you are providing info that doesn't answer the questions I asked; and is not particularly useful. You didn't try 3G or 4G. So what? Does that mean you never want to use them, and will never use cell data? Or otherwise?
The following states that Mobilis uses 2100 MHz for 3g, but doesn't state info on 4G: http://www.worldtimezone.com/gsm.html
You can typically call your carrier, and get the answer to the question.
jonasess said:
Another qeustion : is that mean i can't unlock the bootloader and install the recovery to install CM rooms
In other word there is a risk for that?
Click to expand...
Click to collapse
You should be able to unlock the bootloader. But whether you can run any current ROMs is questionable.
Your firmware is a mess. The old firmware number 1.xx won't work with any current ROMs. You should fix your firmware first. But again, by RUU and I need more info before I can direct you to an RUU.
Also the version TWRP custom recovery you will need to flash custom ROMs, depend on what firmware version you have. And your firmware is all screwed up (seems to be partially modified) so again, its best you fix the firmware by RUU before proceeding with anything else.
I already have the mobile fully working perfectly but i want to upgrade to Android 7 and my current android version (Lollipop 5.1 -Sense 7) does not receive OTA updates so id like to install a new version of it so i can get them. Already tried to install the new Android 7 via the RUU (.exe) but i always got a non compatibility error.
It would be awesome if someone could redirect me to get immediately the Android 7 otherwise getting Android 6 which could receive updates after flashing it would be great too.
here are the fastboot getvar all results of my phone.
Thanks
C:\Users\Albi>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.708.27
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.016s
ALBI SHTYLLA said:
I already have the mobile fully working perfectly but i want to upgrade to Android 7 and my current android version (Lollipop 5.1 -Sense 7) does not receive OTA updates so id like to install a new version of it so i can get them. Already tried to install the new Android 7 via the RUU (.exe) but i always got a non compatibility error.
It would be awesome if someone could redirect me to get immediately the Android 7 otherwise getting Android 6 which could receive updates after flashing it would be great too.
here are the fastboot getvar all results of my phone.
Thanks
C:\Users\Albi>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 2.11.708.27
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_83.06.50709G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
all:
finished. total time: 0.016s
Click to expand...
Click to collapse
Your MID is wrong, if you want to use the Android 7(I suppose you are talking about Dev-Edition ruu) RUU.exe it should be mid: 0PJA11000
Have a look here ---> http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
Mat08.cc said:
Your MID is wrong, if you want to use the Android 7(I suppose you are talking about Dev-Edition ruu) RUU.exe it should be mid: 0PJA11000
Have a look here ---> http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
Click to expand...
Click to collapse
I downloaded and tried this one from the HTC website
http://www.htc.com/us/support/htc-one-m9/news/
In my case based on the link to direct me it means i have to change my mid right? Any safe source how to do that?
P.S. as i am aware until now there are many users worldwide reporting they have received the OTA update of the Android 7, i suppose that not all of them are using the DEV version!! Anyway my target is to get the Nougat in the safest way without risking to brick my device.
Thanks
ALBI SHTYLLA said:
I downloaded and tried this one from the HTC website
http://www.htc.com/us/support/htc-one-m9/news/
In my case based on the link to direct me it means i have to change my mid right? Any safe source how to do that?
P.S. as i am aware until now there are many users worldwide reporting they have received the OTA update of the Android 7, i suppose that not all of them are using the DEV version!! Anyway my target is to get the Nougat in the safest way without risking to brick my device.
Thanks
Click to expand...
Click to collapse
I'm pretty sure that only the dev-unlock htc m9 has received android 7.0, anyway the update you got from HTC is precisely for the dev-unlock edition (x.xx.617.xx).
If you want to flash that on your phone you'll need the MID I told you and there's no risk in changing it but you must be S-OFF otherwise you won't be able to do that!
ALBI SHTYLLA said:
Anyway my target is to get the Nougat in the safest way without risking to brick my device.
Thanks
Click to expand...
Click to collapse
Wait for your carrier to release an update.
Beamed in by telepathy.
shivadow said:
Wait for your carrier to release an update.
Beamed in by telepathy.
Click to expand...
Click to collapse
My device is unlocked without any carriers and doesn't recieve updates. Please read the thread explanation on top.
ALBI SHTYLLA said:
My device is unlocked without any carriers and doesn't recieve updates. Please read the thread explanation on top.
Click to expand...
Click to collapse
Your original post shows that you have SuperCID; that implies your phone is S-OFF - you can change your MID to register as any model you'd like.
To apply the Nougat RUU, your phone must identify as the developer model - currently your MID identifies your phone as the Europe WWE model. Mat08.cc is right: you'll need to change your MID to 0PJA11000 in order to apply the Nougat RUU.
(to answer your doubt - yes, the M9 Nougat update is only currently available for the developer edition)
Mat08.cc said:
I'm pretty sure that only the dev-unlock htc m9 has received android 7.0, anyway the update you got from HTC is precisely for the dev-unlock edition (x.xx.617.xx).
If you want to flash that on your phone you'll need the MID I told you and there's no risk in changing it but you must be S-OFF otherwise you won't be able to do that!
Click to expand...
Click to collapse
ok, i changed the mid to 0PJA11000 but still i cant install the ruu.exe, in every attempt i get the SIGNATURE ERROR notification.
Also i tried to flash the rom.zip from the link you sent me but looks like the zip file was corupted. (already tried downloading it 3 times just in case but still the same result)
computerslayer said:
Your original post shows that you have SuperCID; that implies your phone is S-OFF - you can change your MID to register as any model you'd like.
To apply the Nougat RUU, your phone must identify as the developer model - currently your MID identifies your phone as the Europe WWE model. Mat08.cc is right: you'll need to change your MID to 0PJA11000 in order to apply the Nougat RUU.
(to answer your doubt - yes, the M9 Nougat update is only currently available for the developer edition)
Click to expand...
Click to collapse
ok, i changed the mid to 0PJA11000 but still i cant install the ruu.exe, in every attempt i get the SIGNATURE ERROR notification.
Also i tried to flash the rom.zip from the link Mat08.cc sent me but looks like the zip file was corupted. (already tried downloading it 3 times just in case but still the same result)
ALBI SHTYLLA said:
ok, i changed the mid to 0PJA11000 but still i cant install the ruu.exe, in every attempt i get the SIGNATURE ERROR notification.
Also i tried to flash the rom.zip from the link you sent me but looks like the zip file was corupted. (already tried downloading it 3 times just in case but still the same result)
Click to expand...
Click to collapse
Forgive if I'm wrong your CID is cid: 11111111 right? change it to BS_US001 like in the guide I sent you last time (fastboot oem writecid BS_US001) and try again.
Super CID gave me errors in past so it might be the problem
EDIT: I mean try again the RUU.exe method
Mat08.cc said:
Forgive if I'm wrong your CID is cid: 11111111 right? change it to BS_US001 like in the guide I sent you last time (fastboot oem writecid BS_US001) and try again.
Super CID gave me errors in past so it might be the problem
EDIT: I mean try again the RUU.exe method
Click to expand...
Click to collapse
It past my mind to change the cid too so i did that like 30 seconds ago. And just when it saids checking header i get the same error again.
ALBI SHTYLLA said:
It past my mind to change the cid too so i did that like 30 seconds ago. And just when it saids checking header i get the same error again.
Click to expand...
Click to collapse
Which RUU are you trying to flash? 3.35.617.12 or 4.14.617.6 ??
Mat08.cc said:
Which RUU are you trying to flash? 3.35.617.12 or 4.14.617.6 ??
Click to expand...
Click to collapse
tried 4.14.617.6 now downloading 3.35.617.12
ALBI SHTYLLA said:
tried 4.14.617.6 now downloading 3.35.617.12
Click to expand...
Click to collapse
Ok, i'm asking because this happened to me also when I tried to flash the 4.14.617.6 over a 2.xxxx firmware. It's strange anyway because there shouldn't be any restrictions for us S-OFF users by the way try and see if it goes well.
Mat08.cc said:
Ok, i'm asking because this happened to me also when I tried to flash the 4.14.617.6 over a 2.xxxx firmware. It's strange anyway because there shouldn't be any restrictions for us S-OFF users by the way try and see if it goes well.
Click to expand...
Click to collapse
ok, i sucesfully installed the 3.35.617.12 and checked for updates but nothing!!!!!
ALBI SHTYLLA said:
ok, i sucesfully installed the 3.35.617.12 and checked for updates but nothing!!!!!
Click to expand...
Click to collapse
well no problem, you have the RUU right? just proceed with the 4.xx ruu.exe now it should work!
Mat08.cc said:
well no problem, you have the RUU right? just proceed with the 4.xx ruu.exe now it should work!
Click to expand...
Click to collapse
I checked again 30 min later for the updates and it finally started receiving them. It first did 3 system updates of M6 and the fourth was Nougat.
Im so excited, thank you very much for your help.
ALBI SHTYLLA said:
I checked again 30 min later for the updates and it finally started receiving them. It first did 3 system updates of M6 and the fourth was Nougat.
Im so excited, thank you very much for your help.
Click to expand...
Click to collapse
I'm glad to have helped! Have a nice day :highfive:
:highfive:
I'm having the same issue. Currently at 3.35 Dev edition firmware. MID and CID are correct. Signature error...
Hello friends!
My HTC10 is not rooted and is running on Nougat 7.0 with software version 2.42.651.66 and im not able to update it from the settings.
It is a Middle East unlocked device.
I tried going to SETTINGS-SYSTEM UPDATES-HTC SOFTWARE UPDATE
and then CHECK NOW
But it is only showing CHECKING for an infinite amount of time.
Tried this over wifi and on cellular data but still cant update.
I need a solution where i can update my ROM (STOCK ROM ONLY, DONT WANT TO ROOT) manually using an SD CARD only because my USB connector has got some issues.
Would really appreciate if someone can help.
That is weird i have unlocked OS with software number 2.41.401.41 and it is the latest update for MENA and EU, how did you update your phone ?
hejawi said:
That is weird i have unlocked OS with software number 2.41.401.41 and it is the latest update for MENA and EU, how did you update your phone ?
Click to expand...
Click to collapse
Why is that weird. It's locked to Sprint. Check the region number. When it's bought in the Middle East it's probably imported. There is more to find about this in the sprint section, it has its own subforum
Mr Hofs said:
Why is that weird. It's locked to Sprint. Check the region number. When it's bought in the Middle East it's probably imported. There is more to find about this in the sprint section, it has its own subforum
Click to expand...
Click to collapse
Do you mean that mine is a Sprint locked?? No... Im using it here in Middle East with the local service provider network. I have even factory restored it a few times...
tej835 said:
Do you mean that mine is a Sprint locked?? No... Im using it here in Middle East with the local service provider network. I have even factory restored it a few times...
Click to expand...
Click to collapse
Not sure what happened to your phone but it has a sprint version number?!
Mr Hofs said:
Not sure what happened to your phone but it has a sprint version number?!
Click to expand...
Click to collapse
Yes I just checked on the HTC website and the software version of my phone matches the Sprint details.
How do I change it to a Middle east version? Is it possible by flashing the ROM?? Which is the latest version of OS available on HTC10?? I have no issues with the network... I have factory reset it several times and yet my Local network is working. If it was locked to Sprint, it wouldnt have worked here on my Local Network.
I know this is an old thread now but I've just purchased a new htc 10 in the UK and it looks like I have the same issue as the op, (running what appears to be an unlocked Sprint phone running nougat on 2.42.651.66). Just wondering should I/is it safe to, update to Oreo via the ruu on the US htc support site, or I guess the other option would be to s-off, change mid and then flash leedroid or similar? I'm happy just running stock Oreo and don't 'want' to go down the route of s-off etc. Will I be safe enough to just flash the ruu?
Stevie1984 said:
I know this is an old thread now but I've just purchased a new htc 10 in the UK and it looks like I have the same issue as the op, (running what appears to be an unlocked Sprint phone running nougat on 2.42.651.66). Just wondering should I/is it safe to, update to Oreo via the ruu on the US htc support site, or I guess the other option would be to s-off, change mid and then flash leedroid or similar? I'm happy just running stock Oreo and don't 'want' to go down the route of s-off etc. Will I be safe enough to just flash the ruu?
Click to expand...
Click to collapse
Yes if the 651 part of the ruu matches and the first numbers are higher than 2.42 (like 3.16.651) you can flash it to get to oreo. After that you can stay stock or gain root, or flash a custom oreo or pie (los, aosp) roms.
Mr Hofs said:
Yes if the 651 part of the ruu matches and the first numbers are higher than 2.42 (like 3.16.651) you can flash it to get to oreo. After that you can stay stock or gain root, or flash a custom oreo or pie (los, aosp) roms.
Click to expand...
Click to collapse
Thanks for that. But now another quick question if you can help. Using a cid app via playstore it reports as a Sprint cid. I've since booted into fasboot/bootloader, it says *locked* but also says s-off. cid there shows cid.11111. I'm thinking this has been flashed with a Sprint ruu. Will I be safe enough to follow the steps to unlock the bootloader and just flash a wwe ruu do you think? I've flashed plenty of roms in the past and from what I remember cid. 11111 looks like supercid? In which case I can flash many different ruu's? Just really want to update to Oreo so would the Sprint ruu be the best option as you say? Then I can go on to whatever I want after that and just ignore the Sprint cid side of things?
Thanks in advance ?
Can you put the output here of "fastboot getvar all" minus the serial number and imei ?
And/or a picture of your download mode..... that way i can see more clearly what to be done.
Mr Hofs said:
Can you put the output here of "fastboot getvar all" minus the serial number and imei ?
And/or a picture of your download mode..... that way i can see more clearly what to be done.
Click to expand...
Click to collapse
Sure thing:
C:\ADB>fastboot getvar all
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61f000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:HT6*********
all:
Finished. Total time: 0.380s
C:\ADB>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: HT6*********
(bootloader) current-slot:
(bootloader) imei: *******************
(bootloader) version-main: 2.42.651.6
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: 11111111
all:
Finished. Total time: 0.061s
As far as i can tell you can safely flash the sprint oreo ruu, i don't think you need to unlock the BL because it's s-off (the flag "locked" is changed by sunshine s-off). You should be able to flash the ruu straight up.
Most easy is to get the nougat sprint ruu and flash that, then update via HTC OTA to oreo.
If you want to flash the oreo ruu you need to flash the oreo firnware first and then the ruu other wise the ruu won't flash.
Mr Hofs said:
As far as i can tell you can safely flash the sprint oreo ruu, i don't think you need to unlock the BL because it's s-off (the flag "locked" is changed by sunshine s-off). You should be able to flash the ruu straight up.
Most easy is to get the nougat sprint ruu and flash that, then update via HTC OTA to oreo.
If you want to flash the oreo ruu you need to flash the oreo firnware first and then the ruu other wise the ruu won't flash.
Click to expand...
Click to collapse
Just want to say thanks again for all your help man. Made some progress late last night. Oreo firmware flashed, Leedroid rom installed. All good....or so i thought...Realised i no longer have either a 3G or 4G data connection. If i put my sim in my old phone i pick up 4G fine. I also know for sure i did have 4G when it was on Nougat. (Why, 'o' why did i start this.....). In the Aroma installer im selecting WWE UHL build. Thought okay, maybe this is the issue. But if i try the sprint setting i then get stuck in a loop on the setup wizard with it trying to do "Handsfree activation". Im thinking maybe its a radio issue that somehow ive skipped/missed? Anyway im going to download the Nougat RUU and try going through the steps again, (if i can, from what ive read im not sure i can do that after flashing an oreo RUU). Any help suggestions you've got would be most welcome at this point mate.
Stevie1984 said:
Just want to say thanks again for all your help man. Made some progress late last night. Oreo firmware flashed, Leedroid rom installed. All good....or so i thought...Realised i no longer have either a 3G or 4G data connection. If i put my sim in my old phone i pick up 4G fine. I also know for sure i did have 4G when it was on Nougat. (Why, 'o' why did i start this.....). In the Aroma installer im selecting WWE UHL build. Thought okay, maybe this is the issue. But if i try the sprint setting i then get stuck in a loop on the setup wizard with it trying to do "Handsfree activation". Im thinking maybe its a radio issue that somehow ive skipped/missed? Anyway im going to download the Nougat RUU and try going through the steps again, (if i can, from what ive read im not sure i can do that after flashing an oreo RUU). Any help suggestions you've got would be most welcome at this point mate.
Click to expand...
Click to collapse
Did you try 4G on the stock oreo build, flash the stock oreo ruu and see if that helps. I think I've seen reports about this in the leedroid thread but never really followed it as i know nothing to little about sprint
Mr Hofs said:
As far as i can tell you can safely flash the sprint oreo ruu, i don't think you need to unlock the BL because it's s-off (the flag "locked" is changed by sunshine s-off). You should be able to flash the ruu straight up.
Most easy is to get the nougat sprint ruu and flash that, then update via HTC OTA to oreo.
If you want to flash the oreo ruu you need to flash the oreo firnware first and then the ruu other wise the ruu won't flash.
Click to expand...
Click to collapse
hi!
i'm exactly in the very same situation
but instead, i'd like to use the ruu you provided (the previous link redirects me to ebay)
i can't update to oreo, can i have some help?
cigarpill said:
hi!
i'm exactly in the very same situation
but instead, i'd like to use the ruu you provided (the previous link redirects me to ebay)
i can't update to oreo, can i have some help?
Click to expand...
Click to collapse
What previous link ? I checked this thread but didn't see that i posted a link ?
Mr Hofs said:
What previous link ? I checked this thread but didn't see that i posted a link ?
Click to expand...
Click to collapse
that's weird, maybe some kind of add the directed me to ebay
i'm looking for the oreo room, so it will be a pleasure if you tell me how to get it
i'm 2.42.651.66