"init fs_mgr_mount_all failed" error - HTC One A9

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

Related

[Q&A] [Recovery] Unofficial CWM - 6.0.5.0 - peregrine

Q&A for [Recovery] Unofficial CWM - 6.0.5.0 - peregrine
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 [Recovery] Unofficial CWM - 6.0.5.0 - peregrine. 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!
black screen cwm
EDIT: SOLVED (with somcom's recovery toolkit http://forum.xda-developers.com/moto-g/4g-development/moto-g-4g-easyrecovery-toolkit-t2856710 /please feel free to delete this post which now only serves as proof of my incompetence)
........................................................................
hello, i've just bought a moto lte (uk) xt1039
have successfully unlocked bootloader
trying to flash recovery via fastboot but having issues
seems to flash ok but then when rebooting into recovery device show (nearly) black screen with some white flickers.
i can boot into bootloader and access via fastboot on windows 7
i downloaded recovery and rom on the moto (before erasing partitions and being unable to boot) and have copies on laptop too.
what have i done? how can i get recovery working to install a rom?
thanks so much for your help, sorry I couldn't find answer here (I tried!
C:\Users\prosody\moto g\RECOVERY>fastboot devices
TA003002KC fastboot
C:\Users\prosody\moto g\RECOVERY>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113(*)
(bootloader) product: peregrine
(bootloader) secure: yes
(bootloader) hwrev: 0x82D0
(bootloader) radio: 0x3
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: TA003002KC
(bootloader) cid: 0x0007
(bootloader) channelid: 0x49
(bootloader) uid: B6C1B20515000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Nov 9 17:24:15 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/peregrine_o2gb/peregrine:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.56/52:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.56.peregrine_o
(bootloader) ro.build.version.full[1]: 2gb.o2gball.en.GB
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gc20375a-00001-g804
(bootloader) kernel.version[1]: 2017 ([email protected]) (gcc version 4
(bootloader) kernel.version[2]: .7 (GCC) ) #1 SMP PREEMPT Tue Aug 5 22:4
(bootloader) kernel.version[3]: 2:49 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.11-0-gcff5797
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/0
(bootloader) ro.carrier: o2gb
all: listed above
finished. total time: 0.100s
C:\Users\prosody\moto g\RECOVERY>fastboot erase system -w
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.078s]
erasing 'userdata'...
OKAY [ 0.243s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.018s]
erasing 'cache'...
OKAY [ 0.070s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.021s]
finished. total time: 0.449s
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
erasing 'boot'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.113s]
finished. total time: 0.117s
C:\Users\prosody\moto g\RECOVERY>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.118s]
finished. total time: 0.122s
C:\Users\prosody\moto g\RECOVERY>fastboot flash CWM-6.0.5.0-peregrine.img
unknown partition 'CWM-6.0.5.0-peregrine.img'
error: cannot determine image filename for 'CWM-6.0.5.0-peregrine.img'
C:\Users\prosody\moto g\RECOVERY>fastboot flash recovery CWM-6.0.5.0-peregrine.i
mg
target reported max download size of 536870912 bytes
sending 'recovery' (7752 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.426s]
finished. total time: 0.746s
C:\Users\prosody\moto g\RECOVERY>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\Users\prosody\moto g\RECOVERY>
Blinking stripes when trying recovery
I just wanted to add that I too have trouble booting into CWM recovery. The screen goes black and some flashing stripes appear accross the screen before it goes completely black. Basically it's unusable...
I can hold the power button and the phone reboots as normal.
The bootloader is unlocked and the phone is rooted.
I hope this information is useful in some way and some fix can be found.
(I have the same problem with TWRP by the way.)
I'm so sorry, you can all ignore what I wrote above.
I fixed it the same way as noted in the post above...
Cheers,
I flashed the CWM recovery as described but when I try to enter it I only get a black screen. I also tried the non-touch version of the recovery but that didn't make any difference. Ideas!?
*edit*
Followed the instructions above and got stuck in the bootloader. Then somehow managed to flash CWM using the Toolkit mentioned above.
C:\Users\prosody\moto g\RECOVERY>fastboot erase boot
Click to expand...
Click to collapse
What's with the flashboot commands posted by prosodyspeaks, I guess that erasing the boot was somehow responsible for being unable to boot the system!?
Every time I create a recovery to my external SD card, it hangs at "Generating md5 sum" but works fine when its in the internal storage. I always have to restart my phone manually. Is there a fix to this, or can I just make a recovery to my internal storage and move the entire recovery folder to my external SD card?
Will this work this the Lollipop 5.1 bootloader?
SJHacker said:
Will this work this the Lollipop 5.1 bootloader?
Click to expand...
Click to collapse
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.
Try this
The easiest method to install CWM without pc:
1. Download the file on your phone (I moved it to the internal storage)
2. Download Flashify from Play Store
3.Go to "flash" section and select "flash recovery image"
4. Click on "choose a file"
5. Choose the downloaded file
6. Click on this file and select "yup"
7. CWM should be now installed
I have tried this method with my device (Motorola Moto G 4G) and everyrhing went well.
_Immanuel_ said:
I have 6.0.5.1 installed on my XT1039 Peregrine and it works, i downloaded it from here h t t p ://builder.unstableapps.com/#/latest/clockworkmodrecovery/peregrine .
Anyway you can always test before flash using
Code:
fastboot boot [B]HERE_YOUR_RECOVERY_IMG[/B]
.
If it boots and works then you flash.
PS: I use the CWM linked above, there is only one issue: when you flash it and boot the recovery screen flickers and shows an horizontal line that goes from up to bottom....but everything seems working.
If i simply boot the recovery image without flashing there are no graphical issues.
Click to expand...
Click to collapse
Thanks!
Does latest version supports the ext. sdcard used as internal in a marshmallow rom? Thx

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

