Hi all, I don't think most Vibrant users worry about it (at least from what I've seen), but do you worry about losing your baseband/EFS partition/IMEI info when flashing?
For those of you who don't know or forgot, basically some flashes can result in a generic IMEI number and you SIM card would no longer be readable under any custom ROM. You would then have to ODIN to stock and stay there forever, as that is the only way your SIM would be readable.
I know this was a problem a while ago when CM7 or MIUI was flashed, but is it even worth worrying about anymore?
Hopefully someone can inform me and others about the issue. Thank you for your time!
I'm not cause I got my efs backed up. Plus AOSP ROMS are no longer tedious to flash..just flash like any other rom. Though odining back to stock is the only way to leave AOSP I don't really care.
Sent from my T959 using XDA App
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
awebster said:
Hey laylovj,
So we only have to ODIN to stock if we're going from an AOSP rom to some non-AOSP ROM? (How common are these?)
Also, I remember hearing that if we want to go from Gingerbread (specifically CM7) back to Froyo we'd have to ODIN. Not true?
Sent from my SGH-T959
Click to expand...
Click to collapse
Yea...there are three for us VIbrant Owners...
You need to Odin back to stock w/ repartition checked if you want to go back to Sammy based roms coming MIUI and any other CM7 based ROMs.
That's great to know, thanks so much for the info laylovj.
Anyone else?
I think i backed up my efs at some point but i dont worry about it too much... at one point, flashing kernels in gb, i lost.my baseband i had 'no imei' according to my phone... i odined to stock and now im back on cm7 texting 24/7 so idk
... itd prob be aa good idea to have a backup
Sent from a cell tower to the XDA server to you.
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
TheSneakerWhore said:
Why worry now? I could understand worrying when we were toying with fire--i.e. early voodoo, etc. But almost all roms now are easily flashed and provided you follow instructions to the tee, you will have no problems.
Click to expand...
Click to collapse
I couldn't stand it if I lost my IMEI and was stuck on a stock, Touchwiz ROM. That's the only reason I worry.
younix258, I do have a backup of my EFS folder, but I guess ODINing to stock will also fix the problem like it did for you. Good to know.
Sent from my SGH-T959
I lost my IMEI a long time ago while flashing an unlocker or maybe CM7. I have this generic IMEI that has been working every since though with all the ROMs. Even Tmobile can't identified what phone I am using but they haven't shut down my service probably because I am paying $200 a month on 3 lines,.
Hmm, I wonder how often that's the case though.
From http://forum.xda-developers.com/showthread.php?t=859914,
"In case you screwed your IMEI by playing with the nv_data.bin and you are experiencing issues like:
Fake IMEI (usually 004999010640000)
Unable to download apps from the market
Unable to unlock your SIM card using your PIN
Weird apps are downloading automatically from the market
Blinking SIM card icon on the top tray… ETC"
So I'd definitely like to avoid losing my IMEI, even if everything seems to be fine without it.
Hi, i've been awaiting the arrival of ics patiently, more specifically CM9. What i'm wondering is if there is a decent version that is easy to install just so i can test it out, as i have not even seen it yet other than half our roms trying to imitate it. I see all kinds of bogus on the international forum but i'm not about to try and install one. I would just like to backup my rom, install, test and flash back UnNamed. Thanks.
None for I777 until the official I9100 release - call audio and buttons will remain broken until kernel source exists.
I suppose if you wanted to you could flash the CM9 alpha for i9100 just to mess around. Make a backup of UnNamed . Flash and Hellraise a i9100 ROM- I used Criskelo ROM. Then i made another backup and flashed CM9. Its booted fine and was able mess around. Pretty smooth overall. Texting and wifi worked. But like Entropy said, audio and soft buttons are broken so don't plan on making phone calls or using all your apps. Then just restore your backup of UnNamed to get back to your happy place.
sent from my SGSII... suckas
Hah! Yes that would be quite nice to return to a happy place. I'll try it out, sounds like it won't be too much trouble. I would just like to see it and feel it out.
Hammersuit said:
Hah! Yes that would be quite nice to return to a happy place. I'll try it out, sounds like it won't be too much trouble. I would just like to see it and feel it out.
Click to expand...
Click to collapse
Just be sure to read the OP and follow the instructions .. you'll have to flash the GApps and face unlock.. other modems available too. All in the OP of the CM9 alpha i9100 thread.
sent from my SGSII... suckas
And do NOT flash one of the releases that includes a PIT file or any that includes bootloaders (boot.bin or Sbl.bin) - you WILL mess up your phone with those.
PIT flashing will be very difficult to recover from, bootloader flashing can hardbrick you.
I have tried each release of cm9 for the international gs2 as they have come out just for kicks and they run great. Just have to use the home button as a back button and the Mic doesn't work.
Sent from my SGH-I777 using XDA App
I have done a couple things here, 1 is I used mobile Odin (which does NOT flash bootloaders) and have installed and tested two of the i9100 Samsung leaks. I have also tried EVERY version of Team Hacksung ICS just to mess with it. I even have it Android backed up.
Now for the IMPORTANT PART before you do either of these. First off I am on CM7 so maybe that has made it easy/easier to do these testing.
1.MAKE A NANDROID BACKUP of your rom.
2. DO NOT FLASH ANY OF THE SAMSUNG LEAKS SINCE THEY HAVE BOOTLOADERS. I ONLY DID IT SINCE I USED MOBILE ODIN WHICH WOULD NOT FLASH THE BOOTLOADERS.
3. The third thing (or first priority for me at least) was to already have a version of my current rom (cm7 in my case) that I extracted the rom, changed the UPDATER-SCRIPT which is found in META-INF/COM/GOOGLE/ANDROID/UPDATER-SCRIPT by ONLY removing all the first lines that deal with get-prop. Then I backed out and rezipped the complete rom. Moved it to my sdcard just in case my Android didn't work.
The Team hacksung ICS is really nice and I just wish audio on phone calls worked. I could live with the HOME button being a back button for a bit and the menu button as menu without the other two buttons. Fun to try but don't blame me if you mileage doesn't work the same as mine. I have not tried it from any other rooms than cm7.
Sent from My KickAss CM7 Captivate
Hey everyone. I have a friend who has been attempting to root and install roms on his i777 device for a while now and every time it seems like something else gets screwy. I have an HTC so I know little about the process of working on his Samsung device, I thought it would be about the same but it seems way more complicated... Anyway I think all his problems started with a bad ROM he installed unknowingly when he first attempted to root his phone. And since then he has went to ICS then back to Gingerbread and it keeps getting more crazy. He has tried to do a factory reset on it but it fails half way through now so it wont even let him pull that off.
So my two questions are:
1) What is the best way to get this phone completely cleared up?
2) And what is a good/dependable Gingerbread ROM for this device?
I did a bit of digging on ROMs and found several in the "AT&T Samsung Galaxy SII i777 Index" thread. But since I dont have this device I cant try any of them out for him, and like I said early I know little on Samsung devices.
Thanks for any help!
Bakuro117 said:
Hey everyone. I have a friend who has been attempting to root and install roms on his i777 device for a while now and every time it seems like something else gets screwy. I have an HTC so I know little about the process of working on his Samsung device, I thought it would be about the same but it seems way more complicated... Anyway I think all his problems started with a bad ROM he installed unknowingly when he first attempted to root his phone. And since then he has went to ICS then back to Gingerbread and it keeps getting more crazy. He has tried to do a factory reset on it but it fails half way through now so it wont even let him pull that off.
So my two questions are:
1) What is the best way to get this phone completely cleared up?
2) And what is a good/dependable Gingerbread ROM for this device?
I did a bit of digging on ROMs and found several in the "AT&T Samsung Galaxy SII i777 Index" thread. But since I dont have this device I cant try any of them out for him, and like I said early I know little on Samsung devices.
Thanks for any help!
Click to expand...
Click to collapse
1) Full wipe in CWM.
2) No one uses Gingerbread ROMS anymore (for the most part). As a matter of a fact we'll be getting Jellybean soon! Stick to an ICS rom, I recommend either AOKP or CM9.
EDIT: If he wants more of a stock feel, try out Mystics Glory.
Ok. Number one, if he wiped with the stock ics kernel installed, there's a chance he messed up his phone. The stock ics kernel had a severe bug in it. Number two, after he's no longer in ics stock kernel , do a full wipe including system, data, cache, dalvik, and run kernel cleaning script. Thirdly, there are a number of roms out there. Tell him to try them and see which one fits.
Sent from my MB860 using Tapatalk 2
I thought about doing all the wipes as well. I wasnt sure if they would work or not though because he cant backup and the factory restore isnt working. I told him to try it through CWM and recovery apparently neither are working well.
And he doesnt want ICS anymore because they changed how the phone connects with tether. With Gingerbread he just had to freeze Tethering Manager to get it to work in ICS Tethering Manager doesnt exist anymore so the same process doesnt work.
However Im sure he would like an ICS ROM if it unlocked tethering for him. The illuminati ROM on my Vivid unlocked the tethering for me, is there something similar for the i777?
Bakuro117 said:
I thought about doing all the wipes as well. I wasnt sure if they would work or not though because he cant backup and the factory restore isnt working. I told him to try it through CWM and recovery apparently neither are working well.
And he doesnt want ICS anymore because they changed how the phone connects with tether. With Gingerbread he just had to freeze Tethering Manager to get it to work in ICS Tethering Manager doesnt exist anymore so the same process doesnt work.
However Im sure he would like an ICS ROM if it unlocked tethering for him. The illuminati ROM on my Vivid unlocked the tethering for me, is there something similar for the i777?
Click to expand...
Click to collapse
In AOKP you can tether with no issues(it also unlocks it). As far as the other stuff, if he did a full wipe like the post above said, with stock recovery. His phone may be messed up
Alright thanks for the help. I'll see if we can get anywhere this afternoon with AOKP. I'll be back after we see where that gets us! lol
I've been using CM9 for a while now. I wanted to try CM10, so I followed the instructions exactly. Nandroid my CM9. Flash back to the original OS, no mods, wifi on, everything working fine. I installed the cm10 zip, gapps zip, wipe data and cache(2x just to be sure), and poof... EFS is broken. I shrug, it's not a big deal, I boot up EFS Pro, restore my backup of the EFS, reboot... nope, it's broken again. I make a nandroid of CM10. I flash back to CM9, fix my EFS, things are fine. Flash back to CM10, poof, broken EFS again. So I start over. I go back to stock OS, fix the EFS, then load just CM10.zip without gapps, no luck. I flash to CM9, try to install CM10 and gapps zip over it, no luck. I tried CM9 with CM10 zip on top and no gapps, nope. CM9, factory data reset, CM10 on top, with and without gapps, no luck. No combination I can think of makes CM10 work. I find it hard to believe that there's no way for CM10 to work on my phone, but right now I have to choose between upgrading to CM10 or the ability to make calls. Please, someone tell me you're familiar with this problem and you know the solution, then I can feel foolish for not finding such an obvious solution and sheepishly thank you for the answer.
tl;dr - CM10 wipes out my IMEI/EFS. How do I fix it?(cm10, not the efs, I know how to fix that)
In case it matters, I've been trying the 10/24 CM10 night, the cm9.1 from 9/09, and the original stock OS.
Use efs back-up....that should work.
Sent from my GT-I9300 using xda premium
What's your baseband version? I don't run CM myself so take this with a pinch of salt, but the newer RIL in CM10 may not be able to communicate with the modem if its firmware is too old and you may see symptoms similar to having a corrupted EFS.
Sent from my GT-I9300 using Tapatalk 2
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