Related
This is Voodoo LagFix beta4 for the Vibrant. It does not include color adjustment just the /data as ext4. This has been tested by many users and is confirmed working, including GPS WiFi BT etc. There is also the performance increase of course as well due to the Voodoo lagfix and the optimized Kernel with OC option.
WARNING BEFORE FLASHING:DISBALE ANY LAGFIX'S YOU MAY ALREADY BE USING BEFORE APPLYING THIS FIX - IS NOT COMPATIBLE WITH THE LATEST LEAK JI2
Samsung has not provided us with the kernel sources that were used in the latest leak (which are different) so until they do we cannot support it.
To enable simply flash the kernel. It will automatically backup your existing /Data partition and create the /data as ext4 and restore so you dont lose your data of course.
To disable simply place a file/folder in the "Voodoo" folder on your SDcard (the internal one) called "disable lagfix" (e.g /sdcard/Voodoo/disable lagfix") no extention just that exact name and reboot. After your phone boots and you check that your /data partition is again RFS you can re-apply any other kernel you were using.
Upon enabling or disabling your phone will sit on the Vibrant screen. This can take 5-10 minutes depending on how much data you have (don't panic). "Linda" the robotic voice should let you know where in the process you are. After its done and your phone boots you should be able to run "mount" in terminal or adb shell and see your data is now EXT4 at
Code:
/dev/block/mmcblk0p4
Disabling by placing the "disable-lagfix" file in the "Voodoo" folder in your sdcard and that simply undoes what the enable did and returns your /data to the RFS setup at its original location.
PLEASE READ
The kernel boots to stock clocks but CAN be OC'd to 1.2Ghz via setupCPU or a user script. If you want to keep the phone OC'd just use setCPU and check apply on boot or use a user script that launches from /system/etc/init.d. If you want to run stock clocks just boot and don't do anything
NOTE This kernel does not need the init.d folder to be present to flash but will parse it if it is there. Also this kernel includes almost all the optimizations my OCv4 kernel so you get the best of both worlds if you want. Voodoo plus OC!
So a simple install routine through recovery would go like this
1.Flash a ROM and root it or flash one that is already ROOTED
2.Download beta4 Voodoo .zip file
3.Reboot into Stock recovery and flash the update.zip made for STOCK recovery.
4.Listen to "Linda" the robot tell you the progress as Voodoo does its thing.
RECOVERY UPDATE
Voodoo Beta4 UPDATE.ZIP
EDIT:Voodoo Beta4 Update zip you can install through STOCK recovery
http://project-voodoo.org/downloads/Voodoo-lagfix-3.0-SGH-T959-update.zip
Clockwork Version by request
www.justanotherdev.slackdev.com/Vibrant-Voodoo_beta4.zip
ODIN UPDATE
Vibrant Voodoo Lag-Fix Beta4
http://project-voodoo.org/downloads/Voodoo-lagfix-3.0-SGH-T959-odin-pda.tar
KNOWN ISSUE:To perform NANDroid backups or restores through clockworkmod recovery please disable the lagfix before either operation otherwise it will not work.
Big Thanks to supercurio for the Voodoo project and for letting me share it with all the Vibrant users out there.
reserved for future use...
I love you.
Going to test in a few. Do you know where we can get the disable-lagfix file? Your OP doesn't include it. =)
EDIT: Nevermind. I should have read more carefully. THANKS AGAIN JAC!
I just flashed the Leaked TMO Kernel with the GPS Fix... can I flash this Lag FIx?
Thanks a lot man! Really appreciate you giving us something to tinker with, been dying to try this out
Will users who already are using 1-click lagfix need to do anything differently in order to use this?
Goog1e Phone said:
I love you.
Going to test in a few. Do you know where we can get the disable-lagfix file? Your OP doesn't include it. =)
Click to expand...
Click to collapse
You just have to name a file "disable-lagfix" and throw it on you sd card. It shouldn't actually have any data in it.
acis said:
Will users who already are using 1-click lagfix need to do anything differently in order to use this?
Click to expand...
Click to collapse
Ya, restoring back to stock or removing the lagfix if its possible. You cannot apply this if you already have a lagfix. Remove it or restore to a previous backup before you were using the lagfix (you made one, right )
just installed on Eugene's r3 rom, and it feels very snappy, can't wait for beta 3, thanks!
Edit: just did a second reboot, and I'm getting an error about a blank internal SD card, and all my data is missing. Any ideas on what I did wrong? I had a lagfix previously installed but had reflashed r3 and didn't redo the fix(not a nandroid just a new flash)
Sent from my SGH-T959 using XDA App
zimphishmonger said:
Ya, restoring back to stock or removing the lagfix if its possible. You cannot apply this if you already have a lagfix. Remove it or restore to a previous backup before you were using the lagfix (you made one, right )
Click to expand...
Click to collapse
Yes. I didn't want to go that far back but meh. 1 click doesn't seem to be working very well tbh.
Appreciate all the hard work that goes in to making the phone actually operate as it should have on day 1. This community is amazing.
It does NOT work on the new leaked rom, fyi :O)
If you are using the leaked rom and you flash this you will need to flash the original rom and check repartition to restore your phone.
Do you need to flash the init.d update before flashing this kernel as with your previous kernels?
Dude this is fast... thank you def. worth the wait so far. the lag is gone! i cant wait to see what you guys come up with next.. its like christmas every few weeks
Eugenes Hybrid r2
Babyface1249 said:
Do you need to flash the init.d update before flashing this kernel as with your previous kernels?
Click to expand...
Click to collapse
No. Just flash the kernal through clockwork. No other steps are needed, unless you already had a lagfix prior.
Goog1e Phone said:
No. Just flash the kernal through clockwork. No other steps are needed, unless you already had a lagfix prior.
Click to expand...
Click to collapse
Giddy up. Flashing now before I get my second replacement vibrant tomorrow lol
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Man this thing is FAST! I say we start calling this fix the doodoo lag fix instead because this thing is the SH*T!
itsjusttim said:
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Click to expand...
Click to collapse
How long did you wait when it was on the Vibrant screen? The OP says it will usually stay on the VIBRANT screen for 5-10 min before it boots up depending on how data you have.
Goog1e Phone said:
How long did you wait when it was on the Vibrant screen? The OP says it will usually take 5-10 min on the Vibrant screen before it boots up depending on how data you have.
Click to expand...
Click to collapse
waited 20+.. nothing!
is there anything i can do? SH*T, i need this phone for work...
itsjusttim said:
HELP!!
i just flashed this through recovery and now my phone wont boot up... just stays at vibrant screen.
when i try to get back to go through "reinstall packages" to get back to nandroid i get stopped. it says...
--install from sdcard...
finding update package...
E:cant mount /dev/block/mmcblk0p1 (or /dev/bloc/mmcblk0)
(device or resouce busy)
E: cant mount SDCARD :update.zip
Installation aborted.
AHHH! what do i do?
Click to expand...
Click to collapse
Did you install the leaked rom? You will need to go back to the stock rom in ODIN and check the repartition box. Follow my instructions here: http://forum.xda-developers.com/showthread.php?t=780935 but use the original rom
Hello all.
I've compiled the latest ClockworkMod recovery for the Tattoo. In addition to the normal features it has, this is using a custom smaller font, so the text fits better on a QVGA screen.
If you're already rooted, you can flash it with "flash_image recovery recovery.img" (after running "su" first) from a terminal shell prompt, or from adb shell.
v2.5.1.8 is the last version included in CyanogenMod 6 sources
v3.0.0.5 is the new recovery from CyanogenMod 7 sources
How to flash instructions
Credits:
CM Team/Koush
KalimochoAz
NForce2506.02.2011 - Repack of 3.0.0.5 with advanced backup and wipe all function. Wipe all will completely format and erase all partitions.
Can you please tell me, in what way exactly is this Recovery better than Amon-RA?
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
arco68 said:
They both do the same basic things. What I find better with ClockworkMod is:
Can turn off signature verification (faster to install roms, and can install unsigned zip files)
Can select zip files in subfolders
Individually select which NAND partition to restore
Can use joy button and back key to navigate
Smaller font (in this special version), so you get to see all text on screen on QVGA devices
Click to expand...
Click to collapse
Is possible to add Ps3 Jailbreaking?
francians said:
Is possible to add Ps3 Jailbreaking?
Click to expand...
Click to collapse
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
arco68 said:
You would need to ask the ClockworkMod author for that feature I'm afraid, but I doubt he well add it. Take a look here though.
Click to expand...
Click to collapse
I asked a couple of weeks ago, but no answer.. I realy like clockworkmod and I'm afraid to change recovery.
Thanks. Good job!
Amazing recovery
Thank you very very much for this recovery. ROM Manager now works properly. BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
sunitknandi said:
BTW, where do I download ClockworkMod Recoveries for HTC Wildfire with my computer? I dont want to use my expensive 3G connection to download and want to use the school network.
Click to expand...
Click to collapse
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
ClockworkMod recovery for the Tattoo isn't added to ROM Manager yet. Until now Tattoo owners had to use the Wildfire/Buzz recovery. I'll contact the author and ask if he can add this recovery for the Tattoo, so it's available from ROM Manager.
Downloading images
arco68 said:
Only available through ROM Manager as far as I know, unless someone compiled it and made it available over at the Wildfire forums.
Click to expand...
Click to collapse
If I knew where the images were hosted, I could fetch them through PC.
sorhe said:
ROM manager does not work with me although I´ve installed this recovery... It seems that the rom manager does not recognize it and it keeps asking me to download clockwork recovery again, and there is no Clockwork recovery for tattoo in that menu????
What seems to B the problem??
Click to expand...
Click to collapse
Press menu button and select "manually installed clockworkmod" or similar option.
sunitknandi said:
Press menu button and select "manually installed clockworkmod" or similar option.
Click to expand...
Click to collapse
That doesn´t help!
With clockworkmod recovery I cannot flash some roms which flashed fine with maverick recovery. The installation aborted with this error:
E:Board does not support mtd utils.E:Failure at line 420:
write_raw_image PACKAGE:boot.img BOOT:
The rom is actually flashed, and only boot.img not. So I can boot the rom after manually flash the boot.img.
Is there any way to include mtd utils future in this recovery, or must to return to maverick?
I think it's a bug in clockworkmod. They changed some detection routines in the latest versions, which seems to have broken flashing to mtd when rom is using update-script instead of updater-script. I've heard that 2.5.0.9 is the latest which it worked correctly with. I'll look into it at some point unless they release a new version which fixes it.
clockworkmod 2.5.1.4 seems to be already out!
arco68 please could you take a look here: https://github.com/klutsh/android_bootable_recovery
or here: https://github.com/klutsh/psfreedom-kernels-patch
could you add psFreedom support?
edit: please fix also the font size for the tattoo screen
I suppose it can be done, so I'll take a look. Thanks for the links.
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
arco68 said:
Ran into some problems with the psfreedom recovery. Patching the kernel and compiling the recovery wasn't a problem, but mounting usb mass storage doesn't work. As far as I can see, there seems to be some bits missing in one of the files for the kernel patch for the Tattoo. I could have used the code from one of the other phones kernel patches, but unfortunately the kernel for the Tattoo is just too different from the other ones, that it can't be easily done. Dunno who the hell coded the board sources for the Tattoo, but I suspect he got fired or something, because sources for all other phones after the Tattoo are much more organized and similar to each other.
Click to expand...
Click to collapse
I think is very hard find what's missing to make it works.. can you do it?
I know you are workin' also on a wonderful rom, but also psfreedom is a nice project that need a skilled man
I see the kernel patches for the Tattoo is no longer there. When he adds a working patch I'll try again.
ClockworkMod Recovery 3.2.0.0
Note:
Amend scripting (update-script) is no longer supported, was deprecated by Google in Android 1.5. Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.
Current version: 3.2.0.0-(01.06)
Recovery_Optimus_2x_3.2.0.0-(01.06).zip
MD5: 1e97b2c8a0d4b84e11ec2f31e51f83ca
SHA-1: 2f7cd8cdf8e239886e31497dcffc9e5026606155
Installation:
Unzip the archive
Plug-in the USB cable and select enable the "debug mode"
Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
Done!
If you want to thank me, click the Thanks button.
Old versions:
Recovery_Optimus_2x_3.2.0.0.zip
Changelog: http://goo.gl/MAuLi (2011-05-30)
Sources available here: https://github.com/CyanogenMod/android_bootable_recovery
All credits to koush for this recovery, I only compiled them!
All Ok with this version!! no /cache umount
Perfect ....
As always one step ahead....
When entering Recovery menu, device vibrates all time long. =/
Good to see you here. Gonna try tomorrow!
Sent from my LG-P990 using XDA App
Just installed. This version is perfect. Thanks.
how come i cant find it in rom manager?
Sorry for a noob question, but with previus version I cannot install CM7 #31.
Can I install this rom now?
ranrick said:
When entering Recovery menu, device vibrates all time long. =/
Click to expand...
Click to collapse
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
initrd said:
good to know i'm not alone. happens on my CWR that RomManger loads too (3.0.2.8?)!
Click to expand...
Click to collapse
Yeah, 3.0.2.8 didnt work either. Only 3.0.1.4 works without vibrations.
Works like a charm.
Anyway to add this aswell: http://forum.xda-developers.com/showthread.php?t=1098745
So you have 2 option.
Internal Sd and External Sd?
That would be awesome!
USB mount doesn't work. Is it me?
Recovery shows 3.2.0.0 but the app still reports it as 3.0.2.8 - is this for compatibility?
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
75markus said:
recovery works fine, thank you, but i noticed a tiny bug:
date of backup is wrong, it shows me 27.04.2011 instead of 27.05.2011
(Time & date settings on phone are correct of course ...)
Click to expand...
Click to collapse
yep. same thing (like at 3.1.0.1)...
just made a nandroid restore and recovery can't mount /boot during restore.
It's probably why we can't ( for exemple ) flash a CM rom ( after nandroid stock rom ) play with it and if you want to return to stock rom using your backup you get a bootloop
Quite common (and annoying), that. Happens each time I've restored a CM NANDroid, have to restore, then reflash CM.
hi. just a noob question
can i use this recovery to flash all the roms for the optimus 2x. like modaco, cm7 and other modaco based custom roms. ?
i been reading the forums and there are so many recoveries. im kinda confused.
Yes you can.
There are only 2 types of recovery in reality, this type (external SD) and the one I built for internal SD use. If you're not sure what you need, pick the external one (unless you don't have an SD card).
bit of a noob..but cant seem to be able to install it. can someone give me a guide to install this with a mac thanks in advance
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Wildfire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications. Can be installed with unrEVOked. Installs and works well according to users in this thread. Off-mode charging works according to t0mas_.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-buzz.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-buzz.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
Flash like a normal ROM ?
Use it with unrevoked then custom recovery in the menu and use the image file in the zip
If you're testing it, let me know if it works.
Sent from my Nexus S using Tapatalk
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Well my phone was installed and works well ...
t0mas_ said:
does this include off mode charging fix?
http://forum.xda-developers.com/showthread.php?t=1014498
Click to expand...
Click to collapse
No idea. It depends on the CM7 3.2.0.0 recovery source code. I didn't change anything, and I'm quite sure j_r0dd didn't touch this.
cse.10100 said:
Well my phone was installed and works well ...
Click to expand...
Click to collapse
Great! Updating the OP.
thanks, i'll try this out when i find time
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
aggourodolmas said:
one silly question. I use as recovery clockwork 2.xxxx version for a long time now since I first rooted my device with Unrevoked tool. If I flash this new recovery or any other recovery with unrevoked will it create another superuser option that will conflict with the one that was created from the first root?
Click to expand...
Click to collapse
Well, the recovery image itself doesn't touch superuser, but unrevoked will. I belive that you might be downgrading the superuser binary, but (at least for CM7) a reflash with the same zip without wiping anything should restore the superuser binary that was included in your ROM. It should work on other ROMs as well, as long as they're not wiping /data or /sd-ext while flashing for some reason. Make a nandroid backup before you consider flashing this recovery, that's my advice.
Can anyone confirm if this supports off mode charging?
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
Not sure where to look, but maybe one can search for this in some type of changelog for the official cwm repository.
s0ulbl5d3 said:
Can anyone confirm if this supports off mode charging?
Click to expand...
Click to collapse
works for me
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
rseke said:
How can i update this clockwork image,i cant see the image in clockworkmod,i just can see zip files.
Click to expand...
Click to collapse
You need to use unrevoked to flash the .img file.
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
rseke said:
ok but how,what i must to do ?
i cant find step by step manual fot clockworkmod update from img file.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12548919&postcount=26
Unrevoked 3.14 can be found in the same thread on the first page.
Thanx for fast reply and for help.
I have one problem now,mu super user app not working how can i fix that,i cant enter to superuser app to update su binary,force close.
By example of this thread, I thought it would be convenient to also create a separate thread for our L5. I will update this first post with relevant information and links when needed.
Info
CyanogenMod's site: http://www.cyanogenmod.org/
Announcement on Google+ by CM: link
Screenshots by luKi13223: link
Screenshots by Sirrocco with dpi lowered to 130 and theme applied: link
Requirements
Properly unlocked boot loader (here, a guide on top of first post)
Root/working CWM
Ability to read and common sense
Downloads
Nightlies started building. You can get the latest build from http://get.cm/?device=e610 OR http://10.cmxlog.com/?device=e610
CWM Recovery by Ricardo Cerqueira (CyanogenMod): Direct download. Alternatively you can download the flashable zip provided in the attachment, it's the same, but easier to install if you already had a recovery installed.
Google Apps (GAPPS) for Jelly Bean/CM10: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Short Installations guide
Make sure you meet the requirements
Download needed files (see above) and place them on your internal sd card
Update your ClockWorkMod Recovery to v6.0.2.8 (you can do this by using terminal, adb (guide) or use the flashable zip I've attached
This will avoid status(7) error messages and prevent issues with ROM Manager.
Flash "cm-10-build date-NIGHTLY-e610.zip" from your internal sd card with CWM (or if you prefer with ROM Manager)
[*]Optional: Flash custom kernel by PinkFlozd: link to thread WARNING: Don't install this kernel with builds created on 21 april 2013 or later (at least not untill someone updates the kernel)
Optional: Flash "gapps-jb-20121011-signed.zip"
After first boot see if your receiving any signal (provided your normally have any signal on that spot). If not, don't worry, a simple reboot might fix it.
Enjoy
Bugs:
Considering these are the very first nightly builds of CM10 for our device, the dev did a pretty great job. Almost everything is working. Thanks to him :highfive:
Network / data is not working after 1st boot. A simple reboot after a few minutes might fix this
Multi-touch not fully working (dual touch works)?
SD card is full error, while there is still room left (up to at least 300 MB). I haven't experienced this bug in a while, it may be fixed, but I'm not sure.
Accelerometer
Small mods/Fixes
Wake with Home key
Pinkflozd's custom kernel[/COLOR]. Supports multi-touch and allows for overclocking. His kernel doesn't work with builds after April 14th
Overclocked kernel for builds made after April 14th
Workaround to make accelerometer work
:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Ianuz1320 said:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
same here...
Will the developer look here for bugs? Or is there some other way to report CM10 bugs?
Anyway, I noticed that it drains battery much faster than the stock rom too.
Tonight it drained 20% of battery just by standby.
Ianuz1320 said:
i tried to flash this on my E612..
But i got an error.
Error in sdcard/cm blah blah.zip
(status 7)
Installation aborted.
Click to expand...
Click to collapse
First install the recovery provide by CM. This will fix this problem. You will need to copy your flashables zips and back ups to the internal SD-card, because this version only mounts internal SD (instead of only the external)
E.jr said:
Will the developer look here for bugs? Or is there some other way to report CM10 bugs?
Anyway, I noticed that it drains battery much faster than the stock rom too.
Tonight it drained 20% of battery just by standby.
Click to expand...
Click to collapse
I don't know if he will look here. We could inform him about it, when we have more clarity about the bugs.
My main purpose was to concentrate talk about CM10 in one place, because in the other thread also other subjects were discussed and it got messy. And we might help each other here with CM10 related problems.
ldeleeuw said:
First install the recovery provide by CM. This will fix this problem. You will need to copy your flashables zips and back ups to the internal SD-card, because this version only mounts internal SD (instead of only the external)
Click to expand...
Click to collapse
thank you buddy..but where can we get recovery provide by CM?
For Instalation aborted :
Open downloaded zip by winrar or 7zip.
Open Meta-inf>google>android>updater-script
Open updater-script by notepad++
Delete first lane in updater-script
Save and rebuild archive (automaticly)
Copy your package to sd card and instal via cwm
Kisloo said:
For Instalation aborted :
Open downloaded zip by winrar or 7zip.
Open Meta-inf>google>android>updater-script
Open updater-script by notepad++
Delete first lane in updater-script
Save and rebuild archive (automaticly)
Copy your package to sd card and instal via cwm
Click to expand...
Click to collapse
it's not working buddy.
delete this lane :
assert(getprop("ro.product.device") == "e610" || getprop("ro.build.product") == "e610");
Click to expand...
Click to collapse
and it will work
Thanks buddy.. it worked on my phone!! but first boot took so long..i was stuck on CyanogenMod boot logo!! untill now!
Ianuz1320 said:
thank you buddy..but where can we get recovery provide by CM?
Click to expand...
Click to collapse
check first post
The new nightly does seem to lag a little as opposed to the original one.
The first one was smoother I've noticed.
E617
Has anyone tried CM10 for the E617 version of the L5? I'm to much of a newb to try it myself, I wouldn't be able to find my way back if I screwed-up my phone.
Bootlop
Im on cm bootloop about 20 minutes WHEN THIS WILL BOOT UP
I noticed that this cm10 for e610 has a kind of problem with multitouch,I have played shadow gun,modern combat 3 and modern combat 4 and six guns and in all these 4 games, I noticed that I can't move at the same time that I shoot,I wait that they solve this problem in next updates ;p
Sent from my LG-E610 using xda premium
Kisloo said:
delete this lane :
and it will work
Click to expand...
Click to collapse
thanks a lot mate!
---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------
DodoKoce said:
Im on cm bootloop about 20 minutes WHEN THIS WILL BOOT UP
Click to expand...
Click to collapse
E: I found out why there is a bootloop, we didn't took the right bootloader, see here my tutorial: http://forum.xda-developers.com/showthread.php?t=2186161 - if you do everything like i did, everything will work properly
Use older build, idk - new is more bugged :/ Old working smarter than new.
OK, I've got it installed (nightly 20130310), first I installed the provided CWM (6.0.2.8), had to do that manually though, because for some reason Rom Manager destroyed the 6.0.2.5 version I had when I tried to install CWM through Rom Manager.
It's running smoothly, although I also see a little graining in the screen. I had no data issues.
Also, booting didn't take that long.
One strange phenomenon:
I had FreeL5 running before CM10. Before flashing CM10 I did a factory reset from CWM, cleaned cache and Dalvik cache. After booting CM10 for the first time, my WiFi settings were still there... hadn't expected that, but since I'm on a corporate WiFi connection which needs a username and password to connect, it was nice not to have to retype it :victory:
---
Previous devices:
HTC Desire - MIUI
HTC Desire HD - MIUI
Sony XPeria S - FreeXPeria JB
Current devices:
Samsung Galaxy Tab 2 7.0 - Stock JB (because my girlfriend doesn't want me 'messing' with it)
LG Optimus L5 (E610) - CM10 nightly
Bootloop too, any way to solve?