Flashing Problem (Bricked phone)

Dear,
I bought a mobile XT1032 in Chile and had the bright idea to install Android 5.0.0, but before that should turn my phone GPE and worked smoothly for about two months, but a few weeks ago the screen began to random failures for example the phone is locked and unlocked without my intervention or the screen, the phone is locked, blinking (as it had voltage changes, such as when you move a flashlight with almost empty and this flashing batteries). I decided to go back to Android 4.4.4 Stock, however this time I did the procedure without considering the consequences, I first downloaded and installed the GPE 4.4.4, then downloaded and installed the Stock Brasil 4.4.4, then tried to go back to stock Movistar Chile but failed to find the 4.4.4 nowhere, so I decided to install the 4.4.3. My mistake. After that my phone did not work more.
Now if I switch it displays the message "Unlocked Bootloader" then shows motorola logos (the world turning) and then the screen goes black but not off (note that is on because it has brightness and that was with that flicker as if he had mentioned voltage failures) but this does not show anything.
I tried installing all the tutorials I found on the internet to revive my phone, I got about 15 different roms and nothing works. I can enter fastboot and no problems (strangely fastboot screen does not flash, it is as if he had nothing wrong), I can also enter recovery (either in recovery flashing display). If I make a recovery "wipe data / factory reset" does well, but if I do "wipe reset partition" android logo shows the blue loading bar appears 2 seconds and the phone reboots.
I not been possible to change the recovery of stock for some other recovery (eg Philz) because although fastboot or mfastboot shows that the process was well (sometimes shown on the phone that is making a downgrade) this does not change the recovery.
Currently my phone is flashed (at least it is assumed that no starts beyond the worlds of motorola) with Android 5.0.2 I downloaded some other forum.
I think, without knowing for sure, for more than I try with the common commands this dont "touch" or change the system version. It's like I always show as well (including with commands in cmd and phone) but practically nothing happened.
I appreciate any guidance to solve my problem.
I attach a "getall var" from my phone
-----------------------------
C:\WorkingMotoG>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4118
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA9300B3Y4
(bootloader) cid: 0x000C
(bootloader) channelid: 0x00
(bootloader) uid: D3BDB4030F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Jan 15 12:11:29 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_tefcl/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.14-L1.40/37:user/relea
(bootloader) ro.build.fingerprint[2]: se-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.Movistar.en.CL
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 01:58:53 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.18-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.18-0-g5742832
(bootloader) rpm.git: git=MBM-NG-V41.18-0-gcecd6e9
(bootloader) tz.git: git=MBM-NG-V41.18-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.18-0-g99084d5
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.059s
Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.
audit13 said:
Are you manually flashing each file/partition? You will get a validation error if you try to flash the motoboot file since you are already on a lollipop bootloader. A very important file to flash in my opinion is gpt.bin.
If you want a custom recovery on your phone, flash the recovery in fastboot or mfastboot, disconnect the USB cable, use the volume buttons to immediately boot into recovery without restarting the phone.
Click to expand...
Click to collapse
All the files loads OK, gpt.bin with exception of boot.img, it says: "version downgraded for boot" in the phone.
BTW: I do what you say about recovery and keep showing stock recovery. Dont show error messages, just no work.
Thanks anyway for you time...
Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?
audit13 said:
Which recovery are you trying to flash?
So you flash custom recovery, use volumes button to boot to recovery from fastboot screen and you keep getting stock recovery, right?
Click to expand...
Click to collapse
I'm trying to flash philz_touch_6.58.7-falcon.img
Thanks for your time
Did you try TWRP?
audit13 said:
Did you try TWRP?
Click to expand...
Click to collapse
Yes, but dont work neither
So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?
audit13 said:
So both recoveries flash without an error but you can't boot into either receiver right after flashing?
If it doesn't work, there may be something wrong with the internal memory?
Click to expand...
Click to collapse
Now my phone is recognized by Windows as "Qualcomm HS-USB QDLoader 9008". I try to fla**** with MotoFlasher and says:
OUTPUT: opening device: \\.\COM12
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for command mode
OUTPUT: OKAY [ -0.000s]
OUTPUT: identifying device
OUTPUT: ...serial = 0x3B4BDD3
OUTPUT: ...chip-id = 0x800 (MSM8226)
OUTPUT: ...chip-rev = 0x0
OUTPUT: ...sv-sbl = 0x0
OUTPUT: OKAY [ 0.002s]
OUTPUT: finding files
OUTPUT: ...programmer = programmer.mbn
OUTPUT: ...singleimage = singleimage.bin
OUTPUT: OKAY [ 0.000s]
OUTPUT: validating files
OUTPUT: OKAY [ 0.000s]
OUTPUT: switching to download mode
OUTPUT: OKAY [ 0.000s]
OUTPUT: greeting device for image downloading
OUTPUT: OKAY [ 0.001s]
OUTPUT: sending programmer
OUTPUT: OKAY [ 0.010s]
OUTPUT: flashing singleimage
OUTPUT: FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
OUTPUT:
OUTPUT:
That's not good. You may have to try the unbrick method to fix it.
audit13 said:
That's not good. You may have to try the unbrick method to fix it.
Click to expand...
Click to collapse
Which method? Can you gave me instructions or a link, please...?
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

