Can't install CM11 on Dev VZ S5 - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

I'm rooted and unlocked running custom ROM TW 4.4.4 with Koontz kernel using TWRP and for the life of me I can't get CM11 installed.
I'm using the KLTEVZW version and the recommended GAPPS. I'm stumped. Any ideas?

A1Barrett said:
I'm rooted and unlocked running custom ROM TW 4.4.4 with Koontz kernel using TWRP and for the life of me I can't get CM11 installed.
I'm using the KLTEVZW version and the recommended GAPPS. I'm stumped. Any ideas?
Click to expand...
Click to collapse
i would be sure to follow the instructions.. is there a aosp kernel you should use or do you use the stock tw kernel?

I'm using Koontz TW Kernel currently. But the CM zip file should contain the new CM Kernel. ?

I am getting this message when it fails, 'this package is for device KLTEVZW, this device is KLTE'. So I guess I'm flashing the wrong zip. But my phone is an Verizon S5 developer model.....confused?

A1Barrett said:
I am getting this message when it fails, 'this package is for device KLTEVZW, this device is KLTE'. So I guess I'm flashing the wrong zip. But my phone is an Verizon S5 developer model.....confused?
Click to expand...
Click to collapse
which cm11 rom are you flashing? from verizon s5 original development section?

Yes, from Ablinoman887 and official cm 11, KLTEVZW. I did flash the KLTE version and it didn't fail but it bootlooped. However I did flash fusion 4.4.4 for KLTEVZW and its working great.

Try using the Version of TWRP from this thread: http://forum.xda-developers.com/showthread.php?t=2794674

Bkuschel u rock. It work. Thanks man

A1Barrett- How did you flash this? ODIN v3.09 doesnt seem to like it, it just errors out after awhile.

Neodawg- I flashed using the TWRP that bkuschel recommended 2 posts up.

A1Barrett said:
Neodawg- I flashed using the TWRP that bkuschel recommended 2 posts up.
Click to expand...
Click to collapse
Right, but how did you flash it? With ODIN? or use TWRP to flash it? The link only provides a .img file and if I tar it ODIN wont flash it, not sure if I am doing something wrong with tarring it or if the img isnt setup to be flashed by ODIN.
Thanks, for your help

Flash the new twrp using the old twrp. Use the zip. Twrp-kt.all-in-one.zip

A1Barrett said:
Flash the new twrp using the old twrp. Use the zip. Twrp-kt.all-in-one.zip
Click to expand...
Click to collapse
Thanks, that worked great, wasnt aware TWRP could even do that.

Yeah no worries.... Glad it worked out for ya

neodawg said:
Thanks, that worked great, wasnt aware TWRP could even do that.
Click to expand...
Click to collapse
lol twrp could always flash zips/recoveries on unlocked bootloaders

elliwigy said:
lol twrp could always flash zips/recoveries on unlocked bootloaders
Click to expand...
Click to collapse
Hmm, suppose so, never really thought about it, I came from a Motorola phone last time and not a Dev device either, so this whole ODIN, unlocked thing is new to me. Either way *facepalm*....hahaha

So it looks like this is only working for the dev version of the verizon GS5? Or at least that's what this page says (http://forum.xda-developers.com/showthread.php?t=2794674)
Guess i'm SOL?

Related

[Q] Help? Galaxy S4 i337 can't boot TWRPs or CWM

