Related
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
*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.
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
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.
Q&A for [ROM] CM12-Light BETA
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] CM12-Light BETA. 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!
GPS Bug
Is the GPS still restarting the phone on this build?
Mustapha21 said:
Is the GPS still restarting the phone on this build?
Click to expand...
Click to collapse
Check the replies in the development build. T399 has to download an app specified in the development but people with the T399N seem to have no problems with v23.
Sent from my SGH-T399 using XDA Premium app
The developer Acreaperjb needed people to test the ROM and kireflow seems to have the SGH-T399N while he is meant to develop it for the SGH-T399. Is he now making a hybrid build for both models?
Sent from my SGH-T399 using XDA Free mobile app
wow
Had the lightwave rom on this before, and it worked well. After a few hrs of running cm i am blown away at the performance. Buttery smooth. Calls crisp, no issues whatsoever aside from the camera. Got xposed on it, gravitybox and greenify working great so far
And just thought I'd try it with the Camera MX from playstore and voila, it works! One picture at least
Bluetooth freezes calling app
Hi everyone, first of all, big thanks to AcreaperJB
I just installed version 0.2.3, overall I really like the ROM, I have two issues with it, really it's just one that I care about, here I go
1 - the big deal) I can't make calls over Bluetooth, after dialing I hear maybe one signal, maybe two if I'm lucky, after that the calling apps freezes, can't finish the call, can't call anybody else, can't hear anything, even turning off Bluetooth won't restore things, I can switch between apps and everything is fine except the calling app it's just stuck until I restart the phone, no more calling basically
2 - the workaround) camera will crash right after taking the photo, won't save the photo, I installed open camera from the play store and it works fine, I know it's a known issue, I just want to confirm it
Things to mention
- I did full install, all the partitions got wiped except the external SD card partition where I kept the ROM
- installation was scary, after installing the ROM it would circle back and forth, it was restarting and it wouldn't let me do anything, as soon as it got to CM wizard it restarted, I had no way to stop it or pause it so after about 10 restarts I gave up and just moved on and left the phone do restarts and I took care of other things around the house, already started thinking on how to go back to the stock rom, after coming back to the phone about two hours later the CM was waiting for me, got so surprised that it got out of the endless loop, i finished the wizard, went into CM and it doesn't restart anymore
thanks again
Uhm
Hey, does anyone know of a fix for the YouTube app? It keeps saying 'an error has occurred touch to retry'
SIM Card not detected?
So I clean installed the dirty v.0.2.3 and when it went to setup it said my sim card wasn't detected. Did I miss something? Does the "dirty" mean I won't get data? I'm new to this and I don't really know what the lingo means. I also can't change the APN's. It says "Access point name not available for this user".
I can't make any phone calls nor send any texts. My cellular data doesn't work either. Wi-fi and everything else works fine. Just the actual service.
Am I missing a step?
I flashed the ROM with twrp 2.8.4.0, I wiped davlick, data, cache, etc. I did the clean install, I don't understand why I am not getting any service or why my sim card isn't detected.
Please help
I need another link to download
Hi everyone
So my problem is for some reason here in Cuba I can enter to www.androidfilehost.com and download (Dirty) V.0.2.3 https://www.androidfilehost.com/?fid=24052804347774276 I dont know why but if anyone can please reupload the file to another server like MEGA or mediafire I have the Galaxy Light and I like to help to test the build and make some comments about.
Regards
michel0303 said:
Hi everyone
So my problem is for some reason here in Cuba I can enter to www.androidfilehost.com and download (Dirty) V.0.2.3 https://www.androidfilehost.com/?fid=24052804347774276 I dont know why but if anyone can please reupload the file to another server like MEGA or mediafire I have the Galaxy Light and I like to help to test the build and make some comments about.
Regards
Click to expand...
Click to collapse
https://mega.co.nz/#!R8RkhRTI!A72ioxNsedZ3uGgY3jE6MMjKkaVYYBwL8z8WBnie8lI
kireflow90 said:
https://mega.co.nz/#!R8RkhRTI!A72ioxNsedZ3uGgY3jE6MMjKkaVYYBwL8z8WBnie8lI
Click to expand...
Click to collapse
Thank you so much Downloading right now.
michel0303 said:
Thank you so much Downloading right now.
Click to expand...
Click to collapse
no problem, glad I could help
Screen going blank upon boot
I tried installing this rom after doing a full backup & then wipe. I made sure to wipe dalvik and cache. I then installed the 0.2.3.zip via TWRP 2.7.1.0 that comes with Light V3 Rom.
Install completed without error but upon boot the setup menu appears and then vanishes. I can get it to display ever-so-briefly by powering the display off/on.
I have a T-Mobile T399 unlocked for use on ATT. Unjustified Devs earlier builds did the same thing but would constantly reboot as well. Your rom doesn't reboot but the screen behaves similarly.
Have you heard of this behavior before, and are there any steps I can take to provide you with diagnostic information?
Update TWRP
Vorell said:
I tried installing this rom after doing a full backup & then wipe. I made sure to wipe dalvik and cache. I then installed the 0.2.3.zip via TWRP 2.7.1.0 that comes with Light V3 Rom.
Install completed without error but upon boot the setup menu appears and then vanishes. I can get it to display ever-so-briefly by powering the display off/on.
I have a T-Mobile T399 unlocked for use on ATT. Unjustified Devs earlier builds did the same thing but would constantly reboot as well. Your rom doesn't reboot but the screen behaves similarly.
Have you heard of this behavior before, and are there any steps I can take to provide you with diagnostic information?
Click to expand...
Click to collapse
Think you need to use the twrp 2.8.4 that is in the forum
http://forum.xda-developers.com/android/development/recovery-twrp-2-8-1-0-touch-recovery-t2924604
Try flashing a T-Mobile radio. Just Google it and it should come up.
Sent from my SGH-T399 using XDA Free mobile app
Answer: CM12-Light BETA for t399n camara workaround.
I have installed cm12 for the Samsung galaxy light t399N.. I am happy to report Everything is working fine! except the stock camera, I tried 7-8 camera apps on the Google play store with no luck, until.... VIOLA, I found one that works. It is called FOTOR. it works now. I have an extra step to deal with but the point is that my phone is now fully functional and running 5.02 lollipop on my METRO PCS t399n. BTW i did not have to edit the apn settings; interestingly, I have an indicator that tells me I have T-Mobil for my carrier.... Thank goodness for the recent merger and switch over to the T-Mobil network, one more problem solved. Hope that helps someone else out there.
thanks
it works
I'm using it a week ago, everythings is ok, only the stock camera not save the photos,
Sorry for my english,
---------- Post added at 01:18 AM ---------- Previous post was at 01:12 AM ----------
md777 said:
I have installed cm12 for the Samsung galaxy light t399N.. I am happy to report Everything is working fine! except the stock camera, I tried 7-8 camera apps on the Google play store with no luck, until.... VIOLA, I found one that works. It is called FOTOR. it works now. I have an extra step to deal with but the point is that my phone is now fully functional and running 5.02 lollipop on my METRO PCS t399n. BTW i did not have to edit the apn settings; interestingly, I have an indicator that tells me I have T-Mobil for my carrier.... Thank goodness for the recent merger and switch over to the T-Mobil network, one more problem solved. Hope that helps someone else out there.
Click to expand...
Click to collapse
I'm using the app A Better Camera, it's woking ok, on my t399n
Reboot cycle
After installing V0.2.3 using TWRP 2.8.4.0 on a T399 on a T-mo network I am stuck in a continuous cycle of rebooting every few seconds. I have tried reinstalling starting from a stock image and wiping the cache, data, and dalvik. Any idea what I could be messing up?
yodal said:
After installing V0.2.3 using TWRP 2.8.4.0 on a T399 on a T-mo network I am stuck in a continuous cycle of rebooting every few seconds. I have tried reinstalling starting from a stock image and wiping the cache, data, and dalvik. Any idea what I could be messing up?
Click to expand...
Click to collapse
Set GPS to device only
Sent from my SGH-T399N using XDA Free mobile app