help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
help guys i know you can
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You will need to give a little more information to get some help.
Please include:
model of your phone
modem/baseband currently on your phone (settings, general,about phone)
firmware version (same location)
recovery installed (if you're currently rooted) or recovery attempting to use
root method being used
flashing steps taken
ROM or ROMs flashed
I know its a long list but it will go a long way towards getting the help you need.
Good luck
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Note 3 sm900p lean kernel now I flashed Cm 11
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
What exactly is your question? I don't actually see what you were trying to do and what went wrong.
One of the biggest problems that people have when trying to flash a 4.4.4-based ROM is that their bootloader is still based on NC5, not NH7. If you want to flash anything newer, you'll have to update your phone to NH7 before flashing a 4.4.4 ROM.
I put together this post when helping another person out on another thread. I think it'll work as a step-by-step guide for you:
I'll explain how to install a custom ROM and some common things to think about/check prior to installing anything:
Installing a Custom ROM
Step 1 - Gather Information
First off, you need to know what version of Android your phone currently is running. This is easily done by looking in the Settings Menu -> General -> About Device.
The Main things we are looking at on this screen are Software Version, Model Number, Android Version, and Baseband Version. I'll explain these (to the best of my knowledge) below:
Software Version:
This is the "type" of Android that you're running. Rather than quoting the entire name, we typically only refer to the last 3 characters (MJ4, NAB, NC5, etc.). Stock Note 3 devices will (most-likely) be running one of 3 different versions of TouchWiz (TW):
MJ4 - This is the last Jellybean version of TW for the Sprint Note 3NAB - This is the first KitKat TW version for the Sprint Note 3NC5 - This is the second KitKat TW version for the Sprint Note 3NH7 - This is the latest KitKat TW version for the Sprint Note 3
The reason that we are concerned with the Software Version is that between the MJ4 and NAB versions, there were major changes. So if you're running MJ4, you will have to do additional steps before flashing a custom ROM based on a newer version. And if you're on NAB or NC5, you will not be able to go back to MJ4, so beware what you're flashing.
For the most part, if you're on NH7, you can flash either a NH7 or NC5 custom ROM, but just read the ROM's FAQ to see if there are any issues with doing so.
Model Number:
Most people don't worry about this, but I always do when looking at a new ROM. The Sprint Note 3 is different from the Verizon Note 3, which is also different from the International Note 3. It's always best to double-check that the ROM you're trying to install is truly meant for your device. This simple check will prevent a LOT of potential issues you'll get when installing a ROM.
Android Version:
This is just an additional check to the Software Version. Always best to know.
Baseband Version:
The Baseband is, unless I'm mistaken, the "kernal" for the phone's cellular and 4G radios. Sometimes upgrading (or downgrading) the Baseband can help with signal strength and reception. Some users have noted that they got better reception on older Baseband versions. I haven't personally looked into it and the reports from other users seem somewhat anecdotal, but it's good to know which Baseband you're on.
The Baseband is independent from the ROM version, so you can run an older Baseband (MJ4 or NAB) on a newer ROM (NC5), and vice-versa.
The last bit of information you need to know is the Bootloader Version. The way to find this information is to reboot your device. When you see the text on the screen, you should look for the Bootloader Version. It'll be a long string of characters, but you're only looking for the last 3 (MJ4, NAB, or NC5).
Once you have all the above information, you should be ready to start the fun process of preparing your phone to flash your first ROM.
Step 2 - Backup your Media
First thing: Backup all of your media to your computer. If there's pictures/music/videos/recordings you don't want to lose, back them up. It's just good practice. Don't lose all your cat pictures because you flashed something and it somehow erased your internal storage. I tend to keep everything of importance on the External Storage, but there are times where even external storage can be wiped, so it's best to back up everything to a PC.
Step 3 - Upgrade your Phone to the latest Stock ROM (NH7)
This only is a MUST applies if you're running an older version and want to install a NH7 ROM. Most continually-developed ROMs are either NC5 or NH7 now, so the first things first: Update your phone to NH7.
Go over to micmar's thread and download the One-Click File. It will remove Root, but don't worry, because when you install a new ROM, it will automatically include root access.
Follow the instructions in his thread and your phone will now be fully upgraded.
At this point, your "About Device" should show the following:
Software Version: N900PVPUCNH7
Android Version: 4.4.4
Baseband Version: N900PVPUCNH7
Reboot your phone and let it sit for a minute so it can get it's bearings.
Step 4 - Install a Custom Recovery
So far, we've been flashing everything in ODIN. Now, we're going to use ODIN one last time to flash a custom recovery, so that you can flash custom ROMs without the need of a computer.
The most-commonly used Custom Recovery is TWRP (XDA Link). You'll want to use the latest version, 2.8.0.
Flash this in ODIN. You should use the "PDA" or the "AP" Slot.
Reboot your phone to make sure it works correctly.
Step 5 - Make a Nandroid Backup of your device
If you don't know what a Nandroid backup is, don't worry. It's basically just taking your phone as is and making a backup of it. In case you make a mistake or flash a bad download of a ROM, this allows you to restore your system. I always keep my backups on the External Storage (microSD Card), so in case I have to wipe my internal storage, it's not a big deal. You can also copy the files over to your PC, just to be more paranoind about your nandroid backups (rhyming is fun!).
You do this by restarting into Recovery (power down device, hold down home button and volume up while powering on phone).
Once in TWRP, go to "backup." Make sure the storage selected is "external storage." This screen will have various options of what to backup. I typically choose everything except external storage. Typically, backups range from 1-2 Gigs.
For me, backups typically take 5-10 minutes to do. In my opinion, this is totally worth it, since I can always restore a backup with no issues.
Step 6 - Install a Custom ROM
Once you choose your custom ROM from the Development Section, follow the instructions on the original post to install it. I'll give a general outline of what I do whenever installing a new ROM, but sometimes a custom ROM will have specific instructions, so you want to make sure to read the posts carefully.
Generic Instructions for Installing a ROM:
Download ROM and check the md5
Internet being spotty in my area, I always check the md5 to make sure that the file downloaded correctly. You can check the md5 using this windows program or using a file explorer on your phone like ES File Explorer. I always copy the ROM zip file to my external SDcard.
Reboot to Recovery
Wipe Data, System, Cache, and Dalvik Cache
This is called a "Clean Wipe," meaning it will wipe out your installed Apps and the data associated with them. Some people will claim that "Dirty Flashing" (i.e. not wiping the above) is OK, but I've seen too many apps Force Closing (FC-ing) when dirty flashing. Also, if you dirty-flash and encounter an issue with a ROM, the first piece of advice is to do a clean install. Might as well do that initially and hopefully not run into any issues.
Install the Custom ROM
Pretty straight-forward on how to do this... just click "Install" and then browse to the place your copied the ROM zip file.
Reboot your phone and run through the typical initial start-up information (google account, etc).
Once you get your phone set up the way you like (apps, accounts, wifi passwords, etc), I'd make another Nandroid backup, just so you have one where it's setup with everything you need. This will make any issues less painful, since you'd restore a backup that's already setup.
Step 7 - Further Considerations
If you ever want to try a new ROM, all you have to do is repeat step 6. Beware, though, people easily become flashaholics when they first figure this stuff out.
If you were paying attention to my "Generic Instructions" when installing a ROM, you'd notice that every time you do a Clean Install of a ROM, you lose all your apps... All of your Angry Birds 3-Star levels are gone!
Well, there are ways to get prevent losing that data... One is by "Dirty Flashing" (Not wiping the "system" or "data" partitions before flashing a ROM in TWRP). This is common practice among users here on XDA, but is typically frowned upon by ROM devs. I've noticed that a good number of issues on ROM threads stem from people Dirty Flashing. It typically causes more problems than it solves.
The other way of backup up and restoring app data (prior to wiping) is by using Titanium Backup. I could write up a long post on how to use Titanium Backup (TiBu), but the main things to remember are the following:
White line items are fine to be restored (both Data and Apps).
Restoring Yellow line items is typically OK (Data only).
Restoring system apps or data (red line items in TiBu) is typically a bad idea.
I've been using TiBu for the past 2-3 years and it's typically worked like a charm. Sometimes, when there's a major Android Update (like from JellyBean to KitKat), it can become broken, but the Developer is really responsive and gets it to work within a few weeks. If you upgrade to PRO, you can schedule automatic app backups (I backup all my user apps every night at 3am). You can also restore apps/data from Nandroid Backups (which is great if you do a Nandroid backup but had forgotten to update your TiBu backups).
In Summary
Whew, that was a lot to write... I'm a Structural Engineer, not a Software Engineer, so I don't know the technical side of things like bootloaders or basebands, but hopefully none of the information I provided was false.
Anyways, let me know if you have any problems with the install. I appreciate any feedback!
Click to expand...
Click to collapse
I hope this helps, but please, in the future, write out your question clearly and provide as much information as possible, that way we can help you quickly and efficiently.
Cheers!
-Topher
OK I noticed that thanks again I finally found a 4.4.4 Cm Rom working awesome very little glitch but can deal with I have no way to update without pc
Sent from my SM-N900P using XDA Premium 4 mobile app
Why does titanium backup not save from deletion says no external backup detected
Sent from my SM-N900P using XDA Premium 4 mobile app
No data sorry
Sent from my SM-N900P using XDA Premium 4 mobile app
Running pac man rom Cm no data
Sent from my SM-N900P using XDA Premium 4 mobile app
Thanks
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Running pac man rom Cm no data
Click to expand...
Click to collapse
Ok, you haven't fully answered the questions myself and @jdelano asked you. If you cannot answer these questions, we will be unable to help you.
Phone Model: Note 3 sm900p
Phone Modem/Baseband: Unanswered
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
I am in the process of downloading/installing the PacMan ROM in this thread. The file I will be flashing is the pac_hltespr__20141110-124721.zip and the Gapps modular package from this thread, filename: pa_gapps-modular-full-4.4.4-20141121-signed.zip.
EDIT: By following the steps in my previous post, I was able to install the PacMan ROM with Gapps and all worked well. I had data, root access, and was able to wifi tether... Please answer the questions I asked before, especially what version is your baseband, as I suspect that's the main issue that you have.
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Nc5
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Phone Model: Note 3 sm900p
Phone Modem/Baseband: NC5
Firmware version: Unanswered
Recovery installed: Unanswered
Root Method: Unanswered
Flashing Steps: Unanswered
ROM flashed: CM11, pac man rom (no build number/date given, please provide a link to the thread you flashed from)
Are you a Sprint Customer, or have you flashed your phone to another carrier?
What is the issue you're having: No data when on CM 4.4.4 ROMs.
Click to expand...
Click to collapse
As I stated in my first reply to you, the issue is that your phone is still on the NC5 bootloader. In order for 4.4.4 ROMs to play nicely on your phone, you'll need to update it to NH7. This is also stated in my previous post. You need to follow those instructions to the letter (particularly Step 3) in order to update it. You must use a computer to flash the update file, as Mobile ODIN is not able to update the bootloader. You need to get access to a computer (work, library, friend who owes you $20, someone at Starbucks).
Until you follow those steps, I doubt any 4.4.4 ROM will work correctly on your device.
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
R1000 said:
Exposed frame work not compatible with roms only tw anyone have zip for NH7 u date with root
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the first you've mentioned XPosed Framework... What exactly are you trying to do with it?
I don't know where you've gotten your information from, but I know for a fact that XPosed is compatible with all 4.4.4 AOSP ROMs as well as all TW ROMs. XPosed is NOT compatible with 5.0+ Roms. I'm currently using it on my "daily-driver" ROM, which is based on 4.4.4 AOSP.
R1000 said:
Y'all packing works great little glitchy phone turns on an off but all good all Cm roms I end up with no data I have Phil's recovery beast kernal average gapps had to update su binary any time I flash cm and it changes my recovery sometimes I cannot format SD card or I will loose all files I have no PC even if I use drop box titanium doesn't work the way it use to can save apps from deleting with confirmation so what's a stable cm Rom or slim rom and gapps or do you have knew updated tw rom rooted I have update my boot loader so
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, lets get you to a known platform with your phone so you can use 4.4.4 TW or AOSP ROMs.
#1. Load latest stock firmware and software
[Stock ROM] Odin flashable N900PSPTDNH7Follow the instructions EXACTLY
Now make sure you boot stock NH7, let it get data and update your profile and PRL by doing:
go to Settings -> General -> System Update, then select Update PRL (wait for it to do its thing), then Update Profile (again wait for it.)
Now we know you're on the most current stock software available and we've updated your profile and PRL (preferred roaming list)
#2. Root stock NH7 acquired in step #1
Go here Download philz_touch_6.48.4-hlte.tar.md5 (save it in the same folder you have Odin in from Step #1)Go Download SuperSU-v2.37.zipCopy the zip to your phone's sd cardUse Odin to put philz_touch_6.48.4-hlte.tar.md5 on your phone (same basic steps you used to Odin NH7) - Make sure you UNCHECK rebootOnce odin is finished and you see PASSED on the screen, unplug your phone from your computer then press Volume UP + HOME + POWER and hold all 3 until the phone reboots and you see blue words "Recovery Booting ..." at the top of the screen - Philz recovery will startnow select install zip -> choose zip from /sdcard -> scroll all the way to the bottom and select the SuperSU-v2.37.zip file -> select Yesonce finished press back until you get to the main recovery menu and select Reboot to System
#3. Update SuperSU binaries
Once your rebooted, Open Apps drawer, open SuperSU, say no to disable knox, it will ask about updating binaries, select yes, select normal, wait until it says its finished.Now you are Rooted Stock NH7You can now flash any 4.4.4 TW-NH7 or AOSP hltespr ROM - make sure to follow each Post #1 instructions on the ROM you choose and of course backup before flashing anything new
I hope this gets you to where you want to be, good luck.
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
piaa_nissan said:
Theres a lot of patience being displayed here. One should never start messing with their phone unless they have even the slightest clue what they are doing from the start
Click to expand...
Click to collapse
The amount of patience I am seeing is mind blowing! To the OP...Just some words of advice. I have been a member of XDA for alot of years now and I can tell you that you will get a tremendous amount of help from this community. My only suggestions would be,when looking for help:
1) Be very clear as to the question you are asking.
2) If someone is willing to help you, Give them all of the information that they are asking you for.
3) Punctuation goes a very long way when someone is trying to understand what you are asking. Try using a period to avoid run on sentences.
Please do not take this as anything other then what I have learned over the years to get the best and quickest help!
I hope these guys are able to help you with your issues! :fingers-crossed:
Related
The phone has been working great on Android 4.1.2 as I describe in the thread ( Optimizing [Rom][I605VRAMC3][4.1.2])
Found Here: http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294
EXCEPT NOW, every time I boot the phone, I get a message that says All the APPS are upgrading automatically . I think the problem is related to me Using Titanium Backup to Freeze SDM 1.0 . The reason I froze SDM 1.0 was to stop the Nag from Verizon for a firmware update .
Anyone know what I need to freeze to stop the auto upgrading on every boot? It really slows down the boot time.
Thanks in advance
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
You probably did this already, but double check to make sure Play Store is not set to Auto Update apps. Can. be found in Play Store. settings. I don't believe that freezing SDM would play a role here, but I've been wrong before.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
doctor-cool said:
Thanks , Play Store was set to auto update so I changed it , I just tried your suggestion and I rebooted . I'm still getting the same message while booting: Android is updating.............................................................................
Click to expand...
Click to collapse
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
Hmmmm.... It's probably still working on updating apps that it started working on previous to disabling the auto update.
This might work..... Toggle off your wifi and data, then try going to phone Settings, Application manager, All Apps... then force close the Play Store and wipe the app data. Then open the Play Store again and it should go straight to settings area. Set it to " Do not Auto Update apps " and then back out of Play Store, turn wifi/data back on, and go back into Play Store and sign into the app again/change any other settings back to how you like them . I hope that will stop the auto update.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
For a test,
I cleared data and disabled the Play Store, Turned off data and wifi . REBOOTED I'm still getting the same message while booting: Android is updating.......................................... ...................................
Now I'm thinking the problem is due to me flashing Gapps.
I flashed (HDPI / MDPI / TINY: gapps-jb-20121011-signed.zip) for Android 4.1.1 – 4.1.2 – Jelly Bean, from http://www.teamandroid.COM/gapps/
I probably shouldn't have flashed it on top of the official stock 4.1.2 Verizon ROM. I probably have two version of Gapps on my phone competing with each other. The quickest thing would probable be to re-flash to the OEM [Rom][I605VRAMC3][4.1.2]
doctor-cool said:
Everything worked just like you predicted except when I reboot the phone it says "Android is updating 1,2,3..........................................88 ...................................
Click to expand...
Click to collapse
Ok.... I just realized that this has nothing to do with the Play Store App or updating your apps.... Your actual phone system is optimizing at boot screen.... like this pic, right?
Sent from my SCH-I605 using XDA Premium 4 mobile app
I'm not in any way a developer or expert.... this stuff is just a hobby for me...so please understand these are just my thoughts to hopefully help and not make things worse for you. With that said, I suspect you have an app or script (or something) that is doing something like wiping the Dalvik cache with each reboot, which is triggering your phone to run through the optimization process each time you boot. I am pretty confident this has nothing to do with SDM being frozen. I'm not sure about gapps with stock. Why do you need that if your running stock?
Sent from my SCH-I605 using XDA Premium 4 mobile app
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
doctor-cool said:
Anyhow, What ROM do you recommend ? I'm using my phone to do Wave Accounting and Pay Pal transactions so I cant have down time.
Click to expand...
Click to collapse
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what you're wanting. If you decide to try out JellyBeans Build 22, let me know if you need help with instructions for flashing it. I saved the install instructions for future reference when I flashed it the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
mattnmag said:
Sorry for being off base with my initial thought on your above post... It's been a long week at work and I'm tired.... so that's my excuse...
I hope you get it sorted out with what's causing your phone to upgrade/optimize apps at each reboot. I did a Google search just now and apparently, this is common issue asked on XDA. I found several comments from people saying they think something causes the Dalvik/Cache to get wiped on reboot. I also read where someone reported that flashing Gapps did the same thing to them. If you're going to flash a new ROM, that should take care of the problem when you wipe things for the new flash.
On the XDA forums, it's generally frowned upon to ask for ROM recommendations. But for me personally, I have decided to settle (for now) on Beanstown106's JellyBeans ROM Build 22 which is based off of 4.1.2. I think this was the last 4.1.2 based Rom (for our SCH-I605's) that he did for his JellyBeans ROM before he moved on to developing for 4.3 MJ9, so I think a lot of the bugs were worked out of it.
I love the ROM and I've tried out several others. I always end up coming back to it because it's really stable and (pretty much) everything works. And with Xposed Modules and his built in options, I can tweak everything to how I like it.
You can still grab his older JellyBeans ROM build 22 by going to the current Alliance Rom Thread here: ( http://forum.xda-developers.com/showthread.php?t=2032447 ), and then going to the "Downloads" area right above the thread title. The ROM Filename is: note2_JellyBeans_B22.zip.
There's tons of great ROM's for our phone and there's so many talented developers..... so I truly think you have to read through the threads on each of the ROM's to make a decision for your personal needs... but I know that JellyBeans Build 22 is very stable if that's what your wanting. If you decide to try out JellyBeans Build 22, let me know if you need instructions for flashing it. I saved the install instructions for future reference when I flashed the first time last year, but I don't see those old install instructions any place now that he's moved on to developing for the updated 4.3 build.
Click to expand...
Click to collapse
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
doctor-cool said:
Thanks and right on time, After I did my return to stock I thought I needed to wipe both caches' and the system to be able to do a Titanium backup.
I lost my operating system and Odin didn't recognize my phone, I was looking for a 4.1.2 zip file at the time I found your post. THANKS!
I'm downloading now
Click to expand...
Click to collapse
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
mattnmag said:
When you say you returned to stock, I'm hoping you didn't ODIN flash a full stock version of 4.1.2, because that would have relocked your bootloader and removed the custom recovery and root. If you were able to use Advance wiping features, you must still have some sort of custom recovery on your phone.
Hopefully, you do so you can flash a zipped ROM back onto it. If you've still got an unlocked bootloader and have a custom recovery, you may want to try to flash this root/modified version of "stock" 4.1.2:
( http://forum.xda-developers.com/showthread.php?t=2261478 ). It was also made by Beanstown106 and the thread still has instructions.
Also, you may do some Google searching to find tips on how to get your computer/ODIN to recognize your phone in download mode again... the most common tips I've seen are to try to uninstall and reinstall the Samsung drivers on your computer...and to try different USB cables and different USB ports on the computer.
I'm exhausted and I'm going to bed, but here are the original install instructions posted by Beanstown106 for JellyBeans ROM Build 22 if needed.
------------------------
"(INSTRUCTIONS) YOU MUST BE UNLOCKED
Step 1-
Make sure u are unlocked
Step 2-
Wipe all(factory reset and davlick wipe) if coming from an old build
Step 3-
Install the Rom (flash it in your custom recovery)
Step 4-
Reboot and Enjoy!"
-------------------------------------
Hope that helps. (Also, if Beanstown's stuff helps you... I'd encourage you hitting the thanks button for all his hard work )
Click to expand...
Click to collapse
Thanks I used JellyBeans ROM build 22 just to have a system so that I could get to Odin. Then I did flash the full stock version of 4.1.2 then I used the Casual method to unlocked the boot-loader and reinstall WIN recovery and root. As explained here http://forum.xda-developers.com/note-2-verizon/help/rom-optimizing-t2817294. ( I ran into some driver issues between Casual and Odin but they were resolved)
Actually I have three Samsung i605's.
I have one that has got all the Verizon OTA updates, never tampered with it's on 4,4,2.
I have the one we have been talking about I have restored it to the fully stock version of 4.1.2 with Root.
And the last one I am experimenting with DN3 (Ditto Note 3) for fun and knowledge.
doctor-cool,
That's great. Glad you got it fixed.
And that's pretty cool to have extra devices to work with. Must be nice.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Longtime XDA'er here with a problem.
I was rooted on stock 4.1.2 for over a year but wanted to update to take advantage of newer features such as chromecast mirror on kitkat. I had a perfectly working phone until I tried flashing updates. I followed instructions and only flashed the MJ9 baseband on roms that tell me too, and even flashed ND7 baseband for other ports. I was able to install multiple variants of 4.4.2 with both twrp and philz recoveries with the same result. I can't get sms/mms to come in. What's weird is upon bootup I will get the same test message only once, then nothing. I even tried flashing agni kernel with no luck. The phone works great with the exception of text messaging. Calls work, GPS locks, and no issues with wifi. APN settings look fine (compared to my wife's note 2 which is identical model still on 4.1.2). I popped my sim into an LG lucid I had as a backup and the text's sitting in limbo start streaming in, so I know my sim isn't bad. I even made sure to disable hangouts with no luck. Even tried Go Sms Pro with same result. I have since decided to go to 4.3 and am having the same issue on those roms on the MJ9 baseband and MJ9 stock kernel.
I'm pulling my hair out because I can't figure this out and I'm a pretty smart fella, this just has me stumped.
Ideas anyone? I have been researching like mad and nothing I try seems to resolve.
Thanks in advance!
timber03 said:
Longtime XDA'er here with a problem.
I was rooted on stock 4.1.2 for over a year but wanted to update to take advantage of newer features such as chromecast mirror on kitkat. I had a perfectly working phone until I tried flashing updates. I followed instructions and only flashed the MJ9 baseband on roms that tell me too, and even flashed ND7 baseband for other ports. I was able to install multiple variants of 4.4.2 with both twrp and philz recoveries with the same result. I can't get sms/mms to come in. What's weird is upon bootup I will get the same test message only once, then nothing. I even tried flashing agni kernel with no luck. The phone works great with the exception of text messaging. Calls work, GPS locks, and no issues with wifi. APN settings look fine (compared to my wife's note 2 which is identical model still on 4.1.2). I popped my sim into an LG lucid I had as a backup and the text's sitting in limbo start streaming in, so I know my sim isn't bad. I even made sure to disable hangouts with no luck. Even tried Go Sms Pro with same result. I have since decided to go to 4.3 and am having the same issue on those roms on the MJ9 baseband and MJ9 stock kernel.
I'm pulling my hair out because I can't figure this out and I'm a pretty smart fella, this just has me stumped.
Ideas anyone? I have been researching like mad and nothing I try seems to resolve.
Thanks in advance!
Click to expand...
Click to collapse
Odin back to stock should fix this issue.
DreamFX said:
Odin back to stock should fix this issue.
Click to expand...
Click to collapse
flashing stock 4.1.2 via Odin does fix it, but when I try to upgrade to any rom from there I have same problem. Pretty much all of the roms 4.3+ specify flashing with MJ9 firmware, which I have done. I have tried 4 roms today and same problem every time.
So annoying, it's like I can't get higher than 4.1.2
timber03 said:
flashing stock 4.1.2 via Odin does fix it, but when I try to upgrade to any rom from there I have same problem. Pretty much all of the roms 4.3+ specify flashing with MJ9 firmware, which I have done. I have tried 4 roms today and same problem every time.
So annoying, it's like I can't get higher than 4.1.2
Click to expand...
Click to collapse
I'm really surprised I'm the only one having this issue. After much research and countless attempts, it seems the most I can do is run stock 4.1.2 rooted, and can apply the MJ9 firmware... but if I try to update to any rom 4.3 or above, my text messaging stops working, otherwise the ROM's work great and phone calls, 4G Data, Wifi, GPS, etc all work perfect... only the sms/mms doesn't.
If I run the stock, rooted 4.1.2, with MJ9 radio everything runs great, including sms/mms, so my feeling is that I need a rom that doesn't flash kernel, or baseband, but jsut system, data, etc... then I might have a shot but it's a long shot at this point. I have even tried beans build 26 which is 4.3 and have EXACTLY the same problem.
The only other thing I've noticed is I have hardware version I605.07 whereas most people it seems have I605.06 from what I've noticed while browsing similar threads.
got it working with no help from anyone... a lot of steps but worth it. Definitely not the normal path everyone has been posting.
timber03 said:
got it working with no help from anyone... a lot of steps but worth it. Definitely not the normal path everyone has been posting.
Click to expand...
Click to collapse
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
sugarfunk said:
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
Click to expand...
Click to collapse
Absolutely... I will type up instructions in the morning. As for driving you nuts I know exactly what you mean... I was pulling my hair out and almost gave up hope but I tried something and it worked. It involves using beans 26 rom and a combination of Twrp and Philz recoveries and backup/restores... if you are having this problem, the main problem is the flashing of the MJ9 firmware.
I'll clue you in tomorrow
sugarfunk said:
Timber any chance you would be ale to point me to the fix? This has been driving me nuts
Click to expand...
Click to collapse
as promised, here's the steps it took for me to get working... It may seem a little bit of a long process but almost 4 days now and no more issues, so I trust this process. It must be something different in my hardware versus other, and I'm assuming yours is like mine.
Let me know if you have any questions
Start with 4.1.2 stock rooted
1. Install latest TWRP Recovery v2.7
2. Backup EFS and Modem as separate backups to your external SD card
3. In Recovery, Wipe.. Advanced Wipe and wipe everything (including Internal Storage) except external SD and USB-TG partitions
The next set of steps is to ensure you have a clean base to work with...
4. Reboot to download mode and using Odin 3.07 flash stock 4.1.2 firmware
in Pit select Sch-i605-16gb.pit
in PDA, select the stock 4.1.2 MC3 firmware
make sure only the following checkboxes are selected: "Auto Reboot", "Re-Partition" and "F. Reset Time"
Hit Start, wait till process completes and boots into o/s. Then skip all wizard options to get to home screen.
5. Root phone using casual
I had no issues using version "NoYouVerizon-GalaxyNote2-CASUAL R515.jar"
6. After root is successful, boot to Recovery and install latest TWRP recovery again since you will have twrp v2.5 due to the root process
7. Repeat step #3 (3 times to make sure everything is wiped clean)
8. IMPORTANT as this is what seemingly fixed the sms issue for me: using twrp recovery, restore the EFS backup you took in step #2 (do not restore the modem)
9. Install Beans 26 rom (Alliance 4.3) which will now give you a proper MJ9 base and kernel to work with. Again, skip all wizard prompts after it loads just so you can get to home screen.
10. Boot into recovery and now backup the new 4.3 EFS and modem partitions to your external SD.
You are not actually going to need the modem backup for the next steps, but if you have a problem installing a rom,
you now have working MJ9 EFS and Modem partitions should you have a problem with any roms from this point forward
11. Repeat step 7 & 8 (restore only the EFS 4.3 partition)
12. Important.. Now install latest Philz recovery
13. Install 4.4.2 rom using Philz recovery
At step 13 is where I installed the Ditto Note 3 rom v5.2, and chose "do not wipe" during the aroma install process.
14. once installed allow it to reboot, if it hangs on samsung boot animation for more than 5 minutes do the following:
a) pull battery and boot into philz recovery, then wipe only the following: Data, Cache, and dalvik cache
b)Install Agni Kernel (PSN_AGNi_pureSTOCK-v4.2.5_I605_4.4.2_AROMA-signed.zip)
c)reboot and you should get the android wizard for the rom in 2 or 3 minutes
If you have a problem like I did with regards to the Camera not working in the new rom, dirty flash the rom again (do not do any wiping)
Then re-install Agni Kernel since the rom installs it's own, otherwise it will break wifi, at least it did on mine.
There are a few more fixes to get tethering, etc working but I can provide those steps if needed. It basically involves installing xposed framework and the moto-x module.
timber03 said:
as promised, here's the steps it took for me to get working... It may seem a little bit of a long process but almost 4 days now and no more issues, so I trust this process. It must be something different in my hardware versus other, and I'm assuming yours is like mine.
Let me know if you have any questions
Start with 4.1.2 stock rooted
1. Install latest TWRP Recovery v2.7
2. Backup EFS and Modem as separate backups to your external SD card
3. In Recovery, Wipe.. Advanced Wipe and wipe everything (including Internal Storage) except external SD and USB-TG partitions
The next set of steps is to ensure you have a clean base to work with...
4. Reboot to download mode and using Odin 3.07 flash stock 4.1.2 firmware
in Pit select Sch-i605-16gb.pit
in PDA, select the stock 4.1.2 MC3 firmware
make sure only the following checkboxes are selected: "Auto Reboot", "Re-Partition" and "F. Reset Time"
Hit Start, wait till process completes and boots into o/s. Then skip all wizard options to get to home screen.
5. Root phone using casual
I had no issues using version "NoYouVerizon-GalaxyNote2-CASUAL R515.jar"
6. After root is successful, boot to Recovery and install latest TWRP recovery again since you will have twrp v2.5 due to the root process
7. Repeat step #3 (3 times to make sure everything is wiped clean)
8. IMPORTANT as this is what seemingly fixed the sms issue for me: using twrp recovery, restore the EFS backup you took in step #2 (do not restore the modem)
9. Install Beans 26 rom (Alliance 4.3) which will now give you a proper MJ9 base and kernel to work with. Again, skip all wizard prompts after it loads just so you can get to home screen.
10. Boot into recovery and now backup the new 4.3 EFS and modem partitions to your external SD.
You are not actually going to need the modem backup for the next steps, but if you have a problem installing a rom,
you now have working MJ9 EFS and Modem partitions should you have a problem with any roms from this point forward
11. Repeat step 7 & 8 (restore only the EFS 4.3 partition)
12. Important.. Now install latest Philz recovery
13. Install 4.4.2 rom using Philz recovery
At step 13 is where I installed the Ditto Note 3 rom v5.2, and chose "do not wipe" during the aroma install process.
14. once installed allow it to reboot, if it hangs on samsung boot animation for more than 5 minutes do the following:
a) pull battery and boot into philz recovery, then wipe only the following: Data, Cache, and dalvik cache
b)Install Agni Kernel (PSN_AGNi_pureSTOCK-v4.2.5_I605_4.4.2_AROMA-signed.zip)
c)reboot and you should get the android wizard for the rom in 2 or 3 minutes
If you have a problem like I did with regards to the Camera not working in the new rom, dirty flash the rom again (do not do any wiping)
Then re-install Agni Kernel since the rom installs it's own, otherwise it will break wifi, at least it did on mine.
There are a few more fixes to get tethering, etc working but I can provide those steps if needed. It basically involves installing xposed framework and the moto-x module.
Click to expand...
Click to collapse
Whatever works for you. Glad your back up and running.
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse
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.