Database Develop

[Q] Trouble going back to Stock

From what I have gathered... this seems to be a problem that only I have encountered, or at the very least something that I have deemed annoying enough that now I have to solve it... but I recently threw Gingerbread onto my i9000, quite successfully I might add, but I decided I wanted to go back to Froyo until the official release of 2.3 comes out of Samsung, since I am a big fan of "stock".
Problem is, every single ROM (I am at ten and counting) always results in Kies telling me that there is no update available. I have been loading only stock ROMs onto my device, so I am a little confused by this, since even the 2.1 firmwares have given me the same message. I know that, when I had Froyo loaded on stock, the message read that everything was up to date or something along those lines. Having that knowledge just means I won't be able to stop trying to put things back to stock until I see that same message again.
Anyone able to shed some light on what is happening here and how to fix it? Ideally I would love to load up 2.1 Eclair, update to Froyo using Kies and then just call it a day.
(PS. on Gingerbread I am getting some weird "static" screen popping up every time I restart... is that normal? I will take a picture and post it into the Gingerbread review forum if I can capture it.)

i was in a similar boat as you, loading 2.3 was no problem but going back is a pain in the ass.
BE WARNED! I spent nearly a day and i know a fair amount about what im doing, i even had to make the USB jig to force download mode at one point (testing different ideas) so be prepared for some issues.
what i did was use odin to flash stock JL2 (9000M bell version here), with 512 pit and a CSC file from another build (sorry i forget), bootloader update repartition clear efs checked. Thats the ONLY thing i could find to get me back to stock without any internal SD error messages.
IF YOU FLASH THE WRONG THING OR THE FLASHING PROCESS SCREWS UP YOU CAN BRICK YOUR PHONE. Read twice, do once.
See if you can find a stock rom for your area, what your phone came with, with the proper pit file and csc file.
Best of luck, you are not alone. I will definately be waiting for a less buggy leak before i switch back to gingerbread.

Kies reads and looks for the correct software for your product code and firmware tied to the supplying network .Once you install different roms you may change those details and Kies cannot find the correct details on your phone to recognise and match it to a firmware .
Spoof product keys and Kies registry patcher posts may help .
jje

Thanks for the quick answers guys... I shall plug-and-chug a bit more tonight and see if I cannot get something to work... then I will be back to post of my success (or failure).

You can use SpoofFw to trick Kies think you are on an official fw, the let Kies do the stock upgrade for you.

Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?

Wirebrook. I already replied to one of these today. Same happened to me. flashed back to jpu with a view to using kies to upgrade me to jpy but it wouldn't. So flashed eclair jm1 and kies upgraded me to jpy so I suggest that. You'll have to flash bootloader afterwards though as you'll lose 3 button reboot. But don't panic
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 rooted, ADW launcher + gingerbread theme

I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Its not an official rom its a Samsung stock rom not the rom that was supplied with your phone . Kies might update it or might not .
You have firmware provided by the original phone seller and product codes hardware id firmware id for that . Kies will see that and update .
But its going to show not the firmware supplied by the original phone seller and tied to product code etc . Then requires you to Spoof Kies for an update .
jje

@Mossy1963
I'll give it a shot this evening... I have the JM1 firmware glaring at me in the face on my desktop right now, though... not sure that worked right the first time.
@JJEgan
As long as it is all "stock" I am pretty much fine with it at the moment. Not too bothered with having it tied to it's specific product code so much, although that would be nice.

wirebook said:
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has mys product code become screwed up?
Click to expand...
Click to collapse
That error message its actually wrong, you get it because nv_data.bin could not be found in /efs folder.
This could be due to a faulty flash where Csc was not applied correctly in recovery on the first boot.
Reflash with Odin is the solution.
Sent from my GT-I9000 using XDA Premium App

@Mossy1963
No cigar whatsoever... Kies simply stated there was no update to be done. Oh well.
@LuffarJoh
Tried reflashing... didn't work either.
Aaaaand to make things weird, that sometimes-working Antenna suddenly started working with an Eclair ROM that it hadn't worked before. Then after a reboot... nothing anymore. And now I have flashed the thing back to Gingerbread and what do you know... no more antenna. I would much rather have a working phone as opposed to a "perfect-stock" phone, so it looks like I might have to get an exchange... and perhaps acquire what I was after in the first place at the beginning of this thread anyways.

Hi, I was wondering exactly the same thing after flashing 2.3.3 today. I just like the idea of being able to plug the phone into kies to get a proper release although, I've no doubt the exact same version will be available for download. Has anyone got any useful info ?

Galaxy S i9000 - Upgrading & KIES - Not happening!

Hey all,
I have a wierd problem - and was wondering if you can help. I have tried searching the forums for a solution - but could not find one (maybe I didn;t look hard enough) - so apologies...
My Galaxy S (GT-I9000) has the following spec:
Firmware - 2.1-Update1
BaseBand - i9000XXJF3
Kernal - 2.6.29 root SE-S602 #2
Build - Eclair
Over time have had the usual problem os on-going lag etc etc. But recently I started having the problem where the built in Media player and You Tube application refused to recognise and play any media. Trying to play DivX file comes back with error message: "Sorry this video cannot be played" - and the same for You Tube. The only solution is to restart the phone.
I tried to connect it to KIES to upgrade but it wouldn't have it - so after speaking to T-Mobile tech(?) ended up doing a factory reset. Now when trying to connect onto KIES - the connection is made but thats it. No indication of upgraded firmware etc etc. This I tried on several computers at work and the same result. Than when I tried on my own computer at home - it came back with the following message:
"This version of the device cannot be updated"
T-mobile have advised its a Samsung problem and have refused to help any further - and Samsung have not replied at all.
Any ideas guys?
Also - will installing Darkys ROM be a good move? Will it retain the TouchWiz UI or will that be blitzed?
Many Thanks guys
~LK~

well kies will only update the firmware you currently have...
example, if your phone is t mobile firmware, then tmobile will have to release a updated version, with their add-ons included, so i dont think its a samsung problem as we are almost upto 2.3.3 never mind 2.2 lol.
if you really want to up date your firmware you are going to have to do this 'unofficially' using www.samfirmware.com - to get the latest firmware release.
if you want to go custom, be sure to read up properly and know the ins and outs incase you have troubles,
the choice of which rom to go for is entirely down to you, we cannot say 'this rom is better than that rom'
so whatever you decide to do, be sure to read the instructions that come with it exactly as they are shown

Hi azzledazzle
I have spoken to t-mobile, and they inform me that they are shipping out 2.2 - and soon to be 2.3. Where the phone is not communicating with KIES or KIES not reporting any new firmware or KIES not updating IS a problem for SAMSUNG and not them. So you see I'm kinda stuck.
I can get the latest Samsung firmware from samfirmware.com but to be honest the long winded procedure of using ODIN etc kinda scares me. I knwo for many this is a simply process, but I don;t want to get it wrong.
Just one question - whats the advantage of having custom over original?
Thanks
~LK~

kies works for a lot of us, so i dont know whats happening where you are
anyway ODIN is relatively simple, providing you follow instrctions, in total there is only about 10 steps and you have nice new firmware
anyway there are many advantages over custom rom / original roms/
custom roms give you more speed, many more features, allow you to customise every feature of the phone and get rid of 'network branded' stuff.
you can also install funky fresh themes and completely revolutionise your device
but there are also downsides, Its possible to brick the phone (this can be fixed 99% of time), you lose your warranty, (this can be replaced by going back to stock) and i cant think of anymore lol
there are more positives than negatives, but it lies down to you..
not every android user runs a custom rom ya know lol

Hahah - so Custom wins
I'm in London - just down south of you...so not sure why KIES is saying that this device cannot be updated???
If I put a custom rom onto the device - would I be able to upgrade it to offical Gingerbread(when it comes out) with ease - or will it pose a problem?
~LK~

no, kies will not detect a custom rom
but however you can flash back to a stock rom and then it will find it

Kies requires two critical components to be in place to update .
One is a later version of the firmware to have been uploaded by the phone provider . In your case TMobile they have uploaded 2.2 or 2.2.1 you can proceed .
TMobile in your post say shipping out does that actually mean its on the servers .
Two Kies requires the correct identification of product code hardware id etc to locate the new TMobile firmware if thats not correct it fails .That usually apply to custom/stock roms .
If you have an untouched TMobile phone and cannot update its nothing to do with Samsung Kies and TMobile are your update path not Samsung .
jje

Hi
Just been on the phone to T-mob...and GAWD my ears burning...but anyway - their "THIRD LINE" support person told me that they do updates OTA, and if my phone is not getting it than there must be somethign wrong with the handset. He has advised me to either visit a local Samsung repair centre to have the phone flashed with the latest firmware or T-mob can do a handset swap...
lets see what the repair centre say - and how long it'll take.
Guys - rather than taking it to teh Repair centre - is flashing a new firmware something I can do? Is it easy?
Many Thanks for all your help.
~LK~