Hey!
I recently rooted my GS4 i337. Everything is all working as of now. However, I want to flash an AOSP ROM onto it. So, I followed instructions and at first, I flashed TWRP to my phone. It said it was successful, but when I go to recovery it puts me in ODIN. I then uninstalled TWRP and got the latest version that is said to support i337 GS4. Flashed successfully, but when I boot it still goes ODIN.
I tried both manually recovery booting with the buttons, and the UI on the actual app. Boots ODIN both ways.
Is there something I'm doing wrong? How can I boot into TWRP or CWM so I can make a quick ROM backup and flash an AOSP ROM?
Cheers! And if this is the wrong section, can a moderator please move it? I'm new to this forum.
Thanks. :laugh:
Check your firmware version then do a lot of reading.
jd1639 said:
Check your firmware version then do a lot of reading.
Click to expand...
Click to collapse
Explain please?
nhannon9 said:
Explain please?
Click to expand...
Click to collapse
Unless your on mdl firmware you can't flash twrp or cwm. I'm guessing you're not.
jd1639 said:
Unless your on mdl firmware you can't flash twrp or cwm. I'm guessing you're not.
Click to expand...
Click to collapse
Don't think so, my baseband is UCUEMK2 on 4.3. So, there's no way to get any custom ROMs on this? What can I do so I can?
nhannon9 said:
Don't think so, my baseband is UCUEMK2 on 4.3. So, there's no way to get any custom ROMs on this? What can I do so I can?
Click to expand...
Click to collapse
Google i337 safestrap mk2 xda
jd1639 said:
Google i337 safestrap mk2 xda
Click to expand...
Click to collapse
I found this a video on how to use Safestrap on 4.3.
It's for the Verizon variant but the SE Linux matches, can I give Safestrap a shot?
EDIT: Scratch that, I've found an ATT compatible version (3.71) and it booted into it perfectly! Now I can backup my stock ROM real quick and flash on my new one! Thanks!!

[Q] Flashing ROM failure

Hi,
Yesterday I went to flash CyanogenMod 11 on my Galaxy s4 (GT19505) and it wouldn't work. The first time, it started then went to a black screen. I turned my phone back on to find it wouldn't boot up at all (I waited over 10 minutes for it). I can access recovery mode, and when I did it again, it said md5 couldn't be found.
I used Odin to flash the most recent CT auto root and then moved over TWRP (with Odin) and I had no trouble with these.
I accidentally moved TWRP 2.5 over instead of 2.7. I was running 4.4 KitKat on my phone. Could it be 2.7 isn't compatible with CM 11?
Help!?
It should just work.
Flash the latest TWRP or Philz.
Perform a full wipe.
Flash Cyanogenmod.
What version are you trying to flash from Cyanogenmod? Use the nightlys and if one doesn't work try the version before that one.
ps you can skip the step nexttime about flashing cf-auto root. You don't have to do this. You can just flash the recovery you want.
3593483
Lennyz1988 said:
It should just work.
Flash the latest TWRP or Philz.
Perform a full wipe.
Flash Cyanogenmod.
What version are you trying to flash from Cyanogenmod? Use the nightlys and if one doesn't work try the version before that one.
ps you can skip the step nexttime about flashing cf-auto root. You don't have to do this. You can just flash the recovery you want.
Click to expand...
Click to collapse
I'm using a stable version. I haven't downloaded any latest ones. How would i do that if I can't access the phone? Boot it to download then go from there?
are you sure you (even) flashed a (compatible) kernel?
Sent from my GT-I9505 using XDA Premium 4 mobile app on OmegaRom v19
Is there any difference between 19500 and 19505? I'll try a new CM download...knowing my uncertainty I probably got an incompatible rom.
How stable are the nightlies?
Manganese said:
Is there any difference between 19500 and 19505? I'll try a new CM download...knowing my uncertainty I probably got an incompatible rom.
How stable are the nightlies?
Click to expand...
Click to collapse
You should only flash a rom for YOUR model phone, and for me the nightlies were stable enough to use.
dwarfer66 said:
You should only flash a rom for YOUR model phone, and for me the nightlies were stable enough to use.
Click to expand...
Click to collapse
So I redid TWRP, now what about CM 11? TWRP uses the jfltexx in its name...do I just use Odin to move CM?
So, I installed TWRP 2.7 and it worked. All is good, currently enjoying CM!!!
Now the battery is saying it's at 0%...how do I fix that?
Now my password isn't working for some reason. I did a restore with TWRP and now I can get into my phone. Fix?
Now my password isn't working for some reason. I did a restore with TWRP and now I can get into my phone. Fix?
Did you wipe before restoring?
Lennyz1988 said:
Did you wipe before restoring?
Click to expand...
Click to collapse
No. I just tried it and the same problem occurred. It's no biggie, I can reformat the settings myself. Thanks for the help.
dude, google it
Sent from my GT-I9505 using XDA Premium 4 mobile app

[newbie] galaxy s4 att UCUAMDL

