Updating captivate - Captivate General

Currently running "Android 4.3.1" this is a SlimRom
Kernal is "3.0.101+ Semaphore", on my Samsung Captivate.
Semaphore CWM Recovery v6.0.3.8 and phone is rooted.
Should I be able to just upgrade to ie: SlimCaptivate 4.4.4 or LiquidSmooth right
over what I have?
Any opinions appreciated.

Also, I read that I need to have CWM 6.0.4.5 to install KitKat?

Inquiry & problem resolved.......

Actually...NOT SOLVED

Related

[Q] Can't flash custom roms

Hello
I have read countless of threads on how to flash cyanogenmod 10.1 and other roms but I have only succeeded in flashing an official (stock) 4.1.1 firmware.
I have tried flashing with ODIN, heimdal, through CWM and with Rom Manager but with no success. My phone is rooted, that I could do. I first flashed the stock (newer) firmware, then I went on flashing clockworkmod touch and then I rooted the phone.
I want to try cyanogenmod 10.1 or other roms but I never succeed in flashing. It always gives me a kind of error and I can't understand why. Is it because the bootloader might be locked or something? I am not sure so could anyone please help me?
I have a samsung galaxy tab2 10.1 gt-p5100 tab
Thank you in advance!

[Q] N7000 upgrade 4.4.2 ROM

as the title at above, i had some problem after upgrade the recovery from old version to the newer version, once installation done, i click "reboot recovery", my phone was dead, and cannot booted up. current running 4.1.4 stock rom, rooted kernel. Or i need upgrade my rom to 4.2.2, after that only to 4.4.2?

[Q] Help: Rom's after 4.4.2 on N8010?

Hi Everybody!
In first place thanks to everybody that reads this thread. Thanks for taking your time.
I upgraded my N8010 to the latest firmaware (4.4.2).
I have rooted and istalled a custom recovery (CWM 6.0.4.6) and installed Gnabo V.7 rom.
I am not particularly keen on TouchWiz, and I would like to move away from it.
Gnabo room (as it currenly is) reboots randmomly, and I also experience problems with my emaîl settings. (have to reconfigure sometimes...)
The issue is that after the new bootloader, it seems to be impossible to install any custom rom that is not TouchWiz 4.4.2 based.
I think that if sombedy could list the options that we have for roming, after the stock 4.4.2 update, this would really help.
Thanks again in advance.
José
Update rom
Here is what I did so far:
Stock N8010 on 4.1.2
Upgrade stock to 4.4.2
Root with Chainfire method (over ODIN)
Instal Philz Recovery
Install CM 11 unofficial rom that led to brick
Unbrick by flashing over odin 4.4.2 firmaware from sammobile
Reroot and CWM recovery 6.0.4.6.
Install Stockish rom 4.4.2 that led to brick --> sorted by backup with CWM recovery
Install OMNI rom --> Success!! only issue is to non boot over charging.
SO... OMNI rom seems to work.
See If I can try another one!
J

[Completed] My t999 s3 doesnt want to install cyangenmod

i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck
eric95204 said:
i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck
Click to expand...
Click to collapse
Do you mean this unofficial CM11: [ROM][4.4] CM 11 Unofficial - Beta 7 11-22-13 (Discontinued due to new device)?
Or this one: Cyanogenmod CM11?
Please check this thread: T999 UVDMD5 Firmware / Bootloader.
According to this, you might have to update some files (bootloader, modem, etc.) to be able to install newer CM versions.
AFAIK, only CM10 is officially suported for your device: [ROM][OFFICIAL] CyanogenMod 10 Nightly Builds for SGH-T999.
If you have further questions, please ask in the T-Mobile Galaxy S III Q&A, Help & Troubleshooting.
Thread closed and thank you.

[Completed] [Q] Cannot Flash SGH-T999

Hey Guys need you HELP.
I have a Samsung Galaxy S3 T999 which was running on android 4.3 (official rom). I rooted the device and also flashed ClockworkMod Recovery which was successfull.
I tried few roms and it did not work and i got an error which siad I have a d2spr device and the rom i was trying to install was meant for d2tmo.
now how is that possible? d2spr is for Sprint and d2tmo is for T-Mobile... and my device is T999 (T Mobile) (I REALIZED THIS AFTER MESSING UP MY DEVICE)
Later I flashed it with a custom rom via recovery menu and after that i tried loading GAPPS also from recovery mode. The custom rom was ok but gapps failed to install.
After falshing the custom rom i checked about device and it says the model number was dat of a sprint mobile (i747)
I tried other custom roms and gapps.zip but now my phone will not boot...when i turn it on it shows the SGS3 CWM screen and reboots into recovery.
No luck trying to flash it with a stock rom using odin either.
NEED SERIOUS HELP PLEASE!
Hi, thank you for using XDA Assist. First, only flash roms that are specific for your exact device. With your model number changing like it is it appears you've flashed some roms for other devices. You may not be able to recover the device. but see this, http://forum.xda-developers.com/showthread.php?t=1949687

Categories

Resources