Database Info

Sensation reboots

Hi, I bought a used sensation.
This sensation have a unlock bootloader and I make S-OFF Juopunutbear an super CID (11111111).
Then use superuser to root, all ok.
The problem is when i flash a Custom Rom the phone restarts every 4 minutes.
I try with more roms: ViperS, Revolution HD, MIUIv4, Blitz, HyperSensation, badosp-experimental, ICSense 3.6, aokp_pyramid_milestone, CoinDroid, OrDroid ... and restarting ...
I try also change RIL, RADIO and Kernel; The RADIO to fastboot cant install, error. The kernel 3.2 install fine and the RIL 4.0.0013HMQ install fine.
I've also tested put silver paper on the conections to the phone with the cover and put a cardboard in the battery to hold, any change, restart always ...
If i put the archive PG58IMG.zip or others, in the root of sdcard, to flash whit bootloader, the telephone dont recognize any
The data of my telephone:
Bootloader: 1.27.0000
RADIO: 11.69.3504.00P_11.22.3504.07_M
RIL: 4.0.0013HMQ
CID: 11111111 but CID Getter say HTC_032
Open ADSP- v02.6.0.2226.00.0131
ENNC- Boot
I do not know what else to do, any ideas?
Thanks
P.D: Sorry for my english, I'm Spanish

vitoces said:
Hi, I bought a used sensation.
This sensation have a unlock bootloader and I make S-OFF Juopunutbear an super CID (11111111).
Then use superuser to root, all ok.
The problem is when i flash a Custom Rom the phone restarts every 4 minutes.
I try with more roms: ViperS, Revolution HD, MIUIv4, Blitz, HyperSensation, badosp-experimental, ICSense 3.6, aokp_pyramid_milestone, CoinDroid, OrDroid ... and restarting ...
I try also change RIL, RADIO and Kernel; The RADIO to fastboot cant install, error. The kernel 3.2 install fine and the RIL 4.0.0013HMQ install fine.
I've also tested put silver paper on the conections to the phone with the cover and put a cardboard in the battery to hold, any change, restart always ...
If i put the archive PG58IMG.zip or others, in the root of sdcard, to flash whit bootloader, the telephone dont recognize any
The data of my telephone:
Bootloader: 1.27.0000
RADIO: 11.69.3504.00P_11.22.3504.07_M
RIL: 4.0.0013HMQ
CID: 11111111 but CID Getter say HTC_032
Open ADSP- v02.6.0.2226.00.0131
ENNC- Boot
I do not know what else to do, any ideas?
Thanks
P.D: Sorry for my english, I'm Spanish
Click to expand...
Click to collapse
try flashing the latest universal 3.33 firmware
use this post for reference
http://forum.xda-developers.com/showpost.php?p=29528198&postcount=5728 (sorry for the postception (post inside post ))

ganeshp said:
try flashing the latest universal 3.33 firmware
use this post for reference
http://forum.xda-developers.com/showpost.php?p=29528198&postcount=5728 (sorry for the postception (post inside post ))
Click to expand...
Click to collapse
Thanks, but .. how i install PG58IMG.zip ? the Bootloader does not recognize none

vitoces said:
Thanks, but .. how i install PG58IMG.zip ? the Bootloader does not recognize none
Click to expand...
Click to collapse
check the post ive linked again ..there ive attached another post explaining flashing the PG58iMG file via fastboot commands

