Develop Bugs

[Q] Factory Unlock HTC One M8 Softbrick HELP!

HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(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: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(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: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Have you flashed a custom recovery on the device? If yes, just try to restore a nandroid back from @Mr Hofs thread and your phone will be fine

Problem is, I don't think there is any nandroid backups available for his device LRA__001. First time I've seen that CID mentioned. Going by MID doesn't help much either, I think the Verizon has the same MID. Going by the "product: m8_wlv" it also indicates Verizon. I do see that he's on AT&T on his profile though but...
Being stuck on bootloader screen for 10minutes or more won't be surprising at all if he flashed a 2.xx.xxx.x firmware based custom ROM instead of a 1.xx.xxx.x version. Need to upgrade firmware in order to do that.
You don't happen to recall what version software your device ran?

Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.

fgarcia10 said:
Hi, I had the 2.7 TWRP recovery but found the 2.8.0.6 works better. I was able to flash PA ROM and it is working now. Plus now is rooted and S-off and super CID.
The phone has no branding and bought from amazon as unlock from factory. But is funny you mention Verizon has similar IDs because when I plug the phone to HTC sync the first splash screen shows Verizon wireless assistant and then go to the normal HTC one.
I tried the latest HD ROM and it was force closing a lot so I think the firmware is 1.... Something. I want to upgrade but don't know which one to get. Maybe I should look on the Verizon forum, thanks for letting me know that.
I spoke with developer support at HTC and they told me they will help restore to stock and escalated the call. I will let you know if they do help.
Thanks for the replies.
Click to expand...
Click to collapse
Honestly if its that much of a hassle, you should stick with something safe, Change the MID and CID to a Dev Edition/Europe, to do a full convert and you wont have to worry about the LRA_001. If you do those 2 steps the the OTA will be automatic as follows.
Else just flash a custom recovery, wipe data/cache and so and restore with one of the TWRP backups posted around here and you'll be good to go :good:

Cool I will try that. I did not know that.

fgarcia10 said:
Cool I will try that. I did not know that.
Click to expand...
Click to collapse
Don't forget though, best steps as follow, change MID, CID, restore via TWRP backup. If youre in Europe then change the MID to EUR, but the CID change it to super CID. Youve gotten past the hardest part which is the SOFF so everything is a breeze from there on out.
You won't lose your internal data if you do any of the following steps but dumping them on your SD card would be safe too.
I had an SG manufactured one, and the OTA came out pretty weird, was an unbranded one too. changed it to Dev/Unlocked MID and the super CID, downloaded the B_US002 TWRP dump thats posted here and restored that. Might want to download the OTA too aswell would save massive time after the first 159MB ota.

Awesome. Thanks!

was any one here ever able to get things working?
i am on LRA__001 and got my radio to stop working, no phone signals
contacted HTC dev and they provided me a zip, flashing that didn't help much, still no signals and can't boot into stock recovery.
seems like i've flashed the wrong hboot or something that's causing everything to be flashed on wrong partition addresses.
any help ?

fgarcia10 said:
HI,
I just bought an unlock htc m8 no branding any where. I unlocked the bootloader and flash a custom recovery but when I tried to root the phone something went wrong because I'm stuck on the boot screen and it would not go past it. I have been looking every where how to fix it, I don't have a nandroid back up and don't know which one to look for. Is there a way to restore it back to normal? I also tried flashing a custom rom but it gets stuck in the same place.
please help.
thanks.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 0.89.20.0328_3
(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: 99000429865069
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(bootloader) cidnum: LRA__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: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
hey
were you able to get it working ?
do you still have that phone?
i need some help

genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).

redpoint73 said:
This isn't the same issue as the OP. You flashed the wrong firmware which is much more serious. This thread isn't relevant to your issue, in addition to being over a year old (which also most likely won't help your issue).
Click to expand...
Click to collapse
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.

genious_t said:
I am just trying to trace ppl with the same variant so I can request them to dump couple of partitions for me. and there is no relevant thread for this particular variant, some says it s bluegrass some says its verizon variant, but according to HTCDev its actually rural area variant.
Click to expand...
Click to collapse
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).

redpoint73 said:
The LRA version is the LRA version. there's no question there. Its based on Verizon, but its not Verizon.
Sounds like you are trying to make up solutions. What you need is LRA firmware or RUU (RUU may not exist).
Click to expand...
Click to collapse
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
read bout the boot process and got to know that hboot reads IMEI and baseband while booting up and holds into some shared memory variables which later read by kernel.
just trying to figure out things and also looking for somebody who can provide dumps so i can try flashing them.

genious_t said:
i've got complete RUU from HTCDev to flash via hboot, did flash that but lost the IMEI and baseband version under settings > about, however the getvar all is still showing that information. so just trying to figure out what went wrong. either something is missing in what they have provided. or the hboot version is mismatching.
Click to expand...
Click to collapse
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.

redpoint73 said:
You flashed a hacked Verizon RUU. Its not the LRA RUU, and its also not an official RUU.
Click to expand...
Click to collapse
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head

genious_t said:
hey
were you able to get it working ?
do you still have that phone?
i need some help
Click to expand...
Click to collapse
I did get it to work again, HTC help me to get it back to stock. I still have the phone. They send me the files to restore it.

genious_t said:
No I explained them my case and they asked to couple of days time and then they provided a zip file to flash via hboot. They claimed that they have prepared this file especially for me. I flashed that file. It was 5.0.1 with almost all the images.
One thing that I doubt is that the hboot is not updated since the android-info.txt says hbootpreupdate=12 and my getvar says 11 so just wondering whether it was updated or not.
Also I dumped mmcblk0p3 (board-info) and I can see my IMEI there too.
Just don't know where to nock my head
Click to expand...
Click to collapse
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.

fgarcia10 said:
they send me the wrong files a couple of times. But they did get me the right one at the end. it seems you have the same problem I did. I still the hboot file and the system image. The hboot zip should be installed on download mode and the system image should be rename to OP6BIMG.zip and put in the sd card and re-start the phone in bootloader and let the zip install itself. It takes a long time but it worked. I have the files in my google drive I don't mind sharing it.
Click to expand...
Click to collapse
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?

genious_t said:
In my case they gave up, the guy said it can still be fixed but I don't know what to do.
Would you be able to share the stuff that worked for you ?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0Bw_sCYzL1RITbGkzRExWTmU1d1U/view?usp=sharing
https://drive.google.com/file/d/0Bw_sCYzL1RITN0ttSVBZZ3VUYkk/view?usp=sharing

Need help updating M8 to Marshmallow

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.

HTC one M8 [Custom ROM]/found what model it is

hi there,
I just get an htc one m8 wich is still in kitkat, but rooted and S-off !
can't do an OTA update, I think to install a custom rom (maximusHD) but before I begin, I want to be sure of what i'm doing, must do a nandroid backup and I don't know how
the other issue is that I dont know how to get the original CID, and on the lower back, I have "0P6B100" model but in the Hboot menu I have "m8 whl pvt ship", how to choose the good custom ROM or even to return to the stock one
help plz

epervier1983 said:
before I begin, I want to be sure of what i'm doing, must do a nandroid backup and I don't know how
Click to expand...
Click to collapse
Making a nandroid is normally quite easy, if you have TWRP (custom recovery) installed. Just boot into TWRP, and select the "Backup" option.
However, you have a lot of other considerations you need to look at, before you flash anything. See more below.
Also, if you aren't familiar with the basic processes (like making a nandroid) plus the device peculiarities of the M8; I'd highly recommend you do some more research and reading of the basic guides and threads here. I'd say minimum 1 hour, before trying anything, like flashing a ROM.
epervier1983 said:
the other issue is that I dont know how to get the original CID, and on the lower back, I have "0P6B100" model but in the Hboot menu I have "m8 whl pvt ship
Click to expand...
Click to collapse
First of all, you can not go by what is on the back cover. We've see a lot of refurbished, modified M8 phones, which have had their back cover replaced to remove carrier brand logos (particularly US carrier branded models). So in those cases (and it appears to be the case for you) the model number on the back cover is nor representative of the original model, or the internal components (which is the most important thing to go by).
You need to do fastboot getvar all, and post the results (delete IMEI and serial number before posting) before we can proceed, and definitely before you try any ROMs or other mods. We need more info about the device, before we can proceed safely.
Reason being, the product ID m8 whl indicates you probably have the US Sprint version. This model is fairly peculiar (and annoying) as it supports CDMA (in addition to GSM, LTE, etc.), and that makes it different from most other M8 versions. Trying to flash another versions stock RUU or firmware is in fact dangerous and can possibly permanently brick the phone.
Further, many custom ROMs which don't specifically support the Sprint version, will not boot. This is due to the fact that the Sprint version uses a different kernel from most other M8 models.
In addition, since your firmware appears to still be on KitKat, you will need to update it before flashing any custom ROMs (even ones that support Sprint version). Otherwise, the ROMs will have severe problems, like failure to boot, extreme long boot time, and broken WiFi.
So really, we need the getvar info before we can advise further, and definitely before you try to mess with anything.
Also, on the bootloader screen, does it say LOCKED, UNLOCKED or RELOCKED near the top. And is TWRP installed; and if so what version?

Hi, thanks for your response! Sorry about the delay,
But I finally returned the phone to sender, the big issue that I found it was a Sprint model and in my country I can't use 4G lte even I change Rom or something else like id number, and according to members it's not a good idea to try flashing it, the hardware is different, I can't unlock the LTE bands of my career (northern africa or Europe) even the flash work correctly,
But if u have some solutions it will be great, because the sender still searching help
The entire characteristics :
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.0119
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA44BS******
(bootloader) imei: 3520900********
(bootloader) imei2: Not Support
(bootloader) meid: 99000499******
(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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Thnx in advance

epervier1983 said:
But if u have some solutions it will be great, because the sender still searching help
(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
The seller is looking for solutions for what exactly?
The product name (m8_whl) as well as model number (0P6B70000) confirm that this is originally the Sprint version M8. The back cover has been swapped to remove the Sprint logo. And the phone was mad s-off and SuperCID (1111111) most likely to unlock the SIM.
Sprint RUUs will return the phone to stock ROM, plus update the firmware (radio, hboot, etc.), which the getvar data (version main = 3.30.651.2) identifies the firmware is extremely outdated, and still on KitKat.
https://forum.xda-developers.com/showthread.php?t=2729173
However, stock RUU may not be that desirable. Sprint stock ROM has a lot of bloat, Sprint carrier branding, and some things (WiFi hotspot/tethering) are probably disabled. Therefore, a custom ROM may be desirable. Custom ROMs which support the Sprint version M8 are recommended, since the Sprint version uses a different kernel from most other M8 versions: https://forum.xda-developers.com/sprint-htc-one-m8/development
However, the user will still probably want to update the firmware first. Otherwise, using current custom ROMs with outdated firmware, will cause a lot of serious problems: extreme slow boot or not boot, broken WiFi, audio issues, etc.
Again, the user is warned to NOT try RUUs or firmware.zip for other M8 versions (other than Sprint) as they are not compatible, and can cause permanent damage.
Also, you should delete the serial number from getvar data, as well as MEID. These are private info, which should not be posted online.

Hi ! Thnx a lot to take Time to respond, the seller wants to update android version at least, official or custom Rom doesn't matter, and sure keep WiFi and all features ok
For the 4G it's not possible because the smartphone doesn't support the 3b (1800) bands, so ..
I'll give him u r links and we'll see,
Ty

epervier1983 said:
the seller wants to update android version at least, official or custom Rom doesn't matter, and sure keep WiFi and all features ok
Click to expand...
Click to collapse
It might not matter to the seller, but it will make a big difference in your approach:
Stock/official Sprint RUU:
1) Flash Marshmallow Sprint firmware
2) Flash Sprint Marshmallow RUU
Custom ROM:
1) Flash Marshmallow Sprint firmware
2) Unlock bootloader (if not already unlocked)
3) Flash TWRP 3.1
4) Flash custom ROM (which support Sprint version M8)
Either of the above will result in WiFi working properly. But I'm not sure what you mean by "all features ok" as that statement is too vague. For instance, the official Sprint software most likely block WiFi hotspot/tethering. As blocking that feature is common on US variants.
epervier1983 said:
For the 4G it's not possible because the smartphone doesn't support the 3b (1800) bands, so ..
Click to expand...
Click to collapse
You might give the following threads a look/try (to enable the 1800 LTE band) - of course at your own risk. But unlocking bands on the Sprint version has mixed results (easier on the other "CDMA" version M8 - Verizon):
https://forum.xda-developers.com/htc-one-m8/general/how-to-convert-cdma-m8-sprint-vzw-gsm-t3303812
https://forum.xda-developers.com/htc-one-m8/general/unlock-bands-qualcomm-device-phone-t2880239

