Very new to Samsung in general, and subsequently the Galaxy Tab 10.1 (P7510). I managed to get the device back to stock (bought it with some whack stuff on it), successfully rooted and flashed the most recent recovery. My problem is that I can't flash any ROMs...
I guess maybe I shouldn't say ANY but i've tried SlimBean (which nobody else seems to have any problems with - me? constant bootloop fun), and D2Dyno's CM 10.1 which fails on flash EVERY time.
The Tab I bought is the Google I/O version but that shouldn't make any difference right? if anyone has any ideas or suggestions I would greatly appreciate it since I'm new and can't actually post in the development thread
Thanks in advance...
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.
Hi,
I am in the process of completely wiping my phone and starting from scratch and thought it would be a good time to try out a few diffrent roms. My plan was to keep the stock rom that came with my phone and install the latest stock rom alongside it. So i would have 4.1.2 (carrier rom) and 4.3 (latest stock rom). Then i discovered that you can dual boot ubuntu os and android and was wondering if anyone had tried this and if so how well it runs. Or if anyone has any better suggestions for a second rom for my s3,
Thanks in advance.
I'm gonna try this in the next couple of days so ill keep yous updated on how it goes.
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.
Hello everyone,
I am running into an issue where if I install a custom rom on my phone, I get no sound whatsoever. No sound from the speaker nor the earpiece. Also, related to having no sound, any app or anything I do relating to sound won't run or work on the phone strangely. (like Youtube for example, won't run)
Everything else works fine.
I tried multiple roms, and all of them ran into the same issue. When I reverted back to the stock rom or the backup I made fortunately, I get sound but I am lost as to why I get no sound from my S3 device with a custom rom. ALSO, when I do revert back to my old stock rom, I get a lot of gapp crashing for unknown reasons. So basically the phone is a DUD .
My Samsung Galaxy S3 device is model: SCH-R530U for US cellular. I hope I can find someone here who knows how to fix this issue =\.
Could it be that the Roms I installed don't have the sound drivers packaged? I made sure the Roms were compatible and all but I am not so sure since I guess I'm not really that experienced in Android.
Someone please help! I have had this issue for months with no solution or no way to fully revert back to a fresh stock rom with apps not crashing on me.
Bump, anyone?
I may be a couple years late but this means the ROM you flashed is not actually for d2usc