I know this is 100% my fault but I was hoping that maybe the genius of XDA could help me out here.
1. Was using phone fine earlier.
2. Flashed Cyanogen 5.0.2
3. Flashed the newest radio version that Cyanogen linked in that thread
4. Didn't test
5. Started playing with 'fastboot oem' commands
6. Gave up tried to send a text message
7. No keybaord
8. Long press -> Input type -> nothing listed
9. Settings -> Keyboard and locale -> nothing about the keyboard.
10. Reflashed latest Cyanogen image
11. Still not working
I think during my fun of fastboot commands I screwed something up. The phone works perfect except I don't have a keyboard, the keypad in the dialer still works. Apparently somewhere along the line I lost my nandroid backup (yes, I know fail on me) I am currently looking for a keyboard app on the web that has a QR code so that I can install a 3rd party one from market. Will let you know how that goes.
Code:
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot flash radio
Radio_20100203_2_Signed_PASSION.img
sending 'radio' (24960 KB)... OKAY
writing 'radio'... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem -?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem secu
rity
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem s=of
f
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
... INFOtask: Parameter error
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
help
... INFOtask -1911570672 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
50
... INFOtask 80 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rtas
k 32
... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
... INFOstart keypad testing ...
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>a
'a' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot oem ?
... ^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rebo
ot
... FAILED (command write failed (Unknown error))
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
???????????? fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFOtask 8 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p passi
on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 1
getvar:1 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 2
getvar:2 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 3
2
getvar:32 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurity
security: on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurit
getvar:securit FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe flash hb
oot hboot-0.33.2012.img
sending 'hboot' (768 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>
Here are all of the commands that I have run since I last closed the CMD window.
Update: I have found the HTC Touch input APK and installed that on my phone. I can now long press input type and select touch input but whenever the keyboard should be coming up I get a force close. I know that on my G1 the HTC Touch input was iffy at best so I am still looking for another solution.
Another update: Got 'Better Keyboard' it works! (yay!) but when I goto click on the voice input it does not. I checked my search widget and the microphone icon is missing from there as well.
Someone posted their nandroid backup of a completely (rooted) stock n1 rom, search around for it and try installing it. I ran accross it while looking for tutorials on how to flash the stock N1 rom if that helps
Update: NOOOO!!!!!!! I did a full wipe from the bootloader (factory restore, dalvik-cache, rotate settings, and what ever that 4th one was and reinstalled cyanogen mod 5.0.2) bad news: all of my settings and applications are gone, as well as my customer ringtones. Very very sad day.
Oh yea, fixed the keyboard issue and the voice input issue. So I guess we can count this as win
Should have backed up your apps with astro or titanium
Oh I had a titanium backup, I just had to reinstall them all, and reset their locations on the home screens, and reset all of my ringtones and notification tones a process that takes a whole 5 - 10 min.
[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.
Code:
Send: fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_ocedugl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) version-main: 1.64.401.10
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF20000
(bootloader) cid: HTC__A07
all:
finished. total time: 0.006s
htc_fastboot finished. total time: 0.106s
i need stock rom or ruu.
Try this RUU
https://www.androidfilehost.com/?fid=3700668719832236904
thanks ur reply
minhnewpro said:
Try this RUU
https://www.androidfilehost.com/?fid=3700668719832236904
Click to expand...
Click to collapse
i trying it now.
please help me imei null.
I'm a little weak to speak English. Sorry for my english.
i installed this rom Link. 2PZFIMG_OCEAN_[email protected]70515_56.34_release_507305_signed_2_4.zip than after setup i locked BL. imei null.
https://androidfilehost.com/?fid=962187416754474071 i install this room. again imei null.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
'mke2fs' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
i hate this mistake.
Adream09 said:
i hate this mistake.
Click to expand...
Click to collapse
10. After flashing, your device can boot into Android but no signal or IMEI received, dont worry, continue these steps
11. Reboot into download mode, reflash TWRP, then boot to TWRP
12. At cmd windows, type
Code:
adb devices
adb shell
mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
13. Reboot device to check if IMEI received
14. If IMEI received, you should reflash stock recovery from RUU.zip, but reflash the RUU is recommended.
If not, try to format the persist partition manually again (step 12)
15. Done
thanks ur reply
minhnewpro said:
10. After flashing, your device can boot into Android but no signal or IMEI received, dont worry, continue these steps
11. Reboot into download mode, reflash TWRP, then boot to TWRP
12. At cmd windows, type
Code:
adb devices
adb shell
mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
13. Reboot device to check if IMEI received
14. If IMEI received, you should reflash stock recovery from RUU.zip, but reflash the RUU is recommended.
If not, try to format the persist partition manually again (step 12)
15. Done
Click to expand...
Click to collapse
thanks bro