Related
so it seems like LG Optimus one P500 is supported by Rom manager as it is listed in the clockworkmod website.
so after i rooted the phone, i can install CWM Recovery from rom manager right?
and flash custom ROM through it right?
i want to install milk's cm 7.1 port for p500, its listed in the clockworkmod website.
so yeah it should work right? and will installing that ROM fix the well known touchscreen bug on the optimus one? i mean the inverted axis multitouch bug and the cpu spike when scrolling bug, or do i need to flash something else after that? if yes could u pls link me to it.
and from what im seeing, p500 kernel is flashable through recovery eh? unlike the x8/x10 mini/pro in which we need to use flash tool?
edit: ive noticed the mik's os in clockworkmod website is beta 6.5.5 in which the latest one is 6.5.8 right? so ill just download the latest 6.5.8 from xda and flash it through rom manager?
yes, but first do a backup in cwm recovery, then wipe everything, flash rom , reboot, flash gapps, the flash from here http://forum.xda-developers.com/showthread.php?t=1227682 BFS gbs.v19.2, and you should be fine, the spikes arent fixed yet
but LG fixed it already in it latest gingerbread ROM, why isnt it fixed in cyanogenmod rom yet? proof utube /watch?v=wgV56dLSbEs
edit :
from MikOS thread :
beta6.5.5 (2011-06-27):
kernel: franco's v18 + 2.6.32.42
Wired headset media button fix moved to kernel
Camera: higher defaults exposure
Updated CM sources (RC1 now)
its already using franco? do i still need to flash that goldenleaf thing?
Remember, that our device isn't officially supported by team Cyanogen.
And that kernel is the old one - look at development section - there's and updated one (i suggest latest goldenleaf + mik's 6.5.8 (your release is old too))
alright so now i wanna clear things up, heres the step i should do :
1.root+install busybox
2.install rom manager and from there install CWM Recovery
3.download latest goldleaf/GBS kernel and latest mik's OS 6.5.8
4.in rom manager, make backup, flash mik's os ROM, reboot, flash gapps, reboot, flash GBS kernel, reboot, full wipe everything.
5. voila!
so thats it right? is there anything i missed? and can i use gapps from rom manager (20110828 Universal) ? if i can't could u please link me to the gapps that i shud be installing?
edit:can i flash franco.Kernel.v19.4 instead of the goldleaf kernel, coz it seems in franco kernel the cpu spike and axis inversion is fixed
6 - August - 2011 - v19
Good touchscreen drivers which should have the CPU **** fixed and the axis inversion workaround
Click to expand...
Click to collapse
rj's custom kernel for Galaxy Player 5 international
aka rumirand
Hi there.
Finally got my YP-G70 back to life, so I'm working on get a better kernel and take advantage of this device. This kernel is based on stock G70XXKPF firmware, but some users report it works on other firmwares.
If you have a G70 US (capacitive home button), use Entropy512's kernel. If you have a 4.0, use Steves kernel.
Features
2.6.35.7 source for GingerBread.
Unsecure mode.
Swap support.
Overclock to 1.2Ghz and undervolt capabilities (use SetCPU or another software for UV).
Added lazy (default), interactive, interactiveX, smartassv2, ondemandX governors.
Added BFQ, V(R) and SIO (default) schedulers.
Init.d support.
Added statically linked busybox 1.19.3 (/sbin)*.
Modified adbd (pointing shell to /sbin/sh), so you can use adbd even if you don't have any partition working*.
ext4 support (ghetto lagfix).
ClockWorkMod (beta). Nandroid backup - restore works, mount/umount, format (formats to ext4).
You can boot in stock recovery placing /cache/.stock_recovery file (In terminal, just do 'touch /cache/.stock_recovery'), and reboot to recovery.
CIFS support.
jhash3.
SoD patch from netarchy/coolbho3k.
TinyRCU.
netarchy's conservative tuning patch.
Custom bootanimation support (/system/media/bootanimation.zip) from Entropy512's kernel.
Per-File fsync() disable - For info, look here.
Charginghacks from Entropy512.
*Useful for recovery/unbrick purposes. My device got bricked and got the partition table faulty. With this, you can rebuild your partition table using fdisk.
Changelog
Code:
r14
- Changed overclock patch (now Entropy512 based)
- BNEP enabled by kernel.
r13
- Add Charginghacks from Entropy512's kernel.
r12
- Overclock to 1.2 Ghz and UV capabilities.
r11
- Switch source code to YP-G70 US (this fixes the SoD patch issue).
- SoD patch reapplied.
- Custom bootanimation support thanks to Entropy512.
r10
- Battery drain fixed.
- Added latest patches/fixes from Entropy512's source code. Take a look at his Github.
r9
- Tentative fix for battery drain problem. Please provide some feedback.
r8
- Added V(R) scheduler.
- Added CIFS.ko.
- jhash3.
- TinyRCU.
- SoD patch.
- Conservative tuning patch.
r7
- Fixed backing up/restoring /dbdata.
- Added ability to backup/restore to internal storage and external sdcard.
r6
- Added ext4 support.
- Added CWM. Nandroid backup - restore works (/system, /data, /cache, kernel and recovery), mount/umount, format (formats to ext4).
r5
- Added ondemandX and interactiveX governors.
- Minor fixes on unsecure mode.
r4
- Added SIO scheduler (default).
- Added support for init.d scripts.
- Radio FM works now.
- Added statically linked busybox 1.19.3 (/sbin)*
- Modified adbd (pointing shell to /sbin/sh)*
r3
- Added cpufreq governors: interactive, smartassv2 and lazy (default).
- Added BFQ I/O scheduler -> to activate it, use some app like CPU Master.
r2
- 2.6.35.7 kernel from GB source.
- Unsecure mode.
- Swap support.
- Get config from /proc/config.gz
- Stock G70XXKPF ramdisk.
r1
- Initial upload -> doesn't work.
Download:
Kernel r14 (Odin) - Kernel r14 (CWM)
Kernel r13 (Odin) - Kernel r13 (CWM)
Kernel r12 (Odin) - Kernel r12 (CWM)
Kernel r11 (Odin) - Kernel r11 (CWM)
Kernel r10 (Odin) - Kernel r10 (CWM)
Kernel r9 - CWM beta
Kernel r8 - CWM beta
Kernel r7 - CWM beta
Kernel r6 - CWM beta
Kernel r5
Kernel r4
Kernel r3
Kernel r2 <- first working kernel.
Initial upload (r1) <- doesn't boot. So don't bother to flash it.
Installing:
Odin:
Download kernel from site.
Get your device in download mode (device turned off, press vol down key, plug the usb cable.
Open Odin3.
Select kernel file in PDA section.
Keep the rest Odin settings untouched (make sure re-partition, phone bootloader update and EFS clear aren't checked).
Start.
CWM:
Download kernel from site.
Place .zip file in /sdcard/external_sd/.
Reboot in recovery mode.
Choose install zip from sdcard.
Reboot.
Enable ghetto lagfix:
FIRST: MAKE SURE YOU HAVE AL LEAST 12MB OF FREE SPACE ON /SYSTEM PARTITION
Enter in recovery mode (CWM).
Do a full Nandroid backup.
Reboot your device.
Change .rfs.tar files in clockworkmod/backup/xx.xx.xx/ to .ext4.tar.
Edit nandroid.md5 to match .ext4.tar files.
Enter in recovery mode (CWM).
Do a full restore.
Reboot (you'll probably have some FCs, I got in GMaps and Market, just delete application's data/reinstall it).
If you want to go back to rfs, revert the steps.
Uninstalling:
Download stock XXKPF kernel here.
Flash it following the same instructions above.
Big thanks to Entropy512 for working in a CWM port for our devices and his kernel. This work is based on his job.
Source code available on my GitHub
Any suggestion/idea is welcome.
Do it at your own risk. I'm not responsible if any damage is done to your device.
Is this a Froyo or GB kernel? The kernel on my device has version 2.6.35.7 (GB 2.3.5). Apart from this, is there a way to backup the existing kernel before testing the development kernel. Thanks!
WT Ho said:
Is this a Froyo or GB kernel? The kernel on my device has version 2.6.35.7 (GB 2.3.5). Apart from this, is there a way to backup the existing kernel before testing the development kernel. Thanks!
Click to expand...
Click to collapse
Ok, first of all, I finally got my Galaxy Player working (thanks thanks for the dump you provided me)! So the next releases will be tested before uploading it.
For backup the kernel, the best to do is open the firmware .tar o .tar.md5 file and extract zImage file. Then, in linux, you can do:
Code:
tar cf zImage.tar <path-to-zImage>
You will get a .tar file containing only the kernel, flashable from odin3.
Don't bother testing the initial upload, it won't boot.
It looks to me like /dev/block/mmcblk0p11 and /dev/block/mmcblk0p12 contain the kernel and recovery kernel, therefore one could do the following to back up the partition:
Code:
dd if=/dev/block/mmcblk0p11 of=/sdcard/zImage-partition bs=4096
lardman said:
It looks to me like /dev/block/mmcblk0p11 and /dev/block/mmcblk0p12 contain the kernel and recovery kernel, therefore one could do the following to back up the partition:
Code:
dd if=/dev/block/mmcblk0p11 of=/sdcard/zImage-partition bs=4096
Click to expand...
Click to collapse
You're right. That's an alternative mode to backup kernel and recovery. You can even flash directly a kernel by dumping a zImage file (unpacked) to mmcblk0p11. I haven't done this myself, but it should work.
rumirand said:
You will get a .tar file containing only the kernel, flashable from odin3.
Don't bother testing the initial upload, it won't boot.
Click to expand...
Click to collapse
That's a good start already. We will wait for the next one.
Can you update the starting post with some information and make a note that the initial upload doesn't work.
Let us know what version of the kernel are you using.
Bump.
r2 is up and working.
Bump.
r3 is up and working. See changelog for details.
Do you have any plans to make an overclock kernel?
bdds13 said:
Do you have any plans to make an overclock kernel?
Click to expand...
Click to collapse
Yes. It's only changing some lines of the source code. Will test later today/tomorrow.
I'll upload it when it's done.
Thanks a lot!
Just flashed it. No major issues so far, will continue to use and see if I found anything unusual. Here are the versions reported on my device
Model number: YP-G70
Firmware version: 2.3.5
Kernel version 2.6.35.7-G70XXKPF-CL562492 [email protected] #rj's
Build number GINGERBREAD.ZSKP8
It should be noted that I am not flash the kernel on XXKPF firmware but ZSKP8 but it still works.
See also the screenshot attached.
rumirand said:
Yes. It's only changing some lines of the source code. Will test later today/tomorrow.
I'll upload it when it's done.
Click to expand...
Click to collapse
Tegrak Overclocking app can already overclock the stock kernel, will this introducing something not available in Tegrak? May be we can add a few more speed levels? Currently the stock kernel only has 1GHz, 800MHz, 400MHz, 200MHz and 100MHz.
WT Ho said:
Tegrak Overclocking app can already overclock the stock kernel, will this introducing something not available in Tegrak? May be we can add a few more speed levels? Currently the stock kernel only has 1GHz, 800MHz, 400MHz, 200MHz and 100MHz.
Click to expand...
Click to collapse
Only we would gain more speed levels. Tegrak does well the job in overclocking/undervolting and I think it's a clean solution (every user can choose if only wants overclocking/undervolting and how far wants to go).
I've overclocked my device to 1.5ghz, only slight overvolt needed at that frequency. Did undervolting too. Runs stable.
I'll see if I can port voodoo lagfix on this device.
Thanks for posting this..would love to try out..
I am already on 2.6.35 by flashing the kernel posted in this forum..official one since mine came with Android 2.1
Is yours without all the Samsung features such as icon shape, interface etc? Can that be removed to use raw Gingerbread?
chen2008 said:
Thanks for posting this..would love to try out..
I am already on 2.6.35 by flashing the kernel posted in this forum..official one since mine came with Android 2.1
Is yours without all the Samsung features such as icon shape, interface etc? Can that be removed to use raw Gingerbread?
Click to expand...
Click to collapse
This is only the kernel. The other things are in the rom. So, the icons, touchwiz UI aren't related to the kernel.
This kernel is great running smartassv2 and using Tegrak Overclocking app to over-clock to 1.3ghz and battery life is great and its very fast. thanks
Rueben_ said:
This kernel is great running smartassv2 and using Tegrak Overclocking app to over-clock to 1.3ghz and battery life is great and its very fast. thanks
Click to expand...
Click to collapse
How it does perform for you the lazy governor? For me seems to be more battery lifesaver than smartassv2 but in performance I don't know.
rumirand said:
How it does perform for you the lazy governor? For me seems to be more battery lifesaver that smartassv2 bit in performance I don't know.
Click to expand...
Click to collapse
I will run smartassv2 for a couple of hours then lazy and see if i notice a difference i will post again tonight. In uk its only 1:00pm lol
Edit: Used lazy now for about 2 hours and battery has gone done about 3% compared to smartassv2 6% doing more or less the same tasks thanks again.
i have 2 questions..
1. does it come with camera/compass/sound fix?
2. is this upgradeable rom or wipe rom?
thanks in advance.
My scripts for the S2 have now all been updated and incorporated into my S4 scripts
Please see here
Old GS2 downloads
My scripts for the S2 have now all been updated and incorporated into my S4 scripts
Please see here
Time and time again I've seen people sleep around with different kernels and flash from kernel to kernel . In time without a good clean you will land into trouble and conflicts.
Welcome to the kernel clean clinic for those of you who flash without protection (ahem... Bob)
Doctor Hawker will cure many of the common issues that occur as mentioned on op.
Please use this as a first step when you encounter issues on a kernel especially if you hop onto another brand of kernel.
You will find debugging a lot easier. Trust me. :thumbup:
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk 2
Main ROM: Alliance rom v5.2
KERNEL : Dorimanx 7.39
(DEFAULT PROFILE AND SETTINGS )
MODEM : BVLP7
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex
My Guides list to install NeatRom and other ROMS and kernels on LSJ + tools to have a bug free rom + how to back up and RESTORE FOM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Current list of kernels on LSJ and pros and cons
http://forum.xda-developers.com/showthread.php?p=36698607
2.Rom Nuke script
http://forum.xda-developers.com/showthread.php?p=36268094
3.Kernel Clean script
http://forum.xda-developers.com/showthread.php?p=34879811
4.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
5. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
Nice job will use on next kernel flash.thanks
Subscribed.
Thanks
Subscribed too
big thanks to The Red Blur for introducing me to this script and thread :good::good:
Reserved thanks for your great job
Verstuurd van mijn GT-I9100 met Tapatalk
Nice job again Paul... well done! Subscribed.
Guys if you find this thread of value, don't forget to vote at the top of the page.
Thanks hawkerpaul, you are one of the best and most helpful dev I know here. :thumbup:
Sent from my GT-I9100 using xda app-developers app
Updated to V2.01
See Changelog
Great job, thanks.
Re: [CWM UTIL] Kernel Wipe Script
Muchas gracias, works great!
Sent from my Nexus 7
Works great! No issues while changing the kernel anymore
Thank you
Cool, thanks for sharing
This probably belongs in the Dev forum though
I read the thread....still question...
I normally use : ultimate kernel cleaning script 2.6
This is a pretty "old" file...
This is the new update for me?
ps, i always wipe cache and dalvik by hand after flashing the .zip
Re: [CWM UTIL] Kernel Wipe Script
marcel112 said:
I read the thread....still question...
I normally use : ultimate kernel cleaning script 2.6
This is a pretty "old" file...
This is the new update for me?
ps, i always wipe cache and dalvik by hand after flashing the .zip
Click to expand...
Click to collapse
The whole point is you don't need to do a whole wipe of delvik and cache?
I don't understand how you don't get that also this cleans specific folders which I belive UKCS never did where junk lies and could have led to conflicts.
All you need to do is flash this script, flash new kernel and fix permissions. That is it.
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk 2
Main ROM: Alliance rom v5.2
KERNEL : Dorimanx 7.43
(DEFAULT PROFILE AND SETTINGS with exception of AFTR turned on)
MODEM : BVLP7
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex
THE CAVE = My Guides list to install NeatRom and other ROMS and kernels on LSJ + tools to have a bug free rom + how to back up and RESTORE FOM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Current list of kernels on LSJ and pros and cons
http://forum.xda-developers.com/showthread.php?p=36698607
2.Rom Nuke script
http://forum.xda-developers.com/showthread.php?p=36742265
3.Kernel Clean script
http://forum.xda-developers.com/showthread.php?p=36742198
4.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
5. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
THE RED BLUR said:
The whole point is you don't need to do a whole wipe of delvik and cache?
I don't understand how you don't get that also this cleans specific folders which I belive UKCS never did where junk lies and could have led to conflicts.
All you need to do is flash this script, flash new kernel and fix permissions. That is it.
SIGNATURE
PHONE : SGSII
Sent via: Tapatalk 2
Main ROM: Alliance rom v5.2
KERNEL : Dorimanx 7.43
(DEFAULT PROFILE AND SETTINGS with exception of AFTR turned on)
MODEM : BVLP7
BATTERY : Stock 1650mAh
EXTERNAL Sdcard : Samsung Class 10 32gb
LAUNCHER : Apex
THE CAVE = My Guides list to install NeatRom and other ROMS and kernels on LSJ + tools to have a bug free rom + how to back up and RESTORE FOM FULLY = http://forum.xda-developers.com/showthread.php?p=35923600
1.Current list of kernels on LSJ and pros and cons
http://forum.xda-developers.com/showthread.php?p=36698607
2.Rom Nuke script
http://forum.xda-developers.com/showthread.php?p=36742265
3.Kernel Clean script
http://forum.xda-developers.com/showthread.php?p=36742198
4.Fast Dormancy :
http://forum.xda-developers.com/showthread.php?p=36396636
5. How to install full wipe with rom nuke on LSJ
http://forum.xda-developers.com/showthread.php?p=36655790
Click to expand...
Click to collapse
Because i was affraid off problems i asked..
Now, after flashing the script.....phone is extreme hot...no matter what rom i try...or kernel...
Flashed script after the kernel i fixed permissions...
Also...my sd card ext gives big problems....media scanner runs all the time, when i disable sc unusabble.
Re: [CWM UTIL] Kernel Wipe Script
marcel112 said:
Because i was affraid off problems i asked..
Now, after flashing the script.....phone is extreme hot...no matter what rom i try...or kernel...
Flashed script after the kernel i fixed permissions...
Also...my sd card ext gives big problems....media scanner runs all the time, when i disable sc unusabble.
Click to expand...
Click to collapse
Just to clarify, you did flash the script BEFORE flashing your kernel?
Media scanning is down to your rom. You may need to flash a media scanning fix, or you may have corrupt media files causing it to loop.
You can also create dummy files called .nomedia in any folders that you want the scanner to ignore which can speed things up significantly
Sent from my GT-I9100 using xda app-developers app
Re: [CWM UTIL] Kernel Wipe Script
Subscribing. :thumbup:
Sent from my GT-I9100 using xda premium
Re: [CWM UTIL] Kernel Wipe Script
Yes. Flashed the cleaner before I flashed new kernel..
Sent from my GT-I9100 using xda app-developers app
I'm running Omega Rom 43.1 as my primary rom on my Samsung Galaxy S3 I9300, I'm trying to dual boot paranoid android 3.1 as my 2nd rom.
When I press 'volume down' or 'home button' to boot into the 2nd rom all I get is a black screen and nothing will happen. I've followed the steps by
'Format 2nd rom > wipe 2nd rom data/cache > wipe 2nd rom dalvik cache > install 2nd rom from internal SD'.
Is there something I'm doing wrong please help
Siyah does not yet support the new Android versions... clearly stated in the siyah discussion thread
Sent from my GT-I9300 using xda app-developers app
Hi
But in their page they said that in the new kernel it was fixed, they say this:
cm10.1 is now supported in dual-boot configurations
1.8.7->1.8.8: fixed cm10.1 not booting when installed as 2ndROM (a tiny typo in ramfs)
1.8.8->1.8.9: fixed the problem when installing cm10.1 directly as 2ndROM. fixed bluetooth issue in cm10/cm10.1 (credits to Entropy512, just cherrypicked his commit from CM10.1 kernel repo). added profile support back to support droidphile’s
So what it does that mean?
The versions of CM 10.1 before 27th (?) are running, whereas later versions not. Reason is the update MALI drivers of new android versions and Siyah was not yet adjusted to it. We have to wait for an updated Siyah kernel.
chrismast said:
The versions of CM 10.1 before 27th (?) are running, whereas later versions not. Reason is the update MALI drivers of new android versions and Siyah was not yet adjusted to it. We have to wait for an updated Siyah kernel.
Click to expand...
Click to collapse
Ahh ok thx for clarifying this
Hi
i have a problem with my phone Galaxy S duos S7562 ! :
1- When i turn it off ! 90% of times when i try to re-turn on it stucks 3 seconds on the starting screen (galaxy s duos....etc ) then goes off ! so that i should every time pull the battery off and put it again to make it start normally ! this is the first problem.
2- when i put the charger on it it charges normally, when i pull of the charger the indication of charging still displayed untill i restart the phone .
can you help me plz ?
PS: Sorry i know i have a bad english i wish you understand my two problems
chegue4 said:
Hi
i have a problem with my phone Galaxy S duos S7562 ! :
1- When i turn it off ! 90% of times when i try to re-turn on it stucks 3 seconds on the starting screen (galaxy s duos....etc ) then goes off ! so that i should every time pull the battery off and put it again to make it start normally ! this is the first problem.
2- when i put the charger on it it charges normally, when i pull of the charger the indication of charging still displayed untill i restart the phone .
can you help me plz ?
PS: Sorry i know i have a bad english i wish you understand my two problems
Click to expand...
Click to collapse
I think you should try your luck with backing up all your stuff and flashing stock Rom !
Stock Rom
I Think First The Kernal Or Rom Is Unstable Try Flashing Stock Rom ...
After Doing This If Problem Solved Then Try Other Rom Nd Install It Perfectly if u want as it was Not Installed Pecrfectly last Time.
If Problem Continues Then Its Must Be Hardware Problem...
This Can Also Happen If Water Has Entered Ur Phone ....
Solution
The main causes of bootloop are listed below:
1.Flashing multiple tweaks
2.Changing custom ROMs without reading the procedure
3.Flashing Kernels one over the other
The following kernel order is placed on general forum for my phone but maybe you can try it too but I don't take responsibility for any damage occuring to your phone:
1).If you are on stock kernel:
you can flash any kernel without bricking your phone...
2). If you are on savie kernel:
1)Stock on savie -- ok
2)white kernel on savie-- ok(you will not get soft bricked but may get busybox problem)
3) hells kernel on savie--ok
4) devient kernel on savie--ok
5) merruk kernel on savie -- ok
6) black reactor kernel on savie--ok
7) kuro kernel on savie-- ok
3) if you are on white kernel:
1) stock kernel on white-- no
2)hells kernel on white-- no
3) savie kernel on white --ok
4) merruk kernel on white --ok(but it is better to flash stock kernel via odin)
5) black reactor kernel on white--no
6) devient kernel on white-- no
7) kuro kernel on white -- no
If you are on merruk kernel:
1) stock kernel on merruk--no
2) white kernel on merruk--ok
3) all other kernel : no
If you are on hells kernel:
All kernels except merruk kernel ....
1) If you are on kuro kernel:
1) Stock kernel on kuro -- ok
2) savie kernel on kuro -- ok
3) white kernel on kuro -- NO
4) merruk kernel on kuro-- NO
5) devient kernel on kuro -- ok
6) black reactor on kuro -- ok
2) if you are on devient kernel:
1) stock kernel on devient-- ok
2) savie kernel on devient --ok
3) white kernel on devient-- ok (but may get busybox problem)
4) merruk kernel on devient -- ok
5) hells kernel on devient--ok no brick (but i got bootloop problem rom-jellynoid)
6) black reactor kernel on devient --ok
7) kuro kernel on devient --ok
3) If you are on Jarvis kernel:
1)White kernel over Jarvis -- ok
2) hells kernel over Jarvis -- OK
3) all other kernels -- NO
4) If you are on Percy cm#2 :
1)Hells kernel over Percy -- OK
2) savie kernel over Percy -- ok
All other kernel -- NO
I don't know whether you have these kernels for your phone. If yes, then you can use it.
Solution:
1. Flash kernel before you flash a ROM.
2. Don't use multiple tweaks. Select the one or two which is the best ones and also compatible.
3. Reflash Stock Kernel and Stock ROM.
Hi
I rooted my s duos with unlock root pro software. I want to install cwm nd custom rom without pc. What is the best rom available. If I install custom rom means shall I move app to sd. Suggest me some apps that records two ways call.
Thanks
Sent from my GT-S7562 using XDA Premium 4 mobile app
Recommend
vino.rk said:
Hi
I rooted my s duos with unlock root pro software. I want to install cwm nd custom rom without pc. What is the best rom available. If I install custom rom means shall I move app to sd. Suggest me some apps that records two ways call.
Thanks
Sent from my GT-S7562 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It is recommended to have a backup of all your data before you proceed. I am telling this from my experience. I am using Samsung Galaxy Y GT-S5360 mobile. You can download the CWM and custom ROM through mobile. Installing a custom rom doesn't allow you to move your apps to sd. You should need to create a second partition in sd card and link it with internal memory using link2sd. If you create second partition, you will lose all the data stored in sd card. Search on google play with keyword: call recorder.
Please press thanks if I have helped you. Also I don't know much about your phone.