Root status of bump/open-bump for LG Volt

jhofseth · Jan 22, 2015

I read bump was shutdown, but found this python2 script for open-bump:
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
I can't test to see if it works for modified ZV5 boot.img's until I replace the third laptop in-a-row stolen. Please let me know if this works or if some alternate bump-related solution works. Thanks in advance! Cheers.

bg4m3r · Jan 22, 2015

Wth... Damn the man! Lol

elisam98 · Jan 22, 2015

jhofseth said:
I read bump was shutdown, but found this python2 script for open-bump:
http://forum.xda-developers.com/lg-g2/orig-development/tool-bump-sign-boot-images-t2950595
I can't test to see if it works for modified ZV5 boot.img's until I replace the third laptop in-a-row stolen. Please let me know if this works or if some alternate bump-related solution works. Thanks in advance! Cheers.

Yes, that Open Bump definitely works for the Volt. I use it frequently on images.

whoshotjr2006 · Jan 22, 2015

Yep been using this for a while now for recoveries and Roms, but nice find.

jhofseth · Feb 4, 2015

whoshotjr2006 said:
Yep been using this for a while now for recoveries and Roms, but nice find.

Whoshotjr2006 and/or Elisam, what syntax do you guys use? Everytime I use it, I extract the ~22mb boot.img and edit init.rc in ramdisk to add init.d support, then: python2 open_bump.py "/path/to/your/boot.img" (using actual directory; syntax example from above URL) it removes the padding making it ~11mb. If I flash modded boot.img with Flashify and reboot, it never gets past going into fastboot. I always have to TWRP restore boot, and it doesn't matter if I hand-edit init.rc and repack boot.img manually or use aroma installer init.d injector to save injected boot.img (before using open bump + Flashify)--the result is the same. So, the common denominator seems to be open bump. Am I missing an option or something? Thanks in advance.

Bad_MOFO_33 · Feb 4, 2015

jhofseth said:
Whoshotjr2006 and/or Elisam, what syntax do you guys use? Everytime I use it, I extract the ~22mb boot.img and edit init.rc in ramdisk to add init.d support, then: python2 open_bump.py "/path/to/your/boot.img" (using actual directory; syntax example from above URL) it removes the padding making it ~11mb. If I flash modded boot.img with Flashify and reboot, it never gets past going into fastboot. I always have to TWRP restore boot, and it doesn't matter if I hand-edit init.rc and repack boot.img manually or use aroma installer init.d injector to save injected boot.img (before using open bump + Flashify)--the result is the same. So, the common denominator seems to be open bump. Am I missing an option or something? Thanks in advance.

No need to edit ramdisk, just use extract boot.img to openbump dir and run the command. We have it incorporated into device folder and boardconfig.mk file to automatically bump image during build

donjuro · Feb 5, 2015

Bad_MOFO_33 said:
No need to edit ramdisk, just use extract boot.img to openbump dir and run the command. We have it incorporated into device folder and boardconfig.mk file to automatically bump image during build

But he's trying to incorporate init.d support.

jhofseth · Feb 10, 2015

donjuro said:
But he's trying to incorporate init.d support.

I found I was using too old of boot image tools. Open bump works for me now, but init.d screws up when I edit init.rc per online tutorials. At least I can successfully flash now.

Root status of bump/open-bump for LG Volt

Member

Android Expert

Well-Known Member

Android Enthusiast

Member

Android Enthusiast

Android Expert

Member

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads