Hi All,
Here is a new version of my boot manager.
If you didn't see first release, its purpose is to allow dual boot a firmware with two different kernels with a third one that manages boot selection:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a demo of the previous version, it behaves almost the same:
Since first release, I added cwmod and twrp support for both build:
First build is run from native partition, and second build is installled on internal storage via loopbacks. Since first release, I added automatic loobpack creation:
CWM will take care of formatting them.
FIRST A BIG WARNING: all you'll see here is highly experimental, I'm not responsible for any damage or problem it could cause.
I don't have any idea if running a build on loops is wearing off flash memory, it could damage your device.
I don't think it dramatically change anything compared to standard wear on native partitions, but who knows... And something else could go wrong.
Pre-requisite
Currently, if you don't want to loose your current data, you have to be on a rom that has already be repackaged. By default, bootmanager installs Sony 6.1.A.2.55 kernel, so if you're using this firmware, no need to reflash it. For all the other roms, you will have to reflash the repackaged zip in the list below after installation. Don't wipe data/factory reset and you should be good to go. In both case, backup your stuff with Titanium Backup or something else!
Note: you won't be able to restore your previous cwm backups!
Installation:
Minimal setup:
Download bootmanager_0.8.zip (mirrors) (previous version bootmanager_0.6.zip).
Download one of the modified custom firmware in the list below
Install bootmanager zip from your current recovery or extract dual.elf and flash it from fastboot.
Reboot
If your previous rom was not 6.1.A.2.55 based (like cm10 or aokp for instance), reflash your firmware from TWRP for native with one of the native firmware listed below.
Reboot
Now, if you want to use dual boot functionnality:
Select TWRP for loopback
The first time, as you don't have loopbacks files on your internal storage, it will ask for system and data partition sizes. Be patient, it could take time to create them.
When finally recovery is displayed, select erase data/factory reset
then do erase system in partitions/format system
loopbacks are now ready, you can flash one of the available build repackaged for loop.
optionally flash regular google apps from here.
Upgrade from 0.6 or higher:
Upgrade should keep your existing firmwares,
optional, but highly recommended, backup your stuff with cwm and/or Titanium backup.
start stock or custom recovery
flash bootmanager_0.8_upgrade.zip (mirrors)
reboot
re-enable dual boot in settings
Recoveries:
Starting with 0.8, offline charging has been added to twrp. As it's not possible to add to cwm, it is highly recommended to stay on twrp and avoid cwm as it's much safer for your phone.
Starting with 0.5, you can choose between cwm and twrp and switch as you wish. Just flash with your current recovery the recovery you want:
- TWRP 0.8.0 (mirrors) (previous TWRP 0.6.1)
- CWM 0.8.0 (mirrors) (previous CWM 0.6.0)
- EXPERIMENTAL, please read this before installing, TWRP 0.8.2 TWRP 2.6.0 and new 3.4 bootmanager kernel.
Firmwares
Stock / native partitions (flash them from stock recovery)
Sony 6.1.A.2.45 (don't pay attention to filename, this is 2.45, not 2.56, it's a silly typo). Note: you don't have to flash it if you have stock already, it will become useful only later on.
Sony 6.1.A.2.45 addon unsecure kernel, Sony stock kernel only, with ro.secure=0
Sony 6.1.A.2.45 addon kernel modules, Flash this is you have wifi problem, (mostly useful if your firmware was using a custom kernel).
Sony 6.1.A.2.50 stock firmware with unsecure kernel.
Sony 6.1.A.2.50 addon Standalone unsecure kernel.
Sony 6.2.B.0.211 stock firmware, rooted, with busybox.
FXP 137 CM 9.1, original firmware thread here.
AOKP ICS m6 beta 1, thanks to Apology11 for repack! original firmware thread here.
Krabappel2548's KA19, mirrors, original firmware thread here.
Sony 6.1.A.2.55, mirrors, untested unsecure kernel only here.
FXP 147 CM 10, mirrors, original firmware thread here.
PA 2.55 17/11/2012, mirrors, original firmware thread here (kernel from FXP147)
AOKP JB Milestone 1 r1, mirrors, original firmware thread here.
FXP 148 CM 10, mirrors, original firmware thread here.
PAC 18.0.0, mirrors, original firmware thread here
FXP 150 CM 10, mirrors, original firmware thread here.
PA 2.55.1 17/11/2012, mirrors, original firmware thread here
FXP 150a CM 9.1, mirrors, original firmware thread here.
FXP 151 CM 10, mirrors, original firmware thread here.
Nova Xperia RC1, mirrors, original firmware thread here.
FXP 152 CM 10, mirrors, original firmware thread here.
PAC 18.0.2, mirrors, original firmware thread here
Nova Xperia RC2, mirrors, original firmware thread here.
Hei1125's unofficial cm10 20130109, original thread firmware here.
FXP 201 CM 10, original firmware thread here.
FXP 206a CM 10, original firmware thread here.
My JB 4.2.2 aosp build, beta 2, thread is here.
My JB 4.2.2 aosp build, beta 3, thread is here.
My JB 4.3 aosp build, alpha 0, thread is here.
My JB 4.3 aosp build, alpha 1, thread is here.
Custom / loopback partitions (flash them from custom recovery)
Sony 6.1.A.2.50 (buggy, will update soon).
Sony 6.1.A.2.50, kernel only.
Sony 6.1.A.2.55, mirrors (tested, is working properly).
Sony 6.2.B.0.211, stock firmware, rooted, with busybox.
MIUI 2.9.7, mirrors, original firmware thread here.
AOKP ICS m6 alpha 2, original firmware thread here.
Krabappel2548's KA19, mirrors, original firmware thread here.
FXP 145 CM 9.1, mirrors, original firmware thread here.
FXP 147 CM 10, mirrors, original firmware thread here.
PA 2.55 17/11/2012, mirrors, original firmware thread here (kernel from FXP147).
AOKP JB Milestone 1 r1, mirrors, original firmware thread here.
Sony stock Gingerbread 6.0.A.3.75 UK, mirrors. (enabling data makes the phone reboot for me, baseband/radio problem).
Sony 6.1.A.2.55 unsecure kernel only, mirrors
XTXperience 7, mirrors, original firmware thread here. Flash 6.1.A.2.55 kernel with it.
FXP 148 CM 10, mirrors, original firmware thread here.
PAC 18.0.0, mirrors, original firmware thread here
MIUI 2.11.5, mirrors (you have to flash one of these kernels)
FXP 150 CM 10, mirrors, original firmware thread here.
PA 2.55.1 17/11/2012, mirrors, original firmware thread here
FXP 150a CM 9.1, mirrors, original firmware thread here.
Nova Xperia RC1, mirrors, original firmware thread here.
FXP 152 CM 10, mirrors, original firmware thread here.
PAC 18.0.2, mirrors, original firmware thread here
PAC 19, original thread here.
Nova Xperia RC2, mirrors, original firmware thread here.
JellyBear 3.35, original firmware thread here.
Hei1125's unofficial cm10 20130109, original thread firmware here.
FXP 201 CM 10, original firmware thread here.
XTXperience 8.1, original firmware thread here.
FXP 206a CM 10, original firmware thread here.
Ubuntu Touch 0.0.0, thread is here. Note: BIG 540 MB download. It installs on a separate 1.2 GB loopback created by the installation zip.
DooMLoRD Sony JB 6.2.B.0.197 leak, original thread here, credits goes to DooMLoRD
My JB 4.2.2 aosp build, beta 2, thread is here.
My JB 4.2.2 aosp build, beta 3, thread is here.
My JB 4.3 aosp build, alpha 0, thread is here.
My JB 4.3 aosp build, alpha 1, thread is here.
Mirrors of few builds, thanks to elpelas
Repackager package for linux 64 bits, unzip and untar, run as root: ./repackage.sh source_file out_name
DONATIONS
Thanks to @rolex0815 for his donation!
FAQ
- Can I flash any update zip with BootManager ?
Most of the time, no. Some may work unmodified, like google apps that mounts system without using explicit partition. But most of the zips found here mounts directly native partitions so they won't work for build installed on loops. Last, all the kernel zips have to be modified. Flashing any unrepackaged kernel zip will replace boot manager completely and will kill it.
- Can I restore my previous CWM backups after installing bootmanager ?
Yes and no. Yes if you want to go back to where you were before installing bootmanager. No if you want to keep boot manager: restoring the backup will erase it.
Known issues
- Moved apps (to storage/sdcard) will disappear when booting from one build to another. I presume it happens because both builds are sharing storage and it messes up ext2sd scheme. As a workaround, move apps back to internal. This is not a boot manager issue per se, but it's more related to the way builds are repackaged, it probably requires different location for ext2sd. I'll take a look someday.
- Recoveries backups will backup/restore all kernels at once instead of of doing each one separately.
History
2013/02/21: version 0.8
- Offline charging embedded in TWRP, bootmanager is no longer using native build to provide it.
- 1 GB system loop size added
Note: Offline charging can't be added to CWM so CWM is not recommended anymore, TWRP is safer for power management.
2013/01/28: version 0.7
- New settings menu, single boot/dual boot, boot manager protection enable/disable, alternate enable/disable
- Default is now single boot: in this mode, boot manager is only using one kernel and is only providing separate recovery for it.
- TWRP upgraded to v 2.3.3.0
- Only released with aosp build
2012/11/20: version 0.6
- Default recovery is now twrp
- Default kernel is now from 6.1.A.2.55 firmware
- TWRP updated to fix keyboard in backups
- Boot menu now remember which kernel was launched and defaults to it at next boot.
- Bootmanager protection: flashing a kernel that hasn't been repacked should fail. Temporary protection removal here if you want to get rid of bootmanager with a normal firmware.
- Native partition protection: flashing from loop recoveries should not be able to mount native partitions
- Kernel flasher bug fix: layout should now be calculated properly and big kernels shouldn't trash bootmanager anymore
- Notification led color changes depending on which recovery is launched
- ram_console is now properly handled by boot manager kernel. From now on, you should go to a recovery to get the last_kmsg for a crashing kernel.
- Boot manager can be flashed from recoveries.
2012/10/20: version 0.5
- flashable recoveries (cwm and twrp)!
- new kernel layout to give more space to loop kernel
- boot menu delay countdown fix
- offline charging forwarded to native build
- pre-installed kernel is now 6.1.A.2.50 one.
- added recoveries for alternate (re-partitioned devices only)
2012/10/06: version 0.4
- initramfs location moved to 0x41500000 for aokp and cm10 compatibility
- debug traces left in cwm removed
- new kernel extraction command (ke)
2012/10/02: version 0.3
- cwm recovery bugfix to get proper Aroma colors.
- stock / custom name changed to native / loopback in menus.
- added menu for cache loopback to adjust cache size.
2012/09/10: version 0.2
- CWMod recoveries are now working for stock (native) and custom (loopbacks).
- Loopbacks files are created if they are missing with multiple sizes.
2012/09/04: version 0.1
- Initial release, original thread here.
For devs:
Source code:
Trimmed kernel uploaded to gitorious here , branch bootloader_kernel.
Boot menu (FBMenu, thanks to openAOS for initial release!) here.
Embedded kernel flasher kf : here.
Elf kernel splitter sksplit here. I use it mostly to extract kernel and cpio in repackaging firmware.
Background:
Here are some details on how it works:
I trimmed down a stock kernel to remove some fat and add a driver to set a specific memory location.
I embed a small assembly loader with this kernel and its cpio plus the other 2.
The tiny kernel is loaded first, it displays the menu and eventually starts cwm. The menu will set the memory location with the kernel choice, then reboot.
At next reboot, the assembly loader will detect the kernel choice and start the appropriate kernel.
So, in fact, you're booting two times, first the small loader, then the real boot.
It adds some boot time, but it's not dramatic. The advantage is that it's easy to build the loader, it's a simple init. Second advantage, the second kernel is running on a "fresh" start, no left-over in memory, no kexec patch to apply, it works with any kernel. Last, cwm can be embedded with the tiny kernel, so it's finally independent from the build kernel.
Repack sample, FXP137 cm9.1:
unzip ../downloads/FXP137-cm-9-20120908-UNOFFICIAL-nozomi.zip
sksplit boot.img
sudo su
mkdir cpio
cd cpio
cat ../sec1-0x41300000.bin | gzip -d | cpio -i --make-directories
emacs init.semc.rc
Code:
# mount mmc partitions
# mount /system, set up links to the modem, and remount r/o
mount ext4 /dev/block/mmcblk0p12 /system wait rw barrier=1
mkdir /system/etc/firmware/misc 0771 system system
mount ext4 /dev/block/mmcblk0p12 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 /dev/block/mmcblk0p14 /data wait noatime nosuid nodev data=ordered noauto_da_alloc
mount ext4 /dev/block/mmcblk0p13 /cache wait noatime nosuid nodev data=ordered noauto_da_alloc
becomes:
Code:
# losetup on storage
mkdir /sd
mount vfat /dev/block/mmcblk0p15 /sd wait rw
# ro directly as misc is created by install script
mount ext4 [email protected]/sd/custom_system.ext4 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 [email protected]/sd/custom_data.ext4 /data wait noatime nosuid nodev data=ordered noauto_da_alloc
mount ext4 [email protected]/sd/custom_cache.ext4 /cache wait noatime nosuid nodev data=ordered noauto_da_alloc
and:
Code:
exec sbin/bootrec
becomes
Code:
exec /system/bin/chargemon
and save
rm init.semc.rc~
cd sbin
rm e2fsck bootrec bootrec-device fix_permissions killrecovery.sh mke2fs nandroid-md5.sh parted postrecoveryboot.sh sdparted tune2fs
cd ..
find . | cpio -o -H newc | gzip > ../initramfs.cpio.gz
cd ..
rm -r cpio sec2-0x00020000.bin sec1-0x41300000.bin boot.img
mv sec0-0x40208000.bin zImage
emacs META-INF/com/google/android/updater-script
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p12", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");
becomes
Code:
format("ext4", "EMMC", "/dev/block/loop2", "0");
mount("ext4", "EMMC", "/dev/block/loop2", "/system");
then
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p3");
becomes
Code:
package_extract_file("zImage", "/tmp/zImage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "2", "/tmp/zImage", "/tmp/initramfs.cpio.gz") == 0);
add before this :
Code:
show_progress(0.200000, 0);
show_progress(0.200000, 10);
this:
Code:
run_program("/sbin/busybox", "mkdir", "/system/etc/firmware/misc");
set_perm(1000, 1000, 0771, "/system/etc/firmware/misc");
and save, then finally:
zip -r ../cm9-loop.zip *
Repack Sample, 6.1.A.2.45 firmware on stock/native:
mkdir stock_6.1.A.2.45_zip
cd stock_6.1.A.2.45_zip
7z x ../downloads/LT26i_6.1.A.2.45_GENERIC_NL.7z
7z x "LT26i_6.1.A.2.45_GENERIC NL.ftf"
rm "LT26i_6.1.A.2.45_GENERIC NL.ftf"
mkdir zip_out
sin2raw kernel.sin kernel.elf
sksplit kernel.elf
mv sec0-0x40208000.bin zip_out/zImage
mv sec1-0x41300000.bin zip_out/initramfs.cpio.gz
sin2raw system.sin system.ext4
sudo su
mkdir system
mount -o loop -t ext4 system.ext4 system
cd system
... optionally add root, busybox:
cp -r /home/tama/supersu/system/* .
cd xbin
chmod 6755 su
cp /home/tama/cm9/out/target/product/gen9/system/xbin/busybox .
cp /home/tama/relink-busybox.sh .
chmod 755 relink-busybox.sh
cd ../..
tar -cvzf zip_out/system.tgz system
... get script from cm9, ..
cd zip_out
cp -a ../../fxp137_cm9_ziploop/META-INF .
emacs META-INF/com/google/android/updater-script
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26a" || getprop("ro.build.product") == "LT26a" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
ui_print("LT26i 6.1.A.2.45 firmware for boot manager (stock)");
show_progress(0.100000, 5);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.700000, 60);
package_extract_file("system.tgz", "/tmp/system.tgz");
assert(run_program("/sbin/tar", "-cvzf", "/tmp/system.tgz") == 0);
show_progress(0.200000, 10);
assert(run_program("/system/xbin/busybox-relink.sh", "");
unmount("/system");
package_extract_file("zImage", "/tmp/zImage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "1", "/tmp/zImage", "/tmp/initramfs.cpio.gz") == 0);
ui_print("Firmware installation complete");
Repackage sample, KA14 with Aroma installer
Code:
sudo su
mkdir ka14
cd ka14
unzip /home/tama/sony/downloads/KA14_Xperia_SSpeed.zip
mv zImage zImage.original
sksplit zImage.original
mkdir cpio
cd cpio
cat ../sec1-0x41300000.bin | gzip -d | cpio -i --make-directories
rm *~
rm init
rm init_gb
mv init_ics init
rm recovery.*
rm -r res
rm 1
rm init.sh
cd sbin
rm tune2fs sdparted parted nandroid-md5.sh nandroid mr mke2fs killrecovery.sh fota-ua fota-mke2fs fix_permissions e2fsck checkabortedflash autoroot.sh
ln -s /init ueventd
cd ..
find . | cpio -o -H newc | gzip > ../initramfs.cpio.gz
cd ..
mv sec0-0x40208000.bin zimage
emacs META-INF/com/google/android/updater-script
change:
Code:
assert(package_extract_file("zImage", "/tmp/zImage"),
write_raw_image("/tmp/zImage", "/dev/block/mmcblk0p3"),
delete("/tmp/zImage"));
to:
Code:
package_extract_file("zimage", "/tmp/zimage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "1", "/tmp/zimage", "/tmp/initramfs.cpio.gz") == 0);
Code:
zip -r ../bm_native_ka14.zip META-INF customize system zimage initramfs.cpio.gz
AOSP experiment
Special build, aosp 4.2.1 experiment!
This one is special and deserve specific instructions.
First, it's not functional, and will never be.
I just wanted to have a look at current status of AOSP experiment for Xperia S, it required much more fiddling than reasonable and ended into a monster.
Again, I take no responsability if you flash this. It doesn't work properly, it's not tested, it can be bad for your phone .
Second, if you want to install this, read carefully instructions, it's not packaged like a normal loop rom.
Last: special thanks to FXP team, it wouldn't have been this far with the work they did on CM10. I took few binaries from FXP release and few patches from Cyanogen repo, no way to make it run without the work they did.
Now, that the warning are there, here is the status:
What's working:
1) It boots
2) Audio
3) Phone call/sms
4) Wifi
What's not working:
1) Data
2) Storage
3) And much more
Pre-Installation:
1) You need around 2G free space on storage
2) It will replace your loop kernel but keeps the loopback files untouched
3) If you want to save your current kernel, you can do this from loopback recovery with adb:
Code:
adb shell ke 2 /tmp/zimage /tmp/initramfs
adb pull /tmp/zimage
adb pull /tmp/initramfs
Installation
From loopback recovery, install zip file.
Restore previous loopback rom
Flash build zip file without wiping data/cache
or if you saved your kernel previously:
Code:
adb push zimage /tmp
adb push initramfs /tmp
adb shell kf 2 /tmp/zimage /tmp/initramfs
adb shell sync
then boot your loopback build.
Download
Download rom here, mirrors.
FAQ
1) What is this ?
I started this to check status of Google/Sony AOSP experiment. I wanted to see how far they went and how it behaves.
2) Why not making it functional ?
As it is, it's not worth it. To have the running state I have, I had to patch google aosp source, patch kernel, fiddle with FXP binaries, etc... This build is a Frankenstein monster and it would take quite a big amount of work to end up with something that takes many things from CM and doesn't work as good as CM.
We'll see if Sony goes further in releasing proprietaries and source code, but without that, AOSP will end up in CM without CM bonus
Wow, this is far more superior than 0.1!
So now I can install every ROM on loops?
Vipitus said:
Wow, this is far more superior than 0.1!
So now I can install every ROM on loops?
Click to expand...
Click to collapse
No, that's not possible, you need adapted zip for it. Maybe in a future version, but I think it would be very difficult to patch cpio's on the fly.
I'll continue adapting few builds to give more choice though.
For now only CM9, yes?
---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------
letama said:
(...)First make sure that your stock firmware is 6.1.A.2.56
Click to expand...
Click to collapse
Do this firmware exists?
Do you mean 6.1.A.2.45?
Oups, Yes, too much writing sorry typo fixed, thanks for noticing.
Cm9.1 only, I'll add more later on, cm10 is difficult because of uncompressed kernel, any other firmware in mind?
letama said:
Cm9.1 only, I'll add more later on, cm10 is difficult because of uncompressed kernel, any other firmware in mind?
Click to expand...
Click to collapse
AOKP JB, MIUI (on stock kernel)
AOKP is using CM10 kernel, so same problem, the 10+MB uncompressed kernel doesn't fit. I'll do MIUI first, it should be quicker...
make a stock + jb dual kernel too
thats needed most right now
Sent from my Xperia S using xda app-developers app
Letama sry i know you are tired but i didnt understand this with pack and repack stuff.
Do i have to do that by my self, or just flash and do what you write in first post?
And then i can switch from one rom to another on the go?
Sent from my LT26i
Seems download link for Cm9 is broken .
Sent from my Xperia S using xda premium
championswimmer said:
make a stock + jb dual kernel too
thats needed most right now
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
+1
I usually don't do that, but I agree. Stock + JB is a must, I guess...
Sent from my LT26i with Tapatalk 2
This is really nice! Fascinating...
Great Job!
I have a Q ? I tried it many times when I finished flash the CM9.1 over the Custom kernel. It always boot on custom kernel. It doest show for me 2 choises like in your video @@
Do I must use 2 roms only in your first page ??
Related
Hi everyone,
First, read the readme.txt in the zip file.
You flash it at your own risk. Backup everything. Learn how to use Heimdall. If it eats your dog it's not my problem . Many things are broken - post about it in the thread if nobody posted before. If you have any idea how to fix things, post too or PM me.
Requirements: GSM (Euro, US ATT/TMO tabs), with JQ1 (Gingerbread) unprotected bootloaders that can run Euro JQ1 ROM and gt-p1000_mr.pit partitioning.
Modem versions:
ATT: use I9000UGJK3 modem (this is what I am using)
TMO: try JK5
Euro: reports say that JK5, JPZ modems work
HK: user reports JK5 modem works.
CDMA: This ROM does not support CDMA Tabs.
LTN: experimental kernel included.
The archive with the build with Heimdall is here http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-08-05.zip
Please use heimdall to install. This zip file is not for flashing with CWM. Unzip and read the readme.txt in the zip file. Flash using the Heimdall command line (below).
The update zip for CWM is here http://gtab7.nexus-lab.com/cm7sgt/cm-7-20120805-UNOFFICIAL-galaxytab.zip, (GSM only, no LTN), please be sure to flash it from recovery that supports EXT4 or flash it once so it updates kernel/recovery, reboot to new recovery and flash it again. If you encounter any problems, use the Heimdall version.
P1000L/N
There is experimental P1000L kernel and bootloaders included in LTN directory in Heimdall package. It should work on P1000L and maybe P1000N.
Big thanks to Humberos for patches and testing. Adventureous souls with Latin Tabs please try it and report how it worked for you. You should have Gingerbread bootloaders and partitioning done first, so it should be easy if you are already running Gingerbread on your P1000L/N.
Installation using Heimdall
normal update from previous CM7 version, or a flash from another Gingerbread ROM:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.ext4
full flash and repartition:
Code:
heimdall flash --repartition --pit gt-p1000_mr.pit --primary-boot boot.bin --secondary-boot sbl.bin --kernel zImage --factoryfs factoryfs.ext4 --cache cache.ext4 --dbdata dbdata.ext4
Please be careful and double check your Heimdall command line when you flash bootladers, you may brick your Tab pretty bad.
If you get stuck on first reboot after install, or your settings aren't saved it means your data partitions need to be reformatted to ext4. This should be handled by setup_fs in init.rc.
If it didn't happen, start adb and run
make_ext4fs /dev/block/mmcblk0p2
make_ext4fs /dev/block/stl10
make_ext4fs /dev/block/stl11
Or try full wipe in recovery.
make_ext4fs is slightly wonky so you could use "/system/bin/mke2fs -t ext4 -m 0" instead (recovery is also using make_ext4fs internally to wipe partitions)
Samsung apps, Swype, Gapps etc
This is an unofficial port of CyanogenMod. I am striving to give us the pure CyanogenMod experience on Galaxy Tab.
So, there are no Samsung apps and don't ask for them.
There is no TouchWiz and don't ask for it.
It comes with ADW Launcher and if you want anything else, there is plenty of launchers in the Market.
If you want Google Apps, get it from the usual place http://goo-inside.me/gapps/ and install from recvery after flashing update.zip. The Heimdall version has Gapps integrated right now.
There is one stupid annoyance on Google sign-in welcome screen. It asks to slide open the keyboard (which we don't have and for now I can't find this setting). So skip the whole set up and sign in to Google account from Settings->Accounts&Sync.
Swype: there is no Swype. Since Swype has a policy of allowing Swype on modded ROMs as long as the original ROM had Swype integrated, if somebody cares to make flashable zip with Swype I can link it from OP.
Market issues.
Market 3.x has much stricter rules about DPI and device checks. So very often it shows apps as not compatible with CM7 on GalaxyTab.
Just go to Settings->Applications and uninstall updated Market it will go back to 2.x for a while.
Or try tool like OldMarket http://forum.xda-developers.com/showthread.php?t=1240344
You can also change build.prop yourself, you will need to change two lines:
ro.build.tags=test-keys to ro.build.tags=release-keys
and
ro.sf.lcd_density=200 ro.sf.lcd_density=240
reboot, delete Market data from Settings->Applications
Big thanks to junkshow for investigating it.
sources at http://github.com/cm7sgt
How to report bugs
If you think you have found a bug.
- verify you can repeat it, make sure it is not caused by the fact you did not wipe the device by rebooting to recovery and using wipe when you first installed CM7. Particularly when coming from other ROMs that use ext4. When coming from RFS your partitions should have been reformatted on first boot but wiping after install will not hurt.
Please read existing open and already closed issues at http://github.com/cm7sgt/android_device_samsung_galaxytab/issues
If your bug is new.
Please see if it is upstream (general CM7 not related to Tab) bug, see in CM7 issues tracker http://code.google.com/p/cyanogenmod/issues/list
If it is already there, please stop or add a comment there.
If the bug is about generic issue, please try to verify it it also happens on other CM7 devices. If so, you should post it in CyanogenMod issues.
If the bug is Galaxy Tab specific, like, some hardware functionality is missing, some driver not working. Dialogs messed up because of resolution etc, this means it belongs to Galaxy Tab device issue tracer and I can fix it.
In this case please open new issue here http://github.com/cm7sgt/android_device_samsung_galaxytab/issues
Please use pastie.org or something like that for posting logs.
SDCARD controversy
By default, the real micro SD is /mnt/sdcard, the internal mmc is /mnt/sdcard/external_sd, like in Galaxy S CyanogenMod builds.
If you don't like it, you can swap the devices, go to Settings -> CyanogenMod settings -> Application and check Use internal storage [ ] checkbox.
Reboot, now internal will be /mnt/sdcard, external will be /mnt/sdcard/external_sd like in Samsung's Android.
In recovery, real sdcard in /sdcard, internal sdcard (embedded MMC) is /emmc.
If you want to flash zip from /emmc just go in recovery "install zip from sdcard" -> "choose zip from internal sdcard" -> choose whatever you want to flash.
--
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Current status:
Voice calls: OK (make sure to use modem.bin compatible with JQ1 RIL)
3G data: OK
Wifi: OK
Bluetooth: OK
Camera: Photos OK, video encoding (movie capture) back OK, front corrupted
Sensors: seem OK
GPS: OK
Recovery and initramfs: CWM, partitions get mounted, wipe works, havent tried backup/restore
Video playback: overlay and copybit work, OMX libraries are in and decoding works.
Changelog:
2012-08-05 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-08-05.zip http://gtab7.nexus-lab.com/cm7sgt/cm-7-20120805-UNOFFICIAL-galaxytab.zip
Fixed Bluetooth MAC address issue. Now it is read correctly from EFS. Thanks to ableeker.
2012-07-28 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-07-28.zip http://gtab7.nexus-lab.com/cm7sgt/cm-7-20120728-UNOFFICIAL-galaxytab.zip
Update to latest from CM7 git.
2012-02-19 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2012-02-19.zip http://gtab7.nexus-lab.com/cm7sgt/update-cm-7-2012-02-19-Beta-GalaxyTab-KANG-signed.zip
Update to latest from CM7 git. set default DPI to 240 to fix market issues, advanced users can set any DPI they want anyway.
Go back to stock dialer layout because it has changed a lot.
2011-11-02 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2011-11-02.zip http://gtab7.nexus-lab.com/cm7sgt/update-cm-7-2011-11-02-Beta-GalaxyTab-KANG-signed.zip
use android socket for wpa_supplicant control interface. anyone upgrading to this version please delete their /data/misc/wifi/wpa_supplicant.conf
thanks to jt1134, removed extra field in mfc interface in kernel which prevented it from working with aries OMX libraries
updated media_profiles.xml to expose 1024x600 and 800x600 resolutions for camcorder. its not perfect but at least video recording works now. front cam produces broken video.
2011-10-31 http://gtab7.nexus-lab.com/cm7sgt/tcm7beta-2011-10-31.zip http://gtab7.nexus-lab.com/cm7sgt/update-cm-7-2011-10-31-Beta-GalaxyTab-KANG-signed.zip
update to latest from git. we are little past 7.1.0.
fix key setting for AP mode
new init.rc/init.gt-p1000.rc unified with CDMA device
2011-10-09
move download cache to /data/cache_download and system dalvik cache to data, it should fix download issues with large APKs
fix bluetooth keyboard keypad rotation issue
move touchscreen event rotation to kernel to to clean up frameworks/base
use switchable pair and new stacked mounts in vold for /mnt/sdcard and and /mnt/sdcard/external_sd
2011-09-20
Update to latest from git.
Merged P1000L/N kernel. P1000L kernel included in build.
Voodoo Sound update to V10. Switch to JHASH3 hash function in kernel.
Disabled NEW_AP in Wifi driver, fixed hotspot mode.
2011-08-07
Update to latest from git. Android 2.3.5.
Added BLN kernel driver and LIGHT_ID_NOTIFICATIONS -> /sys/class/misc/backlightnotification/notification_led device to liblights. Big thanks to Neldar.
Fix geolocation/networklocation settings in props and frameworks' config.xml
Update EGL driver and pvrsvrkm kernel driver to latest from EF17 Sprint GB release.
2011-07-20
Update to latest from git.
Merge changes from Sprint GB kernel source release. Merge relevant kernel changes to up to 2.6.35.10.
2011-06-21
Enable CRT screen off/on animation.
Add virtual flag to capacitive buttons to enable vibration when they are pressed.
Increase HCI baud rate to 3M, hopefully this will help A2DP issues with BT keyboards.
2011-06-13
Rotary Lockscreen bitmaps and Twelve Key Dialer portrait and landscape layouts have been fixed by Fabrizio. Big thanks!
Fixed wrong parameter to ril->setCallVolume, hopefully will make call audio better.
Switched to use Samsung's binary brcm_patchram_plus with the same parameters in init.rc. Bluetooth SCO works now. Magic?
2011-06-06
Add attribute for available frequencies, fix cpufreq sysfs permissions so CMParts can access it.
Change compile options for kernel to cortex-a8. Enable Tiny RCU.
Fixed calls from other places in the kernel that used olde speed levels and caused frequency spikes to 1.2GHz.
Fixed Low Power Mode (it properly starts /lpm.rc and displays charging animation).
2011-06-05
Added 10-point Multitouch to kernel (thanks to The_Double and hoss_n2)
Added overclock (1.4GHz) and undevolt (thanks to Richard Trip and Koxudaxi)
Added Voodoo Sound V9 (thanks to Supercurio and Richard Trip)
Switched to (some) Crespo EGL SOs, hopefully will fix some OpenGL issues.
2011-06-03
Add usb_connected switch to kernel, fixes usb mounting and usb connection detection.
Use mke2fs instead of make_ext4 for formatting in OTA and setup_fs. Should be more reliable.
Added download mode to reboot menu.
2011-05-30
Fix problems with headphones/headsets and libaudio, kanged common-aries libaudio.
Added OMX libraries and overlay from common-aries.
2011-05-28r2
Fixed setup_fs so it properly formats partitions.
Enabled more tablet tweaks (soft buttons).
Removed format for .android_secure in recovery, should fix wipe.
2011-05-28
Switched to Gingerbread kernel 2.6.35.7 recently released by Samsung.
Use JQ1 binary drivers for OpenGL, sensors, lights, copybit, overylay, camera etc, so they all work!
Portrait is default orientation now, ro.sf.hwrotation=90 is set and touchscreen events are rotated in input layer so they match.
<cut short, more in readme.txt>
Big thanks to noobnl, coolya, codeworkx, rotohammer, KhasMek, deodexed, captainkrtek, lilstevie, a_snowman, frusso, humberos, koxudaxi, spacemoose, oldmacnut and others for help, advice, testing etc etc.
DEVS ONLY HERE ---------------------------------------
How to build CYanogenMod 7 for Galaxy Tab GT-P1000
First, please read this article http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_CaptivateMTD
You will need the same prerequisites.
Then
Get repo as described there. I put mine in /usr/local/bin
Sync Android tree. You need to use manifest from cm7sgt github.
(If you have more/less than 4 cores modify your -j4 accordingly)
Create a directory for your Android, you will need oer 10GB of free space. It helps a lot to put it on SSD.
repo init -u git://github.com/cm7sgt/android.git -b gingerbread
since kernel.org gits are still down, until they are back up you need to sync repo tool from github, so use this command line, thanks to Disgustipated for pointing it out.
curl https://raw.github.com/android/tools_repo/master/repo > ~/bin/repo
chmod a+x ~/bin/repo
repo init -u git://github.com/cm7sgt/android.git -b gingerbread --repo-url=git://github.com/android/tools_repo.git
repo sync -j4
Grab Rom Manager as described.
You can't (no script) and don't need to copy proprietary files, everything is already included in vendor git.
Setup your android build environment and choose device to build:
. build/envsetup.sh
lunch cyanogen_galaxytab-eng
make -j4
There, it should build with no issues. Sometimes it will complain about API changes, run make update-api then.
From here you have two options.
1. Build Heimdall images. You will need kernel with loop support, losetup, ext4 tools (mkfs.ext4).
cd device/samsung/galaxytab/tools
./buildimage
it will grab stuff from out and create ext4 images. Flash with Heimdall.
2. Build update.zip
make -j4 bacon
How to build kernel
First, you will need the arm toolchain from CodeSourcery. You need arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
From http://www.codesourcery.com/sgpp/li...q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
Unpack it in /opt/toolchains. as root
mkdir -p /opt/toolchains
cd /opt/toolchains
tar -xjvf arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
Then in your CM7 tree
BEFORE YOU BUILD CM7 TREE
cd device/samsung/galaxytab
./kernel.sh defconfig
./kernel.sh modules
This will configure the kernel and build and copy modules to prebuilt directories. The kernel build directory is out/target/product/galaxytab/kernel_build
Build your android tree normally so initramfs is created.
Then again
cd device/samsung/galaxytab
./kernel.sh kernel
This will build the kernel using the initramfs in recovery/root and update prebuilt kernel image.
(for Latin kernel use kernel_ltn.sh script and use kernel_ltn file it produces)
Now you need to run make on your android tree again so boot.img is updated.
And proceed to buildimage or make bacon as usual.
sweet news
P1000L tabs too?
I can test for you.
ivannw said:
P1000L tabs too?
I can test for you.
Click to expand...
Click to collapse
AFAIK P1000L hardware is different so it will need different kernel
How do we check which bootloader we have?
TheGrammarFreak said:
How do we check which bootloader we have?
Click to expand...
Click to collapse
If you installed Euro JJ4 ROM you probably have JJ4 bootloader.
It will probably also work with stock ATT and TMO bootloader but I cannot guarantee that. I have JJ4. People have reported issues using Euro ROMs on ATT bootloaders, I believe the same issues will show up in my CM7.
Great news. I have polish rom maybe i help. galaxy tab jm6
That is amazing work!
Well done.
Which issue r u tlaking abt? I have recent att tab went straight to jme no issue. Lemme know if i could hrlp testing. Ubuntu & heimdall ready. I actually pulled your old cm6 and cp kernel-tab and what not to cm7 but failed at lunch cyanogen...
Sent from my GT-P1000 using XDA App
quattr0 said:
Which issue r u tlaking abt? I have recent att tab went straight to jme no issue.
Click to expand...
Click to collapse
some white lines while booting etc. if JME works for you my stuff should work too.
TheGrammarFreak said:
How do we check which bootloader we have?
Click to expand...
Click to collapse
I'm no expert but this seems obvious (for me). If you have a linux box, do a "strings boot.bin" on a protected bl (extract from JMF downloaded from samfirmware for instance), you will see these lines
PBL: Error.. sbl verification failed..
PBL: booting stop!
My at&t backup boot.bin does not have the above 2 lines.
Just my guess.
Technomancer said:
AFAIK P1000L hardware is different so it will need different kernel
Click to expand...
Click to collapse
Can you help me or give the way to compile the correct kernel?
Sent from my GT-P1000L using XDA App
I can't wait for this... My Tab seems to just be less awesome without the love CM gives to Android.
installed but touch doesnt works.
what is the next step?
ivannw said:
installed but touch doesnt works.
what is the next step?
Click to expand...
Click to collapse
this is because of the different hardware!
if ur not a developer, leave it till it is stable because u are missing some necessary features for everyday use!
landroid thanks for your response.
btw i wanna learn how to fix that. can you give me directions ?
first of all I'll try to get stock rom compiled.
too bad again not for CDMA tab user
ivannw said:
landroid thanks for your response.
btw i wanna learn how to fix that. can you give me directions ?
first of all I'll try to get stock rom compiled.
Click to expand...
Click to collapse
First off all u need to find the kernel source for ur tab (i think P1000L, right?) And then apply the patches technomancer made to the kernel but this is very hard to do! The best thing would be to contact technomancer! And if i find some spare time tommorrow ill try to compile a P1000L kernel for u but i cant guarantee that if i manage to do that everything works! But i knoe how to compile kernels from source so it should not be a problem!
Sent from my GT-P1000 using Tapatalk
ivannw said:
landroid thanks for your response.
btw i wanna learn how to fix that. can you give me directions ?
first of all I'll try to get stock rom compiled.
Click to expand...
Click to collapse
Get sources for your kernel from opensource.samsung.com.
Compile it with gingerbread branch of this initramfs https://github.com/cmsgs/android_initramfs_galaxytab
See what happens ;-)
Look awesome!!
Well what do you do when you're bored and need some distraction .....Modify the stock kernel and include SU!
If you just search on the internet and especially on XDA than you find out that this is not so difficult.
The only purpose of this modified kernel is install SU and thus get ROOT
Why superuser and busybox are not installed by default is simple: it takes only 1 minute to download it from the market...
So here I give you the stock kernel + su/Root for XXJVQ/ XXJVR
installation:
1. Flash the tar file with Odin
2. Download superuser from the market and install it
3. Download Busybox installer from the market and install it
Credits to Supercurio, Hardcore, Liliniser for the tools and sources
Tutorial is Linux based!!!
So if i can do it than you can do it also!! All you have to do is read and follow post 2
Update 01/08/11 Added XXJVT
Update 01/08/11 Added Working XXJVR
Update 06/07/11 Howto add init.d support to the kernel (post 3)
Tutorial
1. Download and install the needed tools
2. extract de stock kernel to a temporary directory
3. modify the init.rc script to include your su install script.
4. add in the tmp folder busybox and su
5. add in the sbin directory your install script.
6. Recompile the kernel
7. Tar de kernel
8. Flash the kernel with heimdall or Odin
1. Download and install the needed tools
* Cross compiler: http://www.codesourcery.com/sgpp/li...eabi/arm-2009q3-67-arm-none-linux-gnueabi.bin and install it to /opt/toolchains/arm-2009q3/
* Kernel repacker made by Liliniser / dkcldark : Download from supercurio's github. with (if installed) git clone git://github.com/project-voodoo/kernel_repack_utils or goto the website https://github.com/project-voodoo/kernel_repack_utils and click on download.
* Download busybox,su and the install script from this post, and extract the files.
2. extract de stock kernel to a temporary directory
Copy the original zImage to de directory where you extracted the kernel repacker
Rename it to zImage.org
create a temp directory in the kernel repacker directory
Open a linux shell and go to kernel repacker directory
./extracter.sh -s zImage.org -d temp (hit enter)
3. modify the init.rc script to include your su install script.
Go to the temp directory and edit init.rc with your favourite editor and put this on a new line at the end off the file.
service install_su /sbin/install_su.sh
user root
oneshot
Save the file and exit
4. add in the tmp folder busybox and su
copy busybox and su to the tmp folder in your extracted kernel folder
make sure they are markt als executable.
5. add in the sbin directory your install script.
copy install_su.sh to the sbin folder in your extracted kernel folder
6. Recompile the kernel
Open a linux shell and go to kernel repacker directory
./repacker.sh -s zImage.org -d zImage -r temp -c gzip
congratulations you must cooked your first modified kernel
7. Tar de kernel
tar -H ustar -c zImage >code.tar
8. Flash the kernel with heimdall or Odin
Howto add init.d support to the stock kernel
Whell this is easy to implement
1. Open a linux shell and goto to the extracted kernel directory. (read post 2 howto do that)
add the following lines to the init.rc file
Code:
service initd_support /sbin/initd_support.sh
user root
oneshot
Save the file and exit
2. Create a new file in the sbin directory called initd_support.sh and add the following code
Code:
#!/tmp/busybox sh
if cd /system/etc/init.d >/dev/null 2>&1 ; then
for file in S* ; do
if ! ls "$file" >/dev/null 2>&1 ; then continue ; fi
/system/bin/sh "$file"
done
fi
Save the file and make it executable
3. repack the kernel (see post 2 for the howto)
4. on your device mount system Read/Writable and create the directory /system/etc/init.d
5. Copy your init scripts to /system/etc/init.d/
Make sure the name starts with a S, and set the permissions to 777
Example step 5/6
Code:
adb push Stweakscript /sdcard/
adb shell
su
/tmp/busybox mount -o remount,rw /system
/tmp/busybox mkdir /system/etc/init.d
/tmp/busybox cp /sdcard/Stweakscript /system/etc/init.d/Stweakscript
/tmp/busybox/chmod 777 /system/etc/init.d/Stweakscripts
7. flash the kernel
I'm sorry in advance.
But WTF?
vladoots said:
I'm sorry in advance.
But WTF?
Click to expand...
Click to collapse
If you only want to root your rom don't wait for devs to do it but do it your self
lownoise said:
If you only want to root your rom don't wait for devs to do it but do it your self
Click to expand...
Click to collapse
Yes, and for learning purposes. Thanks for the tips, I was sitting down to do this on another phone the other day actually... it's good to see your ideas, I was getting pretty frustrated with the limited Android init environment (the toolbox commands are so limited!).
Thanks for this nice tutorial.Worked great!
Great! Now we have good rooting kernel.
If I want root - I want root, not tweaks and other "shiny" things.
Cfroot breaks BT in some cases, Fuguroot breaks Kies connection.
Kernel which don't add Superuser.apk as a system application is the best choice - we don't have to delete other system files and there are updates of this app, so why should we have older version on /system and new on /data as an update?
Can I do "adb root" on this kernel ?
Sure Just install superuser and busybox from the market
Wooow! These are the sort of tutorials I miss here sooo much. It's a developer forum, but what we are getting here mainly are ready-products (roms, modded kernels). And why not to do it yourself. But sometimes googling for the information is not so easy, because applies to different conditions(devices, phone models, soft versions). There are many people who would spend their time learning how to compile a kernel or edit framework files. But there are so few tuts on this here... I miss tuts that tell how to do things step-by-step, without any specific linux/java knowledge.
sebarkh said:
Wooow! These are the sort of tutorials I miss here sooo much. It's a developer forum, but what we are getting here mainly are ready-products (roms, modded kernels). And why not to do it yourself. But sometimes googling for the information is not so easy, because applies to different conditions(devices, phone models, soft versions). There are many people who would spend their time learning how to compile a kernel or edit framework files. But there are so few tuts on this here... I miss tuts that tell how to do things step-by-step, without any specific linux/java knowledge.
Click to expand...
Click to collapse
And therefore I did it. Share the knowlegde and safe this forum
Why doesn't XDA have more stuff like this?
Thanks OP!
Yes, I must thank you too.
Now I understand... Sorry for my initial confusion!
I've problem:
after applying script:
line 47: ./out/project/original.cpio -> no such files or directory
Any idea ?
Where is original.cpio files ?
Screen of error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tq man...!!
man this is amazing, I was looking for something simple like this for months. It's right, should be more posts like these in xda
+1
Thank you very much for this, lownoise
We need more topics like that, since I am interested to learn myself...
Members posting tutorials like that are always appreciated, I cannot thank you enough.
Do you know how to replace the recovery 3e with 2e additionally?
It would be great to know since I want to have it CWM compatible (flash unsigned update.zip)
AFAIK recovery is a part of the kernel....
It would be great if you could point me to the right direction.
Others probably would like to know that as well.
Thanks again.
dago said:
I've problem:
after applying script:
line 47: ./out/project/original.cpio -> no such files or directory
Any idea ?
Where is original.cpio files ?
Screen of error:
Click to expand...
Click to collapse
Which kernel did you try to modify
lownoise said:
2. extract de stock kernel to a temporary directory
Copy the original zImage to de directory where you extracted the kernel repacker
Rename it to zImage.org
create a temp directory in the kernel repacker directory
Open a linux shell and go to kernel repacker directory
./extracter.sh -s zImage.org -d temp (hit enter)
Click to expand...
Click to collapse
Two noob questions:
1. from where to copy zImage file? Where can I find zImage file?
2. How to open linux shell? Should I install linux shell application on my PC and run it or?
Sorry for such questions but I want to try.
Thanks.
New Users Visit this Thread it has less complexity.......
...............................................................................................................................................
GIOPRO v1.4
...............................................................................................................................................
Adobe Flash Player 11.1.102.59 For Galaxy Gio http://forum.xda-developers.com/showpost.php?p=19623732&postcount=1
------------------------------------------------------------------------------------------------------------------
This Thread, Samsung Galaxy Gio gt-s5660 | Firmware Releases ,Custom Roms , Rooting, has been moved from the Android Software and Hacking General forum to the Galaxy Gio GT-S5660 Android Development forum.
NOTE:Even though it has been moved its a redirect notice (expires in 1 week) in the original forum so users Bookmark the New thread link.
-------------------------------------------------------------------------------------------------------------------
Android 2.3.7 - Cyanogen Mod 7.1.0 For Galaxy GIO (Unofficial) By- phiexz
--------------------------------------------------------------------------------------------------------------------
(Devs Only)How To compile a Kernel for Samsung Galaxy Gio By Delanoister
-------------------------------------------------------------------------------------------------------------------
Update.zip Recoveries (For Software installation through recovery) Thanks to ZimniY
------------------------------------------------------------------------------------------------------------------
Everyone vote for official cyanogenmod at the cyanogen mod forum
http://forum.cyanogenmod.com/topic/22386-samsung-galaxy-gio-gt-s5660
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------------
Read this thread thoroughly,Before Asking your question, Most of your questions are answered , but if still have confusion don't hesitate to ask
Users with Galaxy Gio Gt-s5660M/L/V , do not try Custom Roms , Please Read the S5660M Section First.
----------------------------------------------------------------------------------------------------------------------
phiexz's Custom Kernels for Galaxy Gio (For 2.3.5 )
------------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------
Developers/Moders Can PM me their Thread Links If they want it to be on This Main page
-------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------
Modified mms.apk for Samsung Galaxy Gio S5660 (For odexed roms only, not for deodexed) Here
--------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------
hyriand's Custom roms for Galaxy Gio are here
--------------------------------------------------------------------------------------------------------------------
Particle Android Custom Rom based on 2.3.5 , detail here---- download latest version
--------------------------------------------------------------------------------------------------------------------
All actions ,flashing and other modification on your phone you do at your own risk and responsibility for your actions and you are solely if you are unsure of your actions - do not!
Any attempt to flash through RomManager will take you to the service center
-------------------------------------------------------------------------------------------------------------------
This thread is collection of all available data about samsung galaxy gio,so it may save time for others , some intial data is copied from another thread by strunkie for that all cradit goes to him , Data has been copied with the permission of Strunkie.
___________________________________________________________________________________________________________________________
If it helps ,Don't forget to press Thanks
--------------------------------------------------------------------------------------------------------------------------
Welcome in the Thread for Samsung's Galaxy Gio (S5660)
---------------------------------------------------------------------------------------------------------------------------
Samsung Galaxy Gio Unlocking
http://forum.xda-developers.com/showthread.php?t=1204705
---------------------------------------------------------------------------------------------------------------------------
Flashing Samsung Galaxy gio using ODIN
http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
---------------------------------------------------------------------------------------------------------------------------
How to Root Samsung Galaxy gio
http://forum.xda-developers.com/showpost.php?p=16979919&postcount=550
---------------------------------------------------------------------------------------------------------------------------
How to create ext2 partition for a2sd darktremor
http://forum.xda-developers.com/showpost.php?p=16979957&postcount=551
--------------------------------------------------------------------------------------------------------------------------
How to Enable a2sd darktremor on 2.3.3/2.3.4/2.3.5
http://forum.xda-developers.com/showpost.php?p=16979976&postcount=552
-------------------------------------------------------------------------------------------------------------------------
Custom Roms/ Modified Roms
http://forum.xda-developers.com/showpost.php?p=16979810&postcount=548
-------------------------------------------------------------------------------------------------------------------------
Firmwares(Official unmodified):
http://forum.xda-developers.com/showpost.php?p=16979769&postcount=547
------------------------------------------------------------------------------------------------------------------------
Ram Optimizer Script by Juwe11
http://forum.xda-developers.com/showpost.php?p=16979996&postcount=553
-----------------------------------------------------------------------------------------------------------------------
Updating failed using KIES ???
http://forum.xda-developers.com/showpost.php?p=16980019&postcount=554
----------------------------------------------------------------------------------------------------------------------
Custom bootanimation and apk lost post
http://forum.xda-developers.com/showpost.php?p=16980043&postcount=556
---------------------------------------------------------------------------------------------------------------------
How To Deodexing + Zipaligning Galaxy Gio GT-S5660 Tutorial(cradit goes to djjonastybe)
--------------------------------------------------------------------------------------------------------------------
Update apps using recovery method
http://forum.xda-developers.com/showpost.php?p=16980103&postcount=558
-------------------------------------------------------------------------------------------------------------------
ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
------------------------------------------------------------------------------------------------------------------
Compass Fix for s5660
http://forum.xda-developers.com/showpost.php?p=17203899&postcount=813
------------------------------------------------------------------------------------------------------------------
Galaxy Gio 5660m SECTION here
-----------------------------------------------------------------------------------------------------------------
Samasung Galaxy Gio S5660m Brightness ,diming issue solved
http://forum.xda-developers.com/showthread.php?t=1233719
----------------------------------------------------------------------------------------------------------------
Samsung Galaxy GIo S5660M Canada Bell Edition
http://forum.xda-developers.com/showpost.php?p=17332208&postcount=1013
----------------------------------------------------------------------------------------------------------------
Common Issues and possible solutions / tips and tricks
Common Issues and possible solutions / tips and trick
shutdown/freeze randomly in your pocket
. Change your Wifi sleep policy to Never, put a small paper behind the battery some times battery gets loose , if problem stays fectory reset and install latest firmware and fectory reset yet again ..
rooted phone and upgragde gingerbread,but still having problem about bootanimated
Install Root explorer and you need to select "remount as r/w".
command on adb shell to replac framework-res.apk?
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
then:
cp /sdcard/framework-res.apk /system/framework/
#reboot (bootloop posibility if framework doesnt match)
Poor Battery Life
Install latest firmware , turn of wifi when not using , try to charge with wall Charge some times data cable don't charge the properly, And don't forget to clean Ram after using apps , it helps to reduce load on device.
Compass doesn't work anymore
Its a bug , there is no solution availble yet , as soon something comes out i'll post here.
Is there a possibility to overclock samsung galaxy Gio
Nop overclocking isn't working with gio yet.
What is the code for fectory reset
Put your phone in recovery mode (By holding home button+Power button) and select fectory reset option from there or if your phone is on use this code
*2767*3855# Fectory reset will remove all your data from the phone, apps , gallery , contacts and messages be sure to make a backupHow to check your firmware version
*#1234# OR Goto setting<About<Scroll down and check
How to put Gio to downloading mode to flash a firmware by ODIN
shut down your phone , hold home button+power button+volume down button altoghether.
How to Restart your phone (without turn on and off)
Volume down + Volume up + Power button hold untill phone goes off it will turn back again itself.. Or use adb , or terminal emulater , type su then type reboot
How to Remove boot up sound??
Delete file /system/etc/poweron.ogg using root explorer.
What is a2sd darktremor and why should i install it ???
a2sd darktremor let you install your all apps on sd card , so in this way internal memory stays empty and phone perform better than stock rom...
I want to Flash my phone , What should i do after and before???
you always have to fectory reset before and after flashing , when you done flashing you need to root(most of custom roms are already rooted so skip to next step) now you have to enable (a2sd daktremor if its not enabled in a custom rom you have to do it manually) . thats it , now you can start restoring your data , and install apps ...
Compass Fix for s5660 (tested on all versions)
Make sure to bakup your old memsicd before doing anything .
UPDATED:Latest Compass Fix .
http://www.mediafire.com/?2tbx9zhp2hnmc40
Thanks to mozgoder for leting me know
Instructions
Method 1 : download the update, and copy to sd card root directory(don't not copy in any folder)
Put your phone into recovery mode(turn off your phone , HOLD home button + power button toghether)
Apply update from sd , locate the copied file and press home button. reboot.
You have to Reboot twice otherwise it will show wrong direction. Recalibrate your compass by typing *#0*# , click on sensor , and now hold your phone and rorate it 8 ways moving your wrist or watch video below
Compass Calibration
NOTE: if this update doesn't work for you , you can try this one
http://www.mediafire.com/?t1hszgxzb56os2b
----------------------------------------------------------------------------
After doing all the stuff you still getting issue , please check the permissions by opening (use root explorer) system/bin/memsicd press for few seconds a list will open goto permissions and check
Permissions has to be rwxrwxrwx
Updates
10/08 - Update Market , Maps and Samsung apps Manually Using recovery method
11/08 - a2sd darktremor installing and enabling
11/08 - Added Custom Roms
11/08 - Flash Player 10.1 for galaxy gio Download (May not work on all roms)
12/08 - Samsung Galaxy Gio Unlocking(Thanks to Jc_master)
18/08 - Custom Rom added with video review (rooted,deodexed,a2sd darktremor,ram script added,custom boot animation)
19/08 - Custom Rom added GIO PRO 1.2 (Minor bug fix,MIUI Music,Maps 5.8.0,New Market,SuperUser 3.0,Blue Theme) by Rachmat
19/08 - Ram Optimizer Script Updated (18-08-11) Thanks to Juwe11
19/08 - New Stock Roms added S5660XXKPL (2.3.3)2011 July 29 - S5660XXKPM (2.3.3)2011 August 6 --- Password (samsung-firmwares.com)
20/08 - Video Added (How to create ext2 partition)
20/08 - 2 Video Review added of GIOPRO v1.2
20/08 - Added Video Tutorial Flashing Samsung Galaxy gio using ODIN
21/08 - Added Custom Rom (SimpliGio Plus)
22/08 - GioPro v1.3 (Update using Recovery) You must have Giopro v1.2 already installed
22/08 - Video Review added (Mixture of SimpliGio+ and GioProV1.3)
23/08 - Video Tutorial Added (How to Change Boot animation on 2.2.3 and 2.2.4)
24/08 - Custom Rom added (GioPro V1.2 LITE version(improved version of giopro v1.2 , although you can update with giopro v1.3)) Thanks to ZimniY
25/08 - Finally Compass Issue Solved
26/08 - ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660(Credits to tjstyle and ilarrain and thanks to hyriand)
29/08 - New custom rom (GringoPro -Autodeodex Mod) by r33p
02-09-11: Added Stock Rom S5660XXKQB_S5660XXKQ5_S5660PRTKQ4 (20th August 2011)
06-0-11 : How To Deodexing + Zipaligning Galaxy Gio GT-S5660 Tutorial(cradit goes to djjonastybe )
08-09-11 : Latest 5660XXKQB_S5660XXKQ5_S5660PRTKQ4 got a2sd enabled
08-09-11 : Added SimpliGio.v.1.2 by ge88 @kaskus.us(Custom based on XXKQ6)
16-09-11 : A2sd Gui Update available in market
16-09-11 : Stock Rom Added to Stock Rom Section (S5660XXKQG_S5660SEBKQ1)
18-09-11 : Galaxy Gio S5660][ROM] Jonas Hendrickx's ROM v2.1 [2.3.4][XXKQG]
01-10-11 2.3.5 Unofficial Stock Rom added
i downloaded the KP1 tar file(S5660XXKPE_S5660XXKPA_S5660OXFKP1), n used odin1.85, i connect the phone in download mode.
but it stuck at:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
which part i did wrong?
minjiet said:
i downloaded the KP1 tar file(S5660XXKPE_S5660XXKPA_S5660OXFKP1), n used odin1.85, i connect the phone in download mode.
but it stuck at:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
which part i did wrong?
Click to expand...
Click to collapse
Download Odin 4.42(from the guide how to flash galaxy gio using odin) and Do a fectory reset in recovery mode and then try to flash it ...
.tar file is a single flash file , don't unzip it , and don't forget to click on one package on ODIN ,and locate .tar flash file and start .
nevermind..
sori.. I dont read the older thread... so i don't know our older thread is closing...
@waqasshahzad1986, maybe it's better to remove the "Remove simlock" link on the first post. That method has been deleted by the author because it on a lot off phones the efs partition got corrupted making the phone completely useless.
could somebody write down what is the modification in the modifyed offical 2.3.4? i dont find any info for it.
DeXeS said:
@waqasshahzad1986, maybe it's better to remove the "Remove simlock" link on the first post. That method has been deleted by the author because it on a lot off phones the efs partition got corrupted making the phone completely useless.
Click to expand...
Click to collapse
New Link Updated
Sent from my GT-S5660 using XDA Premium App
laalee said:
could somebody write down what is the modification in the modifyed offical 2.3.4? i dont find any info for it.
Click to expand...
Click to collapse
Modification is only in code nothing look different . No compass issue solved.. only improvements are done..
Sent from my GT-S5660 using XDA Premium App
Ok, is there some trick to shut the hardbutton of the volume down.
Sometimes i dont hear the phone go of, i pused that darn button again by acident.
So is there a methode to bypasse that hardbutton?
laalee said:
could somebody write down what is the modification in the modifyed offical 2.3.4? i dont find any info for it.
Click to expand...
Click to collapse
Yes, Waqas,kindly advise if the official modified 2.3.4 is better than the 23 July unofficial 2.3.4 ROM, please? My main reason for upgrading is to avoid the random shutdowns which have`worsened after upgrading to 2.3.3.
Is the modified official 2.3.4 better than the unmodified unofficial 2.3.4?
earthling3m said:
Yes, Waqas,kindly advise if the official modified 2.3.4 is better than the 23 July unofficial 2.3.4 ROM, please? My main reason for upgrading is to avoid the random shutdowns which have`worsened after upgrading to 2.3.3.
Is the modified official 2.3.4 better than the unmodified unofficial 2.3.4?
Click to expand...
Click to collapse
In my experience and observation , its better but don't mark my words , try it , there is no harm to try it ....
I have been reading your problem since your first post ...
Please follow these steps..
Do a fectory reset , Install modified 2.3.4
after flash completes (never dissconnect your device until 'PASS' is written on ODIN)
Do a fectory reset again ...
In WIFI settings , set sleep to never ... and connect with your regular wifi router , for all other connections must click forget
I have faced same problem but i alwasy fectory reset before and after flashing it avoids glitches ..
rendom shut down could be due to hardware or software , i have told you software solution , hardware problem could be with wifi chip , and quick tip put a small paper behind your battery , sometimes bettery gets loose and it could cause rendom shut down , and freez...
is there a way to disable sound of volume buttons in stock rom?
Sent from my GT-S5660 using Tapatalk
laalee said:
could somebody write down what is the modification in the modifyed offical 2.3.4? i dont find any info for it.
Click to expand...
Click to collapse
try this one.......
this rom was modded by ge88
Custom ROM based on S5660XXKQ6 (2.3.4) >>> SimpliGio
Changelog:
Code:
- Rooted
- Support link2sd
- Support custom boot animation.
- CRT Animation
- Tweak script added (increased performance).
[B][U][COLOR="Red"]Removed Stock apps :[/COLOR][/U][/B]
* Dual Clock
* Email (if u need it back. please download [URL="http://www.mediafire.com/?468o38mz9zlk9vu"]this[/URL] and restore using titanium backup.)
* Forest
* Home screen tips
* News & Weather
* Samsung account
* Samsung Apps
* Samsung Home (Touchwiz Launcher)
* SNS
* SNSAccount
* Social Hub
* Software update
* Yahoo Finance
* stock Swype
[B][U][COLOR="Red"]Added apps :[/COLOR][/U][/B]
* TagHome 2.9.3 (as default launcher )
* Swype 3.6 (with Bahasa support).
* Google Maps 5.8.0
Code:
[CENTER][IMG]http://i1081.photobucket.com/albums/j357/Angga_Bastian/SimpliGio/SC20110807-152328.png[/IMG]
TagHome
[IMG]http://i1081.photobucket.com/albums/j357/Angga_Bastian/SimpliGio/SC20110807-152338.png[/IMG]
Application Drawer TagHome
[IMG]http://i1081.photobucket.com/albums/j357/Angga_Bastian/SimpliGio/SC20110807-152426.png[/IMG]
SimpliGio.v.1.0
[IMG]http://i1081.photobucket.com/albums/j357/Angga_Bastian/SimpliGio/SC20110807-152406.png[/IMG]
[IMG]http://i1081.photobucket.com/albums/j357/Angga_Bastian/SimpliGio/SC20110807-152414.png[/IMG]
[IMG]http://i1081.photobucket.com/albums/j357/Angga_Bastian/SimpliGio/SC20110807-152909.png[/IMG]
Swype 3.6 with Bahasa support
[IMG]http://i1081.photobucket.com/albums/j357/Angga_Bastian/SimpliGio/SC20110807-154100.png[/IMG][/CENTER]
- Enable A2sd Darktremor
Steps =
** SDCard must have 2 parttion FAT32 (Primary) and EXT2 (Primary, Cluster Size 4kb).
** Download Darktremor A2sd + a2sd_enabler.sh and extract to sdcard.
** (Just in case, If u have root explorer app make sure the /system/ "Mounted as R/W"))
** open command prompt
Code:
adb shell
su [COLOR="Red"](look on gio screen and choose allow) [/COLOR]
cd sdcard
sh a2sd_enabler.sh
df ([COLOR="Red"]find the "/system/sd.........", if don't show up. open again Root Explorer make sure the [B]/system/[/B] "[B]Mounted as R/W[/B]")
and repeat the process[/COLOR])
reboot recovery
The screenshot (look at the "/system/sd" lines) =
Code:
C:\Users\xxxx>adb shell
$ su
su
# cd sdcard
cd sdcard
# sh a2sd_enabler.sh
sh a2sd_enabler.sh
Remounting system partition as read/write..
Mounting SD card ext2 partition..
DONE: Now you can install Darktremor's a2sd, nJo
# df
df
Filesystem Size Used Free Blks
/dev 139M 32K 139M 4096
/mnt/asec 139M 0K 139M 4096
/mnt/obb 139M 0K 139M 4096
/cache 25M 24K 25M 4096
/data 180M 65M 115M 4096
/system 208M 174M 33M 4096
[B][COLOR="Red"]/system/sd 524M 210M 313M 4096[/COLOR][/B]
/mnt/sdcard 6G 5G 1G 4096
/mnt/secure/asec 6G 5G 1G 4096
# reboot recovery
reboot recovery
** In recovery console apply update from sdcard and choose :dtapps2sd-2.7.5.3-beta04-signed.zip, reboot.
** After boot open again command prompt or Terminal Emulator, to check the "a2sd"
Code:
adb shell
su
[COLOR="Red"][B]a2sd check[/B][/COLOR]
The screenshot (look at the red color line) =
Code:
C:\Users\xxxx>adb shell
$ su
su
# a2sd check
a2sd check
[ ] GREP: Using ROM Busybox.
[ ] REBOOT: Using ROM Busybox.
[ ] FDISK: Using ROM Busybox.
[ ] CAT: Using ROM Busybox.
[ ] MKDIR: Using ROM Busybox.
[ ] RMDIR: Using ROM Busybox.
[ ] CHMOD: Using ROM Busybox.
[ ] MOUNT: Using ROM Busybox.
[ ] UMOUNT: Using ROM Busybox.
[ ] CP: Using ROM Busybox.
[ ] RM: Using ROM Busybox.
[ ] MV: Using ROM Busybox.
[ ] LN: Using ROM Busybox.
[ ] MORE: Using ROM Busybox.
[ ] MKNOD: Using ROM Busybox.
[ ] AWK: Using ROM Busybox.
[ ] SLEEP: Using ROM Busybox.
[ ] SYNC: Using ROM Busybox.
[ ] TEE: Using ROM Busybox.
__ _____
| \ |
| | |
|__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30)
[-] Checkpoint 1: Check for SD Card Fix and Implement.
[-] Checkpoint 2: Run Dalvik Heap Program (if exists).
[-] Checkpoint 3: Run Set Low Memory Killer Program (if exists).
[-] Checkpoint 4: Determine Mount Point.
[-] Checkpoint 5: Set Parameter Variables.
[ ] GetProp Command = /system/bin/toolbox getprop
[ ] SetProp Command = /system/bin/toolbox setprop
[ ] Mount Point = /system/sd
[-] Checkpoint 6: Insert CyanogenMod patch.
[ ] Creating /cache/dc
[ ] Symlinking /cache/dalvik-cache to /data/dalvik-cache
[-] Checkpoint 7: Complete Dalvik Cache Move (if applicable).
[-] Checkpoint 8: Resetting Dalvik Cache Partition
[-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable)
[-] Checkpoint 10: Checking for existence of command parameter
[-] Checkpoint 11: Check for a2sd help command
[-] Checkpoint 12: Check for a2sd check command
[ ] Starting Apps2SD Check Program.
Darktremor 2.7.5.3 Beta 4a Apps2SD Status Report
============================================================================
===
Legend: [G£ö]=Setting is correct
[GÇ+]=Setting is correct, but not optimal.
[G£û]=Setting is incorrect and needs to be fixed or option is not av
ble.
============================================================================
===
[COLOR="Red"][B]Block Device - [G£ö] /dev/block/mmcblk0p2
Mount Point - [G£ö] /system/sd
Support EXT2? - [G£ö] Yes[/B][/COLOR]
Support EXT3? - [G£û] No
Support EXT4? - [G£û] No
Apps - [ ] Linked to SD Card.
[ ] No Apps2SD Flag File not found.
[G£ö] Programs run from SD card
To run from internal storage, type a2sd remove
Private Apps - [ ] Linked to SD Card.
[ ] No Apps2SD Flag File not found.
[G£ö] Private Programs run from SD card
To run from internal storage, type a2sd remove
Dalvik Cache - [ ] Regular directory.
[ ] Dalvik to /cache flag file not found.
[ ] Dalvik to SD flag file not found.
[G£ö] Dalvik runs from Int. Storage.
To run from SD card, type a2sd cachesd.
To run from /cache partition, type a2sd cachep
Data - [ ] Program Data on Internal Storage.
Swap - [ ] Partition not present or no swap support.
[G£ö] Swap does not start.
ZipAlign - [G£ö] Not running at boot.
To activate it, type a2sd zipalign
Dalvik Heap(MB) - [G£ö] 64m
Low Memory
Killer Settings - [G£ö] 1536,2048,6144,8192,12288,15360
Note: Values are in pages.
1 page = 4KB memory.
Values represent the following:
1st number = Foreground App
2nd number = Visible App
3rd number = Secondary Server
4th number = Hidden App
5th number = Content Provider
6th number = Empty App
[Güç] For a list of commands that you can use with Apps2SD
Type: a2sd help
** Activate the a2sd using "a2sd cachesdreset". Or "a2sd datasd" if u like the extreme a2sd.
+++(Optionally, activate a2sd using A2sdGUI
klebengan said:
Custom ROM based on S5660XXKQ6 (2.3.4) >>>
Click to expand...
Click to collapse
That's some nice and clean ROM! What program's did you use to cook this if I may ask?
kajjtan said:
is there a way to disable sound of volume buttons in stock rom?
Sent from my GT-S5660 using Tapatalk
Click to expand...
Click to collapse
No, not that i found.
But you can change or replace the audio.ogg files.
If you reedited them with a somekind of audioediting program, you can create your own sound or you can change ( the volume ) the original ones.
...................don't fotget to backup the originals first..............
DeXeS said:
That's some nice and clean ROM! What program's did you use to cook this if I may ask?
Click to expand...
Click to collapse
not mine bro, its actually mod by a friend of mine (ge88) an active modder in "the biggest forum in indonesia". u can check this GIO's thread here. i am sure the main cooking process using the Linux.
klebengan said:
not mine bro, its actually mod by a friend of mine (gupan88) an active modder in "the biggest forum in indonesia". u can check this GIO's thread here. i am sure the main cooking process using the Linux.
Click to expand...
Click to collapse
@Klebengan Thanks for sharing i am also flashing it , will post results ..
@EVERYONE : Please don't forget to visit the main page every day i am puting alot of updates on the main page , always check the changes i update on dailly basis..
here is the guide
http://forum.xda-developers.com/showpost.php?p=24747881&postcount=4
thakz irfanbagus for the guide
where's the package link?have you try this guide by yourself?
i hope he tried
got a ubuntu, i will try this one (cross-fingers)
it's not working. sgy stock kernel do not have /proc/config.gz and gcc version in arm-2011.03 not compatible with other precompiled module.
this is work for me
requirement :
1. linux box 32 bit with working gcc. you can use real linux machine or virtual machine
2. Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI from http://www.codesourcery.com/ (Linux version without installer arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2)
3. mkbootimg with md5support. got it from http://forum.xda-developers.com/showpost.php?p=22224170&postcount=241 . credit to harish2704
4. split_bootimg.pl (google it)
5. kernel source from http://opensource.samsung.com . i use GT-S5360_GB_Opensource_Update2.zip
6. stock boot.img (or from your custom kernel).
step :
1. make folder "sgy" in your home. the result is folder "/home/<yourname>/sgy". <yourname> is your linux user name, and from now replace <yourname> with your user name. put all file you already download there
2. extract "GT-S5360_Kernel.tar.gz" from "GT-S5360_GB_Opensource_Update2.zip". put also in "sgy" folder
3. open terminal emulator and go to your working path with command
Code:
cd ~/sgy
4. extract your compiler with
Code:
tar -xvf arm-2009q3-68-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
5. create folder "kernel" and extract kernel source there
Code:
mkdir kernel
cd kernel
tar -xvf ../GT-S5360_Kernel.tar.gz
you got 2 folder, "common" and "modules"
6. open folder "common", there is file "Makefile". open with text editor and find line with content "/opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-". replace with "/home/<yourname>/sgy/arm-2009q3/bin/arm-none-eabi-", don't forget replace <yourname>.
7. in terminal goto folder "common" and load default config for sgy
Code:
cd ~/sgy/kernel/common
make bcm21553_totoro_05_defconfig
8. if you want change you config run
Code:
make menuconfig
9. if you ready to build then run
Code:
make
or if you have dual core cpu and want to make it faster
Code:
make -j3
10. when complete and no error appear, copy your kernel to "sgy" folder
Code:
cp arch/arm/boot/zImage ~/sgy
11. extract ramdisk from your boot.img
Code:
cd ~/sgy/
perl split_bootimg.pl boot.img
you got "boot.img-kernel" and "boot.img-ramdisk.gz". move "boot.img" and "boot.img-kernel" to other place.
12. repack your new kernel and ramdisk. but first get md5sum of your new kernel
Code:
md5sum zImage
you got something like
Code:
1fd319aa60abc2abae2e5932bcb9fc77 zImage
you need that "1fd319aa60abc2abae2e5932bcb9fc77" write it or copy to text editor. you need run it every time compile new kernel
13. repack
Code:
chmod +x mkbootimg
./mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --base 0x81600000 --kernelMD5 <your md5sum result> -o boot.img
14. make odin flash-able
Code:
tar -cf boot-sgy.tar boot.img
I thought you have to put your post into a new thread irfan...this one is a fake guide.
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
kurotsugi said:
offtopic:
btw, do you know who's working on cm7 from source with motafoca?his thread is missing and I just get curious on their progress.
Click to expand...
Click to collapse
His thread was closed by moderator.You can request MOD to reopen his thread.Motafoca wanted a galacy y to be lended for his experiments
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
Can someone download the sources around 15Gigs and stripe down the file and share it to Maroc ?
Whre can i download it?
Sent from my GT-S5360 using xda premium
kurotsugi said:
I thought you have to put your post into a new thread irfan...this one is a fake guide.
Click to expand...
Click to collapse
i don't call it fake. it's just too general and missing some detail (but critical) for our device. and in the 'spirit of operation iron fist', i think it's better to put here
premolikeshtc said:
Irfan must create a guide.yes yes..I also think Irfan sahab must compile a CM7.2 from sources.
Click to expand...
Click to collapse
with my internet connection, it will take weeks just to download the source. and i think cm, like android source, use repo. so you can't just download it. you clone it from their source repository, that mean no download accelerator.
btw beside kernel source, samsung also release their mod to android source. but to build it, you still need to get android source (about 10GB according their website).
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
kurotsugi said:
well...thats your choice, irfan.
@sgy.creed: sorry, I don't mean to offend you. IMHO it will be nice if before someone post any guide they already have tested it by them. in this way, they'll able to give more accurate direction to anyone who need their guide. as we already know, kernel is crucial part in our device. any mistake in compiling it will lead to brick our device. we have to cautious on it. peace ^,^v
Click to expand...
Click to collapse
if you (or others) think it's better to put in other thread, or maybe op wanna edit his post, fell free to copy my post (or just link, it's up to you). i don't take any credit to that post, because it just recompilation from other thread.
GT-B5510
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Rui Oliveira 21 said:
Is there by chance anyway to find a stock Kernel for my device for my GT-B5510???
I recently flashed a custom Kernel for GT-S5360 and the result was a Brick.
is there someone willing to help me??
Click to expand...
Click to collapse
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
sgy.creed said:
Hi guys,
This guide teaches how to make a new kernel for your device, it works in most of the cases but doesnt mean it will work for everyone
You need a minimal linux experice to know WTF you are doing
If you have any questions, post Belloowww
Download the required files
You will need a linux machine with the basic development tools or a virtualbox machine running a linux distribution (ubuntu 64bits will do fine)
I use the codesourcery package
Download the IA32 GNU/Linux TAR
The tar package is the easier to install
You will also need your kernel source from your manufacturer, for samsung the sources are available here
Install the cross compiler
Enter the folder were you downloaded the package and extract it, you will get something like arm-2011.03
Move that folder to some location, i use opt
ex: mv arm-2011.03 /opt/
or
sudo mv arm-2011.03 /opt
Done!
Extract and prepare the kernel sources
I will use the samsung sources as example, but anything can be used
For the samsung sources, after you extract the zip, you will get something like DEVICE_Platform.tar and DEVICE_Kernel.tar.gz
Extract the kernel:
tar zxvf DEVICE_Kernel.tar.gz
Enter the kernel folder and list the folder contents
ls
The structure is something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Most devices contain the config file inside the device
You can extract it like this:
adb shell
su
cp /proc/config.gz /sdcard/
exit
exit
adb pull /sdcard/config.gz
Good, now we have the sources, compiler and configuration
Compiling the kernel
To compile ther kernel, i usually clean the sources first, with this i know for sure nothing will go wrong (usually )
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- distclean (Remember to replace acordingly the compiler folder)
Sources cleaned, time to load the config file
gunzip config.gz
cp config ./.config
Good, now lets check the menuconfig (menuconfig is a menu to choose the kernel options, created to make it easy to select)
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- menuconfig
Change whatever you want and exit and save
good, now its time to build
make ARCH=arm CROSS_COMPILE=/opt/arm-2011.03/bin/arm-none-eabi- -j2
Now wait for it to finish!
Your compiled kernel will be located inside arch/arm/boot/zImage
Extracting a boot.img
Good, now we have the zImage, but WTF to do with it?
Well, android usually (some samsung devices use a different boot.img method, ex: I9000) has the boot.img, inside of it we contain:
- ramdisk (required files to load the /system partition and continue the boot sequence)
- zImage (our kernel)
- pagesize
- base
- cmdline (some kernel paremetes used on boot)
To create your own boot.img, you need one from a nandroid backup that was made from CWM or AmonRA custom recoveries (there are other methods, but for those use the madteam forum )
The boot.img is located inside your /sdcard/clockworkmod/backup/somedate/boot.img
You will also need the unpackbootimg and mkbootimg binaries, i this link there is the 64 bit version (wont work on 32 bit linux)
create an empty folder, copy the downloaded file inside, enter it and do:
tar zxvf bootimgtools.tar.gz
chmod 755 *
now copy the boot.img you got from the backup
and extract the boot.img with:
./unpackbootimg -i boot.img
this will create the files as explained above
Creating the boot.img
Before making the boot.img, we need some information from the files extracted
cat boot.img-base ( save the output #1)
cat boot.img-pagesize (save the output , place the value inside the Hex Value of this site, and copy the decimal value and save it #2)
cat boot.img-cmdline (save the output #3)
Good, now copy the compiled kernel (zImage) inside the current folder and do:
mkbootimg –kernel zImage –ramdisk boot.img-ramdisk.gz –cmdline “(replace with output#3)” –base (replace withoutput #1) –pagesize (replace with output#2) -o /tmp/boot.img
Good, the boot.img is created!
Now test on your device!
If you dont know how to flash the boot.img, enter the madteam forum and request help (its too difficult to explain the flashing of boot.img if you dont know how to do it )
Take care!
<External link removed>
Click to expand...
Click to collapse
please credits motafoca madteam
GT-B5510
Harsh06 said:
Have u tried through kies?if the answer u failed then only odin is the way.
u need pda files from the update.Search google,i found one FW but it is from Italy :
B5510CEKK1.
Click to expand...
Click to collapse
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Rui Oliveira 21 said:
Kies said that I had the most recent firmware, tough I found some new versions.
right now trough kies I tried to do an emergency firmware restore, i guess thats the name, but it asked for a code, a 4 number code i guess and i dont know what's the code.
Via odin I tried to install stock firmware from sammobile but it failled as well, if you want I'll post the dialog from odin.
I can boot in recovery mode, Odin(download) mode and CWM mode.
could you point me in the right direction???
thanks for your time
Click to expand...
Click to collapse
I believe Doky already reply your post n willing to help u in others thread.Give doky some info about your current FW.U need 3 complete files n flash through Odin.Key in *#1234# with your dialer(u will see current info version) and PM doky about the info.He surely gonna help u.
Sorry OP off topic.
GT-B5510
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Kernel
How to change Kernel Version when build kernel ??
usually display 2.6.35.7 [email protected] #1
i wanna change [email protected] #1 so how the setting on linux or maybe what file??
Thanks b4
Rui Oliveira 21 said:
He did help, thanks
question now is...while trying to revive the phone I installed Creed's Rom for Gt-s5360, I got quiet, and obviously it doesnt work that well in my GT-B5510, so I need a custom Rom for my device or a Stock Rom, but I cant find neither :S
any lights??
Click to expand...
Click to collapse
I was just wondering if you went to the oldest possible firmware you could find and then proceeded to update from that. Sometimes the updates only contain necessary info and kind of rely on the previous installs.
Sent from my TF101 using Crashntalk 2
ANYKERNEL
tuna (maguro / toro / toroplus)[#WARRANTY]
It is difficult to update all Roms frequently, and it does not always makes sense to compile, download and flash a whole rom, if only some kernel changes are applied.
This kernel will include changes before we add them official to our kernel source on Unlegacy-Android (most of the time security bugfixes)!
Android 5.1, Android 6.0 and Android 7.x
This Kernel should work on all Android 5.1, Android 6.0 and Android 7.xRoms
Android 4.4
On Android 4.4 we need a different kernel, 4.4 Kernel includes "KitKat" tag on zip name.
What else to say
Kernel compiled using GCC 4.7
Anykernel based on Anykernel2 by @osm0sis ( https://github.com/osm0sis/AnyKernel2 ) - it will dump your boot.img and replace the zImage and add proper kernel modules.
Roms with default libion
LineageOS (unofficial)
lineage-13.0_maguro-6.0.1-20180130-2235.zip and newer
lineage-13.0_toro-6.0.1-20180130-2258.zip and newer
lineage-13.0_toroplus-6.0.1-20180130-2323.zip and newer
OmniRom (unofficial)
OmniRom 4.4: omni_tuna-4.4.4-20180128-0005.zip and newer
OmniRom 6.0: omni_tuna-6.0.1-20180128-0334.zip and newer
OmniRom 7.x: omni_tuna-7.1.2-20180128-1348.zip and newer
SlimRoms (unofficial)
Slim6: Slim_tuna-6.0.1-20180128-2356.zip and newer
Slim7: Slim_tuna-7.1.2-20180131-1640.zip
Unlegacy-Android:
All official Unlegacy-Android builds starting on 15th feburary use the default libion
On older Roms, using TI's libion, you can use attached kernel from here.
[#DONATETOME]
XDA:DevDB Information
(tuna) Anykernel, Kernel for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/Unlegacy-Android/android_kernel_samsung_tuna/tree/staging
Kernel Special Features: Testing before applying on our source official, CVE fixes
Version Information
Status: Testing
Created 2017-06-23
Last Updated 2018-05-09
Reserved
As requested, here's my setup to compile tuna kernel.
01.05.2020
Follow https://github.com/andi34/android_build-bot/blob/manifest/README.md and https://github.com/andi34/android_build-bot/blob/kernelcompile/README.md
What do you need
Kernel Source (you can get our latest kernel source on SlimRoms, OmniRoms or CyanogenMods github, "tuna kernel")
GCC ( https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7 )
pvr source, added to omap4-common device repo and hardware_ti_omap4 repo (can be found on SlimRoms, OmniRoms or CyanogenMods github)
you can use my scripts put below (update some paths, marked red )
AnyKernel2 Source from osm0sis (update for tuna needed)
build-gcc4.7.env
Code:
export CROSS_COMPILE=[COLOR="Red"]'/home/andi/android2/kernelcompile/arm-eabi-4.7/bin/arm-eabi-'[/COLOR]
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm
export ARCH=arm
export STRIP=[COLOR="Red"]/home/andi/android2/kernelcompile/arm-eabi-4.7/bin/arm-eabi-strip[/COLOR]
alias 'stm'='$STRIP --strip-unneeded *.ko'
compile-tuna.sh
Code:
#!/bin/bash
readonly red=$(tput setaf 1) # red
readonly grn=$(tput setaf 2) # green
readonly ylw=$(tput setaf 3) # yellow
readonly blu=$(tput setaf 4) # blue
readonly cya=$(tput setaf 6) # cyan
readonly txtbld=$(tput bold) # Bold
readonly bldred=$txtbld$red # red
readonly bldgrn=$txtbld$grn # green
readonly bldylw=$txtbld$ylw # yellow
readonly bldblu=$txtbld$blu # blue
readonly bldcya=$txtbld$cya # cyan
readonly txtrst=$(tput sgr0) # Reset
err() {
echo "$txtrst${red}$*$txtrst" >&2
}
warn() {
echo "$txtrst${ylw}$*$txtrst" >&2
}
info() {
echo "$txtrst${grn}$*$txtrst"
}
setbuildjobs() {
# Set build jobs
JOBS=$(expr 0 + $(grep -c ^processor /proc/cpuinfo))
info "Set build jobs to $JOBS"
}
info "Kernel source path: $KERNELSOURCE"
info "PVR Source path: $PVRSAUCE"
info "Working directory: $WORKINGDIR"
info "resulting zImage and modules stored at: $WORKINGOUTDIR"
setbuildjobs
info "Moving to kernel source"
cd $KERNELSOURCE
info "Import toolchain environment setup"
info "Toolchain: $TOOLCHAIN"
source $SAUCE/build-$TOOLCHAIN.env
info "Create a buid directory, known as KERNEL_OUT directory"
# then always use "O=$SAUCE/tuna" in kernel compilation
info "create working directory"
mkdir -p $WORKINGDIR
warn "Make sure the kernel source clean on first compilation"
make O=$WORKINGDIR mrproper
warn "Rebuild the kernel after a change, maybe we want to reset the compilation counter"
echo 0 > $WORKINGDIR/.version
info "Import kernel config file: $DEFCONFIGNAME"
make O=$WORKINGDIR $DEFCONFIGNAME
info "Change kernel configuration if needed using:"
info " make O=$WORKINGDIR menuconfig "
info "lets build the kernel"
make -j$JOBS O=$WORKINGDIR
if [ -f $WORKINGDIR/arch/arm/boot/zImage ]; then
info "Copying the resulting zImage and modules to: $WORKINGOUTDIR"
info "Creating directory..."
mkdir -p $WORKINGOUTDIR
mkdir -p $WORKINGOUTDIR/modules
cp $WORKINGDIR/arch/arm/boot/zImage $WORKINGOUTDIR/
find $WORKINGDIR/ -type f -name *.ko -exec cp {} $WORKINGOUTDIR/modules/ \;
info "Files moved!"
info "Pointing KERNELDIR to KERNEL_OUT directory"
export KERNELDIR=$WORKINGDIR
warn "Make sure the PVR source clean."
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Building the PVR module..."
make -j8 -C $PVRSAUCE/build/linux2/omap4430_android TARGET_PRODUCT="blaze_tablet" BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.1
info "Copying the resulting PVR module to: $WORKINGOUTDIR"
cp -fr $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/pvrsrvkm_sgx540_120.ko
mv $PVRSAUCE/binary2_omap4430_android_release/target/pvrsrvkm.ko $WORKINGOUTDIR/modules/
warn "Don't leave any module objects in PVR source!"
warn "Running 'make clean'..."
make clean -C $PVRSAUCE/build/linux2/omap4430_android
info "Properly stripping the kernel modules for smaller size (implified as stm command inside build.env)..."
cd $WORKINGOUTDIR/modules
stm
info "####################"
info "# Done! #"
info "####################"
else
warn "####################"
warn "# FAILED! #"
warn "####################"
fi
cd $SAUCE
tuna_k.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.7"
DEFCONFIGNAME=tuna_kitkat_defconfig
WORKINGDIR=$SAUCE/tuna-kitkat
WORKINGOUTDIR=$WORKINGDIR-bin
. `dirname $0`/compile-tuna.sh
tuna_m.sh
Code:
#!/bin/bash
[COLOR="Red"]SAUCE=~/android2/kernelcompile
PVRSAUCE=~/android2/official/omap4/stable/pvr-source/eurasiacon
KERNELSOURCE=~/android2/official/kernel/android_kernel_ti_omap4[/COLOR]
TOOLCHAIN="gcc4.7"
DEFCONFIGNAME=tuna_defconfig
WORKINGDIR=$SAUCE/tuna-marshmallow
WORKINGOUTDIR=$WORKINGDIR-bin
. `dirname $0`/compile-tuna.sh
Hey together!
We started preparing a common 3.0 omap4 kernel.
I have started applying some small stuff to our current kernel (also reverts some previous commits) which needs testing.
The kernel should work on all L, M and N Roms. Please let me know if you face any new issues.
Android-Andi said:
Hey together!
We started preparing a common 3.0 omap4 kernel.
I have started applying some small stuff to our current kernel (also reverts some previous commits) which needs testing.
Click to expand...
Click to collapse
Thanks for your hard work. I flashed your kernel onto DU 11.5 (Android 7.12). It boots fine and I'm writing this post with this configuration. I will test it during the next days. First difference: Nightlight now works...
Android-Andi said:
Want to support development? You can consider donating, we've spent countless of hours with this
Click to expand...
Click to collapse
@Android-Andi @Ziyan Thank you for your work! I have donated $10 and I hope others will join me to support our developers
Android-Andi said:
Please let me know if you face any new issues.
Click to expand...
Click to collapse
It's running very well but I'm getting battery drain cause of missing deep-sleep-cycles.
@guest4711 maguro?
On toro or toroplus issues i need a dmesg always because i own a maguro only.
Android-Andi said:
@guest4711 maguro?
Click to expand...
Click to collapse
Yes, good old maguro (with baseband I9250XXLJ1, see #3).
@guest4711 attached kernel reverts "cpufreq: interactive: sync with p-android-omap-3.0-dev", let's see if this fixes your issue.
double, ignore
Android-Andi said:
@guest4711 attached kernel reverts "cpufreq: interactive: sync with p-android-omap-3.0-dev", let's see if this fixes your issue.
Click to expand...
Click to collapse
Ok, I'll test it. Simple dirty flashing without any wiping?
guest4711 said:
Ok, I'll test it. Simple dirty flashing without any wiping?
Click to expand...
Click to collapse
Yeah if it's not that i have another idea. My maguro was almost empty, only could quick test wifi, camera, audio yesterday. Charging it now and going to work on it later again.
Android-Andi said:
Yeah if it's not that i have another idea. My maguro was almost empty, only could quick test wifi, camera, audio yesterday. Charging it now and going to work on it later again.
Click to expand...
Click to collapse
Ok. Quick tries to enter deep sleeping show "some devices failed to suspend" in dmesg, see attached log.
guest4711 said:
Ok. Quick tries to enter deep sleeping show "some devices failed to suspend" in dmesg, see attached log.
Click to expand...
Click to collapse
Would it help to log the same with "DU kernel" and post it here? Or do you need other logs too?
guest4711 said:
Would it help to log the same with "DU kernel" and post it here? Or do you need other logs too?
Click to expand...
Click to collapse
One more to test.
Android-Andi said:
One more to test.
Click to expand...
Click to collapse
Keep quite, please - the cpus are sleeping...
One more attached. Almost spend the whole day with it.
Have fun with it!
Android-Andi said:
One more attached. Almost spend the whole day with it.
Have fun with it!
Click to expand...
Click to collapse
Thank you. Installed and running, but need a while for testing it.
Have a nice weekend!
Another one, adds a bunch of zram changes (not enabled - shouldn't hurt) and core parts from galaxy tab2 (shouldn't hurt tuna, but we need to test).