So after this 4.2.2 10.2 update on the Verizon Galaxy S4 which now changed the baseband version to I545VRUAME7 I can no longer access boot recovery to install the latest 4.2.2 10.2 CM Nightlies. That I have deduced from google search.
What I do not understand is why is CM NIghtlies still releasing newer and newer 10.2 nightlies for the Verizon Galaxy S4 if you can not boot into recovery yet.
I really hate the factory operating system. Facebook never works right and I can not even use my Smoothie King APP!!! It keeps force closing. Not to mention, the keyboard is extremely slow and buggy too.
Is there something I do not know?
Thanks
Because anybody who bypassed the bootloader under the old software version (MDK) still has a bypassed bootloader, and some of them want CM10.2. It's only the stock update that breaks the bootloader exploit, not Android 4.2.2 and above in general. You can still install new ROMs to the phone forever as long as you hacked it under MDK, and never put completely stock, unrooted ME7 on it for some reason.
Your question have been answered, but I don't know how you or anyone else is having issues with the stock ROM. Any apps force closing or going slow such as facebook are not the ROM's fault, its the app itself. So you are stuck with the factory ROM for now, and who knows how long. I have been on the stock ROM and it still runs fast enough for me and i've rooted every phone I've owned since the G1.
AsaSpades said:
Your question have been answered, but I don't know how you or anyone else is having issues with the stock ROM. Any apps force closing or going slow such as facebook are not the ROM's fault, its the app itself. So you are stuck with the factory ROM for now, and who knows how long. I have been on the stock ROM and it still runs fast enough for me and i've rooted every phone I've owned since the G1.
Click to expand...
Click to collapse
Had the same issue on the previous 10.1 stock rom. The CM Nightlies ROM fixed my problems and made the Galaxy S4 much faster.
Related
Hello, I have the "4g" flavor white back T-Mobile version of this tab and with there being different flavors of the 10.1 I am not sure which rom to use. After rooting the phone and getting revovery installed CM downloaded and installed the wifi version of the rom. I thought I found the nightly thread of the tmo version but revovery wouldn't install it saying that the build version was wrong. So I have gone back to stock until I can get this issue cleared up. I think my build prop may be wrong in the device because com.phone.android force closes on boot on the stock rom (I think I need to reinstall stock). But I am still not sure which flavor of the rom to install. I want the CM ICS.
I am not new to installing and using custom roms. I have been doing this since the MT3GS and have been using CM on that since Froyo. I am currently using MT4GS and currently have the CM ICS alpha 4 on it. I am just a bit confused at this point since it is not cut and dry.
c0c0c0 said:
Hello, I have the "4g" flavor white back T-Mobile version of this tab and with there being different flavors of the 10.1 I am not sure which rom to use. After rooting the phone and getting revovery installed CM downloaded and installed the wifi version of the rom. I thought I found the nightly thread of the tmo version but revovery wouldn't install it saying that the build version was wrong. So I have gone back to stock until I can get this issue cleared up. I think my build prop may be wrong in the device because com.phone.android force closes on boot on the stock rom (I think I need to reinstall stock). But I am still not sure which flavor of the rom to install. I want the CM ICS.
I am not new to installing and using custom roms. I have been doing this since the MT3GS and have been using CM on that since Froyo. I am currently using MT4GS and currently have the CM ICS alpha 4 on it. I am just a bit confused at this point since it is not cut and dry.
Click to expand...
Click to collapse
I have this one on now There are also CM9 nightlies on the CM site I believe but no issues with this other than camera. There is a camera patch also that makes the back camera work.
http://droidbasement.com/db-blog/
Here is the thread with the camera patch.
http://forum.xda-developers.com/showthread.php?t=1787399&page=65
Not sure why not many people help on this device it's a very nice device and works great on the T-Mobile network but anytime I ask anything no one ever really answers.
This thread will help you get started
http://forum.xda-developers.com/showthread.php?t=1446500
Thank you very much!! I think I have the wrong recovery installed which is causing all my issues. It is seeing my device as a wi-fi only device and not a tmo device.
I just got home a few minutes ago, and I had the wrong recovery installed. I got the right one in and everything is going swimmingly so far. Thank you again!
I wish there were subforums for every flavor instead of everything all mixed up. It makes it confusing when you are dealing with 80 different versions of the same device.
Okay...I have had this problem for a while now and cant find a solution to the current problem. Here goes. I have the Samsung Galaxy Note I717M. This is the Canadian version to the AT&T Note I717 I have been rooting my phones for several years now and pretty familiar with the ongoings of the whole process. I rooted my phone via ODIN and put a custom rom onto my Note with no problems. Everything works great! Where I run into a problem is when I decided to go with the Jellybean update 4.2.2. The Jellybean rom I am using is called Jellybam version 7.8.0. ParanoidAndroid Ver. 3.15 quincyatt_jb-mr1_build-6. When I installed it everything seemed to work fine for the first couple of days. All of a sudden my phone started to freeze where everything was non functioning. This frozen state would last for about 15 seconds then my screen would go completely light blue for another 5 to 10 seconds then turn off and reboot. It doesnt do this with any 4.2.1 custom roms. Only with the 4.2.2 version. Does anyone have this similiar problem? Is there a fix for this? I love my custom 4.2.2 rom and dont want to go back to any other earlier Android OS and rom. Can someone shed some light as to what is happening and is there a proceedure that needs to be followed or done differently so that this doesn't continues to happen. Or yet again is the a know issue? Any insight to fixing this problem would be greatly appreciated! I await your helpfull tools and hints. Any help I will be happy with.
thanks Guys
Paul
This is a known issue on Kelly bean roms. Oddly, most people are having less reboots with the new 4.2.2 over the 4.1.2 .... The issue is the kernel. There is no source to build from yet. So ... There are issues.
I have had a lot of freezing and reboots on many of the jelly roms. I'll tell you that you rom, jellybam, is not supported on xda.
I'm am currently on the unofficial AOKP and having great luck. You may want to give it a go.
Im new to flashing roms but have a slight idea as to what im doing. I am looking for a 4.4 kitkat rom specifically for the tmobile version (sgh-m919) of the s4. Or if there is a specific process to making it work with that phone. I installed the google play edition that I downloaded from XDA but had serious signal problems that weren't present with the stock rom. I then installed the cyanogenmod version and the signal problems went away and everything was going fine then suddenly my google apps stopped working for no apparent reason. Can someone help my greenhorn ass??
alexwah said:
Im new to flashing roms but have a slight idea as to what im doing. I am looking for a 4.4 kitkat rom specifically for the tmobile version (sgh-m919) of the s4. Or if there is a specific process to making it work with that phone. I installed the google play edition that I downloaded from XDA but had serious signal problems that weren't present with the stock rom. I then installed the cyanogenmod version and the signal problems went away and everything was going fine then suddenly my google apps stopped working for no apparent reason. Can someone help my greenhorn ass??
Click to expand...
Click to collapse
have you wipe everything when flashing the CM ?
and use the 4.4 gapps ?
Years ago a friend installed CM7 on my Atrix and now it's pretty unstable. I would like to reinstall the ROM fresh. The question is, which ROM should I install. (He didn't backup before installing CM7)
I'm thinking it would be nice to go back to an official ROM but, there is CM10.1. I'm leary of going back to CM because the 10.1 ROM is not official and it doesn't seem there will be much improvements for CM on an Atrix 4G.
I'm leery of going to an official ROM because I see all the banter of bricking it with Gingerbread.
Suggestions?
Atrixor said:
Years ago a friend installed CM7 on my Atrix and now it's pretty unstable. I would like to reinstall the ROM fresh. The question is, which ROM should I install. (He didn't backup before installing CM7)
I'm thinking it would be nice to go back to an official ROM but, there is CM10.1. I'm leary of going back to CM because the 10.1 ROM is not official and it doesn't seem there will be much improvements for CM on an Atrix 4G.
I'm leery of going to an official ROM because I see all the banter of bricking it with Gingerbread.
Suggestions?
Click to expand...
Click to collapse
The real question is what version of android do you want to run? CM7/7.2 is the only official CM ROM. CM10.1 is not official b/c of the kernel issues, which is still being worked. Does it really matter if a ROM is official or not? No. "Doesn't seem there will be much improvements for CM on an Atrix 4G."? Really? I'm not even going to post the link, I'm just going to say go google android version history and see what CM9, 10, and 10.1 have that CM7 does not have, and then restate that noob statement. Seriously, you have no idea what you are talking about.
Multiple users, including myself, have unlocked, rooted, restored to stock, many times over the past 3 yrs. In addition, there are guides readily available to help you through the process of preparing your device for custom ROMs. So the concern of bricking is a non issue unless you don't know what you're doing. Banter of bricking it only exists if you flash the incorrect sbf. Its not that hard. Sit down, read guides, ask questions as needed.
Let me be the first to admit that I am a noob and have no idea what I'm doing because this is my first foray into the world of smart phones (we all have to learn somewhere).
I went ahead and put CM10.1 on there and after adding the fixed gapp package it seems to be working fine.
Does anyone have a working link to a gingerbread ROM that works for an AT&T Atrix 4G? The links on this tread are dead: http://forum.xda-developers.com/showthread.php?t=1163342
I've read as many posts on this problem from the S3 through the S5 and have still not come up with a solution to the problem that's plaguing my S3. There are a lot of different hypothesis across the internet about the cause of this problem. I'll give the details with my personal experience.
As a side note, there is a possibility I could have flashed something wrong or rooted something wrong, but, given every other application works with no force closes on anything, I'll assume that everything was rooted and flashed correctly.
I've tried a couple of different ROMs after rooting the SGS3, but have stuck with Wicked. Unfortunately, I did not try out the camera until I came across Wicked, which is where the problem presented itself. This does not mean that it's Wicked itself, but possibly a problem further along than that.
Here's the specs on the phone.
I went from a fully updated software version on the T-Mobile USA Samsung Galaxy S3 non-LTE to
Android 4.1.1
Baseband T999 UVUEMJC
Kernel 3.0.65 Deviant
Build Wicked V10
I've tried the normal Force Stop Camera then clear Cache, cleared Davlik, tried other cameras, Factory Reset twice, reloaded ROM, and will flash new baseband (4.1's) My guess is that's the problem, possibly.
I've checked hardware as well from tightening screws, covering the camera, and removing the rear camera and plugging it back in; no change. As well as testing the hardware via *#0*#. The front camera works, rear/Mega does not. Which leads me to believing it's a software issue and not a hardware issue.
Flashing CM 11 - M9 on I9300, stock camera is missing
I have flashed CM11 - M9 on my Samsung Galaxy S3 (I9300) freshly, doing factory reset and wiping all the data, then flashed PA Gapps Full Modular version. After booting the phone, was getting a prompt "Google Keyboard has stopped", there after was unable to get the keyboard option at all, during setting up the phone and CM account. Again, wiped, factory reset, clear cache and freshly flashed the CM11 - M9 without flashing PA Gapps this time. Booted the phone, got the setting done, noticed that Gapps are already installed in the phone. And CM stock Camera is missing
I have been using CM 11 since a long time, but issue arrived when I flashed Gapps 4.4.3 (Google Stock), my CM camera has been replaced with Google Camera which sucks, thereby I have decided to reflashed my phone with CM11 - M9. Now the Stock CM Camera is missing.
Someone, please suggest, how to fix this issue??
Gaurav Kumar said:
Someone, please suggest, how to fix this issue??
Click to expand...
Click to collapse
I would suggest trying to start a new thread instead of posting a problem that is no where related to the problem at hand. Might give you some better feedback.
I've brought back the Galaxy S3 back to stock:
Android Version: 4.3
Baseband: T999UVUENC2
Kernel: 3.0.31-1962493
Build: JSS15J.T999UVUENC2
Lo-And-Behold the camera and everything else works now. Definitely a software issue or a flash issue with Wicked ROM 10
I may flash it again in the future, but for now the stock ROM is much more stable all around and will continue using it, rooted of course.
do you have a link where to find the stock rom?
thnx for so far
caffeinetripp said:
I've brought back the Galaxy S3 back to stock:
Android Version: 4.3
Baseband: T999UVUENC2
Kernel: 3.0.31-1962493
Build: JSS15J.T999UVUENC2
Lo-And-Behold the camera and everything else works now. Definitely a software issue or a flash issue with Wicked ROM 10
I may flash it again in the future, but for now the stock ROM is much more stable all around and will continue using it, rooted of course.
Click to expand...
Click to collapse
Rick_v1989 said:
do you have a link where to find the stock rom?
thnx for so far
Click to expand...
Click to collapse
I believe that I downloaded mine here at SamMobile. It's pretty self explanatory and has given the best information on reverting back to stock firmware, let alone the choices for the models and firmware are second to none as I've searched and searched across many websites. It offers, as far as I can tell, the most recent firmwares for all Samsung phones across many/all carriers.