Related
I have a brand new GE Android 4.2.2 running MFD that I'd like to be able to flash Android 4.3 and/or the Faux Kernel on to enhance functionality. I've been scouring the xda forums for a couple of days and can't find any posts with anyone attempting this. I had no problem rooting the phone and installing CWM recovery but for the life of me I can't get a custom rom or kernel on it. I have tried i9505 MF8 roms and various kernels including Faux. I've tried dirty flashing and clean flashing. I can't the phone to boot after installing any of these and always have to revert back to my stock backup. (I believe it because I'm on MFD).
Anyone else trying this, something similar, or have any ideas?
Any advice would be greatly Appreciated.
matthemattix said:
I have a brand new GE Android 4.2.2 running MFD that I'd like to be able to flash Android 4.3 and/or the Faux Kernel on to enhance functionality. I've been scouring the xda forums for a couple of days and can't find any posts with anyone attempting this. I had no problem rooting the phone and installing CWM recovery but for the life of me I can't get a custom rom or kernel on it. I have tried i9505 MF8 roms and various kernels including Faux. I've tried dirty flashing and clean flashing. I can't the phone to boot after installing any of these and always have to revert back to my stock backup. (I believe it because I'm on MFD).
Anyone else trying this, something similar, or have any ideas?
Any advice would be greatly Appreciated.
Click to expand...
Click to collapse
Hi,
Look HERE
4.3 is at the bottom of the second post.
matthemattix said:
I have a brand new GE Android 4.2.2 running MFD that I'd like to be able to flash Android 4.3 and/or the Faux Kernel on to enhance functionality. I've been scouring the xda forums for a couple of days and can't find any posts with anyone attempting this. I had no problem rooting the phone and installing CWM recovery but for the life of me I can't get a custom rom or kernel on it. I have tried i9505 MF8 roms and various kernels including Faux. I've tried dirty flashing and clean flashing. I can't the phone to boot after installing any of these and always have to revert back to my stock backup. (I believe it because I'm on MFD).
Anyone else trying this, something similar, or have any ideas?
Any advice would be greatly Appreciated.
Click to expand...
Click to collapse
It doesn't work yet. We have no custom ROMs or custom recovery for our phone (9505G) as of yet. The 4.3 leak has a lot of issues for most of us. If you've flashed and gotten stuck not being able to load - I recommend following my directions here to fix - http://forum.xda-developers.com/showthread.php?t=2360346
4.3 on GE
Thanks malybru!
I was able to flash 4.3 on my i9505 GE this evening.
It's a little buggy. Navigation is gone and the GPS doesn't seem to function correctly.
The rom does say experimental so I was expecting some degree of bugs.
Frankly I'm just happy I was finally able to flash something on my phone.
Are there any other roms available for the i9505 GE?
I haven't been able to find any, but of course I was unable to find the 4.3.
Thanks again for your help
No Roms
donovanbrock said:
It doesn't work yet. We have no custom ROMs or custom recovery for our phone (9505G) as of yet. The 4.3 leak has a lot of issues for most of us. If you've flashed and gotten stuck not being able to load - I recommend following my directions here to fix - http://forum.xda-developers.com/showthread.php?t=2360346
Click to expand...
Click to collapse
The only thing I wasn't able to load were the MF8 roms such as Omega. I was never in a soft brick state. It's disappointing to know there are no roms out yet but not surprising. I was wondering how the community would support the GE phones. I wasn't sure if there'd be hoards of developers using the phones or none at all.
XDA should have a GE category in the i9505 section.
Thanks for the advice.
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Same issues apon using The Samsung Galaxy S4 for Verizon (jfltevzw) Build MK2 rooted using vRoot (English) and using safestrap. if needed I can upload the safestrap apk or version. If I install any type of AOSP ROM the boot logo is either missng or baby blue with wierd static lines. AOKP is the only AOSP ROM that eventually boots (with static boot logo) but no wireless works, and this is the same wether MK2 and/or MJ7 modules are installed or not. the only rom I can successfuly install and use daily that has no bootloader based issues is Hyperdrive ROM For jfltevzw & jflteatt. Any info would be much apreciated!
Sent from my SCH-I545 using xda app-developers app
^ Interesting. I didn't expect anyone else to have this issue. I never read about it before. I really feel like it has something to do with SafeStrap.
Heath Cliff said:
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Click to expand...
Click to collapse
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
REEEEEEAAAAADDDD!!!!
It's been very well documented that AOSP does not work with safestrap. Neither does loki. There currently is no way/fix to flash AOSP.
So
1. No AOSP or GPE
2. No loki
3. No flashing custom kernels
Sent from my GT-I9505 using Tapatalk
John The Rhino said:
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
Click to expand...
Click to collapse
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Heath Cliff said:
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Click to expand...
Click to collapse
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
John The Rhino said:
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
Click to expand...
Click to collapse
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Heath Cliff said:
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Click to expand...
Click to collapse
Hey man I totally understand. It's hard to watch all these other roms pop up for the original S4 & we can't flash them. But we no longer have to suffer with only the stock rom option since Hashcode's brilliant Safestrap was released. Once you get use to it, the ability of being able to multi-boot roms really kind of makes up for the locked boot loader. Soon though, we will have 4.4 Kit Kat & then we can start this process of getting off the stock rom all over again. Right? It could be worse, we could have I-phones. We do have a ever growing number of great custom TW based roms available to us here for our device. So try them, you'll be surprised how much better your phone performs. Glad I made sense & forgive my bluntness that's just how us Rhinos roll.
Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).
jbrookley said:
Hello everyone,
So, I've been looking into the status of unlocking the bootloader for MF3 updates (I downloaded it and read too late that they locked the bootloader in the update, sneaky bastards) and it appears this issue still hasn't been fixed. From what I understand, Dan Rosenberg waited until the Verizon update was released before he revealed the Loki exploit but, from what I've read, this exploit does not work on the MF3 update.
My question is now what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
I'm trying to understand some of the specifics as I've read a number of articles and links (both in XDA as well as others) and I'm still a bit confused as to where we're at with this. From what I can see, it doesn't appear there is any workaround in sight if the Loki exploit doesn't fix it. Am I more than likely stuck with a locked bootloader for the life of this phone?
Realistically, I am still able to get root access, so it's really not the end of the world but I'd definitely like to be able to flash custom roms if I wanted to. It sounds like I can indirectly do that via Safestrap (does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?). But as of now, I believe that's my only option, if I understand correctly.
I realize a number of these issues have been addressed probably a number of times but, due to the amount of details and updates that seem to be changing, I just want to make sure I have a good understanding of everything so I know what my options are. If anyone wants to address this, I'd appreciate it but if these have all been answered a million times in one form or another, I understand that as well.
Thanks for your help!
(I put my questions in bold just to draw attention to them so anyone reading it doesn't have to search through my message to find them to address them, I'm not trying to come off like I'm yelling).
Click to expand...
Click to collapse
When Samsung released the MF3 update they used a two-prong attack to close the Loki exploit... those being
1. Closing the exploit in the code itself.
2. Blowing a qFuse on the board to prevent us from flashing any firmware lower then MF3.
I don't really want to get into the technical aspects of how this happened... I'll let someone else answer it if they wish.
jbrookley said:
Hello everyone,
what is it that stops this from working with the MF3 version? Wasn't that the initial point of the release was to solve this particular issue?
Am I more than likely stuck with a locked bootloader for the life of this phone?
does it basically just protect all the crucial stuff that can break the fuse on the device and allow you just use TW based roms, just not custom kernals, is that correct?
Click to expand...
Click to collapse
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.
DeadlySin9 said:
Nighthawk gave the short answer for the first two. Also, it's possible the update mentioned may have been the MDB>MDL update or verizon equivalent.
Technically even MDL people are stuck with a locked bootloader, but they have an exploit. People are working on an exploit for MF3+, but I can't say how likely it is one will be found.
Safestrap lets you do anything a normal recovery can except flash kernels. This is why you can only flash TW ROMs, as the AOSP and TW kernels are not compatible. Kernels would trip the bootloader checks. However, to add a bit to this and the last answer, something called kexec is in progress of being implemented into Safestrap. The exploit found allows loading unsigned modules, which in turn allows loading a kexec module, which would then load a kernel over the stock kernel while in the boot process. So if this works, it would be the next best thing to a bootloader exploit in that it would give us the same result, though I don't know if kernels will require tweaks to load in kexec.
Click to expand...
Click to collapse
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium
jbrookley said:
Thanks for taking the time to explain that!
A somewhat related question, if my S4 ever gets an OTA update for 4.3, should I deny the update in case they create more obstructions for updates or should I take it since that's the only way my phone will get 4.3 at this point?
Click to expand...
Click to collapse
[email protected] said:
I believe the kexec exploit is being worked on for mk2? But I'm not too sure you will have to review the threads.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
It is MK2 exclusive since the MK2 root method gives access to kernel memory and allows it. However, once on MK2 you should definitely not take any and I'm not sure whether the security policy updates are safe or not.
Hey,
I got my Galaxy S4 AT&T SGH-I337 as I337UCUAMDB, and ever since then was running cyanogenmod 11.
Recently after a stupid mistake (updating to a nightly, then to M10) I had to return to stock ROM, and on a CM dev's lead installed a NB1 ROM.
Since then, I wasn't able to install TWRP (installing it would make the phone boot only into download mode), and installing CM would produce constant "com.android.phone/acore/media" errors.
Right now I'm running Google Edition for SafeStrap (v1.1 - 4.4.4), which, TBH, isn't nearly as good as CM11 and still very buggy...
I read as much as I could about the whole AT&T GS4 bootloader situation, but still haven't understood it fully:
Could my bootloader have been locked by the update?
If not, why can't I install a custom recovery and CM again?
If so, is there anyway I can downgrade back to MDB (maybe from here?) Or to anything that can allow me to install CM again?
Thanks in advance,
Yuval.
Edit: If I can still use safestrap to install any custom ROM, why can't I install CM? (I did a clean install [full wipe] a couple of times, w/ and w/o gapps, to no avail) Or did I not understand well the safestrap custom ROM options?
Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.
RAID Xero said:
Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.
Click to expand...
Click to collapse
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
novikyuval said:
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
Click to expand...
Click to collapse
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Sent from my Nexus 5 using XDA Free mobile app
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
jd1639 said:
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Click to expand...
Click to collapse
RAID Xero said:
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
Click to expand...
Click to collapse
Okay, I think I now fully understand this. Thank you RAID Xero and jd1639 for the help!
I guess I learnt my lesson to look into evil AT&T ROMs before updating to and from them
Also, too bad I never noticed any warning regarding this on Cyanogenmod's website (or maybe I just missed it)...
Thanks again, and unless there's a new magical way to bypass the locking, this thread may be marked as locked.
You're welcome, and happy flashing!
Not sure what all information you will need but ask and I shall gladly supply
Got a LG-ls980
Running stock lollipop 5.0.1 on ZVG update or w/e
Rooted using LG One Click Root (program never said it finished but checked phone and root is verified)
Used autorec to get TWRP v2.8.6.1 (seemingly worked fine)
currently trying to flash the latest nightly of Cyanogenmod
Receiving errors like
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error executing updater binary in zip '/pathtopackage/packagename.zip
can no longer boot normally "security error"
I've done some looking around and tried a few different things but nothing has made any changes, any assistance would be greatly appreciated, thanks
I was told something about loki needing to be unlocked but haven't made any progress as this is my first LG style phone
I'm sure the solution has probably been posted somewhere and probably isn't that difficult but either I couldn't find it or I didn't recognize what I was reading
Tokerot said:
Not sure what all information you will need but ask and I shall gladly supply
Got a LG-ls980
Running stock lollipop 5.0.1 on ZVG update or w/e
Rooted using LG One Click Root (program never said it finished but checked phone and root is verified)
Used autorec to get TWRP v2.8.6.1 (seemingly worked fine)
currently trying to flash the latest nightly of Cyanogenmod
Receiving errors like
assert failed: run_program("/system/bin/loki.sh") == 0
E: Error executing updater binary in zip '/pathtopackage/packagename.zip
can no longer boot normally "security error"
I've done some looking around and tried a few different things but nothing has made any changes, any assistance would be greatly appreciated, thanks
I was told something about loki needing to be unlocked but haven't made any progress as this is my first LG style phone
I'm sure the solution has probably been posted somewhere and probably isn't that difficult but either I couldn't find it or I didn't recognize what I was reading
Click to expand...
Click to collapse
Doesn't the 5.x autorec install the 4.4 bootloader? You need a 4.2 bootloader to flash cyanogenmod 12 at the moment, because it still uses the loki exploit, instead of the bump provided with the 4.4 bootloader.
Choristav said:
Doesn't the 5.x autorec install the 4.4 bootloader? You need a 4.2 bootloader to flash cyanogenmod 12 at the moment, because it still uses the loki exploit, instead of the bump provided with the 4.4 bootloader.
Click to expand...
Click to collapse
I realized there were bootloader issues, how do I go about getting a 4.2 bootloader
Tokerot said:
I realized there were bootloader issues, how do I go about getting a 4.2 bootloader
Click to expand...
Click to collapse
Are you planning on running lollipop? I'd suggest keeping the 4.4 bootloader and flashing a CAF-based rom, not only they are much less hacky, they're pretty much stable now.
I'd only flash the old bootloader if I were to install kitkat. Current CM12 sources are VERY outdated.
I was trying to find you the jellybean bootloader but since I don't own a ls980 and I don't visit the section too often this was the closest I could find http://forum.xda-developers.com/showthread.php?t=2627765
I was trying to find you the jellybean bootloader but since I don't own a ls980 and I don't visit the section too often this was the closest I could find http://forum.xda-developers.com/showthread.php?t=2627765[/QUOTE]
My goal is to have CM12 Lollipop but with a working radio (so a KK bootloader but LP rom?) Reading around I've seen people who have successfully done it but I've got no luck. I'm willing to start over and reflash everything needed, I just need the files and order to flash.
If i could find out how to fix this Loki issue i could finish this easy.
Tokerot said:
I was trying to find you the jellybean bootloader but since I don't own a ls980 and I don't visit the section too often this was the closest I could find http://forum.xda-developers.com/showthread.php?t=2627765
Click to expand...
Click to collapse
My goal is to have CM12 Lollipop but with a working radio (so a KK bootloader but LP rom?) Reading around I've seen people who have successfully done it but I've got no luck. I'm willing to start over and reflash everything needed, I just need the files and order to flash.
If i could find out how to fix this Loki issue i could finish this easy.[/QUOTE]
Can you link me to the rom thread?
If everything else fails, there's always the Kitkat KDZ -> Kitkat autorec (which installs the JELLYBEAN bootloader, the one you're looking for).
Otherwise, have you considered maybe using a 5.1.1 lollipop rom?
Choristav said:
Can you link me to the rom thread?
If everything else fails, there's always the Kitkat KDZ -> Kitkat autorec (which installs the JELLYBEAN bootloader, the one you're looking for).
Otherwise, have you considered maybe using a 5.1.1 lollipop rom?
Click to expand...
Click to collapse
Anything you would suggest? I use aviate launcher so really whatever is the best for battery. As long as it's for ls980 and is easy to do.
Thank you for helping me this far I appreciate it.
Tokerot said:
Anything you would suggest? I use aviate launcher so really whatever is the best for battery. As long as it's for ls980 and is easy to do.
Thank you for helping me this far I appreciate it.
Click to expand...
Click to collapse
My pleasure, thank you for using the Q&A section instead of spamming the development threads like users usually do.
While I can't recommend any rom personally (this leads to uneasiness between developers, publicly saying a rom is better than another is frowned upon and for good reason, as they all bust their asses to deliver something for -free-), I can say that anything that has [CAF] in the title is a green light for you.
You can check here or here. I personally use Euphoria-OS as it's basically what you probably think of cyanogenmod with extra customization, but RR, blisspop crdroid and others are really good, too. You just have to look a tiny bit into it. Many if not all of these threads support multiple variants, just search for ls980 and you're good to go.
There are also developers like @zg85 who have done an amazing job both contributing to the CAF-rebase and building several roms for the d802, although practically none are posted as a thread on XDA. While they're not for your variant, there probably is at least a single developer who doesn't post his builds to XDA for the sprint version.
Lastly, as soon as the CAF rebase is complete (as in completely stable, as at the moment there's a bluetooth bug and some connectivity issues), rashed97 himself will post a CM12.1 build and many other roms will pop up (as the device source will be stable, porting will be really easy).