hi all , sorry but my english is so bad
i just bought a galaxy s4 att secondhand , this had bassband UCUAMDL . and i checked the lastest version of it is 4.2.2
can i upgrade my phone up to 4.4 ?
and i dont know terminology about "MF3 - MK2 ............."
could you tell me ?
thanks so much :victory::victory::victory:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
HORiZUN said:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
Click to expand...
Click to collapse
thanks so much ,
can you get me links :crying:
but MF3 - MK2 ............. what is it ?
when i flash rom , what i have to notice ?
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
i am in 4.2.2
sonluyen94 said:
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
Click to expand...
Click to collapse
I have the same question. hopefully someone will be able to explain it to us.
MF3 would be the last three digits of your system software version
HORiZUN said:
MF3 would be the last three digits of your system software version
Click to expand...
Click to collapse
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
You don't have MF3, and that's a good thing. You can install a custom recovery. You need to root, install a custom recovery, and then you can start flashing roms.
sonluyen94 said:
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
Click to expand...
Click to collapse
nogods said:
I have the same question. hopefully someone will be able to explain it to us.
Click to expand...
Click to collapse
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
npjohnson said:
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
Click to expand...
Click to collapse
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
sonluyen94 said:
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
Click to expand...
Click to collapse
Most if not all. They're all built from either GPE or CM.
All good advice. Plus when you root and get Twrp recovery installed do a backup thru Twrp (Nandroid) and keep on phone and put a copy on pc. That way you have something to restore if you get in trouble. Also, your bootloader is not unlocked. No Att i337s are. Instead devs use an exploit called Loki-Doki to bypass Sammy's security checks to allow custom roms/kernels etc to flash. You can google Loki Doki and read up on it. If the rom or kernel is not loki'd you will have to flash the zip thru recovery to allow the rom or kernel to flash. You will come across this when flashing International roms and kernels. I don't have link any more so maybe someone else can link it. Keep it on SD card. Like noted read OP carefully and last 20 pages of rom thread. Builds newer than MDL are blocked by Att from using Loki and require SafeStrap. Which you don't need to worry about. Although you can read up on it. Good Luck. [emoji1]
Sent from my iPhone 6 Plus using Tapatalk
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
plasticglock said:
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
Click to expand...
Click to collapse
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
plasticglock said:
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
Click to expand...
Click to collapse
ROM manager didn't work. It said it installed cwm recovery but it didn't. I was able to install the latest TWRP with this ROM Installer and it worked like a charm! I then installed my custom TWRP from there, rebooted recovery, and installed Danvh's Google edition. I'm setting it up right now. I'm so happy to get my phone back. I just hope the odin flash fixed my problems.
To the OP try ROM installer to get your custom recovery going. Also if you like simple and fast AOSP check out Danvh's google edition rom, but stick to 4.4.4 for now. 5.0 is out but its buggy. Here's a link to the custom version of twrp that I use. https://www.dropbox.com/l/iDQQqlzNbyiFbQrMF4XcRc It's already loki'd so you can flash it if you have any problems with the latest build.

Cant Flash ROMs ??