it is somewhat easy providing you take your time and read the instructions 2 - 3 times.
flashing your new firmware will take less than 30mins to download the required software / firmware - read the instructions and flash... it will take longer than this to send it to samsung.
BUT and this is a big BUT (like my gf's ) if you feel confused or scared... DO NOT DO IT, the chances of getting it wrong under pressure is high and if you dont know how to fix a brick, your doomed.
if in doubt..... do nout

Struggling with Cappy. Help Please.

Hi, all XDA users.
I've been waiting to post my problems here and tried a few things I could to fix then with no success.
Here's what happened.
I bought a Captivate in february in an eletronics store in Miami, and since I am from Brazil, at the time my only concern was to make sure the device was unlocked, so I tested my sim card and was OK.
So my problems started as I went back to my country, the phone works good, but some issues appeared and they are kind of major for a device like that. Here they are:
I can't download from the market ever since I bought the phone. From a wifi conection or 3G . That was disturbing me so I did the factory reset and that allowed me to use the market for a while, something like 10 minutes maybe, before started giving me the "download was unsuccessful" error. And I did the factory reset a few times . But that was only a taste .
I also can't update my phone from the 2.1 eclair to 2.2 froyo or whatever is available, through Mini Kies, always getting the "unregistered device" message, before anyone asks I tried that in a Win XP and a Win 7 64 .
I tried to do the update several times but I was never able to enter download mode on the phone.
I installed some apps using the Sideload Wonder Machine, since I wasn't able to do it using SDK tools . Perhaps because of the Win 7 64?
So I decided to leave the IPhone for this device for its greater hardware capacity and because of the Android OS overall improvement, but I can't do much with it now, and since I am totally noob, I don't really know if my device was rooted before I bought, I don't know If the best thing to do is to flash stock and start over.
Didn't flash because I am afraid of bricking it.
The one thing I know is that I was able to get rid of all the crap from AT&T and nothing changed in my phone, and I heard that I needed to be rooted to be able to do what I did.!?! Is that true? Please help.
Here are some info about my phone.
Firmware version: 2.1 update 1
Kernel version : 2.6.29
Samsung SGH-I897
Baseband Version : I897UCJF6
Thanks all for your time .

Kies Mini is for US updates. Did you try the full version of Kies? Might work for you there.
Mobile Phone's Software & Manual

Will flashing a new modem help? Did you check network settings? Call company and switch to that region. I don't know. Just some suggestions.
Sent from my SGH-I897 using XDA App

Download one click odin flash the stock jf6 and master clear.this will do a full factory reset.
Sent from my GT-I9000 using XDA Premium App

cappysw10 said:
Kies Mini is for US updates. Did you try the full version of Kies? Might work for you there.
Click to expand...
Click to collapse
I did try the full version, but I will do it again in a XP version of windows and tell what happens .
I am downloading it from the brazilian samsung domain (.com.br) .

I tried again to use the regular Kies but didn't work.
It kept saying my device is not supported .
Funny thing is that in the Kies website, as you change the country flag in the bottom of the screen, the supported devices also changes, and in Brazil there is only a "Wave" called line of devices, while seems that the cappy I can only find in Canada. My point is that the Captivate IS supported.

I had a similar problem when a bad ROM flash borked my IMEI and product code. Chances are good that whoever unlocked your phone ended up screwing this up. Check out this guide to restore a specific IMEI to the device.
Also, you won't find the Captivate supported outside of the US or Canada, since it is only sold under that name by a few specific carriers (in the US, only AT&T carries it). Outside the US, Samsung mostly pushes other Galaxy S phones. Still the same "family" of phones, but there are differences between them.

yourname146 said:
I had a similar problem when a bad ROM flash borked my IMEI and product code. Chances are good that whoever unlocked your phone ended up screwing this up. Check out this guide to restore a specific IMEI to the device.
Also, you won't find the Captivate supported outside of the US or Canada, since it is only sold under that name by a few specific carriers (in the US, only AT&T carries it). Outside the US, Samsung mostly pushes other Galaxy S phones. Still the same "family" of phones, but there are differences between them.
Click to expand...
Click to collapse
Thank you so much. When I first had the problem I figured this was one possibilitie, but the salesguy assured the phone was "factory unlocked", so no one could've laid their hands on the device to screw it up like that. Your info was very valious, I will try to do the restore and let you know.

[Q] NO GPS related to stock rom baseband? (philippines) need help!;)

Greeting XDA Devs!:laugh:
Here's my situation. As you can see my GPS does not lock on my N7000 and could not even find a satellite. I've tried a lot of fixes from the play store including AGPS patches. even modified gps.conf from system/etc though i backed up the original one. unfortunately GPS wont lock. I've flashed Angry Vt1 with the OTA update before. but I thought restoring to an earlier and stock rom would help, I restored to IMM76D.DXLR5 build with N7000DXLR1 baseband flashed Philzdxlr safe kernel with my Note but still it doesnt lock only finds my location if i turn on the mobile data but whenever I use a Navigation app "waze" and Google Maps the location where I turn it on doesnt move while im driving.
I Live here in the Philippines i even tried changing the NTP server to ph.pool.ntp.org unfortunately no results. Tried rebooting like hell nothing helped. I found some Stock ICS roms from "dr.ketan" for my country though it has a carrier indicated in it.
http://forum.xda-developers.com/showthread.php?t=1424997
like this:
N7000DXLR5---4.0.4/12.07.30-N7000OLBLR2---Download--Philippines (Sun)
N7000DXLP9---4.0.3/12.05---N7000OLBLP6---Download--- Philippines (Sun)
N7000DXLR5---4.0.4/12.07.30-N7000OLBLR2---Download--Philippines (Smart)
N7000DXLP9---4.0.3/12.05---N7000OLBLP6---Download--- Philippines (Smart)
ive not tried it since im afraid its carrier is locked to the indicated one.does it?
I used to own another N7000 which ran CM10, PAJELLYBAM. but sold it since I have a new Note with ongoing warranty. which I had no problems with its GPS. unfortunately i cant recall what stock rom was in my new note for restocking purposes since i impulsively flashed Angry VT1. i experienced ANGRY VT1 and im never going back to Cyanogen.
So it ends with my basic question for my pursuit of the fix does reflashing other stock roms from other country will fix my gps? currently im downloading JZO54K.N7000XXLSC which was posted by chronosmachine http://forum.xda-developers.com/showthread.php?t=1992573 i wanted XXLSC as stock since ill return back to ANGRYvt1 rom. Does anyone know whats the best stock rom there is? (what i mean best is the fewest issues that goes with the rom, so that maybe i could put an end to this gps dilemma)
Any ideas anyone?
Thank you and good day:good:

Today i tried another fix which is more about the innards of my note. Prying it open and slightly bending the gps antenna. Still nothing. Sigh. I found it in the at&t gnote thread. http://forum.xda-developers.com/showthread.php?t=1973727 i was convinced to do it because almost everyone who did it Worked. Im sending it to a service center later im afraid its hardware issue like the gps module.
Question if you have a device which is rooted with a voided warranty will the official samsung service center still repair your phone? Or do i still have to restock and unroot?(im sorry if i voided it myself i just like learning at whatever cost)

kingbabajigalo said:
Today i tried another fix which is more about the innards of my note. Prying it open and slightly bending the gps antenna. Still nothing. Sigh. I found it in the at&t gnote thread. http://forum.xda-developers.com/showthread.php?t=1973727 i was convinced to do it because almost everyone who did it Worked. Im sending it to a service center later im afraid its hardware issue like the gps module.
Question if you have a device which is rooted with a voided warranty will the official samsung service center still repair your phone? Or do i still have to restock and unroot?(im sorry if i voided it myself i just like learning at whatever cost)
Click to expand...
Click to collapse
Gps will not be affected by flashing different rom, maybe radio will affect it but does sound like hardware problem. If you're sending it in, you'll need to flash stock gb rom via pc odin after erasing flash counter. Service won't honour warranty if it has raised flash counter and/or root.
You don't need to unroot, just flashing 3 part stock rom will remove root.
Sent from my GT-N7000 using xda premium

thanks for the reply SpyderTracks
b.t.w if you dont mind which stock gb should I flash? like which baseband? thanks in advance! im using an international open one from europe

kingbabajigalo said:
thanks for the reply SpyderTracks
b.t.w if you dont mind which stock gb should I flash? like which baseband? thanks in advance! im using an international open one from europe
Click to expand...
Click to collapse
It's probably best to flash one with your csc that was on it originally. In theory you can flash any but to be safe as houses, best to stick with the original csc. If you don't know your original csc (I'm guessing phillipines doesn't have its own?) then any will do.
Sent from my GT-N7000 using xda premium

Rooting Galaxy s3 mini....

Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you

