Database Develop

[HACK] compiled mkbootimg and unpack/repack linux scripts for boot.img

want to edit your boot.img?
included files in zip: mkbootimg (i compiled this file from android source), unpack-bootimg.pl, repack-bootimg.pl
i edited the repack script to compile the nexus s img correctly.
Code:
--base 0x30000000 --pagesize 4096
first dump original boot.img:
Code:
cat /dev/mtd/mtd2 > /sdcard/boot.img
then drag/drop to your linux box to edit file.
use unpack script:
Code:
./unpack-bootimg.pl boot.img
you will end up with 2 compressed files and 1 folder.
finished editing and want to repack boot.img, for example:
Code:
./repack-bootimg.pl <kernel> <ramdisk-directory> <outfile>
most info and scripts pulled from here: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images, thanks to the original author.
test your new boot.img:
Code:
fastboot boot boot.img

Two things:
1. if you have any bad blocks in your boot partition, this method will fail to extract the boot.img (you need to skip bad blocks, but cat will just get an error)
2. you can replace just the kernel (leaving the ramdisk and parameters intact) using:
Code:
% fastboot flash zimage zImage
The bootloader will read-modify-write the boot partition, replacing the kernel only.

how would you skip bad blocks? i never thought of a phone as having bad blocks.

k0mpresd said:
i never thought of a phone as having bad blocks.
Click to expand...
Click to collapse
All flash devices can have bad blocks. But it usually isn't something the end user would notice, unless there are so many and something is wrong that you're losing drive space.
edit: more info here if your curious http://en.wikipedia.org/wiki/Flash_memory

hmm, very strange thing happening to me. I've only gotten my boot.img to compile and boot successfully once with this method, but now I can't seem to get it to compile? I keep getting errors of the file name or file type. I'm using the correct usage.. If I compile manually with mkbootimg on the cmd line it'll compile but it won't boot. Just bootloops at the Google splash..

Jroid try my Matr1x kernel and see what happens
Sent from my Nexus S using XDA App

The problem seems to be compiling the boot with the perl scripts, not the kernel itself.

Try manually:
Once unpacked do the boot.img-ramdisk.cpio.gz with the following command (moved to the ramdisk folder):
Code:
#sudo find . | cpio -o -H newc | gzip > ../<your boot name>.img-ramdisk.cpio.gz
Then cd ../
And repack:
Code:
#./mkbootimg --kernel <your boot name>.img-kernel.gz --ramdisk <your boot name>.img-ramdisk.cpio.gz --base 0x30000000 --pagesize 4096 -o boot.img

you can replace just the kernel (leaving the ramdisk and parameters intact) using:
Code:
% fastboot flash zimage zImage
The bootloader will read-modify-write the boot partition, replacing the kernel only.
Click to expand...
Click to collapse
It won't work on the Nexus S.

python08 said:
It won't work on the Nexus S.
Click to expand...
Click to collapse
exactly, i'd love to be able to do this for some testing but it doesn't allow me.
EDIT: yes it does. Swetland is right

Chamb' said:
Try manually:
Once unpacked do the boot.img-ramdisk.cpio.gz with the following command (moved to the ramdisk folder):
Code:
#sudo find . | cpio -o -H newc | gzip > ../<your boot name>.img-ramdisk.cpio.gz
Then cd ../
And repack:
Code:
#./mkbootimg --kernel <your boot name>.img-kernel.gz --ramdisk <your boot name>.img-ramdisk.cpio.gz --base 0x30000000 --pagesize 4096 -o boot.img
Click to expand...
Click to collapse
I've tied compiling a boot both manually (with cmdline) and with the perl scripts and have used a simple kernel.gz and ramdisk.cpio.gz for my file names.. doesn't really matter what I name it as long as it has the correct file format in this .gz and .cpio.gz right? the manual compile goes fine with base 0x30000000 and pagesize 4096
however, it does not boot and will bootloop at the Google splash

Used boot.img extracted from (what ROM ?) cat /dev/mtd/mtd2 ?
Is the phone start with this boot.img (unchanged) if you flash it by typing "fastboot flash..." ?
After that, just try to unpack and repack the boot.img without changes on ramdisk or kernel, if it works that means your changes suck (^^).
These commands (or perl scripts) work perfectly for me.

Lol I will try doing that. The boot.img I used is from stock 2.3.4, edited the ramdisk (specifically init.rc & init.herring.rc)
Like I said, first time I used the perl scripts I edited my ramdisk, threw in a netarchy kernel, it compiled fine and booted. Now if I use the perl script to repack with an aosp kernel, it gives me an error about file name and/or extension being wrong. Or complains it can't find mkbootimg when its there and executable. I'll re run it again and post errors
Sent from my Nexus S

