Hi,
I downloaded the SM-N910F kernel from samsung compiled and burned it with Heimdall. It works fine.
The problem I am facing is when I add some code into the kernel. It won't boot (returns do DOWNLOAD mode screen), error message "could not do normal boot".
Note: I have tried burning my boot.img both with Heimdall (linux) and Odin (windows), and get the same results, i.e. unmodfied kernel works fine, modified -- fails.
It seems to be a zImage size issue.
I tested this by only adding lots of seq_print(m ,"something somthing ....") in print_binder_transaction() (drivers/stagin/android/binder.c). just to make the zImage bigger (unmodified zImage size: 9792000 bytes, bloated zImage 9799072 bytes, only ~7Kb more).
I checked the with busybox fdisk the BOOT partition size, its 17MB.
I pulled the boot.img with dd from the device and used "abootimg -u boot.img -k ../arch/arm/boot/zImage" to update it with my compiled zImage.
any ideas?
missing info?
Thanks,
Daniel.
lightydo said:
Hi,
I downloaded the SM-N910F kernel from samsung compiled and burned it with Heimdall. It works fine.
The problem I am facing is when I add some code into the kernel. It won't boot (returns do DOWNLOAD mode screen), error message "could not do normal boot".
Note: I have tried burning my boot.img both with Heimdall (linux) and Odin (windows), and get the same results, i.e. unmodfied kernel works fine, modified -- fails.
It seems to be a zImage size issue.
I tested this by only adding lots of seq_print(m ,"something somthing ....") in print_binder_transaction() (drivers/stagin/android/binder.c). just to make the zImage bigger (unmodified zImage size: 9792000 bytes, bloated zImage 9799072 bytes, only ~7Kb more).
I checked the with busybox fdisk the BOOT partition size, its 17MB.
I pulled the boot.img with dd from the device and used "abootimg -u boot.img -k ../arch/arm/boot/zImage" to update it with my compiled zImage.
any ideas?
missing info?
Thanks,
Daniel.
Click to expand...
Click to collapse
ok, solved the problem. used unpackbootimg & mkbootimg to create the new boot.img. works fine...
Related
Sorry for the totally newbie question (for both android and linux).
I've rom images from legend ruu: android-info.txt, boot.img, hboot_legend_7227_1.01.0000_101108.nb0, radio.img, rcdata.img, recovery.img, splash1.nb0, system.img, userdata.img.
Is there any way to mount them (especially boot.img, recovery.img and system.img) on a linux box using a loop device?
The files boot.img and recovery.img are starting with magic word "ANDROID!°¨#", while I cannot recognize any string in system.img. What kind of file systems are these?
Thank you in advance,
TiceRex
system.img should just be a yaffs image and can be mounted loopback if you have the yaffs drivers installed. boot.img and recovery.img are ramdisk images which consist of a kernel and a cpio archive (containing the files for the root filesystem) bundled together in a package. HBOOT loads the kernel first, then unzips the cpio archive into a newly created ramdisk. Once all is loaded, execution is passed off to the kernel which has a nice ramdisk full of the init files needed for the remainder of the boot process. system and data images are then mounted to mountpoints in the ramdisk.
To extract and manipulate boot.img and recovery.img, see this thread:
http://forum.xda-developers.com/showthread.php?t=551711
Thank you very much.
Seeing into dsixda's rom kitchen scripts I was able to extract the boot.img and recovery.img files (and found the kernel and initrd).
I will look for the yaffs drivers.
Regards, TiceRex
Hello everyone,
I have an I5800 and tried to make a simply custom rom deleting some apps and adding others. I did:
- mount with loop device the factorsfs.rfs from PDA.tar
- delete / add some apps
- unmount
- repackaged factoryfs.rfs cache.rfs datafs.rfs zImage to PDA.tar
- md5 singned the tar package
- with ODIN flashed (PHONE, CSC and the new PDA)
Now the phone boots nomore and got stuck at GT-5800 logo.
What should I do? Can anyone help?
best regards
[Resolved ] I5800XXJPF - Custom ROM not booting
Hello eveyone,
It worked before I did a "Factory data reset" with the command
*#*#7780#*#*
best regards,
nsdroid said:
Hello everyone,
I have an I5800 and tried to make a simply custom rom deleting some apps and adding others. I did:
- mount with loop device the factorsfs.rfs from PDA.tar
- delete / add some apps
- unmount
- repackaged factoryfs.rfs cache.rfs datafs.rfs zImage to PDA.tar
- md5 singned the tar package
- with ODIN flashed (PHONE, CSC and the new PDA)
Now the phone boots nomore and got stuck at GT-5800 logo.
What should I do? Can anyone help?
best regards
Click to expand...
Click to collapse
Two questions.
How do you repackage the factoryfs.rfs?
How do you md5 sign the tar package?
The Dark Lestat said:
Two questions.
How do you repackage the factoryfs.rfs?
How do you md5 sign the tar package?
Click to expand...
Click to collapse
1. Pack to tar "PDA.tar" all the file from factoryfs.rfs (system):
tar -H ustar -c cache.rfs datafs.rfs factoryfs.rfs zImage > PDA.tar
where the factoryfs.rfs is the modified one and other three are the same as in the original JPF's PDA file.
2. Sign the tar (the same name):
md5sum -t PDA.tar >> PDA.tar
3. Rename the tar as a file with extention tar.md5
mv PDA.tar PDA.tar.md5
best regards
When you mounted the rfs, it was mounted as vfat, yes? I doubt that if you modify it as vfat, it will still be a valid rfs. After all, it never was a real vfat file system, as a fsck.vfat will point out (it will throw a lot of errors if you run it on any rfs image). So the result of your modifications will probably be some file system which is neither a valid vfat nor a valid rfs.
Hi,
Thank you. You're right. It's more simple:root the phone, modify all you want, with
dd make an rfs image of the /dev/block/stl6 (system) and pack into pda.tar...
This way the files are not corrupted anymore.
best regards
Hi,
I've compiled a modified version of the 2.6.36.3 kernel (downloaded from the git repository) to include a USB Network Adapter driver (AX88772A) into a zImage. But I don't know how to flash the zImage onto my A500. When I run "fastboot flash zimage zImage" it always returns < waiting for device >. But I am able to run adb to pull and push files to the tablet.
How can I update the kernel so that it can detect my USB -> Ethernet adapter (chipset AX88772A)? Any ideas? Thanks!
You have to put it in the boot.img, then you can dd it or create a zip update, like custom roms!
You can ask for more info to a kernel guy like richardtrip or thor202ro!
Try to open one of their zip update to see how it works!
you should use android's mkbootimg
like
mkbootimg --ramdisk initrd.gz --kernel zImage -o boot.img
then you can dd it to boot partition (/dev/mmcblk0p2) and run itsmagic. And do not flash both p1 and p2 at the same time - if you flash two unbootable images or forget to update the checksum, you'll have to pm sc2k to recover the device via nvflash.
Moving to General.
PS: Every Q? thread should be posted in General.
So, I'm unable to unpack the boot.img successfully. Tried alot of tools, either it would give me an error or it would unpack but the zImage would be empty and the ramdisk would be corrupted. It would report a page size of over 530000 and the address would be wrong. My phone is a G531F.
Any help?
I have this problem after the murtirom 33b and twrp 2.0.2.0 i have tried different version of every channel.I can't post a screenshot for details.
it says
Current boot sector was used as base for fake boot.img!
system-image-upgrader failed
Restoring mounts...
Processing boot.img for Ubuntu Touch
Extracting boot image...
Found dtb
Decompressing ram disk...
Ramdisk uses GZIP compression
Compressing partition details...
...done
MTP already enabled
MTP Enabled
davidescion said:
I have this problem after the murtirom 33b and twrp 2.0.2.0 i have tried different version of every channel.I can't post a screenshot for details.
it says
Current boot sector was used as base for fake boot.img!
system-image-upgrader failed
Restoring mounts...
Processing boot.img for Ubuntu Touch
Extracting boot image...
Found dtb
Decompressing ram disk...
Ramdisk uses GZIP compression
Compressing partition details...
...done
MTP already enabled
MTP Enabled
Click to expand...
Click to collapse
There is a problem with the latest recovery. Flash this recovery 'TWRP_multirom_bacon_20160221-01.img' and it'll get installed without any errors
sandesh780 said:
There is a problem with the latest recovery. Flash this recovery 'TWRP_multirom_bacon_20160221-01.img' and it'll get installed without any errors
Click to expand...
Click to collapse
ok now it works perfectly fine