ganeshp said:
check the post ive linked again ..there ive attached another post explaining flashing the PG58iMG file via fastboot commands
Click to expand...
Click to collapse
lets go.
sending 'zip' (14228 KB)... OKAY [ 3.391s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 9.922s
:crying:
Trying ... now ..
INFO[RUU]UZ,radio,83
INFO[RUU]UZ,radio,92
INFO[RUU]UZ,radio,99
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,73
INFO[RUU]WP,radio,100
OKAY [ 40.188s]
finished. total time: 43.656s
Turn on sensation
The radio and hboot change:
Hboot 1.29.0000
RADIO: 11.24A.3504.31_M

vitoces said:
lets go.
sending 'zip' (14228 KB)... OKAY [ 3.391s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 9.922s
:crying:
Click to expand...
Click to collapse
thats not an error (wait you did downloaded the 3.33 universal firmware only right?)
any ways flash the zip again
fastboot flash zip PG58IMG.zip and let me know this time

ncemossi sometimes
ganeshp said:
thats not an error (wait you did downloaded the 3.33 universal firmware only right?)
any ways flash the zip again
fastboot flash zip PG58IMG.zip and let me know this time
Click to expand...
Click to collapse
YESSS!!! THAT THIS!! Thanks!
I did not know that method to PG58.IMG.
Thaks, solved

[HTC ONE M7] Collection of Firmware up to 6.06.401.1 modified HBOOT, (No Red warning)

Hi Everyone,
OP UPDATE: DON'T reboot your device until you get a success message, also double check you understand EVERY STEPS before trying it out. I AM NOT RESPONSIBLE FOR ANYTHING IF YOU MESS UP THE STEPS...!!
This firmware is WITH OUT the development disclaimer overlay:
This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission.
Failure to comply may
lead to legal action.​
** With Latest Radio **
Upgrade your HTC Sync to 3.1.13.0 if you flash this firmware..
DOWNLOAD Firmware 6.06.401.1, NO Red Warning, --md5: -- dd9f5fb8416de0fb6f533ce3e40bbafe
These Firmwares DO NOT delete the contents in SD Card. But please make a back up before flashing for safety.
**N.B. Thanks and Donations are most welcome **
Requirements for flashing: S-OFF
Please Follow the instructions carefully!! Otherwise you may BRICK your device.
Please note that it is for the HTC One M7 UL Only. Not Tested with Sprint Version!!
You may change the MID (at your own risk) in the android-info.txt attached and replace the one inside the firmware.zip if you have another MID.
If you have Super CID "11111111", you don't need to worry about the CID lists inside the android-info.txt file
​
DON'T FORGET TO CLICK THANKS IF YOU FIND THIS THREAD USEFUL.
Dear All,
I have noted a lot downloads of the firmware and most of them just don't even bother clicking thanks :silly:
I appreciate your encouragements and appreciation for my work so that it will give motivation to keep all you updated.
Thanks a lot for everyone contributed..
Thanks @thoughtlesskyle for this video tutorial http://youtu.be/ybu7fZa41so
​
To Check ModelIDs:
Code:
adb reboot bootloader
----- Mobile reboots---
Code:
fastboot getvar all
----Check the following line in the command window: INFOmodelid: PN0714000----
Steps for flashing:
-----
Windows users, need to do these steps first:
- move the file you downloaded and renamed (firmware.zip) to the C:\adb\ folder.
- next, in the C:\adb\ folder hold down SHIFT key and RIGHT-CLICK and select "Open command window here".
-----
Next, plug in phone to PC and type this in terminal/command prompt:
Code:
adb reboot bootloader
----- Mobile reboots---
Now type:
Code:
fastboot reboot-bootloader
After that, type:
Code:
fastboot oem rebootRUU
Note: You should see a silver HTC logo come up on your phone after executing this command.
Note: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
fastboot flash zip C:\adb\firmware.zip
Got this:
Code:
sending 'zip' (30367 KB)... OKAY [ 6.184s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] flushing...
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,99
INFO[RUU]WP,hboot,100
INFO...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 8.090s
Repeat the same command: !! IMPORTANT !! -- PLEASE WAIT A FEW SECONDS BEFORE ISSUING THE COMMAND AGAIN; Otherwise the cmd prompt will be non-responsive saying "Sending data...", If this happens, try disconnecting the USB cable and reconnect.
Code:
fastboot flash zip C:\adb\firmware.zip
You will see this:
Code:
sending 'zip' (30367 KB)... OKAY [ 3.277s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[adsp] unzipping & flushing...
INFO[RUU]UZ,adsp,0
INFO[RUU]UZ,adsp,18
INFO[RUU]UZ,adsp,30
INFO[RUU]UZ,adsp,41
INFO[RUU]UZ,adsp,52
INFO[RUU]UZ,adsp,64
INFO[RUU]UZ,adsp,75
INFO[RUU]UZ,adsp,86
INFO[RUU]UZ,adsp,97
INFO[RUU]UZ,adsp,100
INFO[RUU]WP,adsp,0
INFO[RUU]WP,adsp,100
INFO...... Successful
INFOstart image[cir] unzipping & flushing...
INFO[RUU]UZ,cir,0
INFO[RUU]UZ,cir,100
INFO...... Successful
INFOstart image[pg2fs_spcustom] unzipping & flushing...
INFO[RUU]UZ,pg2fs_spcustom,0
INFO[RUU]UZ,pg2fs_spcustom,31
INFO[RUU]UZ,pg2fs_spcustom,57
INFO[RUU]UZ,pg2fs_spcustom,82
INFO[RUU]UZ,pg2fs_spcustom,100
INFO...... Successful
INFOstart image[rpm] unzipping & flushing...
INFO[RUU]UZ,rpm,0
INFO[RUU]UZ,rpm,100
INFO[RUU]WP,rpm,0
INFO[RUU]WP,rpm,100
INFO...... Successful
INFOstart image[sbl1-1] unzipping & flushing...
INFO[RUU]UZ,sbl1-1,0
INFO[RUU]UZ,sbl1-1,100
INFOsignature checking...
INFOverified fail
INFO..... Bypassed
INFOstart image[sbl1-2] unzipping & flushing...
INFO[RUU]UZ,sbl1-2,0
INFO[RUU]UZ,sbl1-2,100
INFOsignature checking...
INFOverified fail
INFO..... Bypassed
INFOstart image[sbl1-3] unzipping & flushing...
INFO[RUU]UZ,sbl1-3,0
INFO[RUU]UZ,sbl1-3,100
INFOsignature checking...
INFO[RUU]WP,sbl1-3,0
INFO[RUU]WP,sbl1-3,100
INFO...... Successful
INFOstart image[sbl2] unzipping & flushing...
INFO[RUU]UZ,sbl2,0
INFO[RUU]UZ,sbl2,100
INFO[RUU]WP,sbl2,0
INFO[RUU]WP,sbl2,100
INFO...... Successful
INFOstart image[sbl3] unzipping & flushing...
INFO[RUU]UZ,sbl3,0
INFO[RUU]UZ,sbl3,100
INFO[RUU]WP,sbl3,0
INFO[RUU]WP,sbl3,100
INFO...... Successful
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO..... Bypassed
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO...... Successful
INFOstart image[tz] unzipping & flushing...
INFO[RUU]UZ,tz,0
INFO[RUU]UZ,tz,100
INFO[RUU]WP,tz,0
INFO[RUU]WP,tz,100
INFO...... Successful
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,6
INFO[RUU]UZ,radio,11
INFO[RUU]UZ,radio,17
INFO[RUU]UZ,radio,23
INFO[RUU]UZ,radio,28
INFO[RUU]UZ,radio,34
INFO[RUU]UZ,radio,40
INFO[RUU]UZ,radio,46
INFO[RUU]UZ,radio,52
INFO[RUU]UZ,radio,59
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,75
INFO[RUU]UZ,radio,81
INFO[RUU]UZ,radio,87
INFO[RUU]UZ,radio,92
INFO[RUU]UZ,radio,99
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,23
INFO[RUU]WP,radio,46
INFO[RUU]WP,radio,69
INFO[RUU]WP,radio,92
INFO[RUU]WP,radio,100
INFO...... Successful
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO...... Successful
OKAY [ 54.864s]
finished. total time: 58.143s
Note:The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
fastboot reboot
Then I went back to the bootloader mode (after the phone reboots successfully):
If Boot-Loop Occurs*:
Code:
fastboot erase cache
Restart in boot-loader to check whether everything is fine*:
Code:
adb reboot bootloader
--Phone reboots into bootloader--
Code:
fastboot getvar all
The resulting variable may look like this:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.06.401.1
INFOversion-misc: PVT SHIP S-OFF
INFOserialno: HT34LXXXXXXX
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0714000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4259mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-01dc707e
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Firmware 5.11.1540.9, NO Red Warning, --md5: -- 6734d095499a72519335bb894503708f
Firmware 4.19.401.11, NO Red Warning, --md5: -- 8f3a59cdbcc84b9ff2319495eee6ae98
Firmware 4.19.401.9, NO Red Warning, --md5: -- DE93220BEB19CA1FCB3FDF407F2B3D3F
Firmware 4.19.401.8, NO Red Warning, --md5: 30772981922e19437085c92adbea9658 --
Firmware 4.19.1540.4, NO Red Warning, --md5: 49dbb024b28a17383da35593d6cbc860 --
Firmware 4.06.1540.3, NO Red Warning ** --md5: 227c88abad17dba0561a91ad6d353373 --
Firmware 4.06.1540.2, NO Red Warning ** --md5: c9b68c6a17ae323112c99ce0550dba38 --
Previous firmware with modified HBOOT,
Firmware 3.62.401.1 with NO Red Warning are below.
Firmware 3.62.401.1 for MODEL ID: PN0710000 NO Red Warning --md5: 728e3dc18abde0fd10835376332f81ec --
Firmware 3.62.401.1 for MODEL ID: PN0711000 NO Red Warning -- md5: 7fb62e47f347ae05baf4dd821b497752 --
Firmware 3.62.401.1 for MODEL ID: PN0712000 NO Red Warning --md5: 7ab96062ff848550a45dd035967adc83 --
Firmware 3.62.401.1 for MODEL ID: PN0713000 NO Red Warning -- md5: 6bcb6dd99da4d4c73a24725b814e161b --
Firmware 3.62.401.1 for MODEL ID: PN0714000 NO Red Warning -- md5: 6b2d5bf151ddf6ebbb7c6303f6db1889 --
Firmware 3.57.401.500 for MODEL ID: PN0714000
Firmware 3.57.401.500 for MODEL ID: PN0713000
Firmware 3.57.401.500 for MODEL ID: PN0712000
Firmware 3.57.401.500 for MODEL ID: PN0710000
Firmware 3.22.1540.1 : MODEL ID: PN0710000
Firmware 2.24.401.1 : MODEL ID: PN0710000 for Android 4.2.2
FIRMWARE FAQ:
Q: Do I need S-OFF for firmware flashing?
A: YES, It is a must.
Q: Do I need to update my firmware?
A: NO, but updating firmware ensures optimal phone performance.
Q: Does it matter when I flash the firmware (before or after new ROM install)
A: No.
Q: Will updating the firmware erase my SD card or Apps?
A: No, The firmware files provided here does not erase none of those.
Q: If I only flash the ROM, will I get updated to the latest firmware?
A: No. You must flash the firmware separate in most cases.
Q: Can I install a UL edition firmware on a U edition phone?
A: Yes (may be), but you won't have LTE or may experience some other incompatibilities.
Possible Errors while flashing:
If it says "FAILED" do not immediately reboot the device. If you reboot with a FAIL it could brick your device! Listed below error are safe to reboot:
If you encounter one of them, you can just reboot. Nothing changes.
- 12 signature fail (means a signed firmware package is required. This would only happen with S-ON phones though. but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means the MODEL ID in the android-info.txt does not match with your device. you can reboot the device. You may change the MID manually in the android-info.txt at your own risk.)
- 42 Wrong Customer ID (means you need to include the CID of your device in the android-info.txt or change the CID to superCID.)
- 99 UNKOWN (is not yet clear but safe to reboot)
DON'T reboot until you get a success message if you get an error bellow:
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions. Don’t reboot before repeating the command. If the command window stuck in the middle for a long time, wait for a few minutes and please unplug the USB and replug it again. Repeat the command again. DON'T reboot until you get a success message.)​
Editing android-info.txt​​
- Use an Editor that doesn't doesn't alter the linebreaks. Don't use Windows Notepad. Use Notepad++
- Only one MID can be in the file.
- CID's can easily be added or removed- one per line
To Get SUPERCID​​
Code:
fastboot oem writecid 11111111
RUUmode:​​
RUU Mode is the mode used for RUU flashes by HTC. It is different from the normal fastboot. You must flash the firmware only in RUU Mode. The RUU mode can be identified by the black background with only a silver HTC logo and if a command is being active a green progress bar will show the progress of any command being excecuted.
For Further Reading​Some more useful threads that might be helpful to you:
- Mike1986’s Firmware thread
- Vomer’s ultimate guide thread
- hes_theone64’s radio flash guide for recovery
- chrisch1974's HOW-TO Flash a custom splash screen
- Sneakyghost's Firmware Flashing & Hboots red warning gone thread
- HTC ONE Partition List:
- Mike1986 Partition explanation:
​
You must be aware that writing to the bootloader -partition increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested. I will not accept any responsibility. The method itself is developed by Google and HTC, i have only adapted it and you execute it. You understand that you should not do it if you are not willing to accept this risk.​
For More info, about Super CID, S-OFF and Firmware update process, check this thread:
[Guide] Vomer's Ultimate AIO - S-OFF, SuperCID, Firmware Upgrade & Custom Recovery
Thanks @vomer and @Sneakyghost

Thanks for this. But does this firmware package wipe SD contents?

Is it safe to use 1.44 hboot with 3.57 firmware and a 4.3 Rom?
Sent from my HTC One using XDA Premium HD app

Thanks for this, works. Not much more I can say.

Huey85 said:
Thanks for this. But does this firmware package wipe SD contents?
Click to expand...
Click to collapse
No, firmware never wiped my SD card yet. I have flashed several firmware zips since I have my one and it never wiped anything!
Only thing is to make sure you are s-off before you flash the zip as it might contain a exploit fixed hboot.
Renovated.

jonas2295 said:
No, firmware never wiped my SD card yet. I have flashed several firmware zips since I have my one and it never wiped anything!
Only thing is to make sure you are s-off before you flash the zip as it might contain a exploit fixed hboot.
Renovated.
Click to expand...
Click to collapse
Thanks. I'm well aware that you need to be S-Off to flash firmware via fastboot. But my concern was more around having the device's SD partition wiped, as you can see, with the original 3.57 firmware released by LlabTooFeR here, he stated that it did wipe his SD partition.

There is one mistake for model MODEL ID: PN0710000,
line mainver: 1.28.401.7 change it with mainver: 3.57.401.500
Code:
modelid: PN0710000
cidnum: 11111111
cidnum: 22222222
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 3.57.401.500
btype:1
aareport:1
DelCache:1
hbootpreupdate:3

jonas2295 said:
No, firmware never wiped my SD card yet. I have flashed several firmware zips since I have my one and it never wiped anything!
Only thing is to make sure you are s-off before you flash the zip as it might contain a exploit fixed hboot.
Renovated.
Click to expand...
Click to collapse
The latest firmware provided by Llabtoofer wipes the sd card (even confirmed by him). The other customized firmware zips floating around have removed the offending files though.

ClydeB1 said:
The latest firmware provided by Llabtoofer wipes the sd card (even confirmed by him). The other customized firmware zips floating around have removed the offending files though.
Click to expand...
Click to collapse
Yeah I use the modified firmwares usually.
Renovated.

SD Card won't get wiped by default
ClydeB1 said:
The latest firmware provided by Llabtoofer wipes the sd card (even confirmed by him). The other customized firmware zips floating around have removed the offending files though.
Click to expand...
Click to collapse
This firmware doesn't wipe SD card data... You can flash it before or after flashing the 4.3 version ROMs. But recommend before flashing the custom ROM s.
This firmware is the newest released so far for WWE. It is modified to remove the red warning message.:laugh:
You flash it in RUU mode only and only if you have S-OFF.

jonas2295 said:
Yeah I use the modified firmwares usually.
Renovated.
Click to expand...
Click to collapse
Always the safest option
jolishj said:
This firmware doesn't wipe SD card data... You can flash it before or after flashing the 4.3 version ROMs. But recommend before flashing the custom ROM s.
This firmware is the newest released so far for WWE. It is modified to remove the red warning message.:laugh:
You flash it in RUU mode only and only if you have S-OFF.
Click to expand...
Click to collapse
Sorry I wasn't implying that your firmware did wipe the sd card, I was only responding to a post saying that firmware doesn't wipe data. Those that have used LLabtoofer's firmware for example (including him) have however had their sd cards wiped and I am only trying to prevent some person using the firmware and loosing all of their precious photos and videos etc without being aware of the possible risks.

This is my getvar all result after the flash:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.30
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.57.401.500
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4308mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
is this all right?

atomantmk said:
There is one mistake for model MODEL ID: PN0710000,
line mainver: 1.28.401.7 change it with mainver: 3.57.401.500
Code:
modelid: PN0710000
cidnum: 11111111
cidnum: 22222222
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
mainver: 3.57.401.500
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
Yes indeed.
Can someone upload the correct modified firmware for PN0710000 ?

wrong thread! sorry!

spdrosin said:
Yes indeed.
Can someone upload the correct modified firmware for PN0710000 ?
Click to expand...
Click to collapse
https://www.dropbox.com/s/qf0yczoxcccguz3/firmware.zip
Sent from my HTC One using Tapatalk

atomantmk said:
https://db.tt/HLkdgAGn
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
still fail

atomantmk said:
https://db.tt/HLkdgAGn
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanx man, but
focuskr said:
still fail
Click to expand...
Click to collapse
he is wright.
"FAILED (remote: 24 parsing android-info fail)"

how to find model no?

chdpiyush said:
how to find model no?
Click to expand...
Click to collapse
fastboot getvar modelid or fastboot getvar all

spdrosin said:
Thanx man, but
he is wright.
"FAILED (remote: 24 parsing android-info fail)"
Click to expand...
Click to collapse
Wait just a little please
Edit: new link added

Mytouch 4g problem with SIM Card after downgrade ROM

my fone is rom ver 2.3.4, i want root and cookrom so i downgrade to 2.2.1 is ok but now sim card not read, only read T-mobile SIM
here is my log of root, unlock sim by gfree file.
C:\ADB>adb push gfree /data/local
1400 KB/s (0 bytes in 134401.000s)
C:\ADB>adb shell
$ su
su
# cd /data/local
cd /data/local
# chmod 777 gfree
chmod 777 gfree
# ./gfree -f
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g899d047
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a63a4, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a6000
Kernel memory mapped to 0x40011000
Searching for brq filter...
- Address: 0xc02a63a4 + 0x34c
- 0x2a000012 -> 0xea000012
Patching and backing up partition 7...
patching secu_flag: 0
Done.
pic1 Bootloader, Pic2 Read sim T-Mobile(sim no services), Pic3 insert onother sim but insert sim
any suggestions, pls. thankx!

tried back to 2.3.4 but the same...
tried back to 2.3.4 but the same...
Code:
C:\ADB>adb reboot bootloader
flash fashboot
C:\ADB>adb reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
C:\ADB>fastboot devices
SH11ET604942 fastboot
C:\ADB>fastboot oem rebootRUU
... OKAY
C:\ADB>fastboot flash zip StockRom.zip
< waiting for device >
sending 'zip' (322693 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,34
INFO[RUU]UZ,boot,72
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,21
INFO[RUU]UZ,recovery,42
INFO[RUU]UZ,recovery,63
INFO[RUU]UZ,recovery,93
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,2
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,8
INFO[RUU]UZ,system,11
INFO[RUU]UZ,system,14
INFO[RUU]UZ,system,17
INFO[RUU]UZ,system,19
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,28
INFO[RUU]UZ,system,31
INFO[RUU]UZ,system,34
INFO[RUU]UZ,system,36
INFO[RUU]UZ,system,39
INFO[RUU]UZ,system,43
INFO[RUU]WP,system,0
INFO[RUU]WP,system,2
INFO[RUU]WP,system,5
INFO[RUU]WP,system,8
INFO[RUU]WP,system,11
INFO[RUU]WP,system,14
INFO[RUU]WP,system,17
INFO[RUU]WP,system,19
INFO[RUU]WP,system,22
INFO[RUU]WP,system,25
INFO[RUU]WP,system,28
INFO[RUU]WP,system,31
INFO[RUU]WP,system,34
INFO[RUU]WP,system,36
INFO[RUU]WP,system,39
INFO[RUU]WP,system,43
INFO[RUU]UZ,system,43
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,51
INFO[RUU]UZ,system,54
INFO[RUU]UZ,system,57
INFO[RUU]UZ,system,60
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,65
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,70
INFO[RUU]UZ,system,73
INFO[RUU]UZ,system,75
INFO[RUU]UZ,system,77
INFO[RUU]UZ,system,81
INFO[RUU]UZ,system,83
INFO[RUU]UZ,system,86
INFO[RUU]WP,system,43
INFO[RUU]WP,system,45
INFO[RUU]WP,system,48
INFO[RUU]WP,system,51
INFO[RUU]WP,system,54
INFO[RUU]WP,system,57
INFO[RUU]WP,system,60
INFO[RUU]WP,system,62
INFO[RUU]WP,system,65
INFO[RUU]WP,system,68
INFO[RUU]WP,system,71
INFO[RUU]WP,system,74
INFO[RUU]WP,system,77
INFO[RUU]WP,system,79
INFO[RUU]WP,system,82
INFO[RUU]WP,system,86
INFO[RUU]UZ,system,86
INFO[RUU]UZ,system,86
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,88
INFO[RUU]UZ,system,88
INFO[RUU]UZ,system,90
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,97
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,99
INFO[RUU]WP,system,86
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,97
INFO[RUU]WP,system,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO[RUU]WP,tp,0
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,8
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,20
INFO[RUU]UZ,radio,25
INFO[RUU]UZ,radio,32
INFO[RUU]UZ,radio,37
INFO[RUU]UZ,radio,45
INFO[RUU]UZ,radio,53
INFO[RUU]UZ,radio,61
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,79
INFO[RUU]UZ,radio,86
INFO[RUU]UZ,radio,94
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,6
INFO[RUU]WP,radio,14
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,27
INFO[RUU]WP,radio,36
INFO[RUU]WP,radio,44
INFO[RUU]WP,radio,100
INFOstart image[rcdata] unzipping & flushing...
INFO[RUU]UZ,rcdata,0
INFO[RUU]WP,rcdata,0
INFO[RUU]WP,rcdata,100
OKAY
C:\ADB>fastboot reboot
rebooting...

There is also always the possibility of a hardware malfunction. Have you messed with the SIM reader at all?

after 24h over don't touch it now my fone is ok, don't see Mytouch 4G....
back to 2.2.1 then cm-7.2.0-glacier.zip still OK.

You try up another rom , 4.3 JJ, if ok ,no need to use rom 2,2,1! Good luck!

[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.

htc one sv bootloop help plz !

hi guys i have a problem the device stuck on bootloop ! i fix before an htc like that so am familiar with the steps but i need som help and files thx i will show the informations below !
**locked***
K2_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
OS-3.11.61.10
eMMC-BOOT 1024MB
NOV 7 2013.15:32.31.0
so guys plz what steps and ruu i need!
regards

same problem.
exactly the same and when i do the steps from HTCDEV.com my revice it not recognized.
SOMEONE HELP US??

guys i download RUU that match with my phone but when i enter :
fastboot>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.155s]
finished. total time: 0.156s
help thanks

benben85 said:
guys i download RUU that match with my phone but when i enter :
fastboot>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.155s]
finished. total time: 0.156s
help thanks
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
sending 'recovery' (5954 KB)...
OKAY [ 0.815s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.519s
everything is failed even to install recovery
?

As long as you are S-on, you can't flash recovery.
What file ending of the ruu you have, zip or exe?

old.splatterhand said:
As long as you are S-on, you can't flash recovery.
What file ending of the ruu you have, zip or exe?
Click to expand...
Click to collapse
i have this on .exe : RUU_K2_CL_JB422_SENSE50_MR_Sprint_WWE_Boost_3.05.653.4_R_Radio_1.12.50.0516_10.30.42.25_NV_NV_Boost_2.20_150_release_389346_signed
but i think is not what i need and the other is zip file : PL80IMG_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1_Radio__1.18.40a.00.05_10.81a.40.23L_release_338297_signed
so whats the solution please !

benben85 said:
i have this on .exe : RUU_K2_CL_JB422_SENSE50_MR_Sprint_WWE_Boost_3.05.653.4_R_Radio_1.12.50.0516_10.30.42.25_NV_NV_Boost_2.20_150_release_389346_signed
but i think is not what i need and the other is zip file : PL80IMG_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1_Radio__1.18.40a.00.05_10.81a.40.23L_release_338297_signed
so whats the solution please !
Click to expand...
Click to collapse
Both files are are not for your phone and won't flash. You need a Ruu for software number 3.11.61.10.

old.splatterhand said:
Both files are are not for your phone and won't flash. You need a Ruu for software number 3.11.61.10.
Click to expand...
Click to collapse
ok do you have one ruu that match with my phone !

benben85 said:
ok do you have one ruu that match with my phone !
Click to expand...
Click to collapse
i found this is a encrypted zip L80IMG_K2_UL_JB422_SENSE50_MR_Orange_UK_3.11.61.10_Radio_1.18.40a.00.05_10.81a.40.23_release_340236_signed
but when i type fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.198s]
finished. total time: 1.198s
and i dont get it into black htc screen is stuck on logo with white background !
help plz

benben85 said:
i found this is a encrypted zip L80IMG_K2_UL_JB422_SENSE50_MR_Orange_UK_3.11.61.10_Radio_1.18.40a.00.05_10.81a.40.23_release_340236_signed
but when i type fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.198s]
finished. total time: 1.198s
and i dont get it into black htc screen is stuck on logo with white background !
help plz
Click to expand...
Click to collapse
I don't have a Ruu for your phone, but the one you have could work.
Rename the zip file to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard. Boot into the bootloader and let the phone recognize the zip. Confirm to update with vol+ and let it run until its finished.

old.splatterhand said:
I don't have a Ruu for your phone, but the one you have could work.
Rename the zip file to PL80IMG.zip (make sure it is not named PL80IMG.zip.zip) and copy it in the external sdcard. Boot into the bootloader and let the phone recognize the zip. Confirm to update with vol+ and let it run until its finished.
Click to expand...
Click to collapse
i renamed like you said the file but when i upgrading all the steps said 'FAIL-Pu'
eexcept [9] TP -OK
[10]SBL1 -bypass-s
[11] sbl1 -bypass -s
update fail in the end
what i can do

benben85 said:
i renamed like you said the file but when i upgrading all the steps said 'FAIL-Pu'
eexcept [9] TP -OK
[10]SBL1 -bypass-s
[11] sbl1 -bypass -s
update fail in the end
what i can do
Click to expand...
Click to collapse
I don't know. Maybe a bad download, not a full Ruu or something else.
You can try to unlock the bootloader with htcdev.com, flash twrp recovery and a rom.

old.splatterhand said:
I don't know. Maybe a bad download, not a full Ruu or something else.
You can try to unlock the bootloader with htcdev.com, flash twrp recovery and a rom.
Click to expand...
Click to collapse
i try to unlock the bootloader but its failed also ! it can be a bad emmc ?

Then i would say, you are out of luck and you should take a look for another phone.