Related
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.
Galaxy Note 3 Can't send SMS or phone calls, but was receive SMS and calls at first
Hangouts was combined with SMS originally
Device was saying “No APN specified for the device”. When trying to go to Settings>Mobile network settings>Access Point Names, I get error message “Unfortunately, the process com.android.phone has stopped”
Was running cm-11-20140905-NIGHTLY-hltespr.zip at time of problem
Tried wipe/factory reset to 'clean' install of CM11, did not resolve issue
Tried updating to the most recent CM11 nightly: cm-11-20140908-NIGHTLY-hltespr.zip
This did not resolve the issue
Tried going back to an older nightly: cm-11-20140904-NIGHTLY-hltespr.zip
Did not resolve issue
Tried flashing a rooted stock ROM: http://stockroms.net/file/GalaxyNote3/SM-N900P/rooted/SM-N900P-HLTESPR-MJ4-Odex-v2.zip[1]
Did not resolve issue, this put the device into a boot loop, would not get past the Galaxy Note 3 splash screen
Flashed back to the cm-11-20140905-Nightly-hltespr.zip, this fixed the boot loop, but now I'm getting a different message
Wiped data and cache in between each flashing of a new ROM
When trying to call from the phone, it says “Mobile network not available”, and still can't get SMS to send. It no longer gives me any message about “No APN specified”, but the same error happens if I go to Settings>Mobile network settings>Access Point Names
I've found this thread but it only seems to be related to the S3/S4 http://forum.xda-developers.com/showthread.php?t=2657822[2]
Also found this: http://www.reddit.com/r/cyanogenmod/comments/1zlsrk/cant_send_sms_after_fresh_cm11_install/[3]
Google Voice is not installed, and I can't find anything in the settings about Voice+
I can't go back to CM10 because there doesn't appear to be a CM ROM for the Note 3 earlier than CM11
I've found threads with similar issues, but they are all for either Galaxy S phones, or for the Note 2. There seems to be little to no information about the Note 3 regarding this issue
At this point, the Note 3 can't send or receive any mobile data, can't make calls, and can't send messages. It's basically a WiFi only device at this point
Perhaps I need to try updating the radio? I'm honestly not sure. But there again, I can't seem to find much on the Note 3
If someone could help me out with this it would be much appreciated, as its my sister's phone and she's going to go crazy without it
EDIT:
One thing I forgot about, somewhere in there I also tried flashing a ROM for hlte, as opposed to hltespr. I think that at point is when all data stopped working
Some have suggested flashing a stable version of CyanogenMod, but there doesn't appear to be one for the Note 3, unless I'm missing something
Warlock0187 said:
Galaxy Note 3 Can't send SMS or phone calls, but was receive SMS and calls at first
Hangouts was combined with SMS originally
Device was saying “No APN specified for the device”. When trying to go to Settings>Mobile network settings>Access Point Names, I get error message “Unfortunately, the process com.android.phone has stopped”
Was running cm-11-20140905-NIGHTLY-hltespr.zip at time of problem
Tried wipe/factory reset to 'clean' install of CM11, did not resolve issue
Tried updating to the most recent CM11 nightly: cm-11-20140908-NIGHTLY-hltespr.zip
This did not resolve the issue
Tried going back to an older nightly: cm-11-20140904-NIGHTLY-hltespr.zip
Did not resolve issue
Tried flashing a rooted stock ROM: http://stockroms.net/file/GalaxyNote3/SM-N900P/rooted/SM-N900P-HLTESPR-MJ4-Odex-v2.zip[1]
Did not resolve issue, this put the device into a boot loop, would not get past the Galaxy Note 3 splash screen
Flashed back to the cm-11-20140905-Nightly-hltespr.zip, this fixed the boot loop, but now I'm getting a different message
Wiped data and cache in between each flashing of a new ROM
When trying to call from the phone, it says “Mobile network not available”, and still can't get SMS to send. It no longer gives me any message about “No APN specified”, but the same error happens if I go to Settings>Mobile network settings>Access Point Names
I've found this thread but it only seems to be related to the S3/S4 http://forum.xda-developers.com/showthread.php?t=2657822[2]
Also found this: http://www.reddit.com/r/cyanogenmod/comments/1zlsrk/cant_send_sms_after_fresh_cm11_install/[3]
Google Voice is not installed, and I can't find anything in the settings about Voice+
I can't go back to CM10 because there doesn't appear to be a CM ROM for the Note 3 earlier than CM11
I've found threads with similar issues, but they are all for either Galaxy S phones, or for the Note 2. There seems to be little to no information about the Note 3 regarding this issue
At this point, the Note 3 can't send or receive any mobile data, can't make calls, and can't send messages. It's basically a WiFi only device at this point
Perhaps I need to try updating the radio? I'm honestly not sure. But there again, I can't seem to find much on the Note 3
If someone could help me out with this it would be much appreciated, as its my sister's phone and she's going to go crazy without it
EDIT:
One thing I forgot about, somewhere in there I also tried flashing a ROM for hlte, as opposed to hltespr. I think that at point is when all data stopped working
Some have suggested flashing a stable version of CyanogenMod, but there doesn't appear to be one for the Note 3, unless I'm missing something
Click to expand...
Click to collapse
If all else fails try flasing back to stock, update profile, update prl then reroot and flash the ROM. Please follow the OP to the "T" and you should be good!
flynhawn2002 said:
If all else fails try flasing back to stock, update profile, update prl then reroot and flash the ROM. Please follow the OP to the "T" and you should be good!
Click to expand...
Click to collapse
Do you know where I can find a stock ROM? The one I have been able to find has not worked. Also, does reinstalling a stock room cause the phone to be unrooted? I thought I read somewhere that there has not been an unroot for the Note 3 released yet
I will attempt to locate a stock ROM on my own and attempt to update Profile and PRL and go from there. Thanks for the assistance!
Warlock0187 said:
Do you know where I can find a stock ROM? The one I have been able to find has not worked. Also, does reinstalling a stock room cause the phone to be unrooted? I thought I read somewhere that there has not been an unroot for the Note 3 released yet
I will attempt to locate a stock ROM on my own and attempt to update Profile and PRL and go from there. Thanks for the assistance!
Click to expand...
Click to collapse
In the development section you should be able to find a stock rom. Yes, by installing a stock rom you will loose root its as if you just got it from the store, lol.
flynhawn2002 said:
In the development section you should be able to find a stock rom. Yes, by installing a stock rom you will loose root its as if you just got it from the store, lol.
Click to expand...
Click to collapse
I was under the impression that you could be running the stock ROM and still have root access, I guess this is incorrect?
Warlock0187 said:
I was under the impression that you could be running the stock ROM and still have root access, I guess this is incorrect?
Click to expand...
Click to collapse
No, when I say stock its fresh, no root. It will be the same stockness as when you first purchase your phone!
flynhawn2002 said:
No, when I say stock its fresh, no root. It will be the same stockness as when you first purchase your phone!
Click to expand...
Click to collapse
Hmm interesting. I always thought that what software you're running and whether or not you have root access are two separate things. Don't they have rooted Stock ROMs?
Anyway, its irrelevant at this point. I've found a stock ROM I'm hoping will work, will update either way
Warlock0187 said:
Hmm interesting. I always thought that what software you're running and whether or not you have root access are two separate things. Don't they have rooted Stock ROMs?
Anyway, its irrelevant at this point. I've found a stock ROM I'm hoping will work, will update either way
Click to expand...
Click to collapse
Did you ever find a solution to this problem? I am having the same issue. I flashed a hlte rom rather than a hltespr and lost SMS and voice, but my data is still working. I tried to restore my backup and it still isn't working. Any help is appreciated.
would flashing a correct modem solve their problem?
kakiesz said:
Did you ever find a solution to this problem? I am having the same issue. I flashed a hlte rom rather than a hltespr and lost SMS and voice, but my data is still working. I tried to restore my backup and it still isn't working. Any help is appreciated.
Click to expand...
Click to collapse
Just flash an htlespr ROM and you'll be fine.
Flashed back to a Stock ROM, and everything works fine again.
Waiting until a milestone is released to try re-rooting and flashing CM again
So heres my problem...a couple days ago I was deleting some system apps from my S4 to make the phone faster and I was running Eclipse 4.02 at the time...Okay well after I got done deleting the apps I rebooted my phone, everything worked fine for a couple of minutes but then I got a pop up that said "The Process com.android.phone has stopped" and I would hit okay but this diables the data and I have to restart my phone to get data working again...I've tried deleting the Rom from my SD card and redownloading it, I've tried factory reset, and I've also tried flashing a stock md5.tar file in ODIN but it fails at the very end...It will boot but the Wi-Fi doesn't work due to me having to flash gogolies Wi-Fi fix in order to have working Wi-Fi on Eclpise and I still get the "com.android.phone has stopped" issue...the only work around I've found so far is flashing the Google Play Edition Rom this fixes the "com.android.phone" issue but sometimes I won't receive SMS or I will gert them in halves and won't get the others until hours later. I made sure to read the instructions carefully and I am aware of the GPE Rom having issues anyway like MPT connection and Tethering not working but is it possible that somehow I corrupted /system or /system/priv-app or even /system/app? If so is it possible to fix this problem I called Samsung and they said they couldn't do anything about it...but still I would love to use Eclipse again but I can't due to the annoying com.android.phone has stopped issue...If anyone can help or upload the original /system, /system/priv-app, and /system/app that would be great I would just need to know how to install them back because I have no idea...Eclipse is a 4.4.2 Rom and GPE is a 4.4.4 Rom and I'm running baseband NC5 and using stock kernel and I am currently runnin g the GPE Rom to avoid the com.android.phone problem but I don't always receive SMS...any help would be greatly wonderful! Thannks!
Killoma572 said:
So heres my problem...a couple days ago I was deleting some system apps from my S4 to make the phone faster and I was running Eclipse 4.02 at the time...Okay well after I got done deleting the apps I rebooted my phone, everything worked fine for a couple of minutes but then I got a pop up that said "The Process com.android.phone has stopped" and I would hit okay but this diables the data and I have to restart my phone to get data working again...I've tried deleting the Rom from my SD card and redownloading it, I've tried factory reset, and I've also tried flashing a stock md5.tar file in ODIN but it fails at the very end...It will boot but the Wi-Fi doesn't work due to me having to flash gogolies Wi-Fi fix in order to have working Wi-Fi on Eclpise and I still get the "com.android.phone has stopped" issue...the only work around I've found so far is flashing the Google Play Edition Rom this fixes the "com.android.phone" issue but sometimes I won't receive SMS or I will gert them in halves and won't get the others until hours later. I made sure to read the instructions carefully and I am aware of the GPE Rom having issues anyway like MPT connection and Tethering not working but is it possible that somehow I corrupted /system or /system/priv-app or even /system/app? If so is it possible to fix this problem I called Samsung and they said they couldn't do anything about it...but still I would love to use Eclipse again but I can't due to the annoying com.android.phone has stopped issue...If anyone can help or upload the original /system, /system/priv-app, and /system/app that would be great I would just need to know how to install them back because I have no idea...Eclipse is a 4.4.2 Rom and GPE is a 4.4.4 Rom and I'm running baseband NC5 and using stock kernel and I am currently runnin g the GPE Rom to avoid the com.android.phone problem but I don't always receive SMS...any help would be greatly wonderful! Thannks!
Click to expand...
Click to collapse
Sent from my SM-N910V using XDA Free mobile app
I'm really new to XDA but just an update...I fixed it by flashing the NC5.tar again and it actually passed finally I then updated to NK1 so if anyone actually has this problem just repeatedly flash the NC5.tar until it passes I also had to flash the .pit file to return it to factory stock and before I did all this I went into stock recovery (Not Safestrap) and cleared data and cache and then flashed everything through ODIN and it passed and haven't had the problem since
Sent from my SCH-I545 using XDA Free mobile app
Q&A for (ROM)(ODIN)OC5 stcock firmware tar
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for (ROM)(ODIN)OC5 stcock firmware tar. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
J_apa_n said:
Hey does anyone wanna share their buildprop, my network is coming up chameleon.
I'd prefer one for Boost Mobile, but that's probably asking for too much, so sprint will do.
Click to expand...
Click to collapse
I am running the NORMA s6 port ROM on my Sprint note 3, it took a lot of searching and edits but I finally got my network to show up as Boost Mobile AND I have working 4g (working 3g and 1x too).
MMS, GPS, NFC all work as well.
I don’t have 10 posts yet so I can’t contribute on main thread, but when I get home later today I will post my build.prop for you if you’d like. It contains some edits at the bottom of it which were placed there from a “universal boost apn fix” I flashed from the “LG all things root” guide I frequented when I had the LG Volt.
After flashing this, and editing my apns.conf file to have the appropriate info for Boost apn, my lte started working and I haven’t had to mess with my phone ever since.
Jfuginay said:
I am running the NORMA s6 port ROM on my Sprint note 3, it took a lot of searching and edits but I finally got my network to show up as Boost Mobile AND I have working 4g (working 3g and 1x too).
MMS, GPS, NFC all work as well.
I don’t have 10 posts yet so I can’t contribute on main thread, but when I get home later today I will post my build.prop for you if you’d like. It contains some edits at the bottom of it which were placed there from a “universal boost apn fix” I flashed from the “LG all things root” guide I frequented when I had the LG Volt.
After flashing this, and editing my apns.conf file to have the appropriate info for Boost apn, my lte started working and I haven’t had to mess with my phone ever since.
Click to expand...
Click to collapse
There are some more things that you will need to edit to enable all of the Boost mobile features for the rom. Specifically in CSC. If you need more info send me a PM and I can help you get your rom even sweeter!
I don't know if this is the right place to be posting this. So forgive me if this question is in the wrong place. I upgraded (with Odin v3.07) from 4.4.4 to NH7 (I believe) and then to OC5. Everything worked fine until I tried to install TWRP. It wouldn't work. It just refused to replace the stock recovery with TWRP. So I finally got Odin to reinstall the software (OC5) again after doing a factory reset and cache reset. After getting OC5 to work I booted to stock recovery. When I rebooted into the OS, I started getting before booting was complete, a message saying, "Unfortunately<An App> has stopped". Pulled the battery, replaced it and same thing. Has anyone seen this before, and if so what did you do to fix this?
Thank you,
Owen M, Jones
I don't know if there is any missing info on your explanation. I did notice problems on the ota. I also noticed differences between ota and full odin tar. The first difference i noticed with the full odin tar is the android wiggled its antennas. The second thing I noticed was the initial setup looked different vs ota.
I was also getting system app stopped responding message. I was also too aggressive with titanium backup freezes. Things I used to get away with, were mucking up operation. Out of final despair, I decided to only freeze apps that showed up in the regular app menu, that I didn't use. So far, no force closes. A week or so has past and no issues so far. There area few apps that are showing up in play updates, that aren't in the normal app menu list, and I'm not updating them. The app isn't responding got so bad for me that i couldn't get fully booted to back up anything, and lost data that I wish I could have backed up. Oc5 is tempermental.
My latest snafu was freezing apps so much that settings didn't work. I unfroze everything and only froze apps that were in the app menu. Before I did that, wifi and wifi calling were forced on and a reboot wouldn't turn things off causing that state. That's why I said oc5 is very touchy when digging under the hood and stopping apps and services that you might think are bloat. I might disable ant, which is an app for monitoring fitness hardware, but I just leave it alone and don't update it.
tx_dbs_tx said:
There are some more things that you will need to edit to enable all of the Boost mobile features for the rom. Specifically in CSC. If you need more info send me a PM and I can help you get your rom even sweeter!
Click to expand...
Click to collapse
I'd love to get wifi calling & hotspot running, were you able to get them running?
ojones838 said:
I don't know if this is the right place to be posting this. So forgive me if this question is in the wrong place. I upgraded (with Odin v3.07) from 4.4.4 to NH7 (I believe) and then to OC5. Everything worked fine until I tried to install TWRP. It wouldn't work. It just refused to replace the stock recovery with TWRP. So I finally got Odin to reinstall the software (OC5) again after doing a factory reset and cache reset. After getting OC5 to work I booted to stock recovery. When I rebooted into the OS, I started getting before booting was complete, a message saying, "Unfortunately<An App> has stopped". Pulled the battery, replaced it and same thing. Has anyone seen this before, and if so what did you do to fix this?
Thank you,
Owen M, Jones
Click to expand...
Click to collapse
FIRST odin CF auto-root. THEN odin the latest TWRP that supports your specific device model. SM-N900P. If Odin fails to flash TWRP by doing it in this order then contact the TWRP team and see if they can look into it.
oscarthegrouch said:
I don't know if there is any missing info on your explanation. I did notice problems on the ota. I also noticed differences between ota and full odin tar. The first difference i noticed with the full odin tar is the android wiggled its antennas. The second thing I noticed was the initial setup looked different vs ota.
I was also getting system app stopped responding message. I was also too aggressive with titanium backup freezes. Things I used to get away with, were mucking up operation. Out of final despair, I decided to only freeze apps that showed up in the regular app menu, that I didn't use. So far, no force closes. A week or so has past and no issues so far. There area few apps that are showing up in play updates, that aren't in the normal app menu list, and I'm not updating them. The app isn't responding got so bad for me that i couldn't get fully booted to back up anything, and lost data that I wish I could have backed up. Oc5 is tempermental.
My latest snafu was freezing apps so much that settings didn't work. I unfroze everything and only froze apps that were in the app menu. Before I did that, wifi and wifi calling were forced on and a reboot wouldn't turn things off causing that state. That's why I said oc5 is very touchy when digging under the hood and stopping apps and services that you might think are bloat. I might disable ant, which is an app for monitoring fitness hardware, but I just leave it alone and don't update it.
Click to expand...
Click to collapse
Don't go freezing stuff willy nilly. There's no need for that and it will cause problems. There's too many dependecies and freezing the wrong app will effect other system apps/services. Battery life is great if you turn of services that you don't use.
J_apa_n said:
I'd love to get wifi calling & hotspot running, were you able to get them running?
Click to expand...
Click to collapse
Ofcourse. Give me a couple of days. Current deodexed Lollipop rom is being tested. Once that is done I can help you with these things.
Guys what's up with all the links lately all down or dead or corrupt
R1000 said:
Guys what's up with all the links lately all down or dead or corrupt
Click to expand...
Click to collapse
If you are looking for OC5 tar download the links are fine I can assure you that.
Thanks
could someone get me the verizon baseband and modem file? I have a sprint model, but there is no sprint service here.
jlucero said:
could someone get me the verizon baseband and modem file? I have a sprint model, but there is no sprint service here.
Click to expand...
Click to collapse
Would it be better to ask for this in the Verizon section?
Galaxy Note 3 on 5.0 lollipop
Can anyone tell me how to root the Note 3 on Lollipop? I used Odin to flash oc5, but I lost root. I flashed cf autoroot 4.4.4, but that didn't work. Then someone said load twrp.img in Odin but pda slot didn't give that option. I am new to Samsung so bear with my inexperiance. I usually add on my Nexus devices. Thanks in advance Guys
djprince2001 said:
Can anyone tell me how to root the Note 3 on Lollipop? I used Odin to flash oc5, but I lost root. I flashed cf autoroot 4.4.4, but that didn't work. Then someone said load twrp.img in Odin but pda slot didn't give that option. I am new to Samsung so bear with my inexperiance. I usually add on my Nexus devices. Thanks in advance Guys
Click to expand...
Click to collapse
Both methods should have worked for you, but just have in mind that you can't use the same odin from cfauto root to flash other tar files than the cfautoroot one, and also you won't be able to flash an img file using odin it has to be a .tar or .md5.
I finally decided to take the jump and root today, tired of not being able to use the secure settings in Tasker/Airdroids Airmirror, and I've ran into a little problem. I successfully flashed the twrp recovery, got the Trapkernel installed, flashed SuperSU, and after booting back up everything works fine except for the WiFi. It's enabled, it sees my router and such, but it refuses to connect. Telling to do so does nothing. It just won't. Disabling/re-enabling doesn't work, nuffin. If I restore my backup before the kernel/supersu however everything works just fine. Am I doing something wrong? Is this some silly user error I'm too stupid to see?
Apologies if this is a frequently asked question or similar that I missed, I did some searches and couldn't find anything and decided to make a post.
It might be ur rom. Try flashing a different one and see.
Sent from my SM-G900T using XDA Free mobile app