why nobody helping me i need help

i flashed my a9 with SenseO V0,4 my firmware is 1.10 and the rom need 1.56
now my phone is only works with cm roms like mokee
i need a solution i tried to relock bootloader and flash stock ruu zips with the same cid not work
the names of the ruu i tried
2PQ9IMG_HIA[email protected]51002.3_29.05_F_release_454007_combined_signed
2PQ9IMG_HIA_AER[email protected]60122.4_43.05_F_release_469200_signed
i get the same error
C:\adb>fastboot flash zip rom.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
sending sparse 'zip' (126573 KB)...
OKAY [ 8.751s]
writing 'zip'...
(bootloader) HOSD CL#635503
FAILED (remote: 9 RU_SECURITY_FAIL zip from usb command in download mode)
finished. total time: 9.765s
my cid information
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) imei: 352636073422391
(bootloader) version-main: 1.10.401.7
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: HTC__J15
all:
finished. total time: 0.021s
please help i want to flash SenseO V0,4 or stock rom i hated stuck on cm roms
please try first: rename 2PQ9IMG_HIA_AERO_UHL_M60_SENSE7GP_MR_HTC_Europe_1. [email protected]_43.05_F_relea se_469200_signed
to 2PQ9IMG.img and put it to an SD-Card (first level, not into a folder) - plug in this sd-card.
If you boot into download-mode you will be asked if you want to flash this RUU. Volume up to start flashing.
Please report (do not write just error)
JochenP said:
please try first: rename 2PQ9IMG_HIA_AERO_UHL_M60_SENSE7GP_MR_HTC_Europe_1. [email protected]_43.05_F_relea se_469200_signed
to 2PQ9IMG.img and put it to an SD-Card (first level, not into a folder) - plug in this sd-card.
If you boot into download-mode you will be asked if you want to flash this RUU. Volume up to start flashing.
Please report (do not write just error)
Click to expand...
Click to collapse
thanks pro solved
i was flashing 2PQ9IMG.zip in relocked bootlader i try flashed after reunlock bootloader and its work now thanks for helping

need correct firnware for htc u11 any htc expert here

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?

Categories

Resources