So i hard bricked my phone a month ago and git it resurrected. I flashed the aosp based roms but every week, the mic in the phone stopped working and i have to reflash the roms to get the mic back then work. What is wrong here?
Related
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.
Hey All,
I purchased a jawbone UP this weekend and was running Slim Rom on my HD. The way the UP works is it syncs its data through the 3.5mm headphone jack. The first one I bought wouldn't get recognized at all on any 4.2.2 ROM and when I revert back to a 4.1.2 based ROM it would recognized and unlock and everything, just woudlnt sync. I ended up with a defect DOA device and had to get a new one.
the new one however now works fine on the 4.1.2 ROM. i havent tried to switch back to 4.2.2 yet but i have a hunch that it won't work.
I wanted to know if anyone else has one of these and if they are using a 4.2.2 ROM and have it working. if so what ROM and Kernel combo are you using? I didnt wanna go nuts flashing random crap just to see if it works but i'll get a feeler here and see
thanks,
It's a known issue with 4.2.2 ROM. I had the issue with my Bionic too. I ended up returning it.
I can vouch that it works on the carbon night lies.
But it works with stock
I had the same issue with my Buttered AOKP ROM. Since I used SS3, I switched to my stock ROM and everything works fine. So, I just switch ROMs (a matter of a couple of reboots) whenever I want to sync data. I know it sucks... But till Jawbone supports custom ROMs, this seems the only way to use the UP app.
I have installed UP on both ROMS (my stock ROM (4.0.3) for syncing and on my 4.2.2 ROM for my other data-wrangling stuff).
GPE kit-kat
I have the galaxy s4... i was running gummy rom 4.4.2 and had this problem. I didn't want to go stock cuz i would lose tethering ability unless I modded this separately, so i tried the Google play edition and this works for me. have been using since with no problems.
xavierroy said:
I had the same issue with my Buttered AOKP ROM. Since I used SS3, I switched to my stock ROM and everything works fine. So, I just switch ROMs (a matter of a couple of reboots) whenever I want to sync data. I know it sucks... But till Jawbone supports custom ROMs, this seems the only way to use the UP app.
I have installed UP on both ROMS (my stock ROM (4.0.3) for syncing and on my 4.2.2 ROM for my other data-wrangling stuff).
Click to expand...
Click to collapse
I installed the slimbean 4.3 ROM a free days ago and I've been experiencing some Bluetooth issues. It will randomly close, and the only way I can get the Bluetooth to restart is to reboot the phone.
now, correct me of I'm wrong please, but Bluetooth is controlled by the modern, so I'll want to maybe flash another compatible modern?
I'm using the latest version of TWRP as my recovery.
It's a known issue with 4.3 roms. You'll just have to wait until if and when the devs figure it out.
Almighty then... thanks for the reply
eachitandi said:
I installed the slimbean 4.3 ROM a free days ago and I've been experiencing some Bluetooth issues. It will randomly close, and the only way I can get the Bluetooth to restart is to reboot the phone.
now, correct me of I'm wrong please, but Bluetooth is controlled by the modern, so I'll want to maybe flash another compatible modern?
I'm using the latest version of TWRP as my recovery.
Click to expand...
Click to collapse
I have similar problem with CM 10.2 and an earlier Rom as well ... kinda learned to live with it.
So...I have had a captivate and SGS3 and have never had so much trouble with a phone. This infuse is frustrating and complicated to work with. I have blue CWM which was acquired by using Entropy's guide and the other numerous helpful tips out there. I had rootbox running which would eventually start FC'ing and acting dumb. I wiped everything the other day and flashed unofficial CM 10.2, it worked perfect then random reboots to stuck at samsung then cyanogen mod then back again. Sometimes it would randomly reboot in CWM, which has never happened to me on other phone. I feel like going back to stock and back again is the only answer, but it seems like a lot of work and I already did that and it was fine.
So, all you guys that understand whats going on behind that scenes, what do you think the issue is?
UPDATE: I found a video that may link this behavior to a hardware issue caused by poor design by Samsung having too many contacts that can get gunked up and causing issues.
Might be a problem with the version of the Gapps you're using. Consider changing and even going back to older versions. I found v 12/12 signed very stable on cm10.1.
If still stuck, consider Odin back to stock in download mode and flash cm9 and cm10.2 again!
Hello!
I was using the SungSonic ROM for almost a year now and I decided to change it today. So I flashed a CyanogenMod Nightly build for the P3100 This morning.
It booted up fine, and there were no issues in the beginning.
But then it started disconnecting calls randomly. Like, Someone calls, The phone rings for a second and boom! It shows a missed call.
I figured rebooting it would fix it but it made my problem only worse.
It now barely shows any Network service at all. If it is there, only for about 20s before it goes back off.
Is there any way to fix it without flashing another ROM? I like CyanogenMod and plus, its for my mother and I prefer keeping it simple.
Also, keep in mind that my Tab does not get recognised on any PC with any Cable I could find.
So, I am stuck with PhilZ Recovery for the P3100.
If the problem can be fixed via Flashing a new Mode/Baseband then please, give me a .zip for only the modem and not the whole ROM.
Thank You for Reading and I will hope you guys help me out.
Regards,
Shinichi Reshima
Always do a nandroid B/U before you flash so if you run into a problem like this you can go back. CM nightlys are not always stable, and sometimes you can't use them unless you have the base stable version of that ROM already installed. Must try and install the base version of the build, it may fix your problem. I run CM11 by Android Andi with no issues and no nightlys.
Pp.