Database Info

[Q] Finally i bricked my HTC SENSATION !!!!

hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: (removed by me because it's not important)
(bootloader) imei: (removed by me because it's not important)
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s

specter16 said:
hi every one
i was trying to match the RIL/basebande versions
i tried to flash some radio files and i dont know what it happend (i really forget what i did exactlly)
sudenlly i pressed the hard reset in the hboot (yes i remember i did this)
after that i tried to reflash a radio file via fastboot
i notices that in my hboot it's writen like this
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.29.0000
eMMC-boot
Mar 2 2012, 18:14:34
now when i try to flash PG58IMG (radio) it says fail-PU
i thaught that i'm still s-on because that pink LOCKED which written above (even it's written s-off under it !!!!!!!!)
okay i was able to change between hboot version by just flashing the hboot zip file and that's all so i tried to do that like i was
now when i try to flash the hboot (PG58IMG) it says alsi fail-PU
and now i'm stuck into this screen
here is my getvar resault if some one could help me
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 9.99.999.999
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3831mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.509s
Click to expand...
Click to collapse
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC

DennisBold said:
As long as you have access to the boot loader and/or fastboot, you're not bricked. You can technically flash Universal firmware and a recovery to get around this but you might want to flash an RUU as it'll boot you into a ROM and give you a working setup to play with.
Since you're S-OFF download and flash an RUU via fastboot, upgrade or downgrade; it makes very little difference as it will put you in a position to flash a recovery and or universal firmware.
A note on RIL/Basebands, 3.32 and 3.33 have no adverse effects of using a non matching RIL baseband so long as your WiFi and mobile network works, you should be good.
P.S: remove your SN & IMEI from your post
Sent from my HTC
Click to expand...
Click to collapse
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting

specter16 said:
i tried an RUU and it says error 171 usb connection error !
i'm in fastboot and i can see my device connected using the fastboot devices commande
by the way this problem happed while i'm trying to get my wifi working
any way now i'm trying to get my device booting
Click to expand...
Click to collapse
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC

DennisBold said:
I skimmed over your other thread, and you probably should have tried a kernel with BCM drivers if you haven't already.
Try with a different (and known to work) USB.
Also, make sure HTC Sync is closed and that you run the RUU as administrator.
Sent from my HTC
Click to expand...
Click to collapse
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working

specter16 said:
i tried Sultan kernel with BCM driver and it didn't work (wifi turning on................................)
any way this is not my current prb now
one other thing
when i try this commande fastboot oem rebootRUU
here is what it says
Code:
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.235s]
finished. total time: 0.257s
and RUU is still not working
Click to expand...
Click to collapse
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC

DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
okay i'll try
please stay connected, i really need you

specter16 said:
okay i'll try
please stay connected, i really need you
Click to expand...
Click to collapse
Sure. If the fastboot commands work I've got something you can try.
Sent from my HTC

DennisBold said:
Format you SDCard, or make sure it's properly inserted.
Download this file and place it in your fastboot directory.
Edit: Link: http://db.tt/4UwSEM33
Then try this:
fastboot erase recovery
fastboot flash recovery recovery.img
Using your bootloader, boot into recovery
Sent from my HTC
Click to expand...
Click to collapse
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s

specter16 said:
not working !!!
fastboot erase recovery gives me this
Code:
erasing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC

DennisBold said:
You are S-OFF?
Try:
fastboot oem unlock
Else move the universal firmware file into the folder with fastboot and type:
fastboot flash zip <zip name>.zip
Sent from my HTC
Click to expand...
Click to collapse
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s

specter16 said:
not working
Code:
(bootloader) [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC

DennisBold said:
Sorry, always getting commands mixed up.
Try:
fastboot update PG58IMG.zip
Sent from my HTC
Click to expand...
Click to collapse
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green

specter16 said:
archive does not contain 'boot.img'
error: update package missing boot.img
are you sure that i'm s-off my friend ??? because it's written in the hboot above with pink
*** LOCKED ***
but under this line it's written S-OFF with green
Click to expand...
Click to collapse
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC

DennisBold said:
You're S-OFF, however your bootloader is locked. Meaning commands are locked, S-OFF disables security allowing you to flash things without being signed by HTC.
Could you try this:
fastboot erase cache
fastboot oem rebootRUU (if you get SDcard errors, take out your SDCard and try again)
fastboot flash zip PG58IMG.zip
fastboot reboot-bootloader
Sent from my HTC
Click to expand...
Click to collapse
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot

specter16 said:
fastboot erase cache
Code:
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.024s
fastboot oem rebootRUU
SD card errors and the device reboot into hboot
Click to expand...
Click to collapse
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC

DennisBold said:
Tried removing your SD-Card? And have you checked the SDCard still works?
Sent from my HTC
Click to expand...
Click to collapse
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s

specter16 said:
nothing is inserted on my phone (SIM / SD)
and my sd card is working fine on my pc
omg what i did :s:s:s
Click to expand...
Click to collapse
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC

Fail-PU errors generally correspond to firmware corruption
Which is pretty hard to solve
If Op can exactly tell flashing what caused this issue
Maybe we can have a chance
Btw can the phone go to recovery?
Also how did the patched hboot flash went?
Sent from my HTC Sensation 4G using xda premium

DennisBold said:
That's odd. Insert your SDCard after formatting it and placing the PG58IMG.zip on it. Then reboot into bootloader. See if it works, and let me know.
Sent from my HTC
Click to expand...
Click to collapse
- Fail-PU next to the bootloader line
i found this command
Code:
fastboot oem writesecureflag 3
i think this will return me back to s-on
but can i s-off my phone from hboot ??? if i want
or it's useless this command for me ?

[Q] bad CID - stuck in bootloader

In my quest to upgrade the hboot of my HTC One XL (evita), I accidentally used a tool intended for the the HTC One X (JFW Tool), and overwrote my CID to HTC__621. Now I'm stuck in the bootloader. Any help would be much appreciated (especially with the steps, I'm still a bit fuzzy on SuperCID, S-Off, bootloaders, roms and recovery). I think I was previously unlocked, running an unofficial CyanogenMod (because updates stopped coming around), and then I wanted to get on the OTA CM train, but needed to update hboot, which got me in my current situation:
Here's what my bootloader screen says:
Code:
*** TAMPERED ***
*** RELOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
FASTBOOT (or FASTBOOT USB)
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
And here's what I've tried:
tried setting CID to 11111111
tried flashing recovery (my TWRP recovery is not present anymore)
tried flashing hboot
tried running X-Factor exploits
ran the all-in-one tool to try and exploit and unlock
I cannot seem to get anything to work. Flashing anything generates a remote signature fail id error.
Please help me to get my phone back up again!
Thanks,
Dave

