Database Info

[Q] Samsung Tab 2 10.1 GT-P5113 CM10.2 to CM10.2 Update

I need a real and very specific answer here please that is for my specific device only. I will tag this post properly.
My Device: Samsung Galaxy Tab 2 10.1 WiFi, GT-P5113. Screenshots attached.
I need advice on getting my Tablet updated from CyanogenMod 10.1 to 10.2. Yes there are lots of entries here about this issue, but they are flooded with all sorts of different devices, 60 or more pages, little of it is for my specific device. I have ClockworkMod Rom Manager installed, tried to update manually to the cm-10.2-20131207-NIGHTLY-p5100.zip and gapps-jb-20130813-signed.zip. Booting to recovery gives me the option to flash a zip file, I choose the cm-10.2 zip. This is not like Safe Strap where I can also choose the gapps. When I tried to flash the zip, I get a system 7 error, no update.
In Settings/About Device is the update section, and the same cd10.2 update is available. But it tells me it will put me into manual mode, I see no way to update the gapps, so I give up. I did this same update with my Droid Razr Maxx and it did work, had to change the Settings, More, Mobile Networks, Network Mode, and choose CDMA + LTE/EvDo to get my phone back, but it worked. I wanted to try to update by Settings, but ended up in Safe Strap, so I choose the ROM zip and added the gapps zip. I cleared the caches and did a factory reset, and it worked, but I had to setup the entire thing all over again, huge PITA! Now, in this forum somewhere, instructions say to flash the rom and gapps, did not say factory reset was necessary. Anyway, it is done on the phone, took a while to setup, switched back and forth from stock to 10.2 until I was comfortable enough with 10.2 to run it all the time.
But this Samsung GT-P5113 is a totally different animal. I wade my way through 60 pages of posts, finding out that some stuff does not work, but the worst thing is that root is gone! Losing root here for me would be a disaster, I have no way of restoring it in CM10.2 that I know of.
Has anyone actually updated a Samsung Tab 2 10.1 to CM10.2 successfully? How did you do it? Method and apps please? Links appreciated. Will I lose root? Must I factory reset or can I update and keep my accounts?
Somebody please address this very one specific device to make it perfectly clear for those of us that have it, have root, moderate experience, and need/want to get this done. Since the GT-P5113 is the same for Gt-P5100, this thread will cover the entire GT-P51xx line. Somebody please help so I can get this done without wrecking or bricking my device. I love Linux and use it often to root or update my phone, at least I do not need drivers for Windows but will accept whatever you can offer with gratitude. Thank you guys!
...well, it looks like the screenshots did not upload or at least do not work for me, have to give images in post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

problem with rooting gtp5113
dear ohmster, I need help desperately the problems I encountered rooting gtp5113. I know it is not reply to your post but I think you can help me to
resolve the problem.

chongfl said:
dear ohmster, I need help desperately the problems I encountered rooting gtp5113. I know it is not reply to your post but I think you can help me to
resolve the problem.
Click to expand...
Click to collapse
chongfl,
What exactly do you need, buddy? My tablet is now running on CyanogenMod ROM 10.2 so I did get it to work and it is real nice. There is an option in ClockworkMod ROM Manager under "Recovery Setup" to choose CWM ROM Manager (Which does not work for this update.) OR TWRP. I selected TWRP over CWM ROM Manager and I was able to perform the update. Then go back with CWM and install the gapps package. I like it and it worked for me.
But if you want help, you have to be very specific as to what your issue is, what make/model device, and what you have or have not done and what happened. Otherwise myself or anyone else cannot help you unless we know what your issue is.
Oh wait a minute, your post title says lost root. So what happened, you updated, got the update done, and now do not have root anymore? Are you sure? You can look for the su binary, superuser app, busybox file, or if you want to make it real easy, go to the Play Store and download a "Root Checker". This free app will tell you if the phone is rooted or not. I think there are many versions of root checker,. but here is Root Checker at the Play Store.
Use an app like that to find out if you really lost root or just cannot find it. And then tell us what you found, what you need, make and model of the device, version of Android you are running. (I have 4.3.1 now and have to update my signature.), and what ROM you installed. Okay?
If my post helps you in any way, please click the big "Thanks" button under my name on the left.

Same question
Hey there just saw your post and I just successfully rooted my wife's Tab 2 10.1 P5113 with clockwork mod recovery and the CM10.1 for android 4.2.2 like yourself. I now want to put CM10.2 for Android 4.3 on it but cannot find the correct zip file anywhere. What did you do? where did you go to get it? I think I'm missing something.... I'm very tech savvy but new to rooting so any info would be appreciated!

