Help needed. For Kernel Image making - Galaxy S I9000 Q&A, Help & Troubleshooting

I was wondering if any body would be kind of enough to write a tutorial of making boot images
I am trying commands from DroidX and so far havent had any success in unpacking and repacking the same kernel.
Also If you can list the different parts of the file system of the phone would be very helpful.
Need a sticky for this
Thanks in advance.

My friend,
Contact skin1980, amit bagaria, rex, ronhoover88 and namaless..
All these people especially amit, skin1980 have very good experience with the source code... ronhoover can point you in the right direction!
Hope I helped.....
Lordrdx666
Sent from my gt-I9003 with A.I. Type

adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"
adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"
adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
adb shell su -c "tar -czvf /sdcard/data.tar.gz /data"
are these numbers correct ?

ganaboy said:
adb shell su -c "dd if=/dev/block/bml1 of=/sdcard/boot.bin bs=4096"
adb shell su -c "dd if=/dev/block/bml2 of=/sdcard/pit.pit bs=4096"
adb shell su -c "dd if=/dev/block/stl3 of=/sdcard/efs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml4 of=/sdcard/Sbl.bin bs=4096"
adb shell su -c "dd if=/dev/block/stl6 of=/sdcard/param.lfs bs=4096"
adb shell su -c "dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096"
adb shell su -c "dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096"
adb shell su -c "dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096"
adb shell su -c "dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096"
adb shell su -c "tar -czvf /sdcard/data.tar.gz /data"
are these numbers correct ?
Click to expand...
Click to collapse
Sorry man, but this need for compile kernel? for me no..
send request to skin, is powerful kernel developer

Its skin who can help on kernel, other than him, no one on this forum. May be amit to certain extent.
Sent from my GT-I9003 using XDA Premium App

Found it !!!!!!
mkbootimg --kernel mykernel --ramdisk myram -o normalboot.img --base 81800000 --pagesize 4096
http://forum.xda-developers.com/showthread.php?t=1109424&page=5
If anyone is interested.

ganaboy said:
Found it !!!!!!
mkbootimg --kernel mykernel --ramdisk myram -o normalboot.img --base 81800000 --pagesize 4096
http://forum.xda-developers.com/showthread.php?t=1109424&page=5
If anyone is interested.
Click to expand...
Click to collapse
Skin and amit are the people for you to contact.... as such I don't have access to a windows based pc usually... having access to linux based computer is another story altogether
Sent from my gt-I9003 with A.I. Type

I wouldn't rely on the source package as of now, Skin mentioned there were outdated files.

Related

[Q] LG Optimus P880 App Removal (Safe List)