I seem to be unable to successfully flash ROMs on my phone...
I am not sure what's going on.
Yes, I am rooted. Yes, I am flashing ROMs made for my phone, and flashing the appropriate firmware to match the ROM. Yes, I perform a clean flash by wiping everything first.
I have tried wiping cache/dalvik after flashing, still no luck. I have tried not flashing gapps, still nothing...
No matter what I do, it never boots. I sit at the Verizon screen for hours on end.
Any ideas?
G900V Verizon Samsung Galaxy S5
If it's any help, here is a list of ROMs I have tried...
Alliance
Jasmine
Eclipse
Optimal
MiUi
FreedomROM
sgirard1991 said:
If it's any help, here is a list of ROMs I have tried...
Alliance
Jasmine
Eclipse
Optimal
MiUi
FreedomROM
Click to expand...
Click to collapse
What build are you on? Do you have safestrap, flashfire?
Nk2. & I use safestrap
Sent from my SM-G900V using Tapatalk
sgirard1991 said:
Nk2. & I use safestrap
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Never heard of this. You might have flashed the wrong thing. We don't flash gapps with our Roms. Start over by using Odin to flash a full stock tar of NGC and root again.
I'll give it a try later. Thanks.
sgirard1991 said:
Nk2. & I use safestrap
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
If you're on NK2 then most of the Roms I read you flashed won't work on that build. After you flash a ROM built for OC4, like FreedomROM for example, you need to Odin over the OC4 firmware (which includes modem and kernel) to the device otherwise Roms won't start. Same thing goes for everyone other ROM with the firmware except it has to be for the respective build.
mrjiggywiggy said:
If you're on NK2 then most of the Roms I read you flashed won't work on that build. After you flash a ROM built for OC4, like FreedomROM for example, you need to Odin over the OC4 firmware (which includes modem and kernel) to the device otherwise Roms won't start. Same thing goes for everyone other ROM with the firmware except it has to be for the respective build.
Click to expand...
Click to collapse
Yeah, I've got that all figured out now. Never really had to do that with any other phones I've had, it was always just flash and go, never really messing with different firmware and whatnot. I have since tested 4 different ROMs and they have all flashed with success..
Thanks
Can a mod please mark this thread as answered/closed ? I got it all figured out. Thanks.

stock note 5 marshmallow port for s5?

