[Q] unpack orginal boot.img into kernel and ramdisk - Xperia Tablet Z General

Hello,
i have extended my orginal Kernel with following code lines to use a USB webcam (modified cam for astrophotography) with my Xperia Tablet Z SGP311 Android 4.4.2 stock rom.
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2_COMMON=y
CONFIG_VIDEO_MEDIA=y
CONFIG_USB_VIDEO_CLASS=y
CONFIG_V4L_USB_DRIVERS=y
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
#UVC driver support..
Click to expand...
Click to collapse
..for the zImage i have used the Tutorial and Toolchains from DooMLoRD :good:
..code lines into my fusion3_pollux_windy_defconfig
ARCH=arm CROSS_COMPILE=/home/xxxxxxxxxxxx/toolchains/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make fusion3_pollux_windy_defconfig
Click to expand...
Click to collapse
..made my .config and compile
ARCH=arm CROSS_COMPILE=/home/xxxxxxxxxxxx/toolchains/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8
Click to expand...
Click to collapse
now have tried to unpack my orginal boot.img wich i have ripped like this Tutorial from Youtube User IT ADV with "abootimg" into kernel and ramdisk
[email protected]:~$ cd boot_sony
[email protected]:~/boot_sony$ ls
boot.img
[email protected]:~/boot_sony$ abootimg -x boot.img
boot.img: no Android Magic Value
boot.img: not a valid Android Boot Image.
[email protected]:~/boot_sony$
Click to expand...
Click to collapse
But everytime i get these errors
no Android Magic Value and not a valid Android Boot :crying:
And another trial
[email protected]:~$ cd boot_sony
[email protected]:~/boot_sony$ perl split_bootimg.pl boot.img
Android Magic not found in boot.img. Giving up.
[email protected]:~/boot_sony$
Click to expand...
Click to collapse
Hmm, why i cant unpack boot.img?
I have tried a different boot.img from my Galaxy S2 Slimrom with the same error.

Related

[Q] initrd.gz repack

Does the initrd.gz need have permissions reset after unpacking and repacking???? I keep getting bootloops and im not sure what commands to run to set permissions. I use ubuntu any help would be greatly appreciated thanks!!!!!!!
I have the same problem, anyone can help?
You can try use Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
blacksn said:
I have the same problem, anyone can help?
Click to expand...
Click to collapse
What commands are you using
The following command will do it for you
Code:
find .|cpio --quiet -H newc -o|gzip -9 -c - > ../initrd.gz
here is original initrd.gz from ROM and image that i want to put inside:
black.volyn.net/or.zip
here is the file i'm getting after command:
black.volyn.net/initrd.gz
(add http to links, i can't post links yet)
Image is changed, but the phone reboots when bootanimation must to start.
Can someone to pack me initrd.gz with image from archieve?
Try the link below
http://dl.dropbox.com/u/26430630/initrd.gz
Hopefully that will work for you
Thanks, works fine!
Which version of Linux did you use to make inird.gz?
blacksn said:
Thanks, works fine!
Which version of Linux did you use to make inird.gz?
Click to expand...
Click to collapse
I use sabayon, debian or ubuntu
The same command should work all linux machines

[DEVELOPERS TOOLS] Unpack, repack boot.img, and editing boot logo

Samsung Galaxy Ace: Unpack and repack boot.img, editing boot logo
Ketut P. Kumajaya ketut.kumajaya @ xda-developers.com
Unpacking boot.img:
Code:
$ mkdir -p unpack
$ tools/unpackbootimg -i boot.img -o unpack
Extracting boot.img-ramdisk.gz
Code:
$ mkdir -p unpack/boot.img-ramdisk
$ cd unpack/boot.img-ramdisk
$ gzip -dc ../boot.img-ramdisk.gz | cpio -i
$ cd ../../
Packing a new ramdisk:
Code:
$ tools/mkbootfs unpack/boot.img-ramdisk | gzip > unpack/boot.img-ramdisk.gz
Create a new boot.img:
Code:
$ tools/mkbootimg --kernel unpack/boot.img-zImage --ramdisk unpack/boot.img-ramdisk.gz -o boot.img-repack --base `cat unpack/boot.img-base`
Convert rle to png:
Code:
$ tools/from565 -rle < COOPER.rle > COOPER.raw
$ convert -size 320x480 -depth 8 rgb:COOPER.raw COOPER.png
Convert png to rle:
Code:
$ convert -depth 8 COOPER-new.png rgb:COOPER-new.raw
$ tools/to565 -rle < COOPER-new.raw > COOPER-new.rle
NOTE:
For developers only, don't ask me for support! Solve your problems by yourself!
PASSWORD:
As usual: ketut.kumajaya
Too usefull
Thanks.
You should get "Recognized Developer" title, ketut.kumajaya!
If I have a Motorola Android device, maybe I can go back to www.MotorolaFans.com as a Developer
ketut.kumajaya, is it possible to resize Data,System and Cache on Ace? Maybe something like this...?
For example, the size of the partition of Indian (S5830DDKQ5) firmware are different (+1Mb to system and cache) from those that have been in all previous firmwares (KPN, KPH...).
EDITED---
guess we have to take boot.img from CWM backup images?
Is this doable under Windows? I tried but unpackbootimg wasn't recognized as a command
Nice work mas bro....
Tari Kecak is Awesome... ^^
autotomy said:
EDITED---
guess we have to take boot.img from CWM backup images?
Is this doable under Windows? I tried but unpackbootimg wasn't recognized as a command
Click to expand...
Click to collapse
It's only for Linux and its variants and derivatives
autotomy said:
EDITED---
guess we have to take boot.img from CWM backup images?
Is this doable under Windows? I tried but unpackbootimg wasn't recognized as a command
Click to expand...
Click to collapse
EmoBoiix3 said:
It's only for Linux and its variants and derivatives
Click to expand...
Click to collapse
Under Windows you can use JDK + Cygwin Custom Package + dsixda kitchen. Head to dsixda kitchen thread for more info. It's built for HTC but usable for Galaxy Ace / Mini (unpack / repack boot.img)
iv tried to us JDK + Cygwin but once I build the boot.img and flash it my boot animations stop working dose anyone no why ?
Nice post
Sent from my GT-S5830 using xda premium
i really need help
i need someone how can extract boot.img add my cooper.rle to it and change the default.prop to this
ro.secure=0
thanks
rickwyatt said:
i really need help
i need someone how can extract boot.img add my cooper.rle to it and change the default.prop to this
ro.secure=0
thanks
Click to expand...
Click to collapse
Use Ubuntu , it'll be easier
Sent from my GT-S5830 using XDA App
First post and attachment updated! Read README.txt and unpack/repack scripts for more details.
ketut.kumajaya said:
First post and attachment updated! Read README.txt and unpack/repack scripts for more details.
Click to expand...
Click to collapse
Thanks Ketut,That might be useful For Me
ketut.kumajaya said:
First post and attachment updated! Read README.txt and unpack/repack scripts for more details.
Click to expand...
Click to collapse
Wow I can't thank you enough ketut !
Herpderp Adreno + Tegra.
nice..........
Incredible, thank you!
hi, guy. I want to short video.
autotomy said:
EDITED---
guess we have to take boot.img from CWM backup images?
Click to expand...
Click to collapse
Good point to ask, can I do this with normal boot.img or I really need boot.img from nandroid backup??

[UTIL] unmkbootimg

I've put together a tool undoing what mkbootimg does. There are other tools splitting a boot image into the
kernel and root file system, but I didn't find any extracting the command line and base addresses, so I wrote this one.
It handles plain boot images as well as boot images embedded in larger filer, e.g. update-images.
Code:
$ unmkbootimg boot.img
Kernel size 2419636
Kernel address 0x20008000
Ramdisk size 152656
Ramdisk address 0x21000000
Secondary size 0
Secondary address 0x20f00000
Kernel tags address 0x20000100
Flash page size 2048
Board name is ""
Command line "no_console_suspend=1"
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x20000000 --cmdline 'no_console_suspend=1' -o new_boot.img
---------------
$ ls -l
totalt 5044
-rw-r--r-- 1 kuisma kuisma 2576384 9 sep 09.44 boot.img
-rw-r--r-- 1 kuisma kuisma 152656 9 sep 09.44 initramfs.cpio.gz
-rw-r--r-- 1 kuisma kuisma 2419636 9 sep 09.44 zImage
Version 1.2 - Support for embedded boot images
Version 1.1 - Support for non-standard mkbootimg images.
Version 1.0 - Initial release.
Including a gziped binary for GNU/Linux in this post (32 bit, linked static). Download, unzip, make sure it is executable.
If running on a 64bit machine, make sure you've got the ia32-libs installed to be able to run 32bit binaries.
Great Tool........ i Always use it..........Thanks For Share
I've updated unmkbootimg. Now it detects and warns if the boot.img is built using a non-standard mkbootimg, and tells you how to patch it.
$ unmkbootimg samsung-boot.img
Kernel size 4905092
Kernel address 0x40408000
Ramdisk size 893395
Ramdisk address 0x41800000
Secondary size 0
Secondary address 0x41300000
Kernel tags address 0x40400100
Flash page size 2048
Board name is ""
Command line "androidboot.hardware=qcom msm_watchdog.appsbark=0 msm_watchdog.enable=1 loglevel=4"
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_RAMDISK_ADDR is 0x01400000
Please modify mkbootimg.c using the above values to build your image.
****************
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x40400000 --cmdline 'androidboot.hardware=qcom msm_watchdog.appsbark=0 msm_watchdog.enable=1 loglevel=4' -o new_boot.img
---------------
Click to expand...
Click to collapse
Thank you for your tool my friend
Though I have one question regarding this:
--cmdline 'no_console_suspend=1'
Click to expand...
Click to collapse
When I attempt to compile kernel from source, Sony said in the read me file that memory layout and other stuff are passed to kernel via cmdline. I do that just like it's written in the cmdline I quoted?! because I want to use the latest kernel source with an existing zRam but i'm unable to make the newly compiled kernel to boot because I am unable to pass arguments via cmdline on boot :crying:
DeepUnknown said:
Thank you for your tool my friend
Though I have one question regarding this:
When I attempt to compile kernel from source, Sony said in the read me file that memory layout and other stuff are passed to kernel via cmdline. I do that just like it's written in the cmdline I quoted?! because I want to use the latest kernel source with an existing zRam but i'm unable to make the newly compiled kernel to boot because I am unable to pass arguments via cmdline on boot :crying:
Click to expand...
Click to collapse
As far as I know, Sony passes all important parameters via kernel ATAGs, not command line.
kuisma said:
As far as I know, Sony passes all important parameters via kernel ATAGs, not command line.
Click to expand...
Click to collapse
I'm sorry I wasn't clear in the previous comment, here is what Sony mentioned:
In the official SW the following command line arguments are given
to the kernel:
cachepolicy=writealloc
noinitrd
init=init
board_id=1
logo.nologo
root=/dev/ram0
rw
rootwait
console=ttyAMA2,115200n8
androidboot.console=ttyAMA2
androidboot.hardware=st-ericsson
<memory layout>
mpcore_wdt.mpcore_margin=359
Click to expand...
Click to collapse
I'm sorry I went out of subject but I was using tools like yours to get zRam from other boot.img file.
Very nice tool, thanks for sharing.
unmkbootimg as of version 1.2 now supports embedded boot images, e.g. a boot image embedded deep in an update.img file.
$ unmkbootimg update.img
unmkbootimg version 1.2 - Mikael Q Kuisma <[email protected]>
File update.img not a plain boot image, seeking for embedded image ... found!
Kernel size 8073252
Kernel address 0x60408000
Ramdisk size 6380372
Ramdisk address 0x62000000
Secondary size 0
Secondary address 0x60f00000
Kernel tags address 0x60088000
Flash page size 16384
Board name is ""
Command line ""
*** WARNING ****
This image is built using NON-standard mkbootimg!
OFF_KERNEL_ADDR is 0x00380100
OFF_RAMDISK_ADDR is 0x01F78100
OFF_SECOND_ADDR is 0x00E78100
Please modify mkbootimg.c using the above values to build your image.
****************
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x60087f00 --pagesize 16384 -o new_boot.img
---------------
$ ls
initramfs.cpio.gz update.img zImage
$
Click to expand...
Click to collapse
kuisma said:
unmkbootimg as of version 1.2 now supports embedded boot images, e.g. a boot image embedded deep in an update.img file.
Click to expand...
Click to collapse
Thanks for the update, very cool feature.
Can not extract zImage?
Could you check why I Can not extract zImage from this Kernel:
http://forum.xda-developers.com/showpost.php?p=37909023&postcount=56
mafamafa said:
Could you check why I Can not extract zImage from this Kernel:
http://forum.xda-developers.com/showpost.php?p=37909023&postcount=56
Click to expand...
Click to collapse
It's because it's not an Android boot image, but a Rockchip specific kernel image file.
Hi, could you please post the source here or upload in github or similar and provide the link. That will be much better.
Sent from my Amazon Kindle Fire HD using xda app-developers app
jeevas.v said:
Hi, could you please post the source here or upload in github or similar and provide the link. That will be much better.
Click to expand...
Click to collapse
Why? It's a trivial hack, and if you're a programmer, you'll put one together in minutes anyway.
So, no.
That is very bad and unethical. It is not a question of I or somebody can do it. Even it violates many things by saying no. What a pathetic situation.
Sent from my Amazon Kindle Fire HD using xda app-developers app
jeevas.v said:
That is very bad and unethical. It is not a question of I or somebody can do it. Even it violates many things by saying no. What a pathetic situation.
Click to expand...
Click to collapse
Say what? I'm providing the community a useful software for free - and you blame me for being unethical? :laugh:
I'm saying that you are using Foss as you like and hesitating to publish even a trivial change that you made. How can the community trust your binaries unless they don't have the source. What kind of mindset is that? Have you ever read GPL?
What do you think you are doing? Social service the Microsoft way? What a joke!
Sent from my Amazon Kindle Fire HD using xda app-developers app
jeevas.v said:
I'm saying that you are using Foss as you like and hesitating to publish even a trivial change that you made. How can the community trust your binaries unless they don't have the source. What kind of mindset is that? Have you ever read GPL?
What do you think you are doing? Social service the Microsoft way? What a joke!
Click to expand...
Click to collapse
GPL? My code is written from scratch, and is not a subject of GPL whatsoever.
You, my friend, are making a fool of your self. Please, don't let me hinder you.
I am trying to spread the awareness against the closed source behaviour and I hope I achieved that in whatever miniscule way.
I don't care about your binary or code but thought of asking you to know if you are intentionally not giving the source by giving just the 32bit binaries. Anyway so now everyone knows...
Sent from my Amazon Kindle Fire HD using xda app-developers app
how to build Rockchip specific kernel image file?
kuisma said:
It's because it's not an Android boot image, but a Rockchip specific kernel image file.
Click to expand...
Click to collapse
Can you tell how to build Rockchip specific kernel image file - or where to loog for that information?
mafamafa said:
Can you tell how to build Rockchip specific kernel image file - or where to look for that information?
Click to expand...
Click to collapse
I have no idea whatsoever how Rocketchip manages its boot images.

Request for framework-res.apk and SystemUI.apk

Hello
Can someone help me and share the framework-res.apk and SystemUI.apk from JOP40D Stock odexed ? Or at least tell me where I can download it.
Thank You.
marser said:
Hello
Can someone help me and share the framework-res.apk and SystemUI.apk from JOP40D Stock odexed ? Or at least tell me where I can download it.
Thank You.
Click to expand...
Click to collapse
You can find these things in the system.img provided by the JOP40D factory image for occam. I've added them to an archive and attached to this post.
Thank you. Just to increase my knowledge... How I can extract the *.img ?? I was looking over the net looking for it, but i couldn't do finally.
marser said:
Thank you. Just to increase my knowledge... How I can extract the *.img ?? I was looking over the net looking for it, but i couldn't do finally.
Click to expand...
Click to collapse
Try 7-zip. I believe it can. Also a super light weight program.
Sent from my GT-I9000 using xda premium
marser said:
Thank you. Just to increase my knowledge... How I can extract the *.img ?? I was looking over the net looking for it, but i couldn't do finally.
Click to expand...
Click to collapse
I can provide the steps to do this in Linux as that is what I'm familiar with.
The system.img file is a sparse ext4 image that needs to be unpacked before it can be mounted. This is done with a binary compiled from AOSP source. Here are the steps for that:
Code:
git clone https://android.googlesource.com/platform/system/core
cd core
git checkout android-4.2.1_r1
cd libsparse
gcc -o simg2img -Iinclude -lz simg2img.c sparse_crc32.c backed_block.c output_file.c sparse.c sparse_err.c sparse_read.c
Once the simg2img binary is compiled you can make use of it on a sparse image:
Code:
simg2img system.img system.unpacked.img
The resulting unpacked.img will be much larger than the sparse image but can now be mounted and it's contents traversed.
Code:
mount -t ext4 -o loop system.unpacked.img /mnt/unpacked_system
want framework and system ui
I want nexus 4's stock rom JB 4.2 frame work and system ui...

[Tutorial] Kernel building instructions for Xperia SP

kernel sources for Xperia SP (C5302, C5303, C5306, M35h) {FW: 12.0.A.1.257} are available...
link to download sources:
http://dl-developer.sonymobile.com/code/copylefts/12.0.A.1.257.tar.bz2
i will keep pushing stock kernel sources to my git tree at the following branch:
https://github.com/DooMLoRD/android_kernel_sony_msm8960t/tree/sony_sources
following are the build instructions for developers who plan to work on this device....
toolchain recommended: Google GCC 4.7
Building kernel (zImage):
for Xperia SP:
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make viskan_huashan_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8
incase u get errors like:
Code:
error : /scripts/gcc-wrapper.py
just correct the permissions of that file
Code:
chmod 755 ./scripts/gcc-wrapper.py
here is patch for compatibility with GCC 4.7 compilation
regards,
DooMLoRD
Instructions for building kernel.elf
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/tree/master/msm8960t_viskan
Sony using the ELF format (similar to the 2012 devices)...
build kernel.elf
u can directly use the files posted at my git repo for build tools
or
use the following command:
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
the correct RPM.bin & bootcmd are posted at my git tree for build tools...
regards,
DooMLoRD
@DooMLoRD
I have to answer a lot of questions when compiling like board selection etc (have been clicking y and and enter for about 30 minutes now) is this normal?
View attachment 2411564
Hi Doomlord.
Being a fresh Xperia User, never heard about u on HTC forums. But glad to know you are helping a lot of people around here. I was wondering whether you could help me in understanding a bit about xperia phones before i dive into kernel kanging n stuff.
What i know from HTC devices
Partitions are like this:
Boot (separate partition on NAND)
Recovery (separate partition on NAND)
System like above
Data, same
Cache, same
etc
There, we used to flash boot.img to boot. boot.img contained kernel zImage+ramdisk
For recovery, we have recovery.img which contained zImage+recoveryramdisk
Then system and data etc as every other phone.
Here in Xperia, i cant understand where the recovery is. Is it inside kernel.elf?
Is it placed on a dedicated partition?
I want to know what i am messing with, before continuing.
What i plan to do is.
Build a clean TWRP from source (for myself, usage and learning.)
Build a stock based kernel from source. Add few govs/scheds and maybe Doubletap2wake etc. (but thats a little way ahead.)
Can you help me with this?
neXus PRIME said:
Hi Doomlord.
Being a fresh Xperia User, never heard about u on HTC forums. But glad to know you are helping a lot of people around here. I was wondering whether you could help me in understanding a bit about xperia phones before i dive into kernel kanging n stuff.
What i know from HTC devices
Partitions are like this:
Boot (separate partition on NAND)
Recovery (separate partition on NAND)
System like above
Data, same
Cache, same
etc
There, we used to flash boot.img to boot. boot.img contained kernel zImage+ramdisk
For recovery, we have recovery.img which contained zImage+recoveryramdisk
Then system and data etc as every other phone.
Here in Xperia, i cant understand where the recovery is. Is it inside kernel.elf?
Is it placed on a dedicated partition?
I want to know what i am messing with, before continuing.
What i plan to do is.
Build a clean TWRP from source (for myself, usage and learning.)
Build a stock based kernel from source. Add few govs/scheds and maybe Doubletap2wake etc. (but thats a little way ahead.)
Can you help me with this?
Click to expand...
Click to collapse
The recovery is inside the kernel but that's all I know
Sent from my C5303 using xda app-developers app
Yep. I found all I needed to know.... Fotakernel partition, elf ramdisk kernel and other stuff.
Sent from my C5303 using Tapatalk
No NAND is used
EMMC is there in all new xperia devices
Sent from my C6902 using xda app-developers app
DooMLoRD said:
No NAND is used
EMMC is there in all new xperia devices
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
ok thanks...
one more thing, if i build a custom kernel (lets say, stock-based), without any major changes..... can i flash that kernel file without unlocking bootloader???
as i understand, only kernel ftf files can be flashed via flashtool in locked bootlaoder.... correct me if im wrong.
neXus PRIME said:
ok thanks...
one more thing, if i build a custom kernel (lets say, stock-based), without any major changes..... can i flash that kernel file without unlocking bootloader???
as i understand, only kernel ftf files can be flashed via flashtool in locked bootlaoder.... correct me if im wrong.
Click to expand...
Click to collapse
No u can't
Sent from my C5302 using Tapatalk
Siddhesh said:
No u can't
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
I compiled my kernel with a different splash screen and it flashed but I got a flashing black screen and it doesn't boot (i have UBL)
hi @DooMLoRD,
when i am making the elf of the zImage i am getting this error
[email protected]:~/android/huashan files/build tools/jk_output$ sudo bash '/home/jk-cha0s/android/huashan files/build tools/jk_output/build_it.sh'
[sudo] password for jk-cha0s:
Traceback (most recent call last):
File "mkelf.py", line 182, in <module>
main(sys.argv[1:])
File "mkelf.py", line 159, in main
size = os.path.getsize(seg.file)
File "/usr/lib/python2.7/genericpath.py", line 49, in getsize
return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory: 'ramdisk.cpio.gz'
where to get the ramdisk.cpio.gz ?
edit:its inside a working kernel extract from there
neXus PRIME said:
Yep. I found all I needed to know.... Fotakernel partition, elf ramdisk kernel and other stuff.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
hey hi,
i need to know how to integrate recovery into a kernel i made. please help me to do it. :silly:
About Xperia SP(m35t)
Hello DooMLoRD
I want to ask you about how to build a kernel of m35t. I had tried to use the build_tools-master to unzip the kernel of m35t, and then repacked it without any modification. I flash the new kernel.elf but the phone doesn't work, how should I do ?
I want let the m35t run on Android 4.3 cause Sony hasn't update it, hope you can help me. Thanks a lot!
NewBay_STanLey said:
Hello DooMLoRD
I want to ask you about how to build a kernel of m35t. I had tried to use the build_tools-master to unzip the kernel of m35t, and then repacked it without any modification. I flash the new kernel.elf but the phone doesn't work, how should I do ?
I want let the m35t run on Android 4.3 cause Sony hasn't update it, hope you can help me. Thanks a lot!
Click to expand...
Click to collapse
Hi,
For android 4.3 the command to pack has changed from
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
To
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
pec0ra said:
Hi,
For android 4.3 the command to pack has changed from
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
To
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
Click to expand...
Click to collapse
Thanks, Pec0ra.
Yes, I know the command is changed, I repacked original kernel with build_it_JB-4.1.sh, the system is 12.0.C.2.58, everything is original, but the phone doesn't work.
I guess there is a little difference between c5303 and m35t, that I need to make a little modification to this tool.
I found the difference between m35t and other SPs
Finally, I found a difference between m35t and other SPs. The build_tools-master shouldn't be wrong, there is only one explanation is the RPM.bin not working for m35t. So,the rebuilt kernel can't boot up the m35t. @DooMLoRD, could you give me the right RPM.bin for m35t? Thanks a lot!
NewBay_STanLey said:
Finally, I found a difference between m35t and other SPs. The build_tools-master shouldn't be wrong, there is only one explanation is the RPM.bin not working for m35t. So,the rebuilt kernel can't boot up the m35t. @DooMLoRD, could you give me the right RPM.bin for m35t? Thanks a lot!
Click to expand...
Click to collapse
I think you can simply unpack it from stock kernel with the build tools. You will just have to find out which one of the extracted file it is since it might have another name.
Good news!
Good news! I found the way to extract rpm.bin witch use the flashtool. I use the version 207 C5303's zimage and ramdisk.cpio.gz and m35t's rpm.bin to repack the kernel. When I flash the kernel and version 207's rom in my m35t, it works! But only press the power button can let the back light gets on and off, the screen still can't display anything, and it can't play any sound, but it still take a big step!

Categories

Resources