Related
Need some help I am having a lot of bugs with my m8. It is on bluegrass cellular. Does anyone know what ruu I can use to restore to stock. I am s off and unlocked cid LRA__001 model I'd m8 wlv
Same here.
I too am in need of it so i can return back to stock.
Ameans4 said:
Need some help I am having a lot of bugs with my m8. It is on bluegrass cellular. Does anyone know what ruu I can use to restore to stock. I am s off and unlocked cid LRA__001 model I'd m8 wlv
Click to expand...
Click to collapse
If you have a stock backup, I have a stock recovery that should work for the LRA models, PM me. Since you're S-off you might take it to Bluegrass and ask them to flash it back to stock and start over again. S-off should stay after they've flashed.
I WOULD NOT use a Verizon or other LRA carrier RUU, since the radios and radio configurations are similar, but different enough that they will likely screw up your service.
durgis said:
If you have a stock backup, I have a stock recovery that should work for the LRA models, PM me. Since you're S-off you might take it to Bluegrass and ask them to flash it back to stock and start over again. S-off should stay after they've flashed.
I WOULD NOT use a Verizon or other LRA carrier RUU, since the radios and radio configurations are similar, but different enough that they will likely screw up your service.
Click to expand...
Click to collapse
hi,
can you help me with this i've messed up with my phone, didnt know its verizon, was assuming its GSM, but was unable to flash any custom rom except SkyDragon, so i thought its a firmware issue, got s-off and updated the firmware which caused radio to stop working, then figured out its verizon, flashed firmware from verizon as well but no luck, now i am not even able to flash any ROM, only AOSP or Verizon or SkyDragon intl boots the phone but then start rebooting every few minutes, radio not working so no calls no data, i am really stuck, there is not much help about this model, if there is a way to go back to stock i would like to go with that, any help would be appreciated.
attached is the screenshot of versions i had before when running fine.
following are the versions now
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.12.20.1211
version-cpld: None
version-microp: None
version-main: 4.17.605.5
version-misc: PVT SHIP S-OFF
serialno: xxxxxxxxxxxx
imei: xxxxxxxxxxxxxxx
imei2: Not Support
meid: xxxxxxxxxxxxxxxx
product: m8_wlv
platform: hTCBmsm8974
modelid: 0P6B17000
cidnum: GOOGL001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f2489bd1
hbootpreupdate: 11
gencheckpt: 0
Thanks
genious_t said:
version-bootloader: 3.19.0.0000
version-baseband: 1.12.20.1211
version-main: 4.17.605.5
version-misc: PVT SHIP S-OFF
modelid: 0P6B17000
cidnum: GOOGL001
Click to expand...
Click to collapse
I believe you installed wrong firmware which is a modded GPE firmware. That's why you can't install most of the ROM now.
You need to put correct CID/MID or at least change the CID to SuperCID 11111111 and MID 0P6B20000
It's not easy to fix your device now as you already installed some other region rcdata.img that come with the wrong firmware.
Anyway .. try again the correct Verizon firmware after change of CID/MID
You'll be able to install any Verizon based ROM but your data connection may still have problem.
Or better to install Verizon 4.4.4 firmware then restore LRA US 3.31.512.2 nandroid backup then do OTA if there is one. Restore the backup I believe you'll get wifi working .. after OTA .. your data connection should be restored.
Code:
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.changelist=395691
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
ro.build.characteristics=default
ro.build.project=M8_WL_K444_SENSE60_VZW_MR:395301
ro.build.sku=LRA US
ro.product.version=3.31.512.2
ro.build.languageremove=0
ro.build.sense.version=6.0
ro.build.version.htcsdk=HTCExt:HTCExtension_Sense60_443_4;SDK:6.25;hdkbase:19.2
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
ckpv5 said:
I believe you installed wrong firmware which is a modded GPE firmware. That's why you can't install most of the ROM now.
You need to put correct CID/MID or at least change the CID to SuperCID 11111111 and MID 0P6B20000
It's not easy to fix your device now as you already installed some other region rcdata.img that come with the wrong firmware.
Anyway .. try again the correct Verizon firmware after change of CID/MID
You'll be able to install any Verizon based ROM but your data connection may still have problem.
Or better to install Verizon 4.4.4 firmware then restore LRA US 3.31.512.2 nandroid backup then do OTA if there is one. Restore the backup I believe you'll get wifi working .. after OTA .. your data connection should be restored.
Code:
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.changelist=395691
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
ro.build.characteristics=default
ro.build.project=M8_WL_K444_SENSE60_VZW_MR:395301
ro.build.sku=LRA US
ro.product.version=3.31.512.2
ro.build.languageremove=0
ro.build.sense.version=6.0
ro.build.version.htcsdk=HTCExt:HTCExtension_Sense60_443_4;SDK:6.25;hdkbase:19.2
ro.build.description=3.31.512.2 CL395691 release-keys
ro.build.fingerprint=htc/lra_us/htc_m8wl:4.4.4/KTU84P/395691.2:user/release-keys
Click to expand...
Click to collapse
sorry about that MID and CID actually was planning to go GPE so changed them but then read the forum and couldn't find a single success story of wlv going GPE so changed my mind.
CID is now super and MID is my original as you mentioned 0P6B20000
the problem is that i am unable to find the correct firmware for my phone. i spent 48 hours searching for it but no luck.
and dont have nandroid as well.
btw couldn't understand the code you have sent.
can you please help me with finding the correct firmware and nandroid or whatever is needed to get this phone working regardless of the version. have no problem going to the older version as well.
Thanks
genious_t said:
sorry about that MID and CID actually was planning to go GPE so changed them but then read the forum and couldn't find a single success story of wlv going GPE so changed my mind.
CID is now super and MID is my original as you mentioned 0P6B20000
the problem is that i am unable to find the correct firmware for my phone. i spent 48 hours searching for it but no luck.
and dont have nandroid as well.
btw couldn't understand the code you have sent.
can you please help me with finding the correct firmware and nandroid or whatever is needed to get this phone working regardless of the version. have no problem going to the older version as well.
Thanks
Click to expand...
Click to collapse
This should work for you.
http://forum.xda-developers.com/showpost.php?p=63236967&postcount=2361
xunholyx said:
This should work for you.
http://forum.xda-developers.com/showpost.php?p=63236967&postcount=2361
Click to expand...
Click to collapse
Already tried this, didn't help
I am on GSM this is CDMA I guess
genious_t said:
Already tried this, didn't help
I am on GSM this is CDMA I guess
Click to expand...
Click to collapse
Didn't realize you were GSM since you are trying to flash verizon firmware with a phone that has the same MID and product version.
If your phone is GSM, you could try flashing WWE/International firmware (4.16.401.10). That's what I am using on a Telus phone. MID for WWE is 0P6B10000, Telus is 0P6B16000. It works great.
I didn't change the MID, just switched to superCID and flashed the firmware. Your product version may not let it install, but it might and it won't brick you. You'll just get errors if it won't work. My product version was M8_UL_CAN and it changed to M8_UL after flashing the WWE firmware, so it might be worth giving a shot.
genious_t said:
can you please help me with finding the correct firmware and nandroid or whatever is needed to get this phone working regardless of the version. have no problem going to the older version as well.
Thanks
Click to expand...
Click to collapse
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
ckpv5 said:
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
Click to expand...
Click to collapse
Thanks bro, trying this now
ckpv5 said:
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
Click to expand...
Click to collapse
Thanks mate, managed to restore the nandroid, still there are no signals, connected wifi and downloading OTA, phone restarted itself once during the download but resumed again, will update you about it.
Edit:
rebooted 2 more time dont know if it will let the OTA download.
ckpv5 said:
1. Install the 4.4.4 firmware that you can find here : http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
2. Restore the LRA_001 nandroid backup that you can find here : http://forum.xda-developers.com/showpost.php?p=58438595&postcount=14
Note : this nandroid is made with CWM and CMW recovery is included in the zip.
3. After restore, boot and check for OTA. You may not have data connection but you should have wifi connection.
4. After the OTA installation, you should get your data connection back.
Good Luck
Click to expand...
Click to collapse
Ok so here is the update,
After about a 100 reboots the OTA was successfully downloaded. But it won't let it flash, whenever I tried to flash it just rebooted, since the firmware didn't contain boot and recovery and I was on CWM I thought its recovery issue so flashed stok firmware and boot. It still didn't work, then flashed TWRP and tried to install OTA again, got some fingerprint error, please see the attached image.
When you restored the nandroid, do you restore the stock recovery included in the zip ?
OTA will install on stock recovery not CWM & not TWRP and not even on vzn stock recovery.
Do you still have the OTA.zip in internal storage/download folder ?
Copy that to PC, open it with 7-zip and extract out firmware.zip. Open firmware.zip and extract out the recovery.img
Flash this recovery.img. As your device is S-Off you can manually install OTA with stock recovery installed. Do you know how ? If not sure, ask .. will tell you how-to when I get to my PC. Not easy to write all these on mobile.
Or you can flash this extracted firmware.zip in ruu mode, you'll solve your data connection problem.
Then you can redo OTA installation process.
ckpv5 said:
When you restored the nandroid, do you restore the stock recovery included in the zip ?
OTA will install on stock recovery not CWM & not TWRP and not even on vzn stock recovery.
Do you still have the OTA.zip in internal storage/download folder ?
Copy that to PC, open it with 7-zip and extract out firmware.zip. Open firmware.zip and extract out the recovery.img
Flash this recovery.img. As your device is S-Off you can manually install OTA with stock recovery installed. Do you know how ? If not sure, ask .. will tell you how-to when I get to my PC. Not easy to write all these on mobile.
Or you can flash this extracted firmware.zip in ruu mode, you'll solve your data connection problem.
Then you can redo OTA installation process.
Click to expand...
Click to collapse
when i restored the nandroid it didn't restore the stock recovery, i flashed the stock recovery from the firmware.zip, the OTA is still in download folder, whenever i check for update it finds the existing file verifies it and prompt to install it, i did select to install it, its still just rebooting, after a couple of attempts it once booted into recovery but then without any progress it kept rebooting into recovery, after several reboots it booted again normally.
so now i have the stock recovery installed, should i rename the firmware.zip to 0P6B2000.zip and install it via hboot?
You flashed the stock recovery from which firmware.zip ? The one from VZN won't work. The one from the OTA zip will.
No .. that's wrong to rename firmware.zip to 0P6B2000.zip
Try this first :
firmware.zip is the one from OTA zip, not VZN
Put your device on bootloader/fastboot mode and connect to PC (you should see fastboot usb highlighted in red).
Put the firmware.zip in your fastboot folder. Open a command prompt from that folder.
type below command :
fastboot reboot-bootloader (to make sure you're on fastboot mode)
fastboot oem rebootRUU (to put the device in RUU mode)
fastboot flash zip firmware.zip (flashing the firmware.zip)
You'll see : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip (to complete firmware installation)
fastboot reboot-bootloader
Check your bootloader now written OS - 4.21.512.4
Now reboot (your data connection should work now) and redo OTA process
EDIT : can you upload that OTA zip to your GDrive or Dropbox and PM me the link. That will help many people.
ckpv5 said:
You flashed the stock recovery from which firmware.zip ? The one from VZN won't work. The one from the OTA zip will.
No .. that's wrong to rename firmware.zip to 0P6B2000.zip
Try this first :
firmware.zip is the one from OTA zip, not VZN
Put your device on bootloader/fastboot mode and connect to PC (you should see fastboot usb highlighted in red).
Put the firmware.zip in your fastboot folder. Open a command prompt from that folder.
type below command :
fastboot reboot-bootloader (to make sure you're on fastboot mode)
fastboot oem rebootRUU (to put the device in RUU mode)
fastboot flash zip firmware.zip (flashing the firmware.zip)
You'll see : FAILED (remote: 90 hboot pre-update! please flush image again immediately)
repeat fastboot flash zip firmware.zip (to complete firmware installation)
fastboot reboot-bootloader
Check your bootloader now written OS - 4.21.512.4
Now reboot (your data connection should work now) and redo OTA process
EDIT : can you upload that OTA zip to your GDrive or Dropbox and PM me the link. That will help many people.
Click to expand...
Click to collapse
ok i did flash the firmware in RUU mode, i can see the latest version in bootloader mode, then rebooted the phone but now its stuck in bootloop,.
managed to get to bootloader again by holding volum and power button while it was rebooting.
cant get to home screen.
yes i will upload the OTA and share the link.
Install CWM and restore the backup again ..
After you already boot and run setup ... copy the OTA zip to root of your internal storage, not in any folder.
boot to bootloader and install the stock recovery from that LRA firmware.zip
select hboot then recovery .. you'll get black screen or red triangle .. press & hold volume up button and press power once .. this will get you to stock recovery menu
select install from phone storage
select the OTA zip
install
reboot
ckpv5 said:
Install CWM and restore the backup again ..
After you already boot and run setup ... copy the OTA zip to root of your internal storage, not in any folder.
boot to bootloader and install the stock recovery from that LRA firmware.zip
select hboot then recovery .. you'll get black screen or red triangle .. press & hold volume up button and press power once .. this will get you to stock recovery menu
select install from phone storage
select the OTA zip
install
reboot
Click to expand...
Click to collapse
ok installed CWM, restored the nandroid, still rebooting and not signals.
flashed the stock recovery (the one from OTA) tried to install the OTA again, same problem rebooting again n again, managed to get into recovery once, but then stuck in boot loop on recovery, managed to get into bootloader by the volume and power button.
There's nothing much that I can offer to help. Your rebooting problem I believe due to motherboard cannot take the heat. I want to say this earlier but let you try all the possibilities first, you may have damaged motherboard that is why previously you have restarting problem when using your device.
Let your phone to cool down ... then try again. If still the same, need to send it to repair centre.
I tried to update my phone to 6.0 from 4.4.2 with ADB. Came with an error "System partition size error". It doesn't see the SD card when I tried to install from it.
My phone stuck at hboot screen. I can only access recovery and hboot menu. And when I tried to update to Lolipop with exe from a computer it says "Error 155: Unknown error". Xp 32 bit USB 2.0.
After I said reboot system through TWRP and it said No OS installed! .
But I have already installed ViperOne 3.2.1 Kitkat and Stock 4.4.4 before without any error still can't escape from boot menu. Any help would appreciate.
Here is some information:
S-OFF
Unlocked
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.2133156.UA24G
version-cpld: None
version-microp: None
version-main: 1.12.401.17
version-misc: PVT SHIP S-OFF
serialno: FA43CSF00379
imei: ***********
imei2: Not Support
meid: 99000499006617
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
And I think the device was T-Mobile 13000 at first but I'm not sure about it.
Did you update the firmware? I ran into a similar issue because my device shipped out with 4.4.2.
To update the firmware, you have to do the following:
Set your OEM's CID. Do not use SUPERCID.
My device was GPE, so [fastboot oem writecid GOOGL001]
Re-lock your Bootloader using Fastboot.
[fastboot oem lock ] then [fastboot reboot ruu]
You'll see the device logo centered onscreen.
Flash a firmware update file (does NOT have to be a whole ROM) and you'll be able to update to the threshold of that firmware.
I have Marshmallow firmware. So I can use MM or LP as well as KK ROMs now without bootloop.
Be sure to hit thanks if I helped! Be even more sure to PM me if you need help (like firmware files if you have the same variant).
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
My current firmware is: 3.28.401.9. Which one do you suggest to install? And I would really appreciate if you send me firmware files. I'm not sure which variant's firmware I should use.
Edit: By the way I can install roms but ruu.exe gives me error.
DreamGod said:
My current firmware is: 3.28.401.9.
Click to expand...
Click to collapse
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
furboom1240 said:
Did you update the firmware? I ran into a similar issue because my device shipped out with 4.4.2.
To update the firmware, you have to do the following:
Set your OEM's CID. Do not use SUPERCID.
My device was GPE, so [fastboot oem writecid GOOGL001]
Re-lock your Bootloader using Fastboot.
[fastboot oem lock ] then [fastboot reboot ruu]
You'll see the device logo centered onscreen.
Flash a firmware update file (does NOT have to be a whole ROM) and you'll be able to update to the threshold of that firmware.
I have Marshmallow firmware. So I can use MM or LP as well as KK ROMs now without bootloop.
Be sure to hit thanks if I helped! Be even more sure to PM me if you need help (like firmware files if you have the same variant).
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
He is S-Off. No need to relock the bootloader ever.
And for S-On users, the only time you will need to relock the bootloader is for running an RUU
Also, superCID will work with any firmware. No need to set the CID to his carrier's (not OEM's) CID
xunholyx said:
He is S-Off. No need to relock the bootloader ever.
And for S-On users, the only time you will need to relock the bootloader is for running an RUU
Click to expand...
Click to collapse
I thought so too. I'm also s-off but my firmware update stalled code 20 until I relocked the bootloader. But when I was finished I reversed that course [fastboot OEM unlock] and then dismissed the warning.
That's exactly what I did. Note that I mention RUU in my Fastboot instructions. :\
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
furboom1240 said:
I thought so too. I'm also s-off but my firmware update stalled code 20 until I relocked the bootloader. But when I was finished I reversed that course [fastboot OEM unlock] and then dismissed the warning.
That's exactly what I did. Note that I mention RUU in my Fastboot instructions. :\
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
Error 20? Never heard of that one, no idea what it is.
ckpv5 said:
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
Click to expand...
Click to collapse
Thank you I will try and tell the results. I though that my device was GSM didn't even know that it was Sprint. I was totally wrong at first then.
xunholyx said:
Error 20? Never heard of that one, no idea what it is.
Click to expand...
Click to collapse
Something I got in the Fastboot.
You open a command window and reference the file.
You either get a OKAY (milliseconds taken) or FAILED (error##). Some errors are obvious, like the cable disconnected, your recovery is out of date, update your SDK.
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
furboom1240 said:
Something I got in the Fastboot.
You open a command window and reference the file.
You either get a OKAY (milliseconds taken) or FAILED (error##). Some errors are obvious, like the cable disconnected, your recovery is out of date, update your SDK.
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
Yeah, I know what the error codes are. LOL! I'm far from new at this.
I just haven't heard of error 20
xunholyx said:
Yeah, I know what the error codes are. LOL! I'm far from new at this.
I just haven't heard of error 20
Click to expand...
Click to collapse
Sometimes remembering this stuff makes my head hurt. I often went to webchat to diagnose issues or find similarities.
Sometimes it's how I word a problem, the other time its the problem itself that throws off a bit... ?
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
ckpv5 said:
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
Click to expand...
Click to collapse
Hello, it's me again. I'm trying to change my model-id but it shows like that:
P6B7\ (enter)
0000
My device won't open (only hboot and fastboot, no recovery) so I'm not sure how I can use adb since it doesn't show my device and its serial number. I appreciate your help...
DreamGod said:
Hello, it's me again. I'm trying to change my model-id but it shows like that:
P6B7\ (enter)
0000
My device won't open (only hboot and fastboot, no recovery) so I'm not sure how I can use adb since it doesn't show my device and its serial number. I appreciate your help...
Click to expand...
Click to collapse
How did you do that ? You wrote the code on your own instead of copy paste the whole code ? I don't know whether can fix that ... let's try again.
1. You need to install the old version TWRP recovery as your current hboot is 3.16.0.0000
install TWRP 2.8.1.0 - https://dl.twrp.me/m8/
2. After TWRP 2.8.1.0 installed, boot to recovery
mount - system
3. connect to PC and open a command prompt from your fastboot/adb folder then run command
adb shell
then this code (copy and paste .. don't write them on command prompt on your own)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
on recovery select reboot - bootloader
then run command fastboot getvar mid - you should have 0P6B70000 now (hopefully)
ckpv5 said:
How did you do that ? You wrote the code on your own instead of copy paste the whole code ? I don't know whether can fix that ... let's try again.
1. You need to install the old version TWRP recovery as your current hboot is 3.16.0.0000
install TWRP 2.8.1.0 - https://dl.twrp.me/m8/
2. After TWRP 2.8.1.0 installed, boot to recovery
mount - system
3. connect to PC and open a command prompt from your fastboot/adb folder then run command
adb shell
then this code (copy and paste .. don't write them on command prompt on your own)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
on recovery select reboot - bootloader
then run command fastboot getvar mid - you should have 0P6B70000 now (hopefully)
Click to expand...
Click to collapse
Firstly I want to thank you with your help I've changed model-id.
Then I installed this firmware: https://www.androidfilehost.com/?fid=24391638059059188
and the screen was like that: http://hizliresim.com/4lZjAL
I've succeeded to open boot menu. Then I tried to install this version: https://www.androidfilehost.com/?fid=24052804347796593
but sd card gave me "wrong zippe image!". When I tried to install with .exe it gave me "Error: 155 Unknown error". Couldn't install with command either. I think something is wrong with firmware or rom. By the way there's a text "OP6B100x" behind my phone. Are we sure about the variant of my phone? I'm not even sure which firmware and rom I should install. I appreciate all your help.
DreamGod said:
Firstly I want to thank you with your help I've changed model-id.
Then I installed this firmware: https://www.androidfilehost.com/?fid=24391638059059188
and the screen was like that: http://hizliresim.com/4lZjAL
I've succeeded to open boot menu. Then I tried to install this version: https://www.androidfilehost.com/?fid=24052804347796593
but sd card gave me "wrong zippe image!". When I tried to install with .exe it gave me "Error: 155 Unknown error". Couldn't install with command either. I think something is wrong with firmware or rom. By the way there's a text "OP6B100x" behind my phone. Are we sure about the variant of my phone? I'm not even sure which firmware and rom I should install. I appreciate all your help.
Click to expand...
Click to collapse
Text "OP6B100x" behind your phone most probably due to change of back cover.
Your getvar on post #1 clearly shown it is Sprint
meid: 99000499006617
product: m8_whl
where the "OP6B100x" should read
meid: 00000000000000
product: m8_ul
After you installed 6.20.651.3_full_firmware.zip, you should run the 6.20.651.3 RUU.exe (you should not get error 155)
but instead, you tried a lower version RUU.zip which require a htc_fastboot to flash it. I don't know what you meant by "sd card gave me "wrong zippe image!"". Was it you tried with external_sd method ?
about the screen that you get .. I don't know for sure .. maybe it's because your ROM version is wrong for the firmware that newly installed ... and maybe (the one that I'm always scare of) .. you previously installed GSM firmware 1.12.401.17 on a CDMA device which may altered some of your system partition tables.
That's why there's a big warning here : http://forum.xda-developers.com/showpost.php?p=51700638&postcount=2
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).
Can you post current fastboot getvar all result after you made all these changes ? You may need to reflash the 6.20.651.3 and run 6.20.651.3 RUU.exe after the firmware installed.
ckpv5 said:
Text "OP6B100x" behind your phone most probably due to change of back cover.
Your getvar on post #1 clearly shown it is Sprint
meid: 99000499006617
product: m8_whl
where the "OP6B100x" should read
meid: 00000000000000
product: m8_ul
After you installed 6.20.651.3_full_firmware.zip, you should run the 6.20.651.3 RUU.exe (you should not get error 155)
but instead, you tried a lower version RUU.zip which require a htc_fastboot to flash it. I don't know what you meant by "sd card gave me "wrong zippe image!"". Was it you tried with external_sd method ?
about the screen that you get .. I don't know for sure .. maybe it's because your ROM version is wrong for the firmware that newly installed ... and maybe (the one that I'm always scare of) .. you previously installed GSM firmware 1.12.401.17 on a CDMA device which may altered some of your system partition tables.
That's why there's a big warning here : http://forum.xda-developers.com/showpost.php?p=51700638&postcount=2
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).
Can you post current fastboot getvar all result after you made all these changes ? You may need to reflash the 6.20.651.3 and run 6.20.651.3 RUU.exe after the firmware installed.
Click to expand...
Click to collapse
After I installed Marshmallow, I can open phone now. Thank you for your all help.
Oh, thanks
Hi everyone, I have an international HTC M9 with S-Off, unlocked bootloader and Maximus 7.1.0 ROM
I was following the steps by @clsA here --> http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
to convert my phone to the dev edition but I have some questions regarding the requisites:
1. my phone has product: htc_himauhl instead of product: htc_himaulatt
2. my version-main is : x.xx.771.x instead of version-main: x.xx.617.x
for the rest i have changed the cid and mid to the one requested (BS_US002, 0PJA11000) so the question is, can I flash the provided RUU.zip with the sdcard method? even if the version I'm going to get is an older android version (lollipop 5.x)?
EDIT: I've seen that there's also the MM6.x RUU.zip so my only question now is if the product and version-main mismatch isn't a problem
Mat08.cc said:
Hi everyone, I have an international HTC M9 with S-Off, unlocked bootloader and Maximus 7.1.0 ROM
I was following the steps by @clsA here --> http://forum.xda-developers.com/showpost.php?p=64451344&postcount=123
to convert my phone to the dev edition but I have some questions regarding the requisites:
1. my phone has product: htc_himauhl instead of product: htc_himaulatt
2. my version-main is : x.xx.771.x instead of version-main: x.xx.617.x
for the rest i have changed the cid and mid to the one requested (BS_US002, 0PJA11000) so the question is, can I flash the provided RUU.zip with the sdcard method? even if the version I'm going to get is an older android version (lollipop 5.x)?
Click to expand...
Click to collapse
Try It but backup all your data.
When you flash the RUU.zip/Rom.zip with fastboot it will warn you and wount flash if you have not all prerequirering stuff Cid / Mid / wrong Version..
I have also convertetd my One M9 International to Nougat Android 7 with the "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" and after that i get the Update via OTA.
But I extracted the Rom.exe from The "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" because i want to flash with fastboot.
When you start the RUU.exe you will get an folder under "C:\Users\##YOURUSERMANE##\AppData\Local\Temp\{0B0B715F-DFF0-448D-819F-C0706246382E}" there you can find the Rom.zip copy it to your fastboot directory and flash it with fastboot.
Befor I had Viper Rom 5.3 on my One M9
At first i have bootet to Download / Bootloader Mode
Than with fastboot: "fastboot oem writemid 0PJA11000" (For Dev Edition)
And Than "fastboot oem writecid BS_US001" (For Dev Edition)
and reboot: "fastboot reboot"
Now I flashed the Ruu / Rom Zip via fastboot
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip (ore Rom.zip original name)
htc_fastboot reboot
After ist is ready you can go to "Settings >Info>SoftwareUpdate" and you will recive the new Nougat Update.
Atention:
After that Update i hav booted to Download mode again and set old cid / mid again.
But i you want stay on Dev Edition an get OTAs you can leav your CID / MID as DEV otherwise you can run in trubble
" fastboot oem writemid 0PJA10000"
and for supercid
"fastboot oem writecid 11111111"
and reboot: "fastboot reboot"
Now hav fun with you dev Phone
niceguy0815 said:
Try It but backup all your data.
When you flash the RUU.zip/Rom.zip with fastboot it will warn you and wount flash if you have not all prerequirering stuff Cid / Mid / wrong Version..
I have also convertetd my One M9 International to Nougat Android 7 with the "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" and after that i get the Update via OTA.
But I extracted the Rom.exe from The "RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe" because i want to flash with fastboot.
When you start the RUU.exe you will get an folder under "C:\Users\##YOURUSERMANE##\AppData\Local\Temp\{0B0B715F-DFF0-448D-819F-C0706246382E}" there you can find the Rom.zip copy it to your fastboot directory and flash it with fastboot.
Befor I had Viper Rom 5.3 on my One M9
At first i have bootet to Download / Bootloader Mode
Than with fastboot: "fastboot oem writemid 0PJA11000" (For Dev Edition)
And Than "fastboot oem writecid BS_US001" (For Dev Edition)
and reboot: "fastboot reboot"
Now I flashed the Ruu / Rom Zip via fastboot
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip (ore Rom.zip original name)
htc_fastboot reboot
After ist is ready you can go to "Settings >Info>SoftwareUpdate" and you will recive the new Nougat Update.
After that Update i hav booted to Download mode again and set old cid / mid again.
" fastboot oem writemid 0PJA10000"
and for supercid
"fastboot oem writecid 11111111"
and reboot: "fastboot reboot"
Now hav fun with you dev Phone
Click to expand...
Click to collapse
Thank you mate, you've been very clear! Let me ask you one more thing, the dev edition rom has multilanguage? and the red-text warning is gone?
multilanguage yes I use german and the red-text warning is not gone.
niceguy0815 said:
multilanguage yes I use german and the red-text warning is not gone.
Click to expand...
Click to collapse
Thanks man, I successfully upgraded to android 7 your help has been really appreciated! :good:
niceguy0815 said:
After that Update i hav booted to Download mode again and set old cid / mid again.
" fastboot oem writemid 0PJA10000"
and for supercid
"fastboot oem writecid 11111111"
Click to expand...
Click to collapse
That's no good idea. If you changed your sku to the 617 one you should stick to the corresponding MID. Besides the SCID has no benefit on the M9 since it won't make your phone ignore mismatches between the current MID and the MID of RUUs like it did on older HTC phones. It even prevents you from being able to install OTAs. Therefore it might be a better choice to keep the dev edition CID, as well.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
That's no good idea. If you changed your sku to the 617 one you should stick to the corresponding MID. Besides the SCID has no benefit on the M9 since it won't make your phone ignore mismatches between the current MID and the MID of RUUs like it did on older HTC phones. It even prevents you from being able to install OTAs. Therefore it might be a better choice to keep the dev edition CID, as well.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Yes you are right!
But for me ..I think there is no OTA in near futer and when came the normal cusom Rom for Nougat I must not remember to get the original CID / MID back again
I can understand that decision. (I'd probably have done the same.)
However I added that warning because you linked those instructions in another thread. Others might run into problems if they do those steps and aren't aware of the "risks" that might follow...
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
I can understand that decision. (I'd probably have done the same.)
However I added that warning because you linked those instructions in another thread. Others might run into problems if they do those steps and aren't aware of the "risks" that might follow...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Hi Flippy498, I'm sorry to bother you but although I have read everything about firmwares, roms, etc (even those in your signature).. I haven't found an answer about the following problem: I want to go back to full stock and remove the red-text warnings so, since I have S-OFF and as I've read on "The Difference between Rom & Firmware" doc there's no problem in going back to an older firmware, I downloaded the 3.35.401.12 - RUU ZIP from SoLdieR9312's thread (http://forum.xda-developers.com/one-m9/development/ota-1-32-401-15-firmware-noredtext-t3072571) and changed MID and CID to those requested. Now before flashing the RUU.zip with the sdcard method my question is, to remove red-text warnings which file I have to flash (3.35.401.12 - Stock Firmware - 3.35.401.12 - Firmware NoRedText - 3.35.401.12 - NoRedText ABOOT only)? and this has to be done before or after flashing RUU.zip?
EDIT: I've also locked the bootloader
If your phone is completely stock then the red text won't appear. So just flash the RUU.
Edit: (I know that this is a stupid question.) You are aware of the fact that the 401 firmware isn't the same as the one your phone got originally delivered with, aren't you? You could've sticked with the dev edition firmware instead of changing to the 401 one. They're in most parts the same. The only difference is that 401 has no android n at the moment.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
If your phone is completely stock then the red text won't appear. So just flash the RUU.
Edit: (I know that this is a stupid question.) You are aware of the fact that the 401 firmware isn't the same as the one your phone got originally delivered with, aren't you? You could've sticked with the dev edition firmware instead of changing to the 401 one. They're in most parts the same. The only difference is that 401 has no android n at the moment.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
I'm aware but flashing the dev-edition with the RUU.exe method didn't resolve the red-text issue so I thought that going back to 401 firmware and do all that process could fix that! Now i'm wondering if the ruu.exe method is the problem, i mean if i flash the dev-edition ruu.zip via sdcard it won't fix the redtext warnings anyway right?
I've never used an exe with the M9. I do know that the SD card method resets the modified status whereas I've read that the exe doesn't. So it might be worth a try.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
I've never used an exe with the M9. I do know that the SD card method resets the modified status whereas I've read that the exe doesn't. So it might be worth a try.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
With the 401 ruu.zip it gives me 12 RUU ZIP error I searched it and found Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
So I believe it might be necessary to flash before one of those "firmwares.zip" from SoLdieR9312's thread but it's strange since my phone is S-OFF
If I remember correctly, error 12 indicates that you don't have the correct CID if it appears during a SD card flash.
Edit: Unless it contains "combined" in its name every RUU (no matter whether zip or exe) is signed.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
If I remember correctly, error 12 indicates that you don't have the correct CID if it appears during a SD card flash.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok, tomorrow I'll have a look at all this again.. you've been even too patient with me! thanks alot for your help! :good:
It looks like there is some kind of problem with the RUU.zip file. Coolberry mentioned that in another thread. (I'm assuming you tried to use his file.)
Edit: I know this post is a bit older and written in the section of a different HTC model. However you could still use its instructions to extract the RUU.zip from the RUU.exe by yourself. The rom.zip is what we call RUU.zip nowadays. Please post any questions that may arise in this thread.
Sent from my HTC One S using XDA Labs
Flippy498 said:
It looks like there is some kind of problem with the RUU.zip file. Coolberry mentioned that in another thread. (I'm assuming you tried to use his file.)
Edit: I know this post is a bit older and written in the section of a different HTC model. However you could still use its instructions to extract the RUU.zip from the RUU.exe by yourself. The rom.zip is what we call RUU.zip nowadays. Please post any questions that may arise in this thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
So i tried another rom.zip from your collection in a google doc page and got the same error (12_RU). Now i'm going to try with the extraction from ruu.exe, I got the wwe lollipop ruu.exe (the only one i found for wwe) and the dev-edition ruu.exe.. let's see if i can get this to work
p.s. I've noticed that i can't copy the rom.zip file directly to my m9 but i have to put the sd card inside the pc, anyway on the google doc is written that this is common so i don't think that's the problem
Mat08.cc said:
So i tried another rom.zip from your collection in a google doc page and got the same error (12_RU). Now i'm going to try with the extraction from ruu.exe, I got the wwe lollipop ruu.exe (the only one i found for wwe) and the dev-edition ruu.exe.. let's see if i can get this to work
Click to expand...
Click to collapse
What's your current CID and MID? It's wasted time if you try to flash RUUs that aren't compatible with the current setup. Are you still S-OFF? If not then you won't be able to change your CID/MID or to downgrade. The RUU.zip files in my sheet should all be fine. Every one of them has already been used successfully by S-ON users. So there should be no need for extracting a WWE RUU.zip. Only the dev one extracted by coolberry seems to have problems.
Flippy498 said:
What's your current CID and MID? It's wasted time if you try to flash RUUs that aren't compatible with the current setup. Are you still S-OFF? If not then you won't be able to change your CID/MID or to downgrade. The RUU.zip files in my sheet should all be fine. Every one of them has already been used successfully by S-ON users. So there should be no need for extracting a WWE RUU.zip. Only the dev one extracted by coolberry seems to have problems.
Click to expand...
Click to collapse
I'm unlocked and still S-OFF and this is the getvar all result:
fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) serialno : ****
(bootloader) imei: ****
(bootloader) version-main: 4.14.617.6
(bootloader) boot-mode: download
(bootloader) version-baseband: ****
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Mat08.cc said:
I'm unlocked and still S-OFF and this is the getvar all result:
[...]
(bootloader) mid: 0PJA10000
(bootloader) cid: 11111111
Click to expand...
Click to collapse
Ok. Being S-OFF and unlocked is totally fine. However for the dev RUU you'll need mid: 0PJA11000 and cid: BS_US002. For the WWE one you should use mid: 0PJA10000 and cid: HTC__001 or whatever HTC__xxx CID belongs to your home country. The SCID actually has no real use on the M9 anymore since it doesn't make your phone ignore MID mismatches with RUUs as it did on older HTC models. It even prevents you from being able to install OTAs.
Hello to you all,
I thought about asking in the help thread but my post will be somewhat long XD
I'm having trouble locating the origin of my HTC One M8 that I bought 2 days ago in bulk from a local shop. It's new, SIM Unlocked, but apparently rooted and S-OFF, figured it was needed in order to unlock it from it's former carrier, which brings me to my question : I want to know it's original carrier and region in order to safely select RUU and ROMs and preferably I would like to do OTAs too. I want to know whether I'll have problems updating to Marshmallow in the future.
Now, in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(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: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT548WMxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Also I have "unknown" under HTC SDK API level, don't know why.
It seems I have the 2.5Ghz version of S801, but some utilities report AC variant some others AB. I got 63k on AnTuTu 6.2.6
Other than that the phone seems to be running really good, snappy, no lag, gets a bit warm with light usage, I don't think I got a fake one but correct me if I'm wrong.
It's in airplane mode, haven't put a SIM card in yet.
So what do you guys think ? I surely appreciate any insight you might have
ELS28 said:
I want to know whether I'll have problems updating to Marshmallow in the future.
Click to expand...
Click to collapse
You don't have to wait to update to Marshmallow if you want to, you can do it now.
ELS28 said:
...in the back of the phone is written : model OP6B700, that would make it a Sprint device right ? which from what I read is pretty delicate to work with, being CDMA and all.
Click to expand...
Click to collapse
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
ELS28 said:
CID Getter gave me : OPTUS_001
And here is my fastboot getvar all :
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-main: 4.18.708.12
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
bootloader) security: off
I noticed I have superCID ... why doesn't CID Getter report it ? If I want to revert it back which one do I input ? I don't know the stock value.
I noticed my MID is OP6B65000 what model is this ?
It seems I have the 2.5Ghz version of S801
Click to expand...
Click to collapse
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
ELS28 said:
Really confused right now should I go ahead and install OTA ? I have one notification version 4.16.401.13 that wants to be installed.
Click to expand...
Click to collapse
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
ELS28 said:
It's in airplane mode, haven't put a SIM card in yet.
Click to expand...
Click to collapse
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.
ckpv5 said:
You don't have to wait to update to Marshmallow if you want to, you can do it now.
That's only back cover get replaced. You getvar result doesn't show it is a Sprint device.
Sprint product is M8_WHL and yours is GSM M8_UL
Based of the info above especially the MID 0P6B65000 & 2.5Ghz .. that's an Optus device ... originally from Australia. The original CID is OPTUS_001
You can't do OTA to 4.16.401.13, won't work .. you'll get system variant error with OTA.
You should put a SIM to test whether it's really SIM unlocked from Optus.
Also to check whether LTE is working fine.
Where are you located ? You have a S-Off device, you can install any region GSM RUU (if available) but not OTA to 4.16.401.13 when your OS on bootloader is shown as Hong Kong and MID is Optus Australia.
Click to expand...
Click to collapse
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
The information you provided raised some more questions :
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?
ELS28 said:
Thank you for replying
To answer your question, my location is north africa. Tomorrow I'll get a nano SIM to try.
Click to expand...
Click to collapse
Do that first .. see any problem with network.
ELS28 said:
1- I can't do OTAs, so the only way to update for me is through RUU or custom ROMS ?
Click to expand...
Click to collapse
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
ELS28 said:
2- I have a Hong Kong OS, can I change it ? will I have to change the MID and CID accordingly ? I can choose whatever values I want it won't cause any problems ?
Click to expand...
Click to collapse
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
ELS28 said:
3- How come while in OS I have different build numbers than in Bootloader ? in OS I have build version : 4.16.401.10. That's europe version right ?
Click to expand...
Click to collapse
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
ELS28 said:
4- Let's say I want to revert everything back to stock international version with Sense etc, to be able to do OTAs, what do I have to do ?
Click to expand...
Click to collapse
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)
ckpv5 said:
Do that first .. see any problem with network.
You can do OTA only if you put the Optus ROM in your device. The problem is back to Optus and do OTA may break the SIM unlock.
But why do you want to OTA ? You can manually direct update it to Marshmallow if that is your intention.
You don't need to change the CID, let it be SuperCID but you may need to change MID (some people said no need to change MID when SuperCID but personally I don't experience a success firmware flashing without proper MID)
You can only choose any value meant for GSM but not CDMA. While on SuperCID, you need only change MID or change it to SuperMID.
Bootloader info is your firmware info.
OS no. in settings is Software info.
So this is like you're running a custom ROM, running a Europe ROM on Hong Kong firmware.
Depends on which International version .. let say it is Europe version
1. I suggest to change the MID to 0P6B10000 - http://forum.xda-developers.com/showthread.php?t=2708581
2. Install latest Europe RUU - http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
(skip the relocking part)
Click to expand...
Click to collapse
Hi, sorry for delayed answer.
Bought a new nanoSIM today, seems to be working fine, made a few calls etc... LTE isn't available in my municipality yet, it will be in the upcoming months but I have the option to select it. I did test HSPA though and it works fine. I guess it's fully sim unlocked then
Regarding OTA, I just saw it as an easier way to update than the commands I had to enter to flash via RUU and all... I guess now I have to learn them alright
So it's my firmware that's from Hong Kong, I didn't know that thanks for the clarification.
Sorry I have more questions
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble free ?
3-I assume that my simUnlock is definitive now, correct ?
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?
A Big Thank you for the big help :good:
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble freeYou need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.
ckpv5 said:
1-Now that I'm running HK firmware and corresponding MID but EU ROM, you suggested I change to EU MID, but won't that cause issues with firmware being HK ?You have OS Hong Kong no. which I assume it's HKG firmware but your MID is not HKG but it can be Australia and it can be India. I assume it is Australia as it has 2.5 Ghz and CID OPTUS001 (as you mentioned it)
Change it to EU MID won't cause any issue but a better option as the current ROM on your device is EU 4.16.401.10 and that's why you get notification for OTA to 4.16.401.13
2- If I flash the EU RUU you sent me, I assume the firmware will no longer be HK, correct ? and after that I can just keep to install EU roms and be trouble freeYou need to change MID first to EU then install EU RUU. The firmware will be EU, no more HKG. You can install any GSM ROM after that, trouble free.
3-I assume that my simUnlock is definitive now, correct ?Yes it is SIM unlocked, the reason why I don't recommend Australia Optus firmware & ROM so it won't get SIM locked again. The best option is EU as you're in North Africa.
4-You seem to be certain I have superCID, so bootloader info trumps CIDgetter info, but I'm curious, why the value differs between the two ? does the app not report it correctly after changing the value ?That's what shown on getvar result. No idea about the app. I tried, it can't read my CID as I'm running Nougat ROM. You can try Simple CID Getter to recheck.
But getvar is always correct and the best option.
5-I will be downloading the files from the links you sent me, and doing my homework too but for information's sake, when I boot in bootloader, I have the "locked" banner, but you know that already I also have "software status : official" does it indicate that the Lollipop EU ROM I currently have is a stock signed one ?Most probably.
If you want to see whether it is stock non-rooted, you change MID to EU then you can accept the OTA and see whether it will be successful to install.
As you have a LOCKED bootloader, you need different method to change the MID .. you need to install a flashable TWRP and do the MID change while in recovery.
But why want to waste time checking, downloading and installing OTA when RUU is available and you can directly update to the latest.
6-My device came rooted but I don't see Superuser installed, I assume I'll have to root it again after the update, correct ?How do you know that it is currently rooted ? OTA won't work on a rooted ROM.
Yes, you have to root again after each update (when you need a rooted stock ROM). If you want to install custom ROM, no need to root .. only install TWRP and install custom ROM. Custom ROM mostly come pre-rooted.
Click to expand...
Click to collapse
Alright thanks for reassuring me.
For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
Upon installing CPU-Z to have more information about the device I noticed "root access : yes" so I installed Root checker and indeed it told me I have root access, that's how I knew about it. Well then I don't plan to OTA anymore XD
The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?
ELS28 said:
1. For the CID, with Simple CID Getter I get the same OPTUS_001... no idea why XD
2. The first method to change MID that you sent me doesn't work even if I'm S-off ? so I'll need to use this tool ? http://forum.xda-developers.com/showthread.php?t=2779524 if so then the sequence order should be : Unlock bootloader from htcdev, then flashing TWRP like you said here http://forum.xda-developers.com/htc-one-m8/help/unlock-bootloader-install-custom-t3371328 then using the MID changer tool ?
3. I don't need to revert to stock recovery and locked bootloader before flashiing with RUU ?
Click to expand...
Click to collapse
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581
ckpv5 said:
1. No idea why these app read differently. Just ignore it for now .. that can be fixed later
2. Don't follow those guide .. I'll give you the guide below
3. No need
First - you need to install TWRP.
a- Download the hboot flashable zip here : http://forum.xda-developers.com/showpost.php?p=70210155&postcount=19
b- put it on root of your microsd
c- boot to bootloader then select hboot - it will ask you to update, volume up to update .. let it finish, reboot once completed. Delete/remove the 0P6BIMG.zip from your microsd.
Second - you need to unlock bootloader as it is easier to thing with unlocked bootloader
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796[/B]
exit
reboot to bootloader .. you should see the bootloader is now unlocked.
Third - change MID to EU MID 0P6B10000
a- boot to bootloader - select hboot then recovery
b- once in recovery, select mount and mount system
c- open a command prompt from your adb/fastboot folder then type (one after another - suggest you copy paste the code, don't manually type them
adb shell
Code:
[B]echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384[/B]
exit
reboot to bootloader
open a command prompt from your adb/fastboot folder then type
fastboot getvar mid
you should see the MID now read as 0P6B10000
Fourth - your device is ready, you can install RUU as per my earlier guide.
Note : if there is error related to CID ... we'll fix it after you tried the RUU. If the SuperCID is correct, the installation should be fine.
Credit to @scotty1223 for his threads as reference
http://forum.xda-developers.com/showthread.php?t=2708571
http://forum.xda-developers.com/showthread.php?t=2708581
Click to expand...
Click to collapse
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD
ELS28 said:
Thank you for taking up the time to write this guide,
I'm in second step, when I select mount, I have multiple cases to tick, do I untick them all but system or do I leave Cache, Data and microSD ticked with system as well ? sorry super noob question xD
Click to expand...
Click to collapse
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.
ckpv5 said:
Doesn't matter what already ticked, the important part is mount system (tick) as it is not mounted at default. The rest let them be as what they are when you select mount menu.
I'll check tomorrow your progress .. time to sleep now as it's over 1.30 am here.
Good luck.
Click to expand...
Click to collapse
alright thank you and good night
EDIT : I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine I don't get the red developpement message on boot to OS, only when I boot to recovery, it doesn't really bother me for now. I don't plan to update to MM immediately though, this has been a lot of new manoeuvers to learn in one take plus I want to read more about eventual issues with apps after I update, so I'll be using the current ROM some time before using your guide again and updating. Thank you so much for taking me through this process, I learned a lot
ELS28 said:
I successfully unlocked and changed MID to 0P6B10000 there seems to be no problem at all and the phone is running fine
Click to expand...
Click to collapse
:good::good:
Guys, my htc one m8 tmobile op6b130 ( bootloader looked, s-off) current software 4.16.1540.8. ... It does not install the update and says that i must revert back to original system software because it is modified version.
so please guide me how to get it done.. how do i install the update. Thanks
What do you mean by software number (where are you reading the nubmer)? Best thing to go by, is the OS number listed on the bootloader screen.
Also, an OTA will fail if the phone is rooted, custom ROM, or even unrooted (needs to be a never rooted stock ROM).
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Otherwise, did you change the CID or MID (and know what they currently are)?
Bootloader screen is like
Software status official
***locked*** S -off
cid -11111111
OS 4.16.1540.8
The model written at rear bottom of my htc is Op6b130 .
i get update with a number 4.17.1540.9 which does not install.
Thats the real confusion with me .. so please tell me the way how do i install the next updates.
mfaizi16 said:
Bootloader screen is like
Software status official
***locked*** S -off
cid -11111111
OS 4.16.1540.8
The model written at rear bottom of my htc is Op6b130 .
i get update with a number 4.17.1540.9 which does not install.
Thats the real confusion with me .. so please tell me the way how do i install the next updates.
Click to expand...
Click to collapse
The phone is heavily modified. It has some point been rooted, SuperCID (11111111) and had the US Developers Edition (4.16.1540.8) firmware and/or RUU applied.
Do you know the history of these mods; did you do them, or did someone else mod the phone?
Can't say for certain, unless I know more details. But the easiest way to update to the latest (MM) version may be to flash 6.12.1540.4 firmware, then flash the 6.12.1540.4 RUU.
I did not do anything like that. I got my htc in this form.
so if MM update is better. Can you please tell me the procedure of installing firmware and ruu file as you said. I would be very grateful to you for this.
Would this procedure be right for me?
https://forum.xda-developers.com/ht...uide-htc-one-m8-to-developer-edition-t3331854
mfaizi16 said:
Would this procedure be right for me?
https://forum.xda-developers.com/ht...uide-htc-one-m8-to-developer-edition-t3331854
Click to expand...
Click to collapse
Yes, that would actually work, and describes what I was talking about. Nice work finding it yourself!
I'm not sure whether you need to change the MID or not. CID is fine to run the 6.12.1540.4 firmware and RUU. And SuperCID will actually bypass the MID in some situations (but not all). Plus, with the info given so far, I can't tell what the current MID is (it may already have been changed).
If you do need to change the MID, you will also need root. So that would be more steps.
So my advice is to first skip the steps of changing CID and MID. Just go to the steps of flashing the 6.12.1540.4 firmware and RUU. If the firmware fails due to wrong MID, it will tell you that via an error message; and we can tackle that issue if it comes up. But if it works on the current MID, then we've saved some steps.
Best (most accurate) way to determine the current MID, is to do command: fastboot getvar all
Then post the output (delete IMEI and serial number before posting).
This will also give us a lot more useful info on the device.
You'll need to use fastboot anyway (for the guide you linked), if you don't already know how. So you may as well figure it out now. The command should also work with the htc fastboot given in the thread you linked, but would be: htc_fastboot getvar all
in fastboot getvar all ... i got
version bootloader: 3.19.0.0000
version baseband: 1.24.21331147A1.09G
version cpld: none
version microp: noone
version mics: pvt ship s-off
meid: 00000000000000
Os : 4.16.1540.8
product: m8_ul
platform: hTCBmsm8974
modelid: OP6B13000
cidnum: 11111111
partition layout: generic
security: off
buld mode: ship
boot mode: fastboot
mfaizi16 said:
in fastboot getvar all ... i got
version bootloader: 3.19.0.0000
version baseband: 1.24.21331147A1.09G
version cpld: none
version microp: noone
version mics: pvt ship s-off
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: OP6B13000
cidnum: 11111111
partition layout: generic
security: off
buld mode: ship
boot mode: fastboot
Click to expand...
Click to collapse
Good to go with 6.12.1540.4 flashing from the guide you linked
Flash the firmware.zip in RUU mode then reboot to bootloader make sure the new os number is 6.12.1540.4 then proceed to flash the RUU.exe
Good luck
Sent from my HTC M8 using XDA Labs
do I need to change Cid & Mid?
when i typed adb.exe shell .. it gave me error that no device is there .
although it showed me my serial number when typed adb devices. it ran fine.
but what's the problem with adb.exe shell?
secondly, is it ok to jump from 4.16.1540.8 to directly 6.12.1540.4?
mfaizi16 said:
do I need to change Cid & Mid?
when i typed adb.exe shell .. it gave me error that no device is there .
although it showed me my serial number when typed adb devices. it ran fine.
but what's the problem with adb.exe shell?
Click to expand...
Click to collapse
no need to change anything you have supercid and the right mid,it will pass the check
it's "adb shell" not "adb.exe shell"
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
mfaizi16 said:
secondly, is it ok to jump from 4.16.1540.8 to directly 6.12.1540.4?
Click to expand...
Click to collapse
yes but use the steps in the guide flash firmware.zip then flash the RUU.exe
While flashing ruu file, when I typed fastboot flash zip rom.zip
It said that targeted maximum download reported 1825********* bytes.
And my pc stucks there and htc stuck there with htc logo..
So what do i do now?
mfaizi16 said:
While flashing ruu file, when I typed fastboot flash zip rom.zip
It said that targeted maximum download reported 1825********* bytes.
And my pc stucks there and htc stuck there with htc logo..
So what do i do now?
Click to expand...
Click to collapse
try another usb port ( use usb 2 not 3 ) and make sure the drivers are installed properly
mfaizi16 said:
While flashing ruu file, when I typed fastboot flash zip rom.zip
It said that targeted maximum download reported 1825********* bytes.
Click to expand...
Click to collapse
You need to use the htc_fastboot to flash the RUU, as indicated in the guide you linked (and required files downloaded from there as well). The "generic" Android fastboot can't handle files that big.
Although, you should drop the ".exe" (indicated in the guide) from all the fastboot commands. I've never seen ".exe" included on fastboot and adb commands, and it will probably cause you an error like it did when flashing firmware. So the command should be:
htc_fastboot oem rebootRUU
htc_fastboot flash zip rom.zip
---------- Post added at 09:51 AM ---------- Previous post was at 09:47 AM ----------
mfaizi16 said:
secondly, is it ok to jump from 4.16.1540.8 to directly 6.12.1540.4?
Click to expand...
Click to collapse
Yes, that is fine. Which is why I told you to do it. If anything else needed to be done, I would have indicated that.
RUU doesn't need to be installed in sequence, meaning you can skip a version(s). RUU is different from OTA, as OTA typically does need to be installed in sequence.
With s-off, you can even go backwards with RUU. Which is also something you can't do with OTA.
while flashing firmware , it first said 'failed' and then automatically came with 'finished and time' .
When i went to ruu .. i first used htc_command .. but it said that ' this command is not in internal and external blaa blaa'. So i went without htc_ and got stuck and waited about half hour for that. Then , knowing nothing i did factory reset with wipe cache to restore my phone back to 4.16.1540.8.
Are there any pre-requisites that phone shold be unlocked and rooted (as i saw some videos on youtube)?
My phone is s-off, bootloader locked and no root access.
mfaizi16 said:
while flashing firmware , it first said 'failed' and then automatically came with 'finished and time' .
Click to expand...
Click to collapse
If it gave a message about "flush image immediately" this just means you need to flash the firmware again (needing to flash 2 times is normal and expected).
If the firmware installed correctly, you will see OS 6.12.1540.4 on the bootloader screen, and also see 6.12.1540.4 for "version-main" if you do fastboot getvar all.
You must have 6.12.1540.4 firmware properly installed, in order to flash the RUU.
mfaizi16 said:
When i went to ruu .. i first used htc_command .. but it said that ' this command is not in internal and external blaa blaa'.
Click to expand...
Click to collapse
You are getting that message, since you are not executing the command from the folder where htc_fastboot.exe is located. After you download htc_fastboot from the thread you linked, open Command Prompt in the folder (Left Shift + Right Mouse Click) and run the commands.
Leaving off the "htc" means you are trying to use the "generic" fastboot tool (fastboot.exe). Which would also confirm the fact you are probably running the command from the wrong folder. Again, using the regular fastboot will never work, since it can't handle the file size of the RUU.
mfaizi16 said:
Are there any pre-requisites that phone shold be unlocked and rooted (as i saw some videos on youtube)?
My phone is s-off, bootloader locked and no root access.
Click to expand...
Click to collapse
You mean prerequisites for the RUU? If so, saying bootloader unlocked and rooted are prerequisites is false and incorrect. If you saw it on a YouTube, you are confusing RUU with something else.
Bootloader locked is normally (s-on) a requirement for RUU. But since you are s-off, it will run with the bootloader unlocked, locked or relocked.
Root has no effect on RUU. RUU will run, whether the phone is rooted or not.
---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------
mfaizi16 said:
Then , knowing nothing i did factory reset with wipe cache to restore my phone back to 4.16.1540.8.
Click to expand...
Click to collapse
What exactly are you trying to "restore" or accomplish with this? It's not clear you have even installed anything past 4.16.1540.8, to begin with.
Finally did it successfully!
Thank you everyone for guiding me.
redpoint73 said:
What do you mean by software number (where are you reading the nubmer)? Best thing to go by, is the OS number listed on the bootloader screen.
Also, an OTA will fail if the phone is rooted, custom ROM, or even unrooted (needs to be a never rooted stock ROM).
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Otherwise, did you change the CID or MID (and know what they currently are)?
Click to expand...
Click to collapse
Hi I can see you are kind on HTC M8. Can you help me? My phone don't see updates. It sprint version.
The was changed to super cid. HTC sync manager don't recognise it Nobody from HTC can help me. They don't know what to do.
pablo_com said:
Hi I can see you are kind on HTC M8. Can you help me? My phone don't see updates. It sprint version.
The was changed to super cid. HTC sync manager don't recognise it Nobody from HTC can help me. They don't know what to do.
Click to expand...
Click to collapse
If you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Basically, Sprint (and most US carrier versions of the M8) won't update if not connected to that actual US carrier (Sprint, in your case). Also, you can NOT "modify" the Sprint version to make it another version (such as Euro), and the reason for that is that the Sprint version you will radio brick the device doing this! So don't try it!
You can update using the RUU meant for the Sprint M8 (and only the RUU meant for the Sprint M8, for the reason mentioned above). Whether you need to update or not (by RUU) depends on what it says in the getvar info I asked for above.