To compile Unofficial CyanogenMod for Pantech Flex P8010 (oscar), following the next steps.
1º - Prepare the Build Environment:
This step is based on the following tutorial: [Tutorial] Compile JB on Ubuntu - Thanks dastin1015.
A) Install Python and Git:
Code:
$ sudo apt-get install python
Code:
$ sudo apt-get install git-core
B) Install Android SDK:
- Download the SDK here: http://developer.android.com/sdk/index.html
- Extract the SDK and place it in your home directory.
- I renamed my SDK to android-sdk to make it easier to navigate to.
- Go to your home folder, press Ctrl+H to show hidden files, and open up your .bashrc file.
- Add these lines at the bottom of the file:
Code:
# Android tools
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin
- Find your .profile file and add this at the bottom of the file:
Code:
PATH="$HOME/android-sdk/tools:$HOME/android-sdk/platform-tools:$PATH"
You have now successfully installed the Android SDK.
To check for updates issue this into your terminal:
Code:
$ android
C) Install required packages:
Building on Ubuntu 10.10/11.10:
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils xsltproc
On Ubuntu 10.10:
Code:
$ sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
On Ubuntu 11.10:
Code:
$ sudo apt-get install libx11-dev:i386
On newer versions of Ubuntu such as 11.10 you may need to do the following:
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so
Building on Ubuntu 12.04/10:
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 openjdk-6-jdk tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386 \
pngcrush optipng
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
D) Install Oracle Java 6:
To install Oracle Java 6 in Ubuntu via PPA: http://www.webupd8.org/2012/11/oracle-sun-java-6-installer-available.html
Code:
$ sudo add-apt-repository ppa:webupd8team/java
$ sudo apt-get update
$ sudo apt-get install oracle-java6-installer
After the installation, check the version of java, using the command:
Code:
$ java -version
Output console:
Code:
java version "1.6.0_38"
Java(TM) SE Runtime Environment (build 1.6.0_38-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.13-b02, mixed mode)
Note: The installed version of java, may have been updated, but should be kept in version 1.6.XX
Verify the symlinks:
Code:
$ ls -la /etc/alternatives/java* && ls -la /etc/alternatives/jar
Output console:
Code:
lrwxrwxrwx 1 root root 39 ene 17 08:02 /etc/alternatives/java -> /usr/lib/jvm/java-6-oracle/jre/bin/java
lrwxrwxrwx 1 root root 45 ene 17 08:02 /etc/alternatives/java.1.gz -> /usr/lib/jvm/java-6-oracle/man/man1/java.1.gz
lrwxrwxrwx 1 root root 36 ene 17 08:02 /etc/alternatives/javac -> /usr/lib/jvm/java-6-oracle/bin/javac
lrwxrwxrwx 1 root root 46 ene 17 08:02 /etc/alternatives/javac.1.gz -> /usr/lib/jvm/java-6-oracle/man/man1/javac.1.gz
lrwxrwxrwx 1 root root 38 ene 17 08:02 /etc/alternatives/javadoc -> /usr/lib/jvm/java-6-oracle/bin/javadoc
lrwxrwxrwx 1 root root 48 ene 17 08:02 /etc/alternatives/javadoc.1.gz -> /usr/lib/jvm/java-6-oracle/man/man1/javadoc.1.gz
lrwxrwxrwx 1 root root 36 ene 17 08:02 /etc/alternatives/javah -> /usr/lib/jvm/java-6-oracle/bin/javah
lrwxrwxrwx 1 root root 46 ene 17 08:02 /etc/alternatives/javah.1.gz -> /usr/lib/jvm/java-6-oracle/man/man1/javah.1.gz
lrwxrwxrwx 1 root root 36 ene 17 08:02 /etc/alternatives/javap -> /usr/lib/jvm/java-6-oracle/bin/javap
lrwxrwxrwx 1 root root 46 ene 17 08:02 /etc/alternatives/javap.1.gz -> /usr/lib/jvm/java-6-oracle/man/man1/javap.1.gz
lrwxrwxrwx 1 root root 42 ene 17 08:02 /etc/alternatives/java_vm -> /usr/lib/jvm/java-6-oracle/jre/bin/java_vm
lrwxrwxrwx 1 root root 41 ene 17 08:02 /etc/alternatives/javaws -> /usr/lib/jvm/java-6-oracle/jre/bin/javaws
lrwxrwxrwx 1 root root 47 ene 17 08:02 /etc/alternatives/javaws.1.gz -> /usr/lib/jvm/java-6-oracle/man/man1/javaws.1.gz
lrwxrwxrwx 1 root root 34 ene 17 08:02 /etc/alternatives/jar -> /usr/lib/jvm/java-6-oracle/bin/jar
E) Configure your USB:
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
Save the file and close it and then issue this command:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
2º - Create the Directories
You will need to set up some directories in your build environment.
Note: For the next steps, I modified the installation path sources, because in this way you can include other repositories (CAF, AOSP, etc ...).
To create them:
Code:
mkdir -p ~/bin
mkdir -p ~/android
mkdir -p ~/android/cyanogenmod
mkdir -p ~/android/cyanogenmod/jellybean
3º - Install the repo:
Enter the following to download make executable the "repo" binary:
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Note: You may need to reboot for these changes to take effect.
4º - Install the CM10 Repository:
Now enter the following to initialize the CyanogenMod repository:
Code:
cd ~/android/cyanogenmod/jellybean/
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
repo sync -j16
5º - Obtain the oscar device tree:
Create/Edit a file with the name roomservice.xml in the ".repo/local_manifests/" directory. To see this directory, you have to press Ctrl-H in your file manager.
Code:
mkdir -p ~/android/cyanogenmod/jellybean/.repo/local_manifests/
gedit ~/android/cyanogenmod/jellybean/.repo/local_manifests/roomservice.xml
Add these lines:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="mifl/android_device_pantech_oscar" path="device/pantech/oscar" remote="github" revision="jellybean" />
<project name="mifl/android_device_pantech_qcom-common" path="device/pantech/qcom-common" remote="github" revision="jellybean" />
<project name="mifl/android_device_pantech_msm8960-common" path="device/pantech/msm8960-common" remote="github" revision="jellybean" />
<project name="mifl/android_kernel_pantech_p8010" path="kernel/pantech/p8010" remote="github" revision="jellybean" />
</manifest>
Synchronize the repositories:
Code:
cd ~/android/cyanogenmod/jellybean/
repo sync
6º - Copy proprietary files:
Option 1:
To compile Pantech oscar, connect the device to the computer and ensure that ADB is working properly.
Code:
cd ~/android/cyanogenmod/jellybean/device/pantech/oscar
./extract-files.sh
Option 2:
You can also include the repository with the necessary files for compilation:
Code:
gedit ~/android/cyanogenmod/jellybean/.repo/local_manifests/roomservice.xml
Add this line:
Code:
<project name="mifl/android_vendor_pantech_oscar" path="vendor/pantech/oscar" remote="github" revision="jellybean" />
Synchronize the repositories:
Code:
cd ~/android/cyanogenmod/jellybean/
repo sync
7º - Download RomManager:
Note: This only needs to be done when an update to RomManager is released. If you are-up-to date, you may skip to Building CyanogenMod.
Download RomManager which is needed by the build:
Code:
cd ~/android/cyanogenmod/jellybean
./vendor/cm/get-prebuilts
8º - Building CyanogenMod:
First, check for updates in the source:
Code:
cd ~/android/cyanogenmod/jellybean/
repo sync
Now, the environment must be configured to build and the ROM compiled.
Code:
. build/envsetup.sh && brunch oscar
9º - Compiled files:
Files generated in the compilation are in the /out directory, the build file is:
~/android/cyanogenmod/jellybean/out/target/product/oscar/cm-10-XXXXX-UNOFFICIAL-oscar.zip
-------------------------------
I hope that more users try to compile the ROM, and report bugs they find. Any help is greatly appreciated.
Greetings.
**Reserved for future updates**
**Reserved for future updates**
**Reserved for future updates**
I followed your instructions to the lleter, and this is what i get.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/oscar/cm.mk]]: "device/*/oscar/cm.mk" does not exist.
Device oscar not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/Cyanogen
Repository for oscar not found in the CyanogenMod Github repository list. If this is in error, you may need to manuato your local_manifests/roomservice.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/oscar/cm.mk]]: "device/*/oscar/cm.mk" does not exist.
** Don't have a product spec for: 'cm_oscar'
** Do you have the right repo manifest?
superbart007 said:
I followed your instructions to the lleter, and this is what i get.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/oscar/cm.mk]]: "device/*/oscar/cm.mk" does not exist.
Device oscar not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/Cyanogen
Repository for oscar not found in the CyanogenMod Github repository list. If this is in error, you may need to manuato your local_manifests/roomservice.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/oscar/cm.mk]]: "device/*/oscar/cm.mk" does not exist.
** Don't have a product spec for: 'cm_oscar'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
Sorry:
There is an error in the wording of post. The kernel repository was wrong, must be changed p9070 for P8010.
Code:
<project name="mifl/android_kernel_pantech_p8010" path="kernel/pantech/p8010" remote="github" revision="jellybean" />
The rest of the repositories are well, and have been updated today and compiled fine.
----------------------------------------------------------------------------------------------------------------
Update:
In CyanogenMod Source, ~/.repo/local_manifest.xml file has been changed to ~/.repo/local_manifests/roomservice.xml
To adapt to change into the your "~/.repo" dir, must create the dir "local_manifests", rename the file local_manifest.xml to roomservice.xml, and move it into the new dir.
----------------------------------------------------------------------------------------------------------------
Greetings.
Ok tried our again still no joy. But also your instructions never mention how the dir pantech, and oscar are made, and when i goto build it say it can't find the mk file in the /devices/pantech/oscar.
Sent from my PantechP8010 using xda app-developers app
superbart007 said:
Ok tried our again still no joy. But also your instructions never mention how the dir pantech, and oscar are made, and when i goto build it say it can't find the mk file in the /devices/pantech/oscar.
Sent from my PantechP8010 using xda app-developers app
Click to expand...
Click to collapse
Projects in the file roomservice.xml have this structure:
Code:
<project name="mifl/android_device_pantech_oscar" path="device/pantech/oscar" remote="github" revision="jellybean" />
Each of the fields is:
name: name of the repository.
path: directory where the files are placed.
remote: git server
Revision: version (branch) to synchronize.
Each time you add a line to your roomservice.xml, you must synchronize the repositories:
Code:
cd ~/android/cyanogenmod/jellybean/
repo sync
Greetings.
Ok thank you, I'm new at doing this, and I'm trying to learn.
Sent from my PantechP8010 using xda app-developers app
Berry does this compile include gapps pu or do i need to use a jb one from goo.im
Sent from my PantechP8010 using xda app-developers app
superbart007 said:
Berry does this compile include gapps pu or do i need to use a jb one from goo.im
Sent from my PantechP8010 using xda app-developers app
Click to expand...
Click to collapse
You have to download Google Apps and flash from CWM Recovery.
Greetings.
Ok cool thanks
Sent from my PantechP8010 using xda app-developers app
Refactor to use repo msm8960-common
Changes in the repositories structure:
The repositories are needed:
Code:
android_device_pantech_oscar
| - android_device_pantech_qcom-common
| - android_device_pantech_msm8960-common
| - android_kernel_pantech_p8010
| - android_vendor_pantech_oscar
To complete this refactoring, you need to add a repository to your file: ~/.repo/local_manifests/roomservice.xml:
Code:
<project name="mifl/android_device_pantech_msm8960-common" path="device/pantech/msm8960-common" remote="github" revision="jellybean" />
And synchronize:
Code:
repo sync
Greetings.
mifl said:
Changes in the repositories structure:
The repositories are needed:
Code:
android_device_pantech_oscar
| - android_device_pantech_qcom-common
| - android_device_pantech_msm8960-common
| - android_kernel_pantech_p8010
| - android_vendor_pantech_oscar
To complete this refactoring, you need to add a repository to your file: ~/.repo/local_manifest/roomservice.xml:
Code:
<project name="mifl/android_device_pantech_msm8960-common" path="device/pantech/msm8960-common" remote="github" revision="jellybean" />
And synchronize:
Code:
repo sync
Greetings.
Click to expand...
Click to collapse
im getting this error message on step 8
Device oscar not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for oscar not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/oscar/cm.mk]]: "device/*/oscar/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_oscar'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Please help
atadres said:
im getting this error message on step 8
Device oscar not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for oscar not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/oscar/cm.mk]]: "device/*/oscar/cm.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_oscar'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Please help
Click to expand...
Click to collapse
Can you write the contents of your file: ~/.repo/local_manifest/roomservice.xml
Greetings.
mifl said:
Can you write the contents of your file: ~/.repo/local_manifest/roomservice.xml
Greetings.
Click to expand...
Click to collapse
sure heres what it says
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="mifl/android_device_pantech_oscar" path="device/pantech/oscar" remote="github" revision="jellybean" />
<project name="mifl/android_device_pantech_msm8960-common" path="device/pantech/msm8960-common" remote="github" revision="jellybean" />
<project name="mifl/android_device_pantech_qcom-common" path="device/pantech/qcom-common" remote="github" revision="jellybean" />
<project name="mifl/android_kernel_pantech_p8010" path="kernel/pantech/p8010" remote="github" revision="jellybean" />
</manifest>
atadres said:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="mifl/android_device_pantech_oscar" path="device/pantech/oscar" remote="github" revision="jellybean" />
<project name="mifl/android_device_pantech_msm8960-common" path="device/pantech/msm8960-common" remote="github" revision="jellybean" />
<project name="mifl/android_device_pantech_qcom-common" path="device/pantech/qcom-common" remote="github" revision="jellybean" />
<project name="mifl/android_kernel_pantech_p8010" path="kernel/pantech/p8010" remote="github" revision="jellybean" />
</manifest>
Click to expand...
Click to collapse
The file seems fine.
To ensure:
Code:
cp ~/android/cyanogenmod/jellybean/.repo/local_manifests/roomservice.xml ~/android/cyanogenmod/jellybean/.repo/local_manifest.xml
Synchronize the repository:
Code:
repo sync
If synchronizing the repository, you get an error, saying it has duplicate projects, you should delete the file: local_manifest.xml.
Greetings.
Ok got it build with no errors, but it just boot loops at the 1st showing of pantech. It could be that you are using cm10.1(jelly bean), and that there is only ics available for this phone. Could you post the changes to build cm9 and then I could give that a try.
superbart007 said:
Ok got it build with no errors, but it just boot loops at the 1st showing of pantech. It could be that you are using cm10.1(jelly bean), and that there is only ics available for this phone. Could you post the changes to build cm9 and then I could give that a try.
Click to expand...
Click to collapse
Before installing the rom, have you applied?
Wipe data/factory reset;
Wipe cache partition;
Advanced -> Wipe dalvik cache;
Greetings.
Yes wiped every thing.
Sent from my PantechP8010 using xda app-developers app
Hi all folks,
I have some question about the stock android system in this specific box and the format of the dumped partition.
Try to explain, I'm using rkflashtool to interact with the memory of the RK3188
This is the output of the command
rkflashtool r 0 1 | head -n 11
-------------------------------------------------------------------------------------------------
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0
init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](userdata),
[email protected](kpanic),
[email protected](system),
[email protected](user)
-------------------------------------------------------------------------------------------------
I guess the boot partition is something linke that:
+-------+ <--- 0x00019fe0
| boot |
+-------+ <----0x00012000
With this command i'm able to dump the entrie boot partition on my linux box in a file named b00t.img :
rkflashtool r 0x12000 0x8000 > b00t.img
Now, i have find out that with the tool rkunpack (or simply with dd) i'm able to unpack this b00t.img. The output are two file:
b00t.img-raw
b00t.img-symbol
The first file is no more than a gzip compressed data file, I'm able to extract the data in a directory with this command:
gunzip < ../b00t.img-raw | sudo cpio -i --make-directories
Now in this dir I have all the files of the / partition. I can modify for example the /init.rc.
I want to repack the entrie b00t.img in order to flash it again on the device.
NB:
In this thread this guys work at something like my problem...
http://www.freaktab.com/showthread.p...ull=1#post4055
The difference is that they work on a different partition layout, and the rkunpack of dumped boot.img return they only boot.img-raw.
Obviously I've already tried to repack the modified directory in this two ways:
mkcramfs myboot myboot-temp.img
kcrc myboot-temp.img customboot.img
or
find . ! -name "."| sort | cpio -oa -H newc | gzip -n > ../newboot.gz
kcrc newboot.gz customboot.img
Neither of these leads to obtain a file large enough to fit the boot partition on the deivice, that I want fill with:
rkflashtool w 0x12000 0x8000 < modifiedb00t.img
Has anyone ever worked with rk3188? Any idea?
Thanks in advance.
SOLVED!
Look at http://www.freaktab.com/showthread.php?12200-ANDROID!-boot-img-want-to-modify-only-the-ramdisk.
Hi all folks,
I have some question about the stock android system in this specific box and the format of the dumped partition.
Try to explain, I'm using rkflashtool to interact with the memory of the RK3188
This is the output of the command
rkflashtool r 0 1 | head -n 11
-------------------------------------------------------------------------------------------------
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0
init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:
[email protected](misc),
[email protected](kernel),
[email protected](boot),
[email protected](recovery),
[email protected](backup),
[email protected](cache),
[email protected](userdata),
[email protected](kpanic),
[email protected](system),
[email protected](user)
-------------------------------------------------------------------------------------------------
I guess the boot partition is something linke that:
+-------+ <--- 0x00019fe0
| boot |
+-------+ <----0x00012000
With this command i'm able to dump the entrie boot partition on my linux box in a file named b00t.img :
rkflashtool r 0x12000 0x8000 > b00t.img
Now, i have find out that with the tool rkunpack (or simply with dd) i'm able to unpack this b00t.img. The output are two file:
b00t.img-raw
b00t.img-symbol
The first file is no more than a gzip compressed data file, I'm able to extract the data in a directory with this command:
gunzip < ../b00t.img-raw | sudo cpio -i --make-directories
Now in this dir I have all the files of the / partition. I can modify for example the /init.rc.
I want to repack the entrie b00t.img in order to flash it again on the device.
NB:
In this thread these guys work at something like my problem...
http://www.freaktab.com/showthread.p...ull=1#post4055
The difference is that they work on a different partition layout, and the rkunpack of dumped boot.img return they only boot.img-raw.
Obviously I've already tried to repack the modified directory in this two ways:
mkcramfs myboot myboot-temp.img
kcrc myboot-temp.img customboot.img
or
find . ! -name "."| sort | cpio -oa -H newc | gzip -n > ../newboot.gz
kcrc newboot.gz customboot.img
None of these leads to obtain a file large enough to fit the boot partition on the deivice, that I want fill with:
rkflashtool w 0x12000 0x8000 < modifiedb00t.img
Has anyone ever worked with rk3188? Any idea?
Thanks in advance.
Anyone?