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
Related
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
bubblebuddyi said:
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
rcklss1 said:
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
bubblebuddyi said:
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
Click to expand...
Click to collapse
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Baldilocks said:
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Click to expand...
Click to collapse
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
bubblebuddyi said:
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
Click to expand...
Click to collapse
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Baldilocks said:
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Click to expand...
Click to collapse
can you link to a stock kernel for the AT&T i337?
xxhorseriderxxx said:
can you link to a stock kernel for the AT&T i337?
Click to expand...
Click to collapse
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
highaltitude said:
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
Click to expand...
Click to collapse
okay, assuming you're using the AT&T variant, I did this:
I got the looping "installing camera firmware" and tried faux an ktoonsez with no luck
I flashed this tmobile stock kernel and the camera firmware updated successfully by going into the camera app.
I then just flashed faux kernel back and everything worked great.
http://forum.xda-developers.com/showthread.php?t=2271976
I use shabbypenguin's auto loki CWM recovery, but you'll have to definitely flash the loki patch after the tmo kernel to make this work.
http://forum.xda-developers.com/showthread.php?t=2291956
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
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?
Ever since I got the KitKat 4.4.4 update my battery has been draining, and I'm not going to get a new battery because I've only had this phone for a short time[emoji27]
Give it a few days, it should improve. If not, you may want to root and install the Greenify app from the Play Store.
StoneyJSG said:
Give it a few days, it should improve. If not, you may want to root and installed the Greenify app from the Play Store.
Click to expand...
Click to collapse
I'll try it, and I'm also going to get cm 12 on it since it's taking Samsung a long time to update it
itzdajosh said:
I'll try it, and I'm also going to get cm 12 on it since it's taking Samsung a long time to update it
Click to expand...
Click to collapse
If you have the at&t sgh-i337 and it's on Android 4.4.4, then you won't be able to install cm 12 due to the locked bootloader. You're only able to boot TW based roms from Safe Strap.
No your right and wrong because twrp recovery already has Loki built into it..
itzdajosh said:
No your right and wrong because twrp recovery already has Loki built into it..
Click to expand...
Click to collapse
no, he's right. no twrp for you
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
no, he's right. no twrp for you
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Go to twrps website and click recovery for jflteatt and look at device specific issues and it clearly states that "our images are already modified with Loki"
itzdajosh said:
Go to twrps website and click recovery for jflteatt and look at device specific issues and it clearly states that "our images are already modified with Loki"
Click to expand...
Click to collapse
If you have mdl firmware, yes. But you don't. Safestrap is the only recovery that's going to work and no, cm. Trust me
Sent from my Nexus 5 using XDA Free mobile app
itzdajosh said:
No your right and wrong because twrp recovery already has Loki built into it..
Click to expand...
Click to collapse
itzdajosh said:
Go to twrps website and click recovery for jflteatt and look at device specific issues and it clearly states that "our images are already modified with Loki"
Click to expand...
Click to collapse
LOKI will only work on the MDL firmware running Android 4.2.2 Jelly Bean. You're on 4.4.4 so LOKI won't work. Go ahead and try, it will fail.
Oh well I'll just be stuck like this but I'll try to find a way how to make it work
itzdajosh said:
Oh well I'll just be stuck like this but I'll try to find a way how to make it work
Click to expand...
Click to collapse
Good luck and remember Odin, you'll need it.
Sent from my Nexus 5 using XDA Free mobile app
So your saying that Odin will be able to flash cm12 without Loki? And dose Loki work on 4.4.4??
itzdajosh said:
So your saying that Odin will be able to flash cm12 without Loki? And dose Loki work on 4.4.4??
Click to expand...
Click to collapse
no, I'm saying trying to flash twrp and/or cm and you'll probably need Odin
Sent from my Nexus 5 using XDA Free mobile app
Why?? If wwjoshdew made a video on how to root and install a custom recovery on all Qualcomm variants for example jflteatt he didn't say anything about KitKat wouldn't work with Loki...
itzdajosh said:
Why?? If wwjoshdew made a video on how to root and install a custom recovery on all Qualcomm variants for example jflteatt he didn't say anything about KitKat wouldn't work with Loki...
Click to expand...
Click to collapse
Trust us dude, LOKI won't work on Android 4.4.4 on the sgh-i337. It was a bootloader bypass that was patched when the mk2 firmware OTA update came out. If you try flashing a custom recovery you risk bricking your phone since the bootloader is locked. The only recovery you can use is Safe Strap.
If you want CyanogenMOD or any other roms of the alike such as AOSP based roms, you will need a at&t Galaxy S3 or an international S4 or if I remember right a sprint or t-mobile S4, (don't quote me on though) they have unlocked bootloaders as far as I know.
StoneyJSG said:
Trust us dude, LOKI won't work on Android 4.4.4 on the sgh-i337. It was a bootloader bypass that was patched when the mk2 firmware OTA update came out. If you try flashing a custom recovery you risk bricking your phone since the bootloader is locked. The only recovery you can use is Safe Strap.
If you want CyanogenMOD or any other roms of the alike such as AOSP based roms, you will need a Galaxy S3. It has an unlocked bootloader.
Click to expand...
Click to collapse
Well alright I did a bit of research myself and you guys are right.. Thanks for the help so I wouldn't brick my galaxy s4![emoji2] I think I'm going to get the lg g2 for custom roms and stuff...
Sent from my SAMSUNG-SGH-I337 using Tapatalk
No problemo, glad to help when I can. Thanks for the PM by the way lol.
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.