Hello,
I am going to sell my T-Mobile HTC One, but I would like to return my device back to stock using the RUU method.
Here is what pops up when I issue the command fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: [B]1.57.0000[/B]
(bootloader) version-baseband: [B]4T.27.3218.14[/B]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: [B]5.14.531.1[/B]
(bootloader) version-misc: PVT SHIP [B]S-OFF[/B]
(bootloader) serialno: Censored
(bootloader) imei: Censored
(bootloader) meid: 00000000000000
(bootloader) product: [B]m7_ul[/B]
(bootloader) platform: HBOOT-8064
(bootloader) modelid: [B]PN0713000[/B]
(bootloader) cidnum: [B]T-MOB010[/B]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: [B]off[/B]
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My HTC One is S-OFF, unlocked bootloader, with TWRP 2.6.3.3 installed. Not sure if it matters but I'm running ARHD 82.0. I already have the 6.10.531.9 RUU file from the official HTC Support website.
So my question is: How do I run this RUU? Do I need to do anything to my phone before running the RUU.exe file? And after flashing the RUU, will I still receive OTA's from T-Mobile?
Thanks.
You have to relock your bootloader. After that, just boot your phone into fastboot and run the RUU.exe
You'll receive the OTA from TMO again. I've done it a few time.
JSing said:
You have to relock your bootloader. After that, just boot your phone into fastboot and run the RUU.exe
You'll receive the OTA from TMO again. I've done it a few time.
Click to expand...
Click to collapse
Even if I'm S-OFF? And will I be able to unlock it again?
uwotm7 said:
Even if I'm S-OFF? And will I be able to unlock it again?
Click to expand...
Click to collapse
Yes you'll retain your S-OFF after it and you can unlock it again if you want.
uwotm7 said:
Even if I'm S-OFF? And will I be able to unlock it again?
Click to expand...
Click to collapse
@JSing
FYI, if you are S-OFF you do not need to relock your bootloader to run a RUU or firmware.
Which RUU are you using, by chance. I am doing the same thing and trying to figure out which one I need. North American, unlocked. 32 GB. T Mobile.
knightsmarian said:
Which RUU are you using, by chance. I am doing the same thing and trying to figure out which one I need. North American, unlocked. 32 GB. T Mobile.
Click to expand...
Click to collapse
Try this one 6.10.531.9.
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
hey, i got a rooted HTC One with TWRP and im kinda new to the rooting since the last phone i rooted was the HTC Evo. I was trying to get s-off, i've used moonshine, revone, and rumrunner with no luck, Can a guy get some assistance please? PM's are welcomed
memfus_boi said:
hey, i got a rooted HTC One with TWRP and im kinda new to the rooting since the last phone i rooted was the HTC Evo. I was trying to get s-off, i've used moonshine, revone, and rumrunner with no luck, Can a guy get some assistance please? PM's are welcomed
Click to expand...
Click to collapse
You're using a rooted rom with an unsecured kernel, right?
T-Mobile Stock 1.27.531.11 Hboot 1.56 can't S-Off
Drashna said:
You're using a rooted rom with an unsecured kernel, right?
Click to expand...
Click to collapse
Same here -
can't get either rumrunner or Firewater to s-off hboot 1.56 with T-Mo Stock 1.27.531.11
here is the full info of my device -
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any idea if that can be done? Tried also installing CW Recovery with CM 10.2 and still no luck.
Thanks for your help
I relocked my bootloader. Turned S- ON and ran the correct RUU.exe file that I downloaded straight from HTC's website and I always get stuck during the update process(technically a downgrade I suppose) The RUU.exe always comes back with error 155 UNKNOWN ERROR. Not sure what I'm doing wrong. I ran ADB and checked before I ran the RUU that my PC does in fact recognize it( both while on my homescreen and FASTBOOT mode). Please I need help!
ok so I unlocked my bootloader again via HTCDev. But I can't for the life of me get S-OFF again. My HBOOT is 1.54. I am on the OFFICIAL GPE ROM. Help please.
vampsandbats said:
ok so I unlocked my bootloader again via HTCDev. But I can't for the life of me get S-OFF again. My HBOOT is 1.54. I am on the OFFICIAL GPE ROM. Help please.
Click to expand...
Click to collapse
Post a fastboot getvar all except remove your imei and serialno! If what I suspect is true, you changed your MID and CID to the Google MID & CID. If you did that, then the T-Mobile RUU will not run since it is the wrong MID & CID. When you went back to S-ON you made it impossible to change your MID & CID back to T-Mobile. As far as S-OFF is concern you might try Sunshine S-OFF.
majmoz said:
Post a fastboot getvar all except remove your imei and serialno! If what I suspect is true, you changed your MID and CID to the Google MID & CID. If you did that, then the T-Mobile RUU will not run since it is the wrong MID & CID. When you went back to S-ON you made it impossible to change your MID & CID back to T-Mobile. As far as S-OFF is concern you might try Sunshine S-OFF.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I appreciate your help.
vampsandbats said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I appreciate your help.
Click to expand...
Click to collapse
Let try an older RUU 5.14.531.11
Place phone in FASTBOOT USB
Lock your bootloader if it is not already locked
Run the RUU from your computer
If it fails post the error
If successful then
Try S-OFF with Sunshine
RUU 6.10.531.9
RUU 6.10.531.10
DUDE THANK YOU SO MUCH. I KNOW ITS LIKE 4 months ago but thank you so much. the old RUU did the trick and I got back to stock.
Currently I am running CM12 and here is my firmware info:
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.21.213311491.A04G
OpenDSP-v47.2.2-00564-M8974_FO.1024
OS-
eMMC-boot 2048MB
Dec 2 2014,22:40:49.0
I have been trying all day to downgrade to 4.4.4 using RUU and zip files but no luck so far.
I have decided to finally go for sunshine. BUT sunshine wants me to use a stock or near stock rom. What rom would you suggest me to install? Or what other options do I have at this point?
devbro said:
I have been trying all day to downgrade to 4.4.4 using RUU and zip files but no luck so far.
Click to expand...
Click to collapse
You are only "downgrading" the ROM, not the firmware. RUU should work fine, as long as its the AT&T 4.4.4 RUU. Did you relock the bootloader? Any error messages for the RUU?
No idea what "zip files" you are trying to flash (stock ROM, firmware, zip full of porn?) as you are the opposite of specific.
devbro said:
I have decided to finally go for sunshine. BUT sunshine wants me to use a stock or near stock rom. What rom would you suggest me to install? Or what other options do I have at this point?
Click to expand...
Click to collapse
Its pretty self explanatory, a stock AT&T ROM is your best best.
redpoint73 said:
You are only "downgrading" the ROM, not the firmware. RUU should work fine, as long as its the AT&T 4.4.4 RUU. Did you relock the bootloader? Any error messages for the RUU?
No idea what "zip files" you are trying to flash (stock ROM, firmware, zip full of porn?) as you are the opposite of specific.
Its pretty self explanatory, a stock AT&T ROM is your best best.
Click to expand...
Click to collapse
I keep on getting error 155 from RUU. and attempting to lock bootloader gives me SPMI write failure.
I have tried this file last:
http://dl3.htc.com/application/RUU_...40.45.C33065.00_F_release_426617_signed_2.exe
still no go
To confirm, your bootloader currently says UNLOCKED?
What is your current CID?
redpoint73 said:
To confirm, your bootloader currently says UNLOCKED?
What is your current CID?
Click to expand...
Click to collapse
My bootloader is unlocked.
cid: CWS__001
here is a fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA45AWM06131
(bootloader) imei: AAAAAAAAAA
(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: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
Everything on the phone looks okay to run an AT&T RUU. It sounds like you tried more than one, so that pretty much eliminates the possibility the RUU file was damaged/corrupt, etc.
Did you by change convert to GPE (black bootloader screen)?
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.