Related
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?
This is my first guide so if I left something out please tell me.
I do not take any credit for any of this work. I just read in a thread how another user did it. I tried it and it worked.
This isn't nessassarily the right way to do this but this is what I did, and all don't from my nexus 7.
I've only tried it on slimkat. I'm going to be testing more ROMs today.
Thanks to
Legolas93
Slimroms.net
ryanrudolf
Things you will need:
A file explorer (I use solid explorer)
Zip app to extract and compress ( included in solid explorer)
Modified TWRP recovery from this post.
1. Download the latest weekly build of Slimkat. http://slimroms.net and extract the zip file to a folder.
2. Next either download the last build from legolass of slimkat here and extract it to its own folder or download attached boot.IMG and updater-script. (Only 2 files that I found that needed to be updated.)
3. If you just decided to download the attached files, extract the archive and inside you will find 2 files. Copy boot.IMG into the root of latest slimkat that you already extracted, overwriting when prompted. Next copy updater-script to./META-INF/Com/Google/android. overwriting when prompted.
If you didn't download the files from the post and choose to do this manually. Just follow above directions and get the files from the latest slimkat f2fs. Same directories.
4. Now its time to zip up the archive so we can flash it. Zip the files so the root of the archive is the same as the one you extracted. Meta-inf, system, Boot.IMG and file_contexts.
5. Flash in twrp.
B]List of working roms.[/B]
Liquid Smooth
Slimkat
CyanogenMod (with method below)
Tested but not fully working.
Paranoid
Method for CM By ryanrudolf
CM Nightly with All-F2FS (Unofficial Method)
1. download latest CM nightly (here is link for CM Nightly already modified for ALL-F2FS http://d-h.st/9By )
2. download faux025 kernel.zip
3. open CM nightly zipfile, extract the boot.img
4. open faux025 zipfile, extract the zImage
5. unpack the boot.img in step3
6. replace the zImage in step5 with faux025 zImage (step4)
7. replace fstab.grouper with this one -
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system f2fs ro,noatime,nosuid,nodev,discard,nodiratime,inline_ xattr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,discard,nodiratime,inline_xat tr,errors=recover wait,nonremovable,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci auto vfat defaults voldmanaged=usbdisk:auto
8. repack boot.img. place it back in the CM nightly zipfile
9. on the CM nightly zipfile, edit updater script and look for these 3 lines -
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace it with
run_program("/sbin/busybox", "mount", "/system");
and these lines too -
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replace with -
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/busybox", "mount", "/system");
10. save the updater script and put it back to the zipfile. CM nightly zipfile is complete and ready for flashing.
11. flash modded twrp with f2fs support. also download the formatpartitions.zip (credits to legolas http://forum.xda-developers.com/show....php?t=2678140)
12. boot to the modified twrp, flash the formatpartitions.zip. reboot back to recovery
13. flash the modified CM nightly zipfile
14. flash gapps.zip (i use slimroms minimal gapps)
15. Wipe > Format Data > yes
16. reboot
17. enjoy!
NOTE - everything is CM ramdisk, except for the fstab.grouper. If I use the original CM fstab.grouper and just edit to f2fs, it does not work.
Credits -
Legolas for the modified TWRP with F2FS
Faux for faux025 kernel with F2FS support
CM for the CM Nightlies
SlimRoms for the minimal gapps
[
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
SkOrPn said:
Thanks again. I will give this a try very soon. Glad someone figured out what these devs are doing. I hope others will come in here and share even more information. :good:
EDIT: So, you managed to do all of this on your device? Wow nice work.
Click to expand...
Click to collapse
Ryanrudolf in the all f2fs slimkat thread said what files he changed. I just followed his direction.
And yes I did all this from my n7.
No problem I'm glad I could contribute.
Sent from my Nexus 7 using XDA Premium HD app
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
ronedogg said:
Any ROMs u want me to test? I'm about to try paranoid 4.2 beta 2 (latest)
For all the other ROMs I'm going to remove the slimroms text that scrolls in twrp when installing. I'll update the op with unbranded updater file so they can try it on other ROMs and not get confused lol.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that would have been great, but the dev on my preferred ROM is already working himself to figure it out. I'm probably going to be testing his latest build here soon. I just want to know what you guys did so that next week, when I want to try another ROM I will have a larger menu to choose from
If you want to mess around and test several ROM's I suggest you try AOSPAL SaberDroid in your list. There will be a new build here soon, maybe today I think.
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
That is a known issue with CM, not this mod. I get that same FC when I use CM11. Its not there on Slim, or Omni or AOSPAL, using the same mod.
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build.
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue (i replaced boot.img with the one you attached).
Click to expand...
Click to collapse
Hmmm. I tried paranoid and got the same result but was keyboard throwing up error....
In the all f2fs slimkat thread another user said he tried cyanogen as well and got same error. Maybe this is just for slimkat, I thought we might have gotten lucky.
I'm going to try to compare the updater scripts for cm and pa with the slimkat script. See if there is something obvious we can change.
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
SkOrPn said:
Actually I take that back, I never tried straight PA, just modified versions of it. I only get that message with CM11.
Click to expand...
Click to collapse
looking at comparing files now.
in cm latest nightly there is a line of code refering to f2fs already.
symlink("../bin/fsck.f2fs", "/system/bin/dump.f2fs");
not sure what that is.
im gonna upload a updated version of the script for cm. Using notepad ++ and compare plugin, should have something shortly that i can test.
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
PatrickMac said:
Just tried this with the latest liquid smooth build, works fine so far. no fc and running really smoothly
Click to expand...
Click to collapse
sweet!. im going to update the OP with working roms.
Thanks for testing
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
SkOrPn said:
Just a suggestion, I would rename the thread to
[Guide] Converting ANY ROM to All-F2FS Partitions - Working ROM list Included!
Click to expand...
Click to collapse
it wont let me rename the title
2 failed attempts at editing the updater script on paranoid.
onto 3rd attempt.......
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
ronedogg said:
after some testing I got paranoid to install. but when i install gapps package all kinds of errors get thrown up....
waaay over my head there. ill try again later tonight see what I can come up with. i might be close... I might be waaay off.
maybe someone will see this thread and give me some pointers.
Click to expand...
Click to collapse
Haha, that's how I felt the weekend before last when I spent 20 straight hours trying to figure this out.
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
CptKlink said:
I have seen a few people ask for this so i'm going to try and edit the SlimRoms SlimBean 4.3.1 version of there rom to see if i can get this working on 4.3.1 Jelly Bean Roms.
I have already edited the fstab file in the SlimBean 4.3.1 kernel/boot.img and have already edited the updater script now just doing a backup of important stuff and going to give it a try
Click to expand...
Click to collapse
Good luck. :good:
carlo93 said:
Hi there,
since i like cyanogenmod, i tried to apply your 'patch' to a cm build. (i just replaced some rows in the updater-script and replaced boot.img in the zip file)
It worked, since the rom booted up but it costantly throws 'Unfortunately, the process com.android.phone has stopped'...
I (hardly) managed to enable developer settings, adb and check mount command output (just to be sure that system, data and cache were mounted in f2fs) and they actually are f2fs.
I guess that com.android.phone message is a kernel related issue.
Click to expand...
Click to collapse
same i got that error too on the latest nightly of CM.
will try more on weekend
Sent from my C6503 using Tapatalk
Error message during failed install of CM zip: assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
Solved: See below.
When I first got my HD+, I did an SD "install" of CM 11. Then I installed CM 11 to the emmc, via CWM, per all the instructions on the xda website.
Once CM 11 was installed, I changed to TWRP 2.6.3.0. (I like being able to name the backups.)
Then I did a wipe and dropped down to CM 10.2.1. (More stable.) I did the install from TWRP.
Then I installed the fuzz kernel from TWRP.
Last, I updated to TWRP 2.6.3.0a when I couldn't get Succulent's CM 11 to install.
Okay, so tonight I wanted to do a clean install of CM 10.2.1, without gapps this time.
So I booted to recovery, did a wipe, and tried installing CM 10.2.1.(The build came direct from Cyanogen mod's website for the Ovation.)
I get an error similar to what I got when I tried to install Succulent's CM 11. Here's the error message:
assert failed: get prop ("ro.product.device") == "ovation" || get prop ("ro.build.product") = ="ovation"
I dropped back to CWM and tried installing the ROM from three different versions: CWM 6.0.4.5, 6.0.4.5b, and CWM 6.0.4.6.
I tried installing CM 10.2.1 from the internal and the external SD card.
No joy. Fortunately, a Nandroid backup beforehand and I've restored to where I was.
Any ideas what's wrong? It shouldn't be this hard. It doesn't seem that a ROM install should be Recovery Dependent . But maybe it is?
==========
Solved. leapinlar, in the thread where I originally posted this question, said to use an older version of CWM to install. Apparently some incompatibility between versions of CWM (and TWRP) and the ROM zip.
Another solution was alluded to by King200 in another forum, but it sounded arcane and hard to do. It wasn't.
Here are Windows instructions:
++++++++++
Note: This method removes the "sanity check" built into the recovery image which checks to make sure the ROM you're installing is compatible with your tablet. Obviously, flashing the wrong ROM can/will brick your tablet.
So be warned.
Since I only have one tablet that I flash CM 10.2.1 on, no problem for me. If you have more than one tablet, perhaps you should delete your hacked zip after you install, to be safe.
Okay?
But for educational purposes, here's what I did to work around the problem.
++++++++++
You do this with 7-Zip. (So install 7-Zip if you don't have it already.)
Right click on the ROM that you're trying to install.
A 7-Zip context menu opens.
Select "Open Archive."
Drill your way down to
/META-INF/com/google/android/updater-script
Right click on the updater-script and select "Edit."
Open updater-script with Notepad.
Delete the first line of code, all the way up to the first semicolon. And delete the first semi-colon as well.
Save the edited file in Notepad. You'll get a 7-zip message asking if you want to incorporate your changes back into the archive. "Yes."
Now the ROM will install with later versions of CWM or TWRP.
Note: I had to do with this with the "fuzz" kernel too.
P.S. I don't know how to read code, so I don't understand exactly what the problem here is. I peeked at the scripts. I have an "ovation" tablet. Both the ROM and the Recovery image mention "ovation" in their updater scripts. Seems like they ought to talk to each other.
Please don't do this procedure. It is dangerous. It could brick your device. And the issue is not whether you have more than one tablet, it is if you accidentally download a hummingbird (HD) zip when you have an ovation (HD+) and try to flash it to an HD+. If you remove that assert statement the HD zip will merrily install to an HD+. And you will have a real mess.
A real case happened where a Nook Color user tried to flash a Nook Tablet ROM to his Color. The assert statement which was designed to prevent that did its job and prevented it. However, another user recommended he remove the assert statement, which he did, and thus flashed the Tablet ROM to his Color. His Color ended up bricked.
NEVER REMOVE AN ASSERT STATEMENT!
There are two more safe procedures.
One, use an older version of CWM to flash the older zips.
Two, do as the procedure says by opening the archive, but don't edit the updater-script file to remove the assert line. Look in a newer zip like CM11 and extract the file 'update-binary' and copy it to the old zip replacing the old update-binary file there. Then the old zip is flashable with the newer CWM/TWRP recoveries.
Sent from my BN NookHD+ using XDA Premium HD app
I download this roms
-Resurrection Remix V.5.4.4
And also download this.
V.5.7 Remix -Resurrection
Download the gapps and did the normal procedure for installation.
what happens is that after attempting to install the ROM. I get this error.
(Enclose all text that I no longer like spending a capture)
Installing: Storage - sd card1-Resurrecction Remix_Lp_v.5.4.4
finding update package
opening update
installing Update
Detected Fylesystem ext4 for /Dev/block/plataform/msm_sdcc.l/by-name/system
mount: Failed to mount /dev/block/plataform/msm_sdcc.l/by-name/system at / system: Invalid argument
unmouunt of / system failed: no such volume
patching system unconditionally
E: error in /storage/sdcard1/REsurrectionRemix_Lp_v5.4.4-20150511
(Status 0)
instalation aborted
This is me 2 rom mentioned.
after that the micro sd is disabled and must be reintroduced to recognize it the team
Try installing the ROM CM By beto, and is not installed not simply do nothing and pass the phone around two hours in the instalalcion and never proceeded
Now my phone does not pass the logo of motorola
help-'
Did you perform a „factory reset” wipe? Changing ROMs kind of requires you to - a factory reset wipes the old sd-ext, and you still have it.
And are you sure you downloaded the right ROM? I can't access the RR site now, but they don't have ROMs for Thea.
What phone do you have, actually?
FCorvin said:
Did you perform a „factory reset” wipe? Changing ROMs kind of requires you to - a factory reset wipes the old sd-ext, and you still have it.
And are you sure you downloaded the right ROM? I can't access the RR site now, but they don't have ROMs for Thea.
What phone do you have, actually?
Click to expand...
Click to collapse
I have xt1045 4g
I've done all the procedures to install the rom .
but gave those mistakes.
try putting on a rom 5.1 stock xt1045 according to what I found here on xda but I do not install it .
the phone did not stay at the logo and not as most do.
Then you need to flash this ROM: CM Peregrine
Or this one: RR Peregrine
See the ROM's discussion thread here.
You are also on the wrong part of this forum - you'll get better advice here: Moto G
UPDATED
Since these issues have been fixed in newer builds but as a s2 hd lte users, we have no option but to use older builds which have many issues. I found a workaround for them. If you are having wifi or other radio related issues, contact the ROM developer. This post can't help you. Flashing latest baseband helped me and could work well for you as well. Lets talk about two of the most common bug that haunts our device
1 Apps auto closing->( only for LMY48G builds,if you have newer builds,just flash gapps and reboot. to check go to about phone-> build number)
This is a webview related bug.
Download latest gapps from opengapps.org.
I prefer aroma installer as smaller packages don't have webview included,which will make the bugs worse.
Flash gapps. Dont forget to select 'android system webview' from the aroma installer.
Download the zip file from the
link
https://mega.nz/#!0d5Tiaja
Decryption key !JAG5Im-T75YN1CKIOiOcyDDaBH2ILD6dzwxw4xnhrBc
Extract "libwebviewchromium.so" and "libwebviewchromium_plat_support.so"
It is taken from stock samsung ROM and only works on armv7 devices.
Copy them to /system/libs using ESfile explorer or any other root explorer.
Overwrite the original file if asked.
give permission (-rw-r-r) to both file
Reboot to recovery
Flash this file "cm12.1 android system webview" from this thread(only for cm12.1, will cause bootloops in Xenon hd and resurrection remix)
http://forum.xda-developers.com/xperia-m/themes-apps/mod-google-android-webview-t3109216
Apps will now no longer auto close in your face without warning
((-> After testing for a month, I concluded that these steps are optional and use only if you want to have google android webview instead of cm12.1's built in 'android system webview'))
2) Now the most important part, random reboots.
This was reported on earlier builds of lollipop by many users.This is mostly caused by minfree that android uses to manage memory. If you navigate to sys/modules/lowmwemorykiller/parameters you can see 4 or 5 files. two of those files have wrong permissions. They are "adj" and "minfree".
If you give them (rw-r-r) permissions, you can adjust minfree values. the stock values are too aggressive and would cause constant reboots, freezes. Download romtoolbox, navigate to task manager, swipe left. you can choose to use any presets. i use 8,12,24,60,70,80 as minfree values.
Dont check "auto apply on boot" because you need to repeat this whole process after a reboot as those two files"adj and minfree" will be replaced from boot.img on boot by kern
Permanent fix: unpack boot.img. Navigate to ramdisc and open init.rc file in notepad. Find the line
chmod 0220 /sys/module/lowmemorykiller/parameters/minfree
chmod 0220 /sys/module/lowmemorykiller/parameters/adj
Change both values to 0644
save and close
Repack boot.img
Put it back inside the zipfile using winrar or use flashify from playstore to update boot.
I found tool to unpack qualcomm boot.img from this website. Full credits to the developer who made this tool.
http://www.droidbeep.com/how-to-unpa...-img-qualcomm/
download ROM toolbox and apply your preferred values
3. Low storage and optimizing apps(configuring ART compiler)
After google updated android runtime from JIT to ART, apps take up huge space and "optimizing app" takes forever. But there is workaround for that too.
1)Open build.prop in any text editor.
2) find these two lines:
dalvik.vm.image-dex2oat-filter=........(blah blah)
dalvik.vm.dex2oat-filter=...(blah blah)
3) Change both of these lines to
dalvik.vm.image-dex2oat-filter=speed
dalvik.vm.dex2oat-filter=Verify-none
If these lines doesn't exist, in your build.prop,you have to add them manually
4) save your build.prop file
5) reboot to recovery and wipe dalvik cache
After this check your storage space, You will have plenty of storage left and optimizing apps should be faster. It works just like old JIT compiler from older android versions.
if this doesn't work for you, you have to edit these same lines from default.prop by unpacking boot.img
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
diabolicalprophecy said:
I have fixed this issue by editing init.rc inside boot.img, but i dont know if i should post it here or not.
Click to expand...
Click to collapse
please, for e120s
OIAUser said:
please, for e120s
Click to expand...
Click to collapse
Please extract Boot.img from the zip file and send it. I don't have boot.img for e120s, or i can tell you how to do it yourself if you are interested.
Tell me how, I'll try to do it myself.
I will be very grateful
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
OIAUser said:
Tell me how, I'll try to do it myself.
I will be very grateful
Click to expand...
Click to collapse
I have updated the post on how to do it. You can find the required tool here with detailed instructions
http://www.droidbeep.com/how-to-unpack-and-repack-boot-img-qualcomm/
kdlinh said:
any way to fix wifi & soft reboot on e120s ???
if you need log or any thign about my devices i will link it to you!!
Click to expand...
Click to collapse
You can try wiping phone efs through odin in order to fix radio issues
1 Download stock jb rom
2 Check "phone efs clear". This is most important.
3 Click pda
4 click start
5 wait for phone to boot up
6 go to settings->software update to check if you are running latest jb build. Soft reboots and radio issues are usually caused by old baseband version.
7 Proceed with usual old way to install lollipop.
This way odin will wipe your efs settings to rebuild from scratch.
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
kdlinh said:
still ploblem ??? :? wait how to clear efs
at first time i have checked this box but failded ,
Click to expand...
Click to collapse
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
diabolicalprophecy said:
you need Stock jb rom to do this. I also had this issue in e120l, but clearing phone efs fixed radio issues for me. you need odin3v 1.85 and samsung usb drivers.
You can find it alongside " phone bootloader update". Be careful not to select this one by accident.
Click to expand...
Click to collapse
i have checked this efs box but failed :crying::crying:
kdlinh said:
i have checked this efs box but failed :crying::crying:
Click to expand...
Click to collapse
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
OIAUser said:
Once again, I read the instructions .. understand. But in the archive libraries are no libvebvievhromium .so file. "There's a file" libwebviewchromium_loader. "This is critical?
Click to expand...
Click to collapse
you get "libWebviechromium .so" file while installing gapps package. Go to opengapps.org and download aroma installer.
there are two files in the archive i uploaded, libwebviwechromium_loader.so and libwebviewplatsupport.so. You need to extract and replace those files in system-> libs after flashing gapps package. The built in webview will cause random apps shutdowns. this file is critical. You need libwebviewchromium_loader to start webview app. your system will not function properly without it.
diabolicalprophecy said:
which firmware did you tried this with? i have no problem doing this with astap 8 or stock jb rom for e120l.
http://i4khmers.blogspot.com/2015/09/official-firmware-samsung-galaxy-sii.html try this
its E120SKSJMH3 version
Click to expand...
Click to collapse
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
kdlinh said:
failed it still this error it seems like i stuck , have at least one error when i up rom to an open source cook rom
Click to expand...
Click to collapse
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
diabolicalprophecy said:
have you checked debugging option from developer options before doing this? Make sure your data cable is not faulty. please make sure you have a backup of efs partition if you are having network issues with all ROMs. try hellcat and stock based roms for testing to make sure you are not having this issue only on lollipop or kitkat. Also try to wipe boot from recovery menu before flashing.
Click to expand...
Click to collapse
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
kdlinh said:
i means that when i up the stock based roms none of error found but when i up rom to cm11 cm10 hellkat miui cm12 & ressuction
ERROR at least found one in this open source rom
Click to expand...
Click to collapse
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
diabolicalprophecy said:
I also had this the same issue.
There is a link to latest baseband in hellkat thread. Thats where i got it. Sadly Its only for E120L
Search the hellkat thread to see if there is one for e120s as well.
I obviously didn't look further as i don't own e120s.
Click to expand...
Click to collapse
can you give me the links , at least what i can do now is tried to install your baseband
it will brick your phone. Its for E120L only