Related
I have a quick question because I've run into a problem I can't seem to fix.
First, so everyone knows what I'm dealing with:
Phone: i717
Changes: Rooted (Shows super user access), CWM v5.5.0.4, Unlocked (Tested)
Rom: Stock AT&T Rom
Sim Card: Works in a T-mo branded Exhibit II 4G.
I flashed a radio (tried KID, 0331122 from the radio thread in the dev section, and reflashed the original AT&T radio).Even w/ the original radio installed, it cannot seem my T-Mo sim now.
Do I need to flash a new Rom or what? Wipe data to factory reset?
I would rather not change anything w/o asking since flashing radios seems to be a straight forward thing that most ppl have done w/o touching the rom.
Thanks ahead of time.
Mine worked with a rooted stock rom at first it didnt see the sim then i tried searching the network under wireless and networks it took a few minutes but then it came up.
Sent from my SAMSUNG-SGH-I717 using xda premium
don't forget if you are running an ICS based ROM you need an ICS based Radio/modem.
EDIT: i see you're running the original GB rom so you need the GB radio.
give it a few minutes to find a signal or go to settings/mobile networks/network operators. choose manual. then let it search a few minutes. then select t-mobile.
I find the Blaze 4G radio worked best for me, but depending on your area, your results may differ. try em all.
You guys are insanely fast.
I'm currently on the stock radio & I'm still getting the same message after letting the sim sit in the phone for 9 minutes (yes, I watched the clock, lol):
Insert SIM card to access network services
Click to expand...
Click to collapse
Where should I go from here?
Edit: Is the answer flashing another rom? Maybe something has become corrupt? I don't see how as I've read & re-read walk thrus for doing this to make sure.
I've done a little more reading. Flashing the beta ICS rom flashes to the old AT&T modem.
Would this be the best bet?
Edit: After looking through the "about" phone...
I'm on 4.0.3
Baseband: Unknown............. that's really bad.
Edit 2:
After reading, I needed to back up the EFS. No where is this stated anywhere, unfortunately. That contains IMEI and everything else.
Edit:
So, after reading MORE, the IMEI number is on a sticker behind the battery, along w/ the S/N.
Huh? Efs? I dont even know what that is nevermind backing it up. Goto clockworkmod and flash the radio.zip and reboot. Thats all there is to it.
Sent from my SAMSUNG-SGH-I717 using XDA
madman604 said:
Huh? Efs? I dont even know what that is nevermind backing it up. Goto clockworkmod and flash the radio.zip and reboot. Thats all there is to it.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
If you look up EMEI number related to flashing the radio, there's a lot of hits.
XDA has a thread on it here: http://forum.xda-developers.com/showthread.php?t=1352371
I'm quite shocked it's not mentioned everywhere as this happens to people now and again.
I have my IMEI number, i just don't know how to input it into the phone.
As for flashing the radio, I've flashed 2, then back to the original. To no avail.
Sorry never had anything like that. I would almost odin back to stock and start over. You dont need root for the sim to work on calls and edge with tmobile.
Sent from my SAMSUNG-SGH-I717 using xda premium
If you're baseband is unknown don't worry just flash a stock at&t modem and it should go back to normal. Your imei is under a different menu in about phone..the status one.
Also its no ones responsibility to tell you that modifying your phone may break it.
Sent from my SAMSUNG-SGH-I727 using xda premium
jamesd86 said:
If you're baseband is unknown don't worry just flash a stock at&t modem and it should go back to normal. Your imei is under a different menu in about phone..the status one.
Also its no ones responsibility to tell you that modifying your phone may break it.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I did flash back to the stock AT&T baseband as stated in the original post.
If I go to About Phone, the Baseband Version is unknown.
If I go to Status, the following are listed as
Network: Unknown
Mobile Network: Unknown
Service State: Out of service
Mobile Network State: Disconnected
IMEI: Unknown
IMEI SV: Unknown
I've backed up the EFS that I have no just so it doesn't degrade further. I'll try to flash again and see, but I still think the EFS is borked.
I'll see what I can, but I think I'll the EFS is borked beyond flashing it to normal.
My point about the EFS back up is that most ppl here don't seem to know what it is. It shouldn't be that foreign of a topic since flashing a radio is obviously problematic for some. I've seen other posts concerning no IMEI after flashing radios on forums other than XDA. It's odd that it's not mentioned as a sticky everywhere.
Backing up EFS would solve a lot of head aches from unlocking / radio flashing woes. I'm hoping this info will save a few people a lot of time and money.
After more digging, I came across this thread:
http://forum.xda-developers.com/showthread.php?t=1646326
Synopsis: Basically, he followed the same guide I did. The only difference is that I flashed the radio while using a stock AT&T rom. Once he flashed back to GB (saurom), he gained back his baseband / IMEI.
This is what I cannot figure out:
CWM will see and flash any radio file I push to my note. If I push a stock AT&T rom, it won't see it. If I put the rom in it's own folder, it seems the rom, but states there's no files.
Is CWM corrupted? Why would it only read firmware to flash radios, but not android roms? Should I just go back and install CWM?
I've searched all over & used google, but I can't find a thread discussing this.
Fixed.
This problem has nothing to do with any of the radios corrupting the EFS folder. Albeit, it's always a good idea to back it up.
Flashing back to AT&Ts stock rom (2.3.6 or 4.0.3) never fix the issue. You will always be stuck w/o a radio, at least from what I've seen. Even flashing back to the stock radio fails. I don't know if it changes the EFS, but AT&T's rom does not like it and shows no IMEI & a bogus SN .
I had to go back, flash to saurom and a compatible GB (or beta T-mobile) radio to get te work fine. ICS radios work fine on ICS.
Saurom and GB radios dont work in my i 717 trying to connect to wind. I got a CM 9 ICS build and ive tired a bunch of radios. they all failed. i keep getting no sim errors. I can see the operator but when i select it it times out and says it cannot connect to the network at this time. it also says interset sim. Im positive it is unlocked.
Modems(radios) or basebands should have nothing to do with whatever rom you are running. Whether they are GB, ICS, or JB modems, they should all work to a degree, at least for phone call ability. I have flashed many different radios trying to get the best function of my att note on t-mo. The best I got was using the Blaze modem. That got me 3g hspa.
The worst will be just giving you edge speed. My note is unlocked and has been on JB running blaze ICS modem working fine. Maybe you need to start over, evaluate what you have, and go from there. There are great threads on att over t-mobile. Good luck.
I picked my rom, and started flashing 5 or 6 radios, and found what one worked best on t-mo.
Presently, I have switched back to att- sort of- straight talk. I'm not thrilled with the speeds. No higher than 4 mbps DL, and 1-1.5 UL. Thinking about going back to t-mo and dealing with the slow UL speeds. I'm on an ICS rom with the ucle6 modem.
Also, flashing a rom does not change your modem. You have to physically reflash the modem you want. Some modems show up as unknown under the baseband. Blaze is one of them.
Another thought- sometimes a reboot will get your sim recognized by your phone.
sico987 said:
Saurom and GB radios dont work in my i 717 trying to connect to wind. I got a CM 9 ICS build and ive tired a bunch of radios. they all failed. i keep getting no sim errors. I can see the operator but when i select it it times out and says it cannot connect to the network at this time. it also says interset sim. Im positive it is unlocked.
Click to expand...
Click to collapse
This is yet another case of the "no sim" bug ....
Damn I wish we could find the answer to this issue, but none exist .....and for some users the return to complete stock even fails to recover service ..
g
Really what an incredible unlucky glitch.I got my note for only 360CDN good condition but missing the stylus, even still it was a good buy. I'm on Wind mobile, T-mobile here in Canada. I even gave it to somebody who's done a bunch and they ran into the no sim problem. I guess I'll be going back to my HTC HD2 and sell the note .
---------- Post added at 11:48 PM ---------- Previous post was at 11:44 PM ----------
So just to confirm I have followed the process correctly over 20 times and no matter which cm9 cm10 based rom and any ics or gb based radio will allow connection or recognize the sim to the 1700 aws network. With a cm9 based rom I can see my network, but it will not allow connection like the phone is locked, even though i have unlocked and tested the phone on other networks.
same here
Yes, I have the same 'No SIM' issue with a working WIND SIM. I've tried everything, multiple Radios, multiple ROMs. Very strange problem. I wish we had the tools that the SGSIII has for dumping and restoring the NV ram. Even stranger, I do have a the correct IMEI number in Phone, About. I have a feeling it's something to do with how the phones were carrier unlocked.
http://forum.xda-developers.com/showthread.php?t=1804117
I have made a backup of the EFS folder with EFS Pro. I tried restoring the NV ram from .bak but there was none found.
http://forum.xda-developers.com/showthread.php?t=1308546
tweebs said:
Yes, I have the same 'No SIM' issue with a working WIND SIM. I've tried everything, multiple Radios, multiple ROMs. Very strange problem. I wish we had the tools that the SGSIII has for dumping and restoring the NV ram. Even stranger, I do have a the correct IMEI number in Phone, About. I have a feeling it's something to do with how the phones were carrier unlocked.
http://forum.xda-developers.com/showthread.php?t=1804117
I have made a backup of the EFS folder with EFS Pro. I tried restoring the NV ram from .bak but there was none found.
http://forum.xda-developers.com/showthread.php?t=1308546
Click to expand...
Click to collapse
It has nothing to do with your unlock. If you've followed the steps and are still having no sim issue you may have to get a new 32k sim card from wind the older ones won't connect in a phone with lte
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Had to replace the TMo SIM card with a newer one today. Solved the problem of "No SIM".
I know this is old
I have the same problem with "NO SIM." One day i flashed so many things to my phone and one time i turned it on i got ATT on the top right corner and everything was good. I made some phone calls and texts and even browsed the web. I restarted the phone to check if it was just a fluke and it was. Ever since then i cannot get it to read my phone, but i know for sure the hardware works.
Hi,
I have an Atrix4g international (Uk retail) which is rooted and unlocked. Until about a week ago I had been running Aura ROM with a days 1.45 kernel. This was all good but I experienced some 3g data problems.
In the end I got fed up of not being able to download pictures when I received an mms and decided to flash back to my original rom. Once done I thought maybe the over clock 1.45 kernel would work with the stock ROM. It didn't and failed but I then noticed my wifi showed error where it usually said connected.
I reflashed my stock room from my recovery backup and it started working ok again. Both times I flashed my recovery it said error with recovery but the phone details read as it did before when it had the original ROM as it was bought.
Since doing I this I have noticed my phone being really laggy.... I also noticein advanced task killer that I never seek to have more than 80mb free ram.
I checked this against task manager and titanium backup and they seem to agree with the figures tb actually said I was using 100% at one point.
I even tried a factory reset fearing the hard brick stories.
I have wiped the davlik and cache and perfomed a factory wipe from recovery mode
Looks like I have a problem..
Anyone got any ideas on how to rectify this.... Is it likely to be anything to do with partitioning???
You atrix geniuses out there are my last hope so I thank you in advance for any wisdom.
Are you using the stock Gingerbread ROM from your carrier? If so, it sounds like you might need to flash a kernel that has the international RAM fix. Try downloading and flashing this if you're on stock Gingerbread.
http://faux.androidro.ms/Atrix-GB-Kernel-024r-ext4-1.00GHz.zip
That's the 1Ghz kernel made by faux123 for Gingerbread ROMs. After you flash that check to see that you have more RAM available.
Sent from my MB860 using XDA
Thanks a million!!!
jadwv2210 said:
Are you using the stock Gingerbread ROM from your carrier? If so, it sounds like you might need to flash a kernel that has the international RAM fix. Try downloading and flashing this if you're on stock Gingerbread.
http://faux.androidro.ms/Atrix-GB-Kernel-024r-ext4-1.00GHz.zip
That's the 1Ghz kernel made by faux123 for Gingerbread ROMs. After you flash that check to see that you have more RAM available.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
You absolute diamond!
Thank you so much.... Perfect fix 556mb ram free and phones running as fast as a priest being chased out of the playground.
You guys on here give priceless advice (most of the time so glad peeps like you take the time to help peeps like me...
Magic!
I'm sorry but I saw the title and just heard this in my head....
Lag city chick, lag lag city chick.... (Tyga - Rack city... stupid song)
Don't ask.
Glad to see you've solved your problem though
Knock on effect??!!
Although I now have many many more rams than an Afghani goat hearder this process has thrown up another problem. The same error message is showing up where it usually says connected under wiring settings and wiring will not activate or connect.
Yes I was trying to flash back to my stock rom (via cm rom manager-reboot into recovery-restore.....)
Ok so the story continues...
after receiving your advice I flashed the file you linked to. And as I reported ram was up dramatically but then when I tried to connect to wifi it wouldn't. I went to settings -wireless settings- checked wiring on check box to turn it on and underneath in grey writing it threw up the message "error" where it usually says "connecting..." or "connected" etc
I went back through cmrm to recovery mode and did the wipe data-wipe cache-restore rom again but did not reflash the file you linked... checked wifi and worked but ram had gone again.
Went back into clement and went through whole process in one. Ie factory data wipe-wipe cache-restored ROM-flashed file you linked to....
Set up phone again checked wifi and still shows error. But my rams are back...
???? Puzzled!
Dont suppose you have an idea whats going on?
tehrules said:
I'm sorry but I saw the title and just heard this in my head....
Lag city chick, lag lag city chick.... (Tyga - Rack city... stupid song)
Don't ask.
Glad to see you've solved your problem though
Click to expand...
Click to collapse
Thats strange cos thats what I was thinking when I wrote it... lol
Problems not yet entirely solved though..... :-(
Desperation is now setting in
Just an update... and help to solve this is really appreciated.
I have trawled the site and others regarding wifi error.
People seem to suggest its a number of things either hardware or software flashing kernels roms radios wifi fix zips etc etc
I can confirm my problem is not hardware.
I flashed back to aura and wifi function is back. And rams up to normal.....
but I have the original problem I cannot send or download pictures when received via mms.
Is there a fix for this?
I assume not and so therefore would like to ask the question does anyone know of a Stock ATRIX international (uk) retail Rom that is compattable with an ATRIX international (uk) retail phone that has been rooted and unlocked.
For some reason my recovery must be corrupt and is giving me jip.
Maybe someone knows why my recovery isn't working and knows how to fix it?
Thanks all in advance...
When I had the problem with wifi reporting just "error", I fixed it by just redownloading the kernel and reflashing it. Maybe try another recovery if that doesn't work, but I don't know why it wouldn't. :|
The wifi problem is most likely the kernel. Since you are on Aura now though with no data or MMS I would recommend changing your APN settings. Try googling the correct APNs for your carrier and changing them under Settings>Wireless and Networks>Mobile Networks>Access Point Names.
Sent from my MB860 using XDA
Dcskeete said:
I assume not and so therefore would like to ask the question does anyone know of a Stock ATRIX international (uk) retail Rom that is compattable with an ATRIX international (uk) retail phone that has been rooted and unlocked.
For some reason my recovery must be corrupt and is giving me jip.
Maybe someone knows why my recovery isn't working and knows how to fix it?
Thanks all in advance...
Click to expand...
Click to collapse
Why dont you try Nottachtrix if you want a blur based rom, or Neutrino for a cm7 based rom?
What recovery are you using? If you arent using Romracers recovery, try flashing his and seeing if his recovery fixes your problem.
Not liking the whole touchwiz layout, I decided I wanted to root my phone onto CM10, after having cm9 on my previous phone. Anyway, just checking through the files I downloaded I think I may have used a I9100G zip to root I9100 without realizing. I then (after making a backup) flashed a CM10 nightly. My phone went into a bootloop so I restored from the backup, Still no luck. Eventually I got my phone working through Odin but since then my phone has had really bad signal strength. I have tried all sorts of kernels, radios and roms but nothing changes. Any Idea of a way of fixing this?
Try "getril" from the market. Might be worth trying, otherwise I'd just try a few more radios.
Sent from my GT-I9100 using xda app-developers app
Use a modem from your region/country. Sammy's always a good choice for looking & finding.
Hey there!
Before anyone asks, I have done the following.
Searched on google/XDA for solutions
Flashed different ROM's
Changed Kernels
Wiped all cache
Did factory Reset
I am currently having bad network problems with my phone.
I am running JellyBam 6.7.0 with default kernel.
Baseband: XXLQ6
Problem
I constently get No Service or "Emergency Calls only" in areas that I've never had emergency calls in. I am not aware of my old modem or RIL, and so am completely lost of what to go from here as I haven't found posts that could help my issue.
When I reboot my phone, turn airplane mode on, or just randomly it will go into the stage above, to where it will stay without signal for 10 minutes up to days (I've had it go for 2 days with no signal). When I try to search for networks (In places where there is 100% a network) it will say "error searching for network".
I have no idea what to do, and am rather scared. There have been 2 emergency situations to where I needed a phone, and yet mine had no signal.
My second question, is if I manage to get it back to stock ICS (4.0.4) and do all the updates through KIES, will I get the original modem + RIL back as well as the ROM? Or will I still need to flash that myself.
TLDR: If I reset it back completely to stock ICS, will everything that I have done (root, flash modems, flash kernels etc...) be erased.
Thanks so much for reading, I've got so much stress rigt now.
Are you getting no service all the time or only intermittently ? Also, check your IMEI in settings/about phone to see if it's the generic one (0049.....), whatever you do tho don't post your actual IMEI here. Just a yes/know answer to the 'is it the generic one' question will do.
If it's a constant thing, call your carrier to check if it's been IMEI blocked. If it's intermittent, flash a stock ICS rom as you'd suggested. You'll end up with whatever modem/baseband is attached to the rom you flash, and yes, you'll lose root & the kernel you're currently running will be replaced by the stock kernel in the rom you flash.
MistahBungle said:
Are you getting no service all the time or only intermittently ? Also, check your IMEI in settings/about phone to see if it's the generic one (0049.....), whatever you do tho don't post your actual IMEI here. Just a yes/know answer to the 'is it the generic one' question will do.
If it's a constant thing, call your carrier to check if it's been IMEI blocked. If it's intermittent, flash a stock ICS rom as you'd suggested. You'll end up with whatever modem/baseband is attached to the rom you flash, and yes, you'll lose root & the kernel you're currently running will be replaced by the stock kernel in the rom you flash.
Click to expand...
Click to collapse
Yes it's only intermittent, so not a problem with the IMEI.
So if I find, and download stock ICS to bring it to factory it should be fine? If I were to, let's say, flash the ICS onto the phone, is there any way to keep the RIL+ Baseband and flash back JB? Or when flashing JB, will it replace whatever RIL+Baseband is attached with the ROM.
Also, thanks for the quick reply. I was expecting days for a response.
Forget about JB/custom roms/anything else until or unless you get your phone working normally again. Flash an ICS stock rom for your region.
And forget about the current RIL/baseband. It sounds like it may well be the cause of the problems you're having; quite possible if you've been mucking around with different RIL's in particular. Pretty sure I said in my PP that you'll end up with whatever baseband is lumped in with the stock rom you flash.
Actually, you might want to stick with a stock rom specific to your carrier if there is one, at least that way you know the modem/baseband will more than likely have been tested by your carrier & is likely to work well with it unless there are other issues (carrier side connectivity issues or other problems with your phone).
As to whether doing this will fix your issues, no idea. At the moment, and in the absence of any clue as to what's causing your issues, it's the best option you've got. If it doesn't fix the problems, then it's probably a carrier-side issue (possible given it only happens at certain times/in certain locations) or a physical problem with the phone (less likely).
xxshabsxx said:
Yes it's only intermittent, so not a problem with the IMEI.
So if I find, and download stock ICS to bring it to factory it should be fine? If I were to, let's say, flash the ICS onto the phone, is there any way to keep the RIL+ Baseband and flash back JB? Or when flashing JB, will it replace whatever RIL+Baseband is attached with the ROM.
Also, thanks for the quick reply. I was expecting days for a response.
Click to expand...
Click to collapse
MistahBungle said:
Forget about JB/custom roms/anything else until or unless you get your phone working normally again. Flash an ICS stock rom for your region.
And forget about the current RIL/baseband. It sounds like it may well be the cause of the problems you're having; quite possible if you've been mucking around with different RIL's in particular. Pretty sure I said in my PP that you'll end up with whatever baseband is lumped in with the stock rom you flash.
Actually, you might want to stick with a stock rom specific to your carrier if there is one, at least that way you know the modem/baseband will more than likely have been tested by your carrier & is likely to work well with it unless there are other issues (carrier side connectivity issues or other problems with your phone).
As to whether doing this will fix your issues, no idea. At the moment, and in the absence of any clue as to what's causing your issues, it's the best option you've got. If it doesn't fix the problems, then it's probably a carrier-side issue (possible given it only happens at certain times/in certain locations) or a physical problem with the phone (less likely).
Click to expand...
Click to collapse
Thanks.
I'm having problems to what official ROM to use from the list.
The only one on the list is Optus, but my phone is with virgin (on the optus network) should that be fine?
The rom is I9100XWLP8
Once again many thanks! I'll update you with the progress.
Yep. Flash the Optus rom given you're effectively using their network & see what happens.
MistahBungle said:
Yep. Flash the Optus rom given you're effectively using their network & see what happens.
Click to expand...
Click to collapse
Thanks mate, you're a champion!
No probs Post here again if you have any dramas.
MistahBungle said:
No probs Post here again if you have any dramas.
Click to expand...
Click to collapse
Just downloaded it (Hotfile takes forever) and flashed through odin.
Worked fine after a factory reset. However, Kies won't update my phone.
Network seems to running smooth, so we'll see how it goes. The more things I do, I guess the more things I can rule out.
EDIT:
I updated the phone, and I get the message "Unfortunately, Application installer has stopped". What am I supposed to do?
Factory reset
Sent from the little guy
gastonw said:
Factory reset
Sent from the little guy
Click to expand...
Click to collapse
That didn't work.
Anyhow, I managed to track down a 4.0.4 variant of the ROM I was using, and made sure the CSC, PDA and Baseband all matched up with what Kies wanted, and flashed it. I think the error occured I was trying to update a ROM with the wrong CSC and Baseband to one with the correct ones and Kies didn't like that.
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