CyanogenMod is officially dead... so, this project is also discontinued. The web links to ROMs may not be available anymore. Please do not expect any replays from me on this thread. Thanks for all the support. You may try LineageOS, the successor of CyanogenMod, as an alternative.
Here are some useful links
LineageOS
LineageOS kltekor
LineageOS XDA thread for all the klte variants
These are official CyanogenMod-13.0 (Android 6.0.x Marshmallow) builds originally developed for the international S5 (klte) with modified boot.img specially designed for Korean Galaxy S5 variants. Team CyanogenMod deserves all the credits for developing this wonderful ROM.
/* Warning */
Warranty of your device is now void.
I am not responsible for any damage to your device. Everything you are doing on your mobile is on your own risk. Please don’t point your finger at me in case you brick your device or lost SD card.
The boot.img file is specially designed for Korean Galaxy S5 SM-G900S/K/L (klteskt – kltektt - kltelgt). Do not try to flash this file on any other S5 variants (and also other devices).
The ROM alone (without the provided modified boot.img) only supports the international variant SM-G900F (klte).
/* Supported devices */
Samsung Galaxy S5 SM-G900S (klteskt): tested
Samsung Galaxy S5 SM-G900L (kltelgt): tested
Samsung Galaxy S5 SM-G900K (kltektt): tested (thanks to @Cm_RoX)
/* Requirements */
Samsung Galaxy S5 SM-G900S/K/L (klteskt – kltelgt -kltektt) device with more than 80% battery charged.
Windows PC/Laptop
ODIN software (for Rooting and flashing Custom Recovery)
A high quality USB cable
/* Downloads */
CyanogenMod 13.0 for klte
Google apps (GAPPS) for CyanogenMod 13.0 (open GAPPS / A-GAPPS).
cm-13.0 boot.img
Rooting
SM-G900S (klteskt)
SM-G900L (kltelgt)
SM-G900K (kltektt)
TWRP Recovery
/* Recommendations */
Back up your contacts, photos and any other data that you considered as valuable.
Probably you can make a Nandroid backup (if you wish to back up your present operating system along with all the data including apps).
/* Important */
You can use official ROM updates from CyanogenMod. However, it is necessary to re-flash the modified boot.img after each update to avoid boot failure.
The modified boot.img files will be updated and posted in this thread in a regular basis (please see second post).
/* Installation */
1. Root your device
2. Install TWRP recovery
3. Wipe data/factory reset
4. Flash ROM
5. Flash GAPPS
6. Flash cm-13.0 boot.img (important for Korean Galaxy S5)
7. Wipe Cache/Dalvik Cache
8. Reboot
/* Known Issues */
1. No important bug other than some issues related with ‘Media audio’ and ‘Phone call audio’. (Fixed in SM-G900S and L: not conformed in SM-G900K)
2. Please report if you find bugs
I appreciate the suggestions and fixes for bugs.
/* Screenshots */
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/* Acknowledgements */
CyanogenMod (for this wonderful ROM)
Team Win Recovery Project
Our Korean Galaxy S5 Facebook group member’s
Chainfire (for CF-Auto Root)
Ljzyal (for fingerprint lock)
Many other XDA developers
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based on: CyanogenMod
Boot-loader: Lollipop
Created: March 17, 2016
Updates
/* Updates */
----------------------------------- -----------------------------------
Boot.img version ------------------------------------ Date
----------------------------------- -----------------------------------
cm-13.0_boot.img for kltexxx -------------------- 2016-07-17
----------------------------------- -----------------------------------
marvelous its functionnaly my korean s5
After the update its important dont forgoten flash cm-13.0_boot_img_SM_G900S_K_L
Yes... It is important to flash that custom boot.img... Otherwise, it will not boot on Korean S5
sunilpaulmathew, where u find update boot.img?
syapk said:
sunilpaulmathew, where u find update boot.img?
Click to expand...
Click to collapse
It is a modified (by myself) boot.img of stock cm-13.0.
New version is just uploaded in the second post.
unlocked verizon s5, using t-mobile sim card.. need help rooting and updating
I cant post a new thread and am unsure where to post.. So just gonna try on here.
I have 2 unlocked verizon s5. using t-mobile sim cards.
model number- SM-G900V
android version- 5.0
Basbeand- G900VVRU2BOE1
tried getting cwm, no support.
can i just browse for a rom on cyanogen and flash using odin or?
apparentlly vzw is more like fort knox?..................
please dont be rude. just wishing to update hopefully to marshmaaaaaalllllow
ilovemyhoohaw said:
I cant post a new thread and am unsure where to post.. So just gonna try on here.
I have 2 unlocked verizon s5. using t-mobile sim cards.
model number- SM-G900V
android version- 5.0
Basbeand- G900VVRU2BOE1
tried getting cwm, no support.
can i just browse for a rom on cyanogen and flash using odin or?
apparentlly vzw is more like fort knox?..................
please dont be rude. just wishing to update hopefully to marshmaaaaaalllllow
Click to expand...
Click to collapse
Unfortunately, SM-G900V is not ab officially supported device of cm-13.0 (Marshmallow). Rooting guides are however available. If you are really like to try marshmallow, try this unofficial build (select the unified version). Since ur device is very similar to SM-G900F (klte), the recovery (like twrp) and custom ROMs for klte variant might work on ur device. But not guarantied. So, please do everything in your own risk. No one else will take the responsibility of any damage caused to ur device while doing these experiments. I recommend you to back-up every valuable data from mobile and download the stock ROM of your device (from sammobiles) before starting the experiments. Good luck.
sunilpaulmathew said:
It is a modified (by myself) boot.img of stock cm-13.0.
New version is just uploaded in the second post.
Click to expand...
Click to collapse
wwooww, Can you explain how to make this?
syapk said:
wwooww, Can you explain how to make this?
Click to expand...
Click to collapse
It is basically easy in Linux. Download mkbootimg from here. 1) Decompress the stock and cm-13 boot.img (check read me file for the commands). 2) Replace the device tree file of the cm boot.img with the file from stock boot.img. 3) repack and flash into device.
greats !!
thanks ^^
Root and erro for device sm-g900s
hello, xda and chainfire first congratulate you all for great works in molhoramentos developments and to structure our plataforna android! recently bought a galaxy galaxy sm-g900s of a friend who went to korea I am Brazilian and I have residence in Rio de Janeiro and see what by Brazilian forum è not given much value to ess magnifico device what in my opinion is better what Brazilian version sm-g900m and I perdir a big favor '' xda and chainfire family. '' which take a little but sevirços this magnificent galaxy s5 device sm-g900s thank you in advance! now let my problem recetemente did root in my sm-g900s with CF-Auto-Root first time it worked perfectly but after a day just vanished and saying that recently your device has been updated to 5.0 porfavor redo the root and asked also update '' su binary '' but how? I am currently with some financial difficulties and can not contribute donations will not lie I'm paying this amazing handset even with great difficulty! Only then ask for help and support in the galaxy s5 sm-g900s and remember and thank also those involved in progeto cynogenmod for sm-g900s I was very happy to know what is' rom cynogenmod '' want to install but wanted to know whether to take root both 5.0 and 6.0 lollipop good marshmellow now comes I have spoken
Boot loop
After carefully following this tut, i can't seem to get it to work on my G900S. Getting stuck at "Android is Starting: Starting apps". After waiting of a couple of minutes or longer, I did tried to reboot but stuck on boot loop.
I will try to do this again tomorrow and will post if successful.
-----edit-----
Do I need to root before anything else because i'm starting with stock 6.0.1 firmware. And as of now cf auto-root is not working in android 6.0.1
BlackMonoch said:
After carefully following this tut, i can't seem to get it to work on my G900S. Getting stuck at "Android is Starting: Starting apps". After waiting of a couple of minutes or longer, I did tried to reboot but stuck on boot loop.
I will try to do this again tomorrow and will post if successful.
-----edit-----
Do I need to root before anything else because i'm starting with stock 6.0.1 firmware. And as of now cf auto-root is not working in android 6.0.1
Click to expand...
Click to collapse
Can you please go back to stock Lollipop and then proceed the steps. It will be successful (I don't know the exact reason).
Regarding rooting: if you are able to flash twrp recovery (hope you can), no need to worry abt rooting.
sunilpaulmathew said:
Can you please go back to stock Lollipop and then proceed the steps. It will be successful (I don't know the exact reason).
Regarding rooting: if you are able to flash twrp recovery (hope you can), no need to worry abt rooting.
Click to expand...
Click to collapse
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160330-NIGHTLY
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
After couple of minutes waiting, still stuck at "Android is starting... Starting apps."
........edit.......
Yay! After taking sometime waiting, I rebooted my device and now starts normally.
Thanks for this tut, now I can finally enjoy CM13 on my phone.
Thanks OP.
Audio Jack Bug
3.5mm audio jack does not work.
BlackMonoch said:
3.5mm audio jack does not work.
Click to expand...
Click to collapse
That is a know bug... and sometimes you may face issues with caller volume. There is no permanent solution at this moment . You can temporarily solve these issues using SoundAbout although it is bit inconvenient. Suggestions are most welcome.
Hi, i'm sorry to bother you guys, i tried everything before replying,
i first downloaded the latest nightly (not sure if cm-13.0-20160401-NIGHTLY-klte.zip or cm-13.0-20160331-NIGHTLY-klte.zip
and Tried to clean install it coming from lollipop that i used for a year i think,
it got stuck at starting apps, after waiting a while i force restarted the device(power+volume down) and it restarted to where i can se the initial device setup UI but i can't click anything as it is getting Force close errors, restarted multiple times - still no luck.
^picture from google but same error message.
so i came back to this thread to see other users experiences and saw BlackMonach's reply and tried what he did,
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160331-NIGHTLY-klte.zip <<<< still this nightly...
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
again stuck at initial setup, so last time i tried the nightly from the night before
cm-13.0-20160330-NIGHTLY
the same one Monach used, and did a dirty install over the 0331 nightly
and it worked perfectly!!!
thank you guys for the thread, just wanted to let other know and not fall for the same mistake,
obosaleh said:
Hi, i'm sorry to bother you guys, i tried everything before replying,
i first downloaded the latest nightly (not sure if cm-13.0-20160401-NIGHTLY-klte.zip or cm-13.0-20160331-NIGHTLY-klte.zip
and Tried to clean install it coming from lollipop that i used for a year i think,
it got stuck at starting apps, after waiting a while i force restarted the device(power+volume down) and it restarted to where i can se the initial device setup UI but i can't click anything as it is getting Force close errors, restarted multiple times - still no luck.
^picture from google but same error message.
so i came back to this thread to see other users experiences and saw BlackMonach's reply and tried what he did,
Downgraded to Lollipop 5.0
Flashed CF-Auto-Root in Odin 3.10.7
Flashed Installed TWRP 3.0.0.0
Wiped data/factory reset in TWRP
Flashed cm-13.0-20160331-NIGHTLY-klte.zip <<<< still this nightly...
Flashed open_gapps-arm-6.0-stock-20160331
Flashed cm-13.0_boot_img_SM_G900S_K_L_20160328
wiped data/factory including cache and dalvik cache
Reboot
again stuck at initial setup, so last time i tried the nightly from the night before
cm-13.0-20160330-NIGHTLY
the same one Monach used, and did a dirty install over the 0331 nightly
and it worked perfectly!!!
thank you guys for the thread, just wanted to let other know and not fall for the same mistake,
Click to expand...
Click to collapse
I also face similar issues with the recent nighties... I tested nighties till 20160323 and found no issues. I'm not sure whether this issue exists in klte too. Anyway, thanks for testing and posting your tips.
i have same problem with new update 31-03 01-04 02-04
Related
CyanogenMod 12.0 is a free, community built distribution of Android 5.0 (LolliPop) which greatly extends the capabilities of your phone.
This is the official Nightly Build of CM12.0 for the AT&T HTC One XL.
To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
Update to latest 5.18 OTA firmware
Flash a custom recovery (TWRP/CWM with SELinux capabilities).
Download latest nightly from http://download.cyanogenmod.org/?device=evita.
Locate 5.0 Gapps via a quick Google search.
Wipe factory/data reset in recovery before installing CM12.0 (unless you are already on a CM12.0 build).
Reboot into recovery and install nightly and gapps.
List all Questions and Off-Topic discussions here
Huge thanks:
h8rift,intervigil, deck, mdmower, invisiblek, flyhalf205 - Great team to work with for the HTC MSM8960 device family.
XDA:DevDB Information
CM12.0 Official, ROM for the AT&T HTC One X
Contributors
jrior001
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: hboot 2.14 or higher
Version Information
Status: Nightly
Created 2015-01-07
Last Updated 2015-01-07
Fantastic! Nice to see some official support still going on for this device.
Have the limited space issues with ART been worked around at all? I've been wanting to use 5.0 but I have too many apps and run into problems storage-wise on ART which is the only option now on Lollipop. I know devs on many phones/tablets have switched to a unified partition layout to circumvent increasing OS and app sizes. Is that possible here?
Thanks for all your work!
Not working SMS and Dialer
It's fantastic news, all works properly and very smooth, BUT:
When I want to cancel call - Dialer app freezes at calling state with missed finish call button. And when i want to send SMS "send" button is inactive.
Latest nightly - cm-12-20150107-NIGHTLY-evita.zip, HBOOT 2.15, RADIO - 1.31a.32.45.16_2
ThisWasATriumph said:
Fantastic! Nice to see some official support still going on for this device.
Have the limited space issues with ART been worked around at all? I've been wanting to use 5.0 but I have too many apps and run into problems storage-wise on ART which is the only option now on Lollipop. I know devs on many phones/tablets have switched to a unified partition layout to circumvent increasing OS and app sizes. Is that possible here?
Thanks for all your work!
Click to expand...
Click to collapse
There's not much we can do because Evita never got the update to the /data/media/ sdcard layout like jewel/ville got.
However app2sd is native now and can move a goof portion of some(but not all) apps over to your internal sdcatd partition which should help some. Any app2sd app from market can show you what apps can move and its also available in the systems app manager pictured below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone stuck at Cyanogen logo
I tried to install CM12. I am coming from CM11. Can anyone tell me why my phone is stuck at boot logo. I am using the same recovery i used for CM11, unofficial TWRP 2.8.
sanimagus said:
I tried to install CM12. I am coming from CM11. Can anyone tell me why my phone is stuck at boot logo. I am using the same recovery i used for CM11, unofficial TWRP 2.8.
Click to expand...
Click to collapse
If this is your first foray into 5.0 lollipop land expect first boot to take 15-20 mins or so. Be patient. Also I'm grabbing the official build now just to confirm no wonk creeped in overnight.
jrior001 said:
If this is your first foray into 5.0 lollipop land expect first boot to take 15-20 mins or so. Be patient. Also I'm grabbing the official build now just to confirm no wonk creeped in overnight.
Click to expand...
Click to collapse
Thanks jrior001. I held the power button for a few seconds and it came out of the boot screen into system.
niihelium said:
It's fantastic news, all works properly and very smooth, BUT:
When I want to cancel call - Dialer app freezes at calling state with missed finish call button. And when i want to send SMS "send" button is inactive.
Latest nightly - cm-12-20150107-NIGHTLY-evita.zip, HBOOT 2.15, RADIO - 1.31a.32.45.16_2
Click to expand...
Click to collapse
Is anyone else having this problem with the 1/7 nightly?
droydr said:
Is anyone else having this problem with the 1/7 nightly?
Click to expand...
Click to collapse
In addition I have huge problems in CM 10, 11. Cellular network connection disappears every 5-7 minutes and if I try to place a call.
Can someone, who have stable system share his firmware, bootloader, radio, recovery etc. versions. I would be very thankful to you.
Is h8rift working on this instead of cm11 now? Will cm11 see a final build?
buradd said:
Is h8rift working on this instead of cm11 now? Will cm11 see a final build?
Click to expand...
Click to collapse
H8rift is still around working on other HTC devices but his Evita has long ago bit the dust so I've been handling the testing on evita. The rest of the HTC msm8960 team has kept this going along with ville/jewel/fireball and the m7 series.
As for cm11 they have moved to weekly builds and I believe 1 more "M" build is scheduled before all focus moves to cm12 exclusively.
niihelium said:
In addition I have huge problems in CM 10, 11. Cellular network connection disappears every 5-7 minutes and if I try to place a call.
Can someone, who have stable system share his firmware, bootloader, radio, recovery etc. versions. I would be very thankful to you.
Click to expand...
Click to collapse
What are your bootloader details ? Maybe running an RUU might help
Does someone see any Wifi problem?
My wifi icon gets stuck and cannot enable at all.
For the best consistent experience please follow the steps in OP. Use the last available RUU (3.18) to get to clean slate and follow the provided link to update to the firmware from the final OTA for Evita (5.18). This updated FW is what CM was built on so its best to be on the same base as everyone else.
jrior001 said:
For the best consistent experience please follow the steps in OP. Use the last available RUU (3.18) to get to clean slate and follow the provided link to update to the firmware from the final OTA for Evita (5.18). This updated FW is what CM was built on so its best to be on the same base as everyone else.
Click to expand...
Click to collapse
Maybe we can just use 5.18 RUU from this post(last under AT&T USA spoiler): http://forum.xda-developers.com/showpost.php?p=37227608&postcount=1
niihelium said:
Maybe we can just use 5.18 RUU from this post(last under AT&T USA spoiler): http://forum.xda-developers.com/showpost.php?p=37227608&postcount=1
Click to expand...
Click to collapse
That will work too, I wasn't aware that RUU existed. I'll update my OP with those links as well
htc one x evita
i was happy with this lollipo very well. current running version cm12 20150108. my battery was draining heavily... is there any solution for this.
jrior001 said:
That will work too, I wasn't aware that RUU existed. I'll update my OP with those links as well
Click to expand...
Click to collapse
Finally! Everything worked perfectly after updating 5.18 DOC. But faced with some difficulties. Decision under the spoiler.
I flashed 5.18 RUU and after this my phone run into loop [white HTC csreen] -> [standart recovery(with green arrow)] -> [restart].
So, my following actions:
0. Hold down 'Power' button for ~10 sec. This reboots phone, but after screen turned black press 'Power'+'Vol. Down' and it goes into bootloader.
1. Go into fastboot mode through bootloader and flash latest CWM recovery with PC:
Code:
fastboot flash recovery recovery.img
2. After this reboot into recovery, mount USB. Download latest nightly and GApps, put them on SD and flash with recovery.
3. Reboot. All works perfectly well.
After all I gues that my problem was older than 2.18 hboot version.
howgeet said:
Does someone see any Wifi problem?
My wifi icon gets stuck and cannot enable at all.
Click to expand...
Click to collapse
None at all here, I'm using this device on Wi-Fi only and it hasn't skipped a beat.
Sent from my Evita
jrior001 said:
For the best consistent experience please follow the steps in OP. Use the last available RUU (3.18) to get to clean slate and follow the provided link to update to the firmware from the final OTA for Evita (5.18). This updated FW is what CM was built on so its best to be on the same base as everyone else.
Click to expand...
Click to collapse
I can't update to RUU 3.18 or firmware 5.18 because I'm on a Windows 8.1 machine and adb/fastboot USB doesn't recognize my Evita from this machine.
If I just do a clean flash from TWRP without doing either of those "required" steps, will CM12 still run ok?
My bootloader details are below. Thanks for any help.
UNOFFICIAL CyanogenMod 12 for Galaxy S5 4G Plus
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This ROM is ONLY for SM-G901F, Galaxy S5 4G Plus [Snapdragon 805, Non QHD].
This Project is WIP Project.
If you can help me, please contact to me.
E-mail : [email protected]
This ROM supports ONLY new Lollipop bootloader.
Please update to samsung official lollipop firmware via odin.
CHANGELOG :
2015.05.18
- separate thread from cm12.1
2015.05.16
- apply intelli-plug hotplug driver.
- increase recording volume.
2015.04.18 -2
- fix IR sensor.
2015.04.18
- Rebased all sources to samsung official 5.0 release.
- fix buggy camera.
- fix buggy dialer, call.
- update NFC HAL.
- audio fx is working.
- audio driver update.
- fix buggy wifi connection.
- support LPM mode.
- support USB charge-only mode.
- remove not working ambient display option.
Not Working
.
CREDITS
@arter97
@skvalex
DONATIONS
Donate to @arter97 : http://forum.xda-developers.com/donatetome.php?u=4898097
Donate to @skvalex : https://callrecorder.skvalex.com/buy/howto.php
Donate to me : Paypal [email protected]
FUND-RAISER
Fund-raising was done.
- Donation use history -
All Donation : $500
Fund-raiser Commission : -$40
Device : -$460
Shipping : -$18
Surtax : -KRW 50,800 ($50)
Thanks.
DOWNLOAD
http://fsrv1.sayanogen.com/KCCAT6/
Please don't make mirror links.
OPENSOURCE
https://github.com/sktjdgns1189
XDA:DevDB Information
[ROM][G901F][5.0.2] UNOFFICIAL CyanogenMod 12 for Galaxy S5 4G Plus, ROM for the Samsung Galaxy S 5
Contributors
sktjdgns1189, arter97, skvalex
Source Code: https://github.com/sktjdgns1189
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Official Lollipop Firmware
Based On: CyanogenMod 12
Version Information
Status: Beta
Created 2015-03-12
Last Updated 2015-05-17
OMG I'll test it right now ! That's just awesome i waited for this day so long !
---------- Post added at 12:26 PM ---------- Previous post was at 12:17 PM ----------
EDIT: Should I choose the nightly version or not ?
Drakorcarnis0 said:
OMG I'll test it right now ! That's just awesome i waited for this day so long !
---------- Post added at 12:26 PM ---------- Previous post was at 12:17 PM ----------
EDIT: Should I choose the nightly version or not ?
Click to expand...
Click to collapse
Now, these files are same.
Thanks.
Error: "This package is for device: kccat6xx; this device is kccat6."
EDIT: The flash seems to work with odin !
EDIT 2: Bootloop
Did you had factory reset?
and which case in bootloop?
cyanogenmod bootanimation loop? or bootlogo loop?
Thanks.
sktjdgns1189 said:
Did you had factory reset?
and which case in bootloop?
cyanogenmod bootanimation loop? or bootlogo loop?
Thanks.
Click to expand...
Click to collapse
I did factory reset.
It's stuck on the blue robot face with a white transparent circle growing and disappearing. Tried to flash again with odin but same. And i've no access to recovery.
EDIT: I do have access to recovery if I restart the phone
Gonna try flashing it now.
Following advice in AndroidGX's other ROM thread, I'm gonna do a data, cache and dalvik wipe before flashing my carriers latest firmware which is ANK5 from the EE network in the UK.
After I've flashed that, I'll do another full data, cache and dalvik wipe before flashing this ROM in order to minimise any errors.
---------- Post added at 01:48 PM ---------- Previous post was at 01:38 PM ----------
ellessess said:
Gonna try flashing it now.
Following advice in AndroidGX's other ROM thread, I'm gonna do a data, cache and dalvik wipe before flashing my carriers latest firmware which is ANK5 from the EE network in the UK.
After I've flashed that, I'll do another full data, cache and dalvik wipe before flashing this ROM in order to minimise any errors.
Click to expand...
Click to collapse
Website is down, can't download. D:
[/COLOR]
Website is down, can't download. D:[/QUOTE]
Still works for me
Following advice in AndroidGX's other ROM thread, I'm gonna do a data, cache and dalvik wipe before flashing my carriers latest firmware which is ANK5 from the EE network in the UK.
After I've flashed that, I'll do another full data, cache and dalvik wipe before flashing this ROM in order to minimise any errors.
Click to expand...
Click to collapse
Applied this and I still have bootloop
Drakorcarnis0 said:
[/COLOR]
Website is down, can't download. D:
Click to expand...
Click to collapse
Still works for me
Applied this and I still have bootloop[/QUOTE]
Gonna give it a shot on my end anyway! Are you able to flash back to stock?
Are you able to flash back to stock?
Click to expand...
Click to collapse
I've to download the stock firmware from sammobile and it's so slow (1hour remaining! ). Do you know where i can download it fast freely ?
EDIT: I'm using Kies: download is a lot faster than with odin+sammobile
Drakorcarnis0 said:
I've to download the stock firmware from sammobile and it's so slow (1hour remaining! ). Do you know where i can download it fast freely ?
Click to expand...
Click to collapse
If you're okay using G901FXXU1ANK3_G901FEVR1ANK1_EVR then I can up it to Mega for you now if that is allowed within the rules? If not then I apologise.
EDIT: Can someone give me a list of stuff that needs testing if I do flash successfully?
EDIT: Android reached the Upgrading Apps X out of X stage...
ellessess said:
If you're okay using G901FXXU1ANK3_G901FEVR1ANK1_EVR then I can up it to Mega for you now if that is allowed within the rules? If not then I apologise.
EDIT: Can someone give me a list of stuff that needs testing if I do flash successfully?
EDIT: Android reached the Upgrading Apps X out of X stage...
Click to expand...
Click to collapse
Finally i use kies and it's fast.
So did I reach that stage but then bootloop.
Bootlooping for me. So close yet so far D:
ellessess said:
if you're okay using g901fxxu1ank3_g901fevr1ank1_evr then i can up it to mega for you now if that is allowed within the rules? If not then i apologise.
Edit: Can someone give me a list of stuff that needs testing if i do flash successfully?
Edit: Android reached the upgrading apps x out of x stage...
Click to expand...
Click to collapse
wifi
network
call quality
camera
hardware acceleration
ram
flash light
led notifications
app crashes
nfc
tethering
location, gps etc
It bootlooped. Looking at every other CM12 install video, they all use a .zip that is flashed from the phone itself.
Could Odin be causing these bootloops?
Flash to stock was successful, no damage done other than Knox 0x1 but I already had that anyway and I don't care about it.
PHONE WILL NOT BOOT PAST SAMSUNG LOGO AT ALL NOW D:
UPDATE: Phone initially bootlooped, battery pulled, reset data/cache in Recovery and now it booted stock.
Click to expand...
Click to collapse
1. Wiped Data/Cache in Recovery
2. Rebooted directly to Download Mode
3. Flashed G901FXXU1ANK3_G901FEVR1ANK1_EVR
4. Wiped Data/Cache in Recovery
5. Rebooted directly to Download Mode
6. Flashed CM12 Odin
7. Android is Upgrading Apps screen reached, bootloop after this.
8. Repeat steps 1 to 4
9. Phone boots back to stock firmware, bootloop without repeating step 4.
ellessess said:
1. Wiped Data/Cache in Recovery
2. Rebooted directly to Download Mode
3. Flashed G901FXXU1ANK3_G901FEVR1ANK1_EVR
4. Wiped Data/Cache in Recovery
5. Rebooted directly to Download Mode
6. Flashed CM12 Odin
7. Android is Upgrading Apps screen reached, bootloop after this.
8. Repeat steps 1 to 4
9. Phone boots back to stock firmware, bootloop without repeating step 4.
Click to expand...
Click to collapse
Hows your XNOX counter?
matthewgwilt said:
Hows your XNOX counter?
Click to expand...
Click to collapse
It was 0x1 before I flashed this ROM. I don't care at all about my Knox counter, my warranty covers my phone regardless of it's Knox state so I'm more than happy to flash this, that and anything else regardless of it's effect on my Knox counter if it means it would be produce results for getting CM12 on our phones.
I'm dying for the Stock Lollipop experience with this phone.
5.0.2 samsung stock for the 901f is now available in nordic countries. you can use that as a base no?
nemoverum said:
5.0.2 samsung stock for the 901f is now available in nordic countries. you can use that as a base no?
Click to expand...
Click to collapse
Samsung firmwares are based on their own android source code. Cyanogenmod is based on pure AOSP... So completely different. Although now Samsung has released the kernel source code for 5.0 g901f along with binaries it should be easier to build CM12 now.
Edit: actually they haven't released the source code just yet
matthewgwilt said:
Samsung firmwares are based on their own android source code. Cyanogenmod is based on pure AOSP... So completely different. Although now Samsung has released the kernel source code for 5.0 g901f along with binaries it should be easier to build CM12 now.
Edit: actually they haven't released the source code just yet
Click to expand...
Click to collapse
ahh, I didn't know they hadn't released source yet. that's kinda what I meant though.
still sounds like a step in the right direction. imagine a 5.02 build, bloat-free on that hardware. should fly.
Trader418's Unofficial CM-13.0
I tweet about updates: @trader418dev
Disclaimer
Code:
/*
* Your warranty is now void. Knox 0x1.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This rom is a fork of temaseks rom (found here). After temasek retired I have decided to update his source with cm-13.0's latest source.
This rom is fully open source.
Device Tree - HLTE - SPR - VZW - Common
Kernel
ROM Source
Changelog
If you appreciate my work you can donate to me on paypal
Downloads:
AndroidFileHost - HLTE - SPR - VZW
BasketBuild - HLTE - SPR - VZW
This rom includes OTA updates.
Credits can be found in the read-me of the main repo here
XDA:DevDB Information
[ROM]CM13[Android 6.0.1_R74] Trader418 unofficial cm-13.0 , ROM for the Samsung Galaxy Note 3
Contributors
trader418
Source Code: http://www.github.com/trader418
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2016-12-21
Last Updated 2016-12-22
#1
#2
This is great. Thank you very much for your amazing work.
Congratulations
Sent from my SM-N9005 using Tapatalk
Thank you supporting this device.
2016 Focus RS
2003 Cobra (Production #2)
Looks like I'm still having issues with Bluetooth phone calls in my car.
2016 Focus RS
2003 Cobra (Production #2)
Hey @trader418,
Just FYI, if you set the NTP_SERVER in gps.conf to 127.0.0.1, NTP is eliminated as a time source completely, and GPS becomes reliable world-wide. AGPS still functions normally with the system clock.
I don't know why Samsung/Google/Qualcomm decided to add NTP support to their GPS subsystem in the first place. It's utterly superfluous.
BY FAR the best incarnation of Cyanogenmod I've ever experienced. Not just for this phone but EVER. Battery drain seems to be fixed. Bless you trader418!!
Hi Trader,
i had the purify kernel installed on this rom due to battery being drained quickly but after updating to 12.3 i cannot reinstall the purify kernal as i get stuck on the loading screen. Can the 12.3 work with other kernals?
Help Please.
I have clean flashed this rom, using TWRP 3.0.2-0, Gapps Pico current, Supersu 2.79. My phone is SM-N9005. Anyway, everything goes according to plan including the bootup and setup. Unfortunately I cannot see any of my data once all is complete.
No Calendar. No Contacts.
Wifi is working and Mobile Data too.
I'm lost as to why and don't know what I can do from here.
Thanks in advance for any help and advice you can give me.
I am using the idle kernel with this newest update
stangdriverdoug said:
Looks like I'm still having issues with Bluetooth phone calls in my car.
2016 Focus RS
2003 Cobra (Production #2)
Click to expand...
Click to collapse
I was not convinced the new version would fix BT. I have come to the conclusion whatever is causing the incompatibility is unrecognized by the developers. That being said CM is the best damn ROM for our Note 3 overall so I will most likely be sticking with it!
I wonder though...any difference with the Purify 4.6 patch included on install?
flashed *cm-13.0-20161220 and lost root access, root access is not under developer option. How can I get root back?
Verizon Note 3
Brock25 said:
flashed *cm-13.0-20161220 and lost root access, root access is not under developer option. How can I get root back?
Verizon Note 3
Click to expand...
Click to collapse
To root you have to flash SuperSU. Had same problem on another build and that was solution trader418 gave me and it worked. Manage root access may be grayed out in developer option like mine but use an app to check root to verify.
Brock25 said:
flashed *cm-13.0-20161220 and lost root access, root access is not under developer option. How can I get root back?
Verizon Note 3
Click to expand...
Click to collapse
Flash SuperSU from here http://download.chainfire.eu/supersu-stable
Sent from my SM-N9005 using XDA Labs
I have downloaded it and flash it through recovery, still nothing. Is there something I need to do once the phone boots back up? I've been at this for hours
Brock25 said:
I have downloaded it and flash it through recovery, still nothing. Is there something I need to do once the phone boots back up? I've been at this for hours
Click to expand...
Click to collapse
You may have to install the SuperSU app from Play Store after flashing.
SuperSU, there is no su binary installed and supersu cannot install it. Ideas? This is my 1st time flashing ROMs so it is very possible I'm missing something
johnjctt1 said:
I have clean flashed this rom, using TWRP 3.0.2-0, Gapps Pico current, Supersu 2.79. My phone is SM-N9005. Anyway, everything goes according to plan including the bootup and setup. Unfortunately I cannot see any of my data once all is complete.
No Calendar. No Contacts.
Wifi is working and Mobile Data too.
I'm lost as to why and don't know what I can do from here.
Thanks in advance for any help and advice you can give me.
Click to expand...
Click to collapse
I'm using open gapps, I've also used Banks Dynamic Gapps on previous versions of this ROM with success. You might try one of those.
---------- Post added at 04:04 AM ---------- Previous post was at 03:59 AM ----------
johnjctt1 said:
I have clean flashed this rom, using TWRP 3.0.2-0, Gapps Pico current, Supersu 2.79. My phone is SM-N9005. Anyway, everything goes according to plan including the bootup and setup. Unfortunately I cannot see any of my data once all is complete.
No Calendar. No Contacts.
Wifi is working and Mobile Data too.
I'm lost as to why and don't know what I can do from here.
Thanks in advance for any help and advice you can give me.
Click to expand...
Click to collapse
Brock25 said:
SuperSU, there is no su binary installed and supersu cannot install it. Ideas? This is my 1st time flashing ROMs so it is very possible I'm missing something
Click to expand...
Click to collapse
The ROM does not include SuperSU. You need to download it and flash it in recovery. Download at http://download.chainfire.eu/supersu
NOTE: If you've tried to download this ROM before and Google Drive didn't let you access it, I have reuploaded the ROM directly to this post
First, the usual disclaimer:
Code:
/*
* Your probably long expired warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you
* and point my finger right back at you.
*/
About the ROM
This is a build of LineageOS 14.1 (Nougat) for the Samsung Galaxy SL (GT-I9003)
Things to take a note of
This ROM is still a Work In Progress. As such, some features do not work, as listed ahead
Make sure you keep a backup of your files. This update WILL wipe every partition (/system, /cache, /data, /sdcard).
IMPORTANT: Returning to an older ROM is non-trivial because this update applies a different partitioning scheme. To return to another version, flash the boot.img (possibly using heimdall or bml_over_mtd) of the ROM you wish to install, reboot to recovery, and flash.
ADB does not authenticate any requests. Hence, ensure you disable ADB if you're not a developer.
Steps to flash
Reboot to Recovery.
Wipe Data / Factory Reset.
Select the ROM zip from your SD Card and flash. It will reboot to TWRP.
Flash the ROM zip again. It WILL fail on this flash to let you go back to an older boot.img to stop installation if you wish to. Flash again to continue.
Flash GApps (OpenGApps pico package recommended).
Reboot. First boot can take 15mins or so.
NOTE: When upgrading from an older version of this ROM, it's recommended to wipe /system due to certain issues with the installer not updating the boot image correctly.
Downloads
ROM: lineage-14.1-20181008-UNOFFICIAL-galaxysl.zip Check the attachments on this post
Older version: lineage-14.1-20170826-UNOFFICIAL-galaxysl.zip
Things that work
WiFi
Bluetooth
Calling
SMS
Vibrator
Audio playback
LegacyCamera (no front camera)
Things that don't work
Adopted storage
Camera2
Mobile data
GPS
Video playback
Anything that is not explicitly listed as working
Tips and tricks
For forcing high end graphics (transparency in UI), add the following to build.prop
Code:
persist.sys.force_highendgfx=true
XDA:DevDB Information
LineageOS 7.1.2 for Samsung Galaxy SL i9003, ROM for the Samsung Galaxy SL i9003
Contributors
Technohacker1995, xc-racer99, Dheeraj CVR (@dhiru1602)
Source Code: https://github.com/Technohacker/android_device_samsung_galaxysl
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 14.1
Beta Release Date: 2017-08-26
Created 2017-08-26
Last Updated 2017-08-26
Known Issues:
Other than the above listed features not working, none as of now
Just curiosity- what is the sense in 7 android on so weak hardware?
dominatos1 said:
Just curiosity- what is the sense in 7 android on so weak hardware?
Click to expand...
Click to collapse
Just to show that it can be done, and a passion for reusing old hardware
Can someone pls enlighten me as soon as possible.....?? Is this ROM stable?? And it is written in the post that the status is given as Beta........ wt does that mean??.......Nd i did not understand......Why is it not possible to go back to an older ROM?? I need a detailed instructions (if pssble) how to get back to the previous ROM...... Currently iam using CM 11.......Can't I get back to my previous nandroid backup of this current ROM ?? pls answer this ASAP......Want to try how this ROM actually looks like on my GT-I9003......And i sincerely request someone to post the screens of this ROM pls..............
And would like to know wat is the difference btwn This Lineage ROM nd the Omni ROM....??
smsry said:
Can someone pls enlighten me as soon as possible.....?? Is this ROM stable?? And it is written in the post that the status is given as Beta........ wt does that mean??.......Nd i did not understand......Why is it not possible to go back to an older ROM?? I need a detailed instructions (if pssble) how to get back to the previous ROM...... Currently iam using CM 11.......Can't I get back to my previous nandroid backup of this current ROM ?? pls answer this ASAP......Want to try how this ROM actually looks like on my GT-I9003......And i sincerely request someone to post the screens of this ROM pls..............
And would like to know wat is the difference btwn This Lineage ROM nd the Omni ROM....??
Click to expand...
Click to collapse
You don't have to double post
This ROM is *somewhat* stable, however there are features missing (mobile data, GPS, video playback, etc.). Alpha and Beta are measures of how stable a version is (Alpha < Beta < Stable, in order of stability).
The reason you cannot go to a previous Android version is because I have repartitioned the phone's internal storage for a bigger /system partition and no internal /sdcard storage (it is now emulated storage). You can return to a previous ROM by flashing the stock ROM (to be more specific, the boot.img), rebooting to recovery and restoring your ROM backup.
I can post some screenshots soon, if needed
I started by porting Omni to our phone, to see if it was possible. Then I went for Lineage because it contains more features. So the Omni port is no longer active, It's recommended to use this LineageOS port.
Also, the Omni port uses the same partitioning format as older ROMs but at the disadvantage of having no system partition space for GApps and lesser fixes.
Cheers!
Thanks fr the reply!!!!
YES!!! i would love to see some screenshots.......
sorry but iam a noob at all this......I actually have another doubt too......
As u said that i should flash the stock rom..... here wt does a BOOT.IMG mean??
If u reply to this As soon as possible i would like to know wat all precautions should i take before flashing this rom.....
Bcoz this is the frst time iam seeing that u can't go back to the previous rom....
Usually i would take a nand. backup and test out a new rom nd then i wld go back to my previous backup......
Iam askin all these because the first time i flashed the Omni Rom a month before....... Nd i actually bricked my phone......
I got this "phone -exclamation-pc" icon everytime i try to get into BOOT mode or RECOVERY........
Then i recoverd safely after flashing the stock rom.......
Nd Instead of 7.1.2 for i9003 I would love to see 5.0 or 6.0 for this device......
Cant find any Lollipop or Marshmellow ROMS for the SL......
And i sincerely thank you for creating this NEW ROM for the SL.....
Have'nt seen any new ROMS lately after the CM11
(nd plssssss once think abt making a 5.0 ROM fr the SL.......What is ur opinion abt it......?? Iam sure it would look great on the SL.....)
Once again thank u for the reply.....
(ppl on xda surely are pretty friendly..... )
smsry said:
Thanks fr the reply!!!!
YES!!! i would love to see some screenshots.......
sorry but iam a noob at all this......I actually have another doubt too......
As u said that i should flash the stock rom..... here wt does a BOOT.IMG mean??
If u reply to this As soon as possible i would like to know wat all precautions should i take before flashing this rom.....
Bcoz this is the frst time iam seeing that u can't go back to the previous rom....
Usually i would take a nand. backup and test out a new rom nd then i wld go back to my previous backup......
Iam askin all these because the first time i flashed the Omni Rom a month before....... Nd i actually bricked my phone......
I got this "phone -exclamation-pc" icon everytime i try to get into BOOT mode or RECOVERY........
Then i recoverd safely after flashing the stock rom.......
Nd Instead of 7.1.2 for i9003 I would love to see 5.0 or 6.0 for this device......
Cant find any Lollipop or Marshmellow ROMS for the SL......
And i sincerely thank you for creating this NEW ROM for the SL.....
Have'nt seen any new ROMS lately after the CM11
(nd plssssss once think abt making a 5.0 ROM fr the SL.......What is ur opinion abt it......?? Iam sure it would look great on the SL.....)
Once again thank u for the reply.....
(ppl on xda surely are pretty friendly..... )
Click to expand...
Click to collapse
Will send screenshots soon
You can ignore that and just go ahead with flashing the stock ROM. The boot.img file is essentially the file that contains the boot code and recovery of the phone (in simplified terms)
The main precautions you should keep in mind are that the Internal SD card is now emulated, so wiping data will wipe any photos/music stored in internal storage. The safest place to keep your files are on an external SD card (keep your CM11 backup there, too)
The exclamation mark error is when the phone can't find the boot code, that might've been the ROM flash geting stopped partway. You can recover from that using Odin.
I actually did make a 5.0.2 NamelessROM build, but it's not very usable as such. Lollipop had an issue which used up phone RAM too much. Our phone having 512MB of RAM just made it worse. In between I was away on other tasks and so, by the time I returned, Nougat was latest. Hence, it didn't make sense (atleast to me ) to make a Marshmallow ROM when Nougat was the one in development.
You're welcome
As said above, a 5.0.2 build exists, which isn't very usable. A Marshmallow ROM doesn't exist for our phone but if one wishes to build CyanogenMod 13.0 for our device, I can give help
XDA and other internet forums are not all that friendly, just make sure you follow the rules of the forum
Cheers!
i need stable recovery for i9003
adm_83 said:
i need stable recovery for i9003
Click to expand...
Click to collapse
In the i9003 and other Samsung devices, the recovery is part of the boot partition. You can't switch recoveries independently of the current ROM (unless the main reason you want the recovery is just for the recovery or you patch the boot.img)
If you want to run a recovery, you have to get the boot.img file (taken from a ROM or otherwise) and flash it to the phone using heimdall/odin/flash_image. You'll have a recovery but it won't boot into Android.
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Does it update OTA?
No news on this rom?
Inviato dal mio MI PAD 2 utilizzando Tapatalk
Yea..... what happened??
Why r there no updates??
Nd i had a question.......What do u think abt the new Android Go concept by Google for Old nd Less RAM Phones??
Do u think we'll get it for our device??
Hi,
I have the same problem. Is there a solution ?
When , i choose "Toggle script asserts" on CWM , this error disappear and the installation continue.
But at the end, the phone has a loop reboot on TWRP . No way to boot on LineageOS.
MiDi0815 said:
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Click to expand...
Click to collapse
Thank you.
LineageOS 15.1 Oreo (Go edition)
dominatos1 said:
Just curiosity- what is the sense in 7 android on so weak hardware?
Click to expand...
Click to collapse
Technohacker1995 said:
Just to show that it can be done, and a passion for reusing old hardware
Click to expand...
Click to collapse
@Technohacker1995 , do you plan to support LineageOS 15.1 Oreo (Go edition) for our devices ?
I Think it will be a great idea to get this device to work with "LineageOS 15.1 Oreo (Go edition)".
The OS is built to deal with a device with low ram and with optimized apps for better performance and lower space
Yehia2amer said:
@Technohacker1995 , do you plan to support LineageOS 15.1 Oreo (Go edition) for our devices ?
I Think it will be a great idea to get this device to work with "LineageOS 15.1 Oreo (Go edition)".
The OS is built to deal with a device with low ram and with optimized apps for better performance and lower space
Click to expand...
Click to collapse
I'm thinking of doing that, actually (more for Project Treble, rather). I can't guarantee anything though
If I get enough time, I'll try porting it over
What remains to be fixed in the 7.1 port, however, is Mobile Data, GPS, H/W Video acceleration and other features listed in the main post. The same pains would be applicable here too.
Technohacker
(P.S. MAN, what happened to XDA? It never notified me for all these posts )
MiDi0815 said:
Trying to update from cm-11-20160705-UNOFFICIAL-galaxysl and gives me error: assert failed: run_program("/tmp/updater.sh") == 0
Tried from sd (sideload aborts at ~60% with error * failed to write data 'protocol fault (couldn't read status): Connection reset by peer' *)
Any suggestions?
CWM is 6.0.5.1
Click to expand...
Click to collapse
avbuuren said:
Hi,
I have the same problem. Is there a solution ?
When , i choose "Toggle script asserts" on CWM , this error disappear and the installation continue.
But at the end, the phone has a loop reboot on TWRP . No way to boot on LineageOS.
Thank you.
Click to expand...
Click to collapse
This ROM uses LVM partitions for a bigger /system partition. Hence it isn't compatible with previous partitioning schemes. I've actually added a part in the script to make sure it flashes and boots into TWRP first, because it acts as an intermediary for the actual install. You'll want to flash the ROM thrice: 1) Install LVM-partitioned TWRP (Reboots), 2) Act as a confirmation step (fails) 3) Actual install by wiping everything (should succeed) (there were supposed to be messages for each flash) .
As for a solution, if you're comfortable with Heimdall, flash the NORMALBOOT partition in download mode with the boot.img in the zip file. Then boot into recovery (TWRP) to continue for the two flashes.
Download mode is ALWAYS accessible, so don't worry, your phone isn't dead.
ryouza said:
No news on this rom?
Inviato dal mio MI PAD 2 utilizzando Tapatalk
Click to expand...
Click to collapse
I've been quite busy with other things, so I couldn't put much focus onto this.
smsry said:
Yea..... what happened??
Why r there no updates??
Nd i had a question.......What do u think abt the new Android Go concept by Google for Old nd Less RAM Phones??
Do u think we'll get it for our device??
Click to expand...
Click to collapse
It's a nice possibility, and if I'm able to get Project Trble support for the device, it'll get equal support for later releases as any other launch-Oreo device
Vershawn_Tan said:
Does it update OTA?
Click to expand...
Click to collapse
No, it doesn't, because it's an unofficial build.
Again, sorry for not responding earlier, XDA never notified me of these posts
K.....I know i may sound frustrating, but when can we expect the new update for this rom??
smsry said:
K.....I know i may sound frustrating, but when can we expect the new update for this rom??
Click to expand...
Click to collapse
I don't think it'd be any time soon, quite busy with other things, sorry :\
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your zeroltexx, or coming from another ROM:
** Make sure you're running a proper working Recovery (CWM or TWRP)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
voLTE
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- enesuzun2002
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
XDA:DevDB Information
crdroid zerolte, ROM for the Samsung Galaxy S6 Edge
Contributors
SimurgAnka, Enesuzun2002
Source Code: https://github.com/Exynos7420
ROM OS Version: Android 10
Version Information
Status: Stable
Created 2020-04-16
Last Updated 2020-04-16
Reserved 1
Reserved 2
No Sim
No sim detected on s6E G925i
zerofltexx:crying:?
does this rom get updated monthly just like other Android 10 roms?
i just flashed this rom. thanks.
Thanks for the work of my favorite CrDroid rom, I hope and you can fix the problem of the sim, it does not detect it and you cannot make calls or browse with data. I have a G925i
the camera does not focus
is it possible to use the rom even without the gapps?
Thanks
Any reason why this wouldn't work with the tmobile variant (and other american carriers)? Just curious.
Any issues on G925i?
areyouanand said:
Any issues on G925i?
Click to expand...
Click to collapse
Sim card keeps turning on and off.
flip cover support
Installed this ROM on my girls S6 Edge and it runs great so far. So thanks for your effort.
Is there any chance to get the official flip cover working again? Currently it doesn't lock/unlock the phone when closing/opening the cover.
Alphalife said:
Sim card keeps turning on and off.
Click to expand...
Click to collapse
Am running Samsung Galaxy s6 edge sm-g925t
But my SIM card is not detected
Great ROM!
I just installed the latest rom, everything is fine! (g925f)... even bluetooth works! which was the reason i tested this rom, because all the other rom's i tested crashed my bluetooth-carradio, this rom works perfekt! GPS, cam, wifi, mobile data, all working fine... :good: very great rom! thanks a lot to the developers!!!!!
Awesome Rom. Everything working perfectly. No issue at all.
I flashed magisk and installed Servicely., the battery backup is now excellent specially when the phone is idle.
Thanks for this awesome rom.
I had the same issue as the other guys. I received my first call on the phone and since then the signal keeps appearing and disappearing, and no reboot fixed it. It's a shame since everything else, from camera, mobile data, bt, ringtones, works, and works well. It's a great rom if it wasn't for that issue makes a great daily driver rom. I have a SM-G925I, and somehow the rom says it's a G925F.
Great rom on 925f
I tested the rom for a while (daily use).
Everything is working fine, no issues found with call's, bluetooth, cam, gps. battery life is very good.
The only thing is that i have to turn wifi off and on to make it work again sometimes..
Before flashing this rom (and of course any others) I reinstall the official samsung rom, then i install twrp, boot into twrp, do a factory reset, wipe everything, then mount a usb drive and install the rom from the usb drive... this prevents me from the most issues other people have with this and of course other custom roms....
again a great :good: THANK YOU :good: to the developer(s)!!!
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
redfox64 said:
.......I have a SM-G925I, and somehow the rom says it's a G925F.
Click to expand...
Click to collapse
...this often happens if you do a "dirty flash". a time ago i tried to flash my g925f with a custom rom, in twrp the flash ended with "...this rom is for a g925f, your device is a g920" even wipe and/or factory reset did'nt do it for me.
i reinstalled the original samung rom, then twrp, then factory reset and wipe everything. after that i was able to install the rom without error....
buddy_67 said:
I tested the rom for a while (daily use).
Everything is working fine, no issues found with call's, bluetooth, cam, gps. battery life is very good.
The only thing is that i have to turn wifi off and on to make it work again sometimes..
Before flashing this rom (and of course any others) I reinstall the official samsung rom, then i install twrp, boot into twrp, do a factory reset, wipe everything, then mount a usb drive and install the rom from the usb drive... this prevents me from the most issues other people have with this and of course other custom roms....
again a great :good: THANK YOU :good: to the developer(s)!!!
---------- Post added at 12:00 PM ---------- Previous post was at 11:52 AM ----------
...this often happens if you do a "dirty flash". a time ago i tried to flash my g925f with a custom rom, in twrp the flash ended with "...this rom is for a g925f, your device is a g920" even wipe and/or factory reset did'nt do it for me.
i reinstalled the original samung rom, then twrp, then factory reset and wipe everything. after that i was able to install the rom without error....
Click to expand...
Click to collapse
I dont know why but the issue with the signal solved itself. The only other bug I found was with screen casting. When it's connecting with wireless screen option enabled (without it, no tv is seen by the phone) the phone restarts itself.