I have a one x+ and i wanted to upgrad to 4.2.2 (it was on 4.1.1) so i flash a dump (from xda) via fastboot , now there no imei ,no wifi adresse (wifi dont work) but phone power on normally its S-off and super cid , i tryed to flash boot.img but no success (Remote not allowed ) , when go to about the main version is 1.14.401.13 but when i check with fastboot its 2.18.401.2 so tryed to flash ruu but always same error : ERROR 258 IMAGE ERRROR
i had tryed those ruu
-RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1 204.168.32_release_299688_signed.exe
-RUU_ENRC2B_U_JB_45_HTC_Europe_1.14.401.18_Radio_3. 1204.167.31_release_291415_signed.exe
-RUU_ENRC2B_U_JB_45_HTC_Europe_1.16.401.6_Radio_3.1 204.168.32_release_297177_signed.exe
the main question can we downgrade one x+ when its s-off (mine is s-off and have super cid) and how to fix the main version probleme ..
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.72.0000
(bootloader) version-baseband: 3.1204.171.33
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.18.401.2
(bootloader) serialno: HT28LW100050
(bootloader) imei: 353567051375446
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511***
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4063mV
(bootloader) devpower: 91
(bootloader) partition-layout: None
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.438s
If you have S-Off and can get hold of one of the older bootloader images, you can flash it from fastboot, with the command "fastboot flash hboot xxx.img"
Your problem is the boot.img though. Are you sure your S-Off? As the error message you get, is because the bootloader is locked. Maybe try unlocking the bootloader too. Or as your S-Off, put the boot.img in an update.zip and flash from recovery.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
If you have S-Off and can get hold of one of the older bootloader images, you can flash it from fastboot, with the command "fastboot flash hboot xxx.img"
Your problem is the boot.img though. Are you sure your S-Off? As the error message you get, is because the bootloader is locked. Maybe try unlocking the bootloader too. Or as your S-Off, put the boot.img in an update.zip and flash from recovery.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
first thanks for your repley ...
Yes im sure im s-off its what indicated in fastboot mode and information readed via fastboot getvar all ..
I must flash boot.img or hboot.img ? i must flash boot for 1.14.401.13 or for 2.18.401.2
can u share the correct file ?
I had flashed 2 boot.img from 2 branded version i found in the forum but same probleme !
Hello all. I recently had a bootloop issue with my HTC one. In my first attempt to fix I unlocked the bootloader and flashed a custom recovery and rom only to experience the same issues. Afterwards I relocked and attempted to run an RUU which updated the phone to 4.3 and the hboot to 1.55. Now when going into recovery the phone says entering recovery then goes back into bootloop. Could the eMMC chip be fried? I am currently *Unlocked* *Tampered* S-On on Hboot 1.55. I can no longer relock to run the RUU again. Any ideas? Here is a copy of my fastboot getvar all:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: HT346Wxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3967mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Thanks in advance!
skandalous1 said:
Hello all. I recently had a bootloop issue with my HTC one. In my first attempt to fix I unlocked the bootloader and flashed a custom recovery and rom only to experience the same issues. Afterwards I relocked and attempted to run an RUU which updated the phone to 4.3 and the hboot to 1.55. Now when going into recovery the phone says entering recovery then goes back into bootloop. Could the eMMC chip be fried? I am currently *Unlocked* *Tampered* S-On on Hboot 1.55. I can no longer relock to run the RUU again. Any ideas? Here is a copy of my fastboot getvar all:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-ON
serialno: HT346Wxxxxxx
imei: xxxxxxxxxxxxxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3967mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Thanks in advance!
Click to expand...
Click to collapse
Did you fastboot erase cache ?
clsA said:
Did you fastboot erase cache ?
Click to expand...
Click to collapse
I did, both before and after flashing recovery. I also tried all of the available recoveries with no success. All result in bootloop after "entering recovery" is displayed.
skandalous1 said:
I did, both before and after flashing recovery. I also tried all of the available recoveries with no success. All result in bootloop after "entering recovery" is displayed.
Click to expand...
Click to collapse
Pretty crazy .. I hope you get it solved
Hello Community,
Let me begin by apologizing if I am in the wrong forum channel. I am new to the site kind of. I mostly sift through answers.
In this case I have not found anyone with my problem cause the wouldn't make the rookie mistake of forgetting to take a backup BEFORE flashing junk on their fancy phones.
Resources: I have latest TWRP, can access it and bootloader
Problem:
I have an HTC One M7 from Sprint. Currently all user data has been formatted (cause I am genius). I am able to lock and unlock bootloader. My phone is in S-ON (another dumb mistake I know). The device is recognized in fastboot but not in ABD and I cant figure out why not. superuser was deleted by the wipe.
Solutions Tried but Failed:
I have download the RUU for my phone (or at least I think *651.10 and *651.7) and tried to run the setup.exe in admin mode while my phone was locked in fastboot... This resulted in an Error:155
I have tried flashing the same RUU from cmd prompt... this resulted in remote 12: signature error (still dont know what that means)
I have tried achieving S-OFF but alas I cant get my device to be recognized by ABD, I dont have an OS for internet/radio signal
I am starting to think I may have just effed everything up.
fastboot getvar all
version: 0.5
version-bootloader: 1.56.0000
version-baseband: N/A
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA
imei: 99*
meid: 99*
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4237mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
PLEASE HELP
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?
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.