johnmwc2 said:
Hi, I posted about this on another thread, but was then told that there is a forum for the S3. I would like to root my S3 mini GT-18190N, running 4.1.2. Its still under guarantee so it needs to be able to unroot.
Somebody mentioned CydiaImpactor, as it would be the easiest. So I installed to my mac, ticked both usb debugging and accept unknown sources, and ran the program. Within seconds I got an error, 'Error signature bugs unavailable'.......which I posted to the thread, and heard nothing from there and still havent about what that meant. I eventually found out that it means the bug has been fixed. But that is all I got.
I just wondered, what does that mean, does it affect any other ways of rooting? I found another rooting program on here, was given the the stock firmware for my phone but that needs to be unlocked. I did ask about whether the same problem would affect that firmware, but no answer. It seems the advice given on the first thread I started, about taking this to the correct forums needs to be done, which is why I am asking here. Sorry for multiple posting its not spam, its on advice from members on here.
I am a complete novice, never rooted before. So could anybody show me a root system that works for my phone.
Thank you
Click to expand...
Click to collapse
hi bro, maybe i will buy this s3mini because i notice that it cost only 114.50 euro in my country, more than 50% less than the official price
so...
about root:
you can root the s3mini flashing the firmware with odin
else you can use cydia impactor(be sure to download the latest version from official websites)
i notice that samsung patched the masterkey bug exploited by cydiaimpactor in other galaxy phone but i dont know about s3mini 18190
however i rooted an s3mini of one of my friend s1 months ago, he has never made a firmware update and after he enabled debug usb and installed driver it work! and got root access on his phone, after root you CAN'T do ota update! you an use odin however maybe samsung upgrade to kitkat android 4.4
did you do some firmware update?

-Install TWRP (this video might be of help)
-enter recovery mode and reboot. TWRP will ask you whether you want to root or not

Hi, before I did anything I took a copy of the phone which I have stored on the laptop, windows 7. Then with CWM rooted the phone, and installed a ROM I found. The first time it didnt work, so I had to find another ROM, and install that. This ROM works but its not from my Carrier, which is EE/Orange. The Base version ends in AMJ2, which I dont seem to be able to find to get the correct ROM. The Build Number I have which is the ROM is DMod v6. It works, but its causing problems with Samsung. I have given hope of getting back to the original, but if I could get it to work with EE, it would be better. DModv6 is a US based ROM.
I hope I have explained it ok, its the first time I have done this, so not sure. Please ask for more details.
Sorry it took me so long to answer, have not been very well.
Thank you for your help

What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app

Mermaid Man said:
What do you mean by it not working with EE/Orange? What functionality do you not have?
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,

johnmwc2 said:
As I have already mentioned, its a US based ROM, which only recognises T-Mobile UK. My phone keeps loosing the connection all the time. and I have to reconnect. T-Mobile UK is the US version of T-Mobile even though we have T-Mobile in the country, but without the UK at the end of it. And believe me it is not working properly. The phone itself does work, its faster, the battery life is much longer than when it was on EE. But I am also now having problems with Samsung, they have stopped me from using their software, because they say my phone is not using the correct software.
My first try, I did get Kit Kat running, but without the CAMERA, it wouldnt work. But there again, it was on a US based ROM, and had problems keeping the connection going. That was awesome but without the Camera, it was a bit useless. If I could get a ROM thet had either EE or Orange,
Click to expand...
Click to collapse
Hey mate,
Try to use Maclaw's Recovery and KitKat ROM. They work perfectly! Flash Maclaw's recovery first (TWRP) and then wipe cache and dalvik and then flash the kitkat ROM (CM 11).
find them all here: maclaw.pl/downloads/ (stupid 10 post rule for new accounts doesn't let me post the link to HELP the user (johnmwc2)
---------- Post added at 06:32 PM ---------- Previous post was at 06:28 PM ----------
Also the reason that your phone has gone all crazy is because of the ROM you flashed (US version) probably only supports the US frequencies which is why you only get t-mobile network (in some places) as the frequencies change in each location as the phone masts give out different frequencies in different locations according to their surroundings (some frequencies penetrate walls much easier but may not go as far and vice versa).
Im 70% sure the ROM is the problem. the other 30% is me thinking maybe the ROM might not have anything to do with allowing the phone to receive phone signal ( in terms of SOFTWARE not hardware - before anyone tries flaming me). My other instinct tells me maybe its the baseband/modem version thats incompatible witht the US ROM?
just use Maclaws KitKat and TWRP!
They work a treat! :laugh: