Related
Hey.
I have decided to share the lastest firmware.zip package from HTC for One S (Snapdragon S3, VilleC2). Follow the instructions, so you will update your hboot, radio, recovery, etc.
WARNING!
I am not responsible for bricked devices, anyway I can help you with fixing them if they are still alive
Don't repack/unpack/change content of firmware.zip or it will simply get broken! Such packages are signed with HTC's unique signature which details needed to hack unfortunately hasn't been leaked yet (and they probably won't)
You have to check if your CID* is compatibile. If it's not, firmware won't be updated.
Type:
Code:
fastboot getvar all
and look for your "CID".
Click to expand...
Click to collapse
DOWNLOAD FIRMWARE.ZIP
Instructions:
Make sure that you have all fastboot drivers
Relock your bootloader (if it is unlocked) by inputing the following method:
Code:
fastboot oem lock
Reboot to hboot and go into fastboot mode
Flash downloaded firmware.zip by inputing the method below:
Code:
fastboot flash zip firmware.zip
Wait until flashing finishes and reboot
SUPPORTED CIDS:
HTC__001
HTC__E11
HTC__304
HTC__A48
HTC__A07
HTC__M27
HTC__032
HTC__016
HTC__203
HTC__102
HTC__405
HTC__Y13
Click to expand...
Click to collapse
Congratulations, you can now flash JB custom ROMs or stock one which you can find in THIS thread! :victory:
Click "thanks" button if I helped, it is the best thing you can reward me on XDA.
*CID - Carried ID Number
this will update hboot?
Sent from my One S C2
yes, it should
bilal_liberty said:
yes, it should
Click to expand...
Click to collapse
is it neccesary to update hboot and what is diference between 2.11 and 3.19 hboot?
Sent from my One S C2
s0kY said:
is it neccesary to update hboot and what is diference between 2.11 and 3.19 hboot?
Sent from my One S C2
Click to expand...
Click to collapse
I cant see any visible difference
There is error in one step. HBOOT will not allow flashing of firmware.zip if device is not in this mode:
fastboot oem rebootRUU
At least not HBOOT 3.01
Work for Cid :BSTAR301
kayserxx said:
Work for Cid :BSTAR301
Click to expand...
Click to collapse
Is that a question or an answer? In any case? Would it Work for CID: BSTAR301? We in Latin America are seriously being left behind here.
s0kY said:
this will update hboot?
Sent from my One S C2
Click to expand...
Click to collapse
Yes, but please read OP first, then ask
maxio1998 said:
Yes, but please read OP first, then ask
Click to expand...
Click to collapse
Did you read what I wrote about flashing zips on One S C2? fastboot oem rebootRUU needs to be issued before trying to flash zip because otherwise HBOOT will deny it (at least HBOOT 3.01).
After that HBOOT will allow flashing firmware.zip but it will fail for the first time with a line to retry immediately and then will work (like on other devices).
I mean, do you even have this phone or not? This is basic stuff, add that to the original post.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.01.0000
(bootloader) version-baseband: 16.11.20.24_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.19.401.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SHXXXXXXXX
(bootloader) imei: 35XXXXXXXX
(bootloader) meid:
(bootloader) product: villec2
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PJ4020000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3925mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
How can I flash that zip for my CID 044? Coz I can't change to supercid and my phone is s-on! And I heard that there's isn't a way to s-off yet ,so flashing this zip is seem to be the only way..
Help me guys
If your CID is not on OPs list there are a bunch of OTAs for other CIDs in a thread on the general board - http://forum.xda-developers.com/showthread.php?t=2200930
If you see yours there just download the OTA, extract the firmware.zip file from it and follow OPs instructions
sending 'zip' (27598 KB)...
OKAY [ 3.471s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 7.791s
i am on cid HTC_032
s0kY said:
sending 'zip' (27598 KB)...
OKAY [ 3.471s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 7.791s
i am on cid HTC_032
Click to expand...
Click to collapse
Like I already said:
"There is error in one step. HBOOT will not allow flashing of firmware.zip if device is not in this mode:
fastboot oem rebootRUU
At least not HBOOT 3.01 "
It will fail for the first time with message to do it immediately after possible soft-reboot but then it will work. It's not a bug, it's a feature. So, you first issue fastboot oem lock, then this.
But original poster is not listening and editing first post.
rasputyn said:
Like I already said:
"There is error in one step. HBOOT will not allow flashing of firmware.zip if device is not in this mode:
fastboot oem rebootRUU
At least not HBOOT 3.01 "
It will fail for the first time with message to do it immediately after possible soft-reboot but then it will work. It's not a bug, it's a feature. So, you first issue fastboot oem lock, then this.
But original poster is not listening and editing first post.
Click to expand...
Click to collapse
i was in fastboot oem rebootRUU mode and nothing i triend 3 times in a row and i got the same message
s0kY said:
i was in fastboot oem rebootRUU mode and nothing i triend 3 times in a row and i got the same message
Click to expand...
Click to collapse
That's impossible. Only if you first didn't do fastboot oem lock. After that you do fastboot oem rebootRUU
rasputyn said:
That's impossible. Only if you first didn't do fastboot oem lock. After that you do fastboot oem rebootRUU
Click to expand...
Click to collapse
maybe because i have wiped rom in recovery ?
Sent from my HTC One S using xda app-developers app
i have flashed it again and it works
Successful!!! Thank you!
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
[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.
i flashed my a9 with SenseO V0,4 my firmware is 1.10 and the rom need 1.56
now my phone is only works with cm roms like mokee
i need a solution i tried to relock bootloader and flash stock ruu zips with the same cid not work
the names of the ruu i tried
2PQ9IMG_HIA[email protected]51002.3_29.05_F_release_454007_combined_signed
2PQ9IMG_HIA_AER[email protected]60122.4_43.05_F_release_469200_signed
i get the same error
C:\adb>fastboot flash zip rom.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (126573 KB)...
OKAY [ 8.751s]
writing 'zip'...
(bootloader) HOSD CL#635503
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 9.765s
my cid information
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) imei: 352636073422391
(bootloader) version-main: 1.10.401.7
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: HTC__J15
all:
finished. total time: 0.021s
please help i want to flash SenseO V0,4 or stock rom i hated stuck on cm roms
please try first: rename 2PQ9IMG_HIA_AERO_UHL_M60_SENSE7GP_MR_HTC_Europe_1. [email protected]_43.05_F_relea se_469200_signed
to 2PQ9IMG.img and put it to an SD-Card (first level, not into a folder) - plug in this sd-card.
If you boot into download-mode you will be asked if you want to flash this RUU. Volume up to start flashing.
Please report (do not write just error)
JochenP said:
please try first: rename 2PQ9IMG_HIA_AERO_UHL_M60_SENSE7GP_MR_HTC_Europe_1. [email protected]_43.05_F_relea se_469200_signed
to 2PQ9IMG.img and put it to an SD-Card (first level, not into a folder) - plug in this sd-card.
If you boot into download-mode you will be asked if you want to flash this RUU. Volume up to start flashing.
Please report (do not write just error)
Click to expand...
Click to collapse
thanks pro solved
i was flashing 2PQ9IMG.zip in relocked bootlader i try flashed after reunlock bootloader and its work now thanks for helping
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: FA79G0500641
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 358182081003810
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
(bootloader) cid: BS_US001
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Delete your SN and Imei.
Wysłane z mojego HTC U11 przy użyciu Tapatalka
skinny1439 said:
First to admit I did something stupid. I am looking for anyone to help me.
Long story short I think I have locked my bootloader. I dont know if i have the stock bootloader or twrp.
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) kernel: lk
(bootloader) product: htc_ocnwhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) version-main: 2.31.617.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 8998-002772-1711021119
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC50000
all:
finished. total time: 0.005s
I cant get into the twrp bootloader menu and I tried to use the RRU from htc to reload my phone. I get a 155 error. I tried to unlock the bootloader again with the htc ulock_code.bin error message
sending 'unlocktoken' (0 KB)...
OKAY [ 1.001s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.199s
I am at a loss on what to do. Am I screwed? I am within the htc 30 day window but dont think they will accept my phone.
Click to expand...
Click to collapse
Skip again the bootloader unlocking procedure via htcdev
HTC U11 & Tapatalk
linar10 said:
Skip again the bootloader unlocking procedure via htcdev
Delete imei and serialno
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
HTC u11 fails to boot.
skinny1439 said:
Thanks I was able to unlock the bootloader via the htc dev. I just had to redownload the unlock key.
Click to expand...
Click to collapse
I have a new problem.
I will start at the beginning. I was running stock htc oreo. I really wanted to install viperu 1.7. I assumed that I needed to reinstall nougat. I attemped to use the htc ruu to roll back. This failed. I booted into twrp and performed a wipe and restore to a known good nougat backup. When I rebooted the device started to boot gets past the htc logo and the shuts off. Thinking that something failed I rebooted into twrp and attempted to reinstall a stock zip. This fails to install. I wiped again and installed viperu 1.7 everything installs properly per the viper install guide. When the phone reboots it starts to install the apps. It finishes but shuts off. I connected it to a charger and booted the phone and attempted to boot but shuts off.
Can someone please tell me what I have done wrong and how to fix it.
thanks in advance.
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
linar10 said:
Without s-off, the older ruu will not work. Probably older rom on newer firmware may not work. Download stock backup 2.xx.xxx.x and restore in twrp and do not forget full wipe before restoring backup
HTC U11 & Tapatalk
Click to expand...
Click to collapse
Do you have a stock backup 2.xx.xxx.x or know where I can get one. I looked online but they dont have 2.x on the list.
My phone is 2PZC50000 BS_US001 WHL (Single SIM) US Unlocked.
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
IT works again!!
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
skinny1439 said:
You saved me. I am extremely grateful of your knowledge. I thought I flushed 700 buck down the drain.
Whats the best way to revert back to nougat so I can flash to viperu 1.7. Right now I am on 2.31.617.2 from the backup you sent me to in the link. I do need to root the phone but have not attempted yet. I was planning to root the phone at the same time as installing viperu. Much thanks again.
Click to expand...
Click to collapse
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
linar10 said:
RUU and backup
https://forum.xda-developers.com/showthread.php?p=74694695
HTC U11 & Tapatalk
Click to expand...
Click to collapse
You're the man.
henslo said:
Can't roll back to 7.1.1 yet. You need to be S-Off and Sunshine isn't fully working on Oreo at this time.
But there is a ViperU Oreo Rom available now. If you want, to just flash it and sick with 8.0.
Click to expand...
Click to collapse
Thanks for all your help. I really appreciate it!
skinny1439 said:
Thanks for all your help. I really appreciate it!
Click to expand...
Click to collapse
The viper rom for oreo doesn't really work right yet and they're working on it. I'm using stock with magisk beta 14.5. Substratum works a bit too.