[Q] sch-i605: Not receiving SMS/MMS after any rom upgrade - Verizon Samsung Galaxy Note II

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.

Related

[Q] FIXED! ATT SGH-I717 Sim card error!!

*READ BELOW FOR A GUIDE TO FIX*
I've had my note for over a year now and i have had it rooted pretty much the entire time. Never any problems with it up until recently it started doing this thing where it would keep restarting. It would boot up and less than a minute later just restart. Off and on for a few days it was doing this. I was still running 2.3.6 at that point. So i decided to push 4.0.4 via odin since kies didnt support the firmware. Everything was working fine for a few hours then all of the sudden "the ring of death" showing me no service. Went through the phone and noticed it was saying there is no sim inserted. Tested sim on another phone. Works fine. Since then ive figured out via kies i can recovery and update firmware. Tried that. No Bueno. Now im to the point where im on 4.0.4 with no service. I've scoured through forums trying all kinds of different things, pushing different roms and modems via odin and cwm. Still no bueno.
Baseband version
Unknown
Kernel Version
3.0.8
Build Number
IMM76D.UCLF6
If anyone can give me ideas im willing to try them out.
Thanks.
I got it working so heres a direction for anyone else who has this issue!
Replaced Sim&SD card reader-No fix
After flashing all kinds of roms & modems still same issue saying no sim inserted.
Do a hard reset through your settings.
Flash cwm and put the radio from this link on your sd card. Use cwm to flash the radio.
Flash rom http://forum.xda-developers.com/showthread.php?t=2261598 via odin.
The first try i got an error during flash and got stuck on the software download error screen.
Reflashed the JB rom.
After its flashed flash clockwork recovery.
Enter cwm and do a factory reset. Clear cache. Clear dalvik cache. Reboot system.
If you get service, turn off phone. enter cwm and do a backup.
Reboot system.
It should be working.
If not restart and make sure to do a factory reset through your settings in the phone before reflashing rom.
Got the Phone up and running for about 30 mins.
After battery removed it reverted back to no sim card inserted.
Kept reflashing rom until it worked again.
Flashed cwm.(ClockworK recovery mod)
Deleted cache, dalvik cache
Backed up via cwm
If it reverts back to no sim after that restore using the cwm backup.-it worked for me
Now for the tricky part, my phone was getting crappy service...
So heres what i did to fix it.
Settings-more settings-mobile networks-access point names-click on the apn.
Name-
ATT Phone
APN-
Phone
Proxy-
Not set
Port
Not set
User Name-
Not set
Password-
Not set
Server-
Not set
MMSC-
http://mmsc.mobile.att.net
MMS Proxy-
proxy.mobile.att.net
MMS Port-
80
MCC-
310
MNC-
410
Authentication type-
None
APN type-
default,admin,fota,mms,supl,hipri,internet
APN protocol-
IPv4
Enable/disable APN-
(check mark)
Bearer-
Unspecified
Hope this helps anyone else having this issue.
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
440bro said:
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
Click to expand...
Click to collapse
I Started from scratch via "kies emergency recovery".
No luck.
dweeezy said:
I Started from scratch via "kies emergency recovery".
No luck.
Click to expand...
Click to collapse
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Stuck power button. Your pants are too tight.
Theoriginalgiga said:
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Click to expand...
Click to collapse
i ordered a new sim port to see if that works. what is gb?
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
dweeezy said:
i ordered a new sim port to see if that works. what is gb?
Click to expand...
Click to collapse
GB stands for Gingerbread which was the first version of the OS that came with the phone. I believe the number was 2.3.6 (you can take a look in the about section in the settings and it'll tell you what you're currently running). ICS is Ice Cream Sandwhich which for our phone was 4.0.4 i believe. Jelly bean just came out today which you can use Kies to upgrade to and that I believe is 4.1.2. The numbers don't really mean a think, just the classification of what the OS is so if your phone reads something else (say 2.3.4) assume your phone is right and I'm wrong. I can't remember OS versions to save my life haha.
But you can use Kies to do an emergency recovery and I THINK it'll install Gingerbread. that's where I'd start, then test it, and then move to ICS and test, and then move to JB and test. I know long tedious process, but sometimes it's necessary. Imagine how fun I am to talk to on the phone while troubleshooting a computer :laugh:
redman9 said:
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
Click to expand...
Click to collapse
what I use to migrate, and I between roms at least once a week with a full wipe because I rely on my phone being stable.
SMS and call logs: SMS Backup + (saves your call logs and sms to your gmail account. Makes a label for it and everything, pretty sweet. You can also restore from it. it takes about an hour for me to restore at 7000+ text messages).
pictures/media: stored on SD card
apps: if rooted and rommed I use titanium backup and run 2 sets. those which I want to keep my data like sms backup + to make restore easier and those I don't care about the data like google voice. If you're stock, just remember to check the little box in the beginning saying backup this phone to google (or something like that) and the next time you have to restore tick the box that says restore from google (or something like that) and it'll reinstall your apps. Mind you not the info, but it'll give you a head start.
As with your issue with installing roms. If you're using CWM i highly recommend switching to TWRP, not saying it's better in fact I like CWM better, but TWRP is the best for our roms and phone. If you have no clue what I mean by CWM or TWRP, read the all info sticky about how to rom thy phone.
I hope that helps.
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
redman9 said:
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
Click to expand...
Click to collapse
No problem always happy to help. since you're used to this sorta thing you don't need to use odin again and reroot. What you can do is either install TWRP through CWM using this file here:
http://goo.im/devs/OpenRecovery/sgh-i717/openrecovery-twrp-2.5.0.0-quincyatt.zip
Or you can install Goo manager, click settings and select Install OpenRecoveryScript (though that's only 2.4.4.0 the link above is 2.5.0.0)
That should change you over to TWRP. and like always do a nandroid backup and then flash to your heart's content!
fixed!
dweeezy said:
fixed!
Click to expand...
Click to collapse
How ?
galinha said:
How ?
Click to expand...
Click to collapse
i have the same issue.....i kn0w its n0t an hardware issue....my ph0ne is fairly new never dr0pped and this started happening 3 days after i p0rted black star jb alpha
I have this same issues ive tried flashing everything ive tried a new sim and replaced the card reader.
What works consistently for me if to flash the latest modem everytime i have to reboot or boot the note. Its my daughters phone now and she drains the battery regularly if it boots after charging or it needs to be rebooted for whatever reason it will come up with the no sim card error. If i flash the modem thru recovery it will work for that boot but only as long as I dont reboot or shut the phone off, then i will have to flash the modem again.
Not fixed
All. This is not fixed. I am having the same issue and if you follow the guide, it works for a day maybe regardless of what rom is loaded or what modems. Has anyone found a real solution to this yet??
i717 running stock GB or ICS or JB roms...
Thanks!
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Kraize said:
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Click to expand...
Click to collapse
I'm having the same problem. There seems to be no set way to get it back to working. Basically any reboot of the phone produces a no sim card error. I have tried flashing the modem through recovery as it was mentioned that will fix the problem. That did not work for me. What does work, sometimes, is one of the following:
1. Full wipe and reinstall
2. Restore backup from Recovery
3. Fix permissions
I just keep doing one of the above listed and eventually it works. However if the phone reboots then it's back to the carousel of trying these options to get it back to working.
I'm running Padawan JB V2
I honestly have no idea what's causing it. I haven't tried to fix permissions before to fix this issue, but if I go into recovery and install the modem again and reboot, it works fine for a while (and by a while, I mean like a few hours at max).
Just started having this issue, myself...after flashing Tmo_SGH-T989_VKL1_radio_ATTNOTE.zip modem on my phone...restoring from a prior backup...
Restoring a backup will not change your modem.

[Q] NOOB here :) Wi-Fi not functioning on custom ROMs

Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Sent from my GT-I9300 using XDA Premium HD app
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
solarisrulez said:
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Click to expand...
Click to collapse
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Guys, Thank you all, trying to reply to everyone:
Enea307 said:
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Click to expand...
Click to collapse
Thanks, maybe I'll give that one a go as first try.
converse5 said:
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
Click to expand...
Click to collapse
No, I'm pretty sure that's not the case. Checked my router admin configuration tried to enter my wi-fi pass about 30 times before giving up.:laugh:
chrismast said:
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
Click to expand...
Click to collapse
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
lefttobleed said:
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Click to expand...
Click to collapse
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
solarisrulez said:
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
Click to expand...
Click to collapse
(1) The best would be to read the mega wipe thread. I use it all the time, it will delete ANYTHING excep the external SD card (also not EFS etc, hence dont worry). Therefore you need a flashable rom on the external sd or via Odin later on. But basically your phone won't start after a mega wipe, just download & recovery will work.
Your wipes are correct I think, whereas /system is missing wich is needed, at least for SlimBean (4.3).
(2) The best would be to read the guides & kernel thread's how-to's first. It is basically the same as flashing a rom, yes.
solarisrulez said:
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
Click to expand...
Click to collapse
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Misleading title .
#There have been a number of identical posts and some have fixed by copying older WiFi files over . But you need to search and read and no i don't know where they are . .
Its not a custom rom problem but a non Samsung custom rom problem on 4.3 .
jje
lefttobleed said:
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Click to expand...
Click to collapse
Yes, reading the guides, so first of all decided to backup my EFS (coz that sounds reassuring before doing more ROM flashes) with EFS Professional from this thread: http://forum.xda-developers.com/showthread.php?t=1308546
Installed BusyBox on my phone, and I'm stuck because of a missing applet: http://cl.ly/image/1a1J1A0I3V0H.
I think I'm going deeper than what I can handle
BTW, Enea307, tried CM 10.2 (4.3) this morming, and same wi-fi problem. So it's most likely not a custom rom issue, as most of you suggested.
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
JJEgan said:
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
Click to expand...
Click to collapse
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
Done everything according to http://forum.xda-developers.com/showthread.php?t=1671969
And the firmware is also the one for my phone, and the *.zip that contained the tar (md5) is not damaged http://cl.ly/image/322h3634211J
Any ideas? thx!
solarisrulez said:
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
JJEgan said:
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
Not installed KIES yet, as I read that that's a big brother or something to Odin, and that his little brother is much better at flashing. Should I give KIES a go? Anyways, trying to redownload the firmware.
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
JJEgan said:
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
Click to expand...
Click to collapse
I had installed Samsung Drivers beforehand, before even rooting / doing anything. Did not had KIES until now.
Still cannot flash to stock firmware with Odin.
BTW in the guide: http://forum.xda-developers.com/showthread.php?t=1671969 i see that it should be blue, but mine is yellow when I connect my phone to Odin: http://img600.imageshack.us/img600/9231/odin4c.jpg and mine: http://cl.ly/image/473N1E0Q3G2X
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
IC3CR34M said:
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
Click to expand...
Click to collapse
Thing is, that I am rooted, done with Odin, by following this guide: http://www.androidrooting.com/how-to-root-samsung-galaxy-s3-gt-i9300-or-gt-i9300t-cwm-recovery/
So I have CWM, and with I tried Android 4.3 via SuperNexus, Android 4.3 via ParanoidAndroid 3.97 ROM, then, lastly CM 10.2 (4.3). With none of them did I managed to get the Wifi going.
Here is my current "About device": https://www.dropbox.com/sc/8hp04dn5o5flytd/LpoJCgZ7sK
Is this stock samsung firmware? Coz I can't tell. It seems stock, but maybe it changed with the rooting procedure.
So I repeat, only with this setup/build does the wifi work. With no other custom rom does...
I did backup and recovery to my current working wifi rom. That's how I recovered after trying these custom roms mentioned before.
Guys, help me pls, with at least flashing to the stock samsung rom with Odin or Kies (Odin failed, scroll up see my recent posts with screenshots)
Note that on my last try, Odin just froze yet again: http://cl.ly/image/0o0o0k2L3J3m
If not with Odin, then how do I restore it to stock samsung rom with KIES?
thx!
You dont do it with kies. Kies is such bull**** software. Dont use it at all. You wanna backup, use TI(titanium backup) or nandroid backup. Take a system backup from CWM. As you said in your post, u want to go back to stock, dl the stock rom, do the same procedure u did to root your phone via odin (pda, etc etc), just this time instead of the root zip file, just put the stock rom zip file.
It should take some time, and aftet its done, your phone will be as good as new. To restore the backup via TI, dont select system apps. Only the apps which are in green font or downloaded apps. Other wise u will have force closes.
Also, when u flash the stock rom via odin from your pc, you will not have root. Just a note.
You can simply remove bloatware like live wallpapers, samsung "never gonna use" features like Svoice via TI by just uninstalling them, but note, if fiddling with system apps, them make sure u take a backup.
I have written it all in simple language so that you understand every essential part and have fun with your rooted phone.
Happy to help
As always last resort restore original firmware with Kies and probably a better method than some others posted.
SEE The how to restore your original firmware using Kies post .
Sent from my GT-N8010 using XDA Premium 4 mobile app