he guys where is the boot image located? not the animation, the google logo at the start of the booting!
Sent from my Nexus S using XDA Premium App

ok so when I used the repack-bootimg.pl script, it kept giving me this error:
Code:
boot.img-kernel.gz Not a directory at ./repack-bootimg.pl line 13.
So I ran mkbootimg manually, without a cmdline comment as stated above. It compiled
and booted beautifully all stock with no init.rc or init.herring.rc edits.
however when I compile a boot.img coupled with a stock kernel and a modified ramdisk, I get a non-booting boot.img. One came out at 2.9 mb and the other at 5.6 mb neither boots using the same cmd that compiled the working boot. Must be my edits.. I literally only changed about 1 line in init.rc and another line in init.herring.rc that causing it not to boot.
By the way, I got some info on a stock boot.img using the unpackbootimg binary (not the perl script) and here's what it outputs:
Code:
#BOARD_KERNEL_CMDLINE console=ttyFIQ0 no_console_suspend
BOARD_KERNEL_BASE 30000000
BOARD_PAGE_SIZE 00001000
I enter that pagesize and it says it's not a valid value when I compile boot.img's

Borky_16 said:
he guys where is the boot image located? not the animation, the google logo at the start of the booting!
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
part of the kernel
to change-https://github.com/morfic/Samsung-logo

ogdobber said:
part of the kernel
to change-https://github.com/morfic/Samsung-logo
Click to expand...
Click to collapse
yeah i know thanks for the link a helping source though!
Sent from my Nexus S using XDA Premium App

Sorry for the Control C Control V of it, but I just found this topic now..
I`m facing this problem when I try to unpack boot.img..
I have done it 2 days ago but dunno why, now I can`t..
Follows what is happening..
Code:
[email protected]:~/NS-bootwork$ ./unpack-bootimg.pl boot.img
Found a secondary file after the ramdisk image.
According to the spec (mkbootimg.h) this file can exist,
but this script is not designed to deal with this scenario.
The Kernel is built, as a zImage and the WLAN as a bmc3429.ko..
Just repeating, I have built this Kernel 2 days ago in the same way, without any problems, but now I`m struggling on the message after inputting ./unpack-bootimg.pl boot.img..
Dunno what else to try, I re-downloaded the unpack-bootimg.pl from 2 different sources, and still the same error..
Any ideas?
Many thanks..
P.S.: Ubuntu 11.04 x64..
EDIT
Well, I already solve it!
That is what I did..
As unpack-bootimg.pl was not working (don`t know why) I used split_bootimg.pl script, splitting the boot.img and created new ramdisk img..
Code:
./split_bootimg.pl boot.img
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i
find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Then after just compiled the Kernel with
Code:
./mkbootimg --kernel zImage --ramdisk newramdisk.cpio.gz --base 0x30000000 --pagesize 4096 --cmdline _console_suspend=1 console=bull's -o newtestboot.img'no
Witches includes " --cmdline _console_suspend=1 console=bull's" to not break BT functionality, in the case of Nexus S..

I found the tools here work well: http://glandium.org/blog/?p=2214
...if you then use the code originally posted above:
Code:
sudo find . | cpio -o -H newc | gzip > ../<your boot name>.img-ramdisk.cpio.gz
./mkbootimg --kernel <your boot name>.img-kernel.gz --ramdisk <your boot name>.img-ramdisk.cpio.gz --base 0x30000000 --pagesize 4096 -o boot.img

Boot Animation

After a little looking around, I found a great boot animation by another guy from the xda forums, and I modded it a bit for the G Tablet.
Here's a preview:
(All credit goes to ASimmons for making this AWESOME animation.)
{
"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"
}
To install it,
adb push bootanimation.zip /logodata
Click to expand...
Click to collapse
Use 7zip to extract the zip file.

I love this! Can I install it without adb? I haven't gotten it working properly on my XP x64 machine.

Mine boots up so quickly, I never get to see the entire automation. Thanks!
I used RootExplorer to copy this over, since I don't have the SDK stuff loaded.

Thanks for the animation but it does not seem to work with VEGAn Beta 4 ROM image I recently loaded. I see it is the same size but cant get it to show - it just shows the normal VEGAn Android animation. Is there something I am doing wrong. Here is output of my what is in my logodata directory:
# ls -l
-rw-rw-rw- root root 16610683 2010-12-29 09:33 bootanimation.zip
-rwxr--r-- adb compass 2359350 2010-09-28 02:43 boot2.bmp
drw-rw-rw- root root 2010-12-30 12:38 lost+found
-rwxr--r-- adb compass 620888 2009-07-14 04:52 Tulips.jpg
Is it a permissions thing - I even set it to executable with chmod and still no different animation.
Anagin thanks for the animation - is there something I am doing wrong?