Does anyone have a list of app/bloatware that we can remove safely using Titanium Backup?
Something like a list i saw for Xperia phone:
h t t p : // forum.xda-developers.com/showthread.php?t=1046699&highlight=safe+to
Could you direct me to such a list? or maybe add to this forum. Thanks.
I create my script for remove some app in 4x HD as below
adb shell "su -c 'rm /system/app/AppBox.apk'"
adb shell "su -c 'rm /system/app/CalendarWidget.apk'"
adb shell "su -c 'rm /system/app/CameraTestApp.apk'"
adb shell "su -c 'rm /system/app/Chrome.apk'"
adb shell "su -c 'rm /system/app/ChromeBookmarksSyncAdapter.apk'"
adb shell "su -c 'rm /system/app/DrmProvider.apk'"
adb shell "su -c 'rm /system/app/DrmService.apk'"
adb shell "su -c 'rm /system/app/EmailWidget.apk'"
adb shell "su -c 'rm /system/app/FavoriteContactsWidget.apk'"
adb shell "su -c 'rm /system/app/Finance.apk'"
adb shell "su -c 'rm /system/app/GMS_Maps.apk'"
adb shell "su -c 'rm /system/app/HiddenMenu.apk'"
adb shell "su -c 'rm /system/app/HiddenSIMUnlockManu.apk'"
adb shell "su -c 'rm /system/app/HTMLViewer.apk'"
adb shell "su -c 'rm /system/app/LGCbReceiver.apk'"
adb shell "su -c 'rm /system/app/lgercui.apk'"
adb shell "su -c 'rm /system/app/LGFotaClient.apk'"
adb shell "su -c 'rm /system/app/LGHome3_Theme_Biz.apk'"
adb shell "su -c 'rm /system/app/LGHome3_Theme_Cozywall.apk'"
adb shell "su -c 'rm /system/app/LGHome3_Theme_Marshmallow.apk'"
adb shell "su -c 'rm /system/app/MediaHome_X3.apk'"
adb shell "su -c 'rm /system/app/MemoWidget.apk'"
adb shell "su -c 'rm /system/app/MusicWidget.apk'"
adb shell "su -c 'rm /system/app/NativeLiveWallpapersPicker.apk'"
adb shell "su -c 'rm /system/app/News.apk'"
adb shell "su -c 'rm /system/app/PlusOne.apk'"
adb shell "su -c 'rm /system/app/SmartShare.apk'"
adb shell "su -c 'rm /system/app/Street.apk'"
adb shell "su -c 'rm /system/app/VoiceSearch.apk'"
adb shell "su -c 'rm /system/app/WeatherWidget.apk'"
adb shell "su -c 'rm /system/app/YouTube.apk'"
adb shell "su -c 'rm /system/app/HomeSelector.apk'"
adb shell "su -c 'rm /system/app/LGHome3.apk'"
adb shell "su -c 'rm /system/apps/bootup/LGWorld.apk'"
adb shell "su -c 'rm /system/apps/bootup/LGWorldClockWidget.apk'"
adb shell "su -c 'rm /system/apps/bootup/NativeLiveWallpapers.apk'"
adb shell "su -c 'rm /system/apps/bootup/NativeNoiseField.apk'"
adb shell "su -c 'rm /system/apps/bootup/PowerControlWidget.apk'"
adb shell "su -c 'rm /system/apps/bootup/TodayPlusWidget.apk'"
adb shell "su -c 'rm /system/apps/bootup/PolarisOffice.apk'"
Click to expand...
Click to collapse
somboons said:
I create my script for remove some app in 4x HD as below
Click to expand...
Click to collapse
I think, you should change ".apk" to ".*". It will also remove *.odex files
I will try to use Titanium Backup to freeze them.
More input will be be welcomed. Thanks
m0b said:
I think, you should change ".apk" to ".*". It will also remove *.odex files
Click to expand...
Click to collapse
I already deodex and remove .odex successly.
Will this make my battery last longer.. ? I just got this phone and im not impressed with the battery use..
If i remove all the things above will my phone still work correctly..
supernielsen said:
Will this make my battery last longer.. ? I just got this phone and im not impressed with the battery use..
If i remove all the things above will my phone still work correctly..
Click to expand...
Click to collapse
I am seriously thinking of buying the lg 4xhd. Only stenho some doubts in relation to their consumption, lack of updates and the impossibility to install custom rooms. Give me your opinion about this equipment.
If you tried uninstalling all these app, tell us what the new cell behavior
Manholas said:
I am seriously thinking of buying the lg 4xhd. Only stenho some doubts in relation to their consumption, lack of updates and the impossibility to install custom rooms. Give me your opinion about this equipment.
If you tried uninstalling all these app, tell us what the new cell behavior
Click to expand...
Click to collapse
I have removed almost every app with some exceptions on the ones that i actually use and like..
The phone is so much faster now and running real smooth.. Power comsumption is MUCH MUCH better..
Am actually very satisfied about it now..
EDIT: I actually decided to remove the rest so i took them from the top and down.. !!! That were the biggest mistake in my life.. Lock screen perfect after that just black screen !
Is there anything i can do now.. ?
supernielsen said:
I have removed almost every app with some exceptions on the ones that i actually use and like..
The phone is so much faster now and running real smooth.. Power comsumption is MUCH MUCH better..
Am actually very satisfied about it now..
EDIT: I actually decided to remove the rest so i took them from the top and down.. !!! That were the biggest mistake in my life.. Lock screen perfect after that just black screen !
Is there anything i can do now.. ?
Click to expand...
Click to collapse
Re flash it to it's original state.
Zhus06 said:
Re flash it to it's original state.
Click to expand...
Click to collapse
I made a hard reset.. ? that is not enough..
So i need to do something like flash with odin or what do you mean.. ? Im kinda lost right now and pretty confused..
sheesh..
I know its a somehow not too new thread but for the records...
you always should back up apps with titanium backup before you remove them.
if you didnt:
it should be possible to get these apks from someone else and restore them on your phone by copying them to the appropriate place.
[edit] you can also just make a backup with the preinstalled backup tool.
reset
supernielsen said:
I made a hard reset.. ? that is not enough..
So i need to do something like flash with odin or what do you mean.. ? Im kinda lost right now and pretty confused..
Click to expand...
Click to collapse
I hope this isnt to late to help u.
Try to put out the battery and restart with power + volium down (recovery)
or power + volium up (also named recovery by my phone but its similiar to odin mode) --hold the buttons ´til u can see a white window
try in which mode do u can go.
1.Try to go in second mode.
2.Now u should be able to use the LG PC suite.
3.Connect phone via usb.
4.Click [install usb driver](needs admin rights)
5.If this was succesfulle, click at [SW-Upgrade] (or SW-Update)
If u cant go in recovery mode try to conect it during the boot --Then go to step 2.--
i hope i could help u and it was not to late
and sorry for my bad english
hello! I can not synchronize my google bookmarks with stock browser. I lost chromebookmarksSyncAdapter.apk and ChromewithBrowser.apk and the respective files.odex from system/app folder.
Could someone kindly post them?