With the recent files being dumped for note 5. Would it be possible to have it ported over to the s5 with some changes, without having to wait til the official release?
I do not think it's possible,as we do not have sources for 6.0 kernel on klte :| But still,hope someone can do some kind of workaround.
just to try the new marshmallow test cm 13 really to home
Wolf80 said:
I do not think it's possible,as we do not have sources for 6.0 kernel on klte :| But still,hope someone can do some kind of workaround.
Click to expand...
Click to collapse
Yeah that's what I was hoping.
superacc75 said:
just to try the new marshmallow test cm 13 really to home
Click to expand...
Click to collapse
I've tried it. It never boots on my g900t. No cm roms seem to work on my s5. Am I doing something wrong? Lol
It might be possible, as there are few unofficial CM13 (Android 6.0) builds already available for our Galaxy S5. Let's just wait and hope someone out there with kind heart and adequate time develop one for our phone.
Vineen said:
It might be possible, as there are few unofficial CM13 (Android 6.0) builds already available for our Galaxy S5. Let's just wait and hope someone out there with kind heart and adequate time develop one for our phone.
Click to expand...
Click to collapse
Yeah i cant get cm 13 to work. :/ or else i would use that.
daddymemoru said:
Yeah i cant get cm 13 to work. :/ or else i would use that.
Click to expand...
Click to collapse
The unofficial CM13 build by @albinoman887 can be actually used as a daily driver.
Vineen said:
The unofficial CM13 build by @albinoman887 can be actually used as a daily driver.
Click to expand...
Click to collapse
It always seems to get stuck in a bootloop for me. Help?
daddymemoru said:
It always seems to get stuck in a bootloop for me. Help?
Click to expand...
Click to collapse
Which varient you have? Which recovery? Which gapps? How are you downloading?
Zehlek said:
Which varient you have? Which recovery? Which gapps? How are you downloading?
Click to expand...
Click to collapse
I have the g900t (T-Mobile) using TWRP. Open gapps 6.0 (where you can choose your own). And I download off the XDA pages with my phone.
I should also note that only touchwiz Roms seem to work. Any cm ROM always gets stuck at bootloop, I can sometimes getting it to optimizing apps by switching kernel, but then it reboots over and over without starting.
daddymemoru said:
I have the g900t (T-Mobile) using TWRP. Open gapps 6.0 (where you can choose your own). And I download off the XDA pages with my phone.
I should also note that only touchwiz Roms seem to work. Any cm ROM always gets stuck at bootloop, I can sometimes getting it to optimizing apps by switching kernel, but then it reboots over and over without starting.
Click to expand...
Click to collapse
I use these gapps
https://www.androidfilehost.com/?fid=24269982086988288
What I do is
-Download ROM and gapps with chrome on my phone
-reboot into twrp
-wipe system, data, cache, dalvik
-flash ROM(klte unified)
-flash gapps
- boot
I have 900w8 variant but that shouldn't matter
Sent from my SM-G900W8 using Tapatalk
Zehlek said:
I use these gapps
https://www.androidfilehost.com/?fid=24269982086988288
What I do is
-Download ROM and gapps with chrome on my phone
-reboot into twrp
-wipe system, data, cache, dalvik
-flash ROM(klte unified)
-flash gapps
- boot
I have 900w8 variant but that shouldn't matter
Sent from my SM-G900W8 using Tapatalk
Click to expand...
Click to collapse
Yeah just get stuck in a bootloop.
daddymemoru said:
It always seems to get stuck in a bootloop for me. Help?
Click to expand...
Click to collapse
Make sure you've performed a full wipe before flashing it and if you're planning on using Google apps then make sure to flash them before booting into CM13 or else you'll get stuck with lots of FCs.
Vineen said:
Make sure you've performed a full wipe before flashing it and if you're planning on using Google apps then make sure to flash them before booting into CM13 or else you'll get stuck with lots of FCs.
Click to expand...
Click to collapse
Yeah I've tried that. CM Roms don't ever boot for me for some reason.
daddymemoru said:
Yeah I've tried that. CM Roms don't ever boot for me for some reason.
Click to expand...
Click to collapse
Have you tried downgrading to KitKat then repeating the process again?
Sent from my SM-G900F using XDA Forums
Vineen said:
Have you tried downgrading to KitKat then repeating the process again?
Sent from my SM-G900F using XDA Forums
Click to expand...
Click to collapse
I thought you couldn't do that with the latest 5.1.1 update. If you can I'd like some steps so I can try. because knowing me I'd get lost somewhere. >.<
daddymemoru said:
I thought you couldn't do that with the latest 5.1.1 update. If you can I'd like some steps so I can try. because knowing me I'd get lost somewhere. >.<
Click to expand...
Click to collapse
Is your bootloader unlocked? Because as far as I know, there are variants of the Galaxy S5 which have their bootloaders unlocked, making them impossible to downgrade or else making their device bootloop.
As for the steps, you only have to download the KitKat firmware (I recommend ANE2 - easiest to root) from sammobile.com then flash it via Odin.
Make sure you have Samsung Mobile Drivers installed if you are working on a Windows environment. Afterwards, root your Galaxy S5 by downloading towelroot from towelroot.com.
Once done, download SuperSU on Play Store. Flash custom recovery using Rashr. Make sure Reactivation Lock is disabled before flashing anything custom or else it will cause problems.
When you have custom recovery successfully installed, try flashing CyanogenMod again.
Sent from my SM-G900F using XDA Forums
Vineen said:
Is your bootloader unlocked? Because as far as I know, there are variants of the Galaxy S5 which have their bootloaders unlocked, making them impossible to downgrade or else making their device bootloop.
As for the steps, you only have to download the KitKat firmware (I recommend ANE2 - easiest to root) from sammobile.com then flash it via Odin.
Make sure you have Samsung Mobile Drivers installed if you are working on a Windows environment. Afterwards, root your Galaxy S5 by downloading towelroot from towelroot.com.
Once done, download SuperSU on Play Store. Flash custom recovery using Rashr. Make sure Reactivation Lock is disabled before flashing anything custom or else it will cause problems.
When you have custom recovery successfully installed, try flashing CyanogenMod again.
Sent from my SM-G900F using XDA Forums
Click to expand...
Click to collapse
OK I'll try that. I have T-Mobile g900t. I'm pretty sure its unlocked. Lol I'd be the happiest person ever if it works. I used to have blisspop, but now the ROM doesn't work.
daddymemoru said:
OK I'll try that. I have T-Mobile g900t. I'm pretty sure its unlocked. Lol I'd be the happiest person ever if it works. I used to have blisspop, but now the ROM doesn't work.
Click to expand...
Click to collapse
Report back if everything goes fine. TouchWiz Lollipop caused me a lot of problems in modding mainly because it's harder to mod it unlike KitKat which is pretty straight forward.
By reverting to KitKat, I was able to use XtreStoLite which stopped working on me for some time. Now I'm on Android Marshmallow 6.0.1 (CyanogenMod 13 unofficial by @albinoman887) and I'm satisfied than ever.
Sent from my SM-G900F using XDA Forums

Categories

Resources