Hey guys, I'm not new to rooting or flashing ROM's but I've encountered some issues. Basically, I was on an early JB Rom and everything was working fine but it mostly was in roaming and would go from 2-4 signal bars.
I backed up and have attempted to flash:
PACman
MIUI 2.11.23
As well as CM10 by joker and AOKP CM 10.
Every flash I end up with no signal bars and no roaming, also following all install instructions in the threads.
I have tried flashing with and without prop tweak, i have even restored the backup all with the same results:
Empty signal bars, occasional R for roaming, every call says mobile network unavailable.
I have also fixed permissions, and have tried to flash via TH3Bill CWM and TWRP recovery... what am I doing wrong? The backup isin't even working!
I wouldn't know off hand, but here's something you can try while waiting for a more professional member to come to the rescue.
System Settings> More>Mobile Networks>System select>Home only
What's your current PRL, APNs?
if it was me I'd sbf back to stock and see if I had signal then go back and try a custom rom again
foxsdaddy67 said:
if it was me I'd sbf back to stock and see if I had signal then go back and try a custom rom again
Click to expand...
Click to collapse
Before sbf'ing if you have a back up of your stock ROM or any ROM that has the update profile/prl setting in it, restore that back up and try updating your profile/prl then wipe/flash your new ROM.
I usually have this problem when I switch back to my Photon from my ET4G, but updating the profile usually does the trick.
When I restored my old backup, I had the same problem. The only fix I could find was on MIUI and selecting automatic netowrk before flashing options chooser. Any other rom would make no changes on automatic or home only. I am going to try a fresh install and if no luck will sbf today. I'll keep you guys posted.
Thanks!
**EDIT** Does it matter if I use Th3Bill's CWM recovery or TWRP? I have tried both with similar results. I jut noticed CWM is usually posted with the ROM builds... does it makes a difference? If so, what should I use?
Normally both work just fine, as long as you're using one of those two
I spent too much time flashing roms and wondering why they wouldn't work right, when I was using the stock CWM
I think It's just my opinion but I have preference for bill's cwm
Having this exact same problem. Did anyone figure it out?
No Radio/Signal
I recently flashed the latest MIUI.US V5 3.4.5 for the Photon provided by Th3Bill. I am familiar with the process of applying ROMs. I tried to go back to Beanstalk, JB, and ICS and could not recover the radio signal. I even restored a few backups with the same result, no signal. I flashed the MIUI V5 3.4.5 ROM back to the Photon and it worked flawlessly. Can anyone please help? I would really like to get off the MIUI ROM, it does not appeal to me like the standard versions of Jelly Bean that Th3Bill has produced.
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
I have a i605 with Verizon. It's rooted and I've been running Jellybeans 22 (4.1) since August. Saturday I decided to install the new 4.4 with CyanogenMod 11 which just came out. I goofed and installed the 7100 copy (I think it was 7100, started with a 7). I got a no service message which makes sense. Ok Mark, what's next dumbass? lol so I got the right version and installed it, and still didn't get service. So then I rolled it back to the image I made before I started this whole thing and still no service? I read other postings and checked for phone number and IMEI which are populated. ERI version is 5. I also keep getting a message asking me to go to a GLOBAL setting which doesn't help either. I tried pulling the SIMS card and rebooting. The instructions said to put the card back in while rebooted but the power supply blocks that. Soo.... do I try to get my stock installed or is there other things I can try.. There's this cute chick who likes me and if I can't text her I might never get laid!!!! (I wish )
I also had the same problem of baseband and imei showing unknown but I was able to fix it.
thanks,
chat/email : [email protected]
Should I unroot
Should I unroot the phone and go back to stock to see if it corrects the issue? Will I need to accept an OTA?
Use cwm.
Sent from my SCH-I605 using Tapatalk 2
I would do what hopesrequiem suggested. If you are using TWRP to flash CM11 you wont have data. You have to use CWM 6.0.4.3 for some odd reason.
DX.Deception said:
I would do what hopesrequiem suggested. If you are using TWRP to flash CM11 you wont have data. You have to use CWM 6.0.4.3 for some odd reason.
Click to expand...
Click to collapse
what Went South was I couldn't make phone calls or text. Even after restoring 4.1 Rom. I didn't have issue with data. But to answer my own question. . I fixed my issue by restoring my stock Image and then used setup / backup / factory reset. That did it. When I restored 4.1 it was working again. Thanks for the info on cwm version.
Well im glad all is well now!
Help!
Hello! Need help!
The problem is this .. darkforvard 4.1 firmware was decided to try the new Android and flashed jungle extreme 4.3 firmware ..
good but a little bit not mine .. while rolling back its 4.1 flew on imei 00000049 ... and the serial number on 00000 .... EFS apparently not kept ... result
does not work and an Internet connection ..
If anyone actually encountered such a problem please tell me how to get out of this situation?
theory of course is good but need a practical personal experience ! If you can write about the points and what to do
Currently in the phone
Firmware version N7100XXDME4
Build number JZO54K.N7100XXDMG1
Rekaveri philz_touch_5.15.0-n7100
Thank you!
not sure if this is the wrong place to post this.
i was recently messing with roms on my yp-g1 galaxy player 4, installed a custom rom that messed up,
o ,
followed this
http://forum.xda-developers.com/showthread.php?t=1531850
I re installed the stock recovery images but I can no longer get the gps to acquire signal.
after this failed i installed steves kernel , and updated it to use the carbon rom firmware ,
But i still cant get the gps to get a signal
i read that this is a bug after you update firmwares,
but i am not sure where to get a radio firmware , and i already tried to restore to the factory firmwares and that didnt seem to have any effect..
help would be appreciated , i primarily use this device for geocaching , so without a gps signal its a brick for me...
bobisunreal said:
not sure if this is the wrong place to post this.
i was recently messing with roms on my yp-g1 galaxy player 4, installed a custom rom that messed up,
o ,
followed this
http://forum.xda-developers.com/showthread.php?t=1531850
I re installed the stock recovery images but I can no longer get the gps to acquire signal.
after this failed i installed steves kernel , and updated it to use the carbon rom firmware ,
But i still cant get the gps to get a signal
i read that this is a bug after you update firmwares,
but i am not sure where to get a radio firmware , and i already tried to restore to the factory firmwares and that didnt seem to have any effect..
help would be appreciated , i primarily use this device for geocaching , so without a gps signal its a brick for me...
Click to expand...
Click to collapse
you need to go back to absolute zero. follow the instructions in this forum http://forum.xda-developers.com/showthread.php?t=1531850 to the letter, being sure to wipe the cache when it says to. also, make sure you install the proper stock rom (international or usa, which ever one is appropriate for your device, if you dont know, look at the top of the fourm i directed you to)
after that, try reflashing again, following the instructions to the letter. usually when these issues happen, it is because of something stupid like a cache not being wiped when it should.
good luck
last night i broke down and trashed out carbon , Witch I liked very much (after having it on for only 4 hours),
Dispite not being able to install Gapps no matter what version I used.:silly:
Repartioned twice, as well as wrote the usa firmware back 3 times ( after fudging /mount multiple times selecting a incorrect firmware file).
and put it back to pure stock. GPS still didnt work.
left gps status app running for the night on my desk just for kicks , After 5+ hours it managed to get a gps signal
crashed the gps app and then magicly the gps is working again.
i am probably too scared to go back to carbon or another firmware
What are the chances this would happen again if i re flashed back to carbon again ?
Don't know, but if I had to guess, unlikely if you follow the directions.
Sent from my Nexus 7 using XDA Premium HD app
Hey all,
I downloaded and flashed MM this past week. I *did* root my phone using the latest supersu 2.74 from chainfire. Now, I am random reboots. I did use odin for the firmware flash.
I have a G900t1.
Thoughts?
Having exactly the same issue, phone will work fine for a day or two , them I will get as many as 5 reboots in a day....
sameog said:
Hey all,
I downloaded and flashed MM this past week. I *did* root my phone using the latest supersu 2.74 from chainfire. Now, I am random reboots. I did use odin for the firmware flash.
I have a G900t1.
Thoughts?
Click to expand...
Click to collapse
After all the random reboots, I downgraded back to kitkat because it's stable.
im wanting do go back to lolipop because i made a complete nandroid backup not entirely sure how to go about it, since ive switched to marshmallow my call quality and network connections have been crappy. like having make a call several times before it goes through with full LTE signal strength etc.
darthmalus said:
im wanting do go back to lolipop because i made a complete nandroid backup not entirely sure how to go about it, since ive switched to marshmallow my call quality and network connections have been crappy. like having make a call several times before it goes through with full LTE signal strength etc.
Click to expand...
Click to collapse
Just a thought.. double check your modem and boot loader are correct. But if your sure you want to go back, there is a couple threads with the roms, bl and modem for download.
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
I've found this release very stable and solid.