You tried all those things without knowing what you're doing? You must love to live life dangerously!
Your bootloader is locked.

In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Sent from my HTC One X using xda premium

Venomtester said:
In bootloader, use volume down to scroll to reboot and hit power button to select it. Then read forums on how to unlock bootloader.
Click to expand...
Click to collapse
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)

boulder_dave said:
Perfect, that's what I needed (I didn't know bootloaders could become "relocked".
So, I'm now back to where I was before, with a phone I cannot update to the latest CM10, because my hboot is too old (=1.09)
I've tried to follow all the instructions on these forums for updating hboot to 2.14, without any success:
Using Hassoon2000's all-in-one kit for the HTC One X (evita) and also from the command line, I've tried to directly install:
hboot 2.14
OTA_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616bcty3drvawwo01k (which contains 2.14)
It fails on signature or hangs. I tried this with bootloader locked and unlocked (thanks to Venomtester, I can now do this without difficulty), and from the bootloader, fastboot and htc screens (gold htc logo).
So any hints on how to get hboot 2.14 installed on this device? Failing that, (or perhaps instead of) I could even go back to a factory ROM and settings, if I could get some hints on this.
Thanks again,
Dave
PS: I have a feeling it may be malfunctioning due to that CID change I did. I tried to change CID back using the regular tool, and then used the instructions for hex editing the CID, all without success (adb shell doesn't work)
Click to expand...
Click to collapse
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.

exad said:
What is your CID right now still the same?
use fastboot oem readcid to find out if you're not sure.
Click to expand...
Click to collapse
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s

boulder_dave said:
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.17.32.09.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.85.502.3
(bootloader) serialno: HT249W300070
(bootloader) imei: 359691042133556
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Click to expand...
Click to collapse
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.

exad said:
Okie dokie, so, your bootloader is unlocked at this point right?
If so, flash twrp 2.6: fastboot flash recovery recoveryfilename.img
Your CID shouldn't matter for right now, you should at least be able to flash a Rom at this point (obv. not cm10.1 3.4 kernel). Then we can work on SuperCID and S-OFF.
Click to expand...
Click to collapse
Thanks for all the help!
2.6 TWRP installed and working. Still running (extremely poorly, all kinds of flakiness: loses cellular data connection constantly) the 10.1 CM I was running before I embarked upon this upgrade.
What should I do next?
Cheers,
Dave

If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.

RollTribe said:
If I'm not wrong, you're gonna need to s-off to get to the newest cm nightlies because of RUU. So first you're gonna need SuperCID. Someone correct me of I'm wrong but I'm gonna say you need to
fastboot oem writecid 11111111
and then head over to the S-Off thread. I wouldn't do this just yet, because I'm not 100% sure, but if someone could confirm that'd be wonderful.
Click to expand...
Click to collapse
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.

exad said:
That command may or may not work.
The good news is, if it doesn't, since you have root and aren't on a 2.14 hboot it's still super easy
If that command doesn't work, boot to the rom you're using, make sure usb debugging is enabled. If you're using CyanogenMod, you'll also have to give ADB root access in developer settings.
Open command prompt in the folder you have ADB and do
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
then you should have superCID and should be able to S-OFF using the sticky in original android dev. section
when you type the su command, it may prompt you on your phone to allow su through adb so keep that in mind.
Click to expand...
Click to collapse
Excellent, you guys are the best! So, I have CID = 11111111, S-OFF.
What's the next step to getting back on the CM10 bandwagon? Or updating hboot? Or whatever I need to do next?
Cheers,
Dave

Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app

exad said:
Run your carrier 3.17/3.18 ruu
Then flash twrp then flash cm10.1
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Here's how I tried to flash the RUU (failing):
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.945s
This booted me into CM unexpectedly
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>adb reboot-bootloader
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.062s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.835s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.936s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.020s
For some reason, if I didn't reissue the below command, subsequent flashes would fail, even though I was still in the black screen with HTC logo mode
Code:
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.060s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.421s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.514s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.024s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.060s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.132s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.234s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.059s]
finished. total time: 0.063s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot flash zip OTA_EVIT
A_UL_JB_45_S_Cingular_US_3.18.502.6_0.24p.32.09.06_10.130.32.34_release_3061616b
cty3drvawwo01k.zip
sending 'zip' (645841 KB)...
OKAY [ 24.144s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 34.232s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.065s]
finished. total time: 0.070s
C:\Users\dkabal\Downloads\android\sdk\platform-tools>
So I'm not sure what to do next. Flashing RUU doesn't seem to work. bootloader says I'm still S-OFF (whatever that means), now "RELOCKED", CID still 11111111, and hboot still 1.09.
Thanks again for taking me through this,
Dave

All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.

Use RUU not OTA, it is easier.
OTA would require stock recovery to complete and much more care with how stock things are.

RollTribe said:
All you need to do is run the RUU as was intended. It's an exe file. Plug in your phone and start the program.
Click to expand...
Click to collapse
Thanks everyone! I'm back on the CM10.1 bandwagon (with OTA updates!) and this HTC One X is working better than ever.
For other folks, here were my mistakes and stumbling blocks:
Don't use utilities intended for the HTC One X (Tegra 3) on the HTC One XL (evita). This is how I accidentally changed my CID. This might seem obvious, but when you're checking around these forums, you can frequently end up in the wrong forum.
ADB commands work when the phone is in its OS.
If the setcid command line doesn't work, use the line from exad.
Don't try and use the RUU flashing procedure (with the OTA .zip file) to flash the firmware, use the .exe file, and just execute it.
I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Back to using my now very functional HTC One X (it was on the verge of a tragic high-velocity intentional disassembly).
Cheers,
Dave

boulder_dave said:
[*]I did not (and still don't really) understand the difference and utility of RUUs, S-On/S-Off, unlocking the bootloader, hboot, ROMs, SuperCID, radios, ADB and fastboot commands.
Click to expand...
Click to collapse
There's a link in my signature that I took time to write up just for explaining these.

Fixed

And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app

ZayedQamer.zq said:
And how will his hboot go to 2.14?
Sent from my HTC One XL using xda app-developers app
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
Cause I'm confused to where you got the exe file from? Thanks
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
by running the RUU :silly: http://forum.xda-developers.com/showthread.php?t=1671237

Cannot get into recovery

Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks

I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka

jaco_lbn said:
I suggest reflashing kernel.
Wysłane z mojego HTC One S przy użyciu Tapatalka
Click to expand...
Click to collapse
Thanks, but I even cannot get into recovery

velvel said:
Thanks, but I even cannot get into recovery
Click to expand...
Click to collapse
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks

Build me a scenario
velvel said:
Hm, really strange behavior, had couple of HTC phones but never seen something like this happening.
I did run RUU (first changed cid and relocked), everything went fine (no errors), but still cannot boot. My experience so far was that if RUU runs fine, you should boot without problem. Thinking more and more that there is some hardware problem, that is causing phone to bootloop.
If anyone has any idea, I would appreciate it a lot.
Thanks
Click to expand...
Click to collapse
According to your first post, everything seems to be okay. Your drivers are seeing the phone, and the phone is recognizing its hardware.
Which recoveries did you try to flash? (TWRP, CWM)
And which version?
Have you tried to reroot the device and flash a recovery again since running the RUU?
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Sorry for all the questions, trying to establish a scenario.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.

42freelancer said:
Which recoveries did you try to flash? (TWRP, CWM)
Click to expand...
Click to collapse
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
And which version?
Click to expand...
Click to collapse
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
Have you tried to reroot the device and flash a recovery again since running the RUU?
Click to expand...
Click to collapse
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
From my experience with running an RUU, you should be able to boot right away. What were the steps you took (in order) before you ran the RUU?
Click to expand...
Click to collapse
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
Sorry for all the questions, trying to establish a scenario.
Click to expand...
Click to collapse
You are welcome and thanks for the help.
[EDIT] Also, I see that you got the initial recovery from the CM11 ROM page. You didn't happen to flash a ROM that is meant for HBOOT 2.16 did you? I sure hope not. That could be a possibility as to why you can not boot anything.
Click to expand...
Click to collapse
No, 2.15 all the time...

velvel said:
I've tried both. fastboot flash recovery imgname would work fine, but I would again finish in bootloop after restart.
TWRP_2.6.1.0_ville_4.2.2 and latest CWM
You mean reunlock, not reroot, right? I've done reunlock so I could flash recovery.
I would run:
fastboot erase cache
fastboot reboot-bootloader
and then start RUU.
You are welcome and thanks for the help.
No, 2.15 all the time...
Click to expand...
Click to collapse
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this. The phone is s-on right?
[edit] actually your security says it's off.

42freelancer said:
Try getting into bootloader and pushing the kernel this way: fastboot flash boot boot.img
you don't have to be in recovery for this.
Click to expand...
Click to collapse
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...

velvel said:
No, it didn't work, this is something more serious
I've basically tried all I could think of, from doing RUUs (3 of them), flashing boot and recovery images, going 2.15, 2.16, locking/unlocking (obviously) and finally going S-On (ok, might be stupid, but I run out of ideas).
Bottom line is that all of the flashing worked for me, I get no error, but even simple fastboot boot recovery.img brings back the bootloop.
For example:
>fastboot flash recovery openrecovery-twrp-2.6.3.0-ville-selinux.img
sending 'recovery' (8668 KB)...
OKAY [ 1.108s]
writing 'recovery'...
OKAY [ 2.059s]
finished. total time: 3.173s
>fastboot reboot
and if I hold Vol- and select recovery in bootloader I am back to bootloop.
Same thing if I try:
>fastboot boot openrecovery-twrp-2.6.3.0-ville-selinux.img
I just do not understand why I am not getting any error message when flushing and is it possible that there is something wrong with the hardware that causes this behavior...
Click to expand...
Click to collapse
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?

42freelancer said:
Sounds like you have a soft brick on your hands.
Can you boot the device at all, stock or custom ROM?
Maybe reverting to COMPLETE STOCK and starting over fresh will help?
What was the last thing you did right before you got stuck?
Click to expand...
Click to collapse
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...

velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
And here we are. Do you happen to have the old All In One Kit that became obsolete, by hasoon2000? It has the function to flash your recovery back to stock. I found two mirrors on the internet, but because of the rules, I can't post them. But they are accessible through the internets if you use the right keywords.

42freelancer said:
And here we are. Do you happen to have the old All In One Kit that became obsolete? It has the function to flash your recovery back to stock. It's probably floating around the internet somewhere. If you don't I can try to find it.
Click to expand...
Click to collapse
Tried that too, no luck. Looks like I am getting a new paperweight

velvel said:
Tried that too, no luck. Looks like I am getting a new paperweight
Click to expand...
Click to collapse
If you haven't lost all hope, try reading through this and (Return to Stock - http://forum.xda-developers.com/showthread.php?t=2164783) see if you missed anything?
You seem pretty savvy in your HTC ONE S know-how. But it's always good to follow someone else's tutorial just for guidance.

Seems issue with Recovery, bootloop is normal
velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Hi,
Bootloop is normal for ROM geeks.
In your case, it seems your phone has issue with version of Recovery. I had this issue too and found correct Recovery @ http://techerrata.com/browse/twrp2/ville ....
You can give a try..:fingers-crossed::fingers-crossed::fingers-crossed:

velvel said:
Hi all
I use HTC One X, but bought some time ago HTC One S, it worked fine for some time, but yesterday restarted and from that point I could not get it back neither to recovery nor ROM anymore. Phone bootloops and I can only get to fastboot.
I've unlocked the bootloader (*** UNLOCKED *** shows on top when in fastboot) and fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.16.666.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT24AW408183
(bootloader) imei: 352103050022322
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3695mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
When I flash recovery (fastboot flash recovery recovery.img and recovery.img is from here (http://forum.xda-developers.com/showthread.php?t=2528113 under Recovery HBOOT 2.15 Users Only ClockworkMod 6.0.4.5), it does flash ok
sending 'recovery' (8106 KB)..
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 1.856s]
finished. total time: 2.943s
but I still cannot get into recovery (phone restarts to screen with red text (for dev only...) and then restarts and bootloops.
Can anybody please help me with this?
Thanks
Click to expand...
Click to collapse
Did you check the fast boot option in the powermenue under settings? If its check it will happen like ur problem.

velvel said:
No, I cannot boot, after RUU that runs fine, phone still bootloops and only thing I can do is go into bootloader.
When you say COMPLETE STOCK, you mean RUU, right?
I was talking on the phone and phone restarted. After that I was able to boot after many tries, after restart, could not boot and than tried RUU etc...
Click to expand...
Click to collapse
Have you tried this? :
--> flash STOCK recovery via fastboot or toolkit
--> Boot to bootloader --> Factory Reset(Userdata) / Clear Stotage (SD-card) (these commands only work with STOCK recovery)

Before I got the same problem, so in Bootloader I did Factory Reset and then flash the Recovery TWRP 2.6.3.0. Now it works

[Q&A] [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp

[Q&A] [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp
Q&A for [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Stuck on Boot screen while trying to flash [ROM] InsertCoin 3.0.6 for DLXUB1 | Androi
Hi,
I tried to flash the [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme and got stuck on the boot screen.
I have TWRP 2.5 installed, Hboot 1.41.0000 and bootloader unlocked.
I simply went into recovery and installed the zip file.
Please help. It is much needed and appreciated.

Capt Vikram Sandhu said:
Hi,
I tried to flash the [ROM] InsertCoin 3.0.6 for DLXUB1 | Android 4.4.2 | HTC Sense 6 | | IC PerApp Theme and got stuck on the boot screen.
I have TWRP 2.5 installed, Hboot 1.41.0000 and bootloader unlocked.
I simply went into recovery and installed the zip file.
Please help. It is much needed and appreciated.
Click to expand...
Click to collapse
Might be because you did not use this TWRP Made by Kairi.

Thanks a ton sir. The room had been flashed and I'm living it.?
Sent from my HTC Butterfly using XDA Free mobile app

Hi,
How to S-Off my devices now. Its HTC x920d, CID: HTC_038, Rooted and other info as attached thumbnails.
Your advice is needed and much appreciated.

Capt Vikram Sandhu said:
Hi,
How to S-Off my devices now. Its HTC x920d, CID: HTC_038, Rooted and other info as attached thumbnails.
Your advice is needed and much appreciated.
Click to expand...
Click to collapse
I personally used Rumrunner to do my S-OFF. Perhaps did you enable usb debugging in developer options?

xunus said:
I personally used Rumrunner to do my S-OFF. Perhaps did you enable usb debugging in developer options?
Click to expand...
Click to collapse
Dear Xunus,
Yes I had the debugging mode on and fastboot off in the dev. options & power settings respectively. Also I don't have HTC Sync. Set up my ASUS ROG G750JMhttp://www.asus.com/in/Notebooks_Ultrabooks/ASUS_ROG_G750JM/according to this guide - http://forum.xda-developers.com/showthread.php?t=2256359 for device recognition in adb/fastboot mode after completly setting up JDK (& enviorment fully with path setting in system enviornment) and Android SDK as per this link - http://developer.android.com/sdk/index.html
But I'm in a thicker soup now. (in between my query and your reply).
Actually this device was initially my first x920d HTC_038.
On this intial device I was S-on, unlocked, maybe rooted or rooted then unrooted ( bootloader displayed *** TAMPERED *** ***UNLOCKED*** ,S-On, Hboot 1.41.00 - if required i can post the image) & definitely had a custom rom installed on it & TWRP 2.5 (don't remember which custom rom {somewhere around Android JB initial versions & subsequently upgraded to JB 4.2, but was not able to update to 4.3});
Last week I came across InsertCoin Kitkat Roms and tried to upgrade by flashing TWRP 2.8 & then flashing the zip through recovery TWRP 2.8 and got stuck at boot screen. You were kind enough to help me out - http://forum.xda-developers.com/showpost.php?p=56987280&postcount=3
Then I flashed Kairi's Twrp and flashed Insert Coin 3.0.6. Then rooted by flashing 'UPDATE-SuperSU-v2.02.zip'. My device info after this was as - http://forum.xda-developers.com/showpost.php?p=57107853&postcount=5
Then I tried to s-off through rumrunner 0.5.xx following this guide - http://rumrunner.us/instructions/ but it never finished - (attached image). Then I relocked the bootloader by fastboot oem lock command in fastboot mode. It did relock my bootloader, then i retried rumrunner through fastboot, but it came up with this - 'attached image 1'. Nnow I'm stuck with relocked bootloader, rooted device running insert coin 3.0.6, cannot boot into recovery, cannot flash PL99IMG.img/TWRP 2.7 Kairi (attached images). But my fastboot/adb is fully up and the IC rom is running good.
Kindly try to help me if you get some time.
Also I want to contribute (though am not able to contribute financially at the moment) to our forum , but sure can commit/devote minimum 6 to 10 hours a week for any job the forum/members' want or can be understudee to any member. Just bear in mind that I'm a noobie
I hope+wish to contribute+learn simultaneously to+from our forum.
Thanks.
:good:

Capt Vikram Sandhu said:
Dear Xunus,
Yes I had the debugging mode on and fastboot off in the dev. options & power settings respectively. Also I don't have HTC Sync. Set up my ASUS ROG G750JMhttp://www.asus.com/in/Notebooks_Ultrabooks/ASUS_ROG_G750JM/according to this guide - http://forum.xda-developers.com/showthread.php?t=2256359 for device recognition in adb/fastboot mode after completly setting up JDK (& enviorment fully with path setting in system enviornment) and Android SDK as per this link - http://developer.android.com/sdk/index.html
But I'm in a thicker soup now. (in between my query and your reply).
Actually this device was initially my first x920d HTC_038.
On this intial device I was S-on, unlocked, maybe rooted or rooted then unrooted ( bootloader displayed *** TAMPERED *** ***UNLOCKED*** ,S-On, Hboot 1.41.00 - if required i can post the image) & definitely had a custom rom installed on it & TWRP 2.5 (don't remember which custom rom {somewhere around Android JB initial versions & subsequently upgraded to JB 4.2, but was not able to update to 4.3});
Last week I came across InsertCoin Kitkat Roms and tried to upgrade by flashing TWRP 2.8 & then flashing the zip through recovery TWRP 2.8 and got stuck at boot screen. You were kind enough to help me out - http://forum.xda-developers.com/showpost.php?p=56987280&postcount=3
Then I flashed Kairi's Twrp and flashed Insert Coin 3.0.6. Then rooted by flashing 'UPDATE-SuperSU-v2.02.zip'. My device info after this was as - http://forum.xda-developers.com/showpost.php?p=57107853&postcount=5
Then I tried to s-off through rumrunner 0.5.xx following this guide - http://rumrunner.us/instructions/ but it never finished -http://dl-1.va.us.xda-developers.com/3/0/3/7/9/2/7/Rumrunner_Error.png?key=vEm3NkbgFBSwUpCE1I-SYQ&ts=1417206844 . Then I relocked the bootloader by fastboot oem lock command in fastboot mode. It did relock my bootloader, then i retried rumrunner through fastboot, but it came up with this - 'attached image 1'. Nnow I'm stuck with relocked bootloader, rooted device running insert coin 3.0.6, cannot boot into recovery, cannot flash PL99IMG.img/TWRP 2.7 Kairi (attached images). But my fastboot/adb is fully up and the IC rom is running good.
Kindly try to help me if you get some time.
Also I want to contribute (though am not able to contribute financially at the moment) to our forum , but sure can commit/devote minimum 6 to 10 hours a week for any job the forum/members' want or can be understudee to any member. Just bear in mind that I'm a noobie
I hope+wish to contribute+learn simultaneously to+from our forum.
Thanks.
:good:
Click to expand...
Click to collapse
I'm not really a pro on this stuff, just sharing my experience on the Butterfly. Since your current situation is a Relocked bootloader and unfortunately its still S-ON. The only thing you could do was to unlocked your bootloader again via every possible ways. I did see you tried to unlock with the 1st unlock_code.bin. But it gave you error. How about getting a new Unlock_code from HTC? Hopefully it will work this round. Without a unlocked bootloader there's pretty much nothing else you could do.( Caution: unlocking your bootloader again will wipe your data. Recommended to backup your stuffs if you need them)
If you are able to unlock your bootloader, things to do and try out.
1st: Flash Kairi's 270X twrp
2nd: Flash Kairi's reset kernel (Because its a unsecured stock kernel)
3rd: Turn on usb debug, HTC fast boot turn off
4th: Try rumrunner again.
The real developers for x920d left here in xda would be kairi_zeroblade and xXminiWHOOPERxX. Its only them that can make a change to the X920D xda community.

xunus said:
I'm not really a pro on this stuff, just sharing my experience on the Butterfly. Since your current situation is a Relocked bootloader and unfortunately its still S-ON. The only thing you could do was to unlocked your bootloader again via every possible ways. I did see you tried to unlock with the 1st unlock_code.bin. But it gave you error. How about getting a new Unlock_code from HTC? Hopefully it will work this round. Without a unlocked bootloader there's pretty much nothing else you could do.( Caution: unlocking your bootloader again will wipe your data. Recommended to backup your stuffs if you need them)
If you are able to unlock your bootloader, things to do and try out.
1st: Flash Kairi's 270X twrp
2nd: Flash Kairi's reset kernel (Because its a unsecured stock kernel)
3rd: Turn on usb debug, HTC fast boot turn off
4th: Try rumrunner again.
The real developers for x920d left here in xda would be kairi_zeroblade and xXminiWHOOPERxX. Its only them that can make a change to the X920D xda community.
Click to expand...
Click to collapse
Voila
I have just unlocked again through flashing unlock token.
Actually if you see in the image in my previous post I had erronouslt typed "fastboot unlocktocken Unlock_code.bin". It should had been "fastboot unlocktoken Unlock_code.bin".
The device is setting up for the first time as I type.
Thanks XUNUS.
Now should I follow your the steps you mentioned or first of all change my CID HTC_038 to CID: 11111111 by "fastboot oem writecid 11111111" and then continue to your steps.
Also can you provide me the link to kairi's reset kernel?
I cannot do a "fastboot oem writecid 11111111" as I'm S-On.
meanwhile I've successfully flashed Kairi's TWRP and now am searching for his Reset Kernel.

Capt Vikram Sandhu said:
Voila
I have just unlocked again through flashing unlock token.
Actually if you see in the image in my previous post I had erronouslt typed "fastboot unlocktocken Unlock_code.bin". It should had been "fastboot unlocktoken Unlock_code.bin".
The device is setting up for the first time as I type.
Thanks XUNUS.
Now should I follow your the steps you mentioned or first of all change my CID HTC_038 to CID: 11111111 by "fastboot oem writecid 11111111" and then continue to your steps.
Also can you provide me the link to kairi's reset kernel?
I cannot do a "fastboot oem writecid 11111111" as I'm S-On.
meanwhile I've successfully flashed Kairi's TWRP and now am searching for his Reset Kernel.
Click to expand...
Click to collapse
Oh ya i forgot to add that in Here it is

xunus said:
Oh ya i forgot to add that in Here it is
Click to expand...
Click to collapse
Finally --- SUCCESS in S-Off thru rumrunner (attached thumbnail)
What I did was downgraded to [ROM]|8.15.2013|NOS M7 v3.0.0|(Sense 5.0 JB 4.2.2)Butterfly - http://forum.xda-developers.com/showthread.php?t=2193912
and ran rummrunner. VOILA.
Will definitely share the steps with you in my next post.
Thanks for all your support. I owe you, NOS, rumrunner, insertcoin and xda a big 'IOU'.
:good::good:

Capt Vikram Sandhu said:
Finally --- SUCCESS in S-Off thru rumrunner (attached thumbnail)
What I did was downgraded to [ROM]|8.15.2013|NOS M7 v3.0.0|(Sense 5.0 JB 4.2.2)Butterfly - http://forum.xda-developers.com/showthread.php?t=2193912
and ran rummrunner. VOILA.
Will definitely share the steps with you in my next post.
Thanks for all your support. I owe you, NOS, rumrunner, insertcoin and xda a big 'IOU'.
:good::good:
Click to expand...
Click to collapse
Haha enjoy! Don't forget to update your firmware to the latest from HTC official. (I supposed you have Super-CID)

xunus said:
Oh ya i forgot to add that in Here it is
Click to expand...
Click to collapse
Hi Xunus,
I was running InsertCoin 3.0.6 on my x920d HTC_038, unloocked (thru HTCDev), S-Off (thru rumrunner) and rooted by flashing 'UPDATE-SuperSU-v2.02' from recovery after flashing the ROM a couple of days earlier.
I had also flashed Kairi's firmware-kk (which is for HTC_061) as I had Super CID 11111111.
There was some problem with the htc backup/restore function, so I reflashed the rom acouple of times thru recovery(TWRP 2.7 by Kairi).
I happened to flash '[ROM] FireKatN4 Deodex V5 TW 4.4.4' from http://forum.xda-developers.com/note...emely-t2916463. Which did not flashed properly; so I re-flashed IC3.0.6 thru recovery and it showed successful at the end.
Now when I tried to reboot it got stuck in bootloop.
Since yesterday I have been trying various steps:
Unlocked the bootloader thru HTCDev once again.
Flashing the firmware-kk thru oemRUU after changing the CID to 11111111 in the adroid-info file of this zip. (it gave Remote90 error and after repeating fastboot flash zip firmware-kk.zip it flashed. Although in between it said "signature checking, verified fail - Bypassing and after that successful at the end. However on my device the green bar moved only to 90% and remained there.)
Rebooted into bootloader, tried flashing the same firmware with Error :
"C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 1.975s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.011s"
Although I'm able to flash recovery img thru fastboot.
My Getvar all read as :
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Re flashed IC3.0.6 thru recover once again. when rebooting, get stuck in bootloop again.
PLEASE HELP
P.S. I have some pics also if required.
I am also S-Off, Relocked/Unlocked and not sure about root status.

Please Help
Here's what I repeated. Step - by -step
1. First of all got the getvar all details:
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
QUERY : Should I be concerned regarding
i. (bootloader) platform: HBOOT-8064
ii. (bootloader) hbootpreupdate: 11, because in Kairi's firmware zip the android-info reads
1) CID H_061 (I changed it to 11111111)
2) hbootpreupdate:3 (This I did not change)
2. Relocked the boot loader (after checking if I could unlock it again through the previous code.bin. I did this successfully but without Selecting 'Yes' option at the end of the process on my device)
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.246s
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.148s
NOTE: Both the times device booted into bootloop.
3. Flashing Kairi's firmware-kk.zip through RUU
a. Rebooted in RUU
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.053s]
finished. total time: 0.055s
b. Flashed firmware-kk (remember the file CID changed to 11111111
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.007s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.490s
C:\Fastboot>
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-2,0
(bootloader) [RUU]WP,sbl1-2,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,8
(bootloader) [RUU]UZ,radio,13
(bootloader) [RUU]UZ,radio,22
(bootloader) [RUU]UZ,radio,31
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,58
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,71
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 10.628s]
finished. total time: 12.650s
Note: In the device the green bar did not reach the end. And did not reboot.
c. 'fastboot reboot bootloader' - command not recognized
d. 'fastboot reboot' - rebooted into bootloop
e. Manually booted the device into bootloader.
4. Getvar all - Same as previous.
5. Unlocked the bootloader.
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.149s
Note: The device automatically rebooted into bootloop yet again. Manually rebooted to bootloader it shows *** UNLOCKED ***
6. Re flashed Kairi's TWRP
C:\Fastboot>fastboot flash recovery TWRP-2-7-Kairi.img
target reported max download size of 1514139648 bytes
sending 'recovery' (10572 KB)...
OKAY [ 1.564s]
writing 'recovery'...
OKAY [ 0.977s]
finished. total time: 2.546s
7. Entered Recovery from the device. (To install Kairi's reset kernel) Did not wipe cache/dalvik after installation
Note: - 'adb reboot bootloader' did not work at recovery, thou
C:\Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA34HPN00627 recovery
C:\Fastboot>adb reboot bootloader
8. Entered bootloader thru TWRP options on the device.
9. Flashed boot.img (extracted from InsertCoin 3.0.6 Zip). Did not erase cache after this.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.747s]
finished. total time: 1.677s
10. Entered recovery to install InsertCoin Rom.
a. Selected - Perform a full wipe in the installer.
b. Deselected all the checkmarks (for HTC + Google)
c. Selected - 'Enable Cache - All times' in the end
d. Install. (Please refer the attached screen shots)
e. Reboot your Device now from the installer. (HOPE TO boot into android. Fingers crossed).
f. Again Bootloop.
g. Rebooted into bootloader
h. Fastboot the boot image once again erased cache after that.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.745s]
finished. total time: 1.675s
C:\Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.070s
I. Still in bootloop.
Please help/advice.

Please share the link to the HTL21 ROM with NFC support...
Please share the link to the HTL21 ROM update with NFC support... Using now Butterfly_Sense6.0_KK4.4.2_Soul16.0
Thank you!

my dlxu x920e japan (i think version) cant get the insertcoin 2.4.0 release to work can you post how you did it

Lollilop update for Butterfly
Is there any possibility of getting Lollilop update via Insertcoin Rom for M7 on Butterfly?
Thanks

No !
jayc007 said:
Is there any possibility of getting Lollilop update via Insertcoin Rom for M7 on Butterfly?
Thanks
Click to expand...
Click to collapse
No ! i dont think so.. I earlier talk with official mentor of IC ROMS. and he told me that development for x920d has been stopped because they dont have a Butterfly now.

lollipop or at least kk 4.4.4 update for htc butterfly
i am running IC 3.0.6 its running ok, but i have some GPU lag in some games that i didnt have issues with when i was running htc stock 4.3 it not a deal breaker everything else works better, but i was hoping IC update this ROM to a newer version like on HTC DNA, at least KK 4.4.4

thanks
thanks for ur sharing.

Pattern lock (factory defaults / official 3.34.401.1 flash)

Hi all,
Maybe someone could push me in the right direction here. I unlocked my HTC U11 and went searching for a good CFW with MHL support. Sadly many don't have decent MHL support, thanks Google! I went into recovery steps, locked the bootloader and flashed official 3.34.401.1 rom. That went fine, but now the phone is stuck at the pattern screen.
Phone works fine, but the pattern is not set by me, almost as if the stock firmware has some secret pattern. It won't ask me to setup my google account and factory defaults doesn't fix the issue.
Current rom file: 2PZCIMG_OCEAN_UHL_P90_SENSE10GP_MR_HTC_Europe_3.34.401.1_Radio_8998-200321-1905141529_release_signed.zip
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Thanks in advance!

ristodesign said:
Device info:
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560000000
(bootloader) serialno: xxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxx
(bootloader) version-main: 3.34.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-200321-1905141529
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: HTC__034
Click to expand...
Click to collapse
To the one/those answering:
How can one have 0 slots?
That's odd, isn't it? I mean there are a/b partitioned devices and 'a' partioned devices out there.
So the slot-count is either 2 (a/b) or 1 (a).
To @ristodesign: Before flashing you had no pattern? And you did a factory data reset with your recovery?

Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)

ristodesign said:
Hi, yes. I tested LineageOS and Goole PixelExperience, but should have known there was no MHL support. Then I tried Viper and LeeDroid, but those didn't enable Wifi somehow.
Then decided to get back to the stock ROM provided by Ziand: https://androidfilehost.com/?fid=1899786940962575313
Locked the bootloader and renamed the rom file to 2PZCIMG.zip so I could restore from booting in download. File was accepted and everything went back to normal. Got a welcome screen, was forced to enable wifi, then suddenly some pattern lock, which does not give any option to escape. Perviously used patterns are certainly not working.
Factory reset does not clear the pattern lock. Which makes me quite unique I guess. ;-)
Click to expand...
Click to collapse
Maybe you can try to boot twrp and see if it asks to decrypt?
The thing is: Passwords, pins, patterns etc. should be stored in the userdata partition. If you wipe this partition, the pattern should be gone.
However, if you manage to boot twrp and to have the userdata partition decrypted (go to /data and see if those entries aren't "randomized" letters), we should be able to delete this manually.
Else I'd like to know whether that pattern has been coded into the update zip you applied... Don't know how to accomplish that, however. But I'll see if I figure out something for the case twrp doesn't work.

You could also try another file like this one from here: https://htcstockrom.com/htc-u11

Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.

ristodesign said:
Will try to get trwp back on the device. It was removed and USB debugging probably disabled.
I did try the rom at https://htcstockrom.com/htc-u11 , after all those Visual C++ x86/x64 fixes it finally worked to start, but at the end it wouldn't accept to downgrade 3.34.401.1 to 2.42.617.7.
Click to expand...
Click to collapse
I see.
You only need to boot twrp temporarily, no need to flash it. Just do:
Code:
fastboot boot twrp.img
EDIT: What if you reflash LineageOS and then the older firmware mentioned above?
LineageOS should allow downgrades.

Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.

ristodesign said:
Good idea, i tried with this result:
downloading 'boot.img'...
OKAY [2.4sec]
booting...
(Then it stops)
Phone screen shows:
Flash image succes
Start downloading (1/1)
It stops there.
Click to expand...
Click to collapse
Oh, well...
That's strange... Then go for the method you already know.
What did you do earlier to flash twrp? Same command but "flash boot"?
EDIT:
I think you flashed it using
Code:
fastboot flash recovery twrp.img
right?
If so, maybe you can boot it somehow similar like this:
Code:
fastboot boot recovery twrp.img
.

Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.

ristodesign said:
Earlier I had to unlock the phone with the HTC Dev website. I created an Unlock_code.bin file. But if I try to flash now it will not accept.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 1.002s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
So USB debugging and the OEM lock seems to have set to default by flashing the stock rom.
Click to expand...
Click to collapse
If you do
Code:
fastboot getvar all
do you get something like this?:
(bootloader) unlocked:yes
Click to expand...
Click to collapse

Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)

ristodesign said:
Nope, it does not. When I try to flash it states that the bootloader is locked. The phone screen shows:
HTC download mode
*** RELOCKED ***
*** PRODUCTION ***
htc_ocnuhl PVT S-ON
yada yada yada... ;-)
Click to expand...
Click to collapse
Well, maybe you should research how to unlock an relocked bootloader.
I heard that some bootloader won't unlock again after relocking, which is why I never relocked my devices bootloader...

Hehe, yes it might be not too smart but it was the fastest solution as I could not find a working MHL CFW. I'll give my kids some money if they can find the pattern lol.