powerx86 said:
Thanks for the animation but it does not seem to work with VEGAn Beta 4 ROM image I recently loaded. I see it is the same size but cant get it to show - it just shows the normal VEGAn Android animation. Is there something I am doing wrong. Here is output of my what is in my logodata directory:
# ls -l
-rw-rw-rw- root root 16610683 2010-12-29 09:33 bootanimation.zip
-rwxr--r-- adb compass 2359350 2010-09-28 02:43 boot2.bmp
drw-rw-rw- root root 2010-12-30 12:38 lost+found
-rwxr--r-- adb compass 620888 2009-07-14 04:52 Tulips.jpg
Is it a permissions thing - I even set it to executable with chmod and still no different animation.
Anagin thanks for the animation - is there something I am doing wrong?
Click to expand...
Click to collapse
I have heard of some people saying that they find the bootanimation under a media directory instead of the logodata, is it possible that for the Vegan ROM that this zip must be put somewhere else?
Take a look at this post, perhaps it will help?
http://forum.xda-developers.com/showthread.php?t=878143&highlight=bootanimation

It didn't work the first time I install because androzip extracted damage zip file. I had to unzip it from my computer then transfer it over to the tablet. Use root explorer to copy it over to system/media.

If you get time can you post a step By step for us total newbs. I assume I just unzip and transfer via a USB cable but that's about it. (wouldnt insoluble exactly where to abstract it and if any other steps are involved)

I logged back on to the shell and did not see any other bootanimation other an executable bootanimation in the following folder:
/system/bin/
So I looked in the /system/media folder and no bootanimation.zip just the following:
# pwd
/system/media
# ls -l
drwxr-xr-x root root 2010-12-29 21:26 audio
I copied the bootanimation.zip file to that directory after reading multiple posts about the file being located in /system/media.
Here is the link that directs you to do the same.
http://forum.xda-developers.com/show...=bootanimation
I finally got this to work and at least for the VEGAn 4, the bootanimation.zip must reside in the /system/media folder.
Basic instructions are as follows and done in Linux:
Requirement: a way to copy data to /system folder (like adb tool). Here are the steps I used.
a) Enter the Android Shell using: ./adb shell
b) At the # prompt enter: mount
c) You should see the following as a READ-Only
/dev/block/mtdblock3 /system yaffs2 ro,relatime 0 0
d) Now you need to make this Read/Write to do this use the following commands:
mount -o rw,remount -t ext2 /dev/block/mtdblock3 /system
e) validate the mount is now read/write by re-executing the mount command - enter the following:
mount
f) You should see the following if everything worked to make this folder read/write:
/dev/block/mtdblock3 /system yaffs2 rw,relatime 0 0
g) Now lets exit the shell type the following:
exit
h) Now push the bootanimation.zip to the android device using the following command:
./adb push bootanimation.zip /system/media
i) Now lets reboot the Android device - execute the following:
./adb reboot
This worked and I have tried a few others. Thanks to all the tips to help me figure this out!

