Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[HACK] Increase Internal Memory Size to Whatever You Want!

OP Doc_cheilvenerdi.org

31st January 2012, 05:36 AM   |  #51  
Member
Flag mumbai
Thanks Meter: 3
 
94 posts
Join Date:Joined: Oct 2011
More
Arre guys plz tell what software do I use to make this possible on other cells
Plz doc tell me the software our the methods you duds this .... I want to do for fit ...
Software name please to edit boot.img

Sent from my GT-S5570 using xda premium
31st January 2012, 01:27 PM   |  #52  
Doc_cheilvenerdi.org's Avatar
OP Senior Member
Flag Ferrara - Ravenna
Thanks Meter: 346
 
123 posts
Join Date:Joined: Oct 2011
More
Thumbs up [DEV] Increase Internal Memory to Whatever You Want!
HOW I DID IT... The Source...





In this post, and few others, I'm going to explain "step by step", "tool by tool" and "code by code" exactly what I do to tweak a boot image for my Galaxy Mini!


Let's follow together an example: I'm going to tweak the boot image of the 2.3.3 XXKPF Stock ROM.
While downloading it from samfirmware, I set up a minimal working environment.

From here on I'll use a PC with a Linux Gentoo Amd64 No Multilib Chroot32 unstable OS, but everything works with any other distribution (ubuntu, debian, opensuse, etc...). Actually Linux is mandatory for me (on Windows you could try to set up a cygwin environment).

I'll do all the job in a system folder called boot_mod, typing all the commands from the console (...or terminal):
Code:
doc@gandalf ~/boot_mod $
Once downloaded the XXKPF firmware (which is multipackage) I unrar the CODE archive to this folder and extract from it the boot image:
Code:
doc@gandalf ~/boot_mod $ tar xf CODE_S5570XXKPF_CL189639_REV02_user_mid_true.tar.md5 boot.img
doc@gandalf ~/boot_mod $ ls -l
total 212864
-rw-r--r-- 1 doc doc 211589203 Jan 31 09:39 CODE_S5570XXKPF_CL189639_REV02_user_mid_true.tar.md5
-rw-r--r-- 1 doc doc   6377472 May  7  2011 boot.img
doc@gandalf ~/boot_mod $

BACKUP
First af all I prepare the Odin Archive of the original boot image, just to share it later: CODE_S5570XXKPF_boot.tar.md5.
Code:
doc@gandalf ~/boot_mod $ tar -H ustar -c boot.img > CODE_S5570XXKPF_boot.tar
doc@gandalf ~/boot_mod $ md5sum CODE_S5570XXKPF_boot.tar >> CODE_S5570XXKPF_boot.tar 
doc@gandalf ~/boot_mod $ mv CODE_S5570XXKPF_boot.tar CODE_S5570XXKPF_boot.tar.md5
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r-- 1 doc doc   6379579 Jan 31 09:51 CODE_S5570XXKPF_boot.tar.md5
...
doc@gandalf ~/boot_mod $
I prepare it just to restore back from the modded image, without flashing the full firmware from scratch.


SPLIT
Now, using this perl script split_bootimg.pl (downloaded into this folder too... Thanks to William Enck for it) I split the boot image into its components, the kernel and the initial ramdisk.
Code:
doc@gandalf ~/boot_mod $ ./split_bootimg.pl boot.img 
Page size: 4096 (0x00001000)
Kernel size: 3221952 (0x003129c0)
Ramdisk size: 3146572 (0x0030034c)
Second size: 0 (0x00000000)
Board name: 
Command line: 
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r-- 1 doc doc 6377472 May  7  2011 boot.img
-rw-r--r-- 1 doc doc 3221952 Jan 31 09:56 boot.img-kernel
-rw-r--r-- 1 doc doc 3146572 Jan 31 09:56 boot.img-ramdisk.gz
-rwxr-xr-x 1 doc doc    6121 Jan 31 09:44 split_bootimg.pl
...
doc@gandalf ~/boot_mod $
Notice: The perl script must be set executable with the chmod command...


I look at the output for Page size (bold 4096) because I'll need it later to complete the task.

