Related
CyanogenMod and D2VZW: Marshmallow Love!
To Make this easy, I am going to copy a bit of the common sense information Master Cylinder put up for the release of Lollipop, same basics apply here!
Huge thanks to Invisiblek for making these builds for us!
Thanks to Master Cylinder for all the super useful information!
De-unified Marshmallow builds for the Galaxy S3 line. This is for the Verizon variant (SCH-I535) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 which is designed to increase performance and reliability over stock Android for your device.
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1 (Also, see "Notes - Possible Bugs" section below)
(EDIT: The following statement might not be true. It happened to one user. Unsure about circumstances...)If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
If you know you never took the 4.3 OTA, then you can flash the firmware and modem to your hearts content.
CWM Recovery addicts: Please seriously consider giving up CWM and come on board with what works for sure with 5.1.x and up, TWRP. Problems have been coming up with CWM users so if you have one, that's were to start. Hopefully there's a 12-step program somewhere for y'all
Google apps addon:
Open GApps opengapps.org They have many options for you to choose from based on your needs. Updated daily.
>>>WARNING!!<<< The first time one installs Open GApps, you have to do it with a ROM update (or reinstall current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally, then wipe Dalvik and Cache. After that, you can flash them anytime. (More info on Website.) ALSO, for now, don't install Webview as it might not work. There is an "Android System Webview" in the Play Store that will work.
I personally don't use GApps on my Daily Driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Dalvik and Cache, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs!
This page will be a work in progress, so please don't yell if something is missing. I just got the OK to share this with others and wanted to get it out there for you to enjoy. I have been playing with it for the last 24 hours and it is ROCK SOLID in my opinion. I haven't found any issues yet! Daily Driver for me for certain. If you have issues, please post them for discussion below!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
BUGS:
Need to possibly load a different File Explorer to access SD Card (DoctorImpossible)
Access to camera is not functioning correctly (DoctorImpossible) *EDIT 11-23 build camera works, camcorder fix coming next build!
Outgoing text messages show "not sent", but actually send fine. (Stealth111)
Incoming phone calls do not show caller information (Stealth111)
**When you get your ROM installed and up and running, please be kind and put a small post with information about your install so we can get as much info gathered as possible. (ROM build you installed, Recovery type/version, Clean install, or Dirty (and if dirty, over what version did you flash), what GApps package you installed(exact one please) as well as when you installed it (if on same initial install as ROM, or differently). And lastly maybe the firmware/modem combo you are running. Thanks!
***IMPORTANT INFORMATION*** If you are going to flash to cm-13.0-20151121-UNOFFICIAL-d2vzw or later build, there have been some database changes. InvisibleK has provided a flashable zip file to accommodate nuking your old telephony and settings databases. Nandroid or backup files as needed if you want, as I seem to remember doing this with CM before, and clearing the database wiped texts and call logs I believe. This only needs to be done 1 time, the first time you flash any build from 11-21 on. After you have done this once, you are good to go moving forward, you will be upgraded to the new databases. If you do not flash the "Nuke_It" zip file, you will get phone FC's and a "No SIM Card" error message. So whether upgrading, dirty flashing or whatever, reboot into recovery, flash the ROM, and BEFORE you boot, flash the following zip!
Nuke IT Database Wiper
Profit!
Enjoy!
Stealth111
For Future Use
First
For Future Use
Second
Stealth111 said:
Second
Click to expand...
Click to collapse
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Master Cylinder said:
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Click to expand...
Click to collapse
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Stealth111 said:
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Click to expand...
Click to collapse
Thanks. I also misread the notation at OpenGApps, which said that need a "ROM" with the patch to allow Google services permissions. Also, there are some posts I've found about fixing permissions after boot then reinstalling GApps, but I won't post that here in case it misleads. I'll be the guinea pig as I've dloaded and backed up and ready to jump out the window!
Stealth111 said:
CyanogenMod and D2VZW: Marshmallow Love!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d..._NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
Enjoy!
Stealth111
Click to expand...
Click to collapse
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
I just finished booting it. It seems pretty nice, and I only noticed a few things. The boot time was around half an hour as usual with lollipop. I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Ghost Protocol said:
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
Click to expand...
Click to collapse
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Doctorimpossible said:
It seems pretty nice, and I only noticed a few things. . I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Click to expand...
Click to collapse
I also can't access the camera even after installing a new camera app. A new file explorer took care of my sd card issues however.
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Master Cylinder said:
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Click to expand...
Click to collapse
So is this a hit or miss when flashing or not?
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Stealth111 said:
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Click to expand...
Click to collapse
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
Of course! It's the first unofficial build for us.
Stealth111 said:
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Click to expand...
Click to collapse
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Master Cylinder said:
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Of course! It's the first unofficial build for us.
Click to expand...
Click to collapse
Here is the MD5 from my file if it helps!
192BD2F6A83BCA791E0AFE9570134058
Doctorimpossible said:
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Click to expand...
Click to collapse
Yuppers! Exposed for Android 6
Thanks for the report!
Fingers crossed for Master Cylinder!!
Stealth111 said:
If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
Click to expand...
Click to collapse
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Jaws4God said:
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Click to expand...
Click to collapse
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Master Cylinder said:
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Click to expand...
Click to collapse
all i rememeber was downgrading from h2 to h1 to get root access.. then flashed CM12.1 on top of that ..
Sent from my SCH-I535
As was my plan all along, kltevzw official support for AOSP roms is picking up. Please see this thread for official downloads and support:
http://forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
My builds will cease.
-- Begin copy-pasta template from my CM13.0 build thread... please let me know if I miss updating something --
Note: I don't run this ROM personally, I really just built it. It shouldn't, but it may eat your cat.
Code:
*** Disclamer
-- You install these at your own risk! You are responsible for anything that happens from flashing these files to YOUR phone! If your
phone melts into a pile of goo, catches on fire etc. IT IS NOT MY RESPONSIBILTY BUT YOURS!
FAQ:
Q: Can I use this?
A: Do you have a developer aboot? If so then yes, but I won't help you install a developer aboot. I only ever had a Developer phone, so I only know the process as well as reading the thread. See this thread for info/help: HERE
Q: When/how often are these built?
A: Less often than my CM13.0 build, but at least every week. Unlike my CM13.0 build, I don't use this ROM so I won't be doing a "does it boot" check before uploading. Please tell the entire thread if one day's build doesn't work properly.
Q: Can I get help with something?
A: I have a full-time job and travel a lot. I'll try to jump in and answer some questions, but there is a lot of info out there for you to learn on your own. Aside from you having a vzw-variant, most of the details are standard KLTE. Please see the normal Resurrection Remix KLTE thread for standard ROM help.
Click to expand...
Click to collapse
Recovery:
The standard KLTE TWRP 3.1.0-0 should mostly work, but MTP doesn't work for any klte* variant using it.
I prefer KToonsez's 2.8.6-based Recovery. It's older, but MTP works.
There are Unofficial 3.*.0-* recoveries available by @jcadduono. I find that these don't support decryption properly, which I find to be mandatory.
Like many other devices, the .zip files can be flashed in a recovery. The .tar.md5 files can be flashed in ODIN. The .img files can be flashed using Flashify, a TWRP recovery. You can even get an .img file from a .zip or .tar.md5 if you just open it up.
If you use adopted storage then things get odd. The latest recovery by @jcadduono MAY support adopted storage if you don't encrypt userdata (I personally know that TWRP handles adopted storage for jflte and d2), but I do use encryption so I don't use that recovery. It may be that you only see /data/media/0 -- if so, I find that using Flashify for each nightly is the most straightforward way to update, but you could always manually copy to /data/media/0 before rebooting to recovery. This is a standard Marshmallow and TWRP thing.
Click to expand...
Click to collapse
Modem/Firmware:
Most of the LP modem/firmwares should work, but I use the one PB1 here. This modem matches with the proprietary vendor files that are part of the build. Flash it in ODIN. Please note that some have reported that you cannot flash these after the aboot unlock; If you cannot flash the PB1 modem/non-hlos it shouldn't cause any big problems.
https://www.androidfilehost.com/?fid=24459283995308895
Click to expand...
Click to collapse
GApps:
Resurrection Remix recommends SlimGapps or OpenGapps. See their thread for discussion of pros/cons and what those users tend to use. If you use OpenGapps, make sure to use an 6.0 version for ARM architecture.
OpenGapps
SlimGapps
Click to expand...
Click to collapse
Downloads (the thing you were looking for):
I'll build at least once per week, at least until the RR team picks up the torch. Once the build is complete, I upload it to my AFH account.
ResurrectionRemix-M v5.6.X KLTEVZW weekly-ish
Click to expand...
Click to collapse
Does/Doesn't Work:
Everyone that gives it a shot needs to let the thread know. See the Unified Resurrection Remix thread for discussion of what generally does/doesn't work with the ROM.
forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
Click to expand...
Click to collapse
Thanks:
Everyone on the Resurrection Remix and CM teams. This is 99% of their stuff with just a couple tweaks to make it build, (hopefully) boot, and run for KLTEVZW. See Post 2 for those changes.
Click to expand...
Click to collapse
Android Version: 6.0.1_r22 (prior to 20160406 build)
Android Version: 6.0.1_r24 (20160406-present build)
I forgot something. I know I did. I'll try to update this post sometime.
More things...
Source
In order of importance:
Resurrection Remix github: https://github.com/ResurrectionRemix
Cyanogenmod github: https://github.com/cyanogenmod
My github: https://github.com/haggertk
Click to expand...
Click to collapse
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
tbclandot said:
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
Click to expand...
Click to collapse
Someone needs to be the guinea pig. I know how much a pain it can be setting a ROM up from a clean install, but if CM feels just a bit too vanilla then I'd say jump into the pool.
Alright going to download and flash it now and I will report back to you thanks for your hard work!
---------- Post added at 01:06 AM ---------- Previous post was at 12:35 AM ----------
Hagg flashed the rom and everything seems to be working so far I can make calls and receive texts I prefer RR to CM13 for the features! Just wish there was a way to get my Gear S to connect to non Touchwiz roms but oh well I'll just use it as a regular watch or maybe get an AW watch lol
Running CM13, what's different?
Hmmm extra features to be honest I like CM13 but it's so boring and as a guy that actually likes Touchwiz RR is nice because of the added customization!
So I've for RR installed. Few things I noticed right away: Built in ad-away, nice! Uses super-su. I personally have no issue with the built in root, but whatever. Other than that, it's very close to CM13 in terms of speed and look/feel.
Edit: One weird glitch I've run into on both this and CM13 is that the camera app gives and error "gallery has stopped working" when launched from the icon. If i used the double power button though, then the icon starts working. Any ideas?
Edit2 : It seems to be the default camera icon that is on the home screen in both ROMS. I noticed the graphic is slightly different from the dock as it is in the app window. Deleted bad icon and replaced with app windows one and it works fine. Probably an easy fix!
No glitches, no forced closes. Everything works, and works smooth. Very nice. My new daily driver.
Unlocked and loaded RR with OpenGApps..
No issues...running great!!
Thanks!!
Will try later, thanks haggertk for your work...
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
drewcu said:
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
Click to expand...
Click to collapse
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
tbclandot said:
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
Click to expand...
Click to collapse
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
drewcu said:
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
Click to expand...
Click to collapse
No idea on the speaker as I don't mess with it usually use headphones and I don't really use T backup but I don't see why you should have problems but you'll probably want to clean wipe when installing
drewcu
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
Not that i notice
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
6.01
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
Work great
4) Does Xposed work?
Yes
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
I advice to flash PB1 firmware no botloader
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
Yes, system, data, cache and dalvik, but dont restore system apps nor system settings
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
Dont know
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
At this time not yet
Every time I attempt to download, it fails after 55kb.....
amaury48 said:
Every time I attempt to download, it fails after 55kb.....
Click to expand...
Click to collapse
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
haggertk said:
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
Click to expand...
Click to collapse
Finally got it by switching browsers.....
Would one of you on RR be so kind as to send me the mixer_paths.xml (if that's what it's still called in MM) in your System > Etc folder (assuming folder structure is the same in MM also)? I would like to compare it to the surround sound modded file I installed in KK as per the following link: http://www.naldotech.com/enable-stereo-surround-sound-speakers-galaxy-s5. I am probably not technically capable of making the same thing possible in MM with the S5 front speaker, but it's entirely possible the same modded file I have will work in MM and it's possible a comparison will reveal only a few lines of code to modify that I could do.
Thanks in advance!
I modified some files for @LeeDroid rom for sprint support prior to sprints nougat ota and posted the download link in his thread but I'm not sure how often other sprint users check his thread being that sprint support wasn't available. If interested in testing to verify before the edits get fully implemented into the rom build please let me know if there are any issues.
***Thread has been updated for Sprint Oreo Support. This thread is for sprint users to report bugs with the sprint specific components of the ROM for me to troubleshoot to lessen the work on Lee since he isn't on the Sprint network. Also with new Sprint updates I will post test zips here because devices act differently and I want to be sure that the fixes/tests I build work for everyone.***
DISCLAIMER
I, nor any of the developers involved, are not liable for any damages that may occur to your device as a result of flashing. Flash at your own risk. I have this version running currently and have had no issues.
Big thanks to @LeeDroid for putting up with my pestering for sprint support and for challenging me to get it done
Thanks to @Captain_Throwback for file location guidance and for the use of his apktool when mine was being fussy, and for the use of his Sprint APNs.
Download Test 1 - Failed attempt, thanks to all who tested and let me know that it was broken. Don't use this one
https://www.androidfilehost.com/?fid=529152257862696764
MD5 6495ccb05ec3886306aad7dbc7088f28
Test 2 was never publicly released. I had multiple test 2's
Download Test 3 - Fresh out the oven. Clean flashed (format data in twrp) and booted, restored most of my settings over mobile data without having to edit any apns, didn't have statusbar clock for a little bit which was weird but it showed up, maybe it was taking a nap . Give it a try and let me know.
https://www.androidfilehost.com/?fid=673368273298925530
MD5 0a61e3fbdad51e4fa3d0ada511606f72
Install procedure
1. Clean start in twrp (full wipe)
2. Flash sprint test zip
3. In aroma select Sprint
This is where I edited the necessary files for sprint data to connect
4. Make selections in aroma for options as you normally would
5. Let install finish
6. Reboot
6.5 Don't worry about the boot animation, personally I prefer the stock Android so that's what it is
7. Wait
8. Wait
9. Profit? Hopefully
gstanke said:
I modified some files for @LeeDroid rom for sprint support prior to sprints nougat ota and posted the download link in his thread but I'm not sure how often other sprint users check his thread being that sprint support wasn't available. If interested in testing to verify before the edits get fully implemented into the rom build please let me know if there are any issues.
<c> <b> DISCLAIMER </b> </c>
I, not any of the developers involved, are not liable for any damages that may occur to your device as a result of flashing. Flash at your own risk. I have this version running currently and have had no issues.
Big thanks to @LeeDroid for putting up with my pestering for sprint support and for challenging me to get it done
Thanks to @Captain_Throwback for file location guidance and for the use of his apktool when mine was being fussy
Click to expand...
Click to collapse
Sprint user here. Will test soon as I get a chance.. what TWRP version is necessary? Does it matter what firmware I'm currently on? Thanks!
Lurien said:
Sprint user here. Will test soon as I get a chance.. what TWRP version is necessary? Does it matter what firmware I'm currently on? Thanks!
Click to expand...
Click to collapse
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
gstanke said:
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
Click to expand...
Click to collapse
Great! Thanks again..
gstanke said:
I haven't updated firmware to most recent yet since it was a security update I didn't feel the need and currently my twrp version is 3.0.2-6 I believe
Click to expand...
Click to collapse
Sprint here as well, I will test too, thanks!
GROOVYJOSHCLARK said:
Sprint here as well, I will test too, thanks!
Click to expand...
Click to collapse
Should flash fine and provide a working data connection
gstanke said:
Install procedure
1. Clean start in twrp (full wipe)
2. Flash sprint test zip
3. In aroma select <b> US UNLOCKED </b>
This is where I edited the necessary files for sprint data to connect
4. Make selections in aroma for options as you normally would
5. Let install finish
6. Reboot
6.5 Don't worry about the boot animation, personally I prefer the stock Android so that's what it is
7. Wait
8. Wait
9. Profit? Hopefully
Click to expand...
Click to collapse
dude!!! awesome!! ive been waiting and wishing ice or leedroid would support sprint with their N builds! trying this now
deakelem said:
dude!!! awesome!! ive been waiting and wishing ice or leedroid would support sprint with their N builds! trying this now
Click to expand...
Click to collapse
Any update? Hopefully everything is good to go
Sprint User Too
I'm a sprint user as well and have been waiting for something like this (impatient waiting for sprint upgrade) will test and post results.
JhoonB51 said:
I'm a sprint user as well and have been waiting for something like this (impatient waiting for sprint upgrade) will test and post results.
Click to expand...
Click to collapse
I finished the edits last night and so far have had no issues but since Lee doesn't have a sprint device for testing I figured this was the best way, if everything is good the edits will be merged into the main rom
I'll try it later but the download speed is poop. Says I have 5 days left. I'll try to download later.
gstanke said:
Any update? Hopefully everything is good to go
Click to expand...
Click to collapse
I flashed like the directions said but the phone sat at the "android" boot logo for at least 30 minutes before i restored a backup. I tried flashing a second time too with certain options not selected (such as using the stock kernel this time) and the same thing happened. should i wait longer?
deakelem said:
I flashed like the directions said but the phone sat at the "android" boot logo for at least 30 minutes before i restored a backup. I tried flashing a second time too with certain options not selected (such as using the stock kernel this time) and the same thing happened. should i wait longer?
Click to expand...
Click to collapse
I did not have that issue.
Try flashing, letting sit at Android screen again if it doesn't boot try dirty flashing over top
I had formatted data through twrp and run unencrypted
Also what selections did you choose? Mmfirmware? Root method?
gstanke said:
I did not have that issue.
Try flashing, letting sit at Android screen again if it doesn't boot try dirty flashing over top
I had formatted data through twrp and run unencrypted
Also what selections did you choose? Mmfirmware? Root method?
Click to expand...
Click to collapse
hmmm.. so i selected the MM firmware options but the only thing i did different from you was I selected encryption each time. I will try again while setting encryption to disabled.
deakelem said:
hmmm.. so i selected the MM firmware options but the only thing i did different from you was I selected encryption each time. I will try again while setting encryption to disabled.
Click to expand...
Click to collapse
Format data in twrp beforehand to be able to run unencrypted, which version of twrp are you using
gstanke said:
Format data in twrp beforehand to be able to run unencrypted, which version of twrp are you using
Click to expand...
Click to collapse
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
deakelem said:
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
Click to expand...
Click to collapse
same results after 30 mins. I even tried not selecting any options other than us unlocked and the stock kernel, and disabled encryption, still had the same result. It sits at the android logo during boot up for a while and will reboot once and sit there again. Anyone else seeing any problems like this?
deakelem said:
yup yup, did that already. just flashed and now its booting.
Update: just an update, it is still booting and is at the android logo, 15 mins so far. I will continue to wait another 30 mins or so
Click to expand...
Click to collapse
I am having the same results, stayed at android logo for well over an hour and would go no further. I chose mm firmware, run unencrypted (been unencrypted long time) twrp 3.0.3....went back to 2.71
XC/KUGO/F5321 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. No USB tethering
2. Wifi sometimes fails to turn on
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.1
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XC][O][8.1][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2018-01-14
Last Updated 2018-11-03
Awesome!! Thank you very much, I'll be trying this out immediately!
oshmoun said:
XC/KUGO/F5321 OmniROM BUILDS
OREO 8.1
Click to expand...
Click to collapse
So far so good. Using Magisk root, and Xposed beta, and micro g, and all working well. WiFi did disconnect once so far. Hopefully a fix coming... Thanks
@oshmoun - can you add option to switch nav buttons, or enable nav bar tuner? I can't get my apktool working on O, and no Gravitybox for O yet either...
levone1 said:
So far so good. Using Magisk root, and Xposed beta, and micro g, and all working well. WiFi did disconnect once so far. Hopefully a fix coming... Thanks
@oshmoun - can you add option to switch nav buttons, or enable nav bar tuner? I can't get my apktool working on O, and no Gravitybox for O yet either...
Click to expand...
Click to collapse
Try this: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
I can register new fingerprints, but i cant use them to unlock my phone or to login on apps.
I installed TWRP https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914, the OEM image and I'm testing OmniROM now, thanks for your work, where can I report bugs?
OmniROM work greatly on my device, I'm using since 14 Jan without any problem! Really Thanks!
coderex96 said:
I installed TWRP https://forum.xda-developers.com/x-...ecovery-twrp-3-1-1-xperia-x-compact-t3640914, the OEM image and I'm testing OmniROM now, thanks for your work, where can I report bugs?
Click to expand...
Click to collapse
Here only. With logs if possible.
farfetch said:
Try this: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Click to expand...
Click to collapse
Oh yeah, I actually have that in my downloads already. Forgot about it... Thanks
---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------
Lost mobile data today. At first boot, working fine, then installed AfWall and changed dns, and still working fine yesterday. Then this morning, no mobile data. Signal shows bars, but no 4g/lte, etc, and won't connect. Tried disabling and uninstalling tweaks and many reboots, but no change.
Update - now it's in and out...
levone1 said:
Oh yeah, I actually have that in my downloads already. Forgot about it... Thanks
---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------
Lost mobile data today. At first boot, working fine, then installed AfWall and changed dns, and still working fine yesterday. Then this morning, no mobile data. Signal shows bars, but no 4g/lte, etc, and won't connect. Tried disabling and uninstalling tweaks and many reboots, but no change.
Update - now it's in and out...
Click to expand...
Click to collapse
seems to be caused by installing afwall? could you please try without it?
oshmoun said:
seems to be caused by installing afwall? could you please try without it?
Click to expand...
Click to collapse
I am testing now. I haven't checked it enough to saying it's a rom issue; just wondering if anyone else has had it. It worked find with AfWall yesterday, but now in and out. I remember the same issue with AfWall on certain CM 12 roms...
oh man, thanks for making these ROMs, but the updater of 7.1 recommended this update and I just pressed install. Recovering from a brick now…
I'll come back to it later, when I have time for all the prerequisites.
OpenDelta
Nice work. OpenDelta advertised this update which I naturally installed without checking the requirements here. No requirements were stated before the update. Bricked my phone in a place where I couldn't do much about it. Just ask to please be more considerate since I more or less trust the update tool.
FYI: I dirty flashed from 7.1.2 via opendelta too. Once I flashed the oem partition using fastboot, the device booted again (only a handful of apps force closed and needed their data cleared to function properly again). Not the best choice to make this update available for installation with opendelta, no...
edit: forgot to mention I of course also had to update gapps to an 8.1 supporting version. I downloaded an unofficial pico opengapps from here
drstefankrank said:
oh man, thanks for making these ROMs, but the updater of 7.1 recommended this update and I just pressed install. Recovering from a brick now…
I'll come back to it later, when I have time for all the prerequisites.
Click to expand...
Click to collapse
cds0 said:
Nice work. OpenDelta advertised this update which I naturally installed without checking the requirements here. No requirements were stated before the update. Bricked my phone in a place where I couldn't do much about it. Just ask to please be more considerate since I more or less trust the update tool.
Click to expand...
Click to collapse
harryharryharry said:
FYI: I dirty flashed from 7.1.2 via opendelta too. Once I flashed the oem partition using fastboot, the device booted again (only a handful of apps force closed and needed their data cleared to function properly again). Not the best choice to make this update available for installation with opendelta, no...
Click to expand...
Click to collapse
Good to know flashing the odm image helps when updating from 7.1
About opendelta, i don't have much control over it to filter out the 8.1 build. It's all done automatically.
Besides, it did do its job well. It notified about the new version.
The requirement to flash a seperate ODM image is similar to how it's needed to flash a vendor image, and not just system and boot images, on Google devices. Guess that's new for Sony devices, hence this confusion.
@oshmoun - how about kcal support? Here's my tests with kppd - https://forum.xda-developers.com/showpost.php?p=75200267&postcount=64 (and forward)
@oshmoun: Yeah I was kind of surprised to see 8.1 was available through opendelta, and I didn't think it would work. So I backed up everything before upgrading. Which is probably what people should do before upgrading anyway
Flashing the oem partition was a relatively easy fix, so it's all good.
Thanks again for your great work! It's much appreciated as the number of custom roms for kugo is really slim pickings.
Latest stock ftf compatible is 34.3.A.0.252, right?
EDIT: It seems so. Flashed it and this build works great with it, so far.
I've performed a clean install after full wipe and also don't have mobile data working. Wi-Fi works, though.
Strange issue I have is the lack of sound over bluetooth ONLY in calls. Playing music/video works otherwise. It's quite baffling. This was working as expected on 7.1.
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631
wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.
Awesome work! I've finally got me a full featured daily driver
I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...
After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.
Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk
I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..
This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.
I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.
Any update?
pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.
won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.
Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.