[Q] Active cmdline overflow!

Search This thread

donkeykong1

Senior Member
Aug 6, 2012
3,901
2,133
Sesvete, Zagreb
So, did anyone figure out what this "active cmdline overflow" means and how to get rid of it? I managed to fix my phone from it by flashing 1.29.401.12 firmware. After that I flashed 4.19.401.8 without a problem, but 4.19.401.11, Elemental kernel and ARHD 52 send me back to bootloader and that nasty "active cmdline overflow"
 

gazment

Senior Member
Feb 25, 2009
59
2
Dearborn, MI
I'm in the same boat seems issue won't even let me use firewater to soff I've tried everything. Isn't there a tool that lets you pull blks from phone then edit in hex then push back.

I wouldn't know where to start in recovering all the phones partitions to stock.
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
I'm in the same boat seems issue won't even let me use firewater to soff I've tried everything. Isn't there a tool that lets you pull blks from phone then edit in hex then push back.

I wouldn't know where to start in recovering all the phones partitions to stock.

Are you able to boot into ROM or custom recovery? and please post a "fastboot getvar all" excluding IMEI and s/n.
 
  • Like
Reactions: gazment

gazment

Senior Member
Feb 25, 2009
59
2
Dearborn, MI
Are you able to boot into ROM or custom recovery? and please post a "fastboot getvar all" excluding IMEI and s/n.

I can't boot into custom recovery or the rom. they both send me back into bootloader.

Heres my getvar all:
Code:
C:\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-076e0e17
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.074s

C:\android\sdk\platform-tools>

Thanks so much for the quick reply.

PS When I rebootRUU (which works when it feels like it) it seems like I can only successfully flash the google edition zip. However any ota updates that I d/l that increases the hboot version above 1.54 cause the system to hang until I rebootRUU again to flash over hboot 1.44 and the system starts booting and working again.:confused:
 

donkeykong1

Senior Member
Aug 6, 2012
3,901
2,133
Sesvete, Zagreb
I can't boot into custom recovery or the rom. they both send me back into bootloader.

Heres my getvar all:
Code:
C:\android\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.1540.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA************
(bootloader) imei: ******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-076e0e17
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.074s

C:\android\sdk\platform-tools>

Thanks so much for the quick reply.

PS When I rebootRUU (which works when it feels like it) it seems like I can only successfully flash the google edition zip. However any ota updates that I d/l that increases the hboot version above 1.54 cause the system to hang until I rebootRUU again to flash over hboot 1.44 and the system starts booting and working again.:confused:
I had exact same problem. Just flash 1.44 RUU and get your phone to boot up and then report. I will lead you to a fix with nkk's help (if he's willing [emoji4])
 
  • Like
Reactions: gazment

gazment

Senior Member
Feb 25, 2009
59
2
Dearborn, MI
I had exact same problem. Just flash 1.44 RUU and get your phone to boot up and then report. I will lead you to a fix with nkk's help (if he's willing [emoji4])

Currently on developers edition 4.4.2 w/ sense 6.0 but of course had to flash hboot 1.44 to make the Rom boot. Originally the phone was T-MOB101. Any help help would be great you guys. Thanks
 

donkeykong1

Senior Member
Aug 6, 2012
3,901
2,133
Sesvete, Zagreb
Currently on developers edition 4.4.2 w/ sense 6.0 but of course had to flash hboot 1.44 to make the Rom boot. Originally the phone was T-MOB101. Any help help would be great you guys. Thanks
You need to pull your mmclbk019 from your phone with file explorer or fastboot and post it here. I don't know if my p19 partition will work for you, but nkk will help us with that [emoji4]
http://xdaforums.com/showthread.php?t=2732757

[Q] Help Please!!! Active cmdline overflow (1085 bytes)
Here is the thread that solved my problem. Take a look and hopefully it will solve yours too [emoji106]
 
Last edited:
  • Like
Reactions: gazment

gazment

Senior Member
Feb 25, 2009
59
2
Dearborn, MI
You need to pull your mmclbk019 from your phone with file explorer or fastboot and post it here. I don't know if my p19 partition will work for you, but nkk will help us with that [emoji4]
http://xdaforums.com/showthread.php?t=2732757

[Q] Help Please!!! Active cmdline overflow (1085 bytes)
Here is the thread that solved my problem. Take a look and hopefully it will solve yours too [emoji106]

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-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA**************
(bootloader) imei: 355*****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3752mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s

C:\android\sdk\platform-tools>

So weird!

i attached the blk019 .img file
 

Attachments

  • mmcblk0p19_bak.zip
    1,016.2 KB · Views: 74

donkeykong1

Senior Member
Aug 6, 2012
3,901
2,133
Sesvete, Zagreb
Now we just need to wait for nkk or chsmitt to reply. I can give you my p19 file but your mid is different from mine and I'm not sure it's a good idea to flash it
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
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

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

Senior Member
Feb 25, 2009
59
2
Dearborn, MI
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?

thanks nkk71!

At the time I I made blk019 backup I didn't have root I believe just twrp no bcb recovery.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Got the same issue after flashing firmware

    Resolved by doing the supercid move :)

    fastboot oem writecid 11111111

    Good luck !

    Fabrice
    2
    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

    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?
    1
    S-ON . CWMD install new rom. Reboot and --- this ACTIVE CMDLINE OVERFLOW.
    I can't hboot downgrade. can't CWMD or TWRP . Can't ADB Sideload! -Nothing:(
    I love this phone please help!

    can you please:
    1- a screenshot of bootloader
    2- a "fastboot getvar all" (xxx-out evertyhing after the first 2 digits of IMEI)
    3- what were you flashing and how (details and links, please)
    1
    M7_UL PVT SHIP S-ON RH
    HBOOT-1.56.0000
    RADIO-4A.23.3263.28
    OS-

    ACTIVE CMD LINE OVERFLOW! (1028 Bytes)

    New rom i install from CWMD. Install from phone memory.
    ROM name --- DLX_WL_K442_SENSE55_MR_4.19.401.8_odexed

    http://xdaforums.com/devdb/project/dl/?id=3599.

    Thenks for help!;) Irealy miss my HTC One.
    Best regards!

    Sorry to be the bearer of bad news, but you're going to miss your phone even more when you send it to repair. :(

    hboot+radio version would imply you "should" be on 4.19.401.8, but obviously are not as OS is now blank and that's because the rom you tried to install overwrote your misc partition:
    Code:
    ui_print(">>> Flashing kernel");
    	run_program("/sbin/dd", "if=/tmp/boot.img", "of=[B][COLOR="Red"]/dev/block/mmcblk0p19[/COLOR][/B]"));

    and that's because the ROM you tried is for: "Target device: HTC Droid DNA (PL8320000)" (it's in the OP!!)

    80fd5f13a2b2c908df494890a462533a.png



    So since you are unable to get to custom recovery anymore, and there's no way (that I know of) of fixing the misc partition using fastboot only (especially with S-On), then it's off to repair.

    Sorry mate :(
    1
    thanks nkk71!

    At the time I I made blk019 backup I didn't have root I believe just twrp no bcb recovery.

    posted the repaired partition here: http://xdaforums.com/showthread.php?p=52910780&postcount=20