I actually miss a number that I must read from the boot.img binary.
I'll read it with an hexadecimal editor:
Code:
doc@gandalf ~/boot_mod $ hexedit boot.img
...
00000000   41 4E 44 52  4F 49 44 21  C0 29 31 00  00 80 60 13  ANDROID!.)1...`.
00000010   4C 03 30 00  00 00 60 14  00 00 00 00  00 00 50 14  L.0...`.......P.
00000020   00 01 60 13  00 10 00 00  00 00 00 00  00 00 00 00  ..`.............
00000030   00 00 00 00  00 00 00 00  00 00 00 00  00 00 00 00  ................
...
doc@gandalf ~/boot_mod $
I show the first 64 bytes of the file while I need only the bolded and coloured ones...
I read them this way:
Code:
base address = 0x13600000
Anyway I need to check for this only once for any Phone model (I feel that this number will be the same for all these samsung phone models too...).

Before Starting the Real Task I must be sure that I'm able to put back toghether the splitted parts of the boot image...

To do it I need to compile a relevant tool from the AOSP Source Code: mkbootimg. Here is my one for 32bit Linux distributions: mkbootimg.
I download it into the working folder too and set it executable with chmod command...
Code:
doc@gandalf ~/boot_mod $ ./mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --base 0x13600000 --pagesize 4096 -o boot_COPY.img
doc@gandalf ~/boot_mod $
I used the numbers just discovered... eh eh...

Now I'll check the original image and the selfmade one looking for differences... If they differ DON'T GO AHEAD!!! The modded boot image will never work!
Code:
doc@gandalf ~/boot_mod $ diff boot.img boot_COPY.img 
doc@gandalf ~/boot_mod $
If I don't read something like Binary files ... differ everything works... I CAN CREATE boot images on my own!


RAMDISK - FIRST ROUND
Now I create a subfolder where I'll store the initial ramdisk contents:
Code:
doc@gandalf ~/boot_mod $ mkdir ramdisk
doc@gandalf ~/boot_mod $ cd ramdisk
doc@gandalf ~/boot_mod/ramdisk $ gunzip -c ../boot.img-ramdisk.gz | cpio -i
14299 blocks
doc@gandalf ~/boot_mod/ramdisk $
Notice: Mostly I'll work within tha ramdisk subfolder... the following commands must run from there to work!

And here it is! The ramdisk Folder opened:
Code:
doc@gandalf ~/boot_mod/ramdisk $ ls -l
total 744
-rw-r--r-- 1 doc doc  13444 Jan 31 10:17 TASS.rle
drwxrwx--x 2 doc doc   4096 Jan 31 10:17 data
-rw-r--r-- 1 doc doc    118 Jan 31 10:17 default.prop
drwxr-xr-x 2 doc doc   4096 Jan 31 10:17 dev
-rw-r--r-- 1 doc doc 222472 Jan 31 10:17 fsua
-rwxr-x--- 1 doc doc  94380 Jan 31 10:17 init
-rwxr-x--- 1 doc doc   1677 Jan 31 10:17 init.goldfish.rc
-rwxr-x--- 1 doc doc   3048 Jan 31 10:17 init.qcom.post_boot.sh
-rwxr-x--- 1 doc doc   7976 Jan 31 10:17 init.qcom.rc
-rwxr-x--- 1 doc doc   6563 Jan 31 10:17 init.qcom.sh
-rwxr-x--- 1 doc doc  24201 Jan 31 10:17 init.rc
drwxr-xr-x 3 doc doc   4096 Jan 31 10:17 lib
drwxr-xr-x 2 doc doc   4096 Jan 31 10:17 proc
-rw-r--r-- 1 doc doc 331588 Jan 31 10:17 recovery
drwxr-x--- 2 doc doc   4096 Jan 31 10:17 sbin
drwxr-xr-x 2 doc doc   4096 Jan 31 10:17 sys
drwxr-xr-x 2 doc doc   4096 Jan 31 10:17 system
-rw-r--r-- 1 doc doc      0 Jan 31 10:17 ueventd.goldfish.rc
-rw-r--r-- 1 doc doc   5759 Jan 31 10:17 ueventd.rc
doc@gandalf ~/boot_mod/ramdisk $

KERNEL MODULES
Stop working on ramdisk for a while...

Now I must deal with the hardest task of the tweak...

I need to compile two kernel modules for my new modded image...

It seems a simple period, but I need to compile inside Linux for an outside Arm architecture...


I'll explain on a next post how I did it!


...continued in post n. 53...



Quote:
Originally Posted by Krishna parmar

...make this possible on other cells...
...to do for fit ...

Surely it could be possible... I actually did it for Galaxy ACE too, but I don't have the possibility to test the modded images... finally, the kernel for Galaxy Fit, Ace and Mini is pretty the same, so I bet on it!
Last edited by Doc_cheilvenerdi.org; 31st January 2012 at 07:00 PM. Reason: Added Link to Post n. 53
The Following 2 Users Say Thank You to Doc_cheilvenerdi.org For This Useful Post: [ View ]
31st January 2012, 06:55 PM   |  #53  
Doc_cheilvenerdi.org's Avatar
OP Senior Member
Flag Ferrara - Ravenna
Thanks Meter: 346
 
123 posts
Join Date:Joined: Oct 2011
More
Thumbs up [DEV] Increase Internal Memory Size to Whatever You Want!
KERNEL MODULES - FIRST RUN


First of all I setup a cross compiling environment: that is a toolchain used on Linux to create arm executables.
I usually build with the Sourcery CodeBench Lite toolchain, but it's well suited also the one prebuilt inside the AOSP source code...

This time I'll use this one; I find it on my PC starting from this path:
Code:
/home/doc/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/
Notice: I have to download it from the AOSP home page... could take a while...

Others known toolchains are Linaro (actually not working for me) or Gentoo Crossdev arm-vfp-linux-gnueabi (selfmade and my favourite one).

NOTICE: Anyway, from now on, I consider the building environment already up and running!


After downloading the Linux-to-Android toolchain I need the Kernel Source Code.
Starting from Samsung Open Source Release Center I Find my one and several others...

I download and unzip it into
Code:
/home/doc/boot_mod/kernel
So, this is now my working directory:
Code:
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r--  1 doc doc 6377472 May  7  2011 boot.img
-rw-r--r--  1 doc doc 3221952 Jan 31 09:56 boot.img-kernel
-rw-r--r--  1 doc doc 3146572 Jan 31 09:56 boot.img-ramdisk.gz
drwxr-xr-x 24 doc doc    4096 Jan 26  2011 kernel
-rwxr-xr-x  1 doc doc   28614 Jan 31 10:08 mkbootimg
drwxr-xr-x  9 doc doc    4096 Jan 31 10:17 ramdisk
-rwxr-xr-x  1 doc doc    6121 Jan 31 09:44 split_bootimg.pl
...
doc@gandalf ~/boot_mod $
First of all I check for the kernel version, looking the first five lines of its Makefile:
Code:
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 35
EXTRAVERSION = .7
NAME = Yokohama
The Bold Numbers must match the ones read from Settings -> About Phone -> Kernel Version otherwise the modded image will never work!


Now I can edit the Makefile inside the kernel directory (need to do only once!) searching for a line starting with
Code:
CROSS_COMPILE = ...
...changing it to the full path of my toolchain binaries:
Code:
/home/doc/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-

Last (but THE MOST IMPORTANT) I setup the kernel configuration for my phone (need to do only once!):
Code:
doc@gandalf ~/boot_mod/kernel $ make tass_rev02_defconfig

...

#
# configuration written to .config
#
doc@gandalf ~/boot_mod/kernel $
How do I know that?

...with the following command
Code:
doc@gandalf ~/boot_mod/kernel $ make help
I find out all the phone supported by this kernel...
...and there are also beni and cooper ones (that means S5670 and S5830!) and really many many others...


WILL IT WORK?
Now I simply try to compile the default kernel modules:
Code:
doc@gandalf ~/boot_mod/kernel $ make modules

...

  Building modules, stage 2.
  MODPOST 7 modules

...
doc@gandalf ~/boot_mod/kernel $
Wow! I built something!


WHAT NEXT?
In the next post I'll finally tweak the ramdisk and then I'll compile the needed kernel modules suited for the XXKPF firmware!


...continued on post n. 54



IN THE MEANWHILE
Optional... but really usefull!
In the meanwhile I'll compile a single module suited for my own kernel, just to try it for free...
...or just to verifiy that everything works fine!

The master command is this:
Code:
doc@gandalf ~/boot_mod/kernel $ make menuconfig
From the kernel menu I can change any config option for the kernel and related modules... but How do I suit it to my phone kernel?

From Settings -> About Phone -> Kernel version I read
Code:
2.6.35.7-perf-CL561937
root@DELL88 #1
I simply put last string of the first line (-perf-CL561937) inside the kernel menu option

General setup -> Local version - append to kernel release

where i write exactly
Code:
-perf-CL561937

...eh eh... this is the trick that opened to me the kernel doors to my modded image tweaks... (10+)

After that I simply choose, for example, the following option:

File systems -> Network File Systems -> CIFS support

where I should see something like this:
Code:
  < >   ...
  <M>   CIFS support (advanced network filesystem, SMBFS successor)
  [ ]   ...
Notice: <M> means "Module"

Now I exit from the menu saving "my new kernel configuration" and repeat the build command:
Code:
doc@gandalf ~/boot_mod/kernel $ make modules

...

  LD [M]  fs/cifs/cifs.ko
doc@gandalf ~/boot_mod/kernel $
I reduce the size of the module removing unused stuffs (...to save space - I'm not going to debug any module for bugs... I'll simply use them...):
Code:
doc@gandalf ~/boot_mod/kernel $ /home/alberto/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-strip --strip-unneeded fs/cifs/cifs.ko 
doc@gandalf ~/boot_mod/kernel $
(more details about stripping later...)

Now I connect the Phone to the PC and push the compiled module to /data/local using adb:
Code:
doc@gandalf ~/boot_mod/kernel $ adb push fs/cifs/cifs.ko /data/local
3687 KB/s (252908 bytes in 0.066s)
doc@gandalf ~/boot_mod/kernel $

...and finally, using "adb shell" (my phone needs to be rooted) I try to insert the module into my running kernel:
Code:
doc@gandalf ~/boot_mod/kernel $ adb shell
$ su
# lsmod
...
# insmod /data/local/cifs.ko
# lsmod
cifs 210416 0 - Live 0xbf1b9000
...
# exit
$ exit
doc@gandalf ~/boot_mod/kernel $

NO ERRORS! GREAT!


The error I don't want to see looks like:
Code:
# insmod /data/local/cifs.ko
insmod: init_module '/data/local/cifs.ko' failed (Exec format error)
where I, probably, mismatched the Kernel Local Version...



...easy play... and waiting for next post...
Last edited by Doc_cheilvenerdi.org; 31st January 2012 at 09:55 PM. Reason: Added Link to Post n. 54
The Following 2 Users Say Thank You to Doc_cheilvenerdi.org For This Useful Post: [ View ]
31st January 2012, 09:51 PM   |  #54  
Doc_cheilvenerdi.org's Avatar
OP Senior Member
Flag Ferrara - Ravenna
Thanks Meter: 346
 
123 posts
Join Date:Joined: Oct 2011
More
Thumbs up [DEV] Increase Internal Memory Size to Whatever You Want!
RAMDISK - SECOND ROUND
I restart from the boot_mod folder:
Code:
doc@gandalf ~/boot_mod $
I need to put into the ramdisk the script that mounts the SD /data filesystem init.data.sh and the binary busybox.
First I download them into the working directory and then I copy them in the right place with the right permissions:
Code:
doc@gandalf ~/boot_mod $ cp init.data.sh ramdisk/
doc@gandalf ~/boot_mod $ chmod 0750 ramdisk/init.data.sh 
doc@gandalf ~/boot_mod $ cp busybox ramdisk/sbin/
doc@gandalf ~/boot_mod $
Now I patch the real init.rc script using this diff file init.rc.patch with this command:
Code:
doc@gandalf ~/boot_mod $ patch ramdisk/init.rc -i init.rc.patch 
patching file ramdisk/init.rc
doc@gandalf ~/boot_mod $
Notice: take care of any warning here; if they occurr the modded boot image could not work properly


KERNEL MODULES - SECOND RUN
Now I'm going to discover the Local Version for the XXKPF kernel:

Option 1: Command for Linux distribution without "sudo" binary (Gentoo, Debian, ...):
Code:
doc@gandalf ~/boot_mod $ su -c 'modinfo ramdisk/lib/modules/fsr.ko' | grep vermagic
Password:  (linux root password asked)

vermagic:       2.6.35.7-perf-CL189639 preempt mod_unload ARMv6 
doc@gandalf ~/boot_mod $
Option 2: Command for Linux distribution with "sudo" binary (Ubuntu, ...):
Code:
doc@gandalf ~/boot_mod $ sudo modinfo ramdisk/lib/modules/fsr.ko | grep vermagic
[sudo] Password for doc:  (linux user password asked)

vermagic:       2.6.35.7-perf-CL189639 preempt mod_unload ARMv6 
doc@gandalf ~/boot_mod $
Now I'll compile the kernel modules (see previous post for details) setting these options in the kernel menu:
Code:
General Setup
 [+] Prompt for development and/or incomplete code/drivers
 ()  Cross-compiler tool prefix
 (-perf-CL189639) Local version - append to kernel release
 [ ] ...
 ...
Code:
File systems
  <M> The Extended 4 (ext4) filesystem
  [ ]   Use ext4 for ext2/ext3 file systems <- This must be UNSELECTED!
  [+]   Ext4 extended attributes (NEW)
  [ ]     Ext4 POSIX Access Control Lists (NEW)
  [ ]     Ext4 Security Labels (NEW)
  [ ]   EXT4 debugging support (NEW)
  [ ] JBD2 (ext4) debugging support (NEW)
  ...
Beware that you need to unselect some options!

I build the modules and put them in the right place inside the ramdisk:
Code:
doc@gandalf ~/boot_mod/kernel $ make modules

...

...

  LD [M]  fs/ext4/ext4.ko

...

  LD [M]  fs/jbd2/jbd2.ko

...

doc@gandalf ~/boot_mod/kernel $
Code:
doc@gandalf ~/boot_mod/kernel $ cd ..
doc@gandalf ~/boot_mod $ cp kernel/fs/jbd2/jbd2.ko ramdisk/lib/modules/
doc@gandalf ~/boot_mod $ cp kernel/fs/ext4/ext4.ko ramdisk/lib/modules/
doc@gandalf ~/boot_mod $
After that i reduce the size of all the modules in the ramdisk (also the proprietary ones):
Code:
doc@gandalf ~/boot_mod $ /home/doc/builds/WORKING_DIRECTORY/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-strip --strip-unneeded ramdisk/lib/modules/*.ko
doc@gandalf ~/boot_mod $

RAMDISK - THE ROOT SIDE
Now I need to issue several commands as "linux root superuser" (mandatory):
(Notice: I'll show only the "su -c" option, while "sudo" one is quite similar...)

Code:
doc@gandalf ~/boot_mod $ su -c 'chown -R root:root ramdisk'
doc@gandalf ~/boot_mod $ su -c 'chmod 04755 ramdisk/sbin/busybox'
doc@gandalf ~/boot_mod $ cd ramdisk/
doc@gandalf ~/boot_mod/ramdisk $ su -c 'find . | cpio -o -H newc | gzip > ../boot.img-ramdisk.gz'
7978 blocks
doc@gandalf ~/boot_mod $ cd ..
doc@gandalf ~/boot_mod $ su -c 'chown -R doc:doc ramdisk'
doc@gandalf ~/boot_mod $ su -c 'chown doc:doc boot.img-ramdisk.gz'

BOOT.IMG - THE END
Last, I repack the modded boot image:
Code:
doc@gandalf ~/boot_mod $ ./mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --base 0x13600000 --pagesize 4096 -o boot.img
doc@gandalf ~/boot_mod $ ls -l
...
-rw-r--r--  1 doc doc 5431296 Jan 31 22:27 boot.img
...
doc@gandalf ~/boot_mod $
I must check that the size of the new image is smaller then 8,0 Megabytes otherwise I could get in trouble while flashing with Odin...

...and finally, after deleting the previous CODE_S5570XXKPF_boot.tar.md5 archive, i make the "Odin Ready" Wanted Archive:
Code:
doc@gandalf ~/boot_mod $ tar -H ustar -c boot.img > CODE_S5570XXKPF_boot.tar
doc@gandalf ~/boot_mod $ md5sum CODE_S5570XXKPF_boot.tar >> CODE_S5570XXKPF_boot.tar 
doc@gandalf ~/boot_mod $ mv CODE_S5570XXKPF_boot.tar CODE_S5570XXKPF_boot.tar.md5
doc@gandalf ~/boot_mod $

THAT'S ALL!

Now I only need to test the XXKPF modded boot image on my phone and then I'll share it on the first post of this thread!
The Following 2 Users Say Thank You to Doc_cheilvenerdi.org For This Useful Post: [ View ]
1st February 2012, 06:26 AM   |  #55  
orieoke's Avatar
Senior Member
Flag YK - ID
Thanks Meter: 48
 
147 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Post Request for S5570DXKPD Asia
Hi DOC..!
Thanks for your posting about this thread.
Now I use STOCK ROM (JVKT1) and increase memory internal to 566MB.

Then I rooted with DooMLoRD_v3_ROOT-zergRush-busybox-su. It's very good and no bug. Different with I used DDKQ7, which must choose increase memory internal or root. We can't root and increase memory internal together.

Last month I share this method to my friends, and they're very happy because not affraid again with Low Memory Space and not have to Rooting the device.
But, in JVKT1 not have Indonesian Language. So, most of my friends want to this method can applied in Asia firmware - S5570DXKPD.
So, if u don't mind... U can make for S5570DXKPD Asia.
Thanks...
The Following User Says Thank You to orieoke For This Useful Post: [ View ]
1st February 2012, 04:21 PM   |  #56  
Doc_cheilvenerdi.org's Avatar
OP Senior Member
Flag Ferrara - Ravenna
Thanks Meter: 346
 
123 posts
Join Date:Joined: Oct 2011
More
Angry [NEXT/MINI/POP/FIT/ACE and GIO] Alltogether...
OTHER PHONE MODELS? ... YOU'RE WELCOME!

I just modded few boot images for Galaxy FIT (S5670) Galaxy ACE (S5830) and Galaxy GIO (S5660)...

Here they are:
Quote:

Galaxy FIT images:

...list moved to Galaxy FIT development Forum...

Quote:

Galaxy ACE Modded boot.img:


Galaxy ACE Original boot.img:

Quote:

Galaxy GIO Modded boot.img:


Galaxy GIO Original boot.img:

WARNING: Backup your data before using them...


P.S. Remember to use Odin and Ops file versions suitable for your phone model!

CREDITS: Many Thanks to kotucisko who Tested (First !) the modded boot image for PDA S5830XWKPY!

CREDITS: Many Thanks to GeorgeParaschiv who Tested (First !) the modded boot image for PDA S5660XXKTF!
Last edited by Doc_cheilvenerdi.org; 14th September 2012 at 11:13 PM. Reason: Added new images
The Following 5 Users Say Thank You to Doc_cheilvenerdi.org For This Useful Post: [ View ]
2nd February 2012, 10:56 AM   |  #57  
Doc_cheilvenerdi.org's Avatar
OP Senior Member
Flag Ferrara - Ravenna
Thanks Meter: 346
 
123 posts
Join Date:Joined: Oct 2011
More
DXKPD 2.3.4
NEW BOOT IMAGE ADDED!

Just added this boot.img (First Post for downloads):
  • S5570DXKPD (2.3.4) <--- Edit: changed from 2.3.6 to 2.3.4 after Wanxbotak notice. Thanks!
Last edited by Doc_cheilvenerdi.org; 5th February 2012 at 08:16 PM. Reason: changed firmware version after type mismatch. Thanks to Wanxbotak
The Following User Says Thank You to Doc_cheilvenerdi.org For This Useful Post: [ View ]
4th February 2012, 10:06 AM   |  #58  
bluedolphin's Avatar
Senior Member
Flag Zagreb
Thanks Meter: 14
 
114 posts
Join Date:Joined: Dec 2006
More
Please for XWKT7 2.3.6 T-Mobile Croatia...

Tnx in advance
5th February 2012, 07:41 PM   |  #59  
Senior Member
Thanks Meter: 70
 
314 posts
Join Date:Joined: Jul 2011
Quote:
Originally Posted by Doc_cheilvenerdi.org

NEW BOOT IMAGE ADDED!

Just added this boot.img (First Post for downloads):

  • S5570DXKPD (2.3.6)

is SS5579DXKPD is 2.3.4, not 2.3.6..
5th February 2012, 08:13 PM   |  #60  
Doc_cheilvenerdi.org's Avatar
OP Senior Member
Flag Ferrara - Ravenna
Thanks Meter: 346
 
123 posts
Join Date:Joined: Oct 2011
More
Type Error and New Image!
Quote:
Originally Posted by wanxbotak

is SS5579DXKPD is 2.3.4, not 2.3.6..

Yes, You are RIGHT! I typed the wrong version ... it is 2.3.4!



In the meanwhile here there is another image:


I soon update the first post and previous one. Thanks!

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes