Coming here for help since the LineageOS subreddit basically told me to **** off since the Note 5 build is unofficial, I hope you guys can help me out a bit more than them.
I just got a new TMobile Note 5 (SM-N920T) and wanted to get the latest CyanogenMod on it, so I went with the only builds of LineageOS I could find (I think the only two builds I found for the 920T came from here on XDA) I could never get the later June build to properly install, only the older March build, so I used that for a while until I ran into several bugs I was hoping to fix.
I looked more into the update and found my N920T was using an old bootloader (UVU4DQC2), and I needed to update it to one of two newer ones (UVU4EQE1 or UVUEQC6, I went with EQE1). The only way I could find to update it was flashing a newer stock ROM, so I did, got it set up real quick, checked the options and found I was indeed using the new bootloader. During this time, I had noticed my 4G LTE data was coming through just fine. After making sure I was on the new version, I put TWRP back on the device, wiped, flashed LineageOS June build (which succeeded), Open Gapps, and rebooted. After which during setup I found I could no longer access any mobile data connection at all.
I checked the usual suspects, APN was set up to properly use TMobile LTE, LTE was set as my preferred network, I reset data connection and enabled then disabled airplane mode, restarted and repeated the previous steps, to find I couldn't find any way to get the data working at all. I looked up online, but the only fixes I could find were to check the APN settings, reset them, and to reinstall root (which I tried to no avail).
After this I gave up on the June build and reinstalled the March build, which I found now also had the same problem. The only difference being that it was now using the EQE1 bootloader instead of the DQC2 version. Same fixes applied with the same results. I only could fix the issue by eventually rolling back to a backup of the March build with the DQC2 bootloader.
Probably the only thing I have left to try is installing the other accepted bootloader and seeing if that will work, but the other version I believe is for the universal/international build, not the TMobile build, so I'm not sure it will be any better. I like LineageOS and I want to keep it if I can, but at this point it's being a major pain to deal with with the bugs and no data on the bugfix build. I would appreciate any suggestions, let me know if there's any information you guys need to know.
I used the lineage port by Raymanfx for months. What you need to do is roll your baseband back in Odin (flash the firmware package) of the firmware T-mobile released in May. After flashing that, get TWRP back on your device and flash the June build by rayman.
Metabolic12 said:
I used the lineage port by Raymanfx for months. What you need to do is roll your baseband back in Odin (flash the firmware package) of the firmware T-mobile released in May. After flashing that, get TWRP back on your device and flash the June build by rayman.
Click to expand...
Click to collapse
If you're referring to the builds in this thread as posted by RaymanFX then those are the ones I'm currently using and having issues with.
That said, I'll still give it a shot. I found some stock builds on samsung-firmware here and it looks like the only TMobile specific releases are either well before may (N920TUVS4DPH2 August 2016), or a few months after (N920TUVU4EQE1 May 2017, the one I'm currently having issues with). I can alternatively try either of the two versions that were released specifically in March 2017 (N920TUVU4DQC2 the one I started with, and N920TUVU4EQC6 I think this is the other one that the June Lineage build supports, but it's not TMobile specific).
Which would you recommend? I'm thinking the EQC6.
I use updato.com no speed restrictions and the server never goes down.
N920TUVU4EQE1 is the firmware you want.
Metabolic12 said:
I used the lineage port by Raymanfx for months. What you need to do is roll your baseband back in Odin (flash the firmware package) of the firmware T-mobile released in May. After flashing that, get TWRP back on your device and flash the June build by rayman.
Click to expand...
Click to collapse
I went ahead and tried that with the EQC6 build only to get the same results as with the EQE1 build. Any suggestions? I feel like there must be something different I'm missing here.
Metabolic12 said:
I use updato.com no speed restrictions and the server never goes down.
N920TUVU4EQE1 is the firmware you want.
Click to expand...
Click to collapse
I'll give it a shot, but it'll have to wait until later tonight when I'm back home. I'm almost out of data for the month so I can't download it while at work.
Alright. If you have anymore problems just PM me or if you want some help.
MufinMcFlufin said:
I'll give it a shot, but it'll have to wait until later tonight when I'm back home. I'm almost out of data for the month so I can't download it while at work.
Click to expand...
Click to collapse
Metabolic12 said:
Alright. If you have anymore problems just PM me or if you want some help.
Click to expand...
Click to collapse
I went ahead and tried out the updato build, and I'm still running into the same issue, so I figured I'd try to list what I'm doing (in as much detail as I can manage) to make sure I'm doing everything as I should be.
1. I'm using ODIN 3.10.6 (can't find an official site that doesn't look sketchy, I just found my download link through a bunch of tutorials), TWRP 3.1.1-0 nobleltetmo, Open Gapps for ARM64 Android 7.1 Micro variant, and LineageOS June build as uploaded by RaymanFX here on XDA.
2. Download Updato UVU4EQE1 build, and extract file from archive.
3. Start up ODIN, click AP, and select file from the UVU4EQE1 archive, then wait the ~5 minutes for it to check the md5 hash, meanwhile doing step 4.
4. Turn off device and start it back up in download mode (Power + Home + Vol. Down), confirm the security check (Vol. Up), then plug device into computer.
5. After md5 finishes, click Start and wait for ODIN to install the stock ROM with UVU4EQE1.
6. Phone will restart into the newly installed stock ROM, go through first startup quickly to verify 4G LTE data is working and that you have the correct baseband (UVU4EQE1)
7. Shut down device and start it back up in download mode again.
8. In ODIN, click Reset, then AP, and select the TWRP img.tar (twrp-3.1.1-0-nobleltetmo.img.tar) file
9. Click Start, and be ready to restart device into Recovery mode (Power + Home + Vol. Up) once the screen turns off, as installing TWRP takes only a few seconds
10. Restart device into newly installed custom recovery (TWRP)
11. Move the LineageOS .zip file onto the device as well as the Open Gapps .zip.
12. In TWRP, select Wipe, and confirm.
13. Then in TWRP, select Install, choose your LineageOS .zip file, and confirm.
14. Go back to main menu of TWRP, select Install again, choose Open Gapps .zip file, and confirm.
15. Reboot into newly installed LineageOS June Build using Baseband UVU4EQE1, and begin first startup.
These are just about the exact steps I follow when trying to install LineageOS. Am I missing something I should be doing or otherwise doing something wrong?
If you have any experience with Win-Rar and Notepad++ you can open the updater script and change the supported bootloader's to the newest (EQG3) bootloader. That's what I did, but most don't have the experience with those programs. Using the newest baseband, you have the latest security features and better performance.
Metabolic12 said:
If you have any experience with Win-Rar and Notepad++ you can open the updater script and change the supported bootloader's to the newest (EQG3) bootloader. That's what I did, but most don't have the experience with those programs. Using the newest baseband, you have the latest security features and better performance.
Click to expand...
Click to collapse
I think I remember seeing how to do that a few days ago, will give it a shot.
If you have any questions just let me know bro
Metabolic12 said:
If you have any questions just let me know bro
Click to expand...
Click to collapse
Found the file just fine, went ahead and just replaced EQC6 with EQG3. I flashed the EQG3 build, but ran into some very odd behavior upon booting. I got the usual Note 5 screen, Samsung, and TMobile screens (TMobile stuck around for a long while as usual), but after TMobile, I got a black screen, then a notification that System UI app has crashed, and I was stuck on a black screen after hitting Ok. I could hit the power button and I'd get the usual stock "Shut down/Restart" options, so I went ahead and tried that so I could try the LineageOS flash regardless of that odd behavior, but I ran into an error with "Invalid ZIP format". I'm gonna guess that 7zip inserted itself another signature file to say "This archive was made with 7zip!" which made the phone act weird. Gonna try a few other things with that LineageOS zip.
I had that same problem. Download Win-Rar and get the free trial. Repack the files into .zip format and you should be good to go. The problem you had with flashing the firmware in Odin is you have to NandErase All, which wipes everything, and turn off auto-reboot. Most people don't know you have to manually boot the phone into recovery twice after using Odin and flashing a firmware.
I found the issue was actually because I accidentally put the folder all the files were in into the archive, so it was .zip/folder/meta-inf, etc. so once I moved everything from the folder to the root archive, it worked just fine. Besides that, not sure exactly what you mean by booting the phone into recovery twice. I've been doing download mode twice (one for stock rom, second for TWRP), but I've only ever been doing recovery once (install LineageOS, Open Gapps, then reboot to system). The only time I ever tend to boot twice into recovery is when I'm reinstalling root after the initial startup.
Metabolic12 said:
Most people don't know you have to manually boot the phone into recovery twice after using Odin and flashing a firmware.
Click to expand...
Click to collapse
So what are the two times you have to manually boot into recovery after Odin? I can only think of one time during the process it's necessary to boot into recovery, when installing LineageOS then Open Gapps.
I meant only when flashing back to stock.
MufinMcFlufin said:
So what are the two times you have to manually boot into recovery after Odin? I can only think of one time during the process it's necessary to boot into recovery, when installing LineageOS then Open Gapps.
Click to expand...
Click to collapse
So I went ahead and tried flashing the EQG3 ROM, using the NAND Erase setting, and for some reason it fails to boot now. I gave it a solid 10 minutes to try and it's stuck on the T-Mobile logo screen. So after giving that enough time, I went ahead and tried putting TWRP back on so I could revert to a backup, and for some reason TWRP now fails to mount internal storage so I can't put the backup file back on the device. I tried several other builds of the stock ROM and all builds appear to fail to boot. Do you have any suggestions? The only things I can find online are saying to factory reset, which doesn't appear to make a difference, since this is failing on its startup boot, not after an update.
Don't know what the issue was exactly, but I somehow fixed it. I tried several options for wiping data on TWRP and eventually found that for some reason "Format Data" right next to "Advanced Wipe" worked. Reflashed TWRP and finally have access to internal storage again. Now I'm back to the old issue of no data on the June LineageOS build once again even with the EQG3 baseband.
Related
Hey guys, I just got my Note Pro a week ago and just started looking into rooting. I keep getting a notification about a 128mb stability update. I would assume it's gonna update to the latest build but I'm not sure what the latest build is or if it'll be rootable afterwords. my current build is KOT49H.P900UEU1ANAE. What is the latest build #? Is there a list of updates somewhere detailing what the improvements are? I just want to root, debloat, turn off OTA and remove KNOX.
Edit: sorry forgot to mention it's just the wife model SM-P900
So 48 views and not one person can tell me the latest build# ? I'll figure out the rest.
Sent from my SM-N900V using Tapatalk
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
muzzy996 said:
Have you checked SamMobile?
http://www.sammobile.com/firmwares/database/SM-P900/XAR/
How i got there:
http://www.sammobile.com
1. Click Firmware on the top.
2. Click the greyed out firmware database link under the blue banner.
3. Under "Select your firmware" I picked Tablet-->Android-->SM-P900....-->Cellular South (which matches the US variants)
Click to expand...
Click to collapse
Thanks muzzy! I had already been to SamMobile but all it had was foreign countries listed. I didn't know about Cellular South being the US version. I'll look again.
Edit: oh look a list of the updates and release dates! My Wi - fi reception seems slow, do any of the update fix that?
I honestly can't say. I'm on NC5 which is dated back in April and have no major issues.
I'm rooted and debloated though, not that this would impact the wifi performance . .
48 views doesn't mean 48 users. About 44 of those are Google Content Crawler, which is Google search engine's bots crawling the net for content to display in google.com. It is an automated process.
Samsung doesn't release changelists, so we don't know what each update does beyond what we can see.
Thanks for the help guys! I just accepted the first update and it took me to ANC5. I guess I'll have to accept all updates until current and then try CF-Auto-Root. I'll report back then.
Actually I just got my tablet like a week ago as well. I m on the same build no as well....haven't updated yet. I also haven't installed Knox either. There is a download arrow on the Knox icon and if I click the icon it starts downloading so I just cancel it. I am thinking of rooting as well. Well what I m trying to say is...keep the thread updated and I will just follow your lead.....hehe.
It always helps to know your country as well as different countries are on slightly different versions. You can always go to sanmobile.com, click on firmware and search for p-900. That will give you the list of all the latest ROMs for different countries / carriers. US based ROMs are listed as "Cellular South".
Successful Root!
Okay guys sorry it's taken so long to respond, I had hernia surgery on Monday so I've been behind on getting this rooted.
My plan was to use CF-Auto-Root and then load TWRP recovery and then load "Debloat Stock Variant" by Gatsrom. I decided to do it in that order because I wasn't sure I could load a custom recovery without being rooted first.
I accepted all updates up to the current = P900UEU1BNK1. Using Win 7 and loaded Samsung drivers. Downloaded ODIN 3.09, Odin 3.07 came with CF-Auto-Root and downloaded TWRP. Booted into download mode and made sure ODIN recognized my P900. And this is when to fun began! Everything seem to be going okay but I did run into a snag. I used ODIN 3.07 because that's what came with Auto- Root and I'd read somewhere of people having trouble with 3.09??? Anyways I got a red "FAIL" message and my screen displayed multicolored lines. I tried running it in ODIN 3.09 and got the same result. (i didn't disconnect anything between the 3.07 or 3.09 attempts, maybe i should have?). I disconnected my P900 and it rebooted giving me a Firmware Error screen telling me to use Kies "Recovery Mode". I tried Kies Recovery but Kies3 wouldn't even recognize the P900. (I started freaking a little at this point!) Anyways, I decided to try and load TWRP because I thought I've got nothing to lose! I loaded TWRP into ODIN and it took, so I thought, because my P900 rebooted into an up and running normal state. (Big Sigh!) I tried booting into recovery but TWRP didn't take, it came up to stock recovery, trying to load TWRP just kicked the P900 out of the Firmware Error state it was in?? I decided to give Auto-Root another go after rebooting Win 7. Used ODIN 3.09 this time and everything went fine and I was rooted! Then I loaded TWRP and it loaded fine! I performed a TWRP backup at this point and things seem to be running smoothly. I still need to load the Debloat Variant, that's what's on my plate for today.
http://forum.xda-developers.com/showthread.php?t=2656551
http://forum.xda-developers.com/showthread.php?t=2706982
http://forum.xda-developers.com/gal...t/rom-original-stock-debloated-stock-t2860069
You are a much braver sole than I. Hope all goes smoothly.
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
treetopsranch said:
You are a much braver sole than I. Hope all goes smoothly.
Click to expand...
Click to collapse
I'm not that brave treetop! I just know my way around a computer and I've rooted a few of these things. Plus I know the guys here on XDA are good at helping out if you hit a snag. Luckily I figured this one out on my own! You've just gotta do your research before jumping in and search read, search read, search read! I provided some links to get you started....get to it!
muzzy99 said:
I could be wrong but I would think that if one is going to a different ROM then rooting isn't necessary. Simply use Odin to flash TWRP but ensure that auto reboot is not enabled in Odin when you do it. If you allow the device to begin booting into stock system it's going to overwrite recovery again (with stock recovery) so what you want to do is flash TWRP, and once it's flashed FORCE a reboot directly into recovery again using the hardware keys on the device. At that point you can do an nandroid backup and then flash your ROM.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Thanks for the info muzzy, I'll remember that for next time! :good:
I did get the Debloat Variant up and running and loaded Xposed framework with sdcard full access. Everything seems to be running smoothly!
Ok So I finally got to it and successfully rooted (in first try, if I may add ). Thanks to xblue's guide/heroic efforts I avoided certain things and everything went smoothly. So Basically I installed samsung drivers using Kies, rebooted pc (Win 8.1). Downloaded cf autoroot and downloaded odin 3.09 as autoroot comes with 3.07. Replaced ONLY 3.07 odin exe with 3.09. Started Odin in Admin mode, put the tablet in download mode. Attched to pc and Odin recognized it. Then Gave it a final thought......lol. Pressed Start, device booted couple times. Then PASS appeared on the Odin window after like 30 secs. Installed root checker...successfully rooted. Installed TWRP via odin and flashed that successfully. Made a full back up and installed a ROM of my choice. I am a happy camper.
Sweet Deal singhsta! I'm glad my efforts were a help!
i would update to the latest version.. i tried using the original one that you have however i got the screen flicker issue so had to update.. the first update isnt very good wifi keeps dropping but the most recent version doesn't tho you may have a bug where every time you unlock the screen the tablet is still asleep even though the icons are visible so you have to lock the screen again and unlock. however if you factory reset this bug goes away.
i find the latest version is the most stable and battery life is better if you disable all the unnecessary apps that you can i usually get rid of most of the samsung back up apps and all the google ones bar the ones it needs to run play store etc and maintaining the ones that sync for back up.
wifi was really slow when i first got it and would drop very annoying but now it seems better but have experienced slow wifi i think it's a hardware issue all note pro's have in built that should have been sorted by the latest build. i hope they finally give it an update in the coming months even to 4.4.4. or something.
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
1. Join the G+ community using the same Google account as you're using for Play on your phone/tablet Here.
2. Sign up to receive the BETA versions from Play Here.
- Use the link provided after sign-up to download the app.
**Notice!** In light of the OE1 ota update these ROM's are no longer safe. Stay tuned for a new Keep Root thread!
***FlashFire v19 Recommended***
Download:
- G900V_OD5_Stock_Rooted_ROM
- G900V_OD5_Stock_Deodexed_ROM
Set your screen timeout to 10mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and use default "Reboot" setting.
6. Last, press the lightning bolt then "Ok" to begin the flash .
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the Verizon splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
- When reporting an issue please always include your starting firmware, FF version, ROM version flashed, and relevant details. Should the flash fail please review FF's last log for errors and include info in your post.
Optional (Flash using FlashFire's "Flash zip or ota" option):
- G900V_OD5_TetherAddOn
- G900V_OD5_Write_to_SDCard
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, Stock Recovery, and Bootloader to OD5.
3. No need to wipe prior to flashing, the ROM will automatically perform a factory data reset.
4. If you do not already have root access (or to unbrick) you must flash the G900VVRU1ANCG_Full_Odin.tar (flash in Odin's PDA slot(AP in Odin v3.09+)), root with Towelroot (this version does not require internet access), then proceed with the above process.
5. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@Dudash - for the system.img used in the ROM and testing.
Good Day family & Friends of XDA. I hope we all have fun here today learning new things together:angel:
I can't seem to get either ROM to flash.. No matter what I do, it gets to "Flashing System" in FF and then the phone just turns off. I've tried factory reset, going back to NCG, trying to flash from your other ROMs, etc and no matter what, the phone just turns off at "Flashing System" and then it will only boot into download mode.
I can't tell if it's a FF or a ROM problem. Maybe you could make a version that can flash in Safestrap like your OA8 ROM.
I'm gonna keep trying tho.
EDIT: Okay so I finally got it to finish the flash process and then it hung on the "Samsung Galaxy S5" splash screen for like 10min before finally going to the Verizon boot animation. I'll edit this with an update if/when it gets past the boot animation.
EDIT 2: 30min and counting at the boot animation. lol. Has anyone gotten the ROM to flash and load up successfully?
Dudash said:
I can't seem to get either ROM to flash.. No matter what I do, it gets to "Flashing System" in FF and then the phone just turns off. I've tried factory reset, going back to NCG, trying to flash from your other ROMs, etc and no matter what, the phone just turns off at "Flashing System" and then it will only boot into download mode.
I can't tell if it's a FF or a ROM problem. Maybe you could make a version that can flash in Safestrap like your OA8 ROM.
I'm gonna keep trying tho.
EDIT: Okay so I finally got it to finish the flash process and then it hung on the "Samsung Galaxy S5" splash screen for like 10min before finally going to the Verizon boot animation. I'll edit this with an update if/when it gets past the boot animation. lol.
Click to expand...
Click to collapse
Screen timeout set at 10mins?
muniz_ri said:
Screen timeout set at 10mins?
Click to expand...
Click to collapse
Yep.
Dudash said:
Yep.
Click to expand...
Click to collapse
I am seeing this symptom across many devices but fortunately not often. It's definately a problem with FF.
muniz_ri said:
I am seeing this symptom across many devices but fortunately not often. It's definately a problem with FF.
Click to expand...
Click to collapse
What's weird is I've never had this problem with FF and I've flashed your ROMs multiple times in the past on multiple devices. It's just odd that it started happening with this new update.
Dudash said:
What's weird is I've never had this problem with FF and I've flashed your ROMs multiple times in the past on multiple devices. It's just odd that it started happening with this new update.
Click to expand...
Click to collapse
I see we have several dozen downloads and only one reported failure. I would be interested to hear if others are having the same issue.
That's why I asked earlier in the thread if anyone had successfully installed and had it load up all the way.
I too have had the same issues as Dudash. I tried 3 times last night using FF and every time, ended up stuck on the Samsung screen.
wccann said:
I too have had the same issues as Dudash. I tried 3 times last night using FF and every time, ended up stuck on the Samsung screen.
Click to expand...
Click to collapse
Whew. Glad I'm not the only one..
And thank you for using your first post to let me know I'm not losing my mind. lol
ive been lurking around these forums for years, and it took me this long to post! i usually wait until i see confirmation of new updates properly working prior to updating my device, but was feeling adventurous last night.. didnt work out so well for me.
wccann said:
ive been lurking around these forums for years, and it took me this long to post! i usually wait until i see confirmation of new updates properly working prior to updating my device, but was feeling adventurous last night.. didnt work out so well for me.
Click to expand...
Click to collapse
Stand by everyone....
What's new in OD5? (Assuming it just came out.)
Actually even if you use safestrap youll get stuck on the samsung logo despite me coming from NCG. Also i did flash 0C4 firmware and i was still unable to move forward, maybe you compiled the rom badly
MuminMohamed said:
Actually even if you use safestrap youll get stuck on the samsung logo despite me coming from NCG. Also i did flash 0C4 firmware and i was still unable to move forward, maybe you compiled the rom badly
Click to expand...
Click to collapse
I believe its the updater script and should be a quick fix. Will upload new versions later tonight.
is there a method of flashing this over oc4 without having to do a full flash and factory wipe?
packetjunkie said:
is there a method of flashing this over oc4 without having to do a full flash and factory wipe?
Click to expand...
Click to collapse
I'd recommend waiting until he uploads new versions of the ROMs later tonight and as far as the factory wipe goes, the ROM does it for you but you can back up your data with FF before doing the flash and then restore it afterwards.
Download:
- G900V_OD5_Stock_Rooted_ROM
- G900V_OD5_Stock_DeOdexed_ROM
Click to expand...
Click to collapse
Er... these aren't linked to anything. At least that's what happens to me. YMMV.
RBEmerson said:
Er... these aren't linked to anything. At least that's what happens to me. YMMV.
Click to expand...
Click to collapse
That's because something was wrong with them and they wouldn't install correctly.
I was hoping he would remove the links so people wouldn't download and try to use them and end up like those of us that tried. lol.
He said he'll be uploading new ones later tonight.
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
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
Latest release
Built from whoshotjr2006/touchpro's sources with minimal changes. All credit to original devs.
I'm not going to commit to regular updates but I'll try to do occasional ones.
Recommend using this TWRP (also stolen from touchpro).
Installation:
Enable developer options in stock ROM (tap build number a bunch of times)
Enable 'Advanced Restart' in developer options
Hold power button, select restart, restart to bootloader
Use fastboot to unlock bootloader
Use fastboot to flash TWRP recovery
Reboot to recovery using fastboot command
Wipe everything in TWRP, format data, and factory reset
Push ROM to /sdcard/ and install
Optionally push Gapps and/or LineageSU and install
Boot and enjoy (first start might take a while)
Tested on a T-Mobile LG G Stylo, all seems well.
As far as I can tell, everything is working fine. You should be able to dirty flash if you are using another Lineage 14.1 build but I haven't tested it.
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
ItzBluestone said:
It's awesome to see others making roms for this device again, but do you think you will be able to make a oreo rom though? ?
Click to expand...
Click to collapse
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
jsheradin said:
The LOS14 tree is still getting security updates and will run a lot faster than LOS16. I could build an Oreo ROM but there's little chance of finding the vendor FW needed to get camera, bluetooth, etc working properly.
Click to expand...
Click to collapse
oh, well that's unfortunate...
So what is different? Just security updates?
This ROM breathed new life into my old MetroPC version of this phone (2GB/16GB)!
I bought this phone two years ago refurbished and carrier-unlocked (other than banned on MPC) off Amazon. Looked brand new. I just installed a new battery last month. Original battery wore out.
ROM works beautifully. Nice to be free of the factory cruft. Also, the TWRP from your OP works much better than the one I had been running. (Neither TWRP reads the current time/date through.)
I had been rooted with SuperSU, now I'm rooted with Magisk. I flashed mini Gapps 7.1.
I have not tested NFC yet.
Thank you for this ROM and your post!
My TMo h631 will not take the image. During the install it will kernel panic and throw an error.
I do factory reset, wipes, formats but still no go.
Anyone knows how I can fix it?
Will this work fine on the LGM631?