>>>>>>>>>>>>>>>>>>>>>>>>: (

>>>>>>>>>>>>>>>>:V

i wanted to use a gif that is around 40 mb 35 seconds long is that something that is possible to do or will i have to shorten it
is it possible to even use a gif

Is there anyway to have sound go along with the bootanimation?
Some phone bootani's have sound -- but I've never been able to get it to work properly after changing the stock...

Thank you for this boot animation. I have been presented with so many choices for customization, that it is hard to choose. I love this little tablet.

[DEVS only] Unpacking RAZR i boot images

I've seen you haven't been able to unpack the boot images so I investigated a bit on this "weird format" Moto used. This is what I could figure out by looking at the image and the bootstub code Motorola released:
Code:
0x00000000 kernel CMDLINE, filled with zeroes where unused
0x00000400 bzImage size
0x00000404 initrd size
0x00000408 SPI UART suppression
0x0000040B SPI type (0: SPI0, 1: SPI1)
0x00001000 future stack for bootstub (?)
0x00002000 actual bzImage start
On the boot image I grabbed from the root post, using the awesome "hexdump" tool we can see at 0x400
Code:
60 a8 46 00 90 6c 1a 00
Which means (remember x86 is Little Endian) bzImage size 0x0046A860 (~4.5MB) and initrd size of 0x001A6C90 (~1.65MB)
So let's go to the practical side:
0x00002000 + 0x0046A860 = 4638816
Code:
$ dd if=razr_i_boot.img of=ramdisk.cpio skip=4638816 bs=1
$ zcat ramdisk.cpio|cpio -i
gzip: ramdisk.cpio: decompression OK, trailing garbage ignored
8927 blocks
$ ls
android.fstab dev init.moto.usb.rc init.sc1.rc init.wifi.rc ramdisk.cpio system ueventd.smi.rc
charger init init.moto.usb.sh init.sdcard1.rc init.xmm.rc res ueventd.goldfish.rc xbin
data init.goldfish.rc init.nfs.rc init.sdcard2.rc lib sbin ueventd.rc
default.prop init.moto.rc init.rc init.sdcard.rc proc sys ueventd.sc1.rc
Code:
$ dd if=razr_i_boot.img of=bzImage skip=8192 count=4630624 bs=1
$ file bzImage
bzImage: Linux kernel x86 boot executable bzImage, version 3.0.8-g229e199 ([email protected]) #1 SMP PREEMPT Sat Sep, RO-rootFS, root_dev 0x806, swap_dev 0x4, Normal VGA
Ta-da! Unpacked. It wasn't that hard really
Now, is there interest on a tool to repack/unpack these images? I don't own the phone (and probably won't, no $$ ) but if there's enough interest I can make one, it should be relatively easy.
EDIT: Okay, so I wrote a pair of tools to unpack existing images and package new images, you can get them at
https://github.com/turl/razr-i-boot-tools
Just run "make" to build the tools, the usage is really simple
Code:
$ ./pack
Usage: ./pack <valid image> <bzImage> <ramdisk> <output>
From left to right, an already existing boot image (to copy bootstub from, it could be built from source on the future), the kernel, the gzipped cpio ramdisk and the output filename
Code:
$ ./unpack
Usage: ./unpack <image to unpack> <bzImage out> <ramdisk out>
From left to right, the image you want to unpack, and the destination files for bzImage and ramdisk. You can then unpack the ramdisk with something like
Code:
$ mkdir ramdisk-unpack
$ cd ramdisk-unpack
$ zcat ../ramdisk.cpio.gz|cpio -i
And then repack it with something like
Code:
$ find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz

turl1 said:
Ta-da! Unpacked. It wasn't that hard really
Now, is there interest on a tool to repack/unpack these images? I don't own the phone (and probably won't, no $$ ) but if there's enough interest I can make one, it should be relatively easy.
Click to expand...
Click to collapse
Making it look so simple
I really appreciate you taking the time to look at this, especially since you don't even have the device. I definitely have interest in a tool if at all possible. I'd donate and encourage others to as well

I agree with everything he said. Awesome job

Okay, so I wrote a tool to package images, check the edit on the first post and let me know how it works. I'll make another one to unpack current images when I get some more time

turl1 said:
Okay, so I wrote a tool to package images, check the edit on the first post and let me know how it works. I'll make another one to unpack current images when I get some more time
Click to expand...
Click to collapse
Been working all day yesterday to get up and running on Linux again, time to redouble my efforts and try a new distro so I can get packin'!
EDIT:Got everything set up besides ramdisk I believe. First attempt is progress, instead of error booting into fastboot it sticks on the boot logo, then reboots and loops that. I'm pretty sure its because I did ramdisk wrong but we'll see if anyone else can get it further.
File includes ramdisk folder, boot.img, and my compiled bzImage. http://d-h.st/Cyn

mattlgroff said:
Been working all day yesterday to get up and running on Linux again, time to redouble my efforts and try a new distro so I can get packin'!
EDIT:Got everything set up besides ramdisk I believe. First attempt is progress, instead of error booting into fastboot it sticks on the boot logo, then reboots and loops that. I'm pretty sure its because I did ramdisk wrong but we'll see if anyone else can get it further.
File includes ramdisk folder, boot.img, and my compiled bzImage. http://d-h.st/Cyn
Click to expand...
Click to collapse
What did you use to repackage the ramdisk? Something like this should work
Code:
$ cd ramdisk
$ find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Then use the generated 'newramdisk.cpio.gz' when calling pack; something like
Code:
$ ./pack boot.img bzImage newramdisk.cpio.gz newboot.img

turl1 said:
What did you use to repackage the ramdisk? Something like this should work
Code:
$ cd ramdisk
$ find . | cpio -o -H newc | gzip > ../newramdisk.cpio.gz
Then use the generated 'newramdisk.cpio.gz' when calling pack; something like
Code:
$ ./pack boot.img bzImage newramdisk.cpio.gz newboot.img
Click to expand...
Click to collapse
Getting a 4.6 MB boot.img with this, trying to boot now.

mattlgroff said:
Getting a 4.6 MB boot.img with this, trying to boot now.
Click to expand...
Click to collapse
Yes, a smaller boot.img is to be expected, the dumped one you guys got has garbage on its tail

turl1 said:
Yes, a smaller boot.img is to be expected, the dumped one you guys got has garbage on its tail
Click to expand...
Click to collapse
Same bootloop issue, looping the bootlogo and phone reboots

Well, it turns out I fail when programming on the late AM
https://github.com/turl/razr-i-boot-tools/commit/34f618b5cb2d6fb4b4c7d8affb194113a0b11270
Update/reclone your tools repo, rebuild it and try again. Rebuild your ramdisk image too, just in case the tool corrupted it.

turl1 said:
Well, it turns out I fail when programming on the late AM
https://github.com/turl/razr-i-boot-tools/commit/34f618b5cb2d6fb4b4c7d8affb194113a0b11270
Update/reclone your tools repo, rebuild it and try again. Rebuild your ramdisk image too, just in case the tool corrupted it.
Click to expand...
Click to collapse
Updated tools, rebuilt tools, rebuilt ramdisk....
6.5 MB newboot.img now.
Boot animation....
Booted!
{
"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"
}
Where's your donation link?

mattlgroff said:
Updated tools, rebuilt tools, rebuilt ramdisk....
6.5 MB newboot.img now.
Boot animation....
Booted!
[image]
Where's your donation link?
Click to expand...
Click to collapse
Awesome! I just wrote the unpack tool by the way, same repo. Check the first post for more info and let me know if you have any issues with it.
I also completed the "donate to me" box on the XDA profile for those looking for it

turl1 said:
Awesome! I just wrote the unpack tool by the way, same repo. Check the first post for more info and let me know if you have any issues with it.
I also completed the "donate to me" box on the XDA profile for those looking for it
Click to expand...
Click to collapse
OMG, I sure won't make use of it but I know how important it is to build Custom Recovery and Custom Roms sooo I'll make a donate soon as I can.

Make boot.img
Hi,
I can't manage to make the boot.img with my compiled kernel for Razr I. Anyone can make the boot.img for me please :victory:
Thank you

"Direct booting from floppy is no longer supported...Please use a boot loader program instead...Remove disk and press any key to reboot..."
WTF?!
open your bzImage with a hex editor, the first lines

Hai mattlgroff, I have switch from your homemade 40002 to 31006 with RST & then OTA auto update to 40002 & then do root & CWM but now the kernel version is older (Sept 2012), so can i copy the recovery.signed in 31006 & change the file name to recovery.img & put into the CWM folder & ADB/Fastboot.
Can i have this better matt-desktop #1 too.Thks.

Daniel 9999 said:
Hai mattlgroff, I have switch from your homemade 40002 to 31006 with RST & then OTA auto update to 40002 & then do root & CWM but now the kernel version is older (Sept 2012), so can i copy the recovery.signed in 31006 & change the file name to recovery.img & put into the CWM folder & ADB/Fastboot.
Can i have this better matt-desktop #1 too.Thks.
Click to expand...
Click to collapse
Its not better, worse actually because things are broken.
Sent from my MB886 using Tapatalk 2

mattlgroff said:
Its not better, worse actually because things are broken.
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
However,thanks Mattlgroff, For you & all info.,I take your 40002 boot.img & Fastboot flash boot boot.img after RSDlite 31006 & got back the newest Nov,2 kernel. It really run very smooth & fast ( I overwrite your ADB file to a newer ADB from android-sdk folder as dont know why ADB devices cant read/see).Cheers.

mat have you got this to complied because iv only got cgywin or could you build my boot.img to unlink data/media

http://batakang.com/ftp/incoming/boot.img
Having some troubles with this Jellybean boot.img. Anyone want to take a stab at it?

Supersu 2.67 no root

