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.
Related
Looks like the Telus website is ready for the Gingerbread 2.3 update...
Durr: add https and www . telusmobility.com/en/ON/Samsung-Galaxy-S-Fascinate/how-to-002921.shtml
Now if only they'd actually release it
From the page:
As of July 2011, a new firmware version is available for the Samsung Galaxy S Fascinate 3G+. Before you update your smartphone, you need to know your current firmware version.
From the Home screen, tap Applications.
Tap Settings.
Select About phone.
You don't need an upgrade if the:
Firmware version is 2.3.3
Build number is GINGERBREAD.LKF9.
Interesting...the actual update page still says update to 2.2 and takes you to a page about updating to 2.2...of course a couple of weeks ago the update page listed 2.3 but had a dead link...so maybe its actually going to happen in our lifetime
have you tried connecting to kies to see if there's anything there??
Theres a new version of kies on samsung apps today but it didn't get me gingerbread yet. new version is Kies_2.0.2.11071_128_2
Yea.. I updated Kies and still nothing.. hopefully soon.. I grow anxious
I've been totally OCD about update checks lately. I'm driving myself nuts
I was the same way when i first say the update now for 2.3.4 on the update page a few weeks ago...gave up when they switched it back to a link to the 2.2 update...now i think it will be back to a nightly check
interesting, kies is suddenly only reporting my current firmware version and not saying that it's the current one... but not offering anything new yet, hopefully it's a sign of a release and not just a glitch
Fallen0ne said:
interesting, kies is suddenly only reporting my current firmware version and not saying that it's the current one... but not offering anything new yet, hopefully it's a sign of a release and not just a glitch
Click to expand...
Click to collapse
Yea.. I noticed that too. I suspect that the server it checks is just not responding, but... fingers crossed
Just checked again.. back to normal. Hopes dashed. :/
That makes me a saaaaaaaaaaaaaad panda
I think they just like toying with us
They're mean now that bell has the SII, it might be time to loose telus.
wow
Been waiting for this myself - checked the NS page and there is an annoucement to get the latest as well. Hopefully I don't have to unroot or disable lagfix before trying ... might disable the lagfix regardless though since that appears to be best practice with any ROM.
Tried but also getting the 'you have the latest firmware' message ... doh!
I gave it a shot, I'm running Bionix-V 1.3.1, and it came up with the message "incompatible device" looks like you'll have to downgrade to the stock rom anyways
..double post, I have no idea how to delete
jpmccarthy said:
Been waiting for this myself - checked the NS page and there is an annoucement to get the latest as well. Hopefully I don't have to unroot or disable lagfix before trying ... might disable the lagfix regardless though since that appears to be best practice with any ROM.
Click to expand...
Click to collapse
I gave it a shot, I'm running Bionix-V 1.3.1, and it came up with the message "incompatible device" looks like you'll have to downgrade to the stock rom anyways
out of curiosity, why not just install one of the many custom gingerbread roms out there? they're no longer the bug-ridden hack-fest they were a few months ago. seeing as some of you already are rooted or running a custom rom, i'm interested to know why wait for stock?
i do understand some people prefer to keep their phones in stock and i respect their decision.
edit: i'm personally running Darky's Rom 10.2 on my T959D. Tried CM7 (nightly 67) before as well, and although that was a headache to set up on my fascinate, it was also nice to see the differences between a samsung and aosp rom.
Japots said:
out of curiosity, why not just install one of the many custom gingerbread roms out there? they're no longer the bug-ridden hack-fest they were a few months ago. seeing as some of you already are rooted or running a custom rom, i'm interested to know why wait for stock?
i do understand some people prefer to keep their phones in stock and i respect their decision.
edit: i'm personally running Darky's Rom 10.2 on my T959D. Tried CM7 (nightly 67) before as well, and although that was a headache to set up on my fascinate, it was also nice to see the differences between a samsung and aosp rom.
Click to expand...
Click to collapse
How is Darky's any issues running it on a T959D?? Did you follow any particulr guide when installing?
How To for Darky's?
Japots said:
out of curiosity, why not just install one of the many custom gingerbread roms out there? they're no longer the bug-ridden hack-fest they were a few months ago. seeing as some of you already are rooted or running a custom rom, i'm interested to know why wait for stock?
i do understand some people prefer to keep their phones in stock and i respect their decision.
edit: i'm personally running Darky's Rom 10.2 on my T959D. Tried CM7 (nightly 67) before as well, and although that was a headache to set up on my fascinate, it was also nice to see the differences between a samsung and aosp rom.
Click to expand...
Click to collapse
Second that - what has made me gun shy is that the Telus Fascinate is actually more like a vibrant or i9000 - so custom ROMs have some risk.
That being said heard so many great things about Darky's - would love a how to from someone with our phone and how it is working ...
Heard from Samsung
Apparently not ready but its weeks away, not months.
I have a Galaxy S2, I9100, original, I had the LoS Kernel from early on, and I have had recent troubles upgrading. I've upgraded to Dream Kernal, Siyah Kernal, and several other kernals. The phone boots when I load each individual rom, however, several services fails to load.
Am I missing something? I haven't updated this phone since it first came out, and after months of "update messages" from Sprint, I've decided to update it and I'm having difficulty. I've got CWM downloaded and I've used CWM to update each rom and kernel. If I could get some direction that'd be great. I just want the latest Android version and some type of superficial visual ROM ontop. I am generally very okay with each ROM, just upset that the current kernal leaves me with a failure of signal, causing me to reboot.
Update
I currently have Kernel version 3.043-rc1-Siyah-Dorimanx-V5.78-SGII-PWR-CORE and AOKP Version ThunderBolt Rom JB by ALHuessein Mohammed and Android version 4.1.1. . My Build is ThundrBolt by ALHussein Mohammed and I can't get any of my active services to work. Wifi doesn't work, sending texts doesnt work, surfing the internet doesn't work. Nothing. I get the phone to boot, but nothing comes of my boot. I have tried several different kernels, and different ROMs, but none of them seem to fix the issue of standard services working. I'd appreciate some help with the issues. My CWM version is 6.0.1.2-Siyah. I'm pretty confused on the whole matter.
As far as my knowledge goes, the Kernel is like the underlying infrastructure, and the ROM is like the OS. I don't really know what I've done to **** this **** up, but it's no longer functioning as a regular phone. I've used ODIN before, but seeing how I have CWM, I figured it wasn't required. Any help would be appreciated. Even setting my phone back to stock, since backing up my phone through CWM didn't actually do anything, since I can't restore back to my previous version.
I'm in dire need. Please assist.
--Zach
So no one has any idea why my phone boots, but every active service fails to load? I guess I'll have to call this one a loss.
zdavidi said:
So no one has any idea why my phone boots, but every active service fails to load? I guess I'll have to call this one a loss.
Click to expand...
Click to collapse
hey ma8 first and foremost u should have patience here on XDA.
bumping Post like this will lead u knowhere and people will simply ignore the same for sure
now coming back to ur issue what i would suggest u is this before jumping into kernel flashing thing have u checked in the ROM thread of the one ur using for what kernel people r using there r any kernel related post in that thread.
if not do the same first (search that thread for post that r similar to ur issues).
also u can try the latest Siyah kernel v4.1.5 and see
zdavidi said:
I have a Galaxy S2, I9100, original, I had the LoS Kernel from early on, and I have had recent troubles upgrading. I've upgraded to Dream Kernal, Siyah Kernal, and several other kernals. The phone boots when I load each individual rom, however, several services fails to load.
Am I missing something? I haven't updated this phone since it first came out, and after months of "update messages" from Sprint, I've decided to update it and I'm having difficulty. I've got CWM downloaded and I've used CWM to update each rom and kernel. If I could get some direction that'd be great. I just want the latest Android version and some type of superficial visual ROM ontop. I am generally very okay with each ROM, just upset that the current kernal leaves me with a failure of signal, causing me to reboot.
Click to expand...
Click to collapse
Several contradicting pieces of information here that I've bolded.
The I9100 is a GSM phone. Sprint is a CDMA network. The I9100 won't even work on Sprint's network.
When I google for "LoS kernel site:forum.xda-developers.com", the first result I get is for this, which is an Epic 4G Touch kernel.
These things tell me you are not in the correct forum for your device.
The Sprint variant for the Galaxy S2 is the Epic 4G Touch, and that forum is located at http://forum.xda-developers.com/forumdisplay.php?f=1281
ctomgee said:
Several contradicting pieces of information here that I've bolded.
The I9100 is a GSM phone. Sprint is a CDMA network. The I9100 won't even work on Sprint's network.
When I google for "LoS kernel site:forum.xda-developers.com", the first result I get is for this, which is an Epic 4G Touch kernel.
These things tell me you are not in the correct forum for your device.
The Sprint variant for the Galaxy S2 is the Epic 4G Touch, and that forum is located at http://forum.xda-developers.com/forumdisplay.php?f=1281
Click to expand...
Click to collapse
Yeeeahh. I had searched Samsung Galaxy SII, and I was led here. I had forgotten that my particular phone was an Epic 4G Touch. Thanks for the direction.
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.
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.