Database Users

semi-bricked Fon - no sdcard available

Hello,
a friend gave me hier "bricked" fon. I could get it booting again, system is up and running - but with any sdcard. Not the external and neither the internal one.
That means I cant put a SAPIMG.nph or anything else to the sdcard.
I cant download an apk or modify anything.
adb shell is working, but certainly su not.
adb push hboot_2010_signed.img /sdcard
certainly doesnt work either, there is no sdcard!
ok, I tried now different fastboot operations.
to come closer:
./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... FAILED (remote: not allow)
... etc... all the normal stuff.. nothing wortks, I usualy get "Not allowed on a production phone"
What to do now, I have no clue anymore!
here my data:
./fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x880705C0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 64
INFOTAG:hwid 0x1
INFOTAG:skuid 0x1E300
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x2
INFODevice CID is not super CID
INFOCID is VODAP102
INFOsetting.cid::VODAP102
INFOserial number: HT93YKF06262
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =346
INFOactive commandline: board_sapphire.disable_uart3=1 board_sap
INFOphire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=6
INFO4 androidboot.baseband=2.22.19.26I androidboot.cid=VODAP102
INFO androidboot.carrier=VODA-Germany androidboot.keycaps=qwerty
INFO androidboot.mode=normal androidboot.serialno=HT93YKF06262 a
INFOndroidboot.bootloader=1.33.0007 no_console_suspend=1 console
INFO=null
INFOPARTITIOM_NUM_MAX =6 Valid partition num=6
Do you see? There is the kernel option board_sapphire.disable_sdcard=1 set !!! But I cant disable it with a fastboot -c option.
./fastboot getvar version-main
version-main: 1.89.162.1
./fastboot getvar cid
cid: VODAP102C??a
#########
Any help is appreciated, thanks!

Code:
fastboot oem enableqxdm 0
Regarding root... follow my guide found in my signature..

./fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
./fastboot devices
HT93YKF06262 fastboot
[[email protected] HTC]# ./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
this seemed to get me a little further:
./fastboot oem rebootRUU
... OKAY
[[email protected] HTC]# ./fastboot -c "board_sapphire.disable_sdcard=0 board_sapphire.disable_uart3=0" reboot
rebooting...
YEAH!"
but then..... still no sdcard when the OS was up :-(
any ideas?

Type
Code:
fastboot oem h
and post here the result.
Root and recovery = follow my guide found in my signature...
Just replace all "/sdcard" paths with "/data/local/tmp"

[Q] SPL/Radio mismatch - possible brick - UK Repair?

During an upgrade where I tried to S-OFF an HTC Magic I got to a point where I was installing from the SAPPIMG.nbh for 32a devices when it hung on the radio update (last of the main changes).
Long and short of it, is that the phone now has no recovery, boot loop and S-ON.
I can use fastboot only for booting to RUU mode and erasing the cache.
Code:
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0010 (SAPP10000)
CPLD-12
RADIO-6.35.08.19
Jun 2 2009, 17:28:28
I have tried following the examples of mumilover and also jeBach from this thread (http://forum.xda-developers.com/showthread.php?t=1231297&page=2).
On jeBach's suggestion I have tried flashing rom and rom1.zip but both times I get Checking Main Version... Update Fail! Errors.
Code:
fastboot getvar version-main
6.35.16.19
Which seems to be wrong/much higher - akin to a radio number?
Code:
\tools>fastboot oem boot
... INFOsetup_tag addr=0xA1200100 cmdline add=0x98072208
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 32
INFOTAG:hwid 0x1
INFOTAG:skuid 0x21401
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x2
INFODevice CID is not super CID
INFOCID is HTC__506
INFOsetting.cid::HTC__506
INFOserial number: HT96VKF02168
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =339
INFOactive commandline: board_sapphire.disable_uart3=1 board_sap
INFOphire.usb_h2w_sw=1 board_sapphire.disable_sdcard=0 smisize=3
INFO2 androidboot.baseband=6.35.08.29 androidboot.cid=HTC__506
INFOandroidboot.carrier=COMMON androidboot.keycaps=qwerty androi
INFOdboot.mode=normal androidboot.serialno=HT96VKF02168 androidb
INFOoot.bootloader=1.33.0010 no_console_suspend=1 console=null
INFOPARTITIOM_NUM_MAX =6 Valid partition num=6
FAILED (status read failed (Too many links))
I have tried mumilover's suggestion of special_sappimg.zip. It looks the most promising
Code:
\tools>fastboot flash zip "special_sappimg.zip"
sending 'zip' (11094 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
FAILED (remote: 43 main version check fail)
Which makes sense as the number is much higher. I have tried this with and without two different GoldCards.
When I create a zip myself with the files contained but modify android-info.txt with the higher version it is no longer signed and I get the following error.
Code:
sending 'zip' (11094 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
I've looked at using nbhextract but it doesn't work on the nbh file.
I think the main issue is that HBOOT is looking for a signature and when it doesn't find it, stops the process. I have no way of installing a recovery/hboot/spl that I know of after looking through a large number of pages here.
Is there any way to modify the sappimg.zip file with the special bootloader etc to have a higher version check whilst maintaining signature/or bypassing it such that the bootloader can be recovered. I need to fix the SPL/Radio before unlocking the bootloader from what I can tell but if it helps I did create an unlock_token before getting into this bricked state.
I have seen and read about the XTC clip. Would that work in unlocking to S-OFF and allowing for recovery/rest of the process to continue.
Failing that are there any people in the South East of England (Hertfordshire), who can recover through JTAG or other means for a price lower than the XTC clip?
Thank you in advance - any questions about other details - please post them and I can reply with answers, subject to the above limitations.

Just sent you a PM...

mumilover said:
Just sent you a PM...
Click to expand...
Click to collapse
Thanks very much to mumilover who spent a long time with me trying to help with this problem. :good:
Unfortunately the error was the version-main value is reported as being much higher than a standard RUU.
As such none of the standard RUU, rom methods will work.
I'm leaving this problem as unresolved, just so that the other posts which have more useful information are looked at first but from my side this is resolved; thanks very much once again mumilover.:highfive:

No problem... this one got away :0)

[FIX][GUIDE][INFO][01-JUN-2014]M7 "Active Cmdline Overflow" error and bootloop

[FIX][GUIDE][INFO][01-JUN-2014]M7 "Active Cmdline Overflow" error and bootloop
This is a collaboration of @cschmitt and myself. Many thanks to @cschmitt for his hard work and help :good::good:
Symptoms
1) Bootloader shows "active cmdline overflow (xxxx bytes)"
2) Unable to enter recovery (neither custom nor stock)
3) (possibly) everything you try reboots to bootloader
Cause
Basically it's because of a corrupt mmcblk0p19 [misc] partition, the [misc] partition includes the bootloader command block (BCB); @schmitt can elaborate on that more than I.
The most often times we've seen this, is when flashing HTC Droid DNA (device=dlx) ROM or kernel (kernel is included in the ROM) on a HTC One M7. The DLX kernel is in mmcblk0p19, and during installation this part of the installer script - run_program("/sbin/dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p19") - will overwrite and therefore corrupt your [misc] partition.
Problems (and why even an RUU won't restore your phone)
Some partitions, in particular mmcblk0p19 [misc] and mmcblk0p6 [mfg], are not contained in any RUU, as they are specific to each individual phone.
So what does a normal [misc] partition look like:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the ones that vary from device to device are the ones in bold green at offsets 0x304 and 0x31C, and what impact or influence they have I don't know.
OK, now get to the point, how do we fix this
Well you need adb commands, root and busybox... which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)
and @cschmitt has modified TWRP to disregard the BCB http://forum.xda-developers.com/showpost.php?p=52262603&postcount=13
Download from AndroidFileHost: twrp-recovery-2.7-m7-nobcb.img only applicable for M7_U or M7_UL models.
Step 1: Install the noBCB recovery
Code:
C:\ADB3>[B][COLOR=Blue]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I]<- we're in bootloader[/I]
C:\ADB3>[B][COLOR=Blue]fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (11278 KB)...
OKAY [ 1.500s]
writing 'recovery'...
OKAY [ 1.240s]
finished. total time: 2.740s
C:\ADB3>[B][COLOR=Blue]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.090s]
finished. total time: 0.090s
C:\ADB3>[B][COLOR=Blue]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
--> enter RECOVERY
If you are still unable to boot into recovery:
Users with S-OFF
Downgrade hboot to 1.44
Download 1.29.401.12_hboot_1.44.zip, check MD5, and flash it in ruu mode:
Code:
C:\ADB3>[B][COLOR=Blue]fastboot oem rebootRUU[/COLOR][/B]
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\ADB3>[B][COLOR=Blue]fastboot flash zip 1.29.401.12_hboot_1.44.zip[/COLOR][/B]
sending 'zip' (501 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.153s]
finished. total time: 2.402s
C:\ADB3>[B][COLOR=Blue]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
and enter RECOVERY
Users with S-ON
Try one of the following recoveries instead:
CWM_6.0.2.8_M7.img
cwm-recovery-m7-6.0.4.9-nobcb.img
Step 2: Backup your current mmcblk0p19 (it's always good to backup things before changing them)
Code:
C:\ADB3>[B][COLOR=Blue]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges[/I]
C:\ADB3>[B][COLOR=Blue]adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img[/COLOR][/B]
2045+0 records in
2045+0 records out
1047040 bytes (1022.5KB) copied, 0.048894 seconds, 20.4MB/s
C:\ADB3>[B][COLOR=Blue]adb pull /tmp/mmcblk0p19_bak.img[/COLOR][/B]
2272 KB/s (1047040 bytes in 0.450s)
C:\ADB3>[B][COLOR=Blue]dir[/COLOR][/B]
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB3
02/05/2014 18:40 <DIR> .
02/05/2014 18:40 <DIR> ..
02/05/2014 18:40 1,047,040 mmcblk0p19_bak.img
[B][I]^^ there it is[/I][/B]
Step 3: Download generic m7_u / ul mmcblk0p19
Download the M7_U / UL generic misc partition by @cschmitt:
http://forum.xda-developers.com/attachment.php?attachmentid=2774855&stc=1&d=1401633317
extract it and put it in your adb/fastboot folder.
Step 4: Restore the generic mmcblk0p19
Code:
C:\ADB3>[B][COLOR=Blue]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges[/I]
C:\ADB3>[B][COLOR=Blue]adb push mmcblk0p19_generic.img /tmp/[/COLOR][/B]
2130 KB/s (1047040 bytes in 0.479s)
C:\ADB3>[B][COLOR=Blue]adb shell dd if=/tmp/mmcblk0p19_generic.img of=/dev/block/mmcblk0p19[/COLOR][/B]
2045+0 records in
2045+0 records out
1047040 bytes (1022.5KB) copied, 0.048894 seconds, 20.4MB/s
C:\ADB3>[B][COLOR=Blue]adb reboot bootloader[/COLOR][/B]
You should now be back in bootloader with NO active cmdline overflow, be able to flash, enter the recovery of your choice, and install things appropriate for your phone.
:victory:
-------------------------------------------------------------------------------------------------------------------------------------------
Revision history
2nd May 2014:Initial preview release.​1st June 2014:Generic misc partition now confirmed working for S-On and S-Off devices, no longer need to "repair" the misc partition.​2nd August 2014:Added links for other recoveries for S-On users, and hboot downgrade instructions for S-Off users.​
-------------------------------------------------------------------------------------------------------------------------------------------
Disclaimer:
We are not responsible for anything going wrong with your phone!
credits:
@cschmitt for his work on the noBCB recovery, as well as his continued work on TWRP: http://forum.xda-developers.com/showthread.php?t=2708134
-------------------------------------------------------------------------------------------------------------------------------------------
If you found this thread useful or educational, please press the THANKS button for both of us .
-------------------------------------------------------------------------------------------------------------------------------------------

The attached mmcblk0p19 should work for any m7_u or m7_ul device.
Unzip and install mmcblk0p19.generic.bin per the instructions in step 4 of OP:
Code:
adb push mmcblk0p19.generic.bin /tmp/
adb shell dd if=/tmp/mmcblk0p19.generic.bin of=/dev/block/mmcblk0p19

As this is a "Work In Progress", you may have your doubts, and I cannot blame you in the slightest, for being VERY careful!!
So the main question is: has this ever been accomplished successfully?
The answer is yes http://forum.xda-developers.com/showpost.php?p=52345379&postcount=48 (or sort of because he used a rooted ROM instead of recovery, you'll need to read the entire thread mentioned)... the thread is here http://forum.xda-developers.com/showthread.php?t=2732757 , and though we haven't heard back from the OP, at least @donkeykong1 got it fixed!!
update, May 25, 2014: confirmed to have worked for 4 users
update, June 1, 2014: generic misc partition, confirmed working for S-On and S-Off users

Retired content, you can disregard this post
[WIP][POSSIBLE FIX][GUIDE][INFO][02-May-2014]HTC One M7 - "Active Cmdline Overflow" error and bootloader bootloop
This is a work in progress and a collaboration of @cschmitt and myself.
And it is still a rough draft!! so excuse any bad formatting (lack of colours, bold, italic, etc.)
Symptoms
1) Bootloader shows "active cmdline overflow (xxxx bytes)"
2) Unable to enter recovery (neither custom nor stock)
3) (possibly) everything you try reboots to bootloader
Cause
Basically it's because of a corrupt mmcblk0p19 [misc] partition, the [misc] partition includes the bootloader command block (BCB); @schmitt can elaborate on that more than I.
The most often times we've seen this, is when flashing HTC Droid DNA (device=dlx) ROM or kernel (kernel is included in the ROM) on a HTC One M7. The DLX kernel is in mmcblk0p19, and during installation this part of the installer script - run_program("/sbin/dd", "if=/tmp/boot.img", "of=/dev/block/mmcblk0p19") - will overwrite and therefore corrupt your [misc] partition.
Problems (and why even an RUU won't restore your phone)
Some partitions, in particular mmcblk0p19 [misc] and mmcblk0p6 [mfg], are not contained in any RUU, as they are specific to each individual phone.
So what does a normal [misc] partition look like:
the ones that vary from device to device are the ones in bold green at offsets 0x304 and 0x31C, and what impact or influence they have I don't know.
OK, now get to the point, how do we fix this
Well you need adb commands, root and busybox... which are only available in a custom recovery or a rooted ROM (with USB debugging enabled)
and @cschmitt has modified TWRP to disregard the BCB http://forum.xda-developers.com/showpost.php?p=52262603&postcount=13
Download from AndroidFileHost: http://www.androidfilehost.com/?fid=23329332407590873 only applicable for M7_U or M7_UL models.
Step 1: Install the noBCB recovery
Code:
C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HT34xxxxxxxx fastboot [I]<- we're in bootloader[/I]
C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (11278 KB)...
OKAY [ 1.500s]
writing 'recovery'...
OKAY [ 1.240s]
finished. total time: 2.740s
C:\ADB3>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.090s]
finished. total time: 0.090s
C:\ADB3>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.040s]
finished. total time: 0.040s
--> enter RECOVERY
Step 2: Backup your current mmcblk0p19
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges[/I]
C:\ADB3>[B][COLOR="Blue"]adb shell dd if=/dev/block/mmcblk0p19 of=/tmp/mmcblk0p19_bak.img[/COLOR][/B]
2045+0 records in
2045+0 records out
1047040 bytes (1022.5KB) copied, 0.048894 seconds, 20.4MB/s
C:\ADB3>[B][COLOR="Blue"]adb pull /tmp/mmcblk0p19_bak.img[/COLOR][/B]
2272 KB/s (1047040 bytes in 0.450s)
C:\ADB3>[B][COLOR="Blue"]dir[/COLOR][/B]
Volume in drive C has no label.
Volume Serial Number is 0622-9D4A
Directory of C:\ADB3
02/05/2014 18:40 <DIR> .
02/05/2014 18:40 <DIR> ..
02/05/2014 18:40 1,047,040 mmcblk0p19_bak.img
[B][I]^^ there it is[/I][/B]
Step 3: Repair mmcblk0p19
As I mentioned this is a work in progress, so for the time being, if you were able to backup your current mmcblk0p19, please compress and upload it, along with a "fastboot getvar all" (excluding IMEI and s/n).
And we'll have a look when we can, and send a "repaired" one back to you.
Step 4: Restore your repaired mmcblk0p19
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I]<- you need to be in custom recovery to
ensure [B]root[/B] privileges[/I]
C:\ADB3>[B][COLOR="Blue"]adb push mmcblk0p19_repaired.img /tmp/[/COLOR][/B]
2130 KB/s (1047040 bytes in 0.479s)
C:\ADB3>[B][COLOR="Blue"]adb shell dd if=/tmp/mmcblk0p19_repaired.img of=/dev/block/mmcblk0p19[/COLOR][/B]
2045+0 records in
2045+0 records out
1047040 bytes (1022.5KB) copied, 0.048894 seconds, 20.4MB/s
C:\ADB3>[B][COLOR="Blue"]adb reboot bootloader[/COLOR][/B]
You should now be back in bootloader with NO active cmdline overflow, be able to flash, enter the recovery of your choice, and install things appropriate for your phone.
:victory:
-------------------------------------------------------------------------------------------------------------------------------------------
Revision history
2nd May 2014: Initial preview release.​
-------------------------------------------------------------------------------------------------------------------------------------------
Disclaimer:
We are not responsible for anything going wrong with your phone!
credits:
@cschmitt for his work on the noBCB recovery, as well as his continued work on TWRP: http://forum.xda-developers.com/showthread.php?t=2708134
-------------------------------------------------------------------------------------------------------------------------------------------
If you found this thread useful or educational, please press the THANKS button for both of us .
-------------------------------------------------------------------------------------------------------------------------------------------

