Related
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
krazie1 said:
This is a thread to see if anyone has ideas on porting CWM or TWRP to our device? Any ideas of getting a custom recovery on this phone is welcomed. We have Root for the At&t/Verizon variants, custom recovery would be topping to the cake.
Click to expand...
Click to collapse
Dont we need an unlocked bootloader first?
chrisexv6 said:
Dont we need an unlocked bootloader first?
Click to expand...
Click to collapse
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
EDIT: I thought about it and your right, you always have to unlock the bootloader before you install the Custom Recovery.
krazie1 said:
I'm not to sure, I know you need the bootloader unlocked for Roms and Kernels
Click to expand...
Click to collapse
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
dmbfan13 said:
Are you sure the bootloader needs to be unlocked in order to install roms?? Thought that was only for custom kernels. Moto devices have always had pretty locked down devices, yet had recoveries and ability to install roms, if I remember correctly...
Click to expand...
Click to collapse
kexec is required to flash a kernel.
Safestrap is a way to flash somewhat custom ROMs (without kexec you need to use stock kernel) without recovery installed but it needs to be adapted to each specific phone. Right now I think they are working on a version that will work with the S4, not sure how attractive the G2 is (or will be).
krazie1 said:
This is a thread to see if anyone has ideas on Unlocking the Bootloader & porting/creating CWM or TWRP to our device? Any ideas are helpful and welcomed.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2443165 <---- these guys are the ones who worked most of the magic for Optimus G (and Pro?).
You guys first need Root to do anything (which i believe you have). Then you need a Custom Recovery. Installing a Custom Recovery can be accomplished via a workaround or by unlocking the bootloader. A workaround like loki by djrbliss on the Galaxy S4 which isn't an unlock but more so a bypass or like Safestrap by Hashcode.
Here is the man djrbliss.
http://forum.xda-developers.com/showthread.php?t=2358871
https://twitter.com/djrbliss
Is there any news on this? I cant even find a good place to look for info about this phone yet.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Darkestred said:
There was someone who posted an IRC room for the g2 but i can't find it and i don't recall who posted it.
Click to expand...
Click to collapse
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
WACOMalt said:
Is there any news on this? I cant even find a good place to look for info about this phone yet.
Click to expand...
Click to collapse
WACOMalt said:
what is the channel name? I wanna hop in there.
I just ripped my aboot.img from my system. Trying to figure out who to send that too for it to be of use.
Click to expand...
Click to collapse
I found it. server is chat.freenode.net room is lg-g2. Not very much going on in there at the moment.
i completely agree with the said explanation. but I'm having difficulties with my device i.e. LG G2 (D802).
I'm rooted with custom recovery TWRP and unable to install most of AOSP roms based on 4.4 KitKat. New Custom roms are coming up very frequently now for this device but so far I'm able to flash ParanoidAndroid Rom and modifited stock rom... Apart from this I always gets error while flashing the rom.
Most of the time Error comes up saying 'Status 7 Error' and 'unable to execute update binary'.
I did google on this subject and tried everything i found but the problem still exist.
I never had these problem flashing LG Stock or Android 4.3 based roms. Need advise on this subject. By the way any help on unlocking the bootloader????
thanks:good:
krazie1 said:
http://forums.androidcentral.com/ht...oader-custom-recovery-root-flashing-roms.html
Why should I unlock?
The explanation to this question is really simple. If you want root, you’d be wanting to flash Custom ROM post-root, and if you want to install a Custom ROM, you’d need to have your stock bootloader unlocked. In simple terms Unlocking the bootloader allows you to install custom Firmware on your Android phone
Warning: Unlocking your phone’s bootloader voids its warranty. It also completely wipes (formats) your Android phone’s internal memory including applications, contacts, SMS and MMS messages etc.
Click to expand...
Click to collapse
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723
Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??
khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol
khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.
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!
I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.
Taymar said:
I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.
Click to expand...
Click to collapse
Yea, you can't flash cm or pa on your device. They can only be flashed on devices with the mdb or mdl bootloader. If you're using safestrap, and it's the only recovery you can use, you're probably on 4.4.4, nb1 or nc1 or nj4, bootloader. You'll need tw based roms. See the ones that work with safestrap.
Sent from my Nexus 9 using XDA Free mobile app
Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.
Taymar said:
Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.
Click to expand...
Click to collapse
Your stuck to 4.4.4 unless you do the method mentioned on the forums and GoldenEye comments.
But a caution its not for the new, is risky and you lose the safestrap recovery boot because safestrap is not lollipop compatible right now.
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
I don't own it so I couldn't tell you but I would look up the forum for it before hand and see what they say about it.
If it's not an ATT and Verizon phone most likely it's not boot loader locked.
Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
Oneplus you will be able to root and recovery, I believe even unlock the bootloader. You just have to pay full price of the phone of course, but it's separate from carrier so no root patching OTAs.
Awesome. Thank you so much guys. I think I'm going to try out the oneplus one. Sounds like it'll be a lot more straightforward than with AT&T's devices.
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).