Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
{
"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"
}
Open Sourcing Mediatek - Wiko DarkMoon ; SoC MT6582
Being owner of an Mediatek device, means (most of the times) not having the sourcecode published by the Official vendor.
Wiko only published an faulty source (incompleted, and unbuildable sources).
Furthermore the source is not for our device (its incompleted and belongs to another phone ...)
Well this is xda after all, meaning we can accomplish pretty much everything
This is an fully Custom Kernel Source.
Hello Guys !
In this thread you will find my custom Kernel for the Wiko DarkMoon (and Clones)
Please be sure to read (and re-read) to avoid unnecessary questions.
Changelogs
Changelog v1.2 (February 15 2015)
Toolchain: Now compiled with the Latest Linaro-Cross 4.9.1
Source fixs in order to compile with Linaro's 4.7>+
New compilation build flags (enabled neon/ ffast-math, etc)
Disabled Mediatek debugger daemon aee
Kernel compression LZMA > XZ
Reduce vfs cache pressure to 20
Random: Entropy tweeks
TCP: initial TCP window size lock to 64K
Dynamic Management of dirty page writebacks (Fully controled on Performance Control app / other kernel management apps)
Increase Swappiness 60>70 (Better UI)
vm MAX readahead increase 512>1024
mm: vm MIN readahead increase 16>32
Several MTK Platform Fixs; Bad symbols fixs
Add IO Schedulers:
Sio
row
vr
zen
Add CPU Governors (enabled):
Ondemand
Hybrid
Conservative
Interactive
Changelog v1.1 (10 August 2014)
ToolChain: Mooved to Linaro Toolchain 4.6.4 Cortex Optimized
CPU Governor: Added SmartAss v2
MTK vermagic hack …
VM_MAX_Readahead 128 --> to 512 Kb
Tweak vm dirty ratios
Compile vfp with neon
NOATIME and NODIRATIME by default
Disabled GFS and enabled ARCH_POWER
Optimized SLUB
Asynchronous I/O latency to a solid-state disk greatly increased
Changelog v1.0 (August 06 2014)
Insecured
Persistent ADB
Compiled using GCC 4.6 ToolChain
zImage Compression changed from GZIP to LZMA
VM MAX READAHEAD changed from 128 to 512 Kb
Removed debug Sh##
Merge Userdata Partition + Internal SDCard
GPL Compliance:
Kernel 3.4.5
GitHub Repo
I do respect the GPL, but using someone else's work without proper credits is just LACK OF RESPECT.
The inclusion of this kernel in your ROMS is NOT allowed.
Instead add a link to my kernel thread as a recommendation on your thread.
I Don't support KANGS!
So please Show some respect, when using my commits, as well as the commits i added from other Dev's (with proper credits/ git authorization)
Fail to comply and i will drop this project
Credits:
superdragonpt
Christopher83 For his awesome ToolChains / Dirty Pages writebacks
varun.chitre15 For several MTK commits (git Authoriz)
faux123 For some merged commits
All (common) kernel contributors | www.kernel.org for keeping Linux / Android alive
I would also like to thank:
bgcngm, for the MTK unpack / repack kernel scripts
XDA:DevDB Information
[KERNEL][3.4.5] Wiko DarkMoon (MT6582) | Performance |, Kernel for the Android General
Contributors
superdragonpt
Source Code: https://github.com/dragonpt/Kernel_Wiko_DarkMoon_Custom
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2014-08-06
Created 2014-08-06
Last Updated 2015-02-16
How to Flash You'll need an Custom Recovery:
You can find the latest Carliv Touch Recovery (CWM Based) here
On recovery:
No need to wipe anything
Just Flash the kernel.zip
It wont afect the rom, or your userdata
But Just in case, make an full backup before flash
Download
Kernel Download is available in the XDA: DEVDB
Or
On my dev-Host
KERNEL_Wiko_DarkMoon_v1.2.zip - 4.05 MB
KERNEL_Wiko_DarkMoon_v1.1.zip - 4.21 MB
Notes
When giving feedback, please refer what's the kernel version / Rom your using
YOUR FEEDBACK IS IMPORTANT
F.A.Q
F.A.Q
What's this new Partition Layout thing ?
--> In Order to fix the Bad stock device Layout (having so less space for installing apps), since Wiko choose to have the emmc nand divided into an Internal SD + Userdata.
I Modified the Kernel partition layout, so that both are merged together (and this is the right way)
So.. What do i need to do?
---> If your using the Stock partition Layout, i have included an modified fstab on the rom.zip so that your device dont fall into bootloop ... however only one of the internal partitions will be available
---> I stongly advise that you modified your Device Layout with the internal userdata mod v2 (2.5GB)
--> IF you still find some issues mounting the SD Card (External), there's an alternative patch that you can download and flash on Recovery (EDIT: Merged on Kernel v1.1)
After flashing the internal userdata mod v2, i have "Phone Storage is damage", what Can i do ?
--> You need to reboot into recovery and wipe /data , later you can restore your data in the advanced Restore Option.
How can I change IO Schedulers and Governors ?
--> You can use the Performance Control app to change CPU Governors / IO Schedulers and many other Kernel features.
What's the Best Governor / IO Scheduler?
--> Depends on your needs (Performance; Powersaving; etc)
An good resource, check this This Thread OR Just Google it ...
Great congratulations!
One question: with the partition mod, there's only sdcard storage available?
Gesendet von meinem T0LTE mit Tapatalk 2
After install sdcard with 0mb free. And sdcard1 with external SD. Cannot install nothing.
Have I done something wrong. On 2.5gb mod.
Regards
Obrigado
Sent from my DARKMOON using Tapatalk
DerTeufel1980 said:
Great congratulations!
One question: with the partition mod, there's only sdcard storage available?
Click to expand...
Click to collapse
Hi, yes (check pics)
I could made the External SD Card show as "SD Card" but apps still think that was an Internal SD card..
So i modified the fstab this way, and everything works (keep in mind that for this to work i had to modified the partition.define on kernel source code)
Regards
jcvr said:
After install sdcard with 0mb free. And sdcard1 with external SD. Cannot install nothing.
Have I done something wrong. On 2.5gb mod.
Regards
Obrigado
Sent from my DARKMOON using Tapatalk
Click to expand...
Click to collapse
Hi
There's an new alternative fstab file, that you can download, simply flash on recovery (no wipes required)
Update INFO about this issue.
Thanks for the feedback
Regards
OK. With alternative fstab all work fine.
Thanks.
Regards.
Sent from my DARKMOON using Tapatalk
superdragonpt said:
Hi, yes (check pics)
I could made the External SD Card show as "SD Card" but apps still think that was an Internal SD card..
So i modified the fstab this way, and everything works (keep in mind that for this to work i had to modified the partition.define on kernel source code)
Regards
Hi
There's an new alternative fstab file, that you can download, simply flash on recovery (no wipes required)
Update INFO about this issue.
Thanks for the feedback
Regards
Click to expand...
Click to collapse
Ah, got it. At first I thought you merged [email protected] (I think it is dev/block/mmcblk0p5) with mmcblk0p8 (which is sdcard) to create only one big /data partition. In your rom you then could use sdcard binary (system/bin/sdcard) to map a virtual sdcard from data/media to storage/sdcard0. But that's only theory and I didn't try this.
Btw:
Do you also have a commit history for older changes?
Gesendet von meinem T0LTE mit Tapatalk 2
Good to see kernel development for mt6582! :thumbup:
Can't just imagine that it took 5 mnths compile it! Well to be really honest i think you would have got better feedback if you realeased it for canvas 2 colours and its clones like myphone agua rio, explay fresh, wiko rainbow, qmobile noir i9 etc because it have the most Android development mostly custom roms and users when we talk about mt6582 generally! ( its my opinion )
Dnt know wether we have the sources for our device or not but is there a way that we the users of similar device but much larger screen i.e 5" can take advantage of this kernel sources and its github repo???
I am new to kernel development so plz never mind this comment of mine you are already doing a great job out there once again keep up the good work! :thumbup:
Sent from my Micromax A120 using XDA Free mobile app
DerTeufel1980 said:
Ah, got it. At first I thought you merged [email protected] (I think it is dev/block/mmcblk0p5) with mmcblk0p8 (which is sdcard) to create only one big /data partition. In your rom you then could use sdcard binary (system/bin/sdcard) to map a virtual sdcard from data/media to storage/sdcard0. But that's only theory and I didn't try this.
Btw:
Do you also have a commit history for older changes?
Click to expand...
Click to collapse
Hi
With this modified layout, ebr2 wonr be used (so indeed i merged emmc+mmcblkxx internal SD into one single partition)
I wont be use an virtual SD Card (data/media) that really messes things really bad ...
ON all my source projects i always have an full commit history, but since this was an on going development for many months, it would be virtually impossible to make an full commit history.
Even worse, it would be useless, since you can't make an "diff" with an "original/stock" source, since there's none.
Most of the changes are under mediatek/platform drivers and mediatek/common and device configs.
And thers files are not on my repo, since they are copyrighted (as we all know) and i really dont need (another) DMCA takedown in one of my git repos.
--> In terms of changes in this new MTK platform MT6582/92, you can check both the Makefile, and build script under /kernel they've got several changes/ commits on them to get this source to compile.
I've done the best i could on # comment my changes on the files. (So you'll see a lot of #CM #WIKO DarkMoon .... etc)
Regards
malick186 said:
Good to see kernel development for mt6582! :thumbup:
Can't just imagine that it took 5 mnths compile it! Well to be really honest i think you would have got better feedback if you realeased it for canvas 2 colours and its clones like myphone agua rio, explay fresh, wiko rainbow, qmobile noir i9 etc because it have the most Android development mostly custom roms and users when we talk about mt6582 generally! ( its my opinion )
Dnt know wether we have the sources for our device or not but is there a way that we the users of similar device but much larger screen i.e 5" can take advantage of this kernel sources and its github repo???
I am new to kernel development so plz never mind this comment of mine you are already doing a great job out there once again keep up the good work! :thumbup:
Sent from my Micromax A120 using XDA Free mobile app
Click to expand...
Click to collapse
I usually only release source built works for devices that i own, it would be impossible to work on an device that i do not own...
About "porting":
Keep in mind, that the only common thing is the SoC (MT6582) everything else is different (device sensors/ custom configs and even custom drivers)
But yes, for an developer that knows what his doing, this aditional source, should be usefull
Regards
Camera
Hi guys
I got feedback from some users that some of you can only use the front camera, and you can't see the rear camera.
Let me just tell you, that this is not kernel related, but this depends on the Wiko rom version your using, i also tested and my own custom rom also suffers this minor issue.
Reason why, is that the initial wiko JB 4.2.2 Roms (from Build 8 /9/10/11/12/13) have different camera .blobs that are not compatible with this kernel (and thats why you see an different kernel build on different wiko rom builds), my rom is based on wiko build 8 btw ...
Tomorow i will release an patch (that will be pre-included in future kernel builds) that fixs this issue for all of you.
Regards
Thanks for the feedback
Kernel v1.1
Kernel Build : v1.1
Changelog v1.1 (August 10 2014)
ToolChain: Upgraded to Linaro-Cross Toolchain 4.6.4 Cortex Optimized
CPU Governor: Added SmartAss v2 (Check F.A.Q)
VM_MAX_Readahead: set to 512 Kb (was 128Kb on Stock)
Tweak vm dirty ratios
VFP: Compile with neon now
NOATIME and NODIRATIME by default
Disabled GFS and enabled ARCH_POWER
Optimized SLUB
Asynchronous I/O latency to a solid-state disk greatly increased
Camera (Rear) fix, for older WIKO Rom builds (including my own modded rom) (.blob)
Merged corrected partition table (older alternative fstab.zip)
Regards
Nice work. I've flashed your kernel 1.1 and after that I can't access my sd card. The apps on sd won't run. Can't take screenshots because it's says that don't have a sd card. I'm on latest official rom with your extended data mod with 2gb partition. Can you help me please. Thanks.
edit:
even after a factory reset i'm stuck in bootloop.
I'm using the official wiko tool to flash the original rom and i'll star all over again
any tips to make this work?
edit 2:
after flashing official rom, root, install custom recovery, extended data MOD 2.5gb (previous has 2gb), flashing kernel 1.1... now everything looks fine.
Sent from my Nokia 3310 using my fingers
outcubus said:
Nice work. I've flashed your kernel 1.1 and after that I can't access my sd card. The apps on sd won't run. Can't take screenshots because it's says that don't have a sd card. I'm on latest official rom with your extended data mod with 2gb partition. Can you help me please. Thanks.
edit:
even after a factory reset i'm stuck in bootloop.
I'm using the official wiko tool to flash the original rom and i'll star all over again
any tips to make this work?
edit 2:
after flashing official rom, root, install custom recovery, extended data MOD 2.5gb (previous has 2gb), flashing kernel 1.1... now everything looks fine.
Sent from my Nokia 3310 using my fingers
Click to expand...
Click to collapse
Hi
Thanks for the feedback.
So your saying that:
A) with the Extended userdata Mod v1 (2GB) ---> No SD Card
B) with the Extended userdata Mod v2 (2.5 GB) -- > OK
Myself im using v2, and everything is ok also
this is the best option, since you'll get the full internal memory for apps.
There's a lot of things im working on at the same time for the wiko ... but working with MTK stuff makes it a lot more harder ...
Regards ... and have funn
superdragonpt said:
Hi
Thanks for the feedback.
So your saying that:
A) with the Extended userdata Mod v1 (2GB) ---> No SD Card
B) with the Extended userdata Mod v2 (2.5 GB) -- > OK
Myself im using v2, and everything is ok also
this is the best option, since you'll get the full internal memory for apps.
There's a lot of things im working on at the same time for the wiko ... but working with MTK stuff makes it a lot more harder ...
Regards ... and have funn
Click to expand...
Click to collapse
Pretty much that. It didn't work for me with the 2GB mod, but so far so good with the 2.5gb. Seems to me that I got better ram management with your kernel nice work. If you need testers tell me.
Sent from my Nokia 3310 using my fingers
outcubus said:
Nice work. I've flashed your kernel 1.1 and after that I can't access my sd card. The apps on sd won't run. Can't take screenshots because it's says that don't have a sd card. I'm on latest official rom with your extended data mod with 2gb partition. Can you help me please. Thanks.
edit:
even after a factory reset i'm stuck in bootloop.
I'm using the official wiko tool to flash the original rom and i'll star all over again
any tips to make this work?
edit 2:
after flashing official rom, root, install custom recovery, extended data MOD 2.5gb (previous has 2gb), flashing kernel 1.1... now everything looks fine.
Sent from my Nokia 3310 using my fingers
Click to expand...
Click to collapse
Did you then restore data or you installed apps again
I'm getting Phone storage is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
pren22 said:
Did you then restore data or you installed apps again
I'm getting Phone storage is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
---------- Post added at 08:31 PM ---------- Previous post was at 08:18 PM ----------
Did you then restore data or you installed apps again
I'm getting SD Card is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
Click to expand...
Click to collapse
Hi. Here's what I've done:
- I flashed original rom with wiko tool.
- install the 2 updates OTA from wiko - root the phone
- install custom recovery
- flash the 2.5gb data mod.
- flash kernel 1.1
- finally restore all apps with titanium backup.
I hope it helps.
Sent from my Nokia 3310 using my fingers
hi,
i have the same problem!
i have instaled the v1.1 kernel and puffff... no SD card anymore!!!
Hi
Like said:
Flash the 2.5Gb userdata mod via SPFlashtool.
Reboot to recovery and wipe data ( make an backup of your internal SD)
Flash the kernel.
If by any chance it says "sd card damaged" this is normal becouse we had disabled the internal sdcard partition...
You can then follow up that message and format the internal userdata ( now extended)
Reboot
Regards
pren22 said:
Did you then restore data or you installed apps again
I'm getting Phone storage is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
Click to expand...
Click to collapse
After flashing the internal userdata mod, thats normal.
You need to reboot to recovery and wipe /data since the partition was now modified.
Later you can restore your old /data in carliv recovery on advanced restore.
FAQ Was updated with more Info
Related
Maybe?: Final Note
Hello everybody,
I'm sad to announce that my Galaxy Y has died on me.
Not completely, but the USB port seems to have died on my phone.
Charging through the connector still seems to work, but other then that the device is not recognized by any computer anymore.
I know a lot of you are thinking of drivers right now, but this is not the problem.
Not even the phone detects anymore when it's connected to the phone.
This renders the device rather useless for developing as a USB port is really important in this case certainly when having a bad kernel.
I have three options left right now.
- First option would be to hand over the complete development to another developer owning this device. Of course I will help you get started with my sources so you can get started where I left.
The second and third option is up to the community
- If there is anybody in the community who knows somebody who doesn't use the Galaxy Y anymore or is willing to donate his/her own phone this would help out a lot as then I can continue myself in this development.
- Or if anyone could spare some money you could also donate it to me over PayPal. These donations will only go towards buying a second hand Galaxy Y, and will be evenly divided between all donates all money which is left in this case will be reimbursed evenly to everyone who donated to me.
Whichever everyone chooses, I want to let everybody know I enjoyed developing for this community.
Greetings PsychoGame
Big Update: First alpha release for CM7.2 Samsung Galaxy Y (GT-S5360) Alpha 5
Screenshots:
{
"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"
}
Installation instructions are simple:
If you are not working with my kernel:
- Flash my provided boot2.tar file to you're phone using odin (You can download the boot2.tar from here)
If already on my kernel:
- Download the cyanogenmod5.zip file from my dev-host: here (Older releases can be found later in the post!)
- Download the Google Apps from here
- Copy the cyanogenmod.zip and the downloaded gapps file to somewhere on your SD-Card
- Boot in CMW by holding (Volume UP + Select) button while powering up.
- In CWM go to Mounts and Storage first and format /system, /data and /cache.
- Go back to main menu in CWM and choose install zip from sdcard and choose zip from sdcard.
- Apply cyanogenmod.zip
- After installation also apply the gapps-... from here
- Do a wipe data/factory reset from the CWM main menu and reboot the phone
- Be patient while the phone boots for the first time, the phone needs to build up the dalvik cache.
- When fully booted happy testing , and don't forget to report you're findings and bugs.
What works:
- Audio
- Bluetooth (Partially: The device is able to scan for other devices and is also found by other bluetooth devices. Sending files works, receiving does not)
- Camera (Partially: Can take pictures but unable to record film material For more info look at: "known bugs")
- Display "Hardware Accelerated" (Also with some small bugs and glitches, look at "Known bugs")
- GPS
- Input
- Lights
- Network interfaces (Mobile internet)
- Power management
- Radio (Phone "Incoming and Outgoing calls")
- Sensors
- Storage
- Vibrator
- Wifi
What doesn't work:
- Media, media_profiles.xml is included, but the OMX interface still needs to be properly ported which is a WIP.
Known bugs:
- Display: Sometimes there appear to be some glitches. This is known, and due to the usage of a released test binary. I'm currently working myself to reverse engineer the test binary released by BroadCom and the proprietary binary included in the GT-S5360 to come up with a hopefully fixed driver.
- Camera: Still has the white screen bug in the preview of what you're taking a picture of. This is not easily fixable, but will do my best. Movie recording is not yet possible as codecs still need to be included in my build.
Troubleshooting:
Sometimes the Google Apps are giving some troubles with Force Quitting etc., a solution for this is to boot to recovery, clear the cache and dalvik cache and after this do a Fix permissions from the Advanced menu. When rebooting the boot process will take a little longer because the dalvik cache needs to be rebuild.
When anybody has some problems getting it to install through my instructions feel free to ask help in this topic.
Downloads:
- CyanogenMod 7 Alpha 1 Release: http://tinyw.in/VJll
- CyanogenMod 7 Alpha 2 Release: Build Removed (No incoming calls)
- CyanogenMod 7 Alpha 2.1 Release: http://tinyw.in/r4Xs
- CyanogenMod 7 Alpha 2.2 Release: http://tinyw.in/AB92
- CyanogenMod 7 Alpha 3 Release: http://tinyw.in/1G7T
- CyanogenMod 7 Alpha 4 Release: http://tinyw.in/DLUU
- CyanogenMod 7 Alpha 5 Release: http://tinyw.in/dZz0
Changelog for Alpha 2:
Bugs Fixed:
- Not all apps had a ldpi overlay. This has been fixed in the last build I forgot to set the overlay in my full_totoro.mk
- USB Mount didn't work in android. This has also been fixed, I forgot to add the string "file" in the path to the lun file. USB mounting now works as it should work.
- Somebody pointed out that MAC address in the settings wasn't set correct. I researched this problem and it was indeed a bug in my build. This has been fixed now by including the get_macaddrs script in /system/bin. The MAC address wasn't correct because the RIL didn't pass through the MAC address.
Added functionality:
- Compcache has been added to this build. Standard it isn't enabled. To enable this you have to go to: Settings -> CyanogenMod -> Performance -> Compcache. You can choose to allocate 10, 18 or 26 percent. The most recommended value I believe is 18%, but using compcache also has some downfalls. See here for more information: http://en.wikipedia.org/wiki/ZRam
- Wireless Hotspot. This has been tested by me, and I can confirm this function is working perfectly. USB Tethering will be supported hopefully next week.
Changelog for Alpha 2.1:
Bugs Fixed:
- Small fix, I changed the system.prop this week, and in the process forgot to put the ro.telephony.ril_class=samsung option back in the system.prop which results in no incoming calls.
Changelog for Alpha 2.2:
Bugs Fixed:
- Big breakthrough, Headset Support Working. A name in the /system/lib/modules folder of the file brcm_headsetsw.ko had to be bcm_headsetsw.ko. This was why the kernel didn't swich to headset. This was a bug which had slipped my eye as the module name is wrong when compiled from kernel source. This is now completely fixed. And as far as I know this phone doesn't have the Headset Volume Bug. At least not on my phone. Credits go to bluestarfish who pointed this out.
Changelog for Alpha 3:
Bugs Fixed:
- Reverted my system.prop so the tweaks from my first build are included again. Also added some extra tweaks which should reduce the graphics glitches.
- Unsure if GT-S5360L is now able to boot. I haven't got this phone myself, so I can't test it. If it's not working sent me a PM I'll add you on GTalk so we can communicate more easy and fix.
Added functionality:
- Camera: You are able to take pictures, only movie recording is still not possible. This will be a project for later as I'm very busy with bluetooth at the moment.
- Bluetooth: Bluetooth is able to scan for devices and is able to be located by other devices. Pairing or sending from/ to the device is still not possible. Hopefully this will get fixed next week.
Changelog for Alpha 4:
Bugs Fixed:
- The Force Close issues have been resolved. So installing gapps now after CM7 is installed doesn't result in a Force Close error anymore. This is thanks to Gadgetroid.
- Proper apns-conf.xml file has been placed in the /system/etc folder, so this build contains almost all provider APN data now.
- Bluetooth has been made more stable. You can enable bluetooth now without Bluetooth crashing. You're now able to sent files to other devices, only receiving is still not possible. But were getting closer every build .
- Headset: Has been fixed again. My build sources got mixed up a little bit so bcm_headsetsw.so by accident got renamed to brm_headsetsw.so which rendered it unusable.
Added functionality:
- FileManager: The standard filemanager for CyanogenMod has been introduced into this build for everybody who was missing it.
Changelog for Alpha 5:
Bugs fixed:
- The compatibility issue with different basebands and GT-5360L has now been solved.
If you're on alpha 4 you dont need to download the whole alpha 5 again. Only use the boot2.tar provided above to flash the new kernel with Odin.
Credits:
- Myself
- Bluestarfish
- Gadgetroid
- WhiteXP
- Squadzone
- Cyanogen
If you appreciate my work please hit thanks or donate me one beer by clicking the "donate to me" button. I'm investing a great deal of time in this project to make this a very stable product.
Greetings Psycho Game, and have a nice weekend everybody. My sources will be released to my Github next week, so I ask everybody to be patient for that .
Everything below here is old information, you can still read it though to get an idea of the project:
As I already said in another thread about a CWM included kernel I'm also working on a version of CyanogenMod myself with another approach than WhiteXP's build.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y myself at first (until 2 day's ago), but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the makefile of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: Complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary (RFS has been removed, only FSR remains for later. [status: WIP -> stalled]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: Complete]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. (Only ADBD has to be fixed) [Status: 99% Complete]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
CM already compiles fully without much warnings, but still isn't ready to be released until all predecended steps have been completet.
At the moment I'm also uploading all sources of the kernel into github, so everybody can revieuw the proces i'm doing, and also point out mistakes maybe and give suggestions.
Update 1: Yes already an update. It's more difficult to work you're way around the FSR kernel modules. What I now want to do is convert the BML block layer (which uses the FSR modules) to MTD which is an opensource version of a Flash Transition Layer. I know this is possible, because it's also done on the Samsung Epic 4G. The only downside of this is that I cannot use the promised ext4 anymore on the final product, but I'm forced to use YAFFS2 filesystem (which is luckily also opensource).
Update 2 (1 Feb. 2013): Hello everybody. After almost a week I have another update on the Kernel modifications. I stalled the removal of the fsr module parts for now and started with the inclusion of the ClockWorkMod recovery in the kernel. The way I included the CWM recovery is other than Merruk and WhiteXP did. I left the stock recovery in place, and added the CWM on top of it. Standard it boots in the CWM recovery, but if for some reason you would need the stock recovery you can also call it. Just by leaving a file called .stock_recovery in the root of the /cache partition. So in short it contains 2 recovery's in one image. To make it all fit the InitramFS and kernel have been compressed using the lmza method. This allows for a smaller resulting boot.img file, but comes with a little extra boot time. When android has booted you don't notice any difference. Appart from this it's a stock kernel with ext4 included, and the rfs filesystem modules removed, so it's a ext4 kernel only! The completely changed initramfs can be found on my github over here: https://github.com/PsychoGame/totoro_initramfs_files.git so everybody can study what I've done.
Update 3 (8 Feb. 2013): Hello everybody. Again an update of my kernel, and a weekly build to test in the weekend . There have been some changes in this release, the most major change has been that the kernel has been patched from 2.6.35.7 to 2.6.35.14. Also a little change in the recovery.fstab stopped the nandroid backup from making a useless recovery.img. Also I now know for sure that it's possible to do a full nandroid restore. As long as the FSR modules still function also the boot.img backup will be restored. The only thing still not working is the Android Debugging Bridge in the recovery self. This seems to be a harder to tackle problem then I thought before. It seems that adbd is not working properly so it doesn't see the device. The new kernel can be obtained from here:
boot.tar (08/02/2013)
With this new 2.6.35.14 kernel you also need to have all other updated compiled modules which are available here:
Version14Modules.zip
These files should be placed in /system/lib/modules
This is not a CWM installable package at the moment because I'm a little bit busy at the moment, so this means you have to copy the files manually to the directory.
I recommend using ES File Explorer in which you need to have full read/write acces to the disk.
When anybody needs some extra help please let me know.
There are two small bugs at the moment:
- ADB still not working inside recovery
- Sometimes the touchscreen has a little problem getting out of it's sleep state. I don't know how to describe it, but will look into this problem very soon. It's not a harmfull bug.
Question to other developers: Hopefully there are other kernel developers among us as well. If you think you can contribute to this as well, then please PM me. At the moment I hope everyone together including myself will look into implementing MTD into out device.
The kernel source is uploaded to https://github.com/PsychoGame/android_kernel_samsung_totoro.git Updated
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Installation Instructions
It's wise to make a EFS backup first to be sure you're IMEI data etc. is safe at all times. It's not only wise for this project but other projects as well. A good tool for this is Galaxy ToolBox. This tool saves the backup on you're SD card which you should keep safe on you're computer
Here are the installation instructions of the first kernel release:
Known bugs:
- Adb is not working in the CWM at this moment. I'm pretty sure it's a simple problem, but will solve that later on. It's not very annoying as anyting else is in my opinion functioning.
In my walktrough I will cover the steps for installing my kernel on a fresh install of Android.
There are a ton of walkthroughs already on the subject of flashing android to the Galaxy Y (GT-5360) through odin.
I didn't test it yet on a working installation, but I'm pretty sure this should work in there also.
Step 1: First of all, download the needed files
- cwm-madteam-galaxY.zip
- boot.tar (01/02/2013)
- boot.tar (08/02/2013)
- Version14Modules.zip
- Odin 1.85 Used
- update-signed.zip (Su Binary)
Step 2: Make a nandroid backup of you're device using Madteam's ClockWorkMod.
Step 3: Enter download mode (Holding down button + Select) + Power button until the phone seems to boot. In download mode flash my supplied boot.tar by putting it in the PDA field in Odin. No .pit file is required, and just leave anything default and click the (flash button).
Step 4: Enter CWM recovery (holding up + select) + Power button until the phone boots, and go to mounts and storage and one by one do (format /data, format /system and format /cache).
Step 5: Also in the menu Mounts and storage click on mount USB storage while the mobile is connected to the computer with the USB cable, or use a cardreader to open you're miniSD card. On the miniSD card there is a folder which is called clockworkmod which contains the backup you just made in the folder backup. Here you should change as an example (system.rfs.tar to system.ext4.tar), and also do this for the data.rfs.tar. Also inside nandroid.md5 these filenames have to be changed accordingly to resp. system.ext4.tar and data.ext4.tar.
Step 6: Reboot the ClockWorkMod Recovery and in the backup and restore menu click on "advanced restore" and choose you're nandroid backup. Choose only to restore (System and Data.)
Step 7: Just reboot and enjoy you're Galaxy Y with CWM included in kernel. As far as I tested everything is working as it should be, if you come across something that doesn't work please report this.
Step 8: Copy the modules supplied in Version14Modules.zip to /system/lib/modules/
If you flashed a fresh android rom you should Root it again using the update-signed.zip I supplied above this article (Before you install the update-signed.zip you have to mount the /system partition in the "Mounts and storage menu" first the mount is forgotten in the installer script.)
I hope you'll enjoy this little beginning, there's a lot more to come. I'll be gone for the weekend, so after the weekend I will be able to respond to any bugs and problems everyone came across.
Greetings
Psycho Game
gud luck !!!!:good: buddy
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I smell a new developer here.. Or maybe a reincarnation of maroc
Good luck bro!
Sent from my GT-S5360 using XDA
:good:
:highfive:
keep it up bro..
reserved
great initiative
really appreciate your efforts - good luck and go on !
hell_lock said:
I smell a new developer here.. Or maybe a reincarnation of maroc
Good luck bro!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
i think reincarnation of maroc....
good luck bro...
carry on ur work..
good luck bro, i can be pray for you
Thanks for the positive comments already, I will try to be as open about the development as I can.
By this I mean that I try to explain every step I do, in my github, but also in the forum so that somebody else could reproduce all the steps I did to create the same thing as me.
So also people beginning with development can try to understand what I'm doing.
Also I will keep this thread as updated as possible.
Greetings PsychoGame
PsychoGame said:
... I will try to be as open about the development as I can.
By this I mean that I try to explain every step I do, in my github, but also in the forum so that somebody else could reproduce all the steps I did to create the same thing as me....
Click to expand...
Click to collapse
I am as excited about that as I am the ROM itself, I will be following this with interest!
Thanks for your efforts so far and for all the work you will put in to realise this project in the future :good:
Stokey
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
Subscribed +2
Awesome work
I expect more from u :thumbup:
jasonxD Leveled to 2
Just wanna ask one question -
Isn't kernel 3 made to make it compatible with ICS/JB ?
If yes, then isn't White's kernel based on kernel 3 ?
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
Ramdisk makes ics/gb/jb boot.. U dont need 3.x kernel for that.. Just make some changes in stock ramdisk and u r good to go.
Sent from my GT-S5360 using XDA
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I like thread.
I subscribe.
---------------------------------------
Questions? Better go to [Help Thread] Ask ANYTHING! xD
Gamer R said:
Just wanna ask one question -
Isn't kernel 3 made to make it compatible with ICS/JB ?
If yes, then isn't White's kernel based on kernel 3 ?
Click to expand...
Click to collapse
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
PsychoGame said:
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Click to expand...
Click to collapse
Very complicated it is..
Sent from my GT-S5360 using XDA
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I love u
Phone Slow? go ------>HERE<------
Ubuntu phone OS announced
what do u think share your thoughts --->HERE<---
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
--Sent from the future with a galaxy s4 like a freaking BAWS--
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
PsychoGame said:
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Click to expand...
Click to collapse
The amount of ur knowledge in this kind of stuff is TO DA*N HIGH
Thanks for ur hard work...
jasonxD Leveled to 2
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
jasonxD said:
The amount of ur knowledge in this kind of stuff is TO DA*N HIGH
Thanks for ur hard work...
jasonxD Leveled to 2
Click to expand...
Click to collapse
Maroc 2.0
Phone Slow? go ------>HERE<------
Ubuntu phone OS announced
what do u think share your thoughts --->HERE<---
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
--Sent from the future with a galaxy s4 like a freaking BAWS--
IMHO most of problem from cm 7 (source) porting come from vendor's proprietary library. i don't think putting effort to porting sgy kernel to 3.x version is worth it. fs and partition only 'small' thing to do. you still have to port gpu, camera, baseband, and other modules which is more difficult.
BIG FAT WARNING:
NEXT kernel 1.0 - 2.0 requires mali-400-r3p2-01rel3-t31x.zip!
NEXT kernel 2.1 and later requires mali-400-r3p2-01rel3-api29-t31x.zip!
Sources:
Kernel sources at https://github.com/kumajaya/android_kernel_samsung_smdk4x12/tree/cm-11.0
Features:
Based on Samsung OSRC Note 2 N7100, Tab 3 8.0 and Note 8.0 kernel source
Single source for T310, T311, and T315 target (and Note 2 N710x, Note 8.0 N51xx). Only T311 version well tested on my device but both T310 and T315 version boot T311, not working GSM radio of course
Traceable source level changes: https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0
Open source Samsung exFAT modules included
Remove a lot of debug message from touchscreen driver, display, mmc, modem, bluetooth, etc. Now, dmesg output more useful than stock kernel
Disable a lot of kernel debugging support
Linaro GCC compiler
The ramdisk based on JB 4.2.2 AMG3 (T310 and T311) and AMH1 (T315), OTA recovery flash disabled
Some tweaks from gokhanmoral's siyahkernel for S3, passive entropy tweak applied
Auto root, SuperSU included please download SuperSU from Google Play. Heimdall v1.4.0 work for our device. For a brand new T31x, flash your device using "sudo heimdall flash --BOOT boot.img" and you will get rooted
Self compiled static BusyBox v1.21.1 in /sbin, android_reboot applet added (a quick but clean port from Android toolbox), swapon applet with priority option. On stock ROM, this version of Busybox will overwrite busybox binary in /system/bin or /system/xbin and save it as busybox.backup
Early boot scripts support (/system/etc/init.d, /data/local/userinit.sh, and /data/local/userinit.d)
Mali GPU driver r3p2-01rel3
KitKat external sdcard write access for user apps patcher
Known Problems:
Thanks To:
gokhanmoral, Chainfire
This part will be expanded. Most of the patches I applied are coded by someone else. Please remind me if I forget to give credits to anybody...
Downloads:
http://forum.xda-developers.com/devdb/project/?id=5210#downloads
Todo:
Dual boot
Special Thanks:
@onemoreidiot, @kutaxov, @bout_time
XDA:DevDB Information
[KERNEL][SM-T31x][SINGLE/DUAL][STOCK/CM] blackhawk's NEXT kernel, Kernel for the Samsung Galaxy Tab 3
Contributors
ketut.kumajaya
Kernel Special Features: Dual boot stock and CM ROM
Version Information
Status: Stable
Current Stable Version: 1.7
Stable Release Date: 2014-07-11
Created 2014-08-01
Last Updated 2014-09-11
Changelog 24/08/2014, NEXT 2.x WIP:
Samsung KitKat support
Auto root reworked
External sdcard write access auto pacher
Mali 400 r3p2-01rel3 API version 29
Changelog 11/07/2014, NEXT 1.7:
Samsung OSRC SM-T310 KitKat NF4 kernel source:
Exynos platform update
Battery, regulator, and charger driver update
Touchscreen driver and firmware update
Flip sensor, WiFi, sound, IR LED and camera driver update
Memory and block related tuning
swap, frontswap, and zswap support, etc
LZO compression/decompression update
Recent GCC versions (e.g. GCC-4.7.2) compatibility fix
Changelog 16/06/2014, NEXT 1.6:
GCC Linaro 4.9.1-2014.05 toolchain
Nintendo Wii remote support, latest CM version needed
Changelog 12/06/2014, NEXT 1.5:
Applied Samsung OSRC N7100 KitKat ND4 update on top of MK9, and then rebase our current kernel to it
Low power mode charging bug fix applied, this kernel compatible to our current JB bootloader and upcoming KitKat bootloader
Incompatibility issue to CM's hwcomposer fixed
New WiFi driver, new exFAT filesystem, arm and exynos spesific update, a lot of updates from Samsung
More efficient method of passing vsync to userspace for CM
GCC Linaro 4.8-2014.04 toolchain
Full changelog https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0 . Linaro 4.8 patch still not available on my github, I will push it later
Changelog 21/04/2014, NEXT 1.4:
Kernel update: stop log buffer spam, extra scheduler (sio, vr, and row), interactive governor, revert f2fs quick hack, etc: https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0
Ramdisk update to upstream CM (SE Linux context, sepolicy, init and healtd binary)
Install script update for easier future maintenance
Remove workaround fix for write access to the root of ext4 or f2fs formatted SD card
Changelog 26/03/2014, NEXT 1.3:
Fix boot menu reboot to bootloader option
Insecure adb, fix compatibility issue to Omni and Slim ROM
SE Linux policy update
Workaround fix for write access to the root of ext4 or f2fs formatted SD card
Default ueventd config
Compiled AROMA from source
Compiled static busybox from CM source with patched reboot applet
Changelog 16/03/2014, NEXT 1.2:
F2FS filesystem support, completely based on @DerTeufel1980 github commits and small hack in include/linux/blk_types.h https://github.com/kumajaya/android_kernel_samsung_smdk4x12/commits/cm-11.0, Extended PhilZ Touch recovery needed for ext4 to f2fs migration
exFAT filesystem integrated in kernel
In sync to CM 11.0 init changes, CM multi SIM support compatibility issue fixed
Changelog 22/01/2014, NEXT 0.6.4:
Updated kernel source, new Mali GPU kernel driver r3p2
SuperSu 1.91 for stock ROM
Directly flash mali-400-r3p2-01rel3-blobs-t31x.zip (on both ROM for dual boot user) is a must or your device will fail to boot!
As reported by @manup456, graphic glitch occurred in stock ROM with Mali r3p2. Workaround for this issue is "Turn off hardware overlays - Always use GPU for screen compositing" in Settings - Developer but this setting doesn't stick, so you must set it on every boot. Another solution is switch to previous version of NEXT kernel and directly flash Mali r3p1 blobs (on both ROM for dual boot user).
Changelog 16/01/2014, NEXT 0.6.3:
Reworked init script as CM playground
Changelog 09/01/2014, NEXT 0.6.2:
Compatible to the new CM lights module
Changelog 05/01/2014, NEXT 0.6.1:
Flip cover detector, work on both stock and CM ROM
Changelog 30/12/2013, NEXT 0.6:
CM 11.0 support
Changelog 10/12/2013, NEXT 0.5:
Initial T315 support
CM: Ramdisk synced to unofficial CM 10.2
Changelog 02/12/2013, NEXT 0.4:
CM: fix back camera still image capture
Changelog 28/11/2013, NEXT 0.3:
CM: fix bluetooth discovery problem
CM: fix front camera preview
Add PAC ROM support
Stock: SuperSU 1.80, thanks Chainfire
T310 support
Changelog 26/11/2013, NEXT 0.2:
Add lates CM-10.2 nightly 20131125 support
SuperSU 1.75 (for stock ROM), thanks Chainfire
Changelog 25/11/2013, NEXT 0.1 brand:
Stop more spams
Linaro gcc 4.7 compatibility fix, now use GCC Linaro 4.7 compiler
VR and SIO scheduler, SIO as default sheduler
R/W semaphores implemented using ARM atomic functions
Merge espresso10 interactive CPU governor, interactive with EARLYSUSPEND support
Initializing Android USB depending on the rom type for dual boot support
Notify userspace of vsync_time using sysfs for AOSP based ROM support
Partial netfilter update, allow tracking loopback and rate limit some of the printks
Unofficial PhilZ Touch recovery
Attached PhilZ Touch recovery repack for T310 and T311. Both version tested on my T311. Both version not well tested (i.e. backup and restore not tested since have no free space SD card) but since this version based on official P5100, everything should be work correctly. Flash this at your own risk using existing CWM/TWRP recovery or Heimdall v1.4.0 "sudo heimdall flash --RECOVERY recovery.img" command.
I am almost sure @Phil3759 will officially support our device anytime soon.
ROOT + BLACKHAWK + PHILZ TOUCH FOR YOUR BRAND NEW T31X
Single step for root and PhilZ Touch recovery using Heimdall v1.4.0:
Extract both blackhawk kernel boot.img and PhilZ Touch recovery.img
Install Heimdall for your operating system: Linux, OSX, or Windows
Boot your device into download mode, connect it to your computer, flash:
Code:
heimdall flash --BOOT boot.img --RECOVERY recovery.img
Done!
NOTE: I've deleted PhilZ Touch non SELinux version to avoid confusion, total 618 downloads for all variant!
Dual Boot FAQs
Adapted from droidphile's "Dual Boot FAQs" with permission.
1. "Why would I wanna dual-boot?"
A. You don't have to.
Suppose you're more of an aosp rom fan. But misses the HDMI out, bluetooth hands-free and love sammy camera more. Do a minimal installation of sammy rom and boot into it when in need of these features and use aosp rom otherwise.
Or you are a sammy rom fan but love the responsiveness and pure android feel of aosp roms.
And while you can dual boot two sammy or two aosp roms, it doesn't make any sense.
2. "What if I don't need dual booting?"
A. No issues. Kernel won't force to setup 2 roms. You can single boot as before.
3. "Will dual booting change my bootloader or do any dangerous stuff like setting my phone on fire?"
A. NO. Changes are at kernel and ramfs level only. Some space in your internal sd card is used, and also the unused hidden partition mmcblk0p16 is used to store cache of second rom. Dual booting doesn't repartition the filesystem or perform anything scary.
4. "I want to setup dual booting."
A. There are four situations:-
1) Sammy rom now. Want to use aosp as secondary.
2) Sammy rom now. Want to use aosp as primary.
3) Aosp rom now. Want to use sammy as secondary.
4) Aosp rom now. Want to use sammy as primary.
Prerequisites for any setup is
a) Flash latest blackhawk's NEXT kernel. BIG FAT WARNING: For stock Samsung ROM, NEXT kernel 1.0 or later requires mali-400-r3p2-01rel3-blobs-t31x.zip!
b) Flash latest Extended PhilZ Touch recovery: http://forum.xda-developers.com/showpost.php?p=51364377&postcount=33
c) Atleast 90% battery left.
d) 3 GB free on internal SD.
e) Some spare time
1) Present sammy, setup aosp as secondary:-
i) Reboot into recovery
ii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for CM/CM based ROM and then close it
iii) Reboot into secondary recovery (red on screen navigation buttons)
iv) Flash aosp ROM as 2nd ROM
v) Flash blackhawk's NEXT kernel again
2) Present sammy, setup aosp as primary:-
i) Reboot into recovery
ii) Nandroid backup your current sammy ROM
iii) Select "Run Aroma Dual Boot Tool" in Advaced Menu, create system.img for Samsung stock/stock based ROM and then close it
iv) Reboot into secondary recovery (red on screen navigation buttons)
v) Nandroid restore your sammy ROM as 2nd ROM
vi) Flash blackhawk's NEXT kernel again
vii) Reboot into primary recovery
viii) Flash aosp ROM as 1st ROM
ix) Flash blackhawk's NEXT kernel again
3) Present aosp, setup sammy as secondary:-
Same as (1), instead of flashing aosp to second, flash sammy to second.
4) Present aosp, setup sammy as primary:-
Same as (2), instead of flashing aosp to first ROM, flash sammy.
NOTE:
-To dual boot Two Aosp or Two Sammy roms, just follow (1) or (2) (depending on which one of them you want as primary/secondary), just flash Sammy instead of aosp or aosp instead of sammy.
5. "What things should I be taking care off while dealing with dual booting?"
A. - Make sure where you are: in primary or secondary recovery.
6. "How to boot into primary rom?"
A. AROMA based boot menu will help you on every boot.
7. "How to boot into secondary rom?"
A. AROMA based boot menu will help you on every boot.
8. "Is kernel partition shared?"
A. Yes. Same kernel boots both roms.
9. "If I flash another kernel (that doesn't support db) do I lose dual booting?"
A. Yes
10. "I lost dualbooting after flashing another kernel. I didn't do anything to second rom files in sdcard/.secondrom. How can I get db back?"
A. Just flash the latest blackhawk's NEXT kernel
11. "Will there be any performance degradation on the rom used as secondary compared to primary?"
A. NO
12. "Will my phone run slow overall because of db?"
A. NO
13. "How to flash a newer version of 1st rom?"
A. As usual, just flash it from primary recovery. Flash blackhawk's NEXT kernel again
14. "How to flash newer version of 2nd rom?"
A. Just flash it from secondary recovery. Flash blackhawk's NEXT kernel again
15. "Would upgrading 1st or second rom cause other rom to fail on boot?"
A. No. Partitions of other rom are not touched during upgrading.
16. "I miss the recovery I used before, so much.."
A. PhilZ Touch not bad at all.
17. "User apps of 1st rom are automatically available for second rom?"
A. NO. However, if you had backed them up using Titanium Backup or similar apps, just restore apps while on second rom.
18. "I wanna keep separate backup for apps in both the Roms, since I use one Rom for say entertainment and other productivity."
A. Setup different backup directory in Titanium Backup in 1st and 2nd rom.
19. "I don't see STweaks app in second rom."
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
20. "Do I need to anything special before flashing a newer blackhawk's NEXT kernel?"
A. NO. Just flash kernel in recovery - whichever you used to do. Kernel image is copied to the unified kernel partition
21. "How can I run same STweaks settings of 1st Rom in 2nd Rom?"
A. This is blackhawk's NEXT dual boot solution for Galaxy Tab 2, a free implementation of gokhanmoral's Siyah dual boot.
22. "How do I remove everything related to DB and run single boot again?"
A. In primary recovery, flash blackhawk's NEXT tool and delete 2nd ROM system image. OR delete .secondrom directory in /data/media while on 1st Rom.
23. "If secondrom files are kept in /data/media, will wiping data in recovery erase second rom files?"
A. NO. /data/media is skipped in CWM recovery.
24. "I read somewhere that both rom data partition use the same space. Doesn't that mean my apps are shared across roms?"
A. NO. It just means they uses same partition. They're still different directories.
1st rom data = /data
2nd rom data = /data/media/.secondrom/data
25. "Will hitting "Boot into Secondary Recovery" in recovery boot menu change my recovery?"
A. NO. It just runs (not flash) an alternate recovery so that you can configure dualboot settings.
26. "How do I backup 1st Rom and 2nd Rom?"
A. To backup 1st Rom, do what you did to backup rom while you were single booting a while ago.
To backup 2nd Rom, use the secondary recovery.
27. "Is there an easier way for dual-boot?"
A. Yes, send your device to me.
28. "DB architecture?"
A. Like you know, every rom has a /data, /system, /cache partition and a kernel to boot.
For primary rom, it's
mmcblk0p21 = /data
mmcblk0p20 = /system
mmcblk0p19 = /cache
And these won't change whether you're single booting or dual booting.
For secondary rom, data and system is stored in internal sd, cache in hidden partition. Note that internal sd in our device is mounted to /data/media.
We have data as a directory, System as an image in data/media/.secondrom. Cache in mmcblk0p16 which is hidden partition and not used otherwise.
- When second rom is booting, second rom data is bind mounted to mmcblk0p21 as /data/
- data/media/.secondrom/system.img partition is mounted as /system.
- mmcblk0p16 is mounted as /cache.
More FAQs will be added and the list will be updated as DB is improved.
Build kernel and kernel modules for Samsung Galaxy Tab 3 8.0 SM-T31x Exynos 4212
Ketut P. Kumajaya <ketut.kumajaya at gmail dot com>, Oct 2013
Samsung Open Source Release Center: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=sm-t31
Samsung OSRC exFAT source: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=exfat
Working kernel source, compilable and tested on SM-T311: https://github.com/kumajaya/android_kernel_samsung_lt01
I assume your home directory is /home/android
Clone kernel source repo:
Code:
$ cd /home/android/
$ git clone git://github.com/kumajaya/android_kernel_samsung_lt01.git
Create an environtment text file, save it as /home/android/build.env (change CROSS_COMPILE to point to your toolchain):
Code:
export CROSS_COMPILE='/opt/toolchains/arm-eabi-4.6/bin/arm-eabi-'
export LDFLAGS=''
export CFLAGS=''
export SUBARCH=arm
export ARCH=arm
Import environtment file above (dot+space+build.env), create build directory outside kernel source directory, and start the building process:
Code:
$ cd /home/android/android_kernel_samsung_lt01
$ . /home/android/build.env
$ mkdir -p /home/android/build/lt01
$ make O=/home/android/build/lt01 mrproper
$ make O=/home/android/build/lt01 tab3_3G8_01_defconfig
$ make -j8 O=/home/android/build/lt01
Copy the resulting kernel and modules to a binary directory:
Code:
$ mkdir -p /home/android/build/lt01-bin
$ cp /home/android/build/lt01/arch/arm/boot/zImage /home/android/build/lt01-bin/
$ find /home/android/build/lt01/ -type f -name *.ko -exec cp {} /home/android/build/lt01-bin/ \;
Your kernel and all kernel modules ready in /home/android/build/lt01-bin/
{
"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"
}
The resulting kernel also already tested as PhilZ Touch recovery kernel, running on SM-T311 PhilZ Touch repacked from PhilZ Touch recovery for Galaxy Tab 2 10.1 target
Samsung Galaxy Tab 3 8.0 original boot logo:
oc kernel ?? thanks.
Finally a developer with GTab 3 8inch :good: :good:
Can't wait to see a flashable zip and try on my tab
Just got a black screen of death when trying to replace Samsung boot logo Solved: reflash my own param.bin Odin flashable tar.md5
rothshek said:
oc kernel ?? thanks.
Click to expand...
Click to collapse
There's no OC commit: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
Kernel and unofficial PhilZ Touch recovery repack attached at post #1.
Kernel: almost stock, compiled using gcc linaro 4.7, a lot of kernel debugging support disabled, still leave all Samsung kernel spams, restricted root disabled
Ramdisk: self compiled busybox included, auto root, init.d support, flash recovery disabled
Open source, commit history: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
PhilZ Touch repack based on official PhilZ Touch for Tab 2 10.1, thanks @Phil3759
Still in development
Flash the kernel and/or PhilZ Touch using existing CWM/TWRP recovery
Derp!
ketut.kumajaya said:
Kernel and unofficial PhilZ Touch recovery repack attached at post #1.
Kernel: almost stock, compiled using gcc linaro 4.7, a lot of kernel debugging support disabled, still leave all Samsung kernel spams, restricted root disabled
Ramdisk: self compiled busybox included, auto root, init.d support, flash recovery disabled
Open source, commit history: https://github.com/kumajaya/android_kernel_samsung_lt01/commits/master
PhilZ Touch repack based on official PhilZ Touch for Tab 2 10.1, thanks @Phil3759
Still in development
Flash the kernel and/or PhilZ Touch using existing CWM/TWRP recovery
Click to expand...
Click to collapse
PhilZ Touch runs on T-310? ExFat memory cards supported? There is support for the work of internal memory?
marincax said:
PhilZ Touch runs on T-310? ExFat memory cards supported? There is support for the work of internal memory?
Click to expand...
Click to collapse
I will upload T310 version. T311 version attached at post #1 also work on T310 but every device have a different identity (default.prop). Internal and external memory works, including exFAT support.
I've been disable so much kernel spam but still a lot left flooding the kernel message buffer, just saying
ketut.kumajaya said:
I will upload T310 version. T311 version attached at post #1 also work on T310 but every device have a different identity (default.prop). Internal and external memory works, including exFAT support.
Click to expand...
Click to collapse
Thanks a lot for your reply.:good:
Will be there be enough to replace default.prop in a version for T-311 on default.prop recovery from original T-310?
marincax said:
Thanks a lot for your reply.:good:
Will be there be enough to replace default.prop in a version for T-311 on default.prop recovery from original T-310?
Click to expand...
Click to collapse
Yes, with 2 lines modification:
Code:
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ketut.kumajaya said:
I've been disable so much kernel spam but still a lot left flooding the kernel message buffer, just saying
Click to expand...
Click to collapse
Please leave messages Logcat, kmsg and dmesg. :crying:
Yes, with 2 lines modification:
Code:
ro.debuggable=1
persist.sys.usb.config=mtp,adb
Click to expand...
Click to collapse
Thank you so will I do.
Still changed:
ro.secure=0
ro.adb.secure=0
marincax said:
Please leave messages Logcat, kmsg and dmesg. :crying:
Thank you so will I do.
Click to expand...
Click to collapse
Don't worry, disable the kernel message is really a bad idea :laugh: How about switchable logcat?
ketut.kumajaya said:
Don't worry, disable the kernel message is really a bad idea :laugh: How about switchable logcat?
Click to expand...
Click to collapse
Yes, it will be good. :good:
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (LOLLIPOP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Unofficial build of CyanogenMod 12.1(Android 5.1.1) for the HTC Explorer (Pico)
Notable features:
No Maps 7 glitches, Browser glitches, Gmail glitches, etc.
Uses ION memory allocator
Native Sd-Card -- Using sd-ext partition for system and data
F2FS Support In kernel and Device tree
Uses the newest Adreno (graphics) libraries and firmware available for our platform (these graphics libraries are newer than the graphics libraries in any other ROM)
Significantly smoother/faster graphics as a result of the new graphics libraries
Removed many hacks designed for old graphics
CAF KitKat 2.7 branch Adreno blobs
What's working:
RIL
Data Connection
Display
Stock browser
Camera
WiFi
GPS
WiFi tethering
Bluetooth
Bluetooth tethering
SDcard
Video playback
Audio playback
Headset
Audio Recording
Sensors of All type
Not working:
OMX ( hardware decoding/encoding )
Camcorder
Download:
BETA#1 : http://forum.xda-developers.com/showpost.php?p=61134823&postcount=316
CyanogenMod 12.0 Builds
Gapps :- https://www.androidfilehost.com/?fid=95897840722646482
Install instructions:
Use Class 6 or Class 10 sd-card for best performance
Make 2 ext4 sd-ext partitions like this
1st partition :- sd-data --->> 1GB minimum
2nd partition :- sd-system --->> 1.2 GB
Flash the updated [03/02/2015] TWRP 2.8.5.0 Recovery
Convert your /data and /system partition to f2fs you can find it in wipe option
Wipe all partitions
Flash the cm-12.1-*-UNOFFICIAL-pico.zip
Reboot
If you Stuck at HTC Splash Screen go into bootloader mode, take out boot.img from rom zip and flash it
Reboot
Done!
After first boot reboot back to recovery
Flash Gapps
Source:
https://github.com/CyanogenMod
Thanks to:
All Pico developers before me
PecanCM (TeamHackLG)
LegacyXperia
Use BUG Tracker in Thread to report your Bug
If you want to help fixing those bugs, please report the bugs in the bug tracker and provide me logcat or i cant help you. Thanks!
Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.
You can get more info here on how to take log HERE
Donations :-
Buy Me A cup of Bear click on donate to ME button
XDA:DevDB Information
Android 5.0 lollipop ( CM-12.1 ) For HTC Explorer, ROM for the HTC Pico (Explorer)
Contributors
kirmaniarslan, Sachin Thomas
Source Code: https://github.com/HtcLegacy
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Rooted
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2015-03-03
Created 2014-11-19
Last Updated 2015-06-11
Changelog :-
CyanogenMod 12.1
Beta#1 03/06/2015 :
- Lollipop 5.1.1
- CM-12.1 Upstream
- Fixed Deepsleep issue
- Disable dialer lookup by default
- Switched to QCOM power HAL
- Added LZ4 Compress/decompress support
- Update zram and zsmalloc up-to 3.17 kernel changes
- inherit media_codecs_google_video_le.xml better for low end devices
- update ril.h for 5.1
- Disable dex2oat watchdog
- Don't disable jit cache
- Set dalvik.vm.dex2oat-filter=balanced
- Disabled LTE as our device doesnot support it
- Update Audio policy for 5.1
- Call broken and Wifi Calling fixed
- Increase ZRAM swap size to 192MB
- fixed heatset and Data connection problem on kernel level ( no patches needed )
CyanogenMod 12.0
Beta#3 02/03/2015 :
- CM Upstream
- Fixed Data Connection
- Fixed Headset thanks @thewisenerd for fix
- Fixed MTP connection with PC
- Enabled WITH_ART_SMALL_MODE you can read it more here : http://source.android.com/devices/tech/dalvik/configure.html#with_art_small_mode
- Symlink dalvik-cache to nand for performance and also decreases the battery usage ( u can see it as sd-ext in recovery for cleaning it )
- Disabled data encryption
- Updated audio_policy.conf from HTC one M7
- Set sd cache to 1MB
- Enable LOGD
- Using NuPlayer instead of Awesome player
- Based on Aw3some mod thanks @thewisenerd
- Gapps Lags Fixed
- Headset profile update from DX kernel 3.4
More Kernel Changelog
Beta#2 29/01/2015 :
- Cm Upstream
- Fixed GPS
- F2FS support in kernel and device tree added for /system and /data partition
- Fixed Sound Recorder
- Enable cortex a9 optimization
- Update HtcMsm7x27aRIL class
- Disabled alpha trasformation in animations
- Added New CPU GOV Intelliactive and set it to default governer
More Kernel Changelog You can Check from HERE
Beta#1 20/01/2015 :
- CM Upstream
- Fixed Camera (Still camcorder is broken )
- Setup for chromecast support.
- Lowmemory killer tweaks to fix oom issues
- Sepolicy inherit from common qcom sepolicy
- Force camera API to version 1
- Updated partition layout
- Set background process to 4
- Inherit dalvik-heap props with 512mb ram (This fixes browser Image Cache problem)
- Enable SystemUI flags to optimize performance
- Builtin bcmdhd module in kernel to fix loading and unloading issues
- Add custom HtcMsm7x27aRIL to fix SignalStrength on gsm
- Disable TARGET_CPU_SMP
- Disable Atlas service
- Cleaned up system.prop
- Disable JIT
- Configure ksm with low ram
- Allow legacy allocations from MM heap
Alpha#2 - 28/11/2014 :
- CM Upstream
- Enable dex-preoptimization to speed up first boot sequence
- Patches for performance Much stable and faster now
- SELinux Support : Set to Permissive mode
- Temp fixed soft reboots
- Forced high-end graphics for transparent lockscreen and statusbar
- Ril fixed GSM working but data connection is not fixed
- Added FFMPEG codec configuration
- Added SELinux support in kernel
- Disabled kernel features
- Added Multi User support upto 4 users allowed can be enabled with ( ro.config.low_ram=false in build.prop )
- Using Awsome Latest layout
Alpha#1 - Nov 19, 2014 :
- Initial upload
- Updated Libaudio
- Disable LOGD
- Enabled Minikin fonts
- Display and Media hals based on msm8960 with some hacks for msm7x27a
- Used dlmalloc instead of jemalloc
FAQ :-
Q: Why SD-ext and what is Partition layout ?
Ans:There is not much space in system partition even with awsome partition layout and secondaly here is the partition layout
/dev/block/mmcblk0p3 mounted as /system i used this partition so that you dont have to create partition again and again
/dev/block/mmcblk0p2 mounted as /data
Q; How Can I clean my sd-ext partitons ?
Ans : you can flash this before flashing rom http://forum.xda-developers.com/showthread.php?t=2392001
Q: I am stuck at HTC splash screen what to do ?
Ans:Simply Take out boot.img from Rom zip and flash it in fastboot mod
Code:
Fastboot flash boot boot.img
Q: I can't find developer options and performance settings, why?
A: Settings -> About phone -> Click 'Build number' several times
Q. No ROOT access WTF ?
Ans : Enable it from Developer option
CyanogenMod 12.0
CyanogenMod 12.0 Builds :-
BETA-3:http://forum.xda-developers.com/showpost.php?p=59174157&postcount=244
BETA-2: http://forum.xda-developers.com/showpost.php?p=58525401&postcount=177
BETA-1 : http://forum.xda-developers.com/showpost.php?p=58297444&postcount=142
Alpha-2 : http://forum.xda-developers.com/showpost.php?p=57106417&postcount=76
Alpha-1 : https://www.androidfilehost.com/?fid=95784891001612903
BasketBuild Mirror
Pico still alive, thank you kirmani for the sweet lollipop Hope it gets stable soon.
@kirmaniarslan You really Rock bro.. Didnt even think of getting a lollipop on our device. Salute you bro Really a grand salute.. You are keeping our device alive and running up.
wow amazing plzz build cm12 for redmi 1s a.k.a armani
Awesome work !!!! hope
Great Stuff Here i See (Y) Good Luck... if people have some issues they can P.M me i have some minor fixtures which can be done in Lollipop... as for now Lollipop is in alpha stages and is a real pain in the arse...
I'll be reporting issues myself when i see other than the given one's in the OP
Thanks man....awesome work
wow the feels!
bro kirmani is really hyping us up!
great work man!
I'll stay tune for this
Booted Successfully
It takes about 10-12 minutes to boot on Class 10 SD-Card
Wow good going pico rocks
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Error
I'm getting a (bad) error. Any one else getting the same? I'm on CWM 5.0 and on Thinking Bridge rom.
kratikedat said:
I'm getting a (bad) error. Any one else getting the same? I'm on CWM 5.0 and on Thinking Bridge rom.
Click to expand...
Click to collapse
Use the given recovery
I installed from a 4GB mem card
It took 30mins or more to boot... but after booting too, it bootlooped! Same happening again and again!
Need to make any partitions?
TheStrix said:
I installed from a 4GB mem card
It took 30mins or more to boot... but after booting too, it bootlooped! Same happening again and again!
Need to make any partitions?
Click to expand...
Click to collapse
Havent u made sd-ext if yes then flash the rom again after wiping
kirmaniarslan said:
Use the given recovery
Click to expand...
Click to collapse
My bad, didn't read theiinstructions thoroughly enough. Another noob question if you dont mind, how do I flash a recovery over my existing recovery? Does the pico being s-on have an issue with it? Sorry again for the noob question!
Aswin08 said:
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Click to expand...
Click to collapse
Use terminal emulator
keep the recovery3.img in the root of sdcard
su
cd sdcard
flash_image recovery recovery3.img
Aswin08 said:
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Click to expand...
Click to collapse
@Ashwin08 this may help for you http://forum.xda-developers.com/htc-explorer/general/how-to-flash-recovery-phone-t2831744
I am proud to present you with an UNOFFICIAL Evervolv powered by K3 for the HTC Desire.
I am grateful to Nikez for allowing me to publish this on xda.
WARNING:
THIS IS A REALLY REALLY PRE-ALPHA, STUFF ARE BOUND TO NOT WORK.
FOR ADVANCED USERS ONLY!
{
"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"
}
Disclaimer:
Please be aware this is an unofficial release compiled from the latest Evervolv codebase (2015-07-18).
If you rely on your device as it is your only phone you should thoroughly consider the risks involved when flashing a custom ROM (e.g. total loss of your data!).
If you decide for flashing this rom, then you do it at your own risk and I am not responsible for any resulting damages!
I don't claim responsibility for the code in this ROM, I have only built the ROM for this device.
My decent changes:
- Kernel 3.0.16 for Kitkat (based on qsd8k-3.0-wip by Nikez)
- Improved Torch (does not turn off when screen shuts down)
- Removed EVUpdater
- Added Jackpal's Terminal Emulator
- A few tweaks for faster scrolling, longer battery life and smoother overall performance
Not working:
- Same as in Evervolv Turba and any other of my KK roms; If you find new issues which are specific to this ROM/Kernel combination, please post your report in this thread together with a logcat
- Camera preview is sometimes distorted (but taking pictures works)
- WiFi tethering / Hotspot WPA/WPA2 not working
- At times, some SD cards cannot get properly mounted
Installation hints:
- Stock hboot or Alphajelly hboot
- SD-EXT partition (512MB or 1GB) required if you plan to use A2SD
- In order to reduce battery consumption switch CPU governor to smartass
Special credits go to:
- EVERVOLV, the original developer of this ROM, as well as htc vendor files and bravo device tree!
- @LaidbackNikez for being a force behind the development of kernel 3.0.16!
- @[email protected] for his awesome work in stabilizing the kernel!
- marc1706 for being a force behind the development of kernel 3.0.16!
- macs18max for providing great tips on kernel developments!
- noonamer for being a force behind the development of kernel 3.0.16!
- walter79 for providing great tips on kernel developments!
- franciscofranco for sharing his magic kernel tweaks!
- everyone else who was involved but does not appear in this list
Have a nice day!
Source:
https://github.com/Evervolv
https://github.com/spezi77/android_kernel_htc_qsd8k_3.0/tree/kitkat-ev
Changelogs
ev_bravo-UNOFFICIAL-4.0.0p2-turba-k3.0.16.
* Initial test release
ev_bravo-unofficial-4.0.0p3-turba
* Kernel Improvements
** added several ARM specific fixes
** used a newer toolchain version (GCC 4.8) for compilation
** added boost pulses for SmartassV2 / introduced SmartassH3 CPU governor (credits H3ROS, M66B and NobodyAtAll)
* GPU: added newer Adreno libs from AU_LINUX_ANDROID_JB_VANILLA_04.02.02.60.051 Build Date: 04/11/13 Thu
* Fixed a problem with SD card mounting at boot
* Added a patch to prevent wakelocks caused by Google Play Services 7.x SystemUpdateService (credits CM)
* Added several tweaks to improve the overall performance of the ROM
* Improved incoming call response time (if screen is turned off the call appears now after ~3 seconds) (credits pixelfreak and walter79)
ev_bravo-unofficial-4.0.0p3-turba-built-for-performance
* Kernel Improvements
** Use per default SMARTASSH3 (allows a better speed/battery-saving ratio)
** Boost enabled per default in smartass governors
** Added conservative governor
** Freed some more ram
** Added a few security fixes from mainline Linux kernel
** Guarded code against potentials deadlocks (ashmem)
** Added improvements taken from Franco's kernel magic
*** I/O boosted - I/O dirty writeback system backported from 3.2
*** Deadline I/O scheduler by default
*** CRC32 library that is used by a lot of internal kernel mechanics completely patched up to the latest version (credits Ezekeel)
*** Merged two stability hotplug patches from mainline Linux kernel
*** Add dynamic writeback feature from 3.1
*** Introduced fsync_control for better performance and i/o throughput (credits cuteprince)
Downloads
ev_bravo-UNOFFICIAL-4.0.0p2-turba-k3.0.16.zip
md5 - df040e5204e7678d132e49de0ef2e318
ev_bravo-unofficial-4.0.0p3-turba.zip
md5 - 5d960975b14ebd4775cf9ef0e34c8fba
ev_bravo-unofficial-4.0.0p3-turba-built-for-performance.zip
md5 - 599d68732a59b8314e18fc754b6984b7
Great cocktail:
kernel 3 + stock hboot + kk turba
ze7zez said:
Great cocktail:
kernel 3 + stock hboot + kk turba
Click to expand...
Click to collapse
I knew that you would like it.
1st of all - let me say thanks. a BIG thank you !
without dev like your self the desire is just another paper brick.
Can you please run a benchmark to give us a hint of the overall responsiveness with K3 Vs K2 ?
I know the K3 is a major upgrade in term of a linux user/dev - but after all the good work that Evervolv et-al put into it - how much the upgrade, qualitatively speaking, worth ?
tested
SD Card doesn't mount (i don't know why?)
some times it fails to boot and i had to eject the battery then try it
thanks for your work!
Rminsh said:
tested
SD Card doesn't mount (i don't know why?)
some times it fails to boot and i had to eject the battery then try it
thanks for your work!
Click to expand...
Click to collapse
Thanks for your reply. I didn't have one of the problems you reported.
Could you share more details about your phone.
- hboot
- sd-ext partition
- recovery
Maybe could you also share a logcat when the phone failed to boot?
Cheers!
P.S.: after leaving my Desire on standby through one night (CPU gov: SmartassV2; 3G on; Wifi off), batt still had 28%.
P.P.S.: I have right now installed slim-gapps from Dec 2014: Slim Gapps 2014-12-02 - md5 26306ee3fb6b57a88c05286a1fef4ff9
P.P.P.S.: I have set zRAM to 30%; reduced animation/transition scales to 0.5%. Everything works really smooth in this rom.
gps3dx said:
Can you please run a benchmark to give us a hint of the overall responsiveness with K3 Vs K2 ?
Click to expand...
Click to collapse
What is the tool that you would recommend for doing a benchmark?
Wow, i'll try as soon as posible! Thanks! :good:
Just a question, why "4.0.0p2-turba" and not lastest nightly? "4.0.0p2-turba" is a very very old build, no?
zinconnu said:
Wow, i'll try as soon as posible! Thanks! :good:
Just a question, why "4.0.0p2-turba" and not lastest nightly? "4.0.0p2-turba" is a very very old build, no?
Click to expand...
Click to collapse
No, no, my stuff is not old. This rom has been compiled from the latest codebase. However there were only little developments in AOSP and/or EVERVOLV's kitkat branch since more than one year. Devs have hopped off kitkat and grabbed for lollipop.
Since there is no official development for this rom, we can say that it is now sort of "abandoned". As I am not a part of Evervolv team, my hands are tied and I decided simply to stick to the "old" codename for the HTC Desire.
In short, you could say that this is a brand-new build which is based on latest nightly from 2015-07-18.
spezi77 said:
Thanks for your reply. I didn't have one of the problems you reported.
Could you share more details about your phone.
- hboot
- sd-ext partition
- recovery
Maybe could you also share a logcat when the phone failed to boot?
Cheers!
P.S.: after leaving my Desire on standby through one night (CPU gov: SmartassV2; 3G on; Wifi off), batt still had 28%.
P.P.S.: I have right now installed slim-gapps from Dec 2014: Slim Gapps 2014-12-02 - md5 26306ee3fb6b57a88c05286a1fef4ff9
P.P.P.S.: I have set zRAM to 30%; reduced animation/transition scales to 0.5%. Everything works really smooth in this rom.
Click to expand...
Click to collapse
Hey
Stock hboot
2GB ext partition (class 10)
Cwm4 recovery (still i didnt change the recovery ) )
I will take a logcat as soon as i can
Sd card doesn't mount and on the status bar shows sd card is damaged or insert one!
Sent from my HTC Desire using Tapatalk with KitKang
spezi77 said:
In short, you could say that this is a brand-new build which is based on latest nightly from 2015-07-18.
Click to expand...
Click to collapse
OK, i understand now, thanks for your answer. I'll try to keep this ROM an entire week to see how it reacts compared to the "old-kernel" version.
zinconnu said:
I'll try to keep this ROM an entire week to see how it reacts compared to the "old-kernel" version.
Click to expand...
Click to collapse
There is nothing better than using a rom for one week, in order to do benchmarking. :thumbup:
Sent from my nexus™4 ?
spezi77 said:
There is nothing better than using a rom for one week, in order to do benchmarking. :thumbup:
Sent from my nexus™4 ?
Click to expand...
Click to collapse
Ok here is my logcat and i find out that the USB tethering is not working!
i think the logcat is not complete and the device sometimes goes offline on adb!
if it's not enough then tell me to repeat it!
Thanks!:good:
Rminsh said:
Ok here is my logcat and i find out that the USB tethering is not working!
i think the logcat is not complete and the device sometimes goes offline on adb!
if it's not enough then tell me to repeat it!
Thanks!:good:
Click to expand...
Click to collapse
That logcat is sufficient. You were telling the truth. There is indeed an issue with your sd card (see error below).
It is tricky to do a remote diagnosis, but the simplest trick could be to format your sd card and again create a sd-ext partition. 1GB is really sufficient.
Or maybe do you have a 2nd sd card, just to ensure that the root cause isn't your sd card?
Code:
I/fsck_msdos( 114): ** /dev/block/vold/179:0 I/fsck_msdos( 114): Invalid signature in boot block: 0000 I/fsck_msdos( 114): fsck_msdos terminated by exit(2) E/Vold ( 114): Filesystem check failed (not a FAT filesystem) W/Vold ( 114): /dev/block/vold/179:0 does not contain a FAT filesystem E/Vold ( 114): /dev/block/vold/179:0 failed to mount via NTFS (No such device) E/Vold ( 114): Volume sdcard0 found no suitable devices for mounting :(
Sent from my nexus™4 ?
spezi77 said:
That logcat is sufficient. You were telling the truth. There is indeed an issue with your sd card (see error below).
It is tricky to do a remote diagnosis, but the simplest trick could be to format your sd card and again create a sd-ext partition. 1GB is really sufficient.
Or maybe do you have a 2nd sd card, just to ensure that the root cause isn't your sd card?
Code:
I/fsck_msdos( 114): ** /dev/block/vold/179:0 I/fsck_msdos( 114): Invalid signature in boot block: 0000 I/fsck_msdos( 114): fsck_msdos terminated by exit(2) E/Vold ( 114): Filesystem check failed (not a FAT filesystem) W/Vold ( 114): /dev/block/vold/179:0 does not contain a FAT filesystem E/Vold ( 114): /dev/block/vold/179:0 failed to mount via NTFS (No such device) E/Vold ( 114): Volume sdcard0 found no suitable devices for mounting :(
Sent from my nexus™4
Click to expand...
Click to collapse
oh sorry! it's 1GB ext4 partition (not 2GB!)
im really confused! isn't it the swap partition that recognize for second partition?or /data ?
honestly it doesn't have problems with kitkang (kernel 2) or other roms!
Rminsh said:
oh sorry! it's 1GB ext4 partition (not 2GB!)
im really confused! isn't it the swap partition that recognize for second partition?or /data ?
honestly it doesn't have problems with kitkang (kernel 2) or other roms!
Click to expand...
Click to collapse
Alright. I thought that there is something wrong with your sd card partitions. Maybe it is worth to consider reformatting it? Have you used this guide? http://forum.xda-developers.com/showthread.php?t=2125513
Sent from my nexus™4 ?
spezi77 said:
Alright. I thought that there is something wrong with your sd card partitions. Maybe it is worth to consider reformatting it? Have you used this guide? http://forum.xda-developers.com/showthread.php?t=2125513
Sent from my nexus™4
Click to expand...
Click to collapse
ok , you were right
i changed my sd card with 8GB class 4 with 750mb ext4 and it works perfect!
still i have boot problems! after the htc logo the screen get dark and reboot to the htc screen again!
here is my logcat
Rminsh said:
Stock hboot
2GB ext partition (class 10)
Cwm4 recovery (still i didnt change the recovery ) )
[...]
Sd card doesn't mount and on the status bar shows sd card is damaged or insert one!
Click to expand...
Click to collapse
For me it is the same.
TWRP or 4EXT - does not matter.
SD Class 10 16GB (FAT32 + 1GB ext4 by gparted)
A moment ago I did logcat on the same hardware just after a clean install.
In the original turba mount the SD operate normally.
K3 is more sensitive.
{
"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's something for you guys to play around with,
the thread will be beautified and completed later.
Now the bare minimum has to suffice
this ROM includes a Wakelock Blocker and a Doze Powersave called feature to make sure your device really sleeps well
So: no Greenify, Amplify, PowerNap, etc. are needed.
From my observation the idle battery consumption is somewhat higher compared to AOSP and CM13 - but still pretty low
In addition it has several goodies from quite a lot other ROMs
Downloads
List of all Releases:
CyanogenMod based Custom ROMs -> Resurrection Remix
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6853/E6803 :
ResurrectionRemix-M-v5.7.0-20160628-satsuki
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6653/E6603 :
SunKernel II.1_2 for ResurrectionRemix-M-v5.6.7-20160426 for the Z5P
Details
For Instructions on how to install, etc.
Please take a look at the CyanogenMod 13 Thread (same ROM base):
http://forum.xda-developers.com/z5-premium/development/rom-cyanogenmod-13-sony-xperia-z5-t3407396
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/ResurrectionRemix/
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-26
Last Updated 2016-06-29
Reserved 01 (ROM)
Reserved 02 (Custom Kernel)
Kernel Changelog/Features (II.1_2) said:
upstream sonyxperiadev sync - mmc (deferred resume) fixes
upstream sonyxperiadev sync - added proper support for replacement display panels
exfat driver
thermal and hotplug fixes
LED notification indicator changes color when battery is really full (thanks to @Tommy-Geenexus )
hardware wakelock switches (modem, wifi, bluetooth)
switch for GENTLE_FAIR_SLEEPERS
backlight calculation improvement
fixes for compiler-caused issues & instabilities
vmalloc improvements (less memory fragmentation, more reliability in the long-term)
vmscan improvements (better reliability when swap/zram is disabled; less thrashing)
cfq-iosched fixes
re-enabled deadline, row i/o scheduler
frandom
LPM (low power mode) fixes & improvements
mmc (internal storage, microSD) reliability and performance fixes & improvements
KSM more efficient scanning and packing [KSM defaults to off, it's a battery drainer]
scheduler: load balancing improvement
cpuidle fixes & improvements
reducing high load average to minimum - less/minimal idle battery drain
a few general fixes (thermal, i2c-msm-v2 [unnecessary error message upon startup/deferral], usb: f_fs, fingerprint scanner)
more governors: elementalX, ZZMove, alucard ( thanks to @AndroPlus )
backported SIM_DETECT & TRAY_SHARED_INTERRUPT_DETECT, MMC_SUPPORT_SVS_INTERVAL from Sony's copyleft kernel; possible preparation for DSDS/DSDA mode)
Click to expand...
Click to collapse
and last one
(Installation)
Q: Can i flash it without losing my actual data ?
A: If you use both zip files (ROM + kernel),
then yes, your data should be safe.
But still backup your data - you never know if it doesn't go crazy
Once you've backed up your data, done a Backup via TWRP - copy the backup of TWRP (in TWRP folder) to your PC
to be really sure
then format (advanced wipe)
/data, /system/, /cache, dalvik cache
and flash the ROM zip + kernel zip + GApps (e.g. Slim GApps)
After that you're good to go
Q: What is the correct order to install it ? Different Kernel + TWRP, then ROM and later your kernel ?
A: You're using TWRP, right ?
Not sure if there's a different TWRP available for the Z5P - but if yes,
you can keep TWRP (and don't need to flash a new recovery).
Copy ROM + Kernel + GApps to internal storage,
reboot - press vol up button to get into TWRP/recovery,
Backup your System,
Reboot and Copy the TWRP folder and ALL your important data to your PC/Mac/...
Reboot again into Recovery/TWRP,
do an advanced wipe (/cache, /data, /system, dalvik cache),
flash ROM, Kernel, GApps,
Reboot -> System
That should be all
Damn cant wait to try this
Okay
Boots up with latest kernel package. :good:
Patiently waiting
Thanks for the heads up
how about E6883
6853 cant see it?
I must be blind because i cant see the rom for 6853 keen waiting for a asop based rom
zacharias.maladroit said:
Reserved 01 (ROM)
Click to expand...
Click to collapse
He does not start , it is loaded into the logo of resurrection remix ... and I've had more than 15 minutes.
pandan80 said:
how about E6883
Click to expand...
Click to collapse
Well, constantly asking won't magically accelerate it
We're working on it, also did some testing,
but the best for now (afaik) was that one SIM card worked and microSD disappeared.
dominicstg2 said:
I must be blind because i cant see the rom for 6853 keen waiting for a asop based rom
Click to expand...
Click to collapse
6853 is satsuki,
can you post the links you're using ?
Or what issue are you running into ?
Custom Kernel is updated,
please flash it along with the ROM since stock kernel doesn't seem to work (might be due to selinux issues or others, dunno - don't have enough time and also don't feel like tracking it down right now,
there are more important priorities in my life currently)
Thanks
Rubensss said:
He does not start , it is loaded into the logo of resurrection remix ... and I've had more than 15 minutes.
Click to expand...
Click to collapse
Rubensss, you flashed the custom kernel, too ?
How did you flash it ?
edit:
you noticed that there's a new custom kernel up, right ?
@moonbutt74 just flashed it - and it appears to work fine
Okay
Boots up with latest kernel package. :good:
m
zacharias.maladroit said:
Rubensss, you flashed the custom kernel, too ?
How did you flash it ?
edit:
you noticed that there's a new custom kernel up, right ?
@moonbutt74 just flashed it - and it appears to work fine
Click to expand...
Click to collapse
I installed it as follows , please tell me where I was wrong .. I installed the kernel and recovery of moonbut74 , after flashee the rom and gapps and rebooted . your kernel you have to install before flashing the ROM and gapps ? or install your kernel and then the recovery of moonbut74 ? zacharias.maladroid thanks for your help
Rubensss said:
I installed it as follows , please tell me where I was wrong .. I installed the kernel and recovery of moonbut74 , after flashee the rom and gapps and rebooted . your kernel you have to install before flashing the ROM and gapps ? or install your kernel and then the recovery of moonbut74 ? zacharias.maladroid thanks for your help
Click to expand...
Click to collapse
Hm, so moonbutt74's recovery means TWRP ?
Not sure if there's a different TWRP available - but if yes,
you can keep TWRP (and don't need to flash a new recovery).
Copy ROM + Kernel + GApps to internal storage,
reboot - press vol up button to get into TWRP/recovery,
Backup your System,
Reboot and Copy the TWRP folder and ALL your important data to your PC/Mac/...
Reboot again into Recovery/TWRP,
do an advanced wipe (/cache, /data, /system, dalvik cache),
flash ROM, Kernel, GApps,
Reboot -> System
That should be all
was looking at the wrong links
zacharias.maladroit said:
Well, constantly asking won't magically accelerate it
We're working on it, also did some testing,
but the best for now (afaik) was that one SIM card worked and microSD disappeared.
6853 is satsuki,
can you post the links you're using ?
Or what issue are you running into ?
Custom Kernel is updated,
please flash it along with the ROM since stock kernel doesn't seem to work (might be due to selinux issues or others, dunno - don't have enough time and also don't feel like tracking it down right now,
there are more important priorities in my life currently)
Thanks
Click to expand...
Click to collapse
Waiting for DSDS version even single sim only is working.
zacharias.maladroit said:
Hm, so moonbutt74's recovery means TWRP ?
Not sure if there's a different TWRP available - but if yes,
you can keep TWRP (and don't need to flash a new recovery).
Copy ROM + Kernel + GApps to internal storage,
reboot - press vol up button to get into TWRP/recovery,
Backup your System,
Reboot and Copy the TWRP folder and ALL your important data to your PC/Mac/...
Reboot again into Recovery/TWRP,
do an advanced wipe (/cache, /data, /system, dalvik cache),
flash ROM, Kernel, GApps,
Reboot -> System
That should be all
Click to expand...
Click to collapse
Thanks installed. I have to say that to be the first version works very well, the speakers sound a bit loose but with impressive quality . As you publish a stable version will install for my daily use , I really like resurrection remix . Thank you very much for your work Zacharias.maladroid
Solid build
Continuing off the other CM build this build is also rather solid.
Once you get the camera working correctly as well as figuring out the Bluetooth issues ill have a new daily driver for sure
Living without my camera / Bluetooth isn't a option for me though haha.