[Q] No mobile network after flashing roms

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

4.4.4 tried to flash all of them no go

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 3​NAB - This is the first KitKat TW version for the Sprint Note 3​NC5 - This is the second KitKat TW version for the Sprint Note 3​NH7 - 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 N900PSPTDNH7​Follow 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.zip​Copy the zip to your phone's sd card​Use 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 reboot​Once 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 start​now select install zip -> choose zip from /sdcard -> scroll all the way to the bottom and select the SuperSU-v2.37.zip file -> select Yes​once 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 NH7​You 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:

[ROM|ROOT|Stockish|NO KNOX|No ItsOn] 9/5/15 TouchWiz Lollipop 5.1.1 (N915PVPU4COG1)

Here's a Stockish ROM for your N915P. This ROM has Knox, Sprint ItsOn, and secure storage removed. Nothing else was done to this ROM. I'm new to the Note Edge so I may upload patches to remove any other traces of Knox or ItsOn or optimizations I happen to find while making my own ROM.
Prereq: OG1 Baseband. Download it below.
Modified stock kernel (BeastMode Stock): Kernel modified to allow root by disabling "Root Restriction in defconfig"
Download
MD5: 75bd507e3b4296a128f1c0c48fd2359c
Version 1.1: Enabled many TCP Congestion options via defconfig. Added init.d ability via ramdisk.
Odex:
Download
MD5: 59d544ef6a4bc12d969f4efd9577d36d
DeOdex DEBLOATED:
Download
MD5: 00b5246b9c2074e7ff04f6af2bad1ec2
OG1 Baseband:
Download
MD5: 3bc88209d60117fb573e0f5a2e50f4e9
Patches and fixes:
None yet.
[size=+3]DeOdex note:[/size]
The first boot time for this DeOdex ROM is very long. Approximately 5-8 minutes. Your phone will get hot as the splash screen remains on the yellow Sprint boot animation. I recommend keeping your phone in a cool environment while this is happening. The heat, if not properly checked, can make boot times even longer as the system throttles speed in order to deal with the heat. This doesn't happen on the Odex version.
[size=+3]Install instructions:[/size]
-Are you currently on the OC8 bootloader and would like to stay on it?
--Simply flash the baseband with Odin, and the ROM.
-Are you on the update from OTA or flashed the OG1 TAR?
--Flash kernel only.
-Are you one of the unlucky ones to take the OTA and hose your system trying to root and are now on another ROM?
--Flash ROM only.
-Are you on any build after OC8 but not the current OG1?
--Flash the baseband and ROM. Bootloader is optional and not available in this thread as of yet.
Wiping is only necessary if you are coming from a different base, such as AOSP/CM. If you are coming from a touchwiz ROM, wiping isn't needed, but won't hurt.
Changelog:
9/5/15: Initial Release.
Kernel source code: Download
Thanks, will flash tomorrow.
Thank you so much freeza!! Patiently waiting for the deodexed version and for the baseband.
Added modified stock kernel v1.1 and baseband.
Freeza if I'm on 5.0.1 still just flashing the baseband may give me better service ? Technically...
Downloading now still waiting on the deodex will play with the stock to see how it is thanks
Ok, flashed rom, kernel, and modem. Took a while to boot but all is running well at the moment. Thanks for supporting our device!!
DeOdex uploading....
What What!!! By far the best developer on a Samsung!! Thank you so much for your hard work brother!! Real Talk, i still have your rom on my Note 3! It runs flawlessly!! XD
Get your DeOdex on, guys! ;D
Thanks so much for this!!! I love the separate edge screen and have no reason to "upgrade" to the Note 5
Thank you freeza NICE WORK WITH THE KERNEL
When I saw you had been requested to come help this phone achieve root I knew great things were going to come to those who waited. I've had other devices where you were there to help gain root and again you came through. I purposely didn't take the OG1 update because I knew in time this device wasn't going to be ignored. IMO it is the best NOTE device out there and it will be mine until they make a NOTE EDGE 2 (With SD card and removable battery). Thank you for the quick response and the hard work you do to make this happen.
Cant get either one of them to boot. Both the odex and the deodex wont boot, they both flash fine and then after the phone reboots it stays on the yellow sprint screen Maybe for up to a minute then reboots and it cycles that way. Never boots. I've tried not wiping/Factory restarting as well as wiping/Factory resetting. Have also tried formatting through TWRP to no avail. Have also tried flashing the kernel and wiping caches after flashing but Nothing is working. Have also flashed the baseband.
Im currently on OF6 if that should matter.
Edit: md5 Sums have also match up. Have downloaded both from my phone and a pc to no avail.
Edit 2: tried both TWRP 2.8.6.0 and 2.8.7.0. Also tried clockworkmod recovery and that didn't work either.
I had success but it took some time. I downloaded the deodexed debloated rom, the kernel, and the baseband. I had a method to how I wanted to do this and here is how i got there.
I was running OC8 rom rooted.
1. I odened the baseband tar file and rebooted. But unfortunately it bootlooped on the initial splash screen (note edge) so
2. I ran TWRP recovery and installed the kernel file. Rebooted phone and it ran fine. I looked at the settings about phone and saw that the baseband and the rom all said OG1 but i had not installed the rom yet. So i figure it was a trick to get the baseband to install. So
3. I went back into recovery. Wiped dalvik cache and regular cache and installed the new rom. It installed fine and i waited the length of time for the initial boot up. But this time as it was "Android is starting" it rebooted and got stuck on the sprint splash screen and kept randomally vibrating. Having the ability to remove the battery
4. Rebooted back into recovery, wiped everything including internal storage, and reinstalled the deodexed rom. It installed fine and went to the initial startup screen where it tries to initialize and it rebooted one time, back to the initialize screen but continued without a hitch.
I currently am running OG1 5.1.1. With root.
At times during setting up the phone it would randomally vibrate for no reason...short bursts...but it hasn't yet again rebooted, restarted, or crashed. It is faster from what i see. Probably because there are almost no google apps installed. I've had to install chrome, youtube, and maps. But all seems fine. My signal and speeds are the same so the baseband didn't do much to change that. But so far so good.
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
I did try to install over my odexed OC8 with this new rom but because there is so much different about the files that are installed IMO formatting the phone was the only way to get this to work.
---------- Post added at 12:16 PM ---------- Previous post was at 11:30 AM ----------
One final thing just in case it isn't known: when you wipe everything in TWRP, excluding external storage, you have to restart the recovery before trying to install a rom. It will say you have no OS installed, but you are restarting the recovery not booting a rom, so that's fine, but you do lose root status when wiping. So the next screen gives you the ability to gain root again, but you have to restart TWRP to do that. In the past i tried to figure out why installing after wiping didn't work, and 99% of the time it was because of that. I also don't like installing new roms over older roms (even if they are the same base (touchwiz to touchwiz)) because i feel I would spend more time troubleshooting why something isn't working instead of just starting over. I find less hassle doing it this way.
I odin baseband .tar file, than reboot it to recovery, and flash kernal and odex room at the same time, saw some red messages when kernel was flashing, than odex rom was next but it was successful when it was done. (I did not know if kernel falsh ok so i reflash kernel again) reboot to system and after the android system updated all its ok. No problems so far.
Oh and i inclided the supersu at the same time i flash kernel, odex rom and supersu.
1. Odin baseband tar file.
2. Flash kernel, odex rom and supersu.
3. Re-flash kernel.
4. Reboot to system and profit.
(Maybe i did un necessary steps, but its working. )
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Johnny Halo III said:
Was running great but have been experiencing Google account and store issues. Tried odex and deodex versions with similar results. Anyone else having issues?
Click to expand...
Click to collapse
Just starting to have random freezing. And not able to select my apps froms the edge screen, i can only scroll through it. Will remove all the app shorcuts and re-add tham again.
**update 1.
I removed all shorcuts from the edge screen and added them back, all work but some i have to select them a few times before they open.
Maybe i have to reflash, reset, clean and wipe.
**update 2.
Clean install of odex rom, and kernal 1.1.
No more lagg but the edge screen does not work properly. Not able to select and open some of the favorite app shorcuts.
**update 3.
Factory reset, cleaned and wype, odin sprint lollipop update (uf something), downloaded OG1 update. Installed all apps from scratch. And the edge screen does not work. I can scroll, side to side, up and down, but when i select an app it does not open it.
** update (last one)
Foud the code to test the phone hardware.
*#0*# on dial screen. Tested all and it came out good. But i notice that some how the edge screen its not as whide as it used to be ( like its more to the right of the phone) so where i use to touch to select an app its now more to the right emd of the edge, thats why i was able to scroll but not select the app.
Its all good now. Now second round of flashing.
Will give it another try at the room.
Thanks Freeza and sorry about the problems i had and hopefully did not cause anyone from not trying this great work pr yours.
I left all the problems i had so tje next person trying this room does not get discureged from trying. But allways fallow direction.
:thumbup:
** last update
After setting and resetting, flashing and un-flashing, rooting and un-rooting. I can finally wrote that all is good. Running latest lollipop 5.1.1 and freeza's new 1.1 kernel, I can reprt that all is smooth as butter.
Thanks for the hard work.
Thank you so much for your hard work Freeza! So glad I'm finally running 5.1.1 on this beast :]
The ROM is working pretty well, but I have noticed that every now and then, the phone will be rather laggy. Turning the screen off and on again seems to fix the issue, making me think that the processor is being throttled while the screen is off (good) but isn't being sped back up when the screen is turned on..sometimes.
It's not a huge deal, but I was wondering if anyone was experiencing the same thing.
No issues here.
Starting on OG1 had to flash bootloader, kernel, deodex rom and supersu to make it stick. Two days now and battery, signal and speed seem improved.
Thanks freeza!

Categories

Resources