To those fellow Touch 3 users and Ultra users.... Hi!
CWM Recovery Test
I'm actually trying to compile custom recoveries but I'm going to focus on one for now... I already have my compile project online but I am need of assistance in booting this in the phone since I already flashed many of my test builds and it returned with no success (no output/not running). Could anyone please assist me in this?
Link to CWM compile project:
Code:
https://github.com/Tatsun0x05rd1/cm_Ultra-eng
Link to recovery image:
Code:
https://github.com/Tatsun0x05rd1/omni_Ultra-eng/tree/master/Recovery%20Source
Link to boot image(kernel "source"?... It's not a source for the kernel):
Code:
https://github.com/Tatsun0x05rd1/omni_Ultra-eng/tree/master/Kernel%20Source
Related
The samsung galaxy s wifi/player 3.6 haven't cwm because we have a verry small comunity (3.6 thread : http://forum.xda-developers.com/showthread.php?t=1864741)
I tried to compile cwm 5 from cm7 source while ago and I didn't succeed : a error with a too big size out image.
Today I re-download the cm7 source but too many file are missing.
If a developper can compile for me or help me for create the cwm recovery. You need the dump image of the recovery ?
vendor/core/definition.xxx
delete some limit，will ok
I am following this guide XDA university porting cwm to a new device and I just wonder if I need the same android version of sources as it is on the android phone.
I mean, the phone is running android 4.2 so it is neccecary to download cm 10.1 sources or can I build it using cm 11 sources?
tulen_kobi said:
I am following this guide XDA university porting cwm to a new device and I just wonder if I need the same android version of sources as it is on the android phone.
I mean, the phone is running android 4.2 so it is neccecary to download cm 10.1 sources or can I build it using cm 11 sources?
Click to expand...
Click to collapse
It is not necessary to have the same android source as your device's android version to make cwm. CWM is part of the kernel and not the android system. Your device's kernel will be extracted and the ramdisk will be replaced with cwm ramdisk and after that the kernel will be built with cwm ramdisk then you can use it as recovery.
If you want I can help you out with twrp recovery. I have done it for LG L65 and L70. If you want my help with twrp then please download omni rom sources (manifest: https://github.com/omnirom/android ) or just replace bootable/recovery folder with the omni's one in your cm source tree, get kernel source code for your device or have a boot.img, make sure your device has a recovery partition so recovery is not part of the kernel image as a secondary ramdisk like on samsung devices otherwise I could not help.
Hi All,
I’m are working on a project to create a KITKAT ROM to a MediaTek MT6589 device. These are the steps that I have taken so far:
Downloaded the CM11 source code
Downloaded the Micromax A210 device tree (the properties appear to be the same as the MediaTek device)
Then I modified the resolutions to match our target device (BoardConfig.mk)
Then I compiled the source code
Then I used the flash tool to install the system on the device
The result: The device seems to get into a boot loop even before the boot animation comes. :crying:
I tried to get the log cat out but it appears that the device stuck before the log cat even been generated.
So am I doing something obviously wrong?
How should one detect what goes wrong at the boot level and to see why the OS does not load?
What other actions could I take?
Is there any recommended system source code for this device (MT6589)?
Any help / criticism would be appreciated. Thank you in advance my friends.
What was the original Android version that came with this device? Are you trying to build an upgrade?
damithark said:
What was the original Android version that came with this device? Are you trying to build an upgrade?
Click to expand...
Click to collapse
Actually yes, what came is Jelly Bean 4.2.2. So thought of creating a KITKAT ROM for MediaTek devices. That's why I had to use the Micromax A210 device tree.
Any help on this is highly appreciated.
Hey guys,I searched the forums for custom ROMs for my device but all were useless First I stumbled upon emotion lollipop(named Note4.zip or something) which I was able to flash with carliv touch recovery easily but my device did not boot.Then I tried myanogrn mod 12.1 and 13.1 both unable to install with any recovery I installed(carliv,philz,cwm) showing error of some 'status 7' and when I try to fix it with the assert deletion there is no assert lines in the ROM's update-script . Finally I decided to post the question here to find if any of you know the answer.My device is running on KitKat(4.4.2) stock ROM,rooted, baseband version:MOLY.WP8.W1315.MD.WG.MP.V43,2014/05/29 11.15.
Kernel version:3.4.67 and build is:ZAW1800G_060A_V8_2_5.
If anybody knows any ROM update please send me a message with the link to download the ROM file.Thank you.
Hello Everyone,
I made Cyanogenmod 13 build for moto e condor(which is supported by cyanogenmod), then I installed it using twrp recovery and it's working fine.. But now from this cyanogenmod source code I made cyanogenmod 13 build for cherry mobile flare S Play (which is not supported by cyanogenmod) by follwing "How To Port CyanogenMod Android To Your Own Device" wiki page.. I did all the steps as mentioned in this page and one more extra thing I did that I changed kernel folder of surce code(which is kernel version 3.4) with another kernel source code (kernel version 3.10.72), because cheery mobile flare s play has 3.10.72 kernel version..
I build Zip file successfully for Cherry mobile flare s play and I installed it using twrp recovery but after installing while doing reboot system it's only showing flare s play icon and then black screen is coming.. now I am not able to install cyanogenmod 13 build in cherry mobile flare s play
Please do help if anyone knows..
Thanks
Fall-through from normal boot mode
hieuvan said:
Although I don't own the device, but here's some common solutions that you can try:
Restoring the old kernel to your build?
Carefully check the new kernel to make sure it's compatible with the firmware?
Re-flash stock ROM then re-flash your build again?
Cheers!
Click to expand...
Click to collapse
Thanks for reply..
old build i have deleted and today I made fresh cyanogenmod 13 build but when I installed it..
It's showing boot up failed..
Fastboot Reason: Fall-through from normal boot mode
boot up failed
why it's showing this error??
When this error comes, do you have any idea?