johnf84 said:
Hey there just saw your post and I just successfully rooted my wife's Tab 2 10.1 P5113 with clockwork mod recovery and the CM10.1 for android 4.2.2 like yourself. I now want to put CM10.2 for Android 4.3 on it but cannot find the correct zip file anywhere. What did you do? where did you go to get it? I think I'm missing something.... I'm very tech savvy but new to rooting so any info would be appreciated!
Click to expand...
Click to collapse
What say John.
You said you have the GT-P5113! Okay, so you have to use the GT-P5110 file. Now I can help. Gee, I have been spending all my time on the phone with CM11 because it is really exciting and "a whole new world on an entirely new level". I might update my tablet with you since it has been a while and there might be a later package for me. I will then go to CM11.
Here is a quote from the instructions page for your ROMS (Click this line to visit page.).
"As the IR blaster is not supported in CyanogenMod for the P5113, it is essentially a P5110 as far as CM is concerned. Therefore, if you own a P5113, please use the p5110 CM builds for flashing."
You know, I have spent all my time updating CM10.2 tp CM11 on my phone that I haven't updated the tablet yet. Kind of a dumb thing, the phone is important for communication and I got a monthly bill with it. So it would have made MUCH more sense to update the Tablet first, then do the phone. But I stubled on a really active thread, over 150 posts, about my phone, the update to CM11, that I read it and got interested. Plus, I was watching for updates to CM10.2 and when I saw there was an update and I got excited, ready to go, until....
...I saw the "update" was not to another CM10.2, but to CM11. Now THAT is a totally different animal. I have been ROMing and doing computers long enough to know a major version change means BIG update and usually means "Clean Install". I stopped dead in my tracks to read up first.Good thing too, because there were not very many updates for 10.2, only a few, never "stable" and then they went directly to CM11. Since CM10.1 and CM10.2 were both Jellybean versions, CyanogenMod did not waste a lot of time on CM10.2. I count 5 updates for CM10.2 and no more. Because Jellybean is "old school", CM11 is Kit Kat and totally different. A LOT different. Matter of fact, I cannot find anymore CM10.2 files on the CM website. They dropped it for CM11. 10.1 & 10.2 were mostly the same anyway, not much of a difference, CM10.2 developing to stable did not seem worthwhile anymore because Android is now taking a different direction and a very welcome one. Very slick, very smooth, totally different and agressive memory management. No more 20-30 apps running all the time, fighting for that precious memory. CM11 puts things to sleep pretty quick when they are not used, there are kernel modules now in something called the Xposed Framework, LOTS of them that let you customize the entire system, how it works, overclocking, almost anything you want.
Check for yourself, here are the pages for the GT-P5110, they do not make a rom for GT-P5113 because they are essentially the same but for the IR blaster so you can use it for a remote to control your TV or something like that.
Instructions Page
Download Page
This quote explains the difference between the two models and why they do not make a special rom for the GT-P5113.
"As the IR blaster is not supported in CyanogenMod for the P5113, it is essentially a P5110 as far as CM is concerned. Therefore, if you own a P5113, please use the p5110 CM builds for flashing."
There are no CM10.2 updates anymore. They dropped it. I have 5 on my device but the updates were easy because they were not a big deal, it was pretty much the same thing. Nothing special for updating. So, for you, the next big update would be CM11 and you take the very latest one they have, get the right gapps, and there is a special kernel called the "JBX" kernel you can apply that will allow all sorts of upgrades to the core of the system like tweak memory, CPU speed, sleep, battery use, governors for the CPU, color balance for the screen.
You need to find the right thread to read and follow to upgrade the GT-P5113 to CM11, read it, take notes, save pages that are guides, ask questions, and READ. Then gather your stuff and get ready to try. You will need a different Recovery Environment to install with too, like TWRP instead of CWM. Because you have to flash not only the rom, but the gapps as well and if you choose, and you should, the jbx kernel with it. ClockworkMod does not do "multiple zips", at least I don't think it does. I had to change inside of CWM to TWPR recovery mode just to get my last updates done.
Alright I found it. This is where we have to move the discussion to. Since you cannot update to CM10.2 because it is no longer supported and was dropped, you move on to CM11. You need the instruction page, with downloads, shows you where to get the files, the recovery tools you can use, plus 49 pages of discussion about it. They give a list of recovery tools, CWM is listed but "CWM 6.0.4.4 or newer (or recoverys based on it" is the only one supported. If I were you and I will be you shortly, I would probably use TWRP. I am using in on my phone in Safe Strap and it gives 6 slots to install roms into, a LOT of features, backups, restores, wipes, and can install more than one zip at a time.
Here is the page you want:
[ROM][P51xx][4.4.2]CyanogenMod 11 (CM11)
Since I have spent all my time updating the phone to CM11, I have not worked on the tablet yet nor picked a recovery yet. I will probably use TWRP, this one.
TWRP 2.6 - Samsung Galaxy Tab 2 10.1 (p5100 or p5110)
It is a LOT different than ClockworkMod Rom Manager and it is nice. Here is a whole page of recoveries you can use for this on XDA.
Now read, read, ask questions, and READ.
You can get the jump on me if you want, I already bookmarked the page and will be doing my tablet soon. Don't take this lightly and spend a week or two reading, asking questions, googling on Kit Kat, and get ready for this. I can tell you it is super cool and WAY worth it. At first you will be overwhelmed when you install the right stuff and all the things you can configure. But it will become clear and this is the best, BY FAR!
You have to really read up on this. The Droid Razr has over 150 pages in the thread so a LOT of people have done it and got over the bugs and are finally enjoying it in all of it's glory. Not sure how far along the Samsung Tablet is with Kit Kat so reading up is a must. You are not missing anything with CM10.2, it is only CM10.1, warmed over with a little extra icing on the same cupcake. CM11 is a serious upgrade.
If you want to see what I have been doing with my Droid Razr Phone, plus learn A LOT about CM11, how it works, what was/is wrong with it, how it is now, read this thread. It is over 225 pages already!
Okay man, I will see you over on the CM11 tablet page. If you found this post helpful, please click the Thanks button. See you on the other side, John! :good:

I Think I Might Have Ruined My Moto G...

Hey, everyone. This is probably going to be pretty long-winded. I do apologize, but also ask that you read carefully and thoroughly before posting.
Pertinent Information:
Model: XT1032
Carrier: Consumer Cellular
Background Information:
A long while back I decided to root my phone so I could remove all of the useless applications I never used that just ate up what limited space this phone has. Everything went successfully.
A couple (or maybe a few) months ago I noticed that Android 5.1 was available for install. I wasn't aware that you needed to remove root access before doing an OTA update, and proceeded to brick my phone. I then followed a guide (http://forum.xda-developers.com/showthread.php?t=2700502) to flash back to stock firmware, thus removing root access, and afterwards, applied the OTA update successfully.
What I didn't notice was that the guide was for the XT1033, but, the phone still worked just fine. I could make / send and receive calls / texts, use my WiFi, etc. The only issues were that my data didn't seem to work at all, and my phone's internal memory was about 80% full, and only ~500MB of that was from my downloaded applications... Weird, right?
New Information:
Today I decided I was going to do a factory reset. I was no longer able to update or download applications because the Google Play Store would stop responding every single time. Also, I was sick of my phone's memory being so full, for seemingly no reason. Well, the factory reset failed to complete, and left my phone bricked; it wouldn't go past the unlocked bootloader warning screen.
I then did some research and fiddling around with a new guide (http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847). After following the instructions, which I found to be quite confusing, actually), I ended up back on Android 4.4.4, with a non-functional network. I used the XT1032 US GSM modem he linked in Step 6, since my phone's from the US, but maybe it was the wrong one? I also tried some different modems / radios from the linked posts in that part of the guide, but they didn't work either.
So, I followed a new guide for installing Lollipop 5.1 GPE via a 1-click batch file (http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522), and it seemed to work... Except my network no longer worked; the phone wasn't recognizing my SIM card. I tried downloading and installing a couple of different US XT1032 modems / radios to no avail.
Next, I took a shot in the dark and flashed back to the Android 5.0.2 XT1033 firmware from before, and now, it works fine... Kind of. The network functions again like it it did before, and the memory is pretty much empty (4.61GB of 5.55GB free) as it should be. The only problem is that the Android 5.1 OTA update has failed twice now, and the phone's not rooted again yet.
My Questions:
1) Why is my network functioning on an XT1033 firmware when my phone's an XT1032, yet on an XT1032 firmware it doesn't function?
2) Why can I suddenly not do the Android 5.1 OTA update like I could before?
3) Why did the Lollipop 5.1 GPE 1-click method leave me with a non-functioning network?
4) Why was my memory so full the last time I installed the Android 5.0.2 XT1033 firmware, yet now it's empty like it should be?
I'm beyond confused right now, and trying very, very hard not to throw my phone into the lake (which I can from the window right in front of me). I just want to use the latest version of Android, NOT have my phone's memory be ridiculously full, and have a functional network.

Have you tried installing CyanogenMod? https://download.cyanogenmod.org/?type=nightly&device=falcon you're going to need a custom recovery I use twrp https://dl.twrp.me/xt1032/
Also need a GApps package I use the Micro Modular Package http://forum.xda-developers.com/android/software/tk-gapps-t3116347

TheMatthew562 said:
Have you tried installing CyanogenMod?
Click to expand...
Click to collapse
No, I've never tried CyanogenMod. It seems complicated, what with the nightly updates and what not.

DrumsXO said:
No, I've never tried CyanogenMod. It seems complicated, what with the nightly updates and what not.
Click to expand...
Click to collapse
It's actually really simple and CyanogenMod now provides updates from within the phone really easy to update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

TheMatthew562 said:
It's actually really simple and CyanogenMod now provides updates from within the phone really easy to update
Click to expand...
Click to collapse
I'll consider looking into it, but I'd still like to, at the very least, get the answers to my questions regarding what the hell is going on with my phone right now...

Okay, what the hell...
I just installed the latest CyanogenMod 12.1 Nightly, along with the latest GApps 5.1.1 Micro Modular Package, and I have no service!

DrumsXO said:
Okay, what the hell...
I just installed the latest CyanogenMod 12.1 Nightly, along with the latest GApps 5.1.1 Micro Modular Package, and I have no service!
Click to expand...
Click to collapse
You could try to
Code:
fastboot erase modemst1
fastboot erase modemst2
after flashing a XT1032 Baseband

k-kuchen said:
You could try to
Code:
fastboot erase modemst1
fastboot erase modemst2
after flashing a XT1032 Baseband
Click to expand...
Click to collapse
Do you happen to have a link to such a Baseband? Because I don't know too much about this stuff.
Is the Baseband the NON-HLOS.bin and/or fsg.mbn file(s)? If so, I have a couple of XT1032 firmwares of various Android versions; can I use one of them?

WHOA! I HAVE SERVICE!
On a whim, I decided to try flashing an XT1032 Baseband based on what I thought the files were, and it worked!
What I Did:
1) Flashed NON-HLOS.bin and fsg.mbn from a US_Retail_XT1032_KXB21.14-L1.32_CFC.xml.zip file I have.
2) Fastboot erased modemst1 and modemst2, then rebooted; voila!
I wasn't sure or not if those were the Baseband files, but I figured I couldn't make things any worse, lol.
EDIT: I'm still on the latest version of CyanogenMod at the moment, which also has the latest version of Lollipop.

DrumsXO said:
WHOA! I HAVE SERVICE!
On a whim, I decided to try flashing an XT1032 Baseband based on what I thought the files were, and it worked!
What I Did:
1) Flashed NON-HLOS.bin and fsg.mbn from a US_Retail_XT1032_KXB21.14-L1.32_CFC.xml.zip file I have.
2) Fastboot erased modemst1 and modemst2, then rebooted; voila!
I wasn't sure or not if those were the Baseband files, but I figured I couldn't make things any worse, lol.
EDIT: I'm still on the latest version of CyanogenMod at the moment, which also has the latest version of Lollipop.
Click to expand...
Click to collapse
Yes, that's what I meant :good:

k-kuchen said:
Yes, that's what I meant :good:
Click to expand...
Click to collapse
Well, thank you so much, man! Now I've got everything working, AND I'm loving CyanogenMod so far too.
1) I'm on Android 5.1.1
2) I've got CyanogenMod
3) My memory isn't super full
4) My service works
The only weird thing is when I plug my phone into my computer, it says "XT1033." Then, in my phone's settings (About Phone > Device Model) it says "Moto G." Lol.

DrumsXO said:
The only weird thing is when I plug my phone into my computer, it says "XT1033." Then, in my phone's settings (About Phone > Device Model) it says "Moto G." Lol.
Click to expand...
Click to collapse
I've heard that before. Fastboot flashing a full firmware image might help to get it back to "XT1032". But I wouldn't do that, if everything else works fine

DrumsXO said:
Well, thank you so much, man! Now I've got everything working, AND I'm loving CyanogenMod so far too.
1) I'm on Android 5.1.1
2) I've got CyanogenMod
3) My memory isn't super full
4) My service works
The only weird thing is when I plug my phone into my computer, it says "XT1033." Then, in my phone's settings (About Phone > Device Model) it says "Moto G." Lol.
Click to expand...
Click to collapse
Glad everything is working properly

k-kuchen said:
I've heard that before. Fastboot flashing a full firmware image might help to get it back to "XT1032". But I wouldn't do that, if everything else works fine
Click to expand...
Click to collapse
Yeah, I'm not gonna mess with it!
TheMatthew562 said:
Glad everything is working properly
Click to expand...
Click to collapse
Thanks!

Okay, I found a problem; my Mobile Data doesn't work...

DrumsXO said:
Okay, I found a problem; my Mobile Data doesn't work...
Click to expand...
Click to collapse
Flash the stock rom for xt1032(usa/brazil/asia) and flash the kernel and radio images...thats it

DrumsXO said:
Okay, I found a problem; my Mobile Data doesn't work...
Click to expand...
Click to collapse
Maybe there's no APN. That happens sometimes

ishaan02 said:
Flash the stock rom for xt1032(usa/brazil/asia) and flash the kernel and radio images...thats it
Click to expand...
Click to collapse
I kinda wanna stick with CyanogenMod now though.
k-kuchen said:
Maybe there's no APN. That happens sometimes
Click to expand...
Click to collapse
How do I fix this?

DrumsXO said:
How do I fix this?
Click to expand...
Click to collapse
Find your provider's APN data and create a new APN entry in the settings.
Maybe those will work -> http://bestmvno.com/apn-settings/apn-settings-for-consumer-cellular/

k-kuchen said:
Find your provider's APN data and create a new APN entry in the settings.
Maybe those will work -> http://bestmvno.com/apn-settings/apn-settings-for-consumer-cellular/
Click to expand...
Click to collapse
I had to do some digging to find where and how to change APN Settings in my phone, but once I found them, I was a little shocked; there are a lot of them! There's a list of about 15 different APNs in my phone!
That seemed a little unusual, so I looked for a way to reset them or something, and found a thread that talked about how to delete their database file with a Root Explorer. I went ahead and did so, then rebooted my phone, to find that they had all come back! Then I discovered you can reset them to default right from the APN Settings page; I did that, but they were all still there, LOL.
I'll give these a try, but I'm not expecting them to work, honestly. Perhaps I need to call my carrier and see if they can help me out. Although, if I tell them I rooted and flashed my phone, they probably won't.

BoxxiRoms are back ~ SinfulROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SinfulROM 2.0​
Some History​
Some of you may remember me, some of you may not. I was around these parts when the S5 first came out and we were waiting for Root access to use ROMs. I released a ROM called BoxxiRoms, but to be honest, it wasn't too good and there were problems with it. I since kind of left, upgraded to 5.0 via someone else's ROM and left it at that.
Then I got bored with 5.0. Too many things I enjoyed with KitKat just didn't work at all with 5.0. I'm huge on Battery Conservation (as you can see from a post linked in my Signature) and I've always wanted to put out the best damn battery life for this phone that's honestly possible.
Well, I'm back. I've learned a lot since my first ROM release and I'm here to keep to my promise of the best damn battery life and the best experience you can have on your Verizon G900V S5.
Code:
Your warranty is void, and i'm not responsible for any bricking. It's frankly difficult to brick an android device, so I don't think you need to worry about it.
Now that that's out of the way... I've been using this rom for 2 weeks straight to make sure its working just right for release. I started out on a personal built of beta 0.1 and now I'm up to 2.0, which is all for you guys.
Features
Ultimate Debloating (thanks to @elliwigy for the starting base. I went further with it and got it to 450 megs at its base.)
All apps Added are Uninstallable like normal apps
Themable through the Launcher (will custom theme soon)
Great Battery Life
4K Video Recording (through the Camera App added)
My Additions
Smart Launcher 2
Textra (instead of Stock SMS app)
Chrome Beta (instead of Standard Chrome)
Matrik (hacked Kik client with TONS of awesome features)
PAW Server (a nice little server app with plugins available. Will have tutorials with this soon)
Apollo Music Player
OGYoutube (a better youtube app)
MyRoll Gallery (better than Stock gallery and smaller size)
Open Camera App (instead of Stock camera)
XAPK Installer (for use with XAPK files from apkpure)
Pixel Battery Saver (the BEST way to get the best battery life)
SQLite3
BusyBox'd
Rooted with Superuser installed
Future Addons
Pre-Dark-Theme
More built in apps
More Tweaks for Battery Life
Free RAM
This is with Textra, Matrik and PAW Server all open and running.​
Eww... Why NCG 4.4.2 KitKat?​
Things like Pixel Battery Saver didn't work on 5.0 or later. Also, I had some real crap battery life on 5.0. With my current rom as is with Pixel Battery Saver always running on level 4, I go from 100% at 9am to about 30% at 9PM with some heavy use at work (a lot of down time for Trivia Crack). Overall, I fell 4.4.2 is the BETTER option for the S5.
INSTALL​If there's a better way to install this, let me know, I'm severely outdated obviously as you'll read below
This has ONLY been tested and installed by this method on a G900V
1.) Flash back to NCG Kernel so you can access SafeStrap (download below)
2.) Advanced Wipe Data/Cache/Dalvik/System
3.) Flash the Rom ZIP file
4.) Boot into Android! (first boot may take an extra minute or so. if it takes longer, LET ME KNOW)
Current Issues​None that I know of. Let me know if you find anything.
DOWNLOAD
ROM
DIRECT LINK (my personal website server)
AndroidFileHost Mirror
Direct Link (BASE ROM No Edits)
NCG Kernel
DIRECT LINK (my personal website server)
AndroidFileHost Mirror
​
credits
Honestly, with how much downloading and tweaking I've done, I'm not entirely who all the people are to thank for this ROM so far.
Lots more to come soon!
XDA:DevDB Information
SinfulROM, ROM for the Verizon Samsung Galaxy S 5
Contributors
KaptinBoxxi, elliwigy
ROM OS Version: 4.4.x KitKat
ROM Firmware Required: NCG
Based On: Extreme Syndicate
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2016-01-14
Created 2016-01-15
Last Updated 2016-01-25

dude this is such great news for me. I loved KK and have hated LP since it was released. You are the f'in man for making another KK rom!
wouldn't it be better to go back to NCG rescue .tar and re-root and then flash this? I dont think it'l work the way you described coming backwards from LP. At least it never worked that way before unless yours does something different i dont know about.
here's a link to Jrkruse's "rooting and firmwares" page. the rescue tar is there.
Safestrap Flashable Firmwares

It might actually be better that way, although this is how I did it. Starting clean is always best though.
Thanks for the interest

KaptinBoxxi said:
It might actually be better that way, although this is how I did it. Starting clean is always best though.
Thanks for the interest
Click to expand...
Click to collapse
i tried it your way from the Jrkruse BOK3 stock rooted rom and it bootlooped. Then fresh from rescue tar and it worked perfect. I wish someone else would get in here and compare methods!

I'll modify the instructions when I get home tonight. Maybe I just got lucky haha

twrp install, no prob

For clarification, Are we able to use this ROM if we rooted from jrKruse's Thread to get root on OK3 phones? I was thinking we could only use Lollipop 5.0 TW based Roms,
Thanks..

I'll give it a whirl...
I hate LP too, fav rom's been Beans NE9 rom but it hasn't beet touched in like a year, I'm excited to see what you brought
---------- Post added at 11:01 PM ---------- Previous post was at 10:57 PM ----------
damagi123 said:
wouldn't it be better to go back to NCG rescue .tar and re-root and then flash this?
Click to expand...
Click to collapse
This would be my preferred method too, total restore to NCG with Odin, root, busybox, safe strap, full wipe, wipe both cache's, flash this gem, bingo... No chance for gremlins lol

damagi123 said:
i tried it your way from the Jrkruse BOK3 stock rooted rom and it bootlooped. Then fresh from rescue tar and it worked perfect. I wish someone else would get in here and compare methods!
Click to expand...
Click to collapse
KaptinBoxxi said:
I'll modify the instructions when I get home tonight. Maybe I just got lucky haha
Click to expand...
Click to collapse
abovenbeyond said:
I hate LP too, fav rom's been Beans NE9 rom but it hasn't beet touched in like a year, I'm excited to see what you brought
This would be my preferred method too, total restore to NCG with Odin, root, busybox, safe strap, full wipe, wipe both cache's, flash this gem, bingo... No chance for gremlins lol
Click to expand...
Click to collapse
Install Kit Kat Roms On All Bootloaders
Edit: I updated the method and added new firmware zips ran into some hardware issues these fixed the problem
This method should work for All Bootloaders Without having to wipe data on Internal storage
Download This one NK2_Firmware_No_Bootloaders_V3.zip should work for all Kit Kat Roms. This is a 4.4.4 Version I tested it on 4.42 Version and it worked fine . If you want to use a differen versions, all Version listed below
Reboot To Safestrap Wipe cache, system, data, dalvik cache then flash above zip
Go back and Wipe cache, system, data
Install Kit Kat Rom
Reboot to system and go through setup.
Remember when using Kit Kat Roms there is no reason to flash kernel in safestrap as you are all ready running kit kat kernel. Also do not use Lollipop Safestrap on kit kat roms you can reach safestrap by simply rebooting rom and choosing safestrap recovery when dialog comes up
If you want to use zip that matches firmware of rom a full list can be found [URL="http://forum.xda-

I updated the install instructions. Sorry it took me longer than expected to do so. I had plans yesterday and wasn't home until literally now.
An actual update about the rom itself
I'm restarting my conversion of the Kali Nethunter conversion to the S5 this week, so keep an eye out for an updated ROM IF you're interested in that sort of thing

jrkruse said:
Install Kit Kat Roms On All Bootloaders
Click to expand...
Click to collapse
Thanks so much for doing that. that's great

Once I boot the SuperSu binary won't update..reboot and no go..any suggests/

I'm gonna manually update it in my next release but frankly it doesn't honestly need to be updated to work correctly
Some news:
If you're looking into making your own Slimmed Down NCG Rom, I'll be uploading and posting my base rom tonight when i get home from work. Base rom I'm uploading is 497 megs. Great starting base for anyone wanting to get into making their own roms. I'll have tutorials as well.

KaptinBoxxi said:
I'm gonna manually update it in my next release but frankly it doesn't honestly need to be updated to work correctly
Some news:
If you're looking into making your own Slimmed Down NCG Rom, I'll be uploading and posting my base rom tonight when i get home from work. Base rom I'm uploading is 497 megs. Great starting base for anyone wanting to get into making their own roms. I'll have tutorials as well.
Click to expand...
Click to collapse
Just a question. Why not do NI2 or NK2 build so VOLTE will work. Was the battery life not as good. I know that's your ultimate goal

So far, everything has worked fine. I don't even know what VOLTE is tbh lol. I still get 4G on this ROM, so it's not something I even thought about

KaptinBoxxi said:
So far, everything has worked fine. I don't even know what VOLTE is tbh lol. I still get 4G on this ROM, so it's not something I even thought about
Click to expand...
Click to collapse
If you enable HD calling on your Verizon plan it allows Volte or video calling and HD calling and Visual Voice mail. Once enable the old voice mail method does not work so you wont get any notifications or any thing without the Visual Voicemail apk wich require VOLTE or HD calling. This feature was first available on NI2 build. For example If I wanted to use your rom as a daily driver I would have to call Verizon and disable Advanced Voicemail so I would be able to receive voice mail notifications. Then if I went back to Lollipop I would have to reactivate it. Thats the only reason I asked. I know thats the one thing people ask the most about in the international roms like Phoenix is that it does not support VOLTE and how do they get voicemail working

Thank you gentlemen.
Thanks for bringing us back to KK. been running great for the past 24 hours then i flashed the NCG zip acciddentally and broke the whole mess. Wiped everything and went back to oding anf the rescure.tar and all is well again. A few questions though.
Before i screwed up i noticed...
1. I was consistently losing wifi settings, ( seem to remember this from KK)
2. Quick Pic doesnt seem to be able to set different wallpaper for lock screen and home screen, is this a KK vs LP thing?
3. Baseband if BOG3 is that what it should be?
Thanks again

jrkruse said:
If you enable HD calling on your Verizon plan it allows Volte or video calling and HD calling and Visual Voice mail. Once enable the old voice mail method does not work so you wont get any notifications or any thing without the Visual Voicemail apk wich require VOLTE or HD calling. This feature was first available on NI2 build. For example If I wanted to use your rom as a daily driver I would have to call Verizon and disable Advanced Voicemail so I would be able to receive voice mail notifications. Then if I went back to Lollipop I would have to reactivate it. Thats the only reason I asked. I know thats the one thing people ask the most about in the international roms like Phoenix is that it does not support VOLTE and how do they get voicemail working
Click to expand...
Click to collapse
Oh... I never had any of those voice mail or HD calling features, that's why I didn't know about it.
JeffersonDavis said:
Thanks for bringing us back to KK. been running great for the past 24 hours then i flashed the NCG zip acciddentally and broke the whole mess. Wiped everything and went back to oding anf the rescure.tar and all is well again. A few questions though.
Before i screwed up i noticed...
1. I was consistently losing wifi settings, ( seem to remember this from KK)
2. Quick Pic doesnt seem to be able to set different wallpaper for lock screen and home screen, is this a KK vs LP thing?
3. Baseband if BOG3 is that what it should be?
Thanks again
Click to expand...
Click to collapse
I based this off of ExtremeSyndicate v1.5 which was based on NCG. I had the wifi issue at first, but realized I just never flashed back to the NCG Files which actually had control over all that. Once I had all the NCG files properly set, I didn't have issues at all. When it comes to the Wifi, I've always had issues with this phone (no matter the rom. I was on a 5.0.1 ROM before I sat down and decided to go back to NCG), I'd get random notifications that Wifi just connected but it never actually disconnected in the first place. I'm not sure what that one is
As for the Wallpaper issue, I actually noticed that. I'm not sure why I can't set pictures. I actually put the gallery back in my personal build last night as a test and still can't set wallpapers so I'm not entirely sure what the issue is. If you use Smart Launcher's settings, you can set a wallpaper i'm pretty sure. I pretty much never change my wallpaper so it wasn't something I noticed at first
Everything should be NCG no matter what.

KaptinBoxxi said:
Oh... I never had any of those voice mail or HD calling features, that's why I didn't know about it.
I based this off of ExtremeSyndicate v1.5 which was based on NCG. I had the wifi issue at first, but realized I just never flashed back to the NCG Files which actually had control over all that. Once I had all the NCG files properly set, I didn't have issues at all. When it comes to the Wifi, I've always had issues with this phone (no matter the rom. I was on a 5.0.1 ROM before I sat down and decided to go back to NCG), I'd get random notifications that Wifi just connected but it never actually disconnected in the first place. I'm not sure what that one is
As for the Wallpaper issue, I actually noticed that. I'm not sure why I can't set pictures. I actually put the gallery back in my personal build last night as a test and still can't set wallpapers so I'm not entirely sure what the issue is. If you use Smart Launcher's settings, you can set a wallpaper i'm pretty sure. I pretty much never change my wallpaper so it wasn't something I noticed at first
Everything should be NCG no matter what.
Click to expand...
Click to collapse
Having the latest baseband is always a good idea. It should affect the rom performance in any way.
---------- Post added at 11:16 AM ---------- Previous post was at 11:10 AM ----------
I ran this rom for a couple of days. I must say the battery life is good

KaptinBoxxi said:
It might actually be better that way, although this is how I did it. Starting clean is always best though.
Thanks for the interest
Click to expand...
Click to collapse
what jrkruse was saying about you trying to go to NI2 with this rom is important for almost everyone on this forum since we've all upgraded to volte so our vvm wont work.
also titanium backup isnt recognizing root at all. no matter what I try. probably because of the supersu binary problem

Xperia bootloop upgrading to 5.1.1 (FTF D2303 Generic UK 18.6.A.0.182)?

The last thing I remember flashing was Clockword Mod 11 last year, ever since then I have been running Firmware build 18.3.1.C.1.15. Upon seeing an update for my phone for Firmware build 18.3.1.C.1.17 I attemted to download it and kept getting the message "Cannot Verify" so after trying this out on PC Companion and relocking my bootloader I was still running into problems. So the simplest thing I could think of is to use Flashtool and flash the latest ftf from there (Firmware 18.6.A.0.182 - obtained from XperiFirm), at first I didnt think it was a problem to not wipe USER_DATA as I just thought of it as an upgrade, if that failed I persumed I would have to wipe everything (this didnt matter much anyway). So I went ahead and flashed the rom however when I went to boot my mobile I got a bootloop "Android is optimising apps xxx of xxx" this went on forever untill I cut the power using a pin. So I tried it again this time wiping everything and still the same problem :crying: . Then I came across people on the forums to use the older FlashTool verison 0.9.18.6 since the new FSC feature can cause probelms, this time I tried it again however I used the older Firmware 18.6.A.0.172 just to be failsafe. Still the same problem. Right then I was thinking Emma would save my phone so I went and applied the 4.4.4 Firmware 18.3.1.C.1.15 service (Which I had to begin with) but for some reason this seemed to have little effect despite trying it twice and reciving a "Sucessful Flash" message. Now I am left very confused as it is still booting in the lollipop style (optimising apps loop) even though I flashed a KitKat rom. I have been left without my phone all day because of this, any help would be STRONGLY APPRICIATED! . Thanks for your time

#1 Open your bootloader again
#2 Install TWRP (See 5.1.1 root topic for installation/guide)
#3 Open TWRP Wipe all data
#4 Reboot into recovery
#5 Flash any custom rom like Cyanogenmod through TWRP
Post results please this is fixable It's seems It's a soft brick which is an easy fix
What i think is you had corrupt data/left over data and after you relocked bootloader something went wrong after flashing. Though flashing should wipe all data let's see

Re-flash ftf wiping data and caches, you must do this if going from 4.4.4 to 5.1 and From 5.1 to 4.4.4 due to changes in runtime from dalvik to art and other changes.

How to get near enough stock?
Thanks for your replies, when I flashed the ftf's I did tick all the boxes under 'Wipe' on FlashTool, when that failed so did emma. I can try flashing CWM however the main purpose of this was for me to upgrade to Lollipop as I wanted a near enough stock experiance (Considering Z5 Rom) with root. When I tried CWM before there were a few things that I just coulnt get used to. Is there any way that I could use recovery to flash a stock rom with the lastest Lollipop releese or Z5 experiance as I have backups on PCC that I have to restore (Important contacts, media etc...) and I dont really want to use a CWM based rom . I wouldnt mind to flash Z5 however I dont know if this is possiable could you guys comfirm this? Thanks for your time .

[Update] TWRP recovery is working!
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .

Zane Finch said:
I have followed this thread to update my Recovery - TWRP 2.8.7.0 .
Many Thanks to @linuxct for the straight forward instructions and @ARandomIndian for putting me in the correct direction :highfive: .
Im just unsure if I can flash Z5 Experiance Rom now. Is it possiable despite my android being messed? I have already wiped data, is it okay to just go and flash? .
Click to expand...
Click to collapse
Don't worry you're android is not messed up, let's do this to fix it back to regular :-
Before starting i highly recommend you charge your phone to have atleast 50+% battery and use the official cable provided also make sure the cable is firmly inplace,
#1 Enter Recovery, wipe all data
#2 Download Stock 5.1.1 i think you like that so get that (Make sure it is for your D2303 or whatever your model is)
#3 Install latest flashtools with latest patch (Or later versions if you don't want to risk it)
#4 Go to the location of flashtools (installation directory) for me it is C:\Flashtool\drivers Open the exe file there, select the 2 Flashmode and Fastboot drivers install them.
#5 Flash the ftf using flashtools
Post results

Somehow...
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .

Zane Finch said:
Using TWRP I wiped Dalvik Cache, Cache, System and Data. Using the same 18.6.A.0.182 Customization UK FTF from yesterday I flashed my phone but somehow I am stuck with the same bootloop again?! "Android is optimising Apps XXX of XXX" I really dont understand this. . Thanks for your help .
Click to expand...
Click to collapse
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you

Optimising
ARandomIndian said:
Hey man Android is optimizing means everything is working just fine it takes about 30+ minutes sometime,
Just leave it charging for atleast 2 hours and see what the progression is and post results please, thank you
Click to expand...
Click to collapse
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!

Zane Finch said:
Yes but this does not seem normal, the first boot always freezes on the wave animation. It then restarts by itsself and optimises upto so many for example 64 of 200 and then freezes and restarts with a different ammount like 90 of 194. This didnt seem normal to me, is this okay?
Edit: I have left it running for almost 40 min now. Every time just before it seems to freeze and reboot it never reaches the end of the ammount say 60 of 200. I'm becoming very doubtful that it is going to work . But I just remembered a while back that I flashed a custom boot img to get recovery and root in my last working state. Maybe this has somthing to do with it?
Really need my phone working now :| If anyone can help please do! Thanks!
Click to expand...
Click to collapse
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download

ARandomIndian said:
Hi okay, try flashing the Z5 style rom please then we'll move forward I think you've a corrupted ftf
Please redownload latest Z5 style rom make sure it's not interrupted during download. Restart router if needed for stability before download
Click to expand...
Click to collapse
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?

If your bootloader is unlocked did you update it before flashing anything? If not this is why

Zane Finch said:
I tried flashing the Z5 experiance rom, I followed the instructions on the rom page (Used TWRP). However this time when it booted it did not say "Optimising Android" but it still did boot loop after the wave animation. I also tried flashing the older firmware but that did the same loop again, I also have been looking for alternative ftf's online becuase I also had the suspicion of a corroupted ftf however there are no Customized UK roms availble. I really am stuck now, my phone seems to be more messed up than I thought. . Any more Ideas?
Click to expand...
Click to collapse
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.

[email protected] said:
If your bootloader is unlocked did you update it before flashing anything? If not this is why
Click to expand...
Click to collapse
ARandomIndian said:
You updated your bootloader before flashing right? If not do that like Andy said,
Also i would give you my Nandroid but It's the D2305.
Click to expand...
Click to collapse
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!

Zane Finch said:
Okay, you mean the same one I flashed to be able to update my bootloader to TWRP? I'll give it a shot! Thanks!
Click to expand...
Click to collapse
Okay nice post the results

ARandomIndian said:
Okay nice post the results
Click to expand...
Click to collapse
I flashed that very bootloder before I flashed the Lollipop ftf I booted my phone and the same thing happend, so I tried it again this time flashing afterwards an still booting with the same damn screen . Was I definatly using the correct bootloader or am I missing out anything when flashing? My phones rebooted like 5 times now for the 'optimisation' and its getting nowhere .
Shall I fire up my classic Nokia 5230 with custom Symbian to record a video so you guys can see what happens when it boots?

Did you wipe user data and cache when flashing the ftf

[email protected] said:
Did you wipe user data and cache when flashing the ftf
Click to expand...
Click to collapse
Yes, everything in the 'Wipe' section was ticked, infact before I flashed it again I also wiped Dalvik, cache, data and system in TWRP.

So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Okay flash this version of Cyanogen http://forum.xda-developers.com/xperia-m2/orig-development/rom-cyanogenmod-12-developement-t2971213 choose the latest one
We'll see what the issue can be any ideas @linuxtt
---------- Post added at 03:18 PM ---------- Previous post was at 03:14 PM ----------
Zane Finch said:
So I just flashed CWM 12.1 and its all running fine for some reason the Wifi doesnt work but atleast I can use this untill we find what the problem is. Do you guys know why my WiFi isnt working? But more importantly why does CWM work and stock rom doesnt?!
Edit: The reason the WiFi isnt working has to be a problem with the kernal as far as I can see, this also suggests that the kernal could be incompatable with Lollipop as it wasnt designed to support it? Correct me if im wrong but if this is the case where can I download the official latest kernal? If someone could confirm this by checking my kernal version above that would be great! Thanks!
I previously updated my kernal here the one that says [new]. If you look at post #8 you will see that this kernal has a problem with WiFi in CWM "As I suspected, in kernel modules there's no WiFi module (wlan.ko), I think that that's the reason why WiFi is not working.
Click to expand...
Click to collapse
Okay can you please flash another FTF? First try a new 5.1.1 ftf from another source for your model and then try older versions like Kitkat and post results please

[INFORM] [XT1575] Don't upgrade to Nougat stock!

Just a warning to fellow members on this forum that if you take the Nougat stock OTA you will NOT BE ABLE TO USE CUSTOM ROMS. Most roms you will find on this forum are developed for the MM bootloader, and there is no going back once you make this switch.
You will likely face INSTABILITY with your modem/wifi/sim activation, which all signs seem to point to the MM versions being more reliable. Additionally, you face the possibility of BRICKING your phone when using return-to-stock methods.
(Trust me, I've done it to 2 of my devices so far...)
I know this has been mentioned before, but I did not readily find this info in any of the stickies when I looked for it and wound up making my last mistake, so it's worth reiterating.

skuppej said:
Just a warning to fellow members on this forum that if you take the Nougat stock OTA you will NOT BE ABLE TO USE CUSTOM ROMS. Most roms you will find on this forum are developed for the MM bootloader, and there is no going back once you make this switch.
You will likely face INSTABILITY with your modem/wifi/sim activation, which all signs seem to point to the MM versions being more reliable. Additionally, you face the possibility of BRICKING your phone when using return-to-stock methods.
(Trust me, I've done it to 2 of my devices so far...)
I know this has been mentioned before, but I did not readily find this info in any of the stickies when I looked for it and wound up making my last mistake, so it's worth reiterating.
Click to expand...
Click to collapse
I went from Lineage OS to stock 6.0 to stock 7.0 to stock 6.0 to Lineage OS on the XT1575. You can absolutely go back and forth to custom roms. The bootloader and gpt files will fail to flash when downgrading, but that can be safely ignored.
You do have to flash back to stock 6.0 before installing a custom rom though. You cannot do it from stock 7.0 due to modem firmware mismatch. All custom roms use the MM 6.0 modem firmware because the current 7.0 firmware is not obtainable.

Thanks for the warning but It's 2017. None of the phones get Hardbricked completely
I was on Stock 7.0 for about 4 months now. And finally decided to flash the LOS Unofficial Build by Hashbang173, that build is based on Nougat Kernel and Modem.
It booted up perfectly and I used it for half a day. But it have some camera and mic issue so I had to go back to Nougat.
I was able to downgrade to Stock 6.0 and then get OTA back to Nougat successfully.
Here's my post on LOS Thread.
Also the Hardbricked issue has been solved.
In case of XT1575, ask any of the fellow forum member to create a silmilar dump for XT1575 devices.

antariksh said:
Thanks for the warning but It's 2017. None of the phones get Hardbricked completely
I was on Stock 7.0 for about 4 months now. And finally decided to flash the LOS Unofficial Build by Hashbang173, that build is based on Nougat Kernel and Modem.
It booted up perfectly and I used it for half a day. But it have some camera and mic issue so I had to go back to Nougat.
I was able to downgrade to Stock 6.0 and then get OTA back to Nougat successfully.
Here's my post on LOS Thread.
Also the Hardbricked issue has been solved.
In case of XT1575, ask any of the fellow forum member to create a silmilar dump for XT1575 devices.
Click to expand...
Click to collapse
I'm using xt1575 us variant. Is there any way you could send a link to the correct 6.0 i should flash? I'm stuck with bad cell service and the same problems you mentioned.

I can tell you that if you mess up the procedure in some fashion you can lose your SIM activation permanently. I updated to 7.0 before putting my SIM in and wasn't able to activate on 7.0. And after fastbooting/restoring back to 6.0 I still did not get it.
In another instance I upgraded the OTA after moving from 7.0 > 6.0 > back to 7.0. Bad decision because this hardbricked my phone. I was able to format an external SD card with a temporary bootloader to get it going again but I was still having problems with my modem (from what I've gathered, you can't revert back to 6.0 modem).
Best steer clear of 7.0 OTA entirely. There's a reason why almost all development is still happening with 6.0 base.

skuppej said:
I can tell you that if you mess up the procedure in some fashion you can lose your SIM activation permanently. I updated to 7.0 before putting my SIM in and wasn't able to activate on 7.0. And after fastbooting/restoring back to 6.0 I still did not get it.
In another instance I upgraded the OTA after moving from 7.0 > 6.0 > back to 7.0. Bad decision because this hardbricked my phone. I was able to format an external SD card with a temporary bootloader to get it going again but I was still having problems with my modem (from what I've gathered, you can't revert back to 6.0 modem).
Best steer clear of 7.0 OTA entirely. There's a reason why almost all development is still happening with 6.0 base.
Click to expand...
Click to collapse
Because they haven't finished implementing the changes in the code for the kernel source. As stated in many of the development threads over a month ago. So actually it will be made with the 7.0 source code but as of now it hasn't. As there aren't many truly active developers for the pure anymore.

Still seeing loads of irrecoverable problems for people updating to Nougat. Don't do it guys.
You can permanently lose your SIM access if you don't upgrade just right, and everyone has a different set of procedures.
And it you go to Nougat you can't go back.

I just can't get my sims to work on any custom rom after recovering from that hard brick. By any i mean both 6.0 & 7.0 compatible modems

Same..I ended up in the same boat where neither MM or Nougat based roms worked with my SIM after I recovered from hard brick using the external SD card bootloader trick
I needed to RMA...hence this warning
Sorry dude

If you ever used Magisk though make sure to uninstall from the app, then flash the uninstaller zip, then wipe, restore, and before booting flash the uninstaller zip again and then boot in
Old Magisk partitions cause the No SIM issue. I think this might have bearing on how upgrading to Nougat stock can break things. Like if you have a Magisk partition and then RSD back to stock without uninstalling first, and then take the OTA. That's my hunch...but not willing to test this this theory out..

Clarification...
skuppej said:
Still seeing loads of irrecoverable problems for people updating to Nougat.
Click to expand...
Click to collapse
I'm not. This is the first report I've seen of that, in fact.
skuppej said:
You can permanently lose your SIM access if you don't upgrade just right, and everyone has a different set of procedures.
Click to expand...
Click to collapse
No, not really. You go on down the list and install each element, then you restart. Or you install the pre-packaged update from the Motorola Update service. That's two. Unless there's just two people using this phone, then I think you might have misunderstood the definition of the word "everyone."
skuppej said:
And it you go to Nougat you can't go back.
Click to expand...
Click to collapse
This is true.
skuppej said:
If you ever used Magisk though make sure to uninstall from the app, then flash the uninstaller zip, then wipe, restore, and before booting flash the uninstaller zip again and then boot in
Click to expand...
Click to collapse
No, the real issue is that Magisk will eat up CPU cycles constantly and keep cores online unecessarily. The workaround is to simply use SuperSu, which still works fine (despite what the uneducated masses might lead you to believe).

To the hatas
I figured I'd get some negative feedback for this warning.. I've had to RMA 3 separate XT1575's for this issue. I've definitely followed the guides listed on this forum on how to update to Nougat exactly, and I've gone through both the flashing each pre-packaged update route, as well as the OTA route.
I know you might like to dismiss this as user error, but the fact that we do not have a way to flash back to MM can leave you in a state where there is a BL/modem mismatch, and no way to flash a compatible modem. You can only really run into this situation from what I've experienced by going to Nougat at some point. It seems to be related to a bad flash, a restore of a MM rom over a N rom, leaving Magisk partition during restore, or something else. You'd think that RSD'ing back to stock should always return things to back to normal, but once the BL changes this simply is not the case.
If you check the Q/A board for "no SIM" and see the thread on Lineage OS 14.1, in particular, you will see enough mixed reports about SIM/WIFI access issues, and all of them recently moved to Nougat. I am not making this up.
(And, yes, having Magisk installed with a new rom flash/restoration *can* lead to No SIM Card Detected. In fact, I experienced this yesterday again while recovering from a bootloop for a separate ROM issue. The only way to fix this flavor of No SIM Card Detected was to flash the uninstaller, restore my backup, flash it again before booting, boot up, verify SIM was working, then flash the Magisk installer only after all those steps have been completed)

Bill720 said:
I'm not. This is the first report I've seen of that, in fact.
No, not really. You go on down the list and install each element, then you restart. Or you install the pre-packaged update from the Motorola Update service. That's two. Unless there's just two people using this phone, then I think you might have misunderstood the definition of the word "everyone."
This is true.
No, the real issue is that Magisk will eat up CPU cycles constantly and keep cores online unecessarily. The workaround is to simply use SuperSu, which still works fine (despite what the uneducated masses might lead you to believe).
Click to expand...
Click to collapse
As for supersu, on nougat, magisk is bad? And I should switch to supersu?

Hitti2 said:
As for supersu, on nougat, magisk is bad? And I should switch to supersu?
Click to expand...
Click to collapse
No, if your phone is working fine, don't mess with it. I guess these guys were seeing some issues with high battery drain and CPU use they pinned down to the magisk daemon. I've never seen the same thing on any of my devices. Magisk has far too many users for this to be a widespread, unrecognized issue. Not saying it didn't happen, just saying it might be some particular version, configuration, app interaction, etc. issue. Was it magisk, or some other rouge app bombarding magisk with requests? Without logs who knows? If you aren't experiencing any problems yourself, why bother changing anything?

Bill720 said:
I'm not. This is the first report I've seen of that, in fact.
No, not really. You go on down the list and install each element, then you restart. Or you install the pre-packaged update from the Motorola Update service. That's two. Unless there's just two people using this phone, then I think you might have misunderstood the definition of the word "everyone."
This is true.
No, the real issue is that Magisk will eat up CPU cycles constantly and keep cores online unecessarily. The workaround is to simply use SuperSu, which still works fine (despite what the uneducated masses might lead you to believe).
Click to expand...
Click to collapse
jason2678 said:
No, if your phone is working fine, don't mess with it. I guess these guys were seeing some issues with high battery drain and CPU use they pinned down to the magisk daemon. I've never seen the same thing on any of my devices. Magisk has far too many users for this to be a widespread, unrecognized issue. Not saying it didn't happen, just saying it might be some particular version, configuration, app interaction, etc. issue. Was it magisk, or some other rouge app bombarding magisk with requests? Without logs who knows? If you aren't experiencing any problems yourself, why bother changing anything?
Click to expand...
Click to collapse
Ok ty. I wouldn't know if bat drain would be normal for my daily use vs supersu usage.
---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Definitely not a myth
Hitti2 said:
As for supersu, on nougat, magisk is bad? And I should switch to supersu?
Click to expand...
Click to collapse
Yes... on the stock Rom at least. It'll be made obvious by using various tools, so you can find out whether or not any other Rom is affected. See my long-running (and fully resolved) thread on the issue here.
jason2678 said:
No, if your phone is working fine, don't mess with it. I guess these guys were seeing some issues with high battery drain and CPU use they pinned down to the magisk daemon. I've never seen the same thing on any of my devices. Magisk has far too many users for this to be a widespread, unrecognized issue. Not saying it didn't happen, just saying it might be some particular version, configuration, app interaction, etc. issue. Was it magisk, or some other rouge app bombarding magisk with requests? Without logs who knows? If you aren't experiencing any problems yourself, why bother changing anything?
Click to expand...
Click to collapse
While it is a seldom-reported issue, I found it to be fully repeatable following hard resets. Again, this was just on the stock Rom where magisk daemon would hold the throttle slightly open. 5-15% CPU use might not sound like much, but it absolutely kills the screen-on-time by defeating the dynamic clocking and battery optimizations.
TL;DR? If Magisk daemon isn't killing your battery life, use it. Otherwise, Supersu is the way to go.

Bill720 said:
Yes... on the stock Rom at least. It'll be made obvious by using various tools, so you can find out whether or not any other Rom is affected. See my long-running (and fully resolved) thread on the issue here.
While it is a seldom-reported issue, I found it to be fully repeatable following hard resets. Again, this was just on the stock Rom where magisk daemon would hold the throttle slightly open. 5-15% CPU use might not sound like much, but it absolutely kills the screen-on-time by defeating the dynamic clocking and battery optimizations.
TL;DR? If Magisk daemon isn't killing your battery life, use it. Otherwise, Supersu is the way to go.
Click to expand...
Click to collapse
? how do i jump from magisk to supersu? Properly uninstall mag. And what version supersu should i use on stock nougat?

This is the version, but know what you are doing...
Hitti2 said:
? how do i jump from magisk to supersu? Properly uninstall mag. And what version supersu should i use on stock nougat?
Click to expand...
Click to collapse
I do believe that Magisk has a built-in uninstaller tool. I personally used SuperSu 2.82. Remember, this is only necessary if Magisk Daemon is constantly utilizing CPU resources. Checking that (using Simple System Monitor or a similar tool) aught to be your first step.

Bill720 said:
I do believe that Magisk has a built-in uninstaller tool. I personally used SuperSu 2.82. Remember, this is only necessary if Magisk Daemon is constantly utilizing CPU resources. Checking that (using Simple System Monitor or a similar tool) aught to be your first step.
Click to expand...
Click to collapse
I'm guessing under active processes I should monitor?

Guess im good.