Related
This probably belongs in the developer section, but I don't have permission to post there yet)
This work is very preliminary. It isn't really anything more than a starting point right now. It DOES NOT yet provide a faithful representation of a custom ROM in the emulator.
Current status:
emulator running 2.6.29 kernel with a combination of frankenstein of the emulator and devoid-franco system image.
I've been working to get a custom ROM working in the Android SDK emulator. There are several reasons for this, but in the end, it makes it a lot easier to test out different tweaks to get the ROM working as I'd like (I need some functions provided on the P509 ROM that aren't provided on any custom ROMS, and reinstalling the APKs isn't sufficient). I spent a lot of time looking for a thread about this, but nothing I could find discusses the specifics of working with a P500 based device
Things I've learned:
a) you need a kernel specifically compiled for the emulator, and the ramdisk image needs to be built to work with an emulator. For the moment i am using the SDK kernel (2.6.29) and ramdisk image to get going
b) the p509 libraries aren't compatible with the emulator, I needed to copy the libraries from the supplied emulator image
Here are some notes I took. I'll try to flush this out more as I make further progress:
Tools you will need:
Android SDK and 2.2 platform files (android-8)
unyaffs
mkfs.yaffs2.x86
a copy of the ROM image to install (devoid.franco.v5 in my case)
before beginning you should build a stock 2.2 emulator env to ensure everything is working (from sdk/tools run):
android list targets
find the id for 2.2 (was '4' for me)
android create avd -n test-froyo -t 4
(I used all defaults, except I set the RAM to 512MB and screen to HVGA)
emulator -avd test-froyo -show-kernel
(this should eventually bring up a running froyo)
you'll need to know where the avd lives. In linux, it should be in ~/.android/avd/test-froyo
I'm working on linux, but this should work in Windows if you can find a compiled version of mkfs.yaffs2 for windows (I've seen a compiled unyaffs version out there)
1) unzip the rom image. it should create a system/ directory.
We should execute the updater-script here, but we'll take a short-cut:
chmod -R 655 system/
2) uncompress the platfrom system image:
in a new dir:
unyaffs <sdk path>/platforms/android-8/images/system.img
3) copy all files from system/ in step-2 to system/ in step-1
we should really need to do this, it is probably sufficient to run the updater-script and then copy the framework/, lib/ and a couple qemu files, but this is just to get things going.
4) make dbus.conf readable:
chmod 644 system/etc/dbus.conf
5) remove system/app/LGSetupWizard.apk
This app relies on custom classes in the firmware that aren't present in the emulator base system. I'm still trying to build a custom firmware.jar that has both.
6) build a new system.img
mkfs.yaffs2.x86 system system.img
7) copy the system image to your avd dir:
cp system.img ~/.android/avd/test-froyo
If everything has gone well, you can now startup the emulator and boot into franco's rom:
emulator -avd test-froyo -show-kernel
Because we copied too much stuff from the default system.img, we've lost his themes and mst of his tweaks, so it isn't really a faithful representation of the ROM at all, but we've cleared the 1st milestone of being able to boot up.
I also booted a stock P509 kernel this way with a few changes:
a) I used nandroid to get the system image, and then unyaffs2 to extract it)
b) I removed all odex files:
find system -name "*.odex" | xargs rm
Again, this isn't really a custom ROM, it is actually the emulator rom with additional apps and customizations. The goal is to get to as close as possible to running a true custom ROM
A few other notes:
the following framework files can be preserved from the custom ROM (no need to overwrite):
Code:
am.jari : ok
android.policy.jar : not ok
android.test.runner.jar : ok
bmgr.jar : ok
core.jar : ok
ext.jar : ok
framework.jar : not ok
framework-res.apk : not ok
framework-tests.jar : ok
ime.jar : ok
input.jar : ok
javax.obex.jar : ok
monkey.jar : ok
pm.jar : ok
services.jar : not ok
svc.jar : ok
framework.jar is the most important of the 'not-ok' ones as far as I can tell, and is missing several classes. I am currently working to build a services.jar that is a merge of the P500 and emulator classes.
Installing the p500 framework,.jar requires many files from system/lib, but once all dependencies are solved, you eventually end up with a segfault. I've been unable to debug that, and am not sure I want to. The goal is to get a running dalvik VM with all classes needed to run P500 apps.
First blood!!!
Hi all,
In this thread, I will try to share the knowledge I have on deodexing, making custom ROMs, modifying initramfs, building kernel and much more.
Please check the below posts for each of these tutorials.
Hope this opens doors to many new ROM and Kernel developers.
NOTE: THESE TUTORIALS ARE WRITTEN FOR GT-I9100. WILL NOT WORK ON OTHER DEVICES. I DON'T TAKE ANY RESPONSIBILITY IF YOU MESS UP AND BRICK YOUR DEVICE OR ANYTHING ELSE. USE AT YOUR OWN RISK.
Deodexing Stock Rom
For GINGERBREAD ROMS:
What you need to have:
xUltimate v2.3.3 - you can download it HERE (Thanks and Credits to Xeudoxus for this awesome app)
Rooted kernel with busybox
JDK installed on your Windows system
If adb is not available in your windows PC, in xUltimate folder open "jar" folder. You'll find adb there.
Extract stock app & framework folders and Deodex:
Connect your device to computer.
Start xUltimate (double-click on Main.exe)
Select option 1. (Pull /system/app)
Once option is done, select option 2. (Pull /system/framework)
In the same folder, now you'll see two new folders (origi_app, origi_frame)
Select option 3 in Main menu (Deodex /system/app)
Once its done, select option 4 in Main menu (Deodex /system/framework)
DONE!!
NOTE: If any apk/odex gives issues while deodexing, remove that corresponding apk and odex from origi_app folder and deodex again. (Mostly the apps which can be downloaded from play store might give errors.. ex: Maps, Voice search etc.)
Now you'll see two new folders done_app and done_frame.
Push deodexed app and framework to device:
Connect your device to PC in USB debugging mode.
Copy done_app and done_frame folders to root of sdcard (/sdcard).
Open Windows command prompt and type the below commands.
Code:
[LIST]
[*]adb shell
[*]su
[*]stop
[*]mount -o remount,rw /dev/block/mmcblk0p9 /system
[*]rm /system/app/*.odex
[*]rm /system/framework/*.odex
[*]busybox cp /sdcard/done_app/* /system/app/
[*]busybox cp /sdcard/done_frame/* /system/framework/
[*]chmod 644 /system/app/*
[*]chmod 644 /system/framework/*
[*]mount -o remount,ro /dev/block/mmcblk0p9 /system
[*]sync
[*]reboot recovery
[/LIST]
In Recovery, Wipe Cache and Wipe Data/Factory reset.
Reboot.
Now you've deodexed app and framework.
For ICS ROMS:
For ICS Roms, the process is quite easy. (Thanks and Credits to jaydvn.)
Download the attached zip file.
Extract it on your windows PC.
Copy your /system/app to _app folder
Copy your /system/framework to _framework folder.
Run AutoDEOToolMain.bat
Follow the instructions.
deodexed jars and apks will be found in deodexed_APK and deodexed_JAR.
Push deodexed app and framework to device:
Connect your device to PC in USB debugging mode.
Copy deodexed_APK and deodexed_JAR folders to root of sdcard (/sdcard).
Open Windows command prompt and type the below commands.
Code:
[LIST]
[*]adb shell
[*]su
[*]stop
[*]mount -o remount,rw /dev/block/mmcblk0p9 /system
[*]rm /system/app/*.odex
[*]rm /system/framework/*.odex
[*]busybox cp /sdcard/deodexed_APK/* /system/app/
[*]busybox cp /sdcard/deodexed_JAR/* /system/framework/
[*]chmod 644 /system/app/*
[*]chmod 644 /system/framework/*
[*]mount -o remount,ro /dev/block/mmcblk0p9 /system
[*]sync
[*]reboot recovery
[/LIST]
In Recovery, Wipe Cache and Wipe Data/Factory reset.
Reboot.
Done.
Enjoy.
Building kernel
Okay. Let's learn how to build kernel for GT-I9100. There are many ways to build. I am just presenting here the way I build and make kernel.
NOTE 1: Follow the instructions exactly.
NOTE 2: Kernel is opensource. If you make any changes to it, you're expected to share your source. (Usually people share it over github )
NOTE 3: FLASHING KERNEL IS RISKY AND DANGEROUS. BE CAREFUL. BUILD AND FLASH ON YOUR OWN RISK.
What you need to have:
Ubuntu 10.04 and above (I use 10.04 )
ARM tool chain (Download HERE. Click on IA32 GNU/Linux TAR under Advanced Packages)
Samsung's opensource kernel for GT-I9100 (Download HERE. Go to Mobile->Mobile Phone-> Select I9100 (update 3 for Gingerbread and update 4 for ICS) and download the zip)
Setting up toolchain:
Extract the tar you downloaded(Suggestion: Extract to one folder where you can have everything. In my case /home/superatmos/build_kernel).
After extracting, you'll see a folder named arm-2010q1. Inside there will be many folders (ex. bin, lib and so on.)
Folder structure will be: /home/<your_name>/build_kernel/arm-2010q1
Setting up kernel:
Extract the zip you've downloaded from samsung's opensource.
You'll find two zips.
Extract GT-I9100_Kernel.tar.gz to /home/<your_name>/build_kernel/
Folder structure: /home/<your_name>/build_kernel/GT-I9100_Kernel
Setting up initramfs:
Samsung's zImage is divided into two parts: Opensource kernel (which you downloaded from samsung's website) and initramfs (which is root file system to boot up the device).
You can extract initramfs from your zImage using the below mentioned links (Credits and Thanks to Chenglu) Original Thread: HERE
To extract initramfs from Gingerbread zImage: HERE
To extract initramfs from ICS zImage: HERE
Folder structure: /home/<your_name>/build_kernel/initramfs
Now the entire setup is ready. Let's start modifying kernel configuration.
Setting up kernel config:
For Gingerbread:
Go to /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/configs folder.
Copy c1_rev02_defconfig file and paste it in kernel root folder (/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Rename c1_rev02_defconfig to .config in kernel root folder.
Now open Makefile which is in your kernel root folder(/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Modify the below lines (I guess line 195 and 196).
For ICS:
Go to /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/configs folder.
Copy u1_defconfig file and paste it in kernel root folder (/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Rename u1_defconfig to .config in kernel root folder.
Now open Makefile which is in your kernel root folder(/home/<your_name>/build_kernel/GT-I9100_Kernel/).
Modify the below lines (I guess line 195 and 196).
Code:
ARCH ?= arm
CROSS_COMPILE ?= /home/<your_name>/build_kernel/arm-2010q1/bin/arm-none-linux-gnueabi-
Save and close.
Modifying kernel configuration:
Now open .config file(which you renamed). If its not seen, it might be hidden. Go to View->Show hidden files and there you go.
Do the below things:
Adding local version:
Change CONFIG_LOCALVERSION=" " to anything you like. I add this way:
CONFIG_LOCALVERSION="-I9100-superatmos"
Adding initramfs path:
You need to let kernel know the path from which it needs to take initramfs.
Change CONFIG_INITRAMFS_SOURCE=" " to ../initramfs (In this tutorial it's the path. If you had copied anywhere else, give the path properly).
Enough for now. Once you get experience, you can modify many configurations as per your liking and save. This configuration can be changed by GUI too with the command make menuconfig.
The Important part: Building the kernel:
For Gingerbread:
Open terminal.
Go to path /home/<your_name>/build_kernel/GT-I9100_Kernel/
Type make.
For ICS:
Open terminal.
Go to path /home/<your_name>/build_kernel/GT-I9100_Kernel/
Type export USE_SEC_FIPS_MODE=true
Type make.
THAT'S ALL. YOUR zImage is ready and is available in /home/<your_name>/build_kernel/GT-I9100_Kernel/arch/arm/boot/zImage.
Install the zImage on the device:
Go to the path where zImage is present and type the below line in command line.
Code:
tar cvf I9100_kernel.tar zImage
Flash the tar using odin.
DONE. CONGRATULATIONS. NOW YOU'VE YOUR OWN KERNEL.
Give me your feedback so that I can improve this tutorial. And post here about how your build went. All the best.
Making custom ROM
Let's move on to make a custom ROM.
Inputs/Feedback/Suggestions are more than welcome. Lets improve this tutorial together for the betterment of the android community.
Steps involved in making a custom ROM:
Getting the system dump from the device.
Deodexing app and framework folders.
Creating various mods by modifying framework and system files.
Modifying build.prop and adding tweaks.
Making META-INF folder and writing an updater-script (edify scripting).
Signing the ROM and making a flashable zip.
Folder Structure:
Before going forward, let's follow the below structure folder to make the tutorial more understandable.
Let our ROM name be CustomROM. The folder structure will be C:\Users\<your name>\CustomROM.
Let's move step by step. Are you ready??
Getting the system dump from the device
Click to expand...
Click to collapse
Make sure USB debugging is ON and connect your device to the PC.
Open command prompt on your windows PC and go to CustomROM folder path.
Type adb devices. You should be able to see the device detected. (If not check environmental variables whether adb is in system path or not. If not present, add the adb path.)
Type the below command to get the dump of system folder.
Code:
adb pull /system system/
Now inside the folder CustomROM, you should be able to see system folder with many folders like app, etc, framework etc inside.
Done with first step.
Deodexing app and framework folders
Click to expand...
Click to collapse
Look HERE how to deodex app and framework folders. Copy the app and framework folders to xUltimate folder, rename them to origi_app and origi_frame and follow the given link to deodex.
NOTE: After deodexing, merge origi_app folder with app folder under C:\Users\<your name>\CustomROM\system\app and origi_frame with framework folder under C:\Users\<your name>\CustomROM\system\framework.
Creating various mods by modifying framework and system files
Click to expand...
Click to collapse
Okay. This the section where your hardwork, innovation and talent comes in. You can use the mods available already, create your own mods, port various mods from other devices and so on.
Below is a list of various mods which can be ported on to GT-I9100. All the credits go these respective thread owners. Thanks to them.
Lidroid 14 toggle mod
Extended power menu with/without header
CRT Off Animation & SIP Over LTE/HSPA
Swipe to remove notifications
NOTE: Let me know more mods with links so that I can add here.
Modifying build.prop and adding tweaks
Click to expand...
Click to collapse
Okay. This is one of those files where you name your ROM(to be visible in settings. ) and add many tweaks.
To name your ROM (to be visible in settings), change the below code.
Code:
ro.build.display.id=CustomROM v1.0
Check the below links for many other tweaks. All credits go to respective thread owners. Thanks to them.
build.prop tweaks by TheFrankenstain
build.prop tweaks by dhlalit11
Making META-INF folder and writing an updater-script (edify scripting)
Click to expand...
Click to collapse
Once you're done with all the modifications, mods and additions, its time to create META-INF folder and make the updater script. Once the user flashes the ROM zip, this is the script that runs and does everything written inside the script. PLEASE BE CAREFUL WITH THIS. TAKE REFERENCE FROM OTHER (SAME DEVICE) ROMS' UPDATER-SCRIPT. (In this case, take reference from other GT-I9100 roms.)
Check the below links for tutorial and how-to on writing edify script and making updater script. All credits go to respective owners of the threads. Thanks to them.
Edify Scripting, Making Flashable ZIPs, ZIP Signing & Key Creation
Edify Scripting Notes
How to Write an Updater-Script with Edify Code
Edify Installation Script Syntax's
NOTE: system folders path, boot/kernel partition path, modem partition path and so on are COMPLETELY DIFFERENT for DIFFERENT DEVICES. Check the partitions for your device properly, carefully and then work on updater-script. TAKE HELP OR REFERENCE FROM OTHER ROM DEVELOPERS FOR YOUR DEVICE.
Lets move on to last step. Making a signing and making a flashable zip.
Signing the ROM and making a flashable zip
Click to expand...
Click to collapse
Make sure, now you should be able to find two folders (META-INF and system) inside C:\Users\<your name>\CustomROM.
Check in THIS thread for test signing your ROM. It WORKS with GT-I9100.
or Check THIS thread to create your own signing key and certificate.
Now you're done with making a custom ROM. Hope to see more custom ROMs from many users.
Give me your feedback so that I can improve this tutorial. And post here about how your custom ROM making went. All the best.
last one
i don't see any tutorials just links to a diff thread and a rom that won't work on i9100
buster041284 said:
i don't see any tutorials just links to a diff thread and a rom that won't work on i9100
Click to expand...
Click to collapse
You're quite fast Updated Deodexing and Building kernel section..
Great thread Superatmos. I'll definately have a go at this.
Quick question ? Am i right in assuming that although your tutorial says to connect your device this line from xUltimate seperceeds that ?
"Alright xUltimate has been updated to v2 What this means is that you do not need your phone connect to your computer to deodex. So you can just manually place the .odex files in (\origi_frame\) and (\origi_app\) and it will deodex. You can also transfer the .odex files from your phone like the last version."
where do I get the zImage to extract the initramfs from? I can't seem to find the zImage on my phone or in the source anywhere.
Great
Very useful.. Added to my favorite.
Thank's man, i'll read that
puccini said:
Great thread Superatmos. I'll definately have a go at this.
Quick question ? Am i right in assuming that although your tutorial says to connect your device this line from xUltimate seperceeds that ?
"Alright xUltimate has been updated to v2 What this means is that you do not need your phone connect to your computer to deodex. So you can just manually place the .odex files in (\origi_frame\) and (\origi_app\) and it will deodex. You can also transfer the .odex files from your phone like the last version."
Click to expand...
Click to collapse
Connect your device to the PC and double click Main.exe inside xUltimate folder. Follow the instructions you see from then. Its quite self explanatory.
If you already have origi_app and origi_frame folders, then just double click on Main Skip.bat.
dmp450 said:
where do I get the zImage to extract the initramfs from? I can't seem to find the zImage on my phone or in the source anywhere.
Click to expand...
Click to collapse
Use ktool (available on market.. compatible with I9100) and click on Dump current kernel. You'll find it on sdcard.
One more way is when you download firmware from sammobile.com, just extract the file and you'll find zImage inside it.
Nice thread,
I m waiting from long time.
Thanks for your work.
Sent from my GT-I9100 using XDA
Making custom ROM section updated
Hi all,
Please find updated custom rom section HERE.
Feedback and suggestions welcome.
Thanks for the kernel part, will come in handy
Enviado desde mi GT-I9100 usando Tapatalk 2
Good tutorial, thanks.
How do you guys sign the rom if you are on Linux (ubuntu for me)
hi superatmos
thanks for this handy thread...may i ask your for a help here?why in my every deodexing always gives error result?
I attach the screenshots.
Many thanks in advance
tks mate will try to pack my own kernel following this method
Sent from my GT-I9100 using Tapatalk 2
Hi Guys ...
For those of you who want to change the logo of your android phone when turned on, it should change the logo on the kernel you are using, with your own logo, I will try to help explain how a simple and more detailed. If you can not do it any other way. Mugkin this way can help you. Tools needed:
- Linuk + Perl
- Windows
- A little patient and creative.
Ok! Go ...............
1. Prepare to be in exstack Kernel. You must open a pack kernel first. "DooMLord" has made the tool easy to us doing that, this tool will work in linuk.
Download the device see here:
+ Unpack-kernelsin:
http://forum.xda-developers.com/showthread.php?t=1262656
+ Kernel.sin-and-FTF-creator-v1.0:
http://forum.xda-developers.com/showthread.php?t=1363460
Run your Linuk ....
Save-kernelsin.pl and unpack the kernel will be open, the folder "HOME" on your linuk.
Call the command prompt, then type:
. / Unpack-kernelsin.pl kernel.sin
or use the command
perl unpack-kernelsin.pl kernel.sin
It will make:
- Folder-ramdisk kernel.sin
- Kernel.sin-ramdisk.cpio.gz
- Kernel.sin-kernel
- Kernel.sin-header
Delete the file "kernel.sin-ramdisk.cpio.gz" and file "kernel.sin-header".
Open the folder "kernel.sin-ramdisk",
Please edit or replace your "logo.rle" in the folder "kernel.sin-ramdisk" according to your desire. When finished editing "logo.rle", then do to repack folder "kernel.sin-ramdisk", by way of
Typing commands at the command prompt:
$ Cd kernel.sin-ramdisk
find. | Cpio-o-H newc | gzip> .. / newramdisk.cpio.gz
This will result in "newramdisk.cpio.gz"
2. Now we take the file "kernel.sin-kernel" and "newramdisk.cpio.gz". Save and make sure that both files in one folder.
3. Now you fire up your windows, preferably on Win-xp.
4. Open the folder kernel.sin-and-FTF-creator for your mobile
5. Enter "kernel.sin-kernel" and "kernel.sin-ramdisk.cpio.gz" into folder-and-FTF kernel.sin-creator.
6. Make sure Java is installed on your windows? or if not, you can follow this step.
7. On BUILD-IT.BAT right click and click edit, in order to be as follows:
echo Manifest-Version: 1.0 > manifest.mf
echo device: X10 >> manifest.mf
echo branding: dooMkernel -v06-BootManager-v1.4 >> manifest.mf
echo Created-By: dooMkernel >> manifest.mf
echo version: 2.3.3 >> manifest.mf
ren kernel.jar X10_2.3.3_dooMkernel-v06-BootManager-v1.4.ftf
8. Remove the line
del manifest.mf
del kernel.sin
save and reflace to BUILD-IT.BAT
9. In the folder-and-FTF kernel.sin-creator instead of the name "kernel.sin-kernel" to "image" and rename "-ramdisk.cpio.gz kernel.sin" to "ramdisk"
*NOTE!!
[Make sure you have change the file name correctly, because if not kernel.sin corupt.
If you have a problem in changing the name, street and do this:
How to Rename File Extensions:
Renaming File Extensions can be very handy when trying to convert one file name to another. There are many programs on the web that can help you do this. But are you aware that windows operating systems can do this for you? Below are instructions on how to do so.
Go to Start
Control Panel
Folder Options
Click on the 'View' Tab
Then simply uncheck 'Hide extensions for known file types'.
Then click Apply
Finally click Ok
Now you will be able to change file extensions, such as .JPG to .jpg.]
10. Then Double-BUILD-IT.BAT then ENTER
11. It generates two files: "kernel.sin" and "MANIFEST.MF"
12. Next create a save file folder "kernel.sin and loader.sin to the folder.
13. Now run Flashtool
14. Click Advanced and select Bundle Creation
15. In the Select source folder, select the folder where you save the file and loader.sin kernel.sin
16. on the choice Devices customize your devices, adjust the version of ROM version, the choice of content with brand Branding your devices.
17. Move all the contents of the folder content list to the Firmware
18. Click OK
19. Click Flash
20. Select the kernel that you create.
21. Click OK ...... connect the PC to your devices.
21. Flash running process ...................
22. And complete ......
As for how to make images become logo.rle, please refer to the way in this post:
http://forum.xda-developers.com/showthread.php?p=26810498#post26810498
The explanation is quite long, but hopefully can be helpful, especially for those of you who are new to this.
Thanks to: Xda-developers
dooMLord for FTF Creator and unpack the kernel
Bin4ry & Androxyde for Flashtool
And you all, in xda forum
linuk？linux ^^
Sadly I don't have a linux OS, and I'm too lazy to install Ubuntu, is this possible to do it all on Windows 7?
lewislulch said:
linuk？linux ^^
Click to expand...
Click to collapse
yes some tools still have to work on linuk
ItBankRock said:
Sadly I don't have a linux OS, and I'm too lazy to install Ubuntu, is this possible to do it all on Windows 7?
Click to expand...
Click to collapse
maybe if those tools, in potring into windows
This 'kernel kitchen' may also be helpful :-D
http://forum.xda-developers.com/showthread.php?t=1659584
From my XPERIA X10S v8.2 @ 1.19ghz. IF SOMEONE HELPS CLICK 'THANKS'
Apif Fuloh said:
Hi Guys ...
For those of you who want to change the logo of your android phone when turned on, it should change the logo on the kernel you are using, with your own logo, I will try to help explain how a simple and more detailed. If you can not do it any other way. Mugkin this way can help you. Tools needed:
- Linuk + Perl
- Windows
- A little patient and creative.
Ok! Go ...............
1. Prepare to be in exstack Kernel. You must open a pack kernel first. "DooMLord" has made the tool easy to us doing that, this tool will work in linuk.
Download the device see here:
+ Unpack-kernelsin:
http://forum.xda-developers.com/showthread.php?t=1262656
+ Kernel.sin-and-FTF-creator-v1.0:
http://forum.xda-developers.com/showthread.php?t=1363460
Run your Linuk ....
Save-kernelsin.pl and unpack the kernel will be open, the folder "HOME" on your linuk.
Call the command prompt, then type:
. / Unpack-kernelsin.pl kernel.sin
or use the command
perl unpack-kernelsin.pl kernel.sin
It will make:
- Folder-ramdisk kernel.sin
- Kernel.sin-ramdisk.cpio.gz
- Kernel.sin-kernel
- Kernel.sin-header
Delete the file "kernel.sin-ramdisk.cpio.gz" and file "kernel.sin-header".
Open the folder "kernel.sin-ramdisk",
Please edit or replace your "logo.rle" in the folder "kernel.sin-ramdisk" according to your desire. When finished editing "logo.rle", then do to repack folder "kernel.sin-ramdisk", by way of
Typing commands at the command prompt:
$ Cd kernel.sin-ramdisk
find. | Cpio-o-H newc | gzip> .. / newramdisk.cpio.gz
This will result in "newramdisk.cpio.gz"
2. Now we take the file "kernel.sin-kernel" and "newramdisk.cpio.gz". Save and make sure that both files in one folder.
3. Now you fire up your windows, preferably on Win-xp.
4. Open the folder kernel.sin-and-FTF-creator for your mobile
5. Enter "kernel.sin-kernel" and "kernel.sin-ramdisk.cpio.gz" into folder-and-FTF kernel.sin-creator.
6. On BUILD-IT.BAT right click and click edit, in order to be as follows:
echo Manifest-Version: 1.0 > manifest.mf
echo device: X10 >> manifest.mf
echo branding: dooMkernel -v06-BootManager-v1.4 >> manifest.mf
echo Created-By: dooMkernel >> manifest.mf
echo version: 2.3.3 >> manifest.mf
ren kernel.jar X10_2.3.3_dooMkernel-v06-BootManager-v1.4.ftf
7. Remove the line
del manifest.mf
del kernel.sin
save and reflace to BUILD-IT.BAT
8. In the folder-and-FTF kernel.sin-creator instead of the name "kernel.sin-kernel" to "image" and rename "-ramdisk.cpio.gz kernel.sin" to "ramdisk"
*NOTE!!
[Make sure you have change the file name correctly, because if not kernel.sin corupt.
If you have a problem in changing the name, street and do this:
How to Rename File Extensions:
Renaming File Extensions can be very handy when trying to convert one file name to another. There are many programs on the web that can help you do this. But are you aware that windows operating systems can do this for you? Below are instructions on how to do so.
Go to Start
Control Panel
Folder Options
Click on the 'View' Tab
Then simply uncheck 'Hide extensions for known file types'.
Then click Apply
Finally click Ok
Now you will be able to change file extensions, such as .JPG to .jpg.]
9. Then Double-BUILD-IT.BAT then ENTER
10. It generates two files: "kernel.sin" and "MANIFEST.MF"
11. Next create a save file folder "kernel.sin and loader.sin to the folder.
12. Now run Flashtool
13. Click Advanced and select Bundle Creation
14. In the Select source folder, select the folder where you save the file and loader.sin kernel.sin
15. on the choice Devices customize your devices, adjust the version of ROM version, the choice of content with brand Branding your devices.
16. Move all the contents of the folder content list to the Firmware
17. Click OK
18. Click Flash
19. Select the kernel that you create.
20. Click OK ...... connect the PC to your devices.
21. Flash running process ...................
22. And complete ......
As for how to make images become logo.rle, please refer to the way in this post:
http://forum.xda-developers.com/showthread.php?p=26810498#post26810498
The explanation is quite long, but hopefully can be helpful, especially for those of you who are new to this.
Thanks to: Xda-developers
dooMLord for FTF Creator and unpack the kernel
Bin4ry & Androxyde for Flashtool
And you all, in xda forum
Click to expand...
Click to collapse
most of it is redundant info, and the op is a little confusing
and my kernel kitchen does it in far less steps & complication
and this should be on themes and apps or general...
this is not development
ItBankRock said:
Sadly I don't have a linux OS, and I'm too lazy to install Ubuntu, is this possible to do it all on Windows 7?
Click to expand...
Click to collapse
Yes, download and install Cygwin.
championswimmer said:
most of it is redundant info, and the op is a little confusing
and my kernel kitchen does it in far less steps & complication
and this should be on themes and apps or general...
this is not development
Click to expand...
Click to collapse
No need to mess around with it, a better job would be the best, be the best developer. Congratulations creative the better. Best wishes. Share the beauty, life is a give and accept each other, cheering for xda developers.
Apif Fuloh said:
Hi Guys ...
For those of you who want to change the logo of your android phone when turned on, it should change the logo on the kernel you are using, with your own logo, I will try to help explain how a simple and more detailed. If you can not do it any other way. Mugkin this way can help you. Tools needed:
- Linuk + Perl
- Windows
- A little patient and creative.
Ok! Go ...............
1. Prepare to be in exstack Kernel. You must open a pack kernel first. "DooMLord" has made the tool easy to us doing that, this tool will work in linuk.
Download the device see here:
+ Unpack-kernelsin:
http://forum.xda-developers.com/showthread.php?t=1262656
+ Kernel.sin-and-FTF-creator-v1.0:
http://forum.xda-developers.com/showthread.php?t=1363460
Run your Linuk ....
Save-kernelsin.pl and unpack the kernel will be open, the folder "HOME" on your linuk.
Call the command prompt, then type:
. / Unpack-kernelsin.pl kernel.sin
or use the command
perl unpack-kernelsin.pl kernel.sin
It will make:
- Folder-ramdisk kernel.sin
- Kernel.sin-ramdisk.cpio.gz
- Kernel.sin-kernel
- Kernel.sin-header
Delete the file "kernel.sin-ramdisk.cpio.gz" and file "kernel.sin-header".
Open the folder "kernel.sin-ramdisk",
Please edit or replace your "logo.rle" in the folder "kernel.sin-ramdisk" according to your desire. When finished editing "logo.rle", then do to repack folder "kernel.sin-ramdisk", by way of
Typing commands at the command prompt:
$ Cd kernel.sin-ramdisk
find. | Cpio-o-H newc | gzip> .. / newramdisk.cpio.gz
This will result in "newramdisk.cpio.gz"
2. Now we take the file "kernel.sin-kernel" and "newramdisk.cpio.gz". Save and make sure that both files in one folder.
3. Now you fire up your windows, preferably on Win-xp.
4. Open the folder kernel.sin-and-FTF-creator for your mobile
5. Enter "kernel.sin-kernel" and "kernel.sin-ramdisk.cpio.gz" into folder-and-FTF kernel.sin-creator.
6. Make sure Java is installed on your windows? or if not, you can follow this step.
7. On BUILD-IT.BAT right click and click edit, in order to be as follows:
echo Manifest-Version: 1.0 > manifest.mf
echo device: X10 >> manifest.mf
echo branding: dooMkernel -v06-BootManager-v1.4 >> manifest.mf
echo Created-By: dooMkernel >> manifest.mf
echo version: 2.3.3 >> manifest.mf
ren kernel.jar X10_2.3.3_dooMkernel-v06-BootManager-v1.4.ftf
8. Remove the line
del manifest.mf
del kernel.sin
save and reflace to BUILD-IT.BAT
9. In the folder-and-FTF kernel.sin-creator instead of the name "kernel.sin-kernel" to "image" and rename "-ramdisk.cpio.gz kernel.sin" to "ramdisk"
*NOTE!!
[Make sure you have change the file name correctly, because if not kernel.sin corupt.
If you have a problem in changing the name, street and do this:
How to Rename File Extensions:
Renaming File Extensions can be very handy when trying to convert one file name to another. There are many programs on the web that can help you do this. But are you aware that windows operating systems can do this for you? Below are instructions on how to do so.
Go to Start
Control Panel
Folder Options
Click on the 'View' Tab
Then simply uncheck 'Hide extensions for known file types'.
Then click Apply
Finally click Ok
Now you will be able to change file extensions, such as .JPG to .jpg.]
10. Then Double-BUILD-IT.BAT then ENTER
11. It generates two files: "kernel.sin" and "MANIFEST.MF"
12. Next create a save file folder "kernel.sin and loader.sin to the folder.
13. Now run Flashtool
14. Click Advanced and select Bundle Creation
15. In the Select source folder, select the folder where you save the file and loader.sin kernel.sin
16. on the choice Devices customize your devices, adjust the version of ROM version, the choice of content with brand Branding your devices.
17. Move all the contents of the folder content list to the Firmware
18. Click OK
19. Click Flash
20. Select the kernel that you create.
21. Click OK ...... connect the PC to your devices.
21. Flash running process ...................
22. And complete ......
As for how to make images become logo.rle, please refer to the way in this post:
http://forum.xda-developers.com/showthread.php?p=26810498#post26810498
The explanation is quite long, but hopefully can be helpful, especially for those of you who are new to this.
Thanks to: Xda-developers
dooMLord for FTF Creator and unpack the kernel
Bin4ry & Androxyde for Flashtool
And you all, in xda forum
Click to expand...
Click to collapse
Hey brother
Would you please help me on this :
http://forum.xda-developers.com/showthread.php?t=1988759
TIA
for windows users these will help:
http://forum.xda-developers.com/showthread.php?t=1090217
http://forum.xda-developers.com/showthread.php?t=1140406
Can't exactly remember how I did and if I used Cygwin or not back in those days but I'm pretty sure I used these two threads for tools & info
riginal said:
for windows users these will help:
http://forum.xda-developers.com/showthread.php?t=1090217
http://forum.xda-developers.com/showthread.php?t=1140406
Can't exactly remember how I did and if I used Cygwin or not back in those days but I'm pretty sure I used these two threads for tools & info
Click to expand...
Click to collapse
Thanks a lot brother :good:
Very usefull info, sorry i just used my last "thank"
for today. Will come back later.
Thanks
Darco
Follow thread http://forum.xda-developers.com/showthread.php?t=2173465
First of all , I'm not responsible for any damage..
Of course that's a rough explanation(i really need to hit the bed) but I hope you get the idea and someone will create more clearer and friendly instruction/guide/how-to/whatever.
When flashing L9 , LG App extracts files into C:\ProgramData\LGMOBILEAX\Phone ,
LGP769_AP[6].bin (contains /system partition which includes hdcp.sh) and that can be easly modified(image) and replaced during flashing process.
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push rooting.sh /data/local/tmp/
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/rooting.sh
Follow thread http://forum.xda-developers.com/showthread.php?t=2173465
Downloading 10g kdz now. Will post back after I try to work this out. Thanks alot dude.
@lelus,
I am old dos buzz, so looking at the hexediting done by you in the BIN file, I can say that I am getting some hints.
You are suggesting to quietly replace the BIN file, in the middle of flashing KDZ file (when it is extracted to following folder), right?
C:\ProgramData\LGMOBILEAX\Phone\LGP769_AP[6].bin
The question is at which point the BIN file is to be changed? I still am confused with the sequence of BIN file replacement, scripts and files pushed via ADB. When these procedures are to be done? before flashing or after flashing?
I get hint that, you have modified BIN file to bypass the script file "hdcp.sh" which is used by LG Tool while flashing and instead of that, you are instructing to push+execute modified script "/data/local/tmp/rooting.sh". This new script is added in the beginning of BIN file, does that mean it will be executed everytime we reboot the phone? I may be wrong, just wanna clarify.
I dont have P769 device (good for me ), else I would have try that by now.
You can push the files and set permissions.
Flash your phone once to copy LGP769_AP[6].bin (it goes up to [10] and takes some time to extract the files, there should be enough time) from C:\ProgramData\LGMOBILEAX\Phone\ to some location.
Modify LGP769_AP[6].bin with a hex editor
Flash you phone once again,just like before you'll see lg flash tool decompressing files into C:\ProgramData\LGMOBILEAX\Phone\, when you see it done with LGP769_AP[6].bin copy/replace original with modded file, like before there should be enough time for it. Phone should be rooted after reboot.
hdcp.sh is setuid root and is executed at boot
Re: root p769 v10g and possibly other variants
Im very new to rooting. I've only rooted one phone(lg optimus p509). I now have my fancy new p769 and want some superuser action. I've been doing a lot of reading, and frankly, im worried about bricking or screwing up my new phone! When the more indepth description of your new found genius is released, could you please include details on exactly how to keep my phone safe and unbricked..THANKS!
Sent from my LG-P769 using xda premium
matts0807 said:
Im very new to rooting. I've only rooted one phone(lg optimus p509). I now have my fancy new p769 and want some superuser action. I've been doing a lot of reading, and frankly, im worried about bricking or screwing up my new phone! When the more indepth description of your new found genius is released, could you please include details on exactly how to keep my phone safe and unbricked..THANKS!
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
As you say you are very new, I advice do not try this method at the moment. its very serious and you may brick your phone.
OK. My phone now rooted. But I only get root in adb shell only. Other root required app in phone don't popup Superuser dialog. My app cannot gain root access even I set "Automatic Response" to "Allow". Any Idea?
My phone firmware is p768f V10D, hdcp.sh is in LGP768_AP[5].bin. For other model I think your method should work if you can find proper file to edit (with hex edit).
Ha. Finally work. I replace su and Superuser from their website (After trial and error I don't know what the problem at first). I'm not sure if improper edit .bin file will brick your phone. So wait for some dev to confirm it. If you're not familiar with Hex editor I don't suggest you do this for now.
This may make me sound stupid, but could someone please post a clear set of directions to follow for this method. I think I understand it, but this is my only phone at the moment, and I don't want to screw it up because I swapped up a couple of steps.
For people who want to root LG L9 ICS Phone, please follow this guide http://forum.xda-developers.com/showthread.php?t=2173465
The method in this thread lack some steps to clean out rooting staff and script
For those who interest, below are the steps I did to root my phone from Lelus post info.
*** Please read it carefully and understand every step before you try. I cannot help you if you brick your phone. And please note that I'm not a android dev and these steps work for Lelus P769 10G and my P768f 10D. It should work in all variants but I'm not guarantee. ***
0. Find your KDZ at http://forum.xda-developers.com/showthread.php?t=2107971
1. Manually extract my kdz with LGExtract 0.2.1 from http://forum.xda-developers.com/showthread.php?t=1566532
2. Copy kdz (my file is V10D_00.kdz) and LGExtract.exe to C:\root\ , In command prompt just run
C:\root>LGExtract.exe -kdz V10D_00.kdz
3. You got V10D_00.cab
4. Extract cab with 7z or other zip program that can handle .cab (Google for it if you don't have it yet.) you got 2 files. LGP768.dll and V10D.wdb
5. Extract wdb with following command
C:\root>LGExtract.exe -wdb V10D.wdb LGP768.dll
*** don't forget my model is P768, you should change it to match the file you got ***
6. You'll found extracted files in BIN directory. After this step use your favorite Hex edit to search for hdcp.sh . I found it in LGP768_AP[5].bin. If you copy text from hex edit it look like following
# hdcp.sh
#
# [email protected], [email protected] , [email protected]
#
# HDCP sh file
#!/system/bin/sh
if ls /persist/mhl/key.bin ; then
echo "alreay exist" > /data/mhl.log
/system/xbin/hdcp-init 1 3 >> /data/mhl.log
echo "step 1 : hdcp on" >> /data/mhl.log
else
if ls /persist/en_hdcp.bin ; then
rm /persist/en_hdcp.bin
fi
echo "not exist" > /data/mhl.log
fi
7. In your hex editor, try to edit that file to following
#!/system/bin/sh
/data/local/tmp/rooting.sh
#.com , [email protected]
#
# HDCP sh file
#!/system/bin/sh
if ls /persist/mhl/key.bin ; then
echo "alreay exist" > /data/mhl.log
/system/xbin/hdcp-init 1 3 >> /data/mhl.log
echo "step 1 : hdcp on" >> /data/mhl.log
else
if ls /persist/en_hdcp.bin ; then
rm /persist/en_hdcp.bin
fi
echo "not exist" > /data/mhl.log
fi
*** for those who not familiar with Hex edit you must edit both left (HEX) and right side (TEXT) of editor because some characters is not on keyboard (ex. ENTER, just type 0a in left side editor to make ENTER key).
8. Trial and error until your copy text look like code above (you can copy your edited text from hex editor to text editor to examine it). Then save your file.
9. Next step is download all required file from Lelus link (or from my root.7z) and place them in C:\root
10. In command prompt run
cd C:\root
adb push su /data/local/tmp/
adb push busybox /data/local/tmp/
adb push Superuser.apk /data/local/tmp/
adb push rooting.sh /data/local/tmp/
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/rooting.sh
*** You can use adb.exe from http://forum.xda-developers.com/showthread.php?t=2085344 thread if you don't install android delveloper tools
11. All files should upload to your phone. After this step try to flash your normal unextracted kdz. You should open C:\ProgramData\LGMOBILEAX\Phone while flashing your rom. After kdz flash program show about 8% progress you should see that there are extract .bin files in that directory. Just quickly copy your edited .bin file (only the file that contain hdcp.sh script) and replace extracted file with it. *** you should wait for flash program to finish extract your file before replace it. ***
Read about how to flash your phone at http://forum.xda-developers.com/showthread.php?t=2085344
12. Done. You phone reboot with Superuser app install. If you have any problem like me that Superuser app don't popup to ask permission, please download latest version from http://androidsu.com/superuser/. I also upload updated files in root.7z below.
13. From Lelus' suggestion : After rooting I would probably suggest
adb shell rm /data/local/tmp/rooting.sh
adb shell touch /data/local/tmp/rooting.sh
adb shell chmod 755 /data/local/tmp/rooting.sh
Thanks Lelus for sharing this, :good:
Edit : Add updated Su, Superuser, LGExtract.exe, hex editor image and rooting.sh
Good one artit.
Do you think all LGP768_AP[5].bin (or other variants) are the same file (so we can uploaded a modified one and everyone can use it)?
Would this be a universal way of rooting all LG phone?
Thank You Lelus!
If this works everyone should click the "Thanks" button on Lelus' post.
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
chicguy said:
Good one artit.
Do you think all LGP768_AP[5].bin (or other variants) are the same file (so we can uploaded a modified one and everyone can use it)?
Would this be a universal way of rooting all LG phone?
Click to expand...
Click to collapse
No. All bin files will be different since it holds the partitions and files that are loaded on the devices.
What I means is within the same variants, would it be the same kdz file downloaded? Then we can upload one bin file corresponding to each kdz file?
artit said:
1. Manually extract my kdz with LGExtract 0.2.1 from http://forum.xda-developers.com/showthread.php?t=1566532
2. Copy kdz (my file is V10D_00.kdz) and LGExtract.exe to C:\root\ , In command prompt just run
C:\root>LGExtract.exe -kdz V10D_00.kdz
3. You got V10D_00.cab
4. Extract cab with 7z or other zip program that can handle .cab (Google for it if you don't have it yet.) you got 2 files. LGP768.dll and V10D.wdb
5. Extract wdb with following command
C:\root>LGExtract.exe -wdb V10D.wdb LGP768.dll
*** don't forget my model is P768, you should change it to match the file you got ***
6. You'll found extracted files in BIN directory. After this step use your favorite Hex edit to search for hdcp.sh . I found it in LGP768_AP[5].bin. If you copy text from hex edit it look like following
Click to expand...
Click to collapse
Welldone! Artit! Thanks a lot.
For this same above process I have made a quick and small batch file of KDZ extraction tool and it keeps LGP768_AP
[*].bin files in single folder for further use.
By the way, when I looked for hdcp.sh in P760V10I, I found hdcp.sh in LGP760_AP[6].bin exactly as mentioned by Lelus. It seems the location of this text is different in BIN file and when extracting it goes to any piece of BINs, not always in 6th piece.
EDIT: Are you using Offline Flash method? Or online?
chicguy said:
What I means is within the same variants, would it be the same kdz file downloaded? Then we can upload one bin file corresponding to each kdz file?
Click to expand...
Click to collapse
I do not know.
I have modified .bin files for 11A and 10G on my home pc. I will upload them when I get home later if no one has already.
rooted
Thanks. Now i got P769bk us tmobile rooted.
Hash editor each hash key must match in same place. sd card removal helped.
Uploaded the V10g modded binary for P769. MD5 checksum included, but I forgot to change the directory in the file that checks it (but you can change it).
filedropper[dot]com/lgp769v10g-bin
gigasize[dot]com/get/t23b42m76yc
MD5: c2cbf3997a9ab7181c71c75d697db6f5
Where is the www[dot]zip file for the OFFLINE FOTA method of flashing (/showthread.php?t=2085344)?
EDIT: Please disregard this post. This was a result of a corrupted download. shttps.zip will include the www directory.
V11a rooted as well!
Hi,
I've backup a few apps from my Nexus 5 (Unrooted),
I've copied the .ab file to my PC and I wondered how can I extract it to edit some file and then repack it again.
I've already tried to extract it using DroidExplorer but I'm getting an un-openable tar file.
Can someone please point me how to can I do it right? and how can I repack it again,
Thanks in advance!
Gilco:good:
There is a sweet guide here
UltraWelfare said:
There is a sweet guide here
Click to expand...
Click to collapse
Thanks man, I tried but I get an error while trying to extract the tar file,
also I saw this warning at the end of the guide:
Warning about Helium (Carbon): helium backups are just android adb backups that are not compressed with Java Deflater. It means they were created with the option static final boolean COMPRESS_FULL_BACKUPS = false.
A normal adb restore should work.
see log from first step:
C:\Users\Gil\Desktop\BandR>java -jar abe.jar unpack com.gameinsight.airport.ab A
C.tar
Strong AES encryption enabled
Magic: ANDROID BACKUP
Version: 1
Compressed: 1
Algorithm: none
20664320 bytes read
gilc8 said:
Thanks man, I tried but I get an error while trying to extract the tar file,
also I saw this warning at the end of the guide: ...
Click to expand...
Click to collapse
Hi all, I play a bit with the conversion from Helium backups. Here is the utility:
xaos.ic.cz/Helium_ab2tar.zip . Still don't know what are the last four bytes in the Helium .ab file. Is that some checksum or what? Anyone knows?
xaos.cz said:
Hi all, I play a bit with the conversion from Helium backups. Here is the utility:
xaos.ic.cz/Helium_ab2tar.zip . Still don't know what are the last four bytes in the Helium .ab file. Is that some checksum or what? Anyone knows?
Click to expand...
Click to collapse
Thank you so much! It's working. I was able to extract my (unencrypted) Helium backup. Did you publish the code somewhere else? Here's a Makefile in case someone wants to build it for Linux. (Just remove .txt before running make or make extract)
Archived utility on Github
Hey everyone,
since the original utility has vanished and is somewhat hard to find, I've archived it at Github for convenience: github.com/floe/helium_ab2tar
If the original author wishes, I can transfer the repo to their ownership.
Best, Floe
floemuc said:
Hey everyone,
since the original utility has vanished and is somewhat hard to find, I've archived it at Github for convenience: github.com/floe/helium_ab2tar
If the original author wishes, I can transfer the repo to their ownership.
Best, Floe
Click to expand...
Click to collapse
Hi, the "helium_ab2tar" finally helped me. Good work!
I was running Win7 and didn't have any C compiler installed, so here is what I found:
• from the link above, extract helium_ab2tar-master.zip to a new directory
• from http://gnuwin32.sourceforge.net/packages/make.htm download Binaries and Dependencies and extract files make.exe, libintl3.dll, libiconv2.dll to your helium_ab2tar-master directory
• from https://bellard.org/tcc/ download a recent TinyCC build and extract the whole zip into your helium_ab2tar-master directory
• edit the makefile and change "CC=gcc" to "CC=tcc\tcc.exe"
• change "-o ab2tar_cut" to "-o ab2tar_cut.exe", "-o ab2tar_corr" to "-o ab2tar_corr.exe", "-o tar2ab_cut" to "-o tar2ab_cut.exe", "-o tar2ab_corr" to "-o tar2ab_corr.exe"
• finally run make.exe
How to use:
ab2tar_cut [.ab file] [temporary file]
ab2tar_corr [temporary file] [.tar file]
Thanks Commander!
It doesn't work for me =(
That's what I'm getting while trying to start it thru terminal
make: *** No targets specified and no makefile found. Stop.
download https://github.com/floe/helium_ab2tar, unzip, run make.exe from helium_ab2tar-master folder
aIecxs said:
download "https://github.com/floe/helium_ab2tar"]https://github.com/floe/helium_ab2tar, unzip, run make.exe from helium_ab2tar-master folder
Click to expand...
Click to collapse
there is no such file as make.exe.
of course, you must follow the steps in Post #7
or use linux. you can use Unetbootin and install Xubuntu to usb flash drive
aIecxs said:
of course, you must follow the steps in Post #7
or use linux. you can use Unetbootin and install Xubuntu to usb flash drive
Click to expand...
Click to collapse
I did so and it gives me another error
Code:
tcc\tcc.exe ab2tar_cut.c -o ab2tar_cut.exe
process_begin: CreateProcess(NULL, tcc\tcc.exe ab2tar_cut.c -o ab2tar_cut.exe, ...) failed.
make (e=2): The system cannot find the file specified.
make: *** [ab2tar_cut] Error 2
try with full path in makefile for example CC="C:\Users\Admin\Downloads\helium_ab2tar-master\tcc\tcc.exe" (path to tcc.exe)
aIecxs said:
try with full path in makefile for example CC="C:\Users\Admin\Downloads\helium_ab2tar-master\tcc\tcc.exe" (path to tcc.exe)
Click to expand...
Click to collapse
ok it seems to work,
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master> C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\make.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe ab2tar_cut.c -o ab2tar_cut.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe ab2tar_corr.c -o ab2tar_corr.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe tar2ab_corr.c -o tar2ab_corr.exe
C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master\tcc.exe tar2ab_cut.c -o tar2ab_cut.exe
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master>
Click to expand...
Click to collapse
what's next ?
---------- Post added at 01:52 PM ---------- Previous post was at 01:47 PM ----------
aIecxs said:
try with full path in makefile for example CC="C:\Users\Admin\Downloads\helium_ab2tar-master\tcc\tcc.exe" (path to tcc.exe)
Click to expand...
Click to collapse
what should be instead of [temporary file] ?
backup.ab.tmp (or any other name)
aIecxs said:
backup.ab.tmp (or any other name)
Click to expand...
Click to collapse
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master>
>> ab2tar_cut backup.ab backup.ab.tmp
ab2tar_cut : The term 'ab2tar_cut' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:2 char:1
+ ab2tar_cut backup.ab backup.ab.tmp
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (ab2tar_cut:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command ab2tar_cut was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\ab2tar_cut". See "get-help about_Command_Precedence" for more details.
PS C:\Users\danbe\Downloads\folders\helium_ab2tar-master\helium_ab2tar-master>
Sorry I was using powershell for it, it doesn't work in PS but it works in CMD
Hello, I am feeling as dumb as a caveman right now because I could not figure out how to decompress and .ab file created with an old version of Helium which pretty much screw me over this.
I'm pretty much an illiterate with command lines in general. I tried cygwin but can't manage to find the right command combo, also android backup extractor doesn't even work despite I've installed the Java SE SDK etc (running Win10 x64). Can someone tell me step by step how I can decompress this hellish .ab file once for all? Thank you in advance.
P.s.= And yes, I also tryied using the method described on these last 2 pages and I get this:
C:\Users\Dingo Dash>"C:\Users\Dingo Dash\Desktop\helium_ab2tar-master\bin\make.exe" ab2tar_cut "C:\Users\Dingo Dash\Downloads\com.koushikdutta.backup\SM-G900F - 353687063301086\backup.ab" xxx.tmp
make: *** No rule to make target `ab2tar_cut'. Stop.
Click to expand...
Click to collapse
- download and edit makefile from post #5
- compile the binaries (.exe files)
- unpack backup + convert to tar
- unpack tar file
aIecxs said:
- download and edit makefile from post #5
- compile the binaries (.exe files)
- unpack backup + convert to tar
- unpack tar file
Click to expand...
Click to collapse
Thank you but I wanted to know what I was doing wrong on the prompt because I had already compiled the binaries aka followed the whole procedure.
Anyway, I managed to extract the whole damn file on another device. I don't have an explaination of why helium behaved this way but it actually worked on a more recent device instead of the original one, were the backup was created, also using a 2015 or so old version of the app, which should be the one the file came from.