[GUIDE] ADB to Pull Images of L90

Thanks to @evoname for showing me how to do this! [emoji4]
This is if you are interested in pulling the system images for whatever reason. I'm not responsible if you brick your device. Use at your own risk!
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/aboot.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/abootb.img
dd if=/dev/block/mmcblk0p16 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/laf.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/recovery.img
dd if=/dev/block/mmcblk0p31 of=/sdcard/system.img
exit
exit
adb pull /sdcard/aboot.img
adb pull /sdcard/abootb.img
adb pull /sdcard/boot.img
adb pull /sdcard/laf.img
adb pull /sdcard/recovery.img
adb pull /sdcard/system.img
exit
Sent from my LG-D415 using Tapatalk

[DEV] Partition backups LG G2

Here's the codes to backup your partitions on the LG G2. Probably work an any variant. I need this for future references as now it will be stored online forever!!!
Need ADB installed.
adb shell
adb su
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/sdcard/rpm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/sdcard/tz.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
----
dd if=/dev/block/platform/msm_sdcc.1/by-name/dbi of=/sdcard/dbi.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/sdcard/sbl1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img

Issue with SuperSU on AndroidThings 1.0

I tried to perform a manual installation of SuperSU (2.82 SR5) on my Raspberry Pi running the developer version of AndroidThings 1.0.4, which is based on Android 8.1.0 / API 27. Rather than flashing the zip in recovery, as I'm not sure where to start with that on the Things platform, I manually pushed files and set file permissions and contexts via adb shell. My guide for this was the summary at the top of the script at SuperSU/META-INF/com/google/android/update-binary.
The new su binary appears to work for the most part. I can execute su and read/write with the interactive shell. However, when I attempt to execute the same operations as a command through su (ie: su -c mkdir /system/testdirectory), it responds saying its a read-only filesystem. The filesystem has been remounted with adb remount. I'm unable to perform the remount with the mount command, as /system is not listed in /proc/filesystems. From my understanding, this is due to some recent security model changes in Android. That being said, after the adb remount, all other normal interactions with the filesystem seem to work without issue. I have verified that selinux is in permissive mode.
I don't have busybox installed. These efforts are to allow for installation of busybox for other projects.
Does anybody know whats causing the commands proxied through su to not work correctly?
Here are the commands I used to perform my manual installation.
Code:
cd ~/Downloads/SuperSU-2.82-SR5
adb connect [IP_ADDRESS]:5555
adb root
adb remount
adb push common/install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 0755 /system/etc/install-recovery.sh
adb shell chcon u:object_r:toolbox_exec:s0 /system/etc/install-recovery.sh
adb shell ln -s /system/etc/install-recovery.sh /system/bin/install-recovery.sh
adb shell chcon -h u:object_r:toolbox_exec:s0 /system/bin/install-recovery.sh
cd armv7
# adding as `su_next` to prevent any issues before dropping it in
adb push su /system/xbin/su_next
adb shell chmod 0755 /system/xbin/su_next
adb shell chcon u:object_r:system_file:s0 /system/xbin/su_next
adb push su /system/xbin/daemonsu
adb shell chmod 0755 /system/xbin/daemonsu
adb shell chcon u:object_r:system_file:s0 /system/xbin/daemonsu
adb push supolicy /system/xbin/supolicy
adb shell chmod 0755 /system/xbin/supolicy
adb shell chcon u:object_r:system_file:s0 /system/xbin/supolicy
adb push libsupol.so /system/lib/libsupol.so
adb shell chmod 0644 /system/lib/libsupol.so
adb shell chcon u:object_r:system_file:s0 /system/lib/libsupol.so
adb shell cp /system/bin/app_process32 /system/bin/app_process32_original
adb shell cp /system/bin/app_process32 /system/bin/app_process_init
adb shell rm /system/bin/app_process
adb shell ln -s /system/xbin/daemonsu /system/bin/app_process
adb shell rm /system/bin/app_process32
adb shell ln -s /system/xbin/daemonsu /system/bin/app_process32
adb shell chmod 0755 /system/bin/app_process
adb shell chmod 0755 /system/bin/app_process32
adb shell chcon u:object_r:system_file:s0 /system/bin/app_process
adb shell chcon u:object_r:zygote_exec:s0 /system/bin/app_process32
# Swapping new su binary in
adb shell cp /system/xbin/su /system/xbin/su_original
adb shell rm /system/xbin/su
adb shell mv /system/xbin/su_next /system/xbin/su
adb shell /system/xbin/su --install
adb reboot
I need to correct myself: the new su binary can only read with privileges. It cannot write at all. I am only able to write either as the adb root shell, or with the stock su binary. I noticed that the device's adbd process relaunches with its own privileged context passed to it when adb remount is run. (adbd --root_seclabel=u:r:su:s0)
If I've run adb root and adb remount, adb shell, and then enter the su binary, I lose the ability to write to the remounted filesystem. So it appears that there is something wrong with the new su binary and its related files.
Anyway, this isn't critical to my project, so I'm abandoning my efforts for now. If anyone has any ideas on what is wrong here, I'd love to hear them and give this another shot!

[SCRIPT] [HACK] root on most variant

REMOVED
Mods please close thread
Code:
adb push su98 /data/local/tmp
adb shell cd data/local/tmp && adb shell chmod 775 su98 && adb shell ./su98 && adb shell su
adb push recovery /sdcard
adb shell cat /dev/zero >> /dev/mtd/mtd2 && adb shell cd /sdcard && adb shell flash_image recovery /sdcard/recovery.img
adb shell rm /sdcard/recovery.img
adb shell reboot
sorry this is incomplete, more like a PoC
I think will not work if bootloader still locked
GiaiPhapAndroid said:
I think will not work if bootloader still locked
Click to expand...
Click to collapse
yEs

Categories

Resources