Related
ok about to root and rom. will verizon know if i call them for service questions? what i mean is, i suppose for a tech support call they can do over-the-phone diagnostics. right? if i call for tech support are they able to determine i am rooted and rommed through their diagnostics?
would i need to return to stock prior to making a tech support call to verizon?
thanks
there are honestly very few reps that know anything about the phones they sell
I'm not sure why you'd call Verizon for diagnostics on a device that's not running their software anymore. I'd think talking to the dev would make more sense. I suppose the could tell, but care? Probably not. I told the manager where I got mine that I intended to root it as soon as I got home shd that my old Incredible was already rooted. His only question was how much better the battery life gets.
They will try to help you for sure but they may no be able to since you do not have stock. They can not look up your phone info on their end but they may ask you for info like software or info about the phone from about phone that could give it away. Honestly you're probably better off posting your issue on this forum and having XDA help.
They wouldn't be too helpful not because you rooted but because you have a different piece of software on your phone.
It'd be like calling Microsoft because your copy of Ubuntu is acting up.
>_> big red is all knowing >_> they will find you.. they will GET YOU! >_>
I don't think they can see what software you are using, but I do believe they may be able to see your radio version.
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
littleguevara said:
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone can google "My Verizon.apk Thunderbolt", download it, and put it on their phones. Even non rooted fellas. So no, this should not throw up any red flags other than you are using a modded application.
U r legally allowed to root so dont worry about it
Sent from my ADR6400L using Tapatalk
I did this a week ago, my TB lost 3G completely at the house and 4G only works in PHX. It just happens the wife's D1 had no 3G so I called and we went through some settings on the phone and they checked the IMEI number etc. Found out the following day after talking to several Verizon people that the issue was the SIM card on the phone so I took it in and they replaced it and that fixed it.
I was rooted when I called, I went back to stock before taking it in and replacing the SIM card. They knew nothing at all.
It would be wise to just find help elsewhere. I find that online support is better than verizons anyways
I am an AT&T tech rep, so I can only speak for here. Bu universally most of us, despite carrier, that know what they are doing will answer the same from what I've found.
When someone walks into the device support center with an obviously rooted I won't exchange it for them. I will help them, find answers, and tell them how to fix it. I will also explain any known problems, or past problems, I know about with various roms. But I won't exchange the phone. And it's not to be mean. But often times when a person does come in with a rooted phone the issue they are experiencing is with the radio they flashed or the rom they are using. I see this a lot with the Inspire as is.
If I deem it to be an actual hardware issue and I can very the rom is not the issue then I will tell them how to take the phone back to stock so I can exchange it. For the Inspire I keep a handy sd card with the stock image there that I can flash it back right away.
If I know a phone has been rooted and the person brings it back to me with it flashed back to stock, I will exchange it without a problem. The phone is still under warranty and the warranty does explain in most products that not current software alterations exist (Ie: rooting, clockwork mod, unlock boot loader). If it's back to stock then warranty guidelines are meet.
Now with that being said, I have physical access to the device. Over the phone, the only way they would really be able to know is if they asked the software version, baseband version, kernel version, etc... and knew what they were off hand. Things like that. They can't magically peer into your phone over the air to see what's going on with it. That's the reason for their little script techs over the phone have to run through.
Ultimately, the advice mentioned above about asking the dev or the rom thread is the best you'll get. Most times this is your best place to look after a custom rom has been flashed. If a problem is deemed hardware and not software and you have to have it exchanged, flash back to stock and take it in. No tech rep will care if it was flashed back to stock (unless they are having a really miserable day and can prove it's rooted. but that's few and far between and not specific to any company).
Just updated by GS2 to KF4 (official UK 3 firmware)
Since then, the phone has an annoying couple of faults:
Cant get GPS lock unless a battery out restart is performed
More importantly, wont connect to the internet unless the handset is restarted, and then, if I leave the phone alone and try and browse again, I need to restart it.
Full 3G/HSDPA signal; calls and texts are fine, both incoming and outgoing. Just the interwebinet.
At the moment, my phone and I are not friends. It's in 3 seperate drawers; body in the top, battery in the middle, and back in the third drawer down.
Any assistance would be appreciated. I dont want to downgrade, or fully reset the phone, beacuse:
1: I shouldnt have to. The firmware update should make things better, not worse. Whilst I realise this is a stupid statement to make, and am fully aware that these niggles happen, I'm a stubborn bastard and (for the moment) am sticking to my guns.
2: I shouldnt have to.
Cheers
Added to my annoyance is that if I have to send the phone off to be repaired, it actually has to be sent off.
Apple let me go to a store, where they just replaced the handset. Perfect.
I moved away from the restrictions that Apple imposed on their devices, right into the jaws of badly written firmware, and an awful warranty scheme.
Heh, in this world there is a lot of SHOULD NOT HAVE TO, but in the end you will cave in...
Just DOOoooooooooo it!
Incidentally, I hear you singing "iPHONE4, buy buy buy" tune.
If flashing firmware started the problem then flashing firmware is the solution. Go back to an older version, if you're not happy with the one you have.
You don't send your phone back for a software problem, whatever make it is.
I've been singing the iphone tune for years. I gave my "4" to the missus because I wanted to escape and get the GS2. Until now, it's been fine; overheated a couple of times, but apart from that, no worries.
OK, then can I downgrade back to KE1, official 3 firmware, which I had no issue with, without losing my data?
trs020382 said:
OK, then can I downgrade back to KE1, official 3 firmware, which I had no issue with, without losing my data?
Click to expand...
Click to collapse
Yeah - most of the firmware updates don't wipe, but it's always advisable to backup everything regardless. Are you familiar with Titanium Backup? It's the most commonly advised backup app, and my personal choice.
It's quite common for people to try a few different firmware versions before they find one they're totally happy with, and it seems to vary from person-to-person, so it's just trial and error on your part.
I'm sure you'll find a good one without having to send your new toy away for weeks
Cheers
Where can I find said version to attempt a downgrade? Is this to be done through Kies or some other way?
To be fair, I've been pretty restrained with this new toy. When things go wrong, I normally have them on eBay within minutes, regretting it after the smug "i showed it" feeling had worn off!
Putting it away somewhere that I can't see it, has delayed that (for the moment).
Have a look at the xda bookmarks in my signature. There's links there for official firmwares and branded carrier firmwares - just take your pick. They explain how to flash them in those threads, but it's a doddle. You just run Odin, connect the phone in download mode, select the downloaded firmware file and click a button.
Just make sure to read the 1st post in the relevant thread thoroughly and you'll be fine.
I have installed here XXKI3 POLAND (I9100_XEO_I9100XXKI3_I9100OXAKI3_I9100XXKI3-GT), but I wanted to go back to 2.3.4 (zto) that is a downgrade .... if you want to know how and whether some procedure changes? have to do some different procedure?
Leverage and ask .... POLAND 2.3.5 that I am that I quoted above is to do the procedure with the root factoryfs?? if you like, which kernel should I use??
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
I had to send my Captivate to Samsung for repair. it was rooted and they fixed it without any issues.
Most manufacturers will fix hardware issues clearly not caused by rooting. Of course, no promises.
That's the reassurance I needed. I'll get on with it and send it away tomorrow. I'll report back in a very long 2 weeks...
Sent from my SGH-I717R using XDA
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
Best luck.... if you were in America you could just take it to an att store. Just be on a stockish rom and turn it in and they would not notice lol, get another device that day. Idk how things go up in Canada though.
Dont Do It!!!!
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Well he should revert back to stock for sure but you can't roll back the counter. But as long as your stock they may not look at the counter and just fix the phone. It's been said before, there's no known case of Samsung voiding a warranty because of it.
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Because in everyone's experience they'll generally fix hardware problems even if you're rooted. Of course they have to, but they tend to. We all said there were no guarantees.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
It seems like one does not simply revert back to stock. Admittedly I'm new to this but all I can find in the development forum is the Bell kernel. The full bell system doesn't seem to be up, just the At&T. After a factory reset and old kernal I still have super user loaded and all of the bell bloatware gone. I'm sure with some due diligence I could have made a back up right after my original root but I didn't. Frustrated with the mess I created I just set the phone back up with Saurom the way I liked it.
alexige said:
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
Click to expand...
Click to collapse
It's only 14 days here. I've had it since launch on Feb 14th. Bell is synonymous for passing the buck off, contact them online and they tell you to call in, call them and they tell you go into a store, go to a store and they'll tell you to go to the original store of purchase or another another store with a repair tech on duty. Going directly through Samsung has been smooth thus far, I just hope if they have an issue they'll contact me before blowing whistles and charging my bill some erroneous fees.
I don't know who's going to read this and/or if there will be any comments to it. I just want to take this horrible frustration and downheartedness out of my chest. I hope this will be of some help for anybody out there trying the same.
Today, I've hit what I hope will be the lowest most bitter point for me as an Android aficionado. Ever since the G1 was announced and came out, I jumped on the wagon and pre-ordered from Tmo (I was a customer at that time). As soon as I had it in my hands, I began learning about its customization, user experience, etc. I came here and learned how to root it (although I registered a bit later). I've owned four G1s, two G2s, an HTC Sensation and two Tbolts. All of them motivated me to dare tweaking and customizing more and more. Always with more or less satisfying results at the end, after overcoming the always present unexpected troubles. This time, however... I feel like I've got a pretty ugly dose of failure.
<s>I'll try to make it short.</s> My in-laws came from China. They had very old phones and wanted to get iPhones. However, the screen ended up seeming pretty small for them compared to my Tbolt. They asked me if I could help them get a good phone. I came up with a couple of choices. The HTC One X and the Samsung Galaxy S2. After thinking about it, I went for the S2. Now, it was a matter of picking the right (GSM) one. Either the ATT or Tmo version. I did more research and picked the ATT (I777) version, since "that's closer" to the international version.
I purchased two of them, still sealed, from Craigslist. I just loved them! Immediately, I purchased the unlocking codes for both. I got home and inserted a Tmo SIM to test them. I couldn't wait to hand them over to them. Then, things started to go just wrong in every way...
I was shocked to see the S2 had no Chinese option in language. The only Asian language available was Korean. At some point later, I realized that the Chinese options in my other phones were probably due to HTC being a Taiwanese company. I kept searching for an answer and ended up trying a couple of apps from the market like Morelocale2, etc. But they only translated about %30 of the whole. Failure.
I kept reading and learned I could flash a ROM with the language included. After more and more reading and rooting it, I had two choices. I could flash the Hong Kong or Singapore version of the phone. Those two come with the language already installed. Even though I don't know Chinese, I managed to get some help from a dev acquaintance and found the HK (I9100) version that even had the ICS version. I followed the tut and flashed it using Odin. When it booted it looked all good. Looking at that Chinese all over the place even made me smile. I sighed and said "I'm done"... little did I know my failure was far from avoided.
First of all, I learned that only two of the four buttons work due to the kernel. Only Back and menu work. I tried to see the good side. It'd be easier for them to get used to using only two buttons. I started installing more goodies, like Chinese input (by strokes, not by keyboard), even a wonderful app I found called Buttonsavior to replace the physical buttons. I was "done" and handed over the phone; only one of them. I wanted to be sure of the procedure to go, before doing the other. Then, I realized something horrific...
As they were trying the phone, poking menus here and there to become familiar with the UI; suddenly, while testing making a phone call, I heard that phrase: "It has no sound!" I wanted to kick myself out of my own disbelief... I thought "OMG! It was so hard hard to get a hold of that ROM. Now what?" I sadly understood I'd have to restore and go back to trying to find a solution to the partially translated gingerbread version. Then, I restored and went cold when I realized what had happened.
During the restoring, I was quite glad I had backed up in case of a disaster. When I booted up and just out of curiosity of how good the sound of the call was supposed to sound, I made a call. Guess what? IT DIDN'T WORK EITHER! This is when I started panicking! I thought "OK, I restored, now what?" I quickly did a wipe, factory reset, even unrooting back to the stock ROM. Did it work? No!! No audio call! "OMG!! The phone I just bought on Craigslist it's defective!"
I didn't give up and let that make me feel down (completely). I said "OK, after all this struggle and time, at least I'm going to make the other one work." I took the other phone and made a call to finally hear the quality of the audio call. It was very good to say the least. It was very nice and clear. At this point I started to feel half of an epic failure. In less than 5 mins the phone was rooted and being updated to the HK ICS ROM. I went as quickly as I could through the initial setup. I hit the home screen and the first thing I touched was the phone call icon, dialed and waited to see what the phone was supposed to be like. Then, the half failure, became full failure. I don't remember feeling that down for something before. I threw in the towel...
The audio didn't work... that's when I realized I had just messed up two brand new S2s I bought out of a stranger's hands. I've thought about it, and I got the feeling something can be done, but at this point I'm not sure what. I feel like my brain has dried up. I struggled with this for about a week, having a massive headache at least three times. But the story didn't end there...
In a feeling of total defeat, I did the last thing I could think of... I called tech support and tell them about the lack of sound. After lot of talking and pushing for some solution (they wanted me to take it back to the 'store'), they said the warranty was good for another eleven months. They've got my info and emailed me a prepaid UPS label. You think think it's a happy ending? No. You want to know why? I can't even reset the binary counter. I even got a jig connector to do the job, but of course 'for some strange reason', it won't do it. If this isn't an example of a perfect failure, then what is it? Total lost: $900.
I'm not as good as most guys here, but I like to read and use common sense as much as I can. This time I thought to my self "I'm a dumbass, what else can I say?" Aren't I?
Thanks for reading,
Edit: Yes, I did flash a stock ROM.
Hi buddy,
I just read your story.. U will both phone work again, I am pretty sure! Try to get some experienced help! Fully restoring by flashing a stocks rom should be the help... Make sure I do it correct!
Good luck!!!
Sent from my GT-I9100 using xda premium
*you do it right..
Sent from my GT-I9100 using xda premium
I can tell you right off the bat that the reason the Home and Search buttons didn't work on your i777 (AT&T S2) is because you flashed an i9100 ROM. The i9100 has a physical home button and no search button. i9100 ROMs ARE compatible with the i777 since other than that they are identical phones, but you need to fix the key mappings. As for the audio, I'm not sure.
I don't know if I forgot to mention it, but I did flash a stock ROM.
I may not have the greatest knowledge of these things but are you sure it's not a radio issue? Have you tried flashing a different radio (one that's compatible with the ROM and region you want to install)? I know I mate who had an issue with calls after flashing a new ROM to his new S2 and the problem turned out to be the radio. Once he flashed a new one (it may have been the factory one he flashed back on to it) it all worked.
Sent from my HTC Desire using Tapatalk 2
Man that's a crazy story. Not sure if I over read it or not cuz I'm baked or not but maybe they were tinkered with before you got them? Like did audio work originally? I know I'm sure glad I found the sbf files for my old OG, since they've saved me numerous times being able to flash to out of the box status. Sounds like you might've jumped into it too quickly without ironing out all the details. Shoot I know it took me like 2 weeks thinking about just rooting my phone to finally do it a couple years ago.
Sent from my OG using XDA
Yes, that was my first thought after flashing that ICS regional ROM: the radio. And that was the reason why I decided to flash the unrooted stock ROM. But like I said, nothing! I'm sure there was nothing wrong with the phones. The second was working fine before I did it. I actually tested it over and over, kind of like to make me feel better that at least that one of them was going to work.
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
Like I said. The reason why I thought it was a radio issue (and flashed a stock ROM via Odin) was because they do have sound, but no during a call.
gazlufc said:
Hi, are you getting no sound at all or just no sound in call.
I would suggest flashing back using Odin. I've had some issue's when flashing using Odin for customers. Some have had non EU devices and wanted EU firmware flashed. After flashing i also experienced sound issues.
I found that flashing back to the earliest possible stock Samsung Rom helped in my case.
hope this help you out bro
Click to expand...
Click to collapse
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
I'd still suggest trying to flash a radio separately. When it happened to my mate he still had sound issues after flashing back to a stock ROM and it was only fixed by flashing a separate radio zip.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
The_Forastero said:
I think trying that is the only thing that separates me from having spent $900 in, virtually, two paper weights. I got this strange feeling it might be a fate prank. If so, I'll probably take a break from this kind of endeavors.
The only time I've done a radio update was when updating my G1 to 1.6. The radio file was hard to find though...
Click to expand...
Click to collapse
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
GraphicGoose said:
This could be a start:
http://www.veyka.co.uk/radios/
http://www.mofirouz.com/wordpress/2011/11/samsung-galaxy-s2-radios/
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Thank you very much mate! Really, I really appreciate it. The clock is ticking back. They're leaving tomorrow. I'll get into it and report back.
Thanks again,
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
The_Forastero said:
While trying to find the right radio, it just hit me. Should I use a chinese (ZS, ZC) version? I feel like a total n00b asking this, but... does the baseband has to do with roaming or something like that?
Thanks,
Click to expand...
Click to collapse
That one I'm not overly sure about sorry mate. Someone else might be able to chime in? But hey, considering they don't work in their current state it can't hurt to give it a try?
Sent from my HTC Desire using Tapatalk 2
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Product F(RED) said:
The modem firmware has to match the hardware. You need to the one that came with the phone. The frequencies are physically programmed into the radio and flashing a radio with a different frequency will make it not work until you flash the correct one.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
KanocX said:
Does that mean, that there are worldwide phones with different hardware chips? Isn't there any chance to reconfigure these chips?
Click to expand...
Click to collapse
The phones are identical in terms of hardware specs (i9100s I mean) but each region may have one that picks up different frequencies. No you can't reconfigure it unless the radio supports it which is rare and not the case for the S2. Like I said flash the radio that came with the phone. You most likely flashed a ROM for an S2 that was a different region and came with a different radio. The software for the radio is trying to tell the radio to tune to a frequency it doesn't support. Get it?
Hopefully you made a nandroid backup before you did anything and can restore it. Also you can always play around with it in English and then change the language to Chinese when you are done if you are able to find a rom that has the language support.
Hello. I am in need of a bit of advice. I have an S4 with Loki. I am having an issue where no one can hear me when I place or receive a call on my phone. I have already checked to make sure there wasn't any pocket lint blocking the microphone, and I have tried switching ROMs (thought it might have been an issue with AOSP, but a rooted stock ROM did the same thing). Now, I can return it and exchange it without having to pay for anything, because I am paying for the insurance. However, I am assuming that if I get one from Verizon, it will probably be updated to a version that can't be Loki'd. So I am not too sure what I should do. Should I take it back and risk my luck at getting one that cannot be Loki'd, or is there something that I might be able to do to solve this problem?
If you take it back this late in the game chances are slim to none that the new one will have MDK. That said, if it was me I would be looking into fixing it or having it repaired at a cell shop that has good reviews.