Related
Hi all, try to be brief, but not simple:
First, I swear I've read many posts with cases similar to mine and I tried so many commands and tricks without success, so I decide to publish mine.
I have an HTC Inspire 4G, AT&T, rooted, S-off, and running Trickdroid. After a while I decided to return it to the original stock. However, when using the RUU utility, I got an error message and my phone it ruined.
Try to summarize as much as possible the conditions and the current situation:
Environments: Windows XP, Windows 7, Mac OS.
Power not work
Power + Vol Down do not work.
If I connect it to the outlet orante LED turn on, and charging it, but I must not press any buttons at all, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later.
I have access to fastboot commands, but not ADB. I tried to format the partitions, reflash, do recovery, recover partitions, etc, endless commands that do not give me a result.
The information obtained from the achievement of limited screen or fastboot commands is as follows:
ACE PVT HIP S-OFF RL
HBOOT-0.85.0019
MICROP-0438
RADIO-26.06.04.06_M
eMMC-BOOT
Dec 27 2012, 14:47:30
RUU
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.85.0019
(bootloader) version-baseband: 26.06.04.06_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 2.47.502.7
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9812000
(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: RUU
(bootloader) commitno-bootloader: dirty-9854d819
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.171s
fastboot oem boot
< waiting for device >
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D08BECC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x27E0E
(bootloader) TAG:hero panel = 0x830012
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is CWS__001
(bootloader) setting->cid::CWS__001
(bootloader) serial number: HT19VT207144
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =506
(bootloader) active commandline: board_spade.disable_uart2=0 board_spade.
(bootloader) usb_h2w_sw=0 board_spade.disable_sdcard=0 diag.enabled=0 boa
(bootloader) rd_spade.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
(bootloader) mmc=true androidboot.baseband=26.06.04.06_M androidboot.cid
(bootloader) =CWS__001 androidboot.batt_poweron=good_battery androidboot.
(bootloader) carrier=ATT androidboot.mid=PD9812000 enable_zcharge=1 andro
(bootloader) idboot.keycaps=qwerty androidboot.mode=normal androidboot.se
(bootloader) rialno=HT19VT207144 androidboot.bootloader=0.85.0019 zygote_
(bootloader) oneshot=off kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) Delay 98712(us) for dpram command before goto AMSS...
(bootloader) jump_to_kernel: machine_id(2844), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:0 msec
FAILED (status read failed (Too many links))
finished. total time: 232.216s
I used the commands, among many others:
Fastboot oem boot
fastboot flash recovery recovery.img (or zip)
fastboot oem resetRUUflag
fastboot reboot -bootloader (this just turn the phone off)
fastboot oem get_identifier_token (answer: (bootloader) [ERR] Command error !!!)
fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.020sfastboot format cache
formatting 'cache' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.017s
In many cases the response message in the command line is: remote no allowed
SD card formatted.
I have no access to the SD card from the phone connected.
Please tell me if there is any other way to recover my phone, or if it is just an expensive piece of nothing.
Thanks for everything.
What happened when you tried to flash recovery from fastboot?
bananagranola said:
What happened when you tried to flash recovery from fastboot?
Click to expand...
Click to collapse
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Frogzter said:
./fastboot flash zip PD98IMG.zip
sending 'zip' (3619 KB)...
OKAY [ 0.623s]
writing 'zip'...
No more response, stuck there...
In many other commands (I just don't remember after trying several) I got the message "remote not allowed"
Click to expand...
Click to collapse
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
bananagranola said:
That's because you need a recovery.img, not a PD98IMG.zip:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I got this:
./fastboot flash recovery r.img
sending 'recovery' (4456 KB)...
OKAY [ 0.764s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.771s
Why?
Click to expand...
Click to collapse
Is your phone in fastboot mode?
bananagranola said:
Is your phone in fastboot mode?
Click to expand...
Click to collapse
Yes, it is, or at least I think so, because the command fastboot devices, found my device, besides, the command fastboot getvarr all, also works...
No more responses guys?
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
bananagranola said:
Where are you getting the recovery? How are you putting your phone in fastboot? Are you running the command from the folder where the recovery is? Are you sure you are S-Off?
Click to expand...
Click to collapse
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Frogzter said:
Power button not work
Power + Vol Down not work either.
If I connect it to the outlet orange LED turn on, and charges the battery, after ten minutes, HTC logo appears with four exclamation marks on the screen. However, Windows can not find the device until 5 or 10 minutes later, after this 10 minutes, if I connect via USB the device is responsive to fast boot devices command...
besides the screen shows:
ACE PVT HIP S-OFF RL
I have to command and the recovery file in the same folder
Click to expand...
Click to collapse
What RUU did you use?? that sounds like a messed bootloader....
bananagranola said:
Er, what about the rest of my questions? How are you getting to fastboot with broken buttons? Is there an "adb reboot fastboot"?
Click to expand...
Click to collapse
I don't do anything.. I can't... if I plug the usb cable and touch any button nothing happen but if just plug it and let the phone alone, after 20 minutes do to fastboot mode...
"adb devices" don't detect the device.. just "fastboot devices" does
glevitan said:
What RUU did you use?? that sounds like a messed bootloader....
Click to expand...
Click to collapse
Well, now I feel ashamed, I can't remember with one I used... I just google the last version, because I wanted to get back to the original rom...
I formatted the computer with MAC OS, Linux, Win 7 and Win XP, looking for fix it, so I don't have much trace of with one I used.
HTC INSPIRE. att cws_001 bootloader 2.00.0030 s-on
Same thing on mine except my phone never comes on but fastboot is the only thing that recognizes my phone with limited commands. when I do a faceboot devices I get this ☺ ⌠σ fastboot no serial numbers as it use to have. Phone will not turn on at all. while nothing plugged in no light or anything even when trying to power on or get to hboot no sign of life at all. When I plug it in I get solid orange light. Pc sees it as android usb devices - my htc. but stock rom exe dont find phone. this happened to me when I was using xlmultitool 2.1. I was tyring for s 0ff after the option to [5] Flash HBOOT S-OFF Unprotected (via adb) this is when my troubles started. cant flash anything to it. when I try to flash the stock rom I get error file to big. In need of help.......I do have a gold card....
C:\Android>fastboot flash zip PD98IMG_Inspire_S-ON_FactoryRestore_GB_1.07.zip.
sending 'zip' (315734 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 26.09.04.11_M2
(bootloader) version-cpld: ☺
(bootloader) version-microp: ☺
(bootloader) version-main: ♦
(bootloader) serialno: ☺ ⌠σ
(bootloader) imei: 3544550xxxxxxxx ......just sits here tells me nothing more
C:\Android>fastboot flash recover recovery.img
< waiting for device >
sending 'recover' (5532 KB)...
OKAY [ 0.624s]
writing 'recover'...
FAILED (remote: partition does not exist!)
finished. total time: 0.625s
C:\Android>fastboot flash system system.img
sending 'system' (571388 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.002s
C:\Android>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [SD_HW_ERR] SD: No device attached
(bootloader) [ERR] Boot/Recovery image does not exist!!!
OKAY [ 0.116s]
finished. total time: 0.117s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
sorry to double post but its been about a year is there a fix for this please someone help....
wacky_35016 said:
sorry to double post but its been about a year is there a fix for this please someone help....
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.002s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.008s
C:\Android>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 1.004s]
finished. total time: 1.005s
Click to expand...
Click to collapse
Sounds like it's still s-on. Where did you get your Unlock_code.bin from? Have you tried using htc dev to get one or a new one?
[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.
[Solved] HTC Butterfly S-Off, Unlock, Bootloader & TWRP Recovery "Stuck in bootloop."
PLEASE try to HELP or acknowlede!
Please forgive me for contacting you as such but I'm desparate right now.
Dear All,
I'm wound up in a bootloop. Please help at the earliest.
This is my current status and a little history.
1. I was flashed InsertCoin 3.0.6 on my x920d (originally HTC_038) a couple of days ago (and did a TWRP Backup after That),
2. Had unlocked my previous, old custom rom (thru HTCDev), S-Off (thru rumrunner) and
3. rooted by flashing 'UPDATE-SuperSU-v2.02' from recovery after flashing the ROM a couple of days earlier.
4. I had also flashed Kairi's firmware-kk (which is for HTC_061) as I had Super CID 11111111 by "fastboot oem writecid..." method, now I'm not able to do it anymore).
Anyway, there was some problem (wrongly presumed by me) with the htc backup/restore function, so I reflashed the IC3.0.6 rom a couple of times thru recovery(TWRP 2.7 by Kairi). And the device booted perfectly.
Stupidly, I happened to flash '[ROM] FireKatN4 Deodex V5 TW 4.4.4' through Kairi's recovery. Link of the ROM - http://forum.xda-developers.com/note...emely-t2916463.
Thish rom was for Samsung T Mobile Galaxy Note 4 N910T and it did not flashed properly; so I re-flashed IC3.0.6 thru recovery (if required I can perform this again) and it showed successful at the end.
Now since then whenever I reboot it get stuck in bootloop.
Since yesterday I have been trying various steps (repeated several times and not inchronological order):
- 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 firmware's 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 then continued on its own 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"
Now my status is:
Although I'm able to flash recovery img thru fastboot. I can do it from oem rebootRUU.
My Getvar all read as :
(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 - (As per Kairi's original Firmware-kk android-info file it is : 3, the CID is HTC_061)
(bootloader) gencheckpt: 0
all: Done!
Now
1. I,m S-Off, Relocked/Unlocked Bootloader (able to do this thru fastboot).
2. Can boot into bootloader & TWRP Recovery - Kairi's, but cannot boot the phone.
3. After flashed IC3.0.6 thru recover once again. when rebooting, get stuck in bootloop again.
Please try to help me out.
P.S. I have somescreenshots available of several steps, if required.
Hi Capt Vikram.
Try extracting the boot img and flash that. It has got me out of a few bootloops
Clarkie_955i said:
Try extracting the boot img and flash that. It has got me out of a few bootloops
Click to expand...
Click to collapse
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Capt Vikram Sandhu said:
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Click to expand...
Click to collapse
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Clarkie_955i said:
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Click to expand...
Click to collapse
Yes Clarkie,
I had flashed firmware-kk thru 'fastboot oem rebootRUU', then 'fastboot flash zip fimware-kk.zip'
It gave me th 90 error and I repeated the command and it went successful.
I'll do that again and update you with each step chronologically.
Thanks for your help in my desparate situation.
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.
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Clarkie_955i said:
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Click to expand...
Click to collapse
Thanks A TON Clarkie,
Your reply is very much appreciated. It seems like a ray of hope in a dark tunnel. Really grateful to you.
Now coming back to the matter at hand -
I had earlier tried to
1. Tried to flash 'NOS_m7_v3.0.0_dlxbu1' thru Recovery, was successful but when tried to boot, got stuck again in bootloop. Then again installed InserCoin.
Note - Maybe I did not perfom a wipe cache & definately did not flash the boot image thru fastboot after flashing the above rom.
Secondly I'm neither able to reboot from bootloader mode into recovery nor vice verca.
Thirdly, I cannot flash any zip from bootloader (but able to flash image files thru bootloader & install zip thru recovery); & no "fastboot reboot recovery" from bootloader mode and no "adb reboot bootloader"
from recovery (same with RUU "fastboot reboot bootloader", though in recovery & fastboot mode "adb/fastboot devices" show my device).
Fourthly, whenever I reboot into system/android I get Two bootscreens - 1. HTC Quietly Brilliant & the device gets disconnected and connected again and the second boot screen is HTC One.
Finally it stays at the HTC One screen for some time and suddenly there is some very slight variation in the brightness of the bootscreen, then the capacitive buttons (Back, Home & Recent app) lightens and it
reboots.
2. Tried to restore from TWRP Backup (when I was successfully running InserCoin for the first time) but again the bootloop. I also have one of NOS_m7_v3.0.0 (When I was S-On), that I've not tried yet as I'm afraid to get
back to S-On and bootloop at the same time..
3. Meanwhile, today a couple of hours ago, I came across this thread - http://forum.xda-developers.com/showthread.php?t=2208833, and
performed an advanced wipe thru recovery (wiping everythingh except external sd card). Wiped Dalvik Cache. TWRP Backup. Rebooted. (For a lovely change) Got stuck at boot screen -HTC Quitely Briliant.
(maybe no OS installed).
4. Manually went into bootloader and then recovery. Installed InsertCoin again. At the end it said no SuperSU. Swiped to install it. Reboot. Got stuck at Bootloop.
Please try to Suggest:
A. When to flash boot.img - before or after installing the rom.
B. Does restoring S-On state backup will effect my S-Off condition.
Thanx In Advance.
1 + 1 = 11
Will Definately try BOA's Rom meanwhile.
HI Clarkie,
Tried the download links at BOA's ROM thread in the forum. Doesen't work.
Can you provide me a link.
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Clarkie_955i said:
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Click to expand...
Click to collapse
Thanks Clarkie,
I'll give it a shot.
And let you know.
Capt Vikram Sandhu said:
Thanks Clarkie,
I'll give it a shot.
And let you know.
Click to expand...
Click to collapse
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Clarkie_955i said:
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Click to expand...
Click to collapse
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Capt Vikram Sandhu said:
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Click to expand...
Click to collapse
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Clarkie_955i said:
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Click to expand...
Click to collapse
Hi Clarkie,
Tried the following:
Installed TWRP 2.6.3
Factory reset from recovery.
Installed BOA V8.0 thru recovery (Couldn't understand the language of aroma installer, but went ahead both the times).
Device Rebooted into bootloop again.
Powered off with only the power button, but then it again restarted into bootloop.
Flashed the boot.img thru fastboot. Reboot. Again bootloop.
Went to Recovery. Wiped everythingh except Micro SDcard
Installed the rom thru recovery install zip
Aroma Installer Finished Screen -> from recovery reboot options went into fastboot. Flashed the boot.img.
Rebooted to System - Back to square 1 in bootloop.
Also during the bootloop pressing down the power button does not power off & restarts the device. But the screen goes off for a few seconds and automatically boots intp the bootloop.
FYI -
I'm using a partitioned sd card. with 1. FAT32, 2. ext4 & 3. Linux SWAP. And thru recovery file manager it showed sd-ext & superuser folders in the root. I'll give it a try on an unpartitioned card.
had successfully, flashed recovery-clockwork-touch-6.0.3.1-dlxub1 before flashing TWRP 2.6.3. But the CWMod recovery shows the following:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I tried adb reboot-bootloader but nothing happens.
Please try to suggest from here.
How can I check (from Bootloader/recovery) if my device is rooted/unrooted.
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Clarkie_955i said:
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Click to expand...
Click to collapse
I have done again the following steps as you said:
1. Started the Device.
2. First Splash screen came up - HTC quietly Briliant.
3. Second Splash Screen came up - HTC One.
4. Waited for one/two seconds and pressed continuosly on the power button.
5. Screen went totally black/maybe powered off.
6. Removed my finger from the Power button in order to press it back to power the device.
7. Before I can press it is back on the first splash screen pops up and the bootloop starts.
8. Even If I do not release the power button after the 5th step it automatically reboots & bootloop starts.
I did try this from the first bootscreen and also after complete power down from bootloader/recovery mode.
Meanwhile I'll search the link you gave.
I think that maybe I'm unrooted now because when i try thru recovery - advance - file manager, I cannot see any file in /system/bin/ (where there should have been a su file there.)
Thanks for your reply . will keep you posted.
Your replies mean a lot to me.
Hi Clarkie,
Re-read all of your posts and guidance.
Motivated by this and the links provided espaicially by you and reply from abhinav.tella I think I'm able to lock on the problem (perhaps).
Right now compiling it and will post with further details.
Kindly try to walk me thru it with your suggestions and guidance.
Thanx in advance.
Bits and Pieces
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Capt Vikram Sandhu said:
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Click to expand...
Click to collapse
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
---------- Post added at 07:37 AM ---------- Previous post was at 07:29 AM ----------
Clarkie_955i said:
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
Click to expand...
Click to collapse
You might want to change your cid. Thought you was supercid 11111111
Hi there!
After stupidly flashing CM on a hiaeuhl device, every time I boot the device it reboots to bootloader with the "init fs_mgr_mount_all failed" error.
Obviously I try to restore my own Stock TWRP backup, but still blocked.
Then I try some RUU/ROM flashing, but since I'm S-ON and 1.27.401.5, I find nothing working for my device.
Have you got any advice?
Thank you so much!
Code:
Product: htc_hiaeuhl
Status: S-ON / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.27.401.5
Radio: [email protected]
Fingerprint: htc/hiaeuhl_00401/htc_hiaeuhl:6.0/MRA58K/656287.5:user/release-keys
OK, I'm on it since two days, post it and solve it in 30min...
For reference, it's possible to downgrade the ROM.
Have to use htc_fastboot and push 1.10.401.7 images.
See http://forum.xda-developers.com/showpost.php?p=64586583&postcount=146 and http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122
InTheNorth said:
Hi there! funny mine to
My is unlocked with S-on
After stupidly flashing CM on a hiaeuhl device, every time I boot the device it reboots to bootloader with the "init fs_mgr_mount_all failed" error.
Obviously I try to restore my own Stock TWRP backup, but still blocked.
Then I try some RUU/ROM flashing, but since I'm S-ON and 1.27.401.5, I find nothing working for my device.
Have you got any advice?
Thank you so much!
I have also tried Cyanogenmod 13. I changed the "updater script" to target my device model too and added the letter "h" in text-editor hiaeul to hiaeuhl with boot loops
Code:
Product: htc_hiaeuhl
Status: S-ON / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.27.401.5
Radio: [email protected]
Fingerprint: htc/hiaeuhl_00401/htc_hiaeuhl:6.0/MRA58K/656287.5:user/release-keys
Click to expand...
Click to collapse
I have the exakt problem too... Your hardware&Software description is identical.
I flash through htc_fastboot.exe and I flash system partition with wrong method
Code:
htc_fastboot flash system apppreload.img
I used images from combined
2PQ9IMG_HIA[email protected]51002.3_29.05_F_release_454007_combined_signed
my
Code:
fastboot get var all
is
h:\>htc_fastboot.exe getvar all
Code:
(bootloader) version:0.5
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x29b000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc6000000
(bootloader) serialno:HT5A????secret
getvar all from download mode is
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeu[B]h[/B]l
(bootloader) version: 1.0
(bootloader) imei: *************secret
(bootloader) version-main: 1.27.401.5
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: HTC__034
a
Is changing manifest working? I'm not sure...
So you have restore your phone with those images?
InTheNorth said:
Is changing manifest working? I'm not sure...
So you have restore your phone with those images?
Click to expand...
Click to collapse
I still haven't succeded to restore phone to factory state... I didn't twrp backup it after root.
Status is unlocked, S-ON
I have tried your links to
I did
H:\>fastboot oem rebootRRU
Code:
:\>htc_fastboot.exe flash zip HTC_A9_1.10.401.7_partial.zip
sending 'zip'... (88062 KB) OKAY
sending time = 8.050 secs
writing 'zip'... (bootloader) HOSD CL#656287
(bootloader) ERR [SD_UPDATE_ERR] Main version NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 19
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAIL19 RU_MAIN_VER_FAIL os-version in android-info missing or i
FAILED (remote: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i)
Execution time is 12(s)
I think it isn't same partition size, I also tried regular fastboot and htc_fastboot in oem-mode.
Code:
>fastboot flash system system.img
target reported max download size of 800000000 bytes
system size on windows is 2,92 GB
according to this guy nenebear http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122 I have another international model.
I am not sure wich version I have... according to this post
International version don't flash is images . Because the unlocked version of the system partitions of different size and international version .
unlocked version system partitions -- mmcblk0p62: d9000000 00000200 "system"
international version system partitions -- mmcblk0p62: c6000000 00000200 "system"
I have tried RUU.exe file with fail to not same main version
I flash zipped with fail
fastboot flash zip 2PQ9IMG_HIAE_UL_ATT_1.27.502.5_firmware.zip
Meanwhile i see that fastboot flash system system.img is working now haha it just took time to read/send system.img that is almost 3GB
thank you for your link, I needed that system.img file
fastboot flash system H:\Htc-blocket\rom\upNorth\partial\system.img
target reported max download size of 800000000 bytes
erasing 'system'...
OKAY [ 2.748s]
sending sparse 'system' (769748 KB)...
OKAY [ 71.392s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 34.540s]
sending sparse 'system' (778860 KB)...
OKAY [ 72.596s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 34.080s]
sending sparse 'system' (770834 KB)...
OKAY [ 72.728s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 33.950s]
sending sparse 'system' (752915 KB)...
OKAY [ 70.736s]
writing 'system'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 33.562s]
finished. total time: 426.364s
Many seconds here, 7 minutes
Click to expand...
Click to collapse
H:\>fastboot flash boot H:\Htc-blocket\rom\upNorth\partial\boot.img
target reported max download size of 167000000 bytes
sending 'boot' (45799 KB)...
OKAY [ 4.548s]
writing 'boot'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.868s]
finished. total time: 8.416s
H:\>fastboot flash recovery H:\Htc-blocket\rom\upNorth\partial\recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (47229 KB)...
OKAY [ 4.416s]
writing 'recovery'...
(bootloader) HOSD CL#656287
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 4.038s]
finished. total time: 8.454s
Solved! Thank you!
So CM is not available for the hiaeuhl ? I bought this device, didn't kno there were variants...
exploreresp said:
So CM is not available for the hiaeuhl ? I bought this device, didn't kno there were variants...
Click to expand...
Click to collapse
You have to remove the /system partition protection (S-on=Secure ON=you licensing the device, S-off=Security off=you own the device=God over your device) because the bootloader is checking the partition integrity and finds out if you did something with it (writing/deleting/etc).
:cyclops: Unfortunately I tried to logcat, adb-watch my device under the hood during the unlocking process by an app named "sunshine.apk" when is was unlocking (S-off'ing) with secret methods/(unshared knowledge), Unfortunately they (the app) kill logcat-process continuously all the way, in and out, out and in so I could'nt figure out that secret method the use....
You can still root your device since the Master of the masterdeveloper named ChainFire is putin th su binaries on a separate partition /su/bi and symlink some how (just guessing, correct me if I'm wrong) with a modified unlocked boot.img.
Forget xposed-framework, forget CyanogenMod unless you release/unchain your phones locked /system partition and other partitions too (not necessary) . It will cost you 25$ dollar, sorry, it is not my faults, I am just like you a hardware-owner of a Taiwanese cellphone.
After you S-off'ed your phone with money (25$) you can install CM13 or CM14 (year 2017). Hopefully some hardware/kernel hacker figure out an easy way to s-unlock/s-off without paying crying: there are more poor people in this world than there are rich people)
Me too bought this phone with the mind of put in CyanogenMod... I don't trust other manufactures android-OS. Also I can overclock/underclock etc and install the mothers of all hack... the xposed-framework... ayhem!
---------- Post added at 04:47 PM ---------- Previous post was at 04:38 PM ----------
exploreresp said:
So CM is not available for the hiaeuhl ? I bought this device, didn't kno there were variants...
Click to expand...
Click to collapse
You simply convert your phone with money and this method in this linked thread
Read further, there is hope with money! :victory: and a payPal / visa account
Cheers :good:
InTheNorth said:
Hi there!
After stupidly flashing CM on a hiaeuhl device, every time I boot the device it reboots to bootloader with the "init fs_mgr_mount_all failed" error.
Obviously I try to restore my own Stock TWRP backup, but still blocked.
Then I try some RUU/ROM flashing, but since I'm S-ON and 1.27.401.5, I find nothing working for my device.
Have you got any advice?
Thank you so much!
Code:
Product: htc_hiaeuhl
Status: S-ON / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.27.401.5
Radio: [email protected]
Fingerprint: htc/hiaeuhl_00401/htc_hiaeuhl:6.0/MRA58K/656287.5:user/release-keys
Click to expand...
Click to collapse
you should be able to install CM13 on your device...
check: http://forum.xda-developers.com/one-a9/general/cm13-t3290846/post64882819#post64882819
Edit: It seems you need to convert to us version first
Hey all,
Bringing that post up because I'm having the same issue here and none of the solutions proposed worked...
Problem is my phone began freezing 2mn after booting (I was still able to use it, apps, phone etc... but after around 2mn can't do anything anymore) after I took it with me in very low temperature. I tried to restore it and then this error appeared "init fs_mgr_mount_all failed"...
I had TWRP, unlocked, S-OFF and tried a few things :
This one first, didn't work : http://android-revolution-hd.blogspot.cl/2013/10/fix-data-htc-one.html
Then tried the solution proposed here, didn't work either : http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122
And as it turned out I came back to the stock recovery ... (wasn't sure of what I was doing) so now I only have adb sideload...
Tried installing CM using sideload, didn't work (signature verification failed... which is pretty normal).
Anyway I'm posting because it is really my last resort... don't have anything left under my sleeve. I'm currently downloading a 1.27.112.5 stock rom (http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344) to try to downgrade but not sure the problem will be solved...
If someone can help, it would be great!!
Code:
Product: htc_hiaeuhl
Status: S-OFF / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.56.401.70
Radio: [email protected]
Aliass01 said:
Hey all,
Bringing that post up because I'm having the same issue here and none of the solutions proposed worked...
Problem is my phone began freezing 2mn after booting (I was still able to use it, apps, phone etc... but after around 2mn can't do anything anymore) after I took it with me in very low temperature. I tried to restore it and then this error appeared "init fs_mgr_mount_all failed"...
I had TWRP, unlocked, S-OFF and tried a few things :
This one first, didn't work : http://android-revolution-hd.blogspot.cl/2013/10/fix-data-htc-one.html
Then tried the solution proposed here, didn't work either : http://forum.xda-developers.com/showpost.php?p=64509541&postcount=122
And as it turned out I came back to the stock recovery ... (wasn't sure of what I was doing) so now I only have adb sideload...
Tried installing CM using sideload, didn't work (signature verification failed... which is pretty normal).
Anyway I'm posting because it is really my last resort... don't have anything left under my sleeve. I'm currently downloading a 1.27.112.5 stock rom (http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344) to try to downgrade but not sure the problem will be solved...
If someone can help, it would be great!!
Code:
Product: htc_hiaeuhl
Status: S-OFF / Unlocked
CID: HTC__034
MID: 2PQ910000
OS: 1.56.401.70
Radio: [email protected]
Click to expand...
Click to collapse
Just use a RUU, that's how you get everything back to stock.
Sent from my HTC One A9 using XDA-Developers mobile app
hi,
my device is htc u11 and i need correct firmware for this,
before i add the details i want to mention my device is no more booting,
bootloader is unlocked and twrp is install, s on. not detecting by htc tool,
let me tell you how the problem comes, device was working perfectly,
but i need to downgrade to 7, so i flashed twrp and make backup of my rom,
and try to flash custom rom, custom rom flashed successfully device rebooted but after few seconds again reboot, now the problem is that i have twrp backup but even i can,t flash back backup, its giving me this error,
failed to mount system device or resource busy
same error during wipe system partition,
ok so whats the condition of my device when it was ok,
its htc u11 single sim,
CID VODAP102
MID 2pZC10000
bootloader version 1.0.0.0000
version baseband 8998 002772 171161638
main version 2.33.161.12
and this is the fastboot info
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: FA81R1800262
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 3
(bootloader) version-main: 2.33.401.10
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 8998-002772-1711161638
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP102
i try to flash this and other 2 more roms but not success, example i flashed this rom via fastboot so i get this error
fastboot flash zip rom.zip
C:\adb>fastboot flash zip rom.zip
target reported max download size of 1560800000 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 1129577793 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 55840065 is not a multiple of the block size 4096
sending sparse 'zip' 1/3 (1048572 KB)...
error: write_sparse_skip_chunk: don't care size 1129577793 is not a multiple of the block size 4096
FAILED (command write failed (Invalid argument))
finished. total time: 19.773s
C:\adb>
i try via sdcard method so got this error
19 RU main ver fail os versin in android id info missing or i
fail 19 ru main ver fail os version in android info missing or i
press power to continue
this rom i try to flash,
2PZCIMG_OCEAN_UHL_N71_SENSE90GP_Vodafone_UK_1.27.161.5_Radio_8998-001791-17
so i think i provided all things hope i,ll get back my device in working condition,
it,ll make me more happy if i,ll be back to 7 rom, :crying:
HTC U11 corrupted
Mr Hassan said:
hi,
my device is htc u11 and i need correct firmware for this,
before i add the details i want to mention my device is no more booting,
bootloader is unlocked and twrp is install, s on. not detecting by htc tool,
let me tell you how the problem comes, device was working perfectly,
but i need to downgrade to 7, so i flashed twrp and make backup of my rom,
and try to flash custom rom, custom rom flashed successfully device rebooted but after few seconds again reboot, now the problem is that i have twrp backup but even i can,t flash back backup, its giving me this error,
failed to mount system device or resource busy
same error during wipe system partition,
ok so whats the condition of my device when it was ok,
its htc u11 single sim,
CID VODAP102
MID 2pZC10000
bootloader version 1.0.0.0000
version baseband 8998 002772 171161638
main version 2.33.161.12
and this is the fastboot info
C:\adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_ocnuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1560800000
(bootloader) serialno: FA81R1800262
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 3
(bootloader) version-main: 2.33.401.10
(bootloader) boot-mode: RUU
(bootloader) version-baseband: 8998-002772-1711161638
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP102
i try to flash this and other 2 more roms but not success, example i flashed this rom via fastboot so i get this error
fastboot flash zip rom.zip
C:\adb>fastboot flash zip rom.zip
target reported max download size of 1560800000 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 1129577793 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 55840065 is not a multiple of the block size 4096
sending sparse 'zip' 1/3 (1048572 KB)...
error: write_sparse_skip_chunk: don't care size 1129577793 is not a multiple of the block size 4096
FAILED (command write failed (Invalid argument))
finished. total time: 19.773s
C:\adb>
i try via sdcard method so got this error
19 RU main ver fail os versin in android id info missing or i
fail 19 ru main ver fail os version in android info missing or i
press power to continue
this rom i try to flash,
2PZCIMG_OCEAN_UHL_N71_SENSE90GP_Vodafone_UK_1.27.161.5_Radio_8998-001791-17
so i think i provided all things hope i,ll get back my device in working condition,
it,ll make me more happy if i,ll be back to 7 rom, :crying:
Click to expand...
Click to collapse
I had the same problem but I locked the bootloader by accident while being on a rooted stock ROM. The reason that the ROM is not working is most likely because it's outdated. I was on 2.33.710.9 and I tried to flash roughly the same version. So unfortunately, I don't think a downgrade to nougat (version 7) will work. But, to fix your phone, download your version from here: https://www.hardreset.info/devices/htc/htc-u11/faq/firmware/. Once you have downloaded it, rename it to 2PZCIMG. Then, put it onto your SD card. Go to bootloader, and should say flash zip vol up for yes and vol down for cancel or something, and press volume up. Let me know if it works.
Thanks.
allenaj said:
Let me know if it works.
Thanks.
Click to expand...
Click to collapse
1st of all thanks for your time bro, but as i said i already try to flash but its fail and the error is already mention, 1 rom is from this site which you suggest me, and the rom name is also mention which i try to flashed, maybe from this or another site,
Can you provide me the exact link of correct firmware it'll save my time,
And let me ask you one question htc is not possible to flash online? Like iPhone's?