Hey guys I have a problem with the latest Supersu. I can't get root with my Samsung Galaxy S6 edge plus. So I tried an older version. That worked very well. Could you take a look at the log, please? I don't know what's the problem with that.
Code:
*****************Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 11/2048 files, 1166/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mknod: /dev/block/loop0: File exists
ioctl LOOP_SET_FD failed: Device or resource busy
- Mounting /system, /data and rootfsrm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
- Extracting filesrm: can't remove '/su/bin/sukernel': No such file or directory
rm: can't remove '/data/SuperSU.apk': No such file or directory
rm: can't remove '/su/su.d/000000deepsleep': No such file or directory
- System-less mode, boot image support requiredsukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/sda5] ...
magic: [ANDROID!]
kernel: [18869536] (18870272) @ 0x10008000
ramdisk: [5367784] (5367808) @ 0x11000000
second: [0] (0) @ 0x10f00000
tags: @ 0x10000100
page size: 2048
unused: [0x0013b000] [0x00000000]
dtb(?): [1290240] (1290240)
name: []
command line: []
extra command line: []
id: [0xcb1a9d371fd0d7b82fa23c023a0cbffc281ecd60000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/sutmp/ramdisk.packed] ...
Decompressing [5367784] --> ungzip: inflate: -3
failed
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sda5
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
If TWRP offers to install
SuperSU, do *NOT* let it!
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
- Unmounting /system
- Done !
Install from sdcard complete.

Luna447 said:
Hey guys I have a problem with the latest Supersu. I can't get root with my Samsung Galaxy S6 edge plus. So I tried an older version. That worked very well. Could you take a look at the log, please? I don't know what's the problem with that.
Code:
*****************Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 11/2048 files, 1166/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mknod: /dev/block/loop0: File exists
ioctl LOOP_SET_FD failed: Device or resource busy
- Mounting /system, /data and rootfsrm: can't remove '/su/bin/su': No such file or directory
rm: can't remove '/su/bin/daemonsu': No such file or directory
rm: can't remove '/su/bin/supolicy_wrapped': No such file or directory
rm: can't remove '/su/lib/libsupol.so': No such file or directory
- Extracting filesrm: can't remove '/su/bin/sukernel': No such file or directory
rm: can't remove '/data/SuperSU.apk': No such file or directory
rm: can't remove '/su/su.d/000000deepsleep': No such file or directory
- System-less mode, boot image support requiredsukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/dev/block/sda5] ...
magic: [ANDROID!]
kernel: [18869536] (18870272) @ 0x10008000
ramdisk: [5367784] (5367808) @ 0x11000000
second: [0] (0) @ 0x10f00000
tags: @ 0x10000100
page size: 2048
unused: [0x0013b000] [0x00000000]
dtb(?): [1290240] (1290240)
name: []
command line: []
extra command line: []
id: [0xcb1a9d371fd0d7b82fa23c023a0cbffc281ecd60000000000000000000000000]
Saving to [/sutmp/ramdisk.packed] ...
sukernel v2.67 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Loading from [/sutmp/ramdisk.packed] ...
Decompressing [5367784] --> ungzip: inflate: -3
failed
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
- Finding boot image
--- Boot image: /dev/block/sda5
- Extracting ramdisk
- Decompressing ramdisk
--- Failure, aborting
*************************
IMPORTANT NOTICES
*************************
If TWRP offers to install
SuperSU, do *NOT* let it!
*************************
First reboot may take a
few minutes. It can also
loop a few times. Do not
interrupt the process!
*************************
- Unmounting /system
- Done !
Install from sdcard complete.
Click to expand...
Click to collapse
Is this a custom kernel?
Please post your boot.img

It's the latest arter Kernel for the s6e+. I think it's the v9.4.
E: http://arter97.com/browse/exynos7420/kernel/9.4/g928fcig this one.
So do you think the kernel is the problem here?

Luna447 said:
It's the latest arter Kernel for the s6e+. I think it's the v9.4.
E: http://arter97.com/browse/exynos7420/kernel/9.4/g928fcig this one.
So do you think the kernel is the problem here?
Click to expand...
Click to collapse
It's probably not compressed with gzip. SuperSU currently only supports gzip compression to modify kernels.

Chainfire said:
It's probably not compressed with gzip. SuperSU currently only supports gzip compression to modify kernels.
Click to expand...
Click to collapse
Oh I see! So what can I do to make it work? Simply extract and recompress is with a tool?

Luna447 said:
Oh I see! So what can I do to make it work? Simply extract and recompress is with a tool?
Click to expand...
Click to collapse
Nothing really. After looking at that kernel, it seems he completely disabled SELinux. That's a case the installer doesn't cover (it should), so it can just use a /system based root instead of systemless.
That and adding support for LZ4 should both fix the problem, but they are both things I need to do.
What you can try is, in recovery, execute this shell command:
Code:
echo SYSTEMLESS=true>>/data/.supersu
That might do the trick.