Some Background
It appears the 'active cmdline overflow' issue began with hboot 1.56. The error means that the command line passed from hboot to start the kernel (or recovery kernel) has exceeded the limit of the kernel command (1024 bytes.) Apparently, previous hboots ignored this error, but 1.56 halts the boot.
The kernel command line is constructed from (1) the command line contained within the kernel itself, (2) any arguments passed in to the kernel (i.e. with fastboot -c blah,blash boot boot.img), (3) the hboot itself, and (4) the bootloader command block (BCB) located in the misc partition (mmclbk0p19 on m7u, m7ul.)
A typical kernel command is around 700 to 800 bytes. You can check the kernel command by pulling the last_kmsg from the device
Code:
adb shell
su
cat /proc/last_kmsg > /sdcard/last_kmsg
exit
exit
adb pull /sdcard/last_kmsg
and searching for 'Kernel command line'. It will look something like this:
Code:
Kernel command line: poweron_status=1 reset_status=0 board_m7_ul.disable_uart3=0 diag.enabled=0 board_m7_ul.debug_uart=0 userdata_sel=0 androidboot.emmc=true androidboot.pagesize=2048 skuid=0 ddt=20 ats=0 dap=6 androidboot.lb=0 uif=?000 td.sf=0 td.td=0 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.ofs=696 imc_online_log=0 androidboot.efuse_info=4FSL androidboot.baseband=4T.24.3218.09 androidboot.cid=11111111 androidboot.devicerev=3 androidboot.batt_poweron=good_battery androidboot.carrier=ALL androidboot.mid=PN0712000 androidboot.keycaps=qwerty androidboot.dq=PASS androidboot.mode=recovery androidboot.serialno=HT34KWxxxxxx androidboot.bootloader=1.54.0000 lscd=0x1 wificd=0x1 androidboot.nledhw=0 androidboot.ddrmid=(0x6) acpu.footprint=FFFFFFFF abnrst=0 zygote_oneshot=on kmemleak=off rpm_debug.enable=0 console=ttyHSL0,115200,n8 androidboot.hardware=qcom user_debug=31
The BCB is 1088 bytes located at offset 0x800 in the misc partition (32 byte command, 32 byte status, 1024 byte recovery command.) Usually it zeroed out or contains a short command like 'recovery --wipe_data', but if it becomes corrupted (sometimes by flashing a rom for a different device which writes a kernel to p19) then this 'junk' data may be interpreted as kernel commands by the hboot and cause the command line to overflow, halting the boot.
Modified 'nobcb' TWRP Recovery
The modified TWRP recovery used in this solution is fairly simple. It has a modified get_args() method in recovery.cpp that skips reading the recovery command line arguments from the BCB, so that any junk data contained there is ignored and the recovery will boot successfully.
Additional Notes
I believe this solution requires S-OFF, as I don't think we can write to p19 with S-ON. We'll need to verify that, probably when someone with an S-ON device encounters 'active cmdline overflow'.
If that turns out to be the case I should be able to build a version of CM11 with a kernel that will ignore the BCB (similar to the no-bcb TWRP build) so that the device can boot an OS, use firewater to S-OFF, and then repair/restore p19.

Help me please
i do the first step but i still cant enter to recovery mode
bootloop on htc one logo
please help me

AjdinKuduzovic said:
i do the first step but i still cant enter to recovery mode
bootloop on htc one logo
please help me
Click to expand...
Click to collapse
after root and flash wrong rom i cant get in recovery mode any more i get (Entering Recovery mode) and its freeze on htc one logo
i flashed rom from this post http://forum.xda-developers.com/showthread.php?t=2626050
Deodexed version
please help me
Click to expand...
Click to collapse
Note: Target device: HTC Droid DNA (PL8320000)
you have just corrupted your misc partition, and are probably getting "active cmdline overflow" in the bootloader screen, and even an ruu won't fix that.
please post a "fastboot getvar all" (excluding IMEI and s/n) and a screenshot of bootloader.

nkk71 said:
please post a "fastboot getvar all" (excluding IMEI and s/n) and a screenshot of bootloader.
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34CW904354
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.142s

AjdinKuduzovic said:
C:\adb>fastboot getvar all
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
finished. total time: 0.142s
Click to expand...
Click to collapse
hmm, S-On
1- is your bootloader unlocked
2- did you check MD5 on the download to make sure it's not corrupt
3- can you copy/paste the output of your command prompt when you're flashing the noBCB recovery

