I have an AT&T M8 which has an old version of the GPE SkyDragon ROM installed.
Bootloader is unlocked, S-ON is still ON.
Android version: 5.0.1
Baseband version: [email protected]_40.34.C35006.02_F
Kernel version: 3.4.0-SkyDragon-V3.0.7 from Jan 2014.
Build number: SkyDragon - LRX22C.H5
I want to send this phone to another country, and for that I need to get it sim-unlocked. I got the unlock code from AT&T, but it doesn't work - I am assuming the ROM is at fault, so I am trying to get the phone back to full stock by flashing an official RUU.
I downloaded the latest official RUU from http://www.htc.com/us/support/htc-one-m8-att/news/, but I cannot get it to flash!
When trying and the phone is booted to regular android, it tells me about error 170, which, as I gather, means it cannot find the phone.
I installed HTC Sync, and that can't find the phone either.
If I reboot to bootloader, the RUU installer finds the phone, but after the HTC logo (silver with black background) shows up on the phone, it throws error 171.
It feels like I need to relock the bootloader but I am afraid to mess it up now.
Please help with some guidance..
Here is the bootloader screen:
Edit: Found an old RUU on my hard drive, version 3.42.502.1 - same as OS version in the screenshot.
I attempted to flash it (using the official exe). It failed on "updating signature" with error 155.
Edit2: Made sure CID and MID match original - they do.
Attempted 'fastboot oem lock'. Now trying to flash the old RUU again.
Edit3: Looks like it's working! RUU is progressing further than ever before.
Edit4: It worked! Booting to Sense now.
Edit5: SIM unlocked worked too, phone is ready to go.
I'll leave this post up in case someone else faces a similar situation.
To run the Marshmallow RUU, try to flash the MM firmware first. See the red font note under the RUU section of my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
I was actually able to just flash the latest official RUU over 3.42.502.1 without the need for commandline.
Back to Stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
Related
Hi guys,
I had Speed Rom 8.0 installed and wanted to bring it back to OTA Wind ICS Ruu. I downloaded:
•RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L .01v2DC_30.69.550L.10_release_229312_signed.exe
I read that I had to lock the bootloader to run the RUU exe but it failed giving me error [140] Incorrect bootloader!
Afterwards I tried other RUU (tmobile, telus) and nothing has worked so far. However I must have messed up along the way and now I am in a boot loop!
I can still get into fastboot/bootloader. Currently I have the bootloader unlocked again. I'm S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1500.6
(bootloader) serialno: SH1BSVP01943
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: GLOBA001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3923mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Zhars7 said:
Hi guys,
I had Speed Rom 8.0 installed and wanted to bring it back to OTA Wind ICS Ruu. I downloaded:
•RUU_Ruby_Globalive_WWE_1.46.1500.3_Radio_1.10.550L .01v2DC_30.69.550L.10_release_229312_signed.exe
I read that I had to lock the bootloader to run the RUU exe but it failed giving me error [140] Incorrect bootloader!
Afterwards I tried other RUU (tmobile, telus) and nothing has worked so far. However I must have messed up along the way and now I am in a boot loop!
I can still get into fastboot/bootloader. Currently I have the bootloader unlocked again. I'm S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.93.0002
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1500.6
(bootloader) serialno: SH1BSVP01943
(bootloader) product: ruby
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH8511000
(bootloader) cidnum: GLOBA001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3923mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6298f8f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Update:
Downloaded •OTA_RUBY_ICS_35_S_Globalive_WWE_2.14.1500.6-1.46.1500.3_release_263096ebhdlebyr7k06p6u.zip
Went into fastboot and tried "Fastboot Update" command
Got the following:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Alright I managed to install SpeedRom 8.0 again. So at least I can boot into the OS.
However the question still remains, how do I go back to Wind Mobile ICS RUU?
Bootloader: Unlocked
S-ON
Zhars7 said:
Alright I managed to install SpeedRom 8.0 again. So at least I can boot into the OS.
However the question still remains, how do I go back to Wind Mobile ICS RUU?
Bootloader: Unlocked
S-ON
Click to expand...
Click to collapse
You need to lock your boot loader, a ruu won't flash without it locked.
Sent from my SGH-T999 using Tapatalk
SuperAfnan said:
You need to lock your boot loader, a ruu won't flash without it locked.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Locking it is no problem, however after the phones goes into a boot loop and I can only access fastboot/bootloader.
My problem is that I'm not sure which Wind Mobile RUU I need to use. Everyone I tried gives me the "wrong bootloader" version error.
Issue is that SpeedRom 8.0 is Tmobile Based and not Wind based.
Do I have execute "Mainver Error Fix" prior to running flashing the RUU?
Zhars7 said:
Locking it is no problem, however after the phones goes into a boot loop and I can only access fastboot/bootloader.
My problem is that I'm not sure which Wind Mobile RUU I need to use. Everyone I tried gives me the "wrong bootloader" version error.
Issue is that SpeedRom 8.0 is Tmobile Based and not Wind based.
Do I have execute "Mainver Error Fix" prior to running flashing the RUU?
Click to expand...
Click to collapse
You have the same issue as I did; installing a T-mobile ROM will generally screw up the bootloader and other system level software. By doing that when you try to go to stock it will complain about not being able to update.
The solution is to get S-off and then force updates. Once you have S-off then the RUU exe will force the install and everything will be OK.
http://forum.xda-developers.com/showthread.php?t=2521403
I soft bricked my AT&T M8 and am hoping some of the great minds here at XDA can help. Unfortunately, this happened back in September so I've forgotten a lot of what I did to get myself in this mess, but I will try to remember as best I can.
I had originally modified my MEID and was running a GPE ROM. When an OTA update was pushed by Google, I foolishly tried to install it and the phone became stuck in a bootloop. I tried to rectify the situation by performing a system wipe, relocking the bootloader, and running the stock AT&T RUU from the SD card. The RUU failed to run and I received "ERROR 159." I am now stuck with the stock recovery image and my device is no longer recognized in fastboot.
First 6 lines of text on the HBoot screen:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning**
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Jun 16 2014,18:47:55.0
Output of fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx (this was populated, I just masked)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 6e0f5a3d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done! finished. total time: 0.013s
Correction, I think it was a GPE RUU that I had installed and not a ROM because my recovery screen is black. I read in another thread that a black screen may indicate this.
I unlocked my bootloader, installed TWRP, and installed Android Revolution 22.1 and the phone still will not boot past the HTC splash screen. I also tried both available RUUs; 1.58 and 2.23. Any suggestions?
I think youd have to revert back to mid of sense version. if s-on I am not sure how you got it to convert in the first place.As I havent ever liked or had the idea of changing the device to gpe. Maybe in the conversion thread you used to convert the device that got you to this point. Are you able to install a gpe rom? I am unfamiliar with ARHD builds
I also have no clue how you got as far as you did without S-OFF. You shouldn't have been able to run a GPE RUU.
ARHD also won't play nice without the 3.x firmware.
Try the desktop .exe versions of the RUUs, if you haven't already, and make sure the md5 matches.
If you can still get twrp on your phone, try restoring a 1.12 or 1.54 backup from here http://forum.xda-developers.com/showthread.php?t=2701376 or http://forum.xda-developers.com/att...nt/att-stock-backups-recoveries-otas-t2855966.
Make sure to factory reset in twrp.
Your cid and mid are still at&t stock, so I don't think those are the cause of your problem. The fields where the firmware version should be displayed are empty though, and I don't know how you got to that state.
If none of that works, then I'd try a 4.4.4 based GPE rom that still works with the 2.x firmware, like an older version of skydragon. An older version of a sense based rom still using 4.4.3 might still work.
I was trying to restore my friend's gpe back to sense because they were having a lot of problems with the gpe install.
No matter what I do it willo boot to the htc screen with exclamation marks in each corner and if i unplug the phone from the pc i get a white bootloader screen it says software status: official
***unlocked***
m8_ul_ca pvt ship s-off
cid-bs_us002
some other stuff
RUU (in orange) last line
a paste of fastboot getvar all:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(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: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT49VWM05000
(bootloader) imei:
(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: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.074s
Can someone walk me through restoring this phone please?!? I'd be greatly appreciative.
fastboot commands still work with the phone but I don't know what to do
thank you all for your help
ayocam said:
No matter what I do it willo boot to the htc screen with exclamation marks in each corner
Click to expand...
Click to collapse
This statement doesn't actually tell us anything about what you tried (or didn't try), which is critical in us helping you.
Please list in detail, the steps you've tried so far, including exact names of files used, specific results (including any error messages and status of the phone after each "attempt").
ayocam said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main: 1.54.401.5
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
Click to expand...
Click to collapse
The above info indicates a mish-mosh of various mods, either before you got a hold of the phone, or a result of the steps you took (or a combination of those two);
- If this was originally the AT&T variant, it was changed to Dev Edition CID
- Not sure, but I think that is the Dev Edition Marshmallow (MM) radio baseband number (or at least some other version MM radio), so apparently had that firmware flashed?
- Had some very old "international" Euro firmware flashed at one point, based on the main version. But this doesn't correspond to the radio number
Its also not clear what version of Sense, is desired: Euro, AT&T, or Dev Edition?
Going to latest Dev Edition RUU is probably the best approach. This will put the phone on Sense, devoid of any AT&T bloat or limitations, plus will update to Marshmallow. Those are all good things, plus the phone already has the proper CID for Dev Edition.
1) Run 6.12.4540.4 firmware from here: https://www.androidfilehost.com/?fid=24438995911977418
By process:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Where "firmware.zip" is the actual name of the downloaded file.
2) Run the Dev Edition RUU (PC required) found at the bottom of the following page: http://www.htc.com/us/support/htc-one-m8/news/
There are other versions that may be converted to (such as Euro) if different band support is desired (Dev Edition has the same band support as AT&T version). But if that is the intent, let me know and I'll walk through that process.
Hi, I was trying to revert back to the stock AT&T 6.0 rom using the RUU. I have "Android Revolution HD 53.1" currently installed which is Android 6.0 and Sense 7.0. It is unlocked and S-on, so I re-locked the phone using the fastboot method. After that the fastboot screen had "***RE-LOCKED*** and ***SECURITY WARNING***" on it. The phone would not reboot normally anymore, it would only go to the fastboot/hboot screen. I tried using the RUU anyway, and while it would detect the phone during the setup stages, as soon as it started the update and the phone switched to the htc screen, it would stop and give "error 171 - lost communication with the device."
So I've unlocked it again and it's working fine again. How can I revert it to the stock rom without making it S-off? Thanks!
Oh and if it matters, on the fastboot/hboot screen, it does show an OS version. It just has "OS-"
Edit: Looked at my previous posts as it's been a while since I've came here. Saw that I made a post last year with a similar problem and that switching USB ports on my computer fixed it. Well, switching USB ports fixed this problem too.
rockr09 said:
Saw that I made a post last year with a similar problem and that switching USB ports on my computer fixed it. Well, switching USB ports fixed this problem too.
Click to expand...
Click to collapse
Nice work figuring it out yourself!
rockr09 said:
After that the fastboot screen had "***RE-LOCKED*** and ***SECURITY WARNING***" on it. The phone would not reboot normally anymore, it would only go to the fastboot/hboot screen.
Click to expand...
Click to collapse
FYI, this is normal and expected. Relocking the bootloader renders the phone unable to boot, as it expects RUU to be run immediately thereafter.
Back to Stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
Appreciate any help. I'm considering all options. My phone got stuck on the boot screen after taking a security update and I was wondering if it's possible to just flash the Marshmallow RUU , i don't mind losing the data its already backed up.
Unlocked bootloader, S-OFF
Variant - M8_UL_CA
CID - BS_US001
OS - 4.16.1540.8
You'll need to flash the MM firmware first (this is a peculiarity with the MM RUU - if you don't the RUU will fail with Error 155), then flashing the RUU is fine.
Also, in the current configuration, you'll need to flash the Developer's Edition RUU (not sure if that is what you meant).
But otherwise, if you are fine with losing your data, I don't seen an issue with running the RUU.
Back to stock
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
safrassm said:
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
Click to expand...
Click to collapse
Yes.
Need Ruu .zip for HTC M8 for this variant
< waiting for device >
(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-OFF
(bootloader) serialno: FA46DSF03997
(bootloader) imei: 990004992158356
(bootloader) imei2: Not Support
(bootloader) meid: 99000499215835
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.019s
Bootloader - Unlocked
Recovery - TWRP
Rooted - yes
Custom ROM - lenage 14.1
shihab94rs said:
74616699(bootloader) product: m8_whl
(bootloader) modelid: 0P6B70000
Click to expand...
Click to collapse
The info above indicates you have the Sprint version. This forum section is specific to the AT&T version M8.
The RUU zips you are looking for, are here: https://forum.xda-developers.com/showthread.php?t=2729173
Also, you should delete your IMEI, serial number, and MEID from the getvar data. Those are personal info, that should never be posted in open forums.
help
Good evening,
I currently have an HTC one M8 under:
version Android: 5.0.2
version sense: 6.0
version ROM 4.28.502.2
I would like to update my Android phone Marshmallow. I am a little lost on the forums.
Thank you for your help.
***Software status: Official ***
***RELOCKED ***
M8_UL PVT SUIP S-OFF
CI-11111111
HBOOT-3.19.0.0000
[email protected]
OpenDNP-v47.2.2-00564-M8974_FO.1024
OS-4.28.502.2
eMMC-boot 2048MB
info tel:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: [email protected]
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.28.502.2
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: SH43XXXXXXXX
INFOimei: 35XXXXXXXXXXXXX
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: m8_ul
INFOplatform: hTCBmsm8974
INFOmodelid: 0P6B10000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 7f8e91a3
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
-----------------------
Hombalala said:
Good evening,
I currently have an HTC one M8 under:
version Android: 5.0.2
version sense: 6.0
version ROM 4.28.502.2
Click to expand...
Click to collapse
Look in my Index thread under "RUU" and you will find a link for the Marshmallow RUU 6.20.502.5 as well as a note (in red font) on flashing the firmware.zip before installing the RUU.
So flash the firmware.zip in fastbootRUU mode, than install the RUU (with phone connected to PC). That is all you need to do.
Did you relock the bootloader to run an RUU, or was it already relocked when you got the phone?
redpoint73 said:
Look in my Index thread under "RUU" and you will find a link for the Marshmallow RUU 6.20.502.5 as well as a note (in red font) on flashing the firmware.zip before installing the RUU.
So flash the firmware.zip in fastbootRUU mode, than install the RUU (with phone connected to PC). That is all you need to do.
Did you relock the bootloader to run an RUU, or was it already relocked when you got the phone?
Click to expand...
Click to collapse
it already unlocked when you got the phone
Hombalala said:
it already unlocked when you got the phone
Click to expand...
Click to collapse
I think you mean to say: the phone was already bootloader relocked when I got the phone.
In any case, you can do as I stated in the previous post. Backup any personal data you want to keep, before you install the RUU. The RUU will wipe the phone.
redpoint73 said:
I think you mean to say: the phone was already bootloader relocked when I got the phone.
In any case, you can do as I stated in the previous post. Backup any personal data you want to keep, before you install the RUU. The RUU will wipe the phone.
Click to expand...
Click to collapse
So do i need my bootloader locked before trying to install MM Firmware then MM Ruu? I am on the same version as of Android 5.0.2, Software 4.28.502.1 and Sense 6.0 as Homblala up above. Mine HTC One M8 is an ATT Version
ELEVO said:
So do i need my bootloader locked before trying to install MM Firmware then MM Ruu?
Click to expand...
Click to collapse
Correct. Bootloader must be locked or relocked to flash firmware and/or RUU. Unlocked bootloader will not allow firmware/RUU to install. Exception is if you have s-off (which bypasses the requirement to relock the bootloader).
Unbricked )
redpoint73 said:
Correct. Bootloader must be locked or relocked to flash firmware and/or RUU. Unlocked bootloader will not allow firmware/RUU to install. Exception is if you have s-off (which bypasses the requirement to relock the bootloader).
Click to expand...
Click to collapse
Thanks for the help. I soft bricked my phone while trying to flash MM firmware so I can install Lineage 15.1 along with Gapps 8.1
All running well now, Thanks all for your help :good:
ELEVO said:
Thanks for the help. I soft bricked my phone while trying to flash MM firmware so I can install Lineage 15.1 along with Gapps 8.1
Click to expand...
Click to collapse
I know what you did. I just don't think you do.
Read my responses to your other threads/posts for a more detailed explanation. No boot after flashing firmware is completely normal and expected. I told you to flash firmware and RUU. You only did firmware.