Sprint M8 Stock Roms

Hi, I made this post in the Sprint section a few days ago, but figured I'd post here as well to see if maybe this section has more traffic. If that's not allowed, I apologize in advance.
https://forum.xda-developers.com/sprint-htc-one-m8/help/stock-roms-t3669676
Basically, I'm looking for a stock rom for Sprint that would work with 1.54.651.8 firmware. All the links I can find on the forums seem to be dead.
Alternatively, a nandroid backup or way to extract the rom from the 1.54.651.8 RUU I do have (but won't successfully flash for whatever reason)
Any help would be appreciated. Thanks!

A custom ROM would need to support the Sprint M8, and be based on 4.4.2. Most any newer (newer than KitKat) ROMs will suffer major incompatibility with your ancient firmware, including extreme long boot time or no boot, and broken WiFi.
Suggest stocking with updating the firmware. Is the device s-on or s-off?
Problems with the RUU while "sending" are usually on the PC side. Try to re-install HTC drivers, try another USB port (USB 2.0 works best), and try another cable. Or even try another PC if possible.

Yeah I was able to find one custom 4.4.4 ROM (It was labelled 4.4.2, but it works so I guess it's close enough). There are just a few issues with it and I've always been more of a stock person anyway so I'd rather use a stock rom if I have the option.
As far as updating firmware, I am S-ON - I only originally rooted for a wifi hotspot app, so I didn't have a need to go S-OFF.
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site? I was willing to try it back when I had no rom at all, but now that I have a custom rom that mostly works, I'd rather not totally crap the bed.

Fuhcue said:
I guess it wouldn't hurt to give the RUUs a shot on a different computer. I'll just have to talk a friend into letting me install the drivers and giving it a go. One thing I'm not sure about - is it safe to go straight to the lastest RUU on HTC's site?
Click to expand...
Click to collapse
You can "skip" RUUs, and go the latest. However, you may (probably) need to update to the Marshmallow firmware anyway, before you can RUU. There is a strange limitation on most US version M8, where the RUU will fail with Error 155, if you try to go to Marshmallow from any former version (be it Kitkat or Lollipop) without first updating the firmware.
So the steps would be:
1) Relock bootloader
2) Flash to Marshmallow signed firmware (Sprint), in fastbootRUU mode
3) RUU to Marshmallow
4) Unlock bootloader again
5) Flash TWRP, root, and do whatever mods you want
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.