nkk71 said:
hmm, S-On
1- is your bootloader unlocked
2- did you check MD5 on the download to make sure it's not corrupt
3- can you copy/paste the output of your command prompt when you're flashing the noBCB recovery
Click to expand...
Click to collapse
C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
sending 'recovery' (11278 KB)...
OKAY [ 1.364s]
writing 'recovery'...
OKAY [ 0.777s]
finished. total time: 2.151s
i tried to set s off i get error to
no luck for me

AjdinKuduzovic said:
C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
sending 'recovery' (11278 KB)...
OKAY [ 1.364s]
writing 'recovery'...
OKAY [ 0.777s]
finished. total time: 2.151s
i tried to set s off i get error to
no luck for me
Click to expand...
Click to collapse
3 questions, half an answer
after checking MD5, and flashing are you erasing cache.
If you can't get to recovery, there's nothing I can do.

nkk71 said:
3 questions, half an answer
after checking MD5, and flashing are you erasing cache.
If you can't get to recovery, there's nothing I can do.
Click to expand...
Click to collapse
yes i erase cache every time but still no luck
why i cant enter recovery mode i dont understand

AjdinKuduzovic said:
yes i erase cache every time but still no luck
why i cant enter recovery mode i dont understand
Click to expand...
Click to collapse
without a working recovery, there's not much that can be done.
can you extract the updater-script from the ROM you tried to flash, compress, and upload it. it's the following file inside the ROM.ZIP:
/META-INF/com/google/android/updater-script

nkk71 said:
without a working recovery, there's not much that can be done.
can you extract the updater-script from the ROM you tried to flash, compress, and upload it. it's the following file inside the ROM.ZIP:
/META-INF/com/google/android/updater-script
Click to expand...
Click to collapse
can you help me to S off for my htc one m7

AjdinKuduzovic said:
can you help me to S off for my htc one m7
Click to expand...
Click to collapse
you can't, to be able to S-Off you need a functioning ROM.

