Related
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?
Hello everyone.
As the title says I recently got my hands on a Samsung Vibrant. I have it from a friend who just left the apartment we lived in together for 5 months as she didn't need it anymore. It currently has a MIUI ROM on it and I'd like to change it to sada23's unofficial CM 11.0
The problem is however that my only previous experience with flashing ROM was with a Samsung Galaxy Chat when I slapped Jelly Bean on it which was only released in a few countries. So I went right ahead but found the amount of things I have to do overwhelming compared to when I just used ODIN on the old phone.
I'm trying to tell what the current status is of the phone and this is what I've been able to come up with so far. (also after googling what everything is and does lol)
- MIUI present so custom ROM install definitely possible
- When I booted into recovery mode I saw it has: "Semaphore CWM Recovery v6.0.1.9" (which I presume is outdated)
- BY default the MIUI ROM apparently has a superuser app (which lead me to think that the device is rooted), however everytime I try to use an app that requires root I encounter errors.
I just did a backup using the recovery mode with semaphore cause I saw this is usually a first step in all the guides I've read. However from here on out I am completely clueless on what to do because all the guides were so different from eachother and I have a feeling my phone is in a vague situation. (root/not rooted?)
So I was hoping someone here could point me into the right direction and help me get to CM from MIUI. Thank you in advance.
I'll be following this thread.. kinda in a similar situation. Although a bit worse. I had an old vibrant in a drawer from years back in mint condish!.. last thing I did was root and install recovery. Unfortunately I'm a stooge and without thinking threw a 4.4 rom zip on the phone.. booted to recovery and cleaned and tried to flash.. bottom line i'm in a bootloop now... and I gave up when odin wasn't detecting the phone.. I"ll figure that out eventually, but it would be great to just have a 4.4 Odin tar for a quick and painless install... or at least a tar from a 4.0 with root and recovery to make the 4.4 upgrade easy.
Also would be interested in knowing if the 4.4 roms work well.. Gps will be most important to me since I plan to use this as my jogging phone.
alrighty.. let's get this party started!
Edit - I think the best thing for you to do is odin back to stock then root install custom bootloader and then flash your new rom, I've heard that you can go straight to kk from stock but the guy who posted above me has problems because of that so I would try flashing an ICS ROM for the recovery first, and don't forget to make a nandroid backup
You can find all the files and programs you'll ever need here http://forum.xda-developers.com/showthread.php?t=1982728 in NOOB_IN_NEED 'S ref thread
Hope I was of some help if I was hit the thanks button
sent from the depths of paradise - Jamaica
using SGH-T959
ROM: unofficial CM11 4.4.4 by sada
Kernel: stock
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Hi, I am in the same boat. Stock standard international S3, but extremely slow. Ram usage on startup is 700mb.
Which rom would you guys suggest that is both stable (no bugs), and fast (using much less ram).
This is my everyday phone, I take a lot of photos, especially the camera should be functioning perfectly.
Any help would be much appreciated.
Edit: Last time I rooted and played around with these things were about 3-4 years ago with my Sony X10 mini. I am slowly getting back into it, reading up on the latest rooting apps etc.
@errolpl: Search in development subforum for 'aroma installer'. Usually these ROMs offer only system apps to choose. 3rd party user apps you'll have to install by your own. You can edit the header with edit-function.
@demozzracy: If you want full camera suport, I recommend NCS-ROM: based on last JB-firmware, but brilliant debloated. So slim, fast, battery friendly and all hardware working. I'm testing many LP-ROMs, but they are primarily newer, hardly better (for S3).
@rp158: Thank you!
I was extremely new just a few weeks back as well. I must say that my attempts on finding a solution for my slow S3 has been a rather hard and bumpy road.
To help you save some time, here is what I've gathered so far:
Last time I flashed phone firmware, a couple of years ago, it required a PC, a cable and some funky software.
Then when I flashed my S3 for the first time, about a year ago, I started out with Cyanogenmod and used their app+cable installer. I think this is still the easiest way to root the phone, and get started with custom roms. Even if you plan to use some other rom than Cyanogenmod.
When the phone is rooted you can install TWRP, simply done via an app on the appstore. TWRP is recovery firmware that can stay on the phone, even though you flash new roms. (The phone is divided into several separate sections, bootloader, recovery, actual system, and data area.... I don't even know much about it yet.) The important part is that it is extremely easy to flash new roms using this tool, and a micro SD-card.
Simply drop the rom zip file onto the card and flash them. (For some roms you need to flash some "GAPPS" as well. These are the google apps, like the play store etc. If you don't flash them you can't really use the phone for much.)
This is where the real problems start. Finding the right ROM.
The S3 is old, and only supported up to Jelly Bean for my 1GB international version, or Kitkat if you have one of the 2gb versions.
This has not stopped developers in providing both Kitkat and Lollipop to any version of the S3. However... as eager they are to provide the newest coolest features, just as lazy do they seem to be with their testing. (Sorry guys, but someone has to say it.)
So I've gone through some roms now... none of them really good.
The first Official Cyanogenmod I flashed half a year ago. I used this for almost a year.. but the camera would crash constantly, and the phone was not able to display video. For example movieclips on facebook.
Second ROM: Cyanogenmod has also stopped developing for the S3, so a few weeks back I switched to some unofficial version. It seemed to work... camera and video was ok, and everything had the nice Lollipop feel to it.
However MMS did not work. I could receive one and send one, next ones would require a reboot for them to work. The problem was brought up in the ROM Q/A tread, but the answer from the developer was: Sorry I don't use MMS so I don't really see a problem.
Third: Onto some next rom. This one was tagged STABLE. It was far from it. In fact it was even easier to discover that this rom had the same MMS problem. Because the message app would crash immediately when trying to send one.
4th attemt was the same rom, but a different kernel... still the same problem.
5th rom was Blisspop... Wau, this was beautiful! Cool webpage, Cool animations.... it was just too bad that the site is dead, and that the rom can't even run for 24 hours without the android keyboard crashing 25 times or so. Also Blisspop has OTA updates... the only problem is that it constantly says that there is a new version for the S3.. but the download fails. Apparently some bad change to the website caused this, and apparently this problem has been going on for 3 months without anyone bothering to fix it.
6th was Archidroid. The second to top ROM for the S3. It looks cool, and has many features... but just as other Lollipop ROMs, sending MMS's without error is not one of them....
I've really tried everything. People always says that the MMS problems are due to APN's not being set up correctly, doing some reboots etc.... but trust me... I've set them up so many times you wouldn't belive it.
7th. After reading this thread and rp158's recommendation of NCS-ROM I'm now running that one. Without a single thing being set up, I was able to send and receive MMS's right away.
However... now I'm stuck back at the ugly kitkat look, and Touch wiz.
tl;dr;
So what do I want to say with all this?
Get root and TWRP and start playing around with ROMs
Lollipop does not look like an option for the S3, at least not right now
Don't let yourself be fooled by nice webpages or [STABLE]-tags, or comments that say: "I've been running this since yesterday.. it's 100% stable!"
Timusius thanks a lot for that post.
Puts things in perspective.
As I said in my post, I am ok with the KitKat look, as long as it is stable, I am always on call at work, and cant afford constant phone crashes.
I am going to try the root/twrp to NCS rom in the next couple of days
@Timusius thank you for your post. You help me a lot!
S5 Sensation
errolpl said:
Hi guys,
I'm new here. I didn't root my S3 yet, but I want to do it and install new rom. But first I would need your help with Rom choosing, as I'm completely blind in this matter
The thing is, I would prefer a ROM which let me choose which application I want to install on my phone and which not - check/uncheck option. This rom should be FAST and stable.
As I have no experience at all, I would like to ask you which ROM will be the best for me? Btw, it would be great if I can choose language (Polish).
Hope you will help me
Regards,
Karol
edit: sorry for typo in the topic, impossible to change it now
Click to expand...
Click to collapse
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Cooldato said:
It's 5 months already that im using S5 Sensation rom for i9300/9305 ( 4.4.4 kitkat). This rom has S5/Note4 features and works great im satisfied. No problems so far, no bugs, etc ^^
It comes with AROMA installer and lets you to choose which apps you want to install and which not.
Click to expand...
Click to collapse
How you install those rom?
Pixelzack said:
How you install those rom?
Click to expand...
Click to collapse
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Cooldato said:
Device must be rooted + newest cwm recovery installed. After that you just download custom rom, move it to ur phone memory/sdcard and flash it throught recovery mode
Click to expand...
Click to collapse
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Pixelzack said:
My phone already rooted without cwm,can i just install cwm like i did to root my phone?
Click to expand...
Click to collapse
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Cooldato said:
https://www.clockworkmod.com/rommanager here is the latest CWM versions for smartphones, but its .img file and u cannt flash it directly from Odin. U need to make .img into .tar.md5 odin flash-able file by some tools, or flash it via adb shell, etc.
Anyway here is Odin rdy .tar file , go to this link http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744 download recovery-cwmtouch-6.0.3.2-GTI9300.tar and flash it via Odin / Download mode.
Click to expand...
Click to collapse
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Pixelzack said:
Can I use this one?
http://forum.xda-developers.com/gal...covery-clockworkmod-touch-6-0-3-2-gt-t1719744
Click to expand...
Click to collapse
Sure, thats what i linked you above.
Cooldato said:
Sure, thats what i linked you above.
Click to expand...
Click to collapse
Hahaha Thanks dude for helping noob like me
Pixelzack said:
Hahaha Thanks dude for helping noob like me
Click to expand...
Click to collapse
No problem Feel free to poke me if u meet some troubles ^^
Cooldato said:
No problem Feel free to poke me if u meet some troubles ^^
Click to expand...
Click to collapse
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Pixelzack said:
How to install this?
http://forum.xda-developers.com/galaxy-s3/development/i9300-to-n00t-bring-lte-fun-to-3g-t2886574
just need some detailed guide xD
Click to expand...
Click to collapse
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Cooldato said:
1. Install ClockworkMod(or PhilZ) recovery
2. Put ROM on your SD card
3. Enter recovery mode
4. Perform a full data wipe(except you're running previous versions of back-to-n00t)
5. Flash ROM
6. Flash SuperSU
Click to expand...
Click to collapse
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Pixelzack said:
perform a full data wipe means "Factory reset"?
How to flash rom? It's included in the recovery mode?
How to flash SuperSU?
Click to expand...
Click to collapse
yeah this means doing a "Factory reset", must be done throught Recovery mode, wipe data, wipe cache, wipe dalvik cache.
Put ROM on your SD card, then enter Recovery Mode by pressing Home + Volume UP + Power buttons and ull have smth like:
Install Zip -> Choose Zip from /Storage/Sdcard (External SDcard) , Search for ur ROM file and start flashing :X
Flash the SuperSu .zip file same way as flashing ROM.