I'm new to the whole rooting and flashing scene. However, I'm good at following instructions, generally pretty good at figuring out how to overcome unexpected problems, and a pretty quick study. I've got the hang of rooting my phone down pat, and I can flash stock ROMs with no trouble. Unfortunately though, I have yet to successfully flash a custom ROM on my Sprint Galaxy S 5 (SM-G900P). First, I thought I'd try for CyanogenMod, but the CM installer says that my device is not supported, and refuses to work for me. I know it can be done without the installer, but I have yet to locate the instructions someplace to do it manually.
After giving up on CM for now, I found Alliance ROM for KitKat 4.4.4, which REALLY intrigues me with its high flexibility. What's more, it's KitKat, which I much prefer over Lolipop. Ever since I switched to Lolipop, my apps have all started crashing frequently, even after being updated, and even TouchWiz itself has started crashing frequently. I also don't like the new drop-down menu or the new Recent Apps display. So, I flashed KitKat 4.4.4 kernal and then tried to flash Alliance ROM, but I just got stuck in a boot loop. I booted back to recovery, flashed the stock 4.4.4 image again, and tried to figure out what to do to get Alliance working. I went through the entire Alliance ROM thread here on xda, and found THIS POST describing a method to get Alliance ROM working on a 4.4.4 kernal without having to flash back to 4.4.2. After following those directions, though, I still wound up in a boot loop. Now, when I did that, I wasn't able to use the de-odexed version, and had to use the odexed one instead. After waiting 2 hours to download both versions, I couldn't get the de-odexed one to flash at all. It gave me an error message about no md5 found, or something like that. Unzipping the zip file would have given me a bunch of disconnected folders, so I just tried to flash it from the zip, but it didn't work. The odexed version, however, had an md5 inside the zip, so I just unzipped and flashed the odexed md5. Still got boot loop, though, after I tried to install Alliance ROM afterward.
So, with all that being said, here's what I'm looking for.
Either:
1.) A reliable way to install Alliance ROM on my Sprint Galaxy S5 (SM-G900P)
2.) A different custom ROM that might be better suited to my needs. This is what I'm looking for:
a.) Rooted
b.) debloated
c.) wifi tether and USB tether
d.) KitKat Drop Down and Recent Apps menus
e.) Some badass-looking themes. I really like the look of the Black Glass themes from Alliance, so either THAT or something that looks equally badass
f.) I would like to be able to overclock
g.) want to see CPU usage
h.) battery percent
i.) want to be able to turn off camera shutter sound. (Maybe this can be handled by just installing a different camera app, idk)
j.) Working private mode
k.) fingerprint scanner functionality would be NICE, but not a must. I really only use it for Private mode.
I'm sure there are probably other things that I'd like to see, but those are the ones I can think of right now. So if anyone can tell me how to get Alliance ROM working, or has a suggestion of another custom ROM that would include those features, and that will work with my Sprint Galaxy S5 (SM-G900P), and where I can find it, I'm all ears.
Thanks!
So, from what I have read here, and I skimmed most of it, is a bootloader issue. You not only need version specific kernel but bootloader as well. You're issue might be that you have a kit-kat bootloader trying to flash lollipop or vice versa. Your best bet is to Odin the Official stock tar of which ever version of custom rom you want to flash, i.e 4.4.2, 4.4.4, 5.0. Then you can reroot and flash the coinciding custom rom. Does that make sense?
metalfan78 said:
So, from what I have read here, and I skimmed most of it, is a bootloader issue. You not only need version specific kernel but bootloader as well. You're issue might be that you have a kit-kat bootloader trying to flash lollipop or vice versa. Your best bet is to Odin the Official stock tar of which ever version of custom rom you want to flash, i.e 4.4.2, 4.4.4, 5.0. Then you can reroot and flash the coinciding custom rom. Does that make sense?
Click to expand...
Click to collapse
Yeah, that makes sense. Where do I find the Official stock tar? Also, if I flash back to 4.4.2, then reroot and flash Alliance for 4.4.2, can I upgrade from there to 4.4.4 without having to flash again? Or do I have to flash stock 4.4.4 followed by flashing Alliance for 4.4.4?
4.4.2 and 4.4.4 are both kit-kat, so you can flash either one. Look in Sprint Galaxy s5 Android development for the tar files
---------- Post added at 11:07 AM ---------- Previous post was at 11:06 AM ----------
http://forum.xda-developers.com/showthread.php?t=2958614
Firmware-Only_Odin_Flashable_ Images_For_4.4.. And_5.0_Roms_Updated_2_7_15
---------- Post added at 11:08 AM ---------- Previous post was at 11:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=2787760
[LINK][ROM][ODIN][TAR]SM-G900P NE5 (NE5 Modem/Kernel/ROM - Stock)
4.4.2
missionary7 said:
Yeah, that makes sense. Where do I find the Official stock tar? Also, if I flash back to 4.4.2, then reroot and flash Alliance for 4.4.2, can I upgrade from there to 4.4.4 without having to flash again? Or do I have to flash stock 4.4.4 followed by flashing Alliance for 4.4.4?
Click to expand...
Click to collapse
Go with 4.4.2, 4.4.4 had such small improvements, you wouldnt even notice. I recommend M.O.A.R. ROM it is the mother of all ROMS. Paired up with ktoons kernal, its amazing!!!
Related
I had some trouble rooting after I first did a 4.4.2 OTA. So I downgraded to 4.3 and got root and installed TWRP without any trouble.
So from a 4.3 firmware I went to Cyanogenmod (Android 4.4.2). Is that ok ? Or do I need to upgrade radio, boot or other parts that dont come with a custom rom? In other words: is a (rooted) 4.4.2 firmware a precondition for installing alternative 4.4.2 roms?
Well, everything might not work perfectly as many things (though little) changed from 4.3 to 4.4. Yup, most of those things (radio,etc) change, flashing a cm11 rom wont change those and cm will most likely need them. Better to upgrade to 4.4. Also, does ART (new kitkat runtime) need anything new from kernel or anything? I don't see anyone who seems to have tried this and might mostly not work.
Also, What root trouble did you have? Easier to solve that issue than deal with any new issues that might arise from this.
hemanthmahesh said:
Well, everything might not work perfectly as many things (though little) changed from 4.3 to 4.4. Yup, most of those things (radio,etc) change, flashing a cm11 rom wont change those and cm will most likely need them. Better to upgrade to 4.4. Also, does ART (new kitkat runtime) need anything new from kernel or anything? I don't see anyone who seems to have tried this and might mostly not work.
Also, What root trouble did you have? Easier to solve that issue than deal with any new issues that might arise from this.
Click to expand...
Click to collapse
Thanks. I will look into that. The kernel is included in a ROM though wright? So that wont be an issue I guess... But just to be save I'll flash 4.4.2 firmware and start from there. My problem was I actually got root, but flashed custom roms always got stuck in the boot animation. The thread on that is here.
Hello Everyone,
New member, longtime lurker here. I have a I535 Verizon GS3, and am rooted. It has been quite a while since I did that, and I just wanted to make sure I knew what I was getting into before I tried to upgrade to a newer rom. The reason I want to upgrade is I currently have a Sony Smartwatch 2, that I love but I shattered the screen. In preparation to buy one of the new Android wearables, I need to be on a newer version of android as far as I can see.
Right now I am on: 4.1.2/ Baseband version, I535VRBMB1/ Kernel Version 3.031-86103/Build number JZO54K.I535VRBMB1
I am not sure what of that info is important so I posted it all. I don't remember the exact name of the rom I flashed before, but I think it was created by member Dalep, and it was something like "Stock Rooted". It was basically just a rooted version of the stock rom. My only reason for rooting was to use a wifi tethering app which has been working well for me. I was nervous with the initial rooting and flash process, so once I got what I needed I stopped working on it and used my phone as is until now. Now I would like some guidance on how to get my phone safely up to date.
1. I am running Clockwork Mod Recovery v6.0.2.3. Is this still usable or do I need to update it?
2. What rom would you all recommend for someone who wants a fairly stable phone and does not care so much about tinkering/customizing?
3. What does a nandroid backup do and what can I do with the backup (I did one before I installed this current rom)
4. What is the best way to get my phone back with the apps I have installed? (i.e. reinstall from Playstore, etc) I don't have many apps.
I am sure there will be more questions, but thank you for reading my long first post, I just want to make sure I am clear about my current state, skill level and intentions.
Thanks,
Victor
Update recovery to latest version of whichever recovery you prefer. I use TWRP. Flash the MF1 firmware and ML1 modem in that order. This will bring you as far up to date as possible without locking down the phone. Then you can flash any rom currently available. I run stock deodexed ML1 4.3 base and then mod it the way I want it. Scott has one in the rom threads. As far as nandroid it will make an image of your current setup in case you need to return due to problems or trying some other rom. There are several options for backing up apps such as TIBU, My Backup or even Google can restore your apps. Here is firmware and modem. Flash MF1 first and ML1 second. ML1 will replace the MF1 modem but leave rest of firmware (bootchain) at MF1 level and will retain root and unlock status.
Flash in recovery in order posted:
#1- MF1 Firmware -- http://www.androidfilehost.com/?fid=23329332407591785
#2- ML1 Modem -- http://www.androidfilehost.com/?fid=23329332407591786
Thanks for the response, I will flash those and check out that rom
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
j006 said:
Sup guys,
I've rooted every phone I've had, but I do it so infrequently that I always have to refresh my memory with it. Current situation is that I have a rooted M8 running mostly stock 4.4.4 ROM, but with a bunch of Xposed mods and a few system tweaks - it's dialed in just the way I want it, but the screen is separating so I've got my hands on another M8 running 4.4.2. I basically want to get the 4.4.2 M8 to the state of my 4.4.4 device. I've already made a complete backup ROM from the 4.4.4 phone and I want to restore that ROM to the 4.4.2 device. With the 4.4.2 device, I plan to:
S-Off (Try Firewater. May or may not work. If doesn't work, try Sunshine)
Install recovery - CWM or TWRP
Flash Super SU
Update firmware from 4.4.2 to 4.4.4 from here: http://forum.xda-developers.com/showpost.php?p=52017763&postcount=2
Flash my complete backup ROM from my current device
Sanity check? Am I missing anything here? When I rooted my current M8 (4.4.2), weaksauce actually worked, and I flashed CWM recovery and Super SU by placing them on the SD card. That is what I plan to do again since that was so easy. Recommendations?
Cheers guys!
Click to expand...
Click to collapse
firewater sever is taken down, even if you have an old version of it laying around it is useless.. you must pay for sunshine.
but other than that everything looks good.
you have your nandroid backup, on the new m8, s-off using sunshine, then update the firmware from 442 to 444, then flash custom recovery (TWRP is recommended), and then wipe and restore the nandroid and you should be good to go. :good:
(no need to flash supersu as the ROM you have backed up using nandroid is already rooted)
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
j006 said:
Many thanks! A couple of years ago when I did this I remember it being fairly straightforward. Do you personally find any real benefit in upgrading to one of the Lollipop ROMs this go 'round? Seems like it's more trouble than what you gain, though I may be uninformed of course..
Cheers!
Click to expand...
Click to collapse
I find many benefits to LP over KK personally.
If you like a stock ROM we have stock based LP ROMs, and firmware.zip you can flash and you are up an running a stock LP ROM within 10 minutes. Sure you need to set things up, but most can be backed up and if you take some screen shots of everything it's pretty easy to get everything set up to your liking.
If you want some customization there are ROMs like mine, that come mostly stock with some benefits like root, busybox, etc, and then offer you a MOD Pack.
See ROM thread here
If you want to customize pretty much every aspect of the ROM you have Venom at your fingertips.
Venom ROM thread
There is the benefit of having all the security updates with the newest firmware.
We also have Marshmallow 6.0 ROMs out already that are rock solid.
A Google Play Edition ROM found here
And a Sense based ROM found here
You can also run some Sense 7 ROMs that are very stable, you can find one in my linked thread posted above, and in the Development area.
I personally would try things out, that's the great benefit of root/s-off/custom recovery/ROMs
You can always make a nandroid backup of your current ROM, and flash the older firmware to get right back where you left off.
Best of luck, enjoy your flashings
Is the camera files only located in system/ app and cameradata?
I'm going to play around madhatter like and attempt to restore the shutter button on the edge panel like it originally should've stayed... I'm using Hyperdrive RLS4 NK3 and RLS7 COK2
n1nj4Lo said:
Is the camera files only located in system/ app and cameradata?
I'm going to play around madhatter like and attempt to restore the shutter button on the edge panel like it originally should've stayed... I'm using Hyperdrive RLS4 NK3 and RLS7 COK2
Click to expand...
Click to collapse
Any updates? Would be really interested in this as well
That was all the places I could find it but when I restored camera phone wouldn't boot... I think it might be cause I didn't set the right permissions.
I did successfully retrograde down to kitkat with a kernel and cok2 5.1.1 odin firmware.
n1nj4Lo said:
That was all the places I could find it but when I restored camera phone wouldn't boot... I think it might be cause I didn't set the right permissions.
I did successfully retrograde down to kitkat with a kernel and cok2 5.1.1 odin firmware.
Click to expand...
Click to collapse
Wait I don't understand. Are you saying you were able to get the old camera app? But it wouldn't open?
And you said you were able to retrograde? So you are back on KK? can you link me to the kernel and firmware and or the directions to do this. I am not the only one that might wanna go back to good Old KK
edo101 said:
Wait I don't understand. Are you saying you were able to get the old camera app? But it wouldn't open?
And you said you were able to retrograde? So you are back on KK? can you link me to the kernel and firmware and or the directions to do this. I am not the only one that might wanna go back to good Old KK
Click to expand...
Click to collapse
No when I tried to port them over to LP then phone would just freeze up on the first splash boot screen, however I accidentally didn't have the permissions set correctly also.
I'm going to post a tutorial thread in a second... But
You can't Odin to NK3 from MM PE3, you've gotta Odin downgrade to LP COK2 and THEN flash recovery flash the selected KK rom of choice and then whatever KK kernel ya can find that ya like, I've found that LLFK is still active and alive. You might also wanna Odin flash the KK modem too for better GPS location.
Samsung made it or tried to make it irreversible ever since COK2, it's impossible to Odin back down to NK3 KK, so you have to flash a rom, kernel and modem for matching baseband.
KitKat Low Lying Fruit Kernel N915T: http://forum.xda-developers.com/note-edge/general/kernel-allows-selinuxpermissive-n915t-t3017469
KitKat NK3 N915T Modem: http://www.mediafire.com/download/s3l46lx7dfs26on/modem.tar.md5
Odin COK2 Firmware LP 5.1.1: https://www.androidfilehost.com/?fid=24545065934258546
Trust me I played around for a day and a half until I discovered it was possible to boot a KK rom off of COK2 and messing with Odin too, just a warning if ya don't flash a kernel you won't have working WiFi at all. Can't even Odin to LP 5.0.1.
n1nj4Lo said:
No when I tried to port them over to LP then phone would just freeze up on the first splash boot screen, however I accidentally didn't have the permissions set correctly also.
I'm going to post a tutorial thread in a second... But
You can't Odin to NK3 from MM PE3, you've gotta Odin downgrade to LP COK2 and THEN flash recovery flash the selected KK rom of choice and then whatever KK kernel ya can find that ya like, I've found that LLFK is still active and alive. You might also wanna Odin flash the KK modem too for better GPS location.
Samsung made it or tried to make it irreversible ever since COK2, it's impossible to Odin back down to NK3 KK, so you have to flash a rom, kernel and modem for matching baseband.
KitKat Low Lying Fruit Kernel N915T: http://forum.xda-developers.com/note-edge/general/kernel-allows-selinuxpermissive-n915t-t3017469
KitKat NK3 N915T Modem: http://www.mediafire.com/download/s3l46lx7dfs26on/modem.tar.md5
Odin COK2 Firmware LP 5.1.1: https://www.androidfilehost.com/?fid=24545065934258546
Trust me I played around for a day and a half until I discovered it was possible to boot a KK rom off of COK2 and messing with Odin too, just a warning if ya don't flash a kernel you won't have working WiFi at all. Can't even Odin to LP 5.0.1.
Click to expand...
Click to collapse
Thanks again for the time you put into this. Btw, to answer the camera question it's just not possible?
If that's the case, is there something else you can look into for me?
I am not sure if you use Briefing. Its flipboard but then version that actually uses the edge screen. Anyways, I hate briefing being part of the home screen. It makes easily navigating between windows tough. The way I went around doing this was the Edge panel that was available, until Samsung took it out with MM. Do you know how I could install the 5.1.1 briefing version. I think it would be a similar thing as removing the native camera app.
Directions being I would remove the briefing app, and install the 5.1.1 version. Prblm is I don't know how to do that (removing stock programs and manually installing old one) Whats worse, It seems I'm the only person that cares about this app and how functional it used to be on Edge. It was my quickest way to accessing the news
I think and believe that the only way to get that camera again is if some cloned the app and redeveloped it for higher versions of android... I've got a full video suite of Infinite Skills How to Develop App's for Android, me and my ADHD have just never gotten around to watching it yet. LoL
removing stock app's is easy if ya have root there's a few simple ways of doing it such as ES File Explorer with Root permissions navigating to the root of the rom then going into system, then either apps or priv-apps and just deleting FlipboardBriefing.apk, it's in apps actually... Then you could install a non-edge google play store version, or get tx toolbox and uninstall it or all-in-one toolbox and go to toolbox then uninstall system apps.
I posted this in the wrong place before and cant delete it.
Im having issues flashing roms. So far Resurection remix os the only one that worked. Cm13 fails code 7, m.o.a.r. 7.0 fails as aroma is begining to run. Gettin a bit annoyed.
Also, cant find a hotspot fix for og1.
Any thoughts?
Sprint S5 G900p
5.0 stock rom
Og1 build
ive had to re-download MOAR 7.0 a couple of times, i have one copy of it that does the exact same thing (failing when aroma launches) Get a clean download and try it again. Also when going from an AOSP to TW or vice versa, make sure to ALWAYS delete the android folder from both internal and external otherwise youll get TONS of f/c's
Right on.
Any thouggts on why cm13 gives a code 7?
Its the right version for my phone. Code 7 is a failsafe for the wrong phone so it wont install (from what ive read)
Redownloaded moar, checked md5, that was good, same thing no go.
I got hotspot going and i guess stock works well enough. Ill just strip it down and add the goodies that I use alot.
Guess my flashaholicism will have to subside for now.
OG1 might be your issue. Try installing OK4 via Odin, then chainfires root method, then TWRP 3.0.2-2 and go from there, unless youre happy with what you have. It doesnt make any sense for it to fail with a fresh download.
I can try that.
Whats the build order on the s5? I tried updating before root and it stayed at og1.
Stock Official OA6
Stock Official OD3
Stock Official OF6
Stock Official OG1
Stock Official OK4 (5.0)
Stock Official PCA (6.0.1)
copied from here
you can get the OK4 from the link i posted and flash it via Odin. Then youll have to reroot (super easy if you can flash the tar.md5 firmware) and then twrp. 3.0.2-2 is the newest
Thank you. Excellent post.
These are all for sprint, correct?
Cant see links on your link but looked at sammobile and they have pe2 as latest build.
Gonna update and try again.
dwilson48625 said:
Thank you. Excellent post.
These are all for sprint, correct?
Click to expand...
Click to collapse
yep, all from sprint
heres the list from today from sammobile. Those last 2 builds are news to me, and im not at all familiar with them
you might need to log in to idoneapps.com to see the post. they have their own forums there and that post is listed under general/support/stock tar.md5s/ stock official tar.md5
Thanks!
Im on the road today but will odin this up tomorrow. Hopefully it solves my issue.
Is the s5 like the s3 where we can go up with the basebands but not back?
dwilson48625 said:
Thanks!
Im on the road today but will odin this up tomorrow. Hopefully it solves my issue.
Is the s5 like the s3 where we can go up with the basebands but not back?
Click to expand...
Click to collapse
no. Many people have flashed the pca build then flashed the OK4 and been just fine
Yeah, hotspot fix didnt work on anything beyond ok4, so i went back.
Makes sense. The ok4 baseband has proven itself to still be quite useful
Sent from my SM-G900P using XDA Free mobile app
Yeah i see no need to go higher.
ive actually recently installed twrp 3.0.2-2 and the aroma installer on MOAR wont launch for me. It has to be a proclivity of 3.0.2-2. Ive never had this issue with previous builds. I can test this tonight unless you want to test it before i get a chance
Yes please. I can install RR rom (name escapes me, remix something lol), but moar wont go. Same issue, aroma wont start.
resurrection remix. Super popular ROM. pretty awesome too. anyways, it really seems like an aroma issue. ill give 3.0.2-1 a whirl later
It's a 3.0.2-2 issue. 3.0.2-1 launches the aroma installer just fine. It's a quick fix in Odin. Literally seconds to download and not much longer to flash