nkk71 said:
you can't, to be able to S-Off you need a functioning ROM.
Click to expand...
Click to collapse
what i can do ((((

@cschmitt, any idea why twrp_noBCB doesn't boot for this guy? do you have any time to build a CWM_noBCB, since sometimes (on regular recoveries, twrp bootloops, but cwm doesn't)... what do you think.

nkk71 said:
@cschmitt, any idea why twrp_noBCB doesn't boot for this guy? do you have any time to build a CWM_noBCB, since sometimes (on regular recoveries, twrp bootloops, but cwm doesn't)... what do you think.
Click to expand...
Click to collapse
i did the same problem and after search a lots of foruns i see one and solve the problem... just downgrade hboot and your htc one back to inicial
but if i upgrade hboot a got the same problem

Watashi_PT said:
i did the same problem and after search a lots of foruns i see one and solve the problem... just downgrade hboot and your htc one back to inicial
but if i upgrade hboot a got the same problem
Click to expand...
Click to collapse
yes, that's similar to the case that was fixed, we used hboot 1.44 + the noBCB recovery to get the misc partition, he sent it to us, we fixed it, and he flashed it back, and then was able to upgrade both hboot and use a normal recovery again without problems.

gazment said:
So I have a new getvar all after the ota install of latest sense 6.0 developers edition w/ self flash of hboot 1.44 afterwards:
Code:
C:\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
So weird!
i attached the blk019 .img file
Click to expand...
Click to collapse
Yep it's corrupt; another DLX kernel in there:
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=[B][COLOR="Red"]dlx[/COLOR][/B] user_debug=31
I'll fix it and upload in a while....
EDIT: are you using custom recovery, or rooted rom to "dd" the partition?
gazment said:
thanks nkk71!
At the time I I made blk019 backup I didn't have root I believe just twrp no bcb recovery.
Click to expand...
Click to collapse
Attached is the fixed partition, extract it and put it in your adb/fastboot folder. then just boot back into the noBCB recovery and follow step 4.
and please be careful with the dd command, be sure to type it correctly (or copy/paste), you don't want to overwrite the wrong partition!!!
Let me know how it goes.

[RUU]M9+ RUU file

“ht”tp:/“/pan.baidu.c”o“m/s/1o6zHTpC 密码（psw）: y571
Now , just has 3 file NAME :
ZhongZhuangbao_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_431201.ZIP
ZhongZhuangbao_HTCCN_CHS_2_1.08.1405.6_Radio_1.1506V24P14.1605.0421__431815_DownLoadModen.zip
ZhongZhuangbao_HTCCN_CHS_2_1.08.1405.6_Radio_1.1506V24P14.1605.0421__431815.zip
I upload speed is only 10-45KB, all the M9+ruu add up to have 50GB.
Now I only upload 3 most people need.
If other people need more, I will upload more.
2GB file takes a week
I've got a question
Publish all the NEWEST RUU What damage to HTC？I don't want to hurt the interests of the HTC company.

Good job, guy!!
TW(709),please!
Thanks!
Sent from my HTC_M9pw using XDA Free mobile app

UAE RUU
Do you have the update ruu for the UAE version .? thnx in advance

Thanks for share it
But,it's only china?

thank you
it is only in chines . can you try to upload it in another website please ?

Thank you so much!!! Could you share HK(708)? =)

I'll upload some too to mega.nz when I'll get back from vacation

0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this on S-On, you must have your device Relocked (on S-Off you don't need to relock) and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800

tbalden said:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this you must have your device Relocked and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800
Click to expand...
Click to collapse
Hi tbalden,
Even the MD5checksum is verified, still can't find the system.img in the rom.zip
the size in the zip file also seems not right.
May you check it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

you need to use a linux, there latest ruuveal, 'ruuveal -D xy.zip' to properly unzip all with system image parts as these are large zips (special format). Then you will have to unify the system img parts with Hima_ImgTool from m9 forum threads. Then you can mount and/or browse them as EXT4 filesystems.
Also, if you are thinking about restoring to stock, it might be better to just flash the whole zip as it's intended by HTC with fastboot.

tbalden said:
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
1.79 GB https://mega.nz/#!MEVWDS6a!K_LTgIXX4C7VLb-to9PeOij_6J7fooJVJo2hwju71SI
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
2.10 GB https://mega.nz/#!FFslyDzD!8INOzNsGkSqH9EBaVrgq7E-kJPzeAq0z93JP_GNTBqU
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
2.25 GB https://mega.nz/#!xNN1nTiS!yS6U9RQOk1Y_AcH2aVen5LAfZug4iVsDp23NwfUWzQ8
0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
2.09 GB https://mega.nz/#!IRtz1A6b!EFsQgQyZ856OU7eEy7yvGuD5dS_4G8K-pI2grk8hrwg
MD5s:
7a2e7e2e973f3209eaeff1db96bed859 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_TW_1.08.709.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430417_signed.zip
e28e0736489da46fee6e0ae72aff8471 *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTCCN_CHS_2_1.08.1405.5_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430624_signed.zip
ed8436646f3dc4542f3b2036300d6e2d *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_hTC_Asia_WWE_1.08.707.4_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_430419_signed.zip
8fa1b59afcd28f2e229728306aba3c6a *0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip
To flash this you must have your device Relocked and then in fastboot mode:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Please be aware that you'll lose all data doing this.
If you're S-On you can only flash the zip that is for you CarrierID (CID). With superCID or modified CID value through S-OFF you can try to flash other regions RUUs.
DISCLAIMER:
All responsibility and risk you take on yourself downloading and using these in any way. Be sure to know what you do!
Read about similar topic here: http://forum.xda-developers.com/showthread.php?t=2251800
Click to expand...
Click to collapse
thanks for the signed RUUs. I'm downloading now I will try them later. I have a question. how can I install different region RUUs? Do I have to change MID like in htc one m8 or m9? If yes, where can I find mid for specific regions/?
---------- Post added at 02:01 AM ---------- Previous post was at 01:22 AM ----------
load_file: could not allocate -2053247557 bytes
error: cannot load '0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip'
I'm getting this error. anyone explain plz/

jura.m said:
thanks for the signed RUUs. I'm downloading now I will try them later. I have a question. how can I install different region RUUs? Do I have to change MID like in htc one m8 or m9? If yes, where can I find mid for specific regions/?
---------- Post added at 02:01 AM ---------- Previous post was at 01:22 AM ----------
load_file: could not allocate -2053247557 bytes
error: cannot load '0PK7IMG_HIAU_ML_TUHL_L50_SENSE70_HTC_Europe_1.08.401.6_Radio_1.1506V24P14.1605.0421_HT[W.T]_release_431201_signed.zip'
I'm getting this error. anyone explain plz/
Click to expand...
Click to collapse
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.

tbalden said:
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.
Click to expand...
Click to collapse
Code:
D:\M9pw>htc_fastboot oem rebootRUU
...
OKAY [ 0.000s]
finished. total time: 0.000s
htc_fastboot finished. total time: 0.173s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.696s]
writing 'zip'...
(bootloader) HOSD CL#549681
(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]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.244s
htc_fastboot finished. total time: 25.291s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.575s]
writing 'zip'...
(bootloader) HOSD CL#549681
(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
[COLOR="Red"](bootloader) ERR ZIP signature checking failed...[/COLOR]
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.481s
htc_fastboot finished. total time: 30.171s
D:\M9pw>fastboot reboot
rebooting...
finished. total time: -0.000s
Now,try to copy the file to SD card.

yvtc75 said:
Code:
D:\M9pw>htc_fastboot oem rebootRUU
...
OKAY [ 0.000s]
finished. total time: 0.000s
htc_fastboot finished. total time: 0.173s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.696s]
writing 'zip'...
(bootloader) HOSD CL#549681
(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]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.244s
htc_fastboot finished. total time: 25.291s
D:\M9pw>htc_fastboot flash zip ROM.zip
htc_fastboot v3.0.8a (2015-04-10)
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (225962 KB)...
OKAY [ 12.575s]
writing 'zip'...
(bootloader) HOSD CL#549681
(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
[COLOR="Red"](bootloader) ERR ZIP signature checking failed...[/COLOR]
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 19
(bootloader) [email protected]
FAILED (remote: 19: fail to flash via downloadzip)
finished. total time: 18.481s
htc_fastboot finished. total time: 30.171s
D:\M9pw>fastboot reboot
rebooting...
finished. total time: -0.000s
Now,try to copy the file to SD card.
Click to expand...
Click to collapse
Do you have the bootloader on higher version than the zip? I think you can't do that. You need the same main version or lower on the phone boot loader (1.08) to flash it. I used the Chinese zip a few times and it went well but I haven't updated the bootloader over 1.08
http://www.xda-developers.com/misctool-gives-htc-users-power-to-readwrite-main-version/

tbalden said:
Do you have the bootloader on higher version than the zip? I think you can't do that. You need the same main version or lower of phone boot loader (1.08) to flash it. I used the Chinese zip a few times and it went well but I haven't updated the bootloader over 1.08
http://www.xda-developers.com/misctool-gives-htc-users-power-to-readwrite-main-version/
Click to expand...
Click to collapse
I misunderstood the post.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
OK,thanks tbalden.
I know the issue. I forgot this main version I ever used in the era of One X.
I must defraud the RUU of main version in the android-info.
Thanks again!! :good:

About modifying main version: I think that will only work with s-off, or maybe even there not either. You need to modify the main version of your phone, not the zip, because modifying the zip will make the signature invalid on it and it won't flash.

tbalden said:
Are you using HTC fastboot exe? Google's fastboot can't handle large files.
Another thing, is it sure that you're in ruu mode?
About the mid I'm not sure there's any such list yet.
Click to expand...
Click to collapse
thanks man. I figured that out after I googled that issue I was getting. I downloaded htc fastboot and done that. I got cid error when I tried to install 707 and 709 RUUs. My device was already s-offed and I changed cid to supercid 11111111. after that I managed to install 707 version. thanks for your help.

yvtc75 said:
I misunderstood the post.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
9. What if I have an RUU? Do I need to worry about all this OTA nonsense?................SuSam
Click to expand...
Click to collapse
Wait for RUU 1.81 release, and now my phone device is 1.61, so 1.08 version is too low, can not be used unless the s-off ~ :crying:

玻璃施工 said:
Wait for RUU 1.81 release, and now my phone device is 1.61, so 1.08 version is too low, can not be used unless the s-off ~ :crying:
Click to expand...
Click to collapse
Wow.......... cool name!! :good:
Yep, wait for the newest RUU.
Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software.

yvtc75 said:
Wow.......... cool name!! :good:
Yep, wait for the newest RUU.........Susan
Click to expand...
Click to collapse
mm... Their ROM is the only antidote to save M9+ (take the Low stool

Instal Blackberry priv Non US Carrier autoloader on AT&T

Hey
Is it possible to install Non US Carrier autoloader on AT&T to get rid of AT&T bloatware and to getting latest update via OTA?
Because I am live outs the US and did not have AT&T SIM.
Sent from my STV100-1 using Tapatalk

Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.

Thank you.
Sent from my iPad using Tapatalk

I did it today. It is woks perfectly. Thank you a lot :good:

I had a typo in my post regarding how to avoid wiping data while flashing. The 2nd command to comment out should be "flash userdata %IMG%\userdata.img".

Hey Kraml, your solution has a lot of interested folks over at Crackberry. Can you post some more detailed instructions?
Better yet, if you have an autoloader that's Marshmellow based already set up and share it with the community you'd become an instant rock star!
Here's the thread I started:
forums dot crackberry dot com/blackberry-priv-f440/potential-solution-our-vzw-att-friends-older-roms-1085292/#post12578681
replace dots with periods to get the link!

Does this convert AT&T to factory unlock??

zed011 said:
Does this convert AT&T to factory unlock??
Click to expand...
Click to collapse
No. It removes ATT software only.

kraml said:
I had a typo in my post regarding how to avoid wiping data while flashing. The 2nd command to comment out should be "flash userdata %IMG%\userdata.img".
Click to expand...
Click to collapse
Hey i have tried as you said and removed both the lines "fastboot.exe oem securewipe" "flash userdata %IMG%\userdata.img" from flashall.bat But i am getting the following error.
I am using AT and T unlocked device and i have tried the AT and T version AAG202 an i am getting the following error
Could you please help me out
BY INSTALLING THE SOFTWARE, YOU ARE AGREEING TO BE BOUND BY THE BlackBerry
Solution License Agreement which can be reviewed at www.blackberry.com/leg-
al/bbsla. IF YOU HAVE ANY QUESTIONS OR CONCERNS ABOUT THE TERMS OF THIS AG-
REEMENT, PLEASE CONTACT blackberry AT [email protected]. PLEASE READ
THIS DOCUMENT CAREFULLY BEFORE INSTALLING OR USING THE SOFTWARE.
***************************************************************************
Note:If device is not in fastboot mode
Please switch to fastboot mode by holding the power and volume down key for 30s
This script will wipe off all user data. Do you want to continue? [y/n]:y
'.\host\windows-x86\bin' is not recognized as an internal or external command,
operable program or batch file.
"It may take 5 to 15 minutes to securely wipe the device"
target reported max download size of 536870912 bytes
sending 'tz' (560 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.015s
target reported max download size of 536870912 bytes
sending 'hyp' (92 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.018s
target reported max download size of 536870912 bytes
sending 'sdi' (27 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.019s
target reported max download size of 536870912 bytes
sending 'pmic' (32 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.018s
target reported max download size of 536870912 bytes
sending 'rpm' (187 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.027s
target reported max download size of 536870912 bytes
sending 'sbl1' (495 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.032s
target reported max download size of 536870912 bytes
sending 'aboot' (1453 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.027s
target reported max download size of 536870912 bytes
sending 'bootsig' (0 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'recoverysig' (0 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'boot' (17908 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'recovery' (17908 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.021s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.021s
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce
flashing unlock_bootloader <request> Issue unlock bootloader using request
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
target reported max download size of 536870912 bytes
sending 'modem' (68433 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.014s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.016s
target reported max download size of 536870912 bytes
erasing 'oem'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.015s
rebooting...
finished. total time: 0.008s
Press any key to close this window

its because your phone has password protection. simply remove password / pin or pattern lock screen

Could someone make a file the that is the AT&T update package minus the bloatwear and without the wipe. I would gladly donate for it working.
Sent from my STV100-1 using Tapatalk
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
Dilini said:
its because your phone has password protection. simply remove password / pin or pattern lock screen
Click to expand...
Click to collapse
Could someone make the file for our AT&T Priv, minus the firmware and where it doesn't wipe the device. I would gladly pay for it!
Sent from my STV100-1 using Tapatalk

Ew, buddy I've done for myself with the instruction pretty easy except PIN password part.
I've pack whole files as a size 1.6GB 7z file, based on my carrier upload limit it's too big to uploading it, estimate more than an hour, so I packed the "Patch"
part for u, which means u still need to access the official site to download AT&T part and decompress it http://global.blackberry.com/content/blackberry-com/en/support/smartphones/Android-OS-Reload.html
Then download my "Patch" part https://drive.google.com/open?id=0B-qpp_ciC37MUEVmSDYzR3c2OXc
Decompress it any where u like then copy it to the folder where your AT&T files decompressed, confirm overwrite the same name files.
Then just run the flashall.bat
And yes I only modified Windows version
theusername said:
Could someone make a file the that is the AT&T update package minus the bloatwear and without the wipe. I would gladly donate for it working.
Sent from my STV100-1 using Tapatalk
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
Could someone make the file for our AT&T Priv, minus the firmware and where it doesn't wipe the device. I would gladly pay for it!
Sent from my STV100-1 using Tapatalk
Click to expand...
Click to collapse

Good morning, I have a question, recently bought the BlackBerry priv AT & T unlocked, I wonder if I can put Android's own BlackBerry 6 clean without losing the unlock? or I have to put the AT & T it? I run the risk of having a locked phone? Excuse my English.

Do we know if this is an error which can be ignored safely or there is fix for this?
error: cannot load '.\img\cache.img.\host\windows-x86\bin\fastboot.exe'
target reported max download size of 536870912 bytes

Hello!
May i ask a question does your patch can work with new version AAG873?
Thanks for your kind reply
loachh said:
Ew, buddy I've done for myself with the instruction pretty easy except PIN password part.
I've pack whole files as a size 1.6GB 7z file, based on my carrier upload limit it's too big to uploading it, estimate more than an hour, so I packed the "Patch"
part for u, which means u still need to access the official site to download AT&T part and decompress it http://global.blackberry.com/content/blackberry-com/en/support/smartphones/Android-OS-Reload.html
Then download my "Patch" part https://drive.google.com/open?id=0B-qpp_ciC37MUEVmSDYzR3c2OXc
Decompress it any where u like then copy it to the folder where your AT&T files decompressed, confirm overwrite the same name files.
Then just run the flashall.bat
And yes I only modified Windows version
Click to expand...
Click to collapse

And also: Could you do a Mac Version as well?
Greetings from Germany

Did anyone else that did this get an OTA update notification today? I'm actually surprised I would get something considering I'm not using an AT&T simcard.
Update:
Looks like this is the reason why I received the OTA update. Blackberry is starting to support the unlocked AT&T phones. http://www.techtimes.com/articles/1...receives-updates-directly-from-blackberry.htm

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
I just did this on the Verizon variant, which i'm using on T-Mobile in the US, and it is insane how much better it's running. I'm pretty sure everyone should do this if they don't have the factory unlocked model

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
Do you know if this will work on a verizon branded model? I am looking at a VZ model for cheap but will be using it on Tmo, on a side note anyone know if the VZ model supports wifi calling on Tmo? Thanks.

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Click to expand...
Click to collapse
I have additionally also replaced system.img with the one from the common autoloader. Otherwise the "System update" wouldn't do anything. Now I get the normal Android update screen, the not dreaded "AT&T Software update". I hope that it'll actually update.
Stefan