Chainfire said:
Nothing really. After looking at that kernel, it seems he completely disabled SELinux. That's a case the installer doesn't cover (it should), so it can just use a /system based root instead of systemless.
That and adding support for LZ4 should both fix the problem, but they are both things I need to do.
What you can try is, in recovery, execute this shell command:
Code:
echo SYSTEMLESS=true>>/data/.supersu
That might do the trick.
Click to expand...
Click to collapse
First of all, thanks for answering. But I'm not sure if I'm doing this right.
So I boot my phone into recovery.
Then I open up the cmd on my pc and navigate to the adb folder.
Now I type in "adb shell" and execute the code you provided above?
(c:\adb-tools>adb shell
~ # echo SYSTEMLESS=true>>/data/.supersu)

Yes, and then you flash SuperSU again.

Chainfire said:
Yes, and then you flash SuperSU again.
Click to expand...
Click to collapse
Hm unfortunately it didn't work. Can you recommend any good Kernel for the s6e+?
I really would like to use your latest Supersu due to the deep sleep issue I'm facing with my phone.

I feel the same, with CM 13 a Galaxy S2 i9100. If I install the superuser without installing the rom no problem, but when the ROM is installed, gives the same error

loparaan said:
I feel the same, with CM 13 a Galaxy S2 i9100. If I install the superuser without installing the rom no problem, but when the ROM is installed, gives the same error
Click to expand...
Click to collapse
Mate, I had the same problems on i9100 after installing a Lanchon kernel.
But I'd flashed a DorimanX one (https://drive.google.com/folderview?id=0B3ApZsjOd2bzWjBBMHc2SWNUSlE&usp=sharing), formatted sdcard0, and then tried to install SuperSU (before a firmware). And it worked! Then installed CM13 and got success!

blackb00m said:
Mate, I had the same problems on i9100 after installing a Lanchon kernel.
But I'd flashed a DorimanX one (https://drive.google.com/folderview?id=0B3ApZsjOd2bzWjBBMHc2SWNUSlE&usp=sharing), formatted sdcard0, and then tried to install SuperSU (before a firmware). And it worked! Then installed CM13 and got success!
Click to expand...
Click to collapse
Before installing the 13 cm, I have no problems with the installation of SuperSU, also it worked out. But when installing the CM13 the first time, the SuperSU is lost.
I'll try with that kernel to see if you let me install it. Thank you

Sumsung Galaxy s4 shv_e330k root

Got a similar problem with my LG G3 running Marshmallow (rooted with method and tools supplied here).
Oddly enough, the SuperSU 2.52 beta from the above link works flawlessly, but the 2.67 beta (and 2.65 stable) both get the "decompressing ramdisk, failure aborting" issue.
Attached recovery log in case its needed to troubleshoot!

You can just use the zips from this thread: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 This will force it in system mode so it will not even attempt to do it in system-less

Xmaster24 said:
You can just use the zips from this thread: http://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120 This will force it in system mode so it will not even attempt to do it in system-less
Click to expand...
Click to collapse
Worked like a charm! Thanks!

Palaryel said:
Worked like a charm! Thanks!
Click to expand...
Click to collapse
No problem this should fix the update problems for everyone on this forum

I have a similar problem! :/ - SAMSUNG GT-i9100GSMH + lineageos 14.1 + TWRP-3.0.2-1-i9100 - SuperSU-v2.79 NO ROOT :/
Odin install Siyah-s2-v6.0b5 Kernel +Recovery by Gatox Tutorialex.tar
AND AFTER recovery install TWRP: recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip
+
lineage-14.1-20170510-nightly-i9100-signed.zip (android 7)
No apps Root lineage :
{
"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"
}
SuperSU-v2.79-201612051815.zip
+
SuperSU GooglePlay
Install SUPERSU and NoRoot:
Do you think the solution is???

the same problem

also the same problem no root D:

[GUIDE] Extracting the latest OnePlus 6T firmwares from ROM update package

* Pre-note: Extracting firmwares and subsequently updating your phone's firmware by flashing the extracted firmwares, is a 2-part process. This guide is only about extracting them, and i also made another guide that is for flashing them afterwards: see [GUIDE] Flashing the latest firmware updates to your OnePlus 6T. The guides supplement eachother, depending on your needs.
General word about firmware updates:
A lot of people know of the importance and benefits of keeping your device firmware updated, just like you keep your custom ROM updated. If you don't keep them updated, you might not get the best out of your custom ROM (like: more bugs, system stability and performance problems/less speed.. also, vendor components, e.g Qualcomm and other chips, have security patches in the firmware.. "Vendor patch level" vs Android "Security patch level").
Besides incremental firmware updates from each OxygenOS release with a small changelog, too many people are missing out on huge jumps such as that they are running an Android 11 custom ROM, while their firmware was never updated so it remained a firmware originally shipped with an Android 10 (or earlier) OxygenOS release. Staying behind on huge jumps like these, cause the biggest list of problems with stability and performance. Therefore it is advisable to keep your firmware updated, and note that even small incremental updates (based on the same Android version) tend to give performance, security and stability benefits.
Let's continue.
If you can't find someone that posted the firmwares separately (or you don't trust their completeness, integrity & authencity.. it's always a potential risk) this guide will help you do it all by yourself, to extract firmwares from the original ROM update package.
GUIDE STARTS BELOW THIS LINE
Prerequisites
First step: Get the updated OxygenOS ROM, it's a zip file named in a format like this: OnePlus6TOxygen_34.J.62_OTA_0620_all_2111252336_339a2fa8335f21.zip (this happens to be the latest version as of writing, it will be outdated from now on)
Make sure to get it from an official source, i dont know where OnePlus shares direct links but i know that their practises regarding it are inconsistent (sometimes they provide, other times they don't). So i advise you to use an useful app in the Play store called Oxygen Updater that fetches it directly from OnePlus servers.
For this app.. if you're on LineageOS, you can click through to download the ROM update file but only after ignoring all warning dialogs saying things like "Unsupported device" and about root + enabling Advanced mode slider in the app's settings. So basically, these steps override 1) that you're on LineageOS (so it thinks it's unsupported) and 2) that it doesn't recognize your current version and thus doesn't offer a direct download of the file, regardless of what it fails to detect about your phone or OS, to your phone storage.. that's what Advanced mode takes care of. So after enabling Advanced mode, download the ROM .zip from the update screen in the app, and it will be placed in your phone's storage root folder
So now that you have the ROM, let's start the firmware extracting process -
Required tool: payload-dumper-go > choose latest version and download the Windows package
1) Extract payload-dumper-go to your folder "FW update"
2) Move the ROM .zip file (downloaded from Oxygen Updater app) from your phone storage to your PC, and place it in that "FW update" folder
3) Open the ROM .zip file with an archiving program, like 7-Zip
4) Extract payload.bin from within the ROM .zip file using 7-Zip, this .bin file should display in 7-Zip as shown below:
{
"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"
}
So after extracting this from the ROM .zip, you open up cmd (command prompt of Windows) and write cd [folder "FW update" location) or even better, copy cmd.exe from System32 to your "FW update" folder. I always use that method for all my maintenance, e.g it's copied to my "adb" folder as well for easy folder targeting
4) Now in cmd, use payload-dumper-go to pull firmwares from payload.bin:
Code:
Enter each command separately, after the other completes
payload-dumper-go -p abl payload.bin
payload-dumper-go -p aop payload.bin
payload-dumper-go -p bluetooth payload.bin
payload-dumper-go -p cmnlib payload.bin
payload-dumper-go -p cmnlib64 payload.bin
payload-dumper-go -p devcfg payload.bin
payload-dumper-go -p dsp payload.bin
payload-dumper-go -p fw_4j1ed payload.bin
payload-dumper-go -p fw_4u1ea payload.bin
payload-dumper-go -p hyp payload.bin
payload-dumper-go -p keymaster payload.bin
payload-dumper-go -p LOGO payload.bin
payload-dumper-go -p modem payload.bin
payload-dumper-go -p oem_stanvbk payload.bin
payload-dumper-go -p qupfw payload.bin
payload-dumper-go -p storsec payload.bin
payload-dumper-go -p tz payload.bin
payload-dumper-go -p vendor payload.bin
payload-dumper-go -p xbl_config payload.bin
payload-dumper-go -p xbl payload.bin
Now they are pulled, but will be automatically put in folder names (as subfolders to your "FW update" folder) that look like this: "extracted_20211216_135146" with unique number each. These folders contain just 1 pulled firmware (.img files) individually
Now you have to move all .img files from each of such folders, to your main directory ("FW update"). I prefer to do it like this: Windows Explorer search for *.img like below image
Select all matching results from this search and copy them to "FW update" or put them in a new subfolder "Pulled firmwares"
Now the firmware extracting process is complete. From this point, the flashing process should be picked up. I made another guide for the flashing process, if you're interested beyond the scope of this one (the act of extracting firmwares alone): [GUIDE] Flashing the latest firmware updates to your OnePlus 6T
Note on this guide: it's possible that these instructions are universal to many, if not all, other modern OnePlus devices.. or even other smartphone brands. But since i am only the owner of an OnePlus 6T, i cannot verify or test it, and therefore this guide targets the 6T. But of course, if you got some know-how you can attempt to use this guide for other models.. although you will surely have to dump the content table listing of the update's payload.bin (with this command: payload-dumper-go -list payload.bin ), to figure out which .img files to extract.. as the relevant firmware packages & components will differ per model