Hi, I followed the procedure for rooting and flashing galaxy s2 gt-i9100 perfectly. I also downloaded the files for my device only and not any other device. The problem started 2 days back when I was on resurrection remix jelly bean rom with Aliyah kernel. I started to randomly not recieve calls. My friends complained that it would go straight to voicemail. So I took it to the service center and they told me the motherboard was screwed. They installed a new motherboard and the phone was working fine until I flashed cyanogenmod 10 with their own kernel. The problem reappeared. Is the problem because I installed the rom or what?
Dark viper said:
Hi, I followed the procedure for rooting and flashing galaxy s2 gt-i9100 perfectly. I also downloaded the files for my device only and not any other device. The problem started 2 days back when I was on resurrection remix jelly bean rom with Aliyah kernel. I started to randomly not recieve calls. My friends complained that it would go straight to voicemail. So I took it to the service center and they told me the motherboard was screwed. They installed a new motherboard and the phone was working fine until I flashed cyanogenmod 10 with their own kernel. The problem reappeared. Is the problem because I installed the rom or what?
Click to expand...
Click to collapse
Never heard of such a thing, I do not believe that a custom ROM that was compiled for the correct phone model and flashed correctly is likely to screw up the motherboard. Make the phone act funny such as losing calls? Sure, that could happen and could be the ROM or kernel or firmware, but the motherboard? I don't believe so.
I would flash the stock ROM and kernel back and see if the problem occurs again before drawing any other conclusions.
Have you tried switching baseband?
Sent from my GT-I9100 using Tapatalk 2
It could be a bad flash, an incompatible Rom, a conflicting app, bad signal or just bad Carma
I too doubt it can affect a motherboard physically. You can brick your phone when installing if something goes extremely wrong (very rare these days), but the physical board should be just fine.
Did you flash back to stock before taking it to the service center? They might not even be able to read the phone's software if it's not stock.
Most will just send you away if they see you have been flashing roms :-/
I hope it was under warranty, because if they "replaced the Mother board" on your dime, I think you got hosed. It worked fine, because they set it back to Stock.
I think they saw that you flashed a custom ROM and just reversed it to stock and told you they changed the motherboard cause i doubt it is the custom ROM fault.....just yesterday i rooted and flashed such a device and works fine
Maybe its even the baseband version the problem.....once a rom didnt booted up.on a galaxy 5 and after a changed it the device runned well
Sent from my HTC HD2 using Tapatalk 2
Maybe the new custom rom found other cell site for you always check the network and signal.
Anyway the carrier was just messing with about the motherboard they dislike custom roms.
i flashed back to the offical firmware and the problem still was there.
Related
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
Why don't you try to Odin a pre-rooted Verizon stock can be found here http://forum.xda-developers.com/showthread.php?t=1984436 to see if it addressed both our your issues?
I just had some major issues with this as well. There is something wrong with the nightly versions of CM 10.1.
Like you - I flashed CM 10.1 12/18 and found that my data was not working. I then searched this forum and found that other users were having the no data issue as well. I decided that I would do the same and flash back to an earlier CM 10 release from December, but the update did not go as expected. Due to going 10.1 to 10 I had to wipe data/cache/dalvik. At this point I got CM 10 reinstalled, but the phone came up with NO cell coverage. I went to System Settings -> About -> Status and found that the phone was no longer registering my cellular network (Verizon) or phone number. My IMEI data was dead.
Luckily in my case I had already made backups of my IMEI data per this post: http://forum.xda-developers.com/showthread.php?t=1852255
I restored my IMEI and reflashed CM 10 12/16. Everything is now working as expected. Your issue sounds identical to mine - I just spent half the day fighting with the exact same issue. I definitely learned my lesson about staying so current with the NIGHTLY builds for day-to-day non-dev use. I knew it before, it just never bit me like this.
Anyways, I hope this information helps you somewhat. Good luck!
a.p.mahaney said:
So I originally rooted my S3 using odin and a stock verizon software followed by using ez bootload unlock, ez recovery, and clockwork mod. I used the custom rom cyanogen mod, and eventually continued to update those roms when they rolled out the OTA updates. When the latest update came out on the 18th I noticed an issue with my contacts. Due to this I reverted to the 16th rom, but something went terribly wrong. At this time I tried re-rooting, tried different types of rooting and got my device working along with my contacts back, but it rendered my sim card useless. I tried everything I could find on the internet. I finally covered my tracks and took it to the verizon store. They replace the sim card, but it still didn't work. They replaced my device, and me being dumb I rooted it again. Same original rooting that worked the first time. It worked at first, but then the same issue occurred. I'm not sure what to do, I can't go back to verizon again. They will expect something this time. It makes no sense. The hardware is not an issue, there is some data error somewhere. PLEASE HELP!!!
TLDR; Crazy weird data issue maybe? Whoever can solve this will be the House of Android rooting.
Click to expand...
Click to collapse
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Hello, this is my first time posting on the forums here.
Recently I flashed the latest version of MIUI on my Verizon Galaxy s3. I decided that I preferred my previous rom; Jelly Bean's Build 10, and I restored it to my phone. After restoring the rom, I got a message saying that I was roaming, even though I am still in the same area where service has been working flawlessly. The first thing I tried to do was change the network type under network settings to LTE/CDMA but that choice was already selected. Thinking that I had no other options, I restored the stock rom that I had backed up on my device and I got the same issue. Thinking I could just send the phone back to Verizon, I unrooted the phone using the built in unroot tool in SuperSu Pro. I am now unrooted, but forgot to reflash the stock recovery (I am still using TWRP). I am just wondering what I should do about the issue, and if I were to send it back to verizon, would they be able to tell that I have a custom recovery. Sorry for being a noob and any help would be much appreciated.
Update: I rolled back to my rooted stock ROM and I used triangle away to reset the custom flash counter. I have also reflashed the stock recovery onto my device. Even though my phone appears to be unmodified I still have the same issue.
Sent from my SCH-I535 using xda app-developers app
there are SOOO many threads about how to fix the roaming issue it's not even funny....
^^^^^what he said!
This happened to me and what I had to do was ODIN to stock ICS rom and enter the code to reprovision sim. Google/forum search is your friend.
This is why Verizon locks down their phones! People who are not willing to search for a way to fix something that they screwed up is unacceptable. The bad thing is this phone is completely fixable with very little effort! Some people should not be allowed to flash anything!
I've dealing with so many issues ever since the DroidX so if there is one thing I've learned is there is ALWAYS a fix you may just need to do a little search if you can't find the resources your looking for on any of forums a simple google search will help you out.
I have two questions 1) is my only way to fix this to go back to stock ICS using ODIN? 2) Once i get back to that, what do i do in order to get to a working version of JB? is it as simple as trying another ROM? Is it ok to skip ICS and just flash another version of JB?
Background if you want it....
Followed vincon guide : http://forum.xda-developers.com/show....php?t=1773659
Started with Stock ATT 4.0.4
CWM via odin
baseb: UCLI3
I flashed JB [ROM] [4.1.2] [UCLL3] Stock Debloat to my i727 last night. Everything went seemingly smooth, everything worked with a strange exception being my exchange account wouldn't authenticate.Today my service is off about 95% of the time, then it will come on and ill get a text or two, then it goes off. voice calls dont work at all. LTE data is hit or miss.WiFi works
In phone status under network type its toggling: UTMS:3 to HSPA:11 to HSPAP15 to no service...then it drops everything and service state will say out of service and disconnected.
My IMEI is correct, I confirmed that.
It tried dialing the *#*#XXXX#*#* thing, that just said no connection and ended.
I started to go down the path of looking to flash a new radio, but that just doesn't seem like the answer to me... obviously the risk of me being wrong is high. i did check the MD5 numbers on other radios though and they came back as mismatched, so i did nothing there.
Also i wiped cache 3 times, as well as dalvek
Is there a simple solution that Ive missed or do i need to go to stock via ODIN? What, if anything, did i do wrong>
If you didn't flash corresponding UCLL3 baseband - AFAIK intermittent service is expected.
If you need to flash baseband - flash the latest UXUMA7 baseband.
Well i've actually had the exact same problem, in several variations and on several androids and here's my conclusions:
1 Magnetic storms and grid issues with the carrier. There's not much to do about these, except maybe for a making a tin hat for your phone. But, on a second thought this would also kill the signal
2 If the issue persists for more than a couple of days then the other thing for me was = radios that just didn't work with my carrier or rom. Changing these showed instant results.
I actually had this exact problem but for me it was on the carrier end. I tried every ROM and radio out there to no avail. After about a month and my parents also experiencing the issue, we called the carrier and they had it fixed in about two weeks.
Sent from my SGH-I727 using xda app-developers app
thanks for the help -
gonna try latest baseband and see how it goes
bgcole said:
thanks for the help -
gonna try latest baseband and see how it goes
Click to expand...
Click to collapse
It worked. Thanks again to all.
That's good to hear
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
Hey guys,
So I got a quite annoying problem and I already spent quite some time searching the forums and google without results. Either the solutioins didn't work or the cases I found were unsolved.
Anyway, here is the story.
I have a xperia tipo (st21i) and I rooted it and unlocked the bootloader and flashed several kernels and roms to find the one I'm most comfortable with.
I used: CM 10.0, paranoid android, super jelly bean and performa v4 in case this is of any interest.
I decided to go with cm 10.0 and it worked fine until after one reboot suddenly my SIM card was unrecognized and it said I should restart the phone with a valid SIM card. I flashed different ROM's and went back to stock now but the problem persists. I really ran out of ideas and since I'm not really skilled and rich of knowledge beyond the point of flashing and the rough structure of android I'm a bit helpless here.
Any help is really appreciated and thanks in advance
P.S.: first post
I don't know if it would work but you can try it
Try flashing ics ftf it should work fine..
follow this may work
first flash the original .ftf file then flash cm10 :fingers-crossed:
This happened to me aswell, but it was a while ago, when I wasn't even rooted yet. Went to the shop to ask about it from them and they said SIMs can go outdated or something.. They gave me a new one and it was fixed. But if you decide to ask them about this, make sure you are on stock ROM and locked bootloader, also unrooted. Because if not, your device isn't under warranty, and they can blame it on that
Sent from my C1505 using XDA Premium 4 mobile app
SmashMii said:
This happened to me aswell, but it was a while ago, when I wasn't even rooted yet. Went to the shop to ask about it from them and they said SIMs can go outdated or something.. They gave me a new one and it was fixed. But if you decide to ask them about this, make sure you are on stock ROM and locked bootloader, also unrooted. Because if not, your device isn't under warranty, and they can blame it on that
Sent from my C1505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So you are saying it's due to my SIM? It still works perfectly fine in my other phone (a samsung galaxy xcover s5690). The phone was used when I got it and I don't have any receipt or anything so I don't have warranty on my phone anyway right? Should I still visit a shop?
I also tried ICS and it didn't work either. I got the ftf file from that link : http://forum.xda-developers.com/xperia-j-e/development/rom-official-st21a-america-firmwares-t2302630
I tried flashing different kernels and roms already even after it refused to take my SIM but nothing helped. It didn't fell down or anything so I don't think anything went loose inside. Could it still be due to hardware failure?
heeey
I got almost the same problem
few weeks ago i found this thread http://forum.xda-developers.com/xperia-j-e/development/sony-xperia-tipo-dual-t2594389
about making custom roms works tipo dual by making it 1 sim not 2 well its ok with me so i used it and all was perfect
custom rom - working gsm - fast - smooth like i dont need anything else
but yesterday well my annoying gf was spamming calls while i was sleeping so i turned airplane mode On
then after i wake up i turned it off and suddenly the device can't recognize the sim any more the same problem this dude got
so i tried everything like tryin to swap the sim place - installing new rom - restore my old stock rom - hard reset - testing the sim - so i tried installing the last update stock ftf which is 11.0.A.6.5 i think it's like this using flash tools anyway it worked and the problem is solved now the phone is workin with no problems u should try it
DreamingDude said:
So you are saying it's due to my SIM? It still works perfectly fine in my other phone (a samsung galaxy xcover s5690). The phone was used when I got it and I don't have any receipt or anything so I don't have warranty on my phone anyway right? Should I still visit a shop?
I also tried ICS and it didn't work either. I got the ftf file from that link : http://forum.xda-developers.com/xperia-j-e/development/rom-official-st21a-america-firmwares-t2302630
I tried flashing different kernels and roms already even after it refused to take my SIM but nothing helped. It didn't fell down or anything so I don't think anything went loose inside. Could it still be due to hardware failure?
Click to expand...
Click to collapse
I tried other phones aswell, it was working on them, but not on my phone. Weird, but yeah, I suggest you go visit them at the shop, they can probably help you out.