BoxxiRoms are back ~ SinfulROM - Verizon Galaxy S 5 Android Development

{
"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

Related

how to fix cm12 modem update and problems thread

{
"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"
}
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
TOP TIP "For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed." Thanks go to tobitege for this.
zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
+1. I also flashed the latest official CM nightly, booted it and checked if everything was working and then flashed the latest unofficial Temasek's rom. Everything works fine.
Cheers
@zaphodbeeb: thanks for having created this!
This morning I tested an extended version of the CM-12 flashable zip containing more partitions of the current nightlies.
First test brought me a jackpot in that it flashed without an error message, but soft bricked my phone (black screen, no adb nor fastboot), but power button rebooted in a special mode "HUSB_BULCK" (viewable in device manager). Takin' up the challenge, so after plenty of searching/reading and multiple tries to install the right drivers, I got it going through Color OS installation with special phone flashing tool, then flashing X44 again, unlocking, custom recovery+rooting... that was (deserved) fun!!
Though in the first moments it scared me s***tless!
Long story short, totally agree to just flashing the full nightly and directly clean on top any LP rom you want, if you want to be sure to have it right.
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
cam30era said:
FWIW I flashed the alpha modem.zip after flashing and booting SlimLP ROM. Worked fine, absolutely no problems.
Click to expand...
Click to collapse
I dirty flashed SlimSaber-bacon-5.0.2-20150110 build on top of SlimSaber-bacon-5.0.2-20150102 and then flashed alpha modem everything works fine.
zaphodbeeb said:
Discuss how best to install the CM12 alpha modem.
Do the rest of us a favour, do it here in this thread, instead of clogging up every lollipop development" thread.
In my experience the best way of sorting problems like wifi issues, proximity failures and dialler problems is just try these.
1. OPO_L5_alpha-modem-flashable.zip
2. cm-12-nightly-modem-flashable.zip
3. cm-12-20150106-NIGHTLY-bacon.zip
Option 3 worked for me! Personally I would recommend all concerned to do this. Yes it takes longer, but in my personal experience it worked. I dont know why, I suspect it has to do with it flashing more than just the modem, but it did for me. I dont have these problems anymore so....
End of my contribution. Just discuss here, not in every development thread for opo on xda endlessly please.
Developer advice. Refer all q's of this nature to this thread.
Click to expand...
Click to collapse
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
That weird baseband version is the correct one, no worries.
radium22 said:
Great info! Would you please add a screenshot showing the baseband version? Everything seems to work but my version is starting with ".3.0.c6...". Thanks!
Click to expand...
Click to collapse
Good idea. Done. Now this really is the end of my contribution on this subject.
zaphodbeeb said:
Good idea. Done. Now this really is the end of my contribution on this subject.
Click to expand...
Click to collapse
So first flash the 3rd zip (cm12 nightly)
Then dirty flash the main Rom or whats the next step?
Thank you
The full nightly should be flashed first, then wipe clean in recovery and install your actual rom (or restore).
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
losthilien said:
So, I have been looking at every single rom since xmas and I haven't yet taken the plunge.
I keep hearing about the modem flash, and while I am not scared at any flashing, I am a bit unsure what happens with the modem flash.
Are all the bands in this alpha modem flash? Can I expect my phone to able to make calls and connect to 4G (LTE) / 3G (UMTS and HSPA+) afterwards?
I do apoligize for me being somewhat retarded in this regard..
Click to expand...
Click to collapse
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
I went for number 3. Did a backup of my temasek ROM. Did a full wipe and installed cm nightly. Had full signal and thought great, this is the right modem. Restored my temasek and signal is gone again.
Any idea why? Did I restore too much of my temasek? Boot, system and data.
Thanks
It might just need another reboot after initial restore to reconnect.
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
VQ30DE said:
I seem to have no issues with cell data on the new modem (running CM12 nightly) but the WiFi sucks. Is this part of the modem or the ROM? Frequently disconnects to my home WiFi and range seems worse than CM11. Hopefully this will be fixed in a modem update soon.
Click to expand...
Click to collapse
Not sure what to tell you. I have no WiFi problems. SlimLP ROM
So I just recovered from a hard brick with a dead battery.... it was brutal. I'm looking to do things more carefully going forward. I'd like to keep CM11S as primary. But obviously I want lollipop asap. If I backup CM11S nandroid... wipe clean, flash CM12 nightly for the modem and such, and then clean wipe and restore CM11S to primary from nandroid... will the modem changes that CM12 nightly made persist? I'd like that.... then I could flash some lollipop roms as secondaries and benefit from the modem changes that cm12 made?
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
tobitege said:
The CM11S and the current CM-12 nightlies both contain the full phone partitions when flashing, so when you flash either of them you'll get that version's full modem package.
For MultiRom users a simple trick for this is to add/use a dummy secondary rom and use that one to do these fresh flashes as to save some time (no need for cache rebuilt on your already installed rom etc.). Afterwards that dummy can just be deleted if the space is needed.
Click to expand...
Click to collapse
Top Tip man. I like.:good: I'll include in the OP.
timmaaa said:
Yes, your phone should continue to operate as normal, all services and bands included.
Transmitted via Bacon
---------- Post added at 08:12 AM ---------- Previous post was at 08:11 AM ----------
@zaphodbeeb, valiant effort in trying to stop the flow of modem questions in dev threads! Unfortunately it requires people to search and read and the vast majority are far too lazy for that lol.
Transmitted via Bacon
Click to expand...
Click to collapse
You will notice the subtle message added to my sig also, using simple large letters for those with limited reading abilities.

[Q] Flashing Sprint S5 back to stock ROM fails

I have a Sprint Galaxy S5 that was up to the latest and greatest version of Android (Sprint's version, anyway) the other day (5/19/15). I decided to root and flash a variant of CyanogenMod 12.1 that was highly recommended by some others. The root and ROM flash were successful and uneventful. However, this ROM and many others based on CyanogenMod 12.1 are all experiencing issues with Bluetooth and skipping of audio. This has been mentioned in several other posts recently. Rather than suffer any more with this, I decided to download the latest stock firmware for Sprint S5 and get it back to the way it was before I rooted and flashed it. I downloaded Odin 3.07 and the stock ROM file. I followed what was shown in this post. I csn't seem to get this to work.
Here is the error I get in Odin:
{
"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"
}
Here is the error I see on my phone:
I've been able to flash lots of other ROMs (although they are all based on CM 12.1 with the same Bluetooth bug, so they are not usable for me). I've been able to put MOAR on, and that is working OK, but I would really like to get this back to the way it was. What am I doing wrong? Did I miss something? Have I missed something I should be doing?
Forgot to mention that I am currently running on MOAR v 6.2 OA6.
So moar rom is working? You can't downgrade the firmware if you took the od3 update or whatever the revision is that just came out. They locked out flashing back to previous builds in the latest firmware I've heard.
Interesting. Yes, MOAR is working just fine. I guess, since it's basically the same as stock Samsung, I should just use it. I like the extra tweaks and tools built in to it. But I really liked CM 12.1 (except for the stupid issues with Bluetooth). I guess I'll stick with MOAR until some gets a stable ROM for CM 12.1 or later out. Hopefully that won't be too far off.
What is your baseband version? As @tdunham stated the latest ota killed it from downgrading. So if you arent on OA6 you wont be able to odin that Stock firmware or any other earlier versions. You will have to find the full OC3 tar
May is Motorcycle Awareness Month Sent from my Galaxy Note 3
I have baseband version G900PVPU2BOD3. Does the baseband remain intact, regardless of the ROMs I have flashed?
Baseband changes, but bootloader doesn't. That is why you get a fail in Odin trying to install stock. Its kind of like a locked bootloader per say. Not really locked, but not able to downgrade. All in all the update to OD3 did what it was suppose to do by preventing a "thief" from factory resetting your device. Although that doesnt matter to people like us because we root for reasons and need that option to downgrade
May is Motorcycle Awareness Month Sent from my Galaxy Note 3
So is there any option to get my phone back to the stock ROM I had on it before I started all of this? Is that ROM available somewhere? I don't think I've seen it. I don't mind using MOAR. I had plans for doing some phone swaps after getting a new phone, and my wife will probably end up with mine. I don't necessarily want to give her a phone that has too much tweaking and settings that she won't understand how to use.
grberk said:
So is there any option to get my phone back to the stock ROM I had on it before I started all of this? Is that ROM available somewhere? I don't think I've seen it. I don't mind using MOAR. I had plans for doing some phone swaps after getting a new phone, and my wife will probably end up with mine. I don't necessarily want to give her a phone that has too much tweaking and settings that she won't understand how to use.
Click to expand...
Click to collapse
You've taken the OTA to OD3 if I read that right. As I understand it, as of now at least, you can't downgrade the firmware with OD3.
Edit: What @elwood says. I better go get some coffee
grberk said:
I have a Sprint Galaxy S5 that was up to the latest and greatest version of Android (Sprint's version, anyway) the other day (5/19/15). I decided to root and flash a variant of CyanogenMod 12.1 that was highly recommended by some others. The root and ROM flash were successful and uneventful. However, this ROM and many others based on CyanogenMod 12.1 are all experiencing issues with Bluetooth and skipping of audio. This has been mentioned in several other posts recently. Rather than suffer any more with this, I decided to download the latest stock firmware for Sprint S5 and get it back to the way it was before I rooted and flashed it. I downloaded Odin 3.07 and the stock ROM file. I followed what was shown in this post. I csn't seem to get this to work.
Here is the error I get in Odin:
Here is the error I see on my phone:
I've been able to flash lots of other ROMs (although they are all based on CM 12.1 with the same Bluetooth bug, so they are not usable for me). I've been able to put MOAR on, and that is working OK, but I would really like to get this back to the way it was. What am I doing wrong? Did I miss something? Have I missed something I should be doing?
Click to expand...
Click to collapse
i have same problem i cant restore to stock rom in odin says aboot error no work with OA6,NDK
i havre installed custom recovery and root i can a install a custom rom OA6 ??WIth bootloader OD3 or i need the OD3 restore !!
ENSENADAS said:
i have same problem i cant restore to stock rom in odin says aboot error no work with OA6,NDK
i havre installed custom recovery and root i can a install a custom rom OA6 ??WIth bootloader OD3 or i need the OD3 restore !!
Click to expand...
Click to collapse
There's only 9 other posts here. Didn't you read them to get your Answer?
Ramer said:
There's only 9 other posts here. Didn't you read them to get your Answer?
Click to expand...
Click to collapse
no!!!
ENSENADAS said:
no!!!
Click to expand...
Click to collapse
Oh, ok.
Can we fix this?
Ramer said:
You've taken the OTA to OD3 if I read that right. As I understand it, as of now at least, you can't downgrade the firmware with OD3.
Edit: What @elwood says. I better go get some coffee
Click to expand...
Click to collapse
As I have this exact same issue and would like my phone back on a stock firmware. Is there anyway to flash the current firmware that the sprint device is on and not downgrade? or am i stuck for a while ? ( I'm also on the moar rom and have tried stupidly all the older firmwares... i also tried the s5 sprint oa6 with no luck. Do i need to go even further forward?
Much Appreciated
-Colin
oreo8631 said:
As I have this exact same issue and would like my phone back on a stock firmware. Is there anyway to flash the current firmware that the sprint device is on and not downgrade? or am i stuck for a while ? ( I'm also on the moar rom and have tried stupidly all the older firmwares... i also tried the s5 sprint oa6 with no luck. Do i need to go even further forward?
Much Appreciated
-Colin
Click to expand...
Click to collapse
If you're already on OD3, you can't do anything about it. You can however flash any custom rom from OA6, MOAR 6.2 works just fine with OD3.
Ramer said:
If you're already on OD3, you can't do anything about it. You can however flash any custom rom from OA6, MOAR 6.2 works just fine with OD3.
Click to expand...
Click to collapse
Thank you. Presuming that there is going to be a fix and or firmware update in the future ?
oreo8631 said:
Thank you. Presuming that there is going to be a fix and or firmware update in the future ?
Click to expand...
Click to collapse
No way of knowing, since I was already rooted and on MOAR, I'm still on OA6 firmware and don't plan to change that.
help s5 back to stock
i have a sprint s5 that im trying to flash back to stock. none of the ## codes work on it. so im hoping going back to stock can fix. im rooted on (i think) a stock rom. already factory reset and still im rooted and ## codes dont work. please help me restore this with odin. not sure on odin use either but i gotta try lol
videokid14 said:
i have a sprint s5 that im trying to flash back to stock. none of the ## codes work on it. so im hoping going back to stock can fix. im rooted on (i think) a stock rom. already factory reset and still im rooted and ## codes dont work. please help me restore this with odin. not sure on odin use either but i gotta try lol
Click to expand...
Click to collapse
what baseband are you on?
youdoofus said:
what baseband are you on?
Click to expand...
Click to collapse
hi. sorry i forgot to update this post. i was able to go back to stock by downloading the stock odin file and used odin to flash back and it worked. however now that im stock and rooted again im looking to load moar rom on my s5. if u want to help me??

(ROM) (VZW PORT) 9/17/2015 Stock Rooted 5.1 GPE LMY47O.H9

Stock M8 GPE 5.1 LMY47O.H9 ported for the Verizon variant of the M8​
Modifications made to this ROM are for Verizon network stability, stock boot.img device tree binary was modified to work on CDMA devices, init.d support, selinux permissive and you should not receive any official OTA notifications.
Its recommended to be on the latest Verizon firmware 4.17.605.9
Install: TWRP is recommended
1. Reboot to recovery
2. Wipe/Factory reset if coming from another ROM
3. Flash ROM
4. Reboot
5. Enjoy, First boot will take 5 to 10 minutes
Special notes:
1. If you were using the partition f2fs, you must switch back to ext4 first.
2. Insert Sim when going through the setup wizard. Just hit skip and continue on with the setup.
3. Unknown phone number will show in settings under Sim Status. You can still make and receive calls and your number automatically populates after first reboot.
4. If you have issues with 3g/LTE data hand off, please call Verizon and have them reset/refresh your SIM or signal whatever they do. Maybe even get a new SIM card.
DOWNLOAD:
AFH: https://www.androidfilehost.com/?w=files&flid=39415
Google Drive: https://drive.google.com/open?id=0B_2pYqG5OJVYMkx0bXB4UTRyd00
DevDB: http://forum.xda-developers.com/devdb/project/dl/?id=14457
MD5: d51a76b9c3e0c94e89d48054f4b91a6e
XDA:DevDB Information
Verizon M8 Stock GPE Rom, ROM for the Verizon HTC One (M8)
Contributors
undarated, enewman17
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.17.605.9
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2015-09-17
Created 2015-09-18
Last Updated 2015-09-27
Hey, thanks for porting this over for us!! I've been saying for a while I want pure stock Android. Well, GPE/Nexus, not, you know, AOSP without Google. I like DH's GPE port, but it's got a ton of tweaks and whatnot. I wonder if I will truly enjoy a pure stock experience.
I will test this tomorrow night. Have you had any problems with GPS? Typically, ROMs that are not Sense have a tendency to lose it.
This ROM won't boot on the verizon htc one m8 with latest firmware. I waited twenty minutes to boot. I felt my phone, and it was hot to the core. I turned the phone off and ran another gpe. However, the other worked seamlessly.
I honestly don't understand why this problem happened with my device.
Thank you for this build. I never got the chance to try full stock.
dragontology said:
Hey, thanks for porting this over for us!! I've been saying for a while I want pure stock Android. Well, GPE/Nexus, not, you know, AOSP without Google. I like DH's GPE port, but it's got a ton of tweaks and whatnot. I wonder if I will truly enjoy a pure stock experience.
I will test this tomorrow night. Have you had any problems with GPS? Typically, ROMs that are not Sense have a tendency to lose it.
Click to expand...
Click to collapse
I haven't had any issues with gps dropping out all all. I travel a lot for my job and have been running the same version as posted for the past 5 days straight.
Check out and let me know if you have any issues
Robby_Rimal said:
This ROM won't boot on the verizon htc one m8 with latest firmware. I waited twenty minutes to boot. I felt my phone, and it was hot to the core. I turned the phone off and ran another gpe. However, the other worked seamlessly.
I honestly don't understand why this problem happened with my device.
Thank you for this build. I never got the chance to try full stock.
Click to expand...
Click to collapse
I'm not sure what went wrong. The rom does boot on the Verizon M8. If you check out the screenshots, those are screenshots taken from my phone. The only thing that comes to mind is if you have you have switched to f2fs instead of ext4 which this rom needs. Maybe bad download?!?!? I'm not sure but the rom does boot and run. It does take a while for the rom to boot. It's too early to tell whats going on just yet.
Bootloops on VZW
grislieber said:
Bootloops on VZW
Click to expand...
Click to collapse
What you mean to say is that it bootloops for you. I'm on Verizon as the screenshots clearly show. It takes at least 10 mins before the spinning circles roll into Android and the phone finshes booting. I'm replying to this post by using the same rom.
undarated said:
The only thing that comes to mind is if you have you have switched to f2fs instead of ext4 which this rom needs.
Click to expand...
Click to collapse
Probably be good to point this out in the OP since people using DH's GPE have the ability to use F2FS, albeit his latest release having some issues with it.
whaevr said:
Probably be good to point this out in the OP since people using DH's GPE have the ability to use F2FS, albeit his latest release having some issues with it.
Click to expand...
Click to collapse
undarated said:
What you mean to say is that it bootloops for you. I'm on Verizon as the screenshots clearly show. It takes at least 10 mins before the spinning circles roll into Android and the phone finshes booting. I'm replying to this post by using the same rom.
Click to expand...
Click to collapse
Any chance you might need to be supercid as well, haven't tried to boot this yet but thought I might bring it up as I remember a lot of people were having problems trying to boot DH's lollipop when he first released it because of that.
mattyd3 said:
Any chance you might need to be supercid as well, haven't tried to boot this yet but thought I might bring it up as I remember a lot of people were having problems trying to boot DH's lollipop when he first released it because of that.
Click to expand...
Click to collapse
I didn't supercid myself. I changed everything in the build.prop to match Verizon by removing any other cid and replacing it with our own. I haven't done anything special to get this to boot on my end. I have the usual set of characters. S-off unlocked, bootloader, latest firmware, latest TWRP, and root. Nothing else special at all.
This rom has no mods or anything else that would make it prone to any issues as far as booting up and running on our M8's. It's the same rom the Google put out except with everything needed for Verizon.
There may be some people who are using DH's 5.1 firmware as well which might be causing issues. You recommend being on the 5.0.1 firmware for this, right?
I want to check this out!
Div033 said:
There may be some people who are using DH's 5.1 firmware as well which might be causing issues. You recommend being on the 5.0.1 firmware for this, right?
I want to check this out!
Click to expand...
Click to collapse
I'm using his 5.1 firmware also. I was running his rom prior to porting this over with no issues
Just to clarify, bootloops and endless boot are very different animals. A boot loop loads the Android OS and then reboots automatically, usually instantly. (I once had a bootloop, on another device, that gave me about a minute.) Endless boot means it just doesn't boot. If this is anything like DH's GPE, first boot will take 8 minutes and change. Maybe less as it has fewer apps to optimise for. Legit 20 minutes is endless boot. I'd say to give up after 12-15.
I wonder if maybe using another kernel might work? I don't know what all needs to be changed to get an international ROM to work on an American phone, but I'd guess the kernel would be one of them.
Just speculating as I haven't tried it yet.
Sorry for late response.
But in my case, I have the latest fw for the verizon htc one m8.
I was NOT saying it does not boot on "THE" HTC One M8. I was trying to say it didn't boot on MY phone. Sorry for the confusion.
The Rom would not boot, as dragontology said, I have the endless boot. The phone was hot and wasn't responding. The boot animation was working but was on for about twenty to thirty minutes until I stopped it.
I clean flashed the rom. I am not running digital high's 5.1 firmware.
Please, I hope that I did something wrong because I really want to try stock GPE.
Thank you DEV for your hard work.
EDIT: I am also not supercid.
---------- Post added at 11:45 PM ---------- Previous post was at 11:28 PM ----------
Actually the reported download size exceeds 577mbs. I will try to flash within the next two hours.
Sorry...
Is there any way to get Hotspot working? I have unlimited and need it.
Thanks
Robby_Rimal said:
Sorry for late response.
But in my case, I have the latest fw for the verizon htc one m8.
I was NOT saying it does not boot on "THE" HTC One M8. I was trying to say it didn't boot on MY phone. Sorry for the confusion.
The Rom would not boot, as dragontology said, I have the endless boot. The phone was hot and wasn't responding. The boot animation was working but was on for about twenty to thirty minutes until I stopped it.
I clean flashed the rom. I am not running digital high's 5.1 firmware.
Please, I hope that I did something wrong because I really want to try stock GPE.
Thank you DEV for your hard work.
EDIT: I am also not supercid.
---------- Post added at 11:45 PM ---------- Previous post was at 11:28 PM ----------
Actually the reported download size exceeds 577mbs. I will try to flash within the next two hours.
Sorry...
Click to expand...
Click to collapse
I honestly have no idea why the rom isn't booting for you guys other than whats been mentioned. The kernel is the exact same one that came in the original rom. I didn't change it either. Honestly, when testing the rom before porting it, all I did was make the changes in the build.prop for Verizon. It's actually a straight forward port. It was a lot easier than it was coming for older JTC devices that i ported roms for.
cuban11182 said:
Is there any way to get Hotspot working? I have unlimited and need it.
Thanks
Click to expand...
Click to collapse
Hotspot is already unlocked by default. It is under Settings, More and Tethering & portable hotspot.
Maybe someone who has successfully flashed the rom will chime in. I can't be the only one!!
undarated said:
Maybe someone who has successfully flashed the rom will chime in. I can't be the only one!!
Click to expand...
Click to collapse
I just flashed it successfully this afternoon, still setting things up (I've never had to install xposed on 5.1 before, had to figure it out). VZW, DH's 5.1 firmware (came from his Rom), ext4 everything. First boot took about 6 min and I haven't had a problem yet.
My only question so far is does this come with a camera? Maybe I'm blind. If so, does it work with duo effects?
cntryby429 said:
I just flashed it successfully this afternoon, still setting things up (I've never had to install xposed on 5.1 before, had to figure it out). VZW, DH's 5.1 firmware (came from his Rom), ext4 everything. First boot took about 6 min and I haven't had a problem yet.
My only question so far is does this come with a camera? Maybe I'm blind. If so, does it work with duo effects?
Click to expand...
Click to collapse
Whew, Glad you got it to work brother. Duo camera? Im not sure. there is a camera app. It's the stock google camera. Should be on the bottom right of the launcher. I'll check on duo camera.
UPDATE: Just took a picture and went to edit it. it had the option of HTC photo edit and photos. I picked HTC photo edit and it had the options for UFocus and Dimension Plus under effects. Hope thats what your looking for.
Alright, sorry I just got back. Yes, the Rom booted perfectly. It is running buttery smooth!!! Sorry man...
I never get good downloads with MEGA. It always looks better but does something weird.
Downloaded the second time with Google Drive. This time the Rom flashed.
Hey undarated, don't worry man. This thing works perfectly!

[BS_FREE_Lollipop_5.0_Rom_BOK3_Based]

This is a modified version of @jrkruse stock BOK3 deodexed ROM with all(or most) of the stock BS removed.
This BS_free ROM does not have two different versions like his previous build. I left only the Samsung apps needed for UPSM and HD calling to work.
INSTRUCTIONS:
I've included the links needed if you want to use xposed and Viper4Android. If you chose not to use these features, then skip them in the flashing process.
I personally prefer using safestrap when clean flashing a ROM, but you can use flashfire if you must.
1) WIPE EVERYTHING!
2) Flash No_BS ROM
3) Flash Extra toggles
4) Flash No_Bootloader_Rooting_Tools_For_S5_Lollipop_V3.zip
5) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
6) Flash Viper Policy
7) Flash Viper4Android
8) Flash BOK3 Firmware without bootloader
9) After first boot, open up Viper4Android and install the driver. Note: Sometimes it takes 2-3 times before the driver will install.
I have confirmed that @jrkruse 5-way reboot with Safestrap works on this ROM!!! If you want to use it, add it to the end of the flashing list. 5Way_Safestrap_Reboot_PM. As a side note, if you use 4-way reboot in Wanam Xposed, then that feature needs to be disabled for 5-way reboot to work.
The ROM should boot in about 8 minutes. The music app will force close everytime the device reboots, but it does work normally.
Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
NO_BS_BOK3_ROM_DEODEXED.zip
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.
Update: NO_BS_BOK3_ROM_DEODEXED_V3.zip is now available. The flashing process is the same. I updated busybox and removed SBrowser. I also implemented the signature verification fix by @jrkruse, along with default animation scales set to 0.5x.
Update: NO_BS_BOK3_ROM_DEODEXED_V4 is now available. The flashing process is the same. I updated all apps, except for YouTube(xposed purposes). I added the missing VPN apk as well. Let me know if there is any other issues with VPN related settings.
Update: NO_BS_BOK3_ROM_DEODEXED_V5 is now available. The flashing process is the same. I updated all apps. I added the headphone app notification, voicenote, and SPrintSpooler. I don't use voicenote or SPrint, so let me know if there are any issues with these apps.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.
I am looking forward in seeing how this Rom is doing.
Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?
Snoopy679 said:
Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?
Click to expand...
Click to collapse
First and last will do just fine.
Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.
jjdavis699 said:
Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.
Click to expand...
Click to collapse
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?
CVertigo1 said:
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?
Click to expand...
Click to collapse
That's the one.
I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay
CVertigo1 said:
First and last will do just fine.
Click to expand...
Click to collapse
do i need to do a clean install or just flash over @jrkruse work that i am currently using?
[VZW_Stock Based TW Rom][5.0 Lollipop BOK3 Build Deodexed] by @jrkruse ?
I dirty flashed this over his stock BOK3 and it worked, so you should be good.
CVertigo1 said:
I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay
Click to expand...
Click to collapse
I actually tried that already. It's honestly not great. Oh well. Maybe if I could figure out a way to strip 3minit...
I fell in love with motion features when someone stole my moto g and I had to pick up a Lumia 640. Great phone, but not an android
I'm on BS_FREE_BOG5_GOOGLE_V2_Deodexed and just updated with @jkruse New Root Tools For S5 Lollipop V6. Already enabled Lollipop Safestrap Recovery again and Flashed Most Current OG5 Firmware_No_Bootloader and current OG5_Kernel. Can I just use that and wipe everything flash this aside from 3Minit Battery without losing Root?
Sent from my SM-G900V using Tapatalk
Just to be clear, are you asking if you can run this on BOG5 firmware?
CVertigo1 said:
Just to be clear, are you asking if you can run this on BOG5 firmware?
Click to expand...
Click to collapse
No, I mean using the V6 Root Tools instead of the V3 as indicated in your directions...
Also, I'm hoping that with a new install I will regain ability to work with Accessibility Options in Settings.
Idk if it makes a difference but I have Original GS5 Rooted, never taken OTA, always ONLY used XDA sources for ROM/Firmware/Kernels.
Sent from my SM-G900V using Tapatalk
My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.
CVertigo1 said:
My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.
Click to expand...
Click to collapse
Ok but all the same, I'm trying to avoid another 300mb DL if I can. As long as it is the same stuff then that's all I need to know.
Sent from my SM-G900V using Tapatalk
Version 2 is now available in the OP.
Universal BS ROM
i would like to know if this BS rom is able to be used on any S5 Carriers or would you consider it in the near future making this a universal rom for other carriers to please. my wife is a T-mobile person and she love the work that you have done here. and is asking me to ask this question. i thank you in advance for your reply.:good:
Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.[/QUOTE]
How did you remove the verizon boot animation? id rather not flash this again cause i just got my stuff all installed.
CVertigo1 said:
Version 2 is now available in the OP.
Click to expand...
Click to collapse
I Flashed it last night with @jkruse's No Bootloader V6 Tools and it worked just fine. I also, noticed that my Accessibility Settings works now and a couple other things were fixed as well. I did have a hard time Restoring Poweramp Music Player - I had to reinstall from Play Store but otherwise seems to be working great!
Sent from my SM-G900V using Tapatalk

[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.

Categories

Resources