Related
Before i begin the actual topic, i feel like i need to share a story. a long, complicated story.
I feel like i can't go willy-nilly flashing things anymore. the USB cable (which btw is OEM) from my fassy is starting to go bad. odin recognizes it 1 out of 3 times, and every time i try to go back to stock, the operation fails half-way through. every other cable i've tried worked just fine, and i reinstalled samsung drivers four times. i believe i also had to reinstall windows at one point (not because of odin, i think something else broke/died) and that didn't help either. so, basically, if i flash a ROM, it has to be like perfect until i can borrow a cable.
a few nights ago, after deciding cm10.1 was too RAM-hungry for daily usage, i borrowed a cable and restored back to stock EH03 firmware. and let's face it, EH03 isn't the best thing ever, but it's usable. but i may go to jelly bean again because touchwiz is bad for your health
after discovering devil kernel (and getting some confirmation from udev that you need devil to properly get by on cm10.1), i have some questions about it:
1. from where should i download and flash it: DerTeufel's site or hhp's dev-host?
2. should i bother with Voodoo Color on jellybean?
3. at what RAM setting does it break 720p recording (as stated on DT's site)?
4. what other features should i know about that could possibly break everything?
by the way, i'm not really a n00b to android. i have a broken nook tablet and an lg vortex that went in the pool
skepticmisfit said:
Before i begin the actual topic, i feel like i need to share a story. a long, complicated story.
I feel like i can't go willy-nilly flashing things anymore. the USB cable (which btw is OEM) from my fassy is starting to go bad. odin recognizes it 1 out of 3 times, and every time i try to go back to stock, the operation fails half-way through. every other cable i've tried worked just fine, and i reinstalled samsung drivers four times. i believe i also had to reinstall windows at one point (not because of odin, i think something else broke/died) and that didn't help either. so, basically, if i flash a ROM, it has to be like perfect until i can borrow a cable.
a few nights ago, after deciding cm10.1 was too RAM-hungry for daily usage, i borrowed a cable and restored back to stock EH03 firmware. and let's face it, EH03 isn't the best thing ever, but it's usable. but i may go to jelly bean again because touchwiz is bad for your health
after discovering devil kernel (and getting some confirmation from udev that you need devil to properly get by on cm10.1), i have some questions about it:
1. from where should i download and flash it: DerTeufel's site or hhp's dev-host?
2. should i bother with Voodoo Color on jellybean?
3. at what RAM setting does it break 720p recording (as stated on DT's site)?
4. what other features should i know about that could possibly break everything?
by the way, i'm not really a n00b to android. i have a broken nook tablet and an lg vortex that went in the pool
Click to expand...
Click to collapse
You do not need devil to get on 1.cm10.1 cm has a built in kernel. 2.Voodoo kernel color is available for 4.2.2.
3.The max mem setting.
HOPE I HELPED
Sent from my SCH-I500 using Tapatalk 2
@skepticmisfit
1. from where should i download and flash it: DerTeufel's site or hhp's dev-host?
DT site does not have kernels for current 4.2.2 ROMs...
My kernel thread does
http://forum.xda-developers.com/showthread.php?t=2149067
2. should i bother with Voodoo Color on jellybean?
Don't see need for it but i have run this setting before and it looks great
From inside your galaxy s settings menu, (different ROMs put this in diff places)
View attachment 2167214
View attachment 2167220
3. at what RAM setting does it break 720p recording (as stated on DT's site)?
The 402 setting, but there is a patch if you search - hugemem patch - or - 720p video
-
http://forum.xda-developers.com/showthread.php?t=1815849
4. what other features should i know about that could possibly break everything?
Read my whole kernel thread post #1
Tons of info/tips
Also read the pages of the ROMs , it's the only way to learn.
...
Give a man a fish, and you feed him for a day; show him how to catch fish, and you feed him for a lifetime.
...
...
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
I am in NO WAY affiliated with any of the ROM developers mentioned below nor am I a developer at all. I discovered this by trial and error and decided to share with the community. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE!!!!!!!!!!!!!!! Everything mentioned worked for me and me alone. I will NOT guarantee it will work for you. I cannot offer any support concerning why it will not work for you and NEITHER DOES THE DEVS AND THEIR VZW ROMs!!!! SO DO NOT CLOG THEIR THREADS WITH QUESTIONS ABOUT WHY THEIR ROM WON'T WORK WITH YOUR SPRINT NOTE 3!!!!!
THIS IS FOR 4.4.X ONLY!!! I am currently on NC5 baseband so I have no idea if it will work with NH7. It should, but again, I can only speak for me and my setup. SMS, MMS (with 3rd party app to send possibly) and GPS all work for me. Calls are working as well.
EDIT: Ok folks, I have decided to go ahead and post the how to anyway even though I have gotten no response from any of the devs of the Verizon ROMs mentioned below. I assume they are working on new projects and do not have time to mess with this discovery. They also do this for free and have lives to live just like the rest of us. If at any time they want me to remove this I will, purely out of respect for what they have done for all of us. With that in mind, THE DEVS HAVE NO TIME TO SUPPORT THIS SO PLEASE DO NOT CLOG UP THEIR THREADS WITH QUESTIONS RELATED TO THEIR VZW ROMS WORKING ON SPRINT DEVICES!
What you will need: A rooted N900P Note 3 device with a custom recovery installed. I am currently using the latest Philz Recovery so I cannot say for sure if using TWRP will cause this not to work on your device. I don't think it will matter, but to be safe I can only speak for Philz Recovery right now.
If you are on TWRP and want to switch to Philz (many have suggested doing so regardless if you try this or not) keep in mind Philz is not being updated now ( I think ) so the latest build for KitKat is 6.12.9 as far as I know and can be found HERE for the N900P. If you don't know how to change recoveries you probably shouldn't be trying this at all. Research it and you will find out how to do it. Or ask around. You will also need to use a 3rd party MMS app possibly to send MMS messages. On Eclipse it seems to work using the stock Messenger, but on Alliance I had to use Textra to send MMS.
Step 1: BACK UP YOUR CURRENT SETUP!!!! I cannot stress how important this is with ANY ROM flashing or file changing. I have been caught with my pants down before and it really sucks when you have to Odin back to stock because you did not do a Nandroid backup. That is the main purpose of having a custom recovery like Philz or TWRP or CWM is to completely back up your device. Most or all offer EFS backups as well. Also keep a copy of said backup on an external device in case you accidentally wipe your EXT card. Don't think it's not possible, I have done it on other devices because I thought I was cool and could wipe real fast and flash.
Step 2: Acquire the stock kernel for your build/baseband ( Mine is NC5 ) in a flashable .zip. The NCS stock kernel can be found HERE OR you can use Lean Kernel 3.10 ( which I am using) that can be found HERE. MAKE SURE YOU GRAB THE HTLESPR version!!!
Step 3: Download the Verizon Touchwiz ROM of your choice. I have successfully tested this on Eclipse and Alliance. Eclipse can be found HERE Make sure you use the correct build ( 4.4.X ) because it needs to match your baseband. In other words, if you are currently on 4.4.2 or 4.4.4 use the same ROM build that they offer. Eclipse 2.0.1 is what I am using. Alliance ROM is HERE Those are the only 2 I have tried thus far. Experiment if you dare, but the others should work as well ( in theory).
Step 4: Grab the flashable app APN Backup and Restore provided HERE THANKS TO FREEZA!!!! You will need this to get the Sprint APNs on your device. More on how do do this later.
Step 5: Take a deep breath. While still on your Sprint ROM, update your PRL and Profile for good measure because those options will not be in settings on the VZW ROMs. Relax, it will be ok.
Step 6: Boot into recovery, do a full wipe like you would any other time flashing a new ROM. Flash the ROM of choice, then flash the Sprint kernel of choice. If you do not get any errors, reboot system and wait...........and wait some more. It will take a few min for either ROM to boot. If you see the Eclipse or Alliance splash screen (boot animation) you are probably ok. Do not panic at the 3 min mark and shut down. Just let it do it's thing. You should eventually see the beginning setup screen. If after 8-10 min you still are seeing the animation it probably is in a bootloop. It may not work but you can simply power down and boot back into recovery and restore your backup, or try again flashing the kernel first, then ROM, then kernel again then boot into system and wait again. Just use some patience.
Step 7: If you made it to this step, congrats, you have booted a VZW ROM onto your Sprint Note 3. But we have more to do. After you set up wifi and gone through the setup menu you may see some Verizon related errors pop up. Just ignore them for now. Those apps can be frozen using TiBu after completely done as a cleanup measure. Boot back into recovery ( On Eclipse you will have to do this using vol up/home/power buttons because there is no 4 way reboot menu. This can be added with Xposed and Wanam later as well). Flash the APN Backup and Restore app ( this could also be done when you flashed the ROM I suppose) and reboot. which will put the APN backup & restore app into your /system/app directory and the SprintAPNxXML file onto your sdcard. Once done installing, boot back up and launch the application, Ignore the warning screen you get from first launch, then press menu and select "Disable ICS check." Once done, exit the app and load it again, then choose "Delete APNs" and select yes to the following prompt. Once done, go ahead and tap Restore APNs, and select the SprintAPNsXML from the prompt and select no to the duplicate check. IF THIS DOES NOT WORK THE FIRST TIME- Move the app from /system/app directory to /system/priv-app/ directory and change permissions to rwx/rwx/rwx and reboot. Then try to Delete APN, then try to Add APNs using the provided SprintAPNxXML file in the app. This will add Sprint APNs.
Step 8: Go into settings/more settings/Mobile Networks/Access Point Names and choose the appropriate one for your area. I chose APN2 LTE Internet n.ispsn. You should now have data icon showing. This worked for me, hopefully it worked for you. I have seen it switch between LTE and 3G so I know it is handing off correctly. Make sure Network Mode is CDMA/LTE/EVDO as well. I haven't tested on the road yet, but will tonight. But it has been working flawlessly for me on local towers.
Step 9: You will need to add Sprint apps you were using, including voicemail. Install Titanium Backup and freeze Verizon related apps if you want. Also you will notice in settings your phone will show to be a N900V instead of N900P due to the Verizon ROM. Don't panic.
Step 10: Profit! At this point you should be able to tinker with the ROMs according to what the threads offer. I know Eclipse has it's own app to customize some things. But Xposed will work as well. I have no idea if Hotspot works or any of that stuff, I do not use it. Alliance has a ton of customization settings and apps built in, including themes. Some minor tweaks haven't worked, but most have. Eclipse has actual AOSP functionality baked in. ENJOY!! I will try to answer as many questions as i can, but again, please DO NOT clog up the threads of those great ROMs with questions, the devs do not, as far as I know, support this method and will not be able to help you with your Sprint device.
EDIT: When you connect to your PC via USB for the first time you may have to toggle MTP on and off to get it to be recognized in Explorer. It will most likely say N900V when you get connected. Also on Alliance a couple of Verizon apps will try to install on your PC. You can cancel them.
Screenshots
MUCH THANKS!!!
Sprint side: Freeza for the APN Backup and Restore app as well as all you have done for the Sprint Note 3!! LMMT for the NC5 kernel thread! Phil3759 for Philz Recovery for the N900P
Verizon Side: Nitroglycerine33 for all he has done for the community. My first attempt at flashing was an Eclipse ROM. Cannot say enough about what he has done! Beanstown106 for the hard work on all the Verizon devices and now along with Team Alliance they continue to dominate!
Multiple Devices: Imoseyon for his great Lean Kernels!! I have run them on every device so far. They just get better and better.
All the devs on all the devices deserve a huge thanks from all of us! Without them none of this would be possible!!
this would be cool to know, and give us more choices at ROM flashing time
Is it me or is XDA running real slow today?? Even on Tapatalk.
Anyway, so far I have SMS, MMS and GPS working smooth. Really was simple. No need to decompile or change the ROM itself. As long as the bootloaders match (4.4.2 to 4.4.2 etc) it works. Thanks to an earlier post by Freeza dealing with APN restore everything works thus far. Really hope Nitro gives me the go ahead to create a thread or at least post a how to with links to his site. If you want real AOSP feel on a TW ROM, Eclipse is the way to go. I ran this all the time on my VZW Note 3.
Also will be trying the same with a couple of other VZW ROMs I once loved as well. Stay tuned. :good:
Looks like I will have to post the How To here anyway so I am testing another VZW ROM now (Alliance) and if all goes well I will add the directions to this thread in the OP.
All the way to Chicago and back with no data issues. Have a hard time believing nobody knew we could do this.
Real_JESRadio said:
All the way to Chicago and back with no data issues. Have a hard time believing nobody knew we could do this.
Click to expand...
Click to collapse
I had no clue! I knew the devices were very similar but figured if it were possible to use VZW ROMs across devices, I'd have started months ago! Thanks for the How To, I'll be giving it a shot this evening. Cheers! :beer:
Sent from my SM-G900P using XDA Free mobile app
sixshooterz said:
I had no clue! I knew the devices were very similar but figured if it were possible to use VZW ROMs across devices, I'd have started months ago! Thanks for the How To, I'll be giving it a shot this evening. Cheers! [emoji481]
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Cool. Hope it goes well. Must be the CDMA thing. At least it gives us more options. Eclipse is working so good I can't get away from it lol
Jasmine 2.4.1 works
---------- Post added at 07:23 PM ---------- Previous post was at 07:22 PM ----------
Hyperdrive RLS8
Vzw lte b4 on/off
are you able to get new LTE Bands (4 ,13) so that n900p can operate on verizon network on MVNO?
or are you able to VZW LTE B4 ON/OFF to enable band 4 on?
This sounds awesome! Thank you for posting! I will have to try this out this weekend.
Latest one I tried was vn Rom 7.2 and Norma beta 6 both good.
Sorry these 2 are not Verizon but are for 9005 and they do work.
Anyone flash T-Mobile roms on this phone?
twisteddroid said:
Anyone flash T-Mobile roms on this phone?
Click to expand...
Click to collapse
Ive flashed this rom selecting the tmobile version in aroma runs with no problems just no data and messaging
I have a Samsung Galaxy S III that I purchased on eBay. It have TWRP on it, and I know absolutely nothing about it except how to open it and get back to the phone. I'm looking for someone who can be patient enough to answer questions and give advice
Ok, to help you with this, in case you haven't fully understood TWRP yet.
It is a very powerful tool that has many features. It can create(backup button in TWRP) and restore(restore button in TWRP) backups(most important feature), it can save those backups to whatever storage location you choose, you have to find the option and select where you want the backup to be stored. You can also choose to backup other partitions along with the default partitions.
It can install(Install button in TWRP) various recovery flashable .zip files including ROMs, Kernels, Modems, newer recoveries, and various other mods/tweaks such as the Xposed framework. It can flash .img files also, provided those .img files are for your device.
It has the ability to wipe(format) the various partitions on the device to clear all data in the selected partition(s), these include the normal wipes when flashing ROMs and such, To do the normal wipes, select the Wipe option in TWRP, you'll see at the top it says Factory reset/wipe data, wipe cache partition and wipe dalvik/ART cache(newer ROM and recoveries use ART, dalvik is older stuff(swipe the slider to wipe). In addition to the normal wipes there are the advanced wipes(select Wipe option, then select Advanced Wipe), typically the advanced wipes are only used when doing a "clean install", it is used to wipe only the System partition and the Data partition to clear any junk that might cause issues with a new ROM you want to use, some ROMs even require a system wipe/clean install to use the ROM. You must be careful when using advanced wipes, if you wipe the wrong thing you'll be screwed. To be safe, only wipe System, Data, Cache, Dalvik/ART, and maybe internal storage(this erases everything you have on internal such as pictures, other media and other downloaded content). Also, when you wipe system partition it removes your OS completely and will have to be flashed with a ROM before rebooting, if you reboot without flashing you'll have nothing to boot to and in some cases it is difficult to revive the device.
It has a file manager that you can use to browse through the folders and files on your device while in recovery.
It can be used to connect the device to ADB where you can do all manner of things with the device. ADB can be used to boot the device to whatever mode you want, it can be used to push or pull files to and from the device, it can be used to capture logcats from the device that give technical live data of what the device is doing below all the layers of software to pinpoint bugs and issues. ADB is used to flash .img files to the device and even pull .imgs from the device using the dd command line, it has many, many things it can do, its all pretty advanced though.
There are other minor, rarely used features as well such as fix permissions, mount and unmount various partitions, etc. You can learn all of them by googling the various features to find descriptions of them.
If you have questions, just ask.
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you again
{
"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"
}
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you againView attachment 3891814
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
You should be able to flash any of the sprint S3(d2spr) ROMs, recoveries, kernels and mods for d2spr and of course the general mods that can be used by virtually any device such as the Xposed framework for ARMv7 devices. I have an S3 that uses the (d2vzw) stuff so I can help you a lot with your S3.
Actually all of the US variant S3(d2vzw, d2spr, d2att, d2usc, d2tmo, etc..)devices can use the d2lte ROMs, on top of that, the d2 devices can all flash each others ROMs without harming the device, they just won't have signal or buttons will be backwards and little things like that, the S3 ROMs can easily be converted from one device to another, the d2 devices are 95% the same.
You could easily flash the newest TWRP and then choose a d2spr lollipop or marshmallow ROM from the Sprint S3 forum as these are the most up to date and readily available ROMs, there's very little support for Kit Kat and older stuff.
And of course, you could always go back to full stock with no root or TWRP if you just want the device to work and would rather avoid all of this custom stuff and its complexities.
For that you just need to do a google search for:
"Return to stock (your model number)"
Or you can go to Sammobile .com or samsung-updates .com and use your model number to find the stock firmware for your device, download it then download the newest version of Odin and install it on PC then boot your phone to download mode(volume down+home+power, press up at the caution screen to enter download mode), connect to Odin, if you get a blue or yellow comm# box you're connected. Click the AP button then browse to your stock firmware .tar.md5 file, select it, back in Odin click start and it will flash the device and reboot into the restored stock firmware, sometimes it bootloops and you have to boot to stock recovery(volume up+home+power) then factory reset and wipe cache in stock recovery then reboot.
I can help you any direction you want to go, just say the word and I'll get you there. Do you want custom or stock? If you want custom, do you want Kit Kat(4.4.x) lollipop(5.x)or marshmallow(6.x), maybe even a Nougat(7.0) ROM?
Droidriven said:
You should be able to flash any of the sprint S3(d2spr) ROMs, recoveries, kernels and mods for d2spr and of course the general mods that can be used by virtually any device such as the Xposed framework for ARMv7 devices. I have an S3 that uses the (d2vzw) stuff so I can help you a lot with your S3.
Actually all of the US variant S3(d2vzw, d2spr, d2att, d2usc, d2tmo, etc..)devices can use the d2lte ROMs, on top of that, the d2 devices can all flash each others ROMs without harming the device, they just won't have signal or buttons will be backwards and little things like that, the S3 ROMs can easily be converted from one device to another, the d2 devices are 95% the same.
You could easily flash the newest TWRP and then choose a d2spr lollipop or marshmallow ROM from the Sprint S3 forum as these are the most up to date and readily available ROMs, there's very little support for Kit Kat and older stuff.
And of course, you could always go back to full stock with no root or TWRP if you just want the device to work and would rather avoid all of this custom stuff and its complexities.
For that you just need to do a google search for:
"Return to stock (your model number)"
Or you can go to Sammobile .com or samsung-updates .com and use your model number to find the stock firmware for your device, download it then download the newest version of Odin and install it on PC then boot your phone to download mode(volume down+home+power, press up at the caution screen to enter download mode), connect to Odin, if you get a blue or yellow comm# box you're connected. Click the AP button then browse to your stock firmware .tar.md5 file, select it, back in Odin click start and it will flash the device and reboot into the restored stock firmware, sometimes it bootloops and you have to boot to stock recovery(volume up+home+power) then factory reset and wipe cache in stock recovery then reboot.
I can help you any direction you want to go, just say the word and I'll get you there. Do you want custom or stock? If you want custom, do you want Kit Kat(4.4.x) lollipop(5.x)or marshmallow(6.x), maybe even a Nougat(7.0) ROM?
Click to expand...
Click to collapse
Wow, you are my hero! I don't know how to thank you enough.
First off, I promise I have put in lots of work on my own trying to find answers. Also, I may be underestimating my own understanding.
As far as ROMs, I haven't worked this hard to give up now! Not only do I want custom, I want to know what kernel does, what a governor does, what mods are. I think everyone else thought I wanted to be told what system to install while I only wanted to be educated so I could decide for myself. Basically, I'm asking for a teacher
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Where were you 4 months ago lol. I searched and begged and googled this with no answers. I didn't know anything about ROMs or kernals or recovery until this phone wanted to update. I followed the instructions and found myself in TWRP and thought my phone had been infected with a virus. That was around October 2015. It took me months more to find XDA, months more to figure out where to post a question, and months more to get information. I manged to flash the MOAR rom in July, but didn't see that it was from 2012, so the developer won't answer any questions I have. I couldn't figure out how to restore what I had before and subsequently deleted the files from my exSd.
My frustration is that I didn't get into this because I was interested in it or knew about the workings of operating systems and wanted to make my phone awesome. I thought I had to in order to make it work right. I was seduced by ideas of having an awesome phone when I read about custom ROMs while trying to find one. The problem is, I don't understand the power I have in order to use it.
Sorry to ramble. I do thank you for your information. I also welcome ( beg for) any help or suggestions about what works with what devices.
Thank you againView attachment 3891814
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Mablemae said:
Wow, you are my hero! I don't know how to thank you enough.
First off, I promise I have put in lots of work on my own trying to find answers. Also, I may be underestimating my own understanding.
As far as ROMs, I haven't worked this hard to give up now! Not only do I want custom, I want to know what kernel does, what a governor does, what mods are. I think everyone else thought I wanted to be told what system to install while I only wanted to be educated so I could decide for myself. Basically, I'm asking for a teacher
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Thank you. My dilemma in finding one is that I read where you need a certain firmware or modem. How do I know if I need it? I looked at the section in my phone that I sent the pic of. Where is the information I need, and how do I know if I can install something?
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Thank you. My dilemma in finding one is that I read where you need a certain firmware or modem. How do I know if I need it? I looked at the section in my phone that I sent the pic of. Where is the information I need, and how do I know if I can install something?
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't know of the d2spr devices requiring flashing a modem. Can you give me a link to see what you're talking about? If not I'll see if I can find what you're talking about. Or I might get in private chat with the d2spr guys on the OctOS team to see if they know.
You do know that there is a d2spr device and the d2spr refresh device, don't you? You can't use the d2spr refresh stuff, that's a different variant. I think it is the one with the certain modem because it is a tri band device I think.
Droidriven said:
I don't know of the d2spr devices requiring flashing a modem. Can you give me a link to see what you're talking about? If not I'll see if I can find what you're talking about. Or I might get in private chat with the d2spr guys on the OctOS team to see if they know.
You do know that there is a d2spr device and the d2spr refresh device, don't you? You can't use the d2spr refresh stuff, that's a different variant. I think it is the one with the certain modem because it is a tri band device I think.
Click to expand...
Click to collapse
I am going to try out the one you sent me the link for. If I think I want more bells and whistles, I'll let you know and see what else is available. I have no reason to look elsewhere. I'm just so thankful for your help. Do you have a link where I can send money to your team or an address where I can send a pie? Lol
Sent from my SPH-L710 using XDA-Developers mobile app
Droidriven said:
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Click to expand...
Click to collapse
I just want to be sure I'm doing the right thing. I went to the link you sent and clicked the link for "stable", then "Samsung", then s3 lte, then sprint gs3. I assume that since you have my current phone information to know what I'm running, you gave me something that is compatible and doesn't need me to modify any of my current settings in order to install, but I'm just double checking. Also, how important is gapps if I use titanium to backup any apps I want to carry over? I've never downloaded gapps before a wipe
Sent from my SPH-L710 using XDA-Developers mobile app
Droidriven said:
Here, may I suggest the ROM linked below?
http://forum.xda-developers.com/showthread.php?t=3033797
This is OctOS Marshmallow, OctOS is pretty much the most stable custom available, they don't try to cram it full of every feature they can, it isn't featureless, its just that their focus is stability and not the bells and whistles. I've used OctOS on my d2vzw S3 for 2 years without a single issue. In fact, I've liked the ROM so much I joined the OctOS team as a beta tester(kinda pointless because even the test builds are rock solid, takes the fun out of testing). I've even built a system for one of the developers on the team to use for developing ROMs. Anyway, that's all unimportant.
Try the ROM, I think you'll like it. It requires using the advanced wipes in recovery to wipe System and Data partitions before flashing the ROM to do a "clean install". I'll help you with that if you need it. I hope you enjoy.
---------- Post added at 11:12 AM ---------- Previous post was at 10:56 AM ----------
Kernels are what integrate your hardware with your software, the kernel is what loads all the software that is installed and the kernel has to be made to work with your specific hardware.
Custom kernels can be used to do things like overclock your processor and your graphics processor to increase performance. Governors do just that, they govern how your processor responds to your usage, such as you can set it to run full speed at all times or you can set it to only respond with full speed when you need it. There are different governors and they each perform differently, it just depends on which ones were included in the kernel. I could explain it all but you wouldn't understand it until you've used it a while and gotten the feel for what they do. There are other things you can do with kernels but its pretty technical and you'll probably never use/need most of what it does. The OctOS ROM actually comes with its own Kraken kernel and the Kernel Auditor app built in. Other ROMs don't have their own kernel, they typically use the stock CM kernel. There are also other stand alone kernels for d2spr that you could use, you just have to verify which kernels work with which ROMs(kit kat kernel for kit Kat ROMs, lollipop kernel for lollipop, etc..., some kernels can be used with kit kat, lollipop and marshmallow, you just have to read about each kernel to see what they work with).
Mods are modifications, not all devices can use all mods, mods can be all kinds of things major and minor. A mod can be absolutely any part of a ROM that someone modifies for whatever reason. There isn't any one thing I can put my finger on and say "this is a mod" that would help you understand what they are. Just know that there are mods that only work on specific devices and mods that can be used by many or even all devices, you just have to know which are which.
By the way, I figured you'd stay with custom, everyone does when they get bitten by the android bug, lol.
Click to expand...
Click to collapse
Ok here goes. I'm about to do this. I will be back shortly with how it went either from this phone or my backup phone.
Sent from my SPH-L710 using XDA-Developers mobile app
Mablemae said:
Ok here goes. I'm about to do this. I will be back shortly with how it went either from this phone or my backup phone.
Sent from my SPH-L710 using XDA-Developers mobile app
Click to expand...
Click to collapse
Tell me what you are flashing first and I'll verify it for you if you want.
Droidriven said:
Tell me what you are flashing first and I'll verify it for you if you want.
Click to expand...
Click to collapse
I flashed this and the screen flashed the whole time with the TWRP screen and the file images over it. I could see an "ok" option and pressed it. When I went to reboot, TWRP said there was no os installed, so I went back and wiped and reinstalled MOAR. Now I can't install titanium. I get some kind of error. Did I lose root?
Droidriven said:
Tell me what you are flashing first and I'll verify it for you if you want.
Click to expand...
Click to collapse
I didn't download the md5 file because I didn't see one
Mablemae said:
I didn't download the md5 file because I didn't see one
Click to expand...
Click to collapse
The file may have its own md5 sum attached to it instead of a separate md5.
As for the issue with Titanium Backup, you don't need root to install it but you do need root to restore the stuff you backed up in Titanium Backup.
When I asked about what you flashed, I was asking for links to what you used so I could go there to where you got it and see if its for your device or not and what might need to be done with it to make sure it comes out right, in other words, I'll check to see if requires the modem you spoke of.
If you think you lost root, download SuperSU.zip and flash that in recovery like you did the ROM and you should have root.
When I ask you questions I need the answer, not partial responses. If you don't give me the answers I need about exactly what you're using and what you're doing, it makes understanding any issues you might have a little harder to understand and troubleshoot. Work with me and I'll work with you.
Mablemae said:
I didn't download the md5 file because I didn't see one
Click to expand...
Click to collapse
That screenshot you gave me is not a ROM. That is a flashable zip to fix your APNs so you that your mobile data works.
This should be your ROM.
https://www.teamoctos.com/download/M_release/d2spr/OCT-M-R2-6.0.1-20160812-d2spr.zip
For the gapps you'll need, do a google search for:
Open Gapps
When you get to their page, select ARM(not ARMx64), then select 6.0, then select mini, pico or nano packages then download.
You have to flash the Gapps with your ROM, they are system apps, apps you install aren't system app, they're user apps, different animal. When flashing a ROM different than what you have you can't use Titanium Backup to back up system apps because they won't restore properly in your new ROM, especially when going from one android version to another.
Flash the Gapps and then only restore apps that you downloaded from Playstore.
The link I gave you was to the thread for your ROM, it should the info you need to know to flash it.
By the way, when you flashed and it said you had no OS, that's because of the advanced wipe when you wiped system partition in recovery, I told you that it removes your OS and that you'll have to flash the ROM AFTER doing the wipe, you can't flash and then do the wipe, that wipes what you flashed.
Droidriven said:
That screenshot you gave me is not a ROM. That is a flashable zip to fix your APNs so you that your mobile data works.
This should be your ROM.
https://www.teamoctos.com/download/M_release/d2spr/OCT-M-R2-6.0.1-20160812-d2spr.zip
For the gapps you'll need, do a google search for:
Open Gapps
When you get to their page, select ARM(not ARMx64), then select 6.0, then select mini, pico or nano packages then download.
You have to flash the Gapps with your ROM, they are system apps, apps you install aren't system app, they're user apps, different animal. When flashing a ROM different than what you have you can't use Titanium Backup to back up system apps because they won't restore properly in your new ROM, especially when going from one android version to another.
Flash the Gapps and then only restore apps that you downloaded from Playstore.
The link I gave you was to the thread for your ROM, it should the info you need to know to flash it.
By the way, when you flashed and it said you had no OS, that's because of the advanced wipe when you wiped system partition in recovery, I told you that it removes your OS and that you'll have to flash the ROM AFTER doing the wipe, you can't flash and then do the wipe, that wipes what you flashed.
Click to expand...
Click to collapse
Yes I wiped, then flashed. This is the path I took that got me to what I flashed
http://forum.xda-developers.com/showthread.php?t=3033797.
On the first page in the thread, I found a link that said it was stable and followed it for my phone.
I only backup user apps to titanium because I did read that system apps can cause problems when carried over to a different rom. Sorry about the lack of information.
Mablemae said:
Yes I wiped, then flashed. This is the path I took that got me to what I flashed
http://forum.xda-developers.com/showthread.php?t=3033797.
On the first page in the thread, I found a link that said it was stable and followed it for my phone.
I only backup user apps to titanium because I did read that system apps can cause problems when carried over to a different rom. Sorry about the lack of information.
Click to expand...
Click to collapse
OK, I'll check out some details and see what might have happened when you flashed. Doing the wipes a d then flashing ROM then Gapps should have worked with no issue, let me do some digging to see why it didn't.
Droidriven said:
OK, I'll check out some details and see what might have happened when you flashed. Doing the wipes a d then flashing ROM then Gapps should have worked with no issue, let me do some digging to see why it didn't.
Click to expand...
Click to collapse
Stop digging. The apps started downloading, but I'm going to try what you sent me tonight when I get off
Mablemae said:
Stop digging. The apps started downloading, but I'm going to try what you sent me tonight when I get off
Click to expand...
Click to collapse
Ok, I'm chatting with my OctOS colleagues, some of them have had d2spr, hopefully they remember whether there is anything special you need to do. I have helped others with d2spr but its been a year or more so I don't remember details.
Edit: They do keep coming!
I looked into doing it, and there is no way in hell that I should be a) doing it, and b) unleashing it onto the world. It would be bad.
I only have the one phone to test it on and can't risk messing it up and I don't have the experience to work on it if it didn't come out perfectly.
I expect that it will be the last Sprint ROM released for this phone, We're nearing the end of support, so it would be good to have these final versions "fixed" and available
...on the off chance a few developers will jump right in and cook up a few mega ROMs for us.
DQG1 Root and Xposed (rewritten)
On a related note, I installed stock DQA1 DQG1, using the usual CF Autoroot, battery pull thingy process Odin for the ROM and TWRP, then booting once, booting into recovery, and then installing SuperSU and it rooted fine. No loss of settings or anything else as far as I can tell.
I did have to install the latest versions of the Xposed files. After rooting and custom recovery (TWRP works fine), install XposedInstaller_3.1.4.apk first like any other apk, then go to recovery and install Wanam v87.1-alt-sdk23-arm-custom-build, but everything (Xprivacy, etc.) worked fine. Keep in mind, you HAVE to use the "alt" (see the "alt" in the file name above?) version or else it won't work. Samsung made some changes, blah, blah, blah. Much thanks to Wanam!
New side note: I did do a factory wipe, and even after reinstalling everything, and using a ROM that contains bloatware, I still have like 40% more space on the phone. I truly don't know what happened there.
Anyone have any thoughts as to kernel? I downloaded Emotion r26 RC1, and BeastModeKernel 1.0BETA, but I haven't tried them yet.
EDIT: Emotion r26 RC1 works fine, but it doesn't seem like CPU freqs are ever going to stick.
No surprise that neither Emotion nor BeastModeKernel worked; I haven't seen anything else that may.
Thoughts anyone?
Both kernels are good, emotion has a few more options to tweak but I took an update a month or two ago and run NotEdge ROM fine , I just use SO launcher with it because I like TW, also latest xposed is 86.1 and I wish I could do what your asking but it probably would be just as bad you'll be fine with that ROM I just suggested it has everything u just requested just make a nandroid and do it at home in case you do something wrong you can always ODIN back your firmware
Sent from my HTC One M9 using XDA-Developers mobile app
D'oh!!
Eating a little crow here. So far, there have been two three 742 updates, maybe there will be more. Who knows?
But I edited the title of the first post. Again. Again. 741 times.
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Over a year later, and the still keep coming.
Hmmmm.
I did take another gander around, but it seems that I would need Linux to do it correctly, so I am still opting out of doing it myself.
mictek said:
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Click to expand...
Click to collapse
They all arrive here: https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915P/ eventually.
Hello i got a note 4 Sprint MM 6.0.1 N910PVPU5DQI5 . i am from Argentina, and i bought the phone used from a guy from USA. (i don`t know how but it`s working with the bands here but i dont know if 4g is working, the guy says it works, maybe i don`t have 4g singal in my zone) .
the phone works fine, but has some srpint stuff and ads that bother me. so i flashed TWRP , and now i am looking for any roms and kernels to flash.
for example, is safe to flash this: https://forum.xda-developers.com/note-4-sprint/development/rom-updated-1-14-2017-t3538051
or should i change something first ???.