redpoint73 said:
Seeing as RUU will also wipe the phone. All this might be more than you want to do, if you are fairly happy with the phone as it is.
Click to expand...
Click to collapse
I don't so much mind the wipe, but I am a bit nervous about updating the firmware since that sounds like it could leave me in limbo if the RUU still didn't want to work for whatever reason. I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).

Fuhcue said:
I guess I'll search around for where I can get that firmware and the procedure of how to do it and see how comfortable I feel with it in case I go that route.
Click to expand...
Click to collapse
The firmware is posted in the same thread as the RUUs. And instructions on how to flash, as well.
https://forum.xda-developers.com/showthread.php?t=2729173
Fuhcue said:
If I knew for sure that it would all go through, I'd be fine with the reset. But that seems to take the attractive part of the RUU away in that it's no longer an "all in one" or one step process. (Not counting unlocking/relocking the bootloader since that's a quick and easy thing).
Click to expand...
Click to collapse
You can also opt for the Lollipop RUU (does not require flashing the firmware first). While not the latest, it's obviously more updated than what you presently have. And most of the current MM ROMs should work with LP firmware. There isn't much difference in the firmware it seems, for LP versus MM. Much different from KK to LP, which causes the problems I mentioned earlier (if you try to run KK firmware with LP or MM ROMs).
For maximum compatibility, matching the firmware is usually best. But I was running LP firmware with MM ROMs for a while (was simply to lazy to flash the MM firmware or RUU).

Ok so it sounds like the easiest option for me at this point is to grab a Lollipop RUU and try to flash it from a new computer with a fresh install of all the drivers. That way, at least if it fails to recognize my phone like the newest one did, I'll still be where I currently am with the stock (though outdated) firmware and custom rom.
Otherwise, I'll keep my fingers crossed that someone stumbles across this thread that has a meticulous archive of all old stock Sprint roms
Thanks so much for all your help and answering my questions so quickly. Much appreciated.

Hi
This is Sudheer from INDIA
i got Sprint HTC one M8 Harman Kardon from my friend.
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting. yesterday i am trying to install os from following reference.
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.

Krishna Sudheer said:
after jail break it's supported Indian GSM sims there after only outgoing calls are working incoming calls are not working.
Click to expand...
Click to collapse
"Jail break" is a term specific to only iPhones. There is not such thing as "jail break" on an Android device. I assume you mean s-off, or some other mod? I can only guess, if you don't use the specific and proper terminology.
Krishna Sudheer said:
after so much of web search i unlock boot loader using HTC All in one and i enter into twrp wipe all system,cache and data. now its' hang on startup white screen not booting.
Click to expand...
Click to collapse
All in one Toolkit is obsolete, you shouldn't be using it. It contains a very old version of TWRP which will cause problems for many folks.
System partition is the OS/ROM. Should be obvious, that wiping the system partition results in no OS. Can't boot to an OS that isn't there any more. If you didn't know what the result would be from wiping a partition, you should be touching it in the first place!!!! Those options are listed under "Advanced" for a reason. If you aren't an advanced user, don't mess with them, unless you are following directions form an experienced user, or know what the result is going to be.
Krishna Sudheer said:
forum.xda-developers.com/showthread.php?t=2729173
finally i got 155 error Unsupported RUU. Please help me to come out with step by step guide because i am new for installing android phones.
Click to expand...
Click to collapse
Not enough info to know why the RUU failed. You linked a post with multiple RUUs, so we don't know which one you tried. We also don't know your current phone configuration.
Which version number RUU did you try? For HK version, you typically will need to flash the one that contains the digits "654". The RUU with digits "651" is for non-HK Sprint version. Assuming CID/MID has not been modified (which we don't know, if you don't provide more info).
Post specific info about your phone. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
If the phone is s-on, you need to lock it in order to RUU. I don't know if you are s-on of s--off.
You can't run a lower number (downgrade) RUU unless you have s-off. Again, I don't know what version number RUU you tried, your current version number on the phone, or whether you are s-on or s-off.

Hi Sir,
Thank you for replying. Sim Unlocked from mobile store. actually I also don't know witch method they are using to unlock. After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
I tried to change CID and s-off but it's not working.
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot?
My mobile model is HTC one M8 HK (831C) Sprint Internal storage is 32GB.
I download and used to flash following files.
1. signed_6.20.654.3_firmware.zip
2.RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe
3.0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(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:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Kindly check and do the needful. Let me know how to install OS and where witch rom I use to install.

My responses below in red font:
Krishna Sudheer said:
After unlocking network signals showing in GSM mode. When I am changing to LTE mode again signals disappeared. In GSM mode incoming calls are not working. SMS both incoming and outgoing working fine.
LTE is difficult (maybe impossible) to get working in cases where the device is not intended for your region/carrier (which I assume is the case, that you are not located in US, on the Sprint carrier). GSM should work (as you indicated) as well as 3G (HSPA) provided that your carrier uses a band(s) supported by the Sprint version M8
I tried to change CID and s-off but it's not working. I don't know what that means "it's not working". Most folks who say they have trouble with getting s-off, are trying the hopeless waste of time, which is trying to usethe long obsolete "free" s-off method of firewater. It's never going to work.
Also, you should also be careful here, when changing CID. Only use a Sprint CID, or SuperCID with a Sprint firmware/RUU. Trying to use any other firmware or RUU will result in a radio brick (possibly permanent).
TWRP I used version v2.7.0.2 these recovery installed from all in one twrp (sprint). when i come back in to bootloader it will asking No OS installed are you sure you wish to reboot? That version is too old (over 4 years) and you should have used current TWRP. This was probably caused by using the toolkit (which I mentioned is not advised anymore). Old versions of TWRP was not compatible with Sprint M8 (it had it's own "CDMA" version TWRP) and it probably caused the wrong partition to be overwritten.
What was I do is
First Re-locked bootloader using with all in one and rename firmware as 0P6BIMG.ZIP then flash from SD Card Installed Successfully. Bootloader also showing OS version 6.20.654.3 Try flashing firmware again, the number should show up in getvar all (below) under "version-main". Flashing firmware twice is usually a good idea.
Next using exe file "RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_Harman_6.20.654.3.exe" everything going well when the process bar reaching to 100% then it's showing error 155. I Checked the error guide provide by exe file there Unsupported RUU please try again with supported RUU.
Error 155 is common, if flashing a US Marshmallow RUU, without being on the matching firmware. Flashing firmware again, as indicated above, may solve it.
Next using with ZIP file "0P6BIMG_Sprint_HTC_One_M8_Harman_6.20.654.3_RUU.zip" flash from SD Card it will showing not enough memory but internal is full empty.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: firmware number should appear here
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid:
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Click to expand...
Click to collapse

Two days of messing up with my M8, just getting worse, need help!!!

Two days of trying to find a solution here on xda and always banging my head in dead links and a load of information to try to understand I now have ended up with a hopefully not bricked device, I'm just stuck and need help.
This is the output of "fastboot getvar all" now.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA4A8SF00188
(bootloader) imei: 990004997721794
(bootloader) imei2: Not Support
(bootloader) meid: 99000499772179
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B20000
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
This is the different lines in the output of the "fastboot getvar all" before
Code:
version-baseband: 1.12.20.1211
version-main 4.21.512.4
commitno-bootloader: 205bdca3
What I did was flashing "unsigned_firmware_6.12.401.4" and to make that work I had to change one line inside the android-info.txt from modelid: 0P6B10000 to modelid: 0P6B20000.
I'm not shure when the trouble started, and after two days of testing I don't remember all I did or not. exactly but I started to try a couple of different roms and the trying to go back to backup made by twrp "twrp-3.1.1-0-m8" there was sudden restarts and twrp got errors with carrier partition, I changed to an older twrp and got that working for a while but ten suddenly I got other errors from /cash and /data partitions when trying to whipe with twrp, tried different twrp:s trying to flash other firmwares and other roms and kernels, I'm stuck.
Now If I install lineage os, 14. .... the installation finish but with errors, I can start the phone but it will restart then and then, and if i shut it down it will not be shut down after some minutes it starts again by it self.
IF i go back to the backed up stock that I got the phone with it will do exactly the same with reboots and not being able to shut down properly.
Android version 4.4.4
HTC Sense-version 6.0
Program version 3.31.512.2
HTC SDK API level 6.25
PRI-version not available
PRL--version not available
Kernel version 3.4.g3e2305b [email protected]#1 SMP PREeMPT
Basebandvesion not available
Versionnumber 3.31.512.2 CL39569 release-keyes.
he phone is only stable in bootloader and in twrp, the twrp for the moment is 2.8.0.
Excuse me for messing up, but what shall I do now?
My goal is a working LineageOS on the phone
Edited: Oh, I forgot to tell that I prefer to use Linux when working on the phone. Somewhere I have a rarely used win10 machine also if needed.

You have a peculiar version of the M8, which is know as LRA (a Verizon variant). This is one of the "CDMA" M8 variants, which supports the Verizon LRA CDMA network (in addition to GSM, HSPA, LTE) and it differs from most other M8 versions. Therefore you can NOT flash firmware from any other version M8, such as the Euro firmware currently installed. The radio is not compatible, results in a radio brick, and that is probably why you have carrier partition errors.
Try flashing the proper RUU for LRA, and only this one: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
I can't personally vouch for the above RUU. But I think others have verified it works on their LRA device. Hopefully, your phone boots after that, and the cell network functions. If so, you can install TWRP 3.1 (or at least 2.8.7) and a Verizon-compatible ROM. I don't know if Lineage qualifies, so I'll leave that up to you to research.

redpoint73 said:
You have a peculiar version of the M8, which is know as LRA (a Verizon variant). This is one of the "CDMA" M8 variants, which supports the Verizon LRA CDMA network (in addition to GSM, HSPA, LTE) and it differs from most other M8 versions. Therefore you can NOT flash firmware from any other version M8, such as the Euro firmware currently installed. The radio is not compatible, results in a radio brick, and that is probably why you have carrier partition errors.
Try flashing the proper RUU for LRA, and only this one: https://forum.xda-developers.com/showpost.php?p=66044439&postcount=37
I can't personally vouch for the above RUU. But I think others have verified it works on their LRA device. Hopefully, your phone boots after that, and the cell network functions. If so, you can install TWRP 3.1 (or at least 2.8.7) and a Verizon-compatible ROM. I don't know if Lineage qualifies, so I'll leave that up to you to research.
Click to expand...
Click to collapse
YEEEES thank you very much redpoint73, your answer led me to the solution. I got the phone back working
It didn't really work with the direct solution you pointed at (I don't know why), but after I red the whole thread RUU for bluegrass cellular variant I found a solution. There is a link to OTA
, I downloaded that, extracted the firmware from the zip and flashed it to my phone. Now it feel like new again. I'm not sure everything is back to normal but the version-baseband is back to where it started, the same with the version-main, but the bootloader? ie the commitno-bootloader is not changed back, will probably not only flashing firmware but so far i'ts working good. I just restored my lineageOS from previous backup.
I have wifi, radio and gps working and the lineageOS seams to work very well, maybe their version of M8 includes all versions?
Thank you again and again redpoint73

vildevilde said:
It didn't really work with the direct solution you pointed at (I don't know why), but after I red the whole thread, I downloaded that, extracted the firmware from the zip and flashed it to my phone. Now it feel like new again.
Click to expand...
Click to collapse
Not sure why the RUU didn't work, either. If the firmware from the OTA worked, the RUU should have worked. But RUU can be more finicky to things on the PC side, such as Windows version, if Visual C++ is installed, USB ports (2.0 vs. 3.0), etc. So nice job, working out a solution that worked.
vildevilde said:
I'm not sure everything is back to normal but the version-baseband is back to where it started, the same with the version-main, but the bootloader? ie the commitno-bootloader is not changed back,
Click to expand...
Click to collapse
The bootloader (3.19.0.0000) isn't different between LRA and Euro, or for that matter Lollipop versus Marshmallow. And since the firmware installed successfully, the bootloader would most likely match everything else installed by the firmware.zip (such as radio).
In other words, the bootloader number looks fine.
vildevilde said:
I just restored my lineageOS from previous backup.
I have wifi, radio and gps working and the lineageOS seams to work very well, maybe their version of M8 includes all versions?
Click to expand...
Click to collapse
I'm not a Lineage user on this device, so like I said before, I don't know either way whether it supports your LRA version M8.
If everything works on Lineage, I'd say it must support your LRA version device.

redpoint73 said:
Not sure why the RUU didn't work, either. If the firmware from the OTA worked, the RUU should have worked. But RUU can be more finicky to things on the PC side, such as Windows version, if Visual C++ is installed, USB ports (2.0 vs. 3.0), etc. So nice job, working out a solution that worked.
The bootloader (3.19.0.0000) isn't different between LRA and Euro, or for that matter Lollipop versus Marshmallow. And since the firmware installed successfully, the bootloader would most likely match everything else installed by the firmware.zip (such as radio).
In other words, the bootloader number looks fine.
I'm not a Lineage user on this device, so like I said before, I don't know either way whether it supports your LRA version M8.
If everything works on Lineage, I'd say it must support your LRA version device.
Click to expand...
Click to collapse
Yes, I'm using this as my daily phone now. Running LOS with microG support and everything works very good, easy updates every second day and no problems,