Related
I have a few questions to ask.
1. How do I keep CWM installed on the phone? I was able to get it to ODIN and have it, but every time it restarts, it's lost.
2. What is the best ROM for this device? I really would like to keep some of the Samsung/Touchwiz elements.
3. What all do I have to know to do anything on here? Let's say... On the Droid X, I had an .apk to one click root. I used ROM Manager to reboot to clockwork and from there I just selected the zip for the ROM I wanted installed. Is there anything special for this device I'll have to do on here? I already have it rooted and I already know I'll have to use ODIN for a lot of things, but I don't really know what it's purpose is I suppose.
4. Is there an easy way to get rid of Bingware/VZW Bloatware?
Thanks!
I have an asnwer to questions #2 and 4. By far the best rom is COMROM 2.0 , which u can find in fascinate development thread. The answer to question 4 is, yes there is an eassy way to get rid of it, all u have to do is flash comrom it gets rid of all the bloatware for you (like I said its the best rom out there)
Sent from my SCH-I500 using XDA App
1. If you are running the stock 2.2 OTA updates from verizon the stock kernel is what is holding your CWM back. It will reinstall the stock recovery every time you reboot.
-The best way to elevate this problem is to flash a new kernel. There are many to choose from and not all will work with your fascinate.
-If you choose to flash Unlimate Kangbang (comm ROM) you can flash a kernel and ROM in one nice little package. See the sticky in the dev forum for more kernels and info.
2. This is really up in the air. Many will say Kangbang (comm ROM) simply because they use it and it is spear headed by a majority of the developers for our phone. There are 5 or 6 options for you to choose from and reading over their features would be best.
-Cyanogen MOD 7 is in the works and currently there are two versions. Koas's version is said to be slightly more buggy then JT's. Neither have fully working camera's as of yet. The word on the street though is that JT may have a fully (don't quote me) working release in the coming weeks. If camera is not a deal breaker check it out.
3. I would check here ---> http://forum.xda-developers.com/showthread.php?t=948722
-This post is a little out of date but it is rich with information on the fascinate. ODIN will be your friend, it is what we use when things go.... not as planned. There are many ODIN packages (radios, ROMS, etc) that will clean the fascinate of previous installs and take care of some problems you may be having if you flash a lot. It should be noted now that most of the ROMS out are already ROOTED so one click and other methods are not needed completely.
4. Yes. If you simply want a stock touchwiz ROM then you can look them up in the sticky. Many of the Devs debloat and debing the stock releases for those that choose that route as an alternative!
Cheers!
gkirby11 said:
1. If you are running the stock 2.2 OTA updates from verizon the stock kernel is what is holding your CWM back. It will reinstall the stock recovery every time you reboot.
-The best way to elevate this problem is to flash a new kernel. There are many to choose from and not all will work with your fascinate.
-If you choose to flash Unlimate Kangbang (comm ROM) you can flash a kernel and ROM in one nice little package. See the sticky in the dev forum for more kernels and info.
2. This is really up in the air. Many will say Kangbang (comm ROM) simply because they use it and it is spear headed by a majority of the developers for our phone. There are 5 or 6 options for you to choose from and reading over their features would be best.
-Cyanogen MOD 7 is in the works and currently there are two versions. Koas's version is said to be slightly more buggy then JT's. Neither have fully working camera's as of yet. The word on the street though is that JT may have a fully (don't quote me) working release in the coming weeks. If camera is not a deal breaker check it out.
3. I would check here ---> http://forum.xda-developers.com/showthread.php?t=948722
-This post is a little out of date but it is rich with information on the fascinate. ODIN will be your friend, it is what we use when things go.... not as planned. There are many ODIN packages (radios, ROMS, etc) that will clean the fascinate of previous installs and take care of some problems you may be having if you flash a lot. It should be noted now that most of the ROMS out are already ROOTED so one click and other methods are not needed completely.
4. Yes. If you simply want a stock touchwiz ROM then you can look them up in the sticky. Many of the Devs debloat and debing the stock releases for those that choose that route as an alternative!
Cheers!
Click to expand...
Click to collapse
1. How do I know which kernel will work with my phone? And if it's easier, I would prefer to just shoot a ROM with kernel at the phone instead of installing separately.
2. What 5 or 6 am I looking at? I know about the COMM ROM, but I'm unsure I actually want to head that route due to the fact that I don't want to go COMPLETELY stock. After using this phone for a little bit, I really like some parts of Touchwiz, and I'd prefer not to lose that.
3. Thanks for the link. I'll definitely read that over.
4. What sticky are you talking about? I'm looking to get rid of Bing ASAP as this is just killing me when I want to use voice commands or search for anything.... It heads to Bing. I wouldn't mind Bing if I had a WP7, but this is a Google Experience.... Well, technically, it's not, but you understand what I mean.
There are ODIN packages in the development section that have a rom, kernel, etc. You can get a package that is stock... but no bloat, no bing. That would be pretty easy to do. Just make sure you backup data on your phone prior to messing with any of this. Really, I would still recommend com rom, ef, or miui wiz.
Posted from my Samsung Fantastinate using Voodoo magic
jptech7 said:
There are ODIN packages in the development section that have a rom, kernel, etc. You can get a package that is stock... but no bloat, no bing. That would be pretty easy to do. Just make sure you backup data on your phone prior to messing with any of this. Really, I would still recommend com rom, ef, or miui wiz.
Posted from my Samsung Fantastinate using Voodoo magic
Click to expand...
Click to collapse
I don't know what I'm looking for. This forum is too jumbled with thousands of other ROMs and kernels and just everything.
the Evil Fascination rom thread answers a lot of your questions. It includes a kernel, it's voodoo'ed, and its debloated. if you want some of the samsung tw stuff, theres a portion on that thread where you can install it individually.
i'd start off finding a debloated/deodexed stock package and flashing that plus any custom kernels and mods and stuff you may want. Then check out the roms you might want, the two major ones right now being ComRom and CM7, but there are Evil Fascination, Dark Revenge, Superclean, and others which are stable and debloated as well.
tapatalked from my rooted/debloated stock eb01 Fascinate
Can you guys just link me to a ROM that's debloated? All I want is Google back so I can give this phone to my mom so she can have a good phone for once.
Shamrock13 said:
Can you guys just link me to a ROM that's debloated? All I want is Google back so I can give this phone to my mom so she can have a good phone for once.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1044406
You want the second link in the OP.
MrBigFeathers said:
http://forum.xda-developers.com/showthread.php?t=1044406
You want the second link in the OP.
Click to expand...
Click to collapse
Doesn't really help. I flashed it, and it still gives me the Bing search when I hit the search button.
Shamrock13 said:
Doesn't really help. I flashed it, and it still gives me the Bing search when I hit the search button.
Click to expand...
Click to collapse
So I ended up installing EF, the MIUI, and the CommROM. I was just testing them for 10-15 minutes. So far, I like the CommROM the best, but I think MIUI is close.
I've been using CommROM all day, but I hate the colours. I wish it was more a standard Touchwhiz colour palette instead.
Also, I cannot seem to get the time to show up in the status bar. I unchecked the box in TSM parts and restarted my phone, but it's still not showing up. Is there something special I have to do?
change the text color setting in status bar settings in tsm parts, then reboot. As for the rest of the colors; there are plenty of themes for comrom 2.0
Sent from my SCH-I500 using XDA Premium App
Hello,
I would appreciate any input.
My Vibrant has a custom ROM (Trigger v2.8.2) and I would like to move to ICS.
It seems that the safest way to do so would be by going back to stock 2.1 as stated here http://forum.xda-developers.com/showthread.php?t=849028
Then, I would have to follow these steps
http://www.youtube.com/watch?v=do6mTvgfH8Y
Could anyone please confirm whether:
1. This is the safest way to move to ICS ? I read about risks related to installing Gingerbread Bootloader and would prefer not taking any.
2. Going back to stock 2.1 means I will lose root and will have to root again (I rooted it long time ago and no longer remember what I really should expect while flashing) ?
Thanks
Vadim1 said:
Hello,
I would appreciate any input.
My Vibrant has a custom ROM (Trigger v2.8.2) and I would like to move to ICS.
It seems that the safest way to do so would be by going back to stock 2.1 as stated here http://forum.xda-developers.com/showthread.php?t=849028
Then, I would have to follow these steps
http://www.youtube.com/watch?v=do6mTvgfH8Y
Could anyone please confirm whether:
1. This is the safest way to move to ICS ? I read about risks related to installing Gingerbread Bootloader and would prefer not taking any.
2. Going back to stock 2.1 means I will lose root and will have to root again (I rooted it long time ago and no longer remember what I really should expect while flashing) ?
Thanks
Click to expand...
Click to collapse
I tried that before and it's safe.
-odin back to stock
-flash CM7
-flash ICS rom of your choice
But beware, it may cause some problems like the rainbow thingy other than that it's safe.
Sent from my ICZen'd Vibe!
See my guide in the General Section. It works. Read it, watch the video ( beware though that djeddieone skips some important steps. Not sure how he did it but there are several things he skips).
GB bootloaders are no longer needed to run ICS but as stated above you may get Rainbows although this seems to have been fixed several versions ago.
Good luck and ask questions if need be but please search first. The ICS guide was on the front page of General.
Thanks everyone.
Woodrube,
Do you think the latest Passion version is still risky (I mean the Rainbows) ?
Thanks,
Woodrube said:
GB bootloaders are no longer needed to run ICS but as stated above you may get Rainbows although this seems to have been fixed several versions ago.
Click to expand...
Click to collapse
GB bootloaders are very recommended. It was found that on mr_psycho's subZero kernel #17 you could not get into recovery at all with Froyo bootloaders but all was fine with GB bootloaders. So sometimes it's not just rainbows.
Vadim1 said:
Thanks everyone.
Woodrube,
Do you think the latest Passion version is still risky (I mean the Rainbows) ?
Thanks,
Click to expand...
Click to collapse
Passion should be fine w/o them (as long as you are using stock kernel or one of the Kissed ones)
bobshute said:
GB bootloaders are very recommended. It was found that on mr_psycho's subZero kernel #17 you could not get into recovery at all with Froyo bootloaders but all was fine with GB bootloaders. So sometimes it's not just rainbows.
Click to expand...
Click to collapse
I agree with Bob, I do recommend having GB bl's but they are not needed on the general ICS builds (for the most part). From what I read in the Zen thread, MP streamlined his kernel and it seems that the recovery broke on Froyos b/c of what he took out but was fine on GB and he recommends most be on GB as well. So the 1 kernel out of all of them broke it for Froyos. I am wondering if MP will fix this for the masses or just keep it as GB exclusive for subZero/Zenwhich?
With that being said, I think that Passion/ Euphoria are good for the general public, while AOKP/ZEN are for more of the advanced users like us. And mostly the ROMs are ROMs. It is the kernels that are being built so fast nowdays. Bootloaders for someone not knowing what they are doing is extremely hazardous and they shouldn't be flashing them unless they know what they are doing.
Woodrube said:
Passion should be fine w/o them (as long as you are using stock kernel or one of the Kissed ones).
Click to expand...
Click to collapse
So, I should not bother installing the bootloader as long as I am using stock kernel? I don't intend making up anything else, just going back to stock 2.1 then moving to ICS Passion. I would prefer not taking useless risks on a phone that I am expecting to last a few more months until I upgrade.
Thanks
Yes you are good (for now), but if you swap kernels, make sure you are reading about them first.
Kiss 2.2 seems to have the best performance with Passion
Woodrube said:
Yes you are good (for now), but if you swap kernels, make sure you are reading about them first.
Kiss 2.2 seems to have the best performance with Passion
Click to expand...
Click to collapse
Sorry to bother you again.
How do you get rid of these "Random offset" errors that prevent from installing the ICS ?
I did try at least ten times and I still did not succeed.
Thanks,
Vadim1 said:
Sorry to bother you again.
How do you get rid of these "Random offset" errors that prevent from installing the ICS ?
I did try at least ten times and I still did not succeed.
Thanks,
Click to expand...
Click to collapse
That's normal. I get it every time I flash an ICS ROM. After it throws that error, don't touch anything. It'll finish installing the ROM on it's own.
dpaul007 said:
That's normal. I get it every time I flash an ICS ROM. After it throws that error, don't touch anything. It'll finish installing the ROM on it's own.
Click to expand...
Click to collapse
Thanks for replying.
Does it install whatever the ICS version is ?
How long does it take ? Hours ?
I had the feeling it gets frozen...
Thanks,
I think you should give Zenwich a try. GPS now works, it is light and based of AOKP too. I have hardly ever encountered the security block.
I know that someone else I was helping kept getting stuck at that point and they just kept flashing it over itself. Sometimes when I get to the point where you are, I would either Odin all the way back and start over or flash CM7 again and let it boot up completely and then try Passion/ Euphoria again. Should push through.
Don't forget to format /system in the appropriate steps too. I have noticed that and not wiping /cache and /dalvik-cache after CM7 boots up causes things to get wonky b/c of ghosts from CM7 apps.
Woodrube said:
Don't forget to format /system in the appropriate steps too. I have noticed that and not wiping /cache and /dalvik-cache after CM7 boots up causes things to get wonky b/c of ghosts from CM7 apps.
Click to expand...
Click to collapse
I no longer remember whether I did wipe/cache and /dalvik cache after I flashed CM7.
Do you think I should do so before retrying to flash ICS ?
Thanks again,
Yes. I actaully forgot to do it once and it made all the difference in the boot up and stability.
Woodrube said:
Yes. I actaully forgot to do it once and it made all the difference in the boot up and stability.
Click to expand...
Click to collapse
Well, still no luck.
Even after wiping cache/delvic and more than one hour waiting for the "Random offset" message to disappear, I can't get past it.
No idea whether it is my device or this Passion 13.1 version.
Which version could I try without taking too many risks (Rainbows) ?
Thanks,
uh oh
i took a fresh vibrant on eclair, rooted, place cwm update.zip, rebooted into cwm recovery, flashed cm7 update kernel, than flashed ics passion 13.1 rc1 build 2. somewhere along the way the phone stopped talking to tmobile but i dont know where. now im left without a backed up efs, my fault i know, and i dont know what to do?
---------- Post added at 05:26 AM ---------- Previous post was at 05:22 AM ----------
Vadim1 said:
I no longer remember whether I did wipe/cache and /dalvik cache after I flashed CM7.
Do you think I should do so before retrying to flash ICS ?
Thanks again,
Click to expand...
Click to collapse
coming from cm7 wipe data, wipe cache partition/dalvik, format system(mouts and storage), than flash ics passion latest edt.
Eventually, I was able to flash ICS Passion.
I simply had to follow all steps mentioned on their thread and it did work OK.
Now, I wish there were secret codes compatible with ICS as I would need to make some changes within the bands.
I read somewhere that old ones would not work (unless used with Samsung firmware).
Anyone know about using secret codes with ICS Passion ?
Thanks,
I couldn't find an answer on the threads. I rooted my at&t last night w entropy512s one click kernel and root. Well I'm new to the phone tech so it took me a while. I now cannot use any of the market Hotspot apps to run my tablet off my s2 wifi. I could before the root and from what I was told it should be easier to do this after rooting. Am I missing something? Is there a special way I have to do it now? I'm so confused.
Sent from a still, small voice with help from my Galaxy s2.
I'm not familiar with those applications. I don't know any reason they would not work. And it's not clear from your post what exactly the problem is. You mean you can't install them, or that they do not produce a wifi signal even though installed?
Anyway, almost all custom roms include portable wi-fi hotspot, as well as usb tethering and sometimes bluetooth tethering. Since you have rooted, why don't you go ahead and pick a custom rom and put that on. Problem solved.
There is a good guide linked in my signature.
Yeah, once you have a custom rom, just use the built-in tethering. Works great for tablets.
Yea I can install them, I've tried a few of them and none put out a wifi signal. I don't know what rom I should flash yet. Since I did the entropy512s one click root+ kernel I understand that the kernel is gingerbread, does that mean I need a gingerbread rom? I was hoping for the latest, greatest build. Any guidance is GREATLY appreciated as it took me hour just to root. Lol
Sent from a still, small voice with help from my Galaxy s2.
nednerbish said:
Yea I can install them, I've tried a few of them and none put out a wifi signal. I don't know what rom I should flash yet. Since I did the entropy512s one click root+ kernel I understand that the kernel is gingerbread, does that mean I need a gingerbread rom? I was hoping for the latest, greatest build. Any guidance is GREATLY appreciated as it took me hour just to root. Lol
Sent from a still, small voice with help from my Galaxy s2.
Click to expand...
Click to collapse
Since you used Entropy512's package to root, you have a stock kernel. In order to install custom firmware, you need to first install a custom kernel that contains ClockworkMod Recovery onto your phone. That kernel must be Gingerbread. However, once you have the kernel and CWM installed, you can then flash any firmware you choose, Gingerbread, ICS or JB.
The guide which is the first link in my signature contains all the info you need.
Fantastic. Thank you so much for your time. I will try first chance I can.
Sent from a still, small voice with help from my Galaxy s2.
I will give you two pieces of advice:
1: Follow the instructions given to you by Creepy (and any instructions in the OP of ROMS) to the T.
2: Read then read some more. When you're done with that, read it all over again. Afterwards, follow step 2 again. This goes for searching about any issue you may come across.
Have fun, this device is really amazing once you figure out more about it
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
I thank you. I will. I'm so confused about this stuff but it seems the more I read I am really UNDERSTANDING what it means. But it takes about 10 read throughs.
Sent from a still, small voice with help from my Galaxy s2.
Ok I was told to get entropys dd kernel since it had cwm with it. I guess thats the next step correct?
Sent from a still, small voice with help from my Galaxy s2.
Use creepy's guide Ned! You need to figure out what your next step is.
Im on the mobile tapatalk (on vacation), So i cant use my computer to reaserch the xda site easily. Im trying to learn as much as possibe before i get home and actually do it.
Sent from a still, small voice with help from my Galaxy s2.
Good plan. When you get the cwm kernel, do a nandroid backup then pick any rom you like... (cm10 nightly just came out, if you like jellybean)
AOKP by Task650 is another JB alternative.
Which is better you ask? Gonna have to try them both! They both offer stability and great user experience for most who try them. Maybe you're a GB or an ICS kinda guy though!
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
It really doesn't matter much which kernel you choose for the next step, because it's only on your phone for a short time. Assuming you rooted with the Gingerbread stock plus root package, then you need a custom Gingerbread kernel which has ClockworkMod Recovery. I believe the links in my guide for the kernels are still working links.
The root I did said it was root + kernel. I take it the one with the entropy512 one click root+ kernel doesnt include the cwm. Im sorry im jist trying to understand the whole process not just do it. Alot of what i read doesnt click. Loke when I rooted it took me 6+ hours because I didnt know you want to save the file not open it when downldng it. also I read the deleting the tethermanager2.apk will open wifi/tether. True?
Sent from a still, small voice with help from my Galaxy s2.
Forget i asked. I re read your comment. Ok its a stock kernel. So it wouldnt. I understand. A stock kernel probably would make it easier to return to stock. right?
Sent from a still, small voice with help from my Galaxy s2.
nednerbish said:
Forget i asked. I re read your comment. Ok its a stock kernel. So it wouldnt. I understand. A stock kernel probably would make it easier to return to stock. right?
Sent from a still, small voice with help from my Galaxy s2.
Click to expand...
Click to collapse
Essentially, yes, but if you're going for custom ROMs, that's not what you want. There are easy ways of getting back to stock if all else fails.
You gotta know what you want first, before you move forward. I know you want tethering to work, and people here have recommended moving to a custom ROM because tethering does not seem to work for you on rooted, stock ROM and stock kernel. So do you want a custom ROM instead (you'll lose some of your current data via that route)? Or do you not care about ROMs and you just want wifi tethering to work now that you're rooted?
Assuming you want just the latter of the two options, I would recommend that you first try a custom kernel (this is different from a custom ROM, but note most custom ROMs include a custom kernel upon install). You mentioned Entropy's Daily Driver Gingerbread kernel, which is a great one. I'd recommend installing it and seeing if that fixes your wifi tethering problem. To install, use Mobile Odin lite version; you can find that apk in Creepy's guide. Download and save the zip from Entropy's DD thread, then extract the zImage file from it (make sure to use the name "zImage", no file extension, important) and move that to your phone via USB mounting. After that, in Mobile Odin lite navigate to the zImage file and flash it; viola, you now have Entropy's custom Gingerbread kernel and stock GB ROM. All custom kernels include ClockworkMod (no other way to get it), so you have that too.
If the custom kernel alone does not fix your wifi tethering problem, then maybe it's time to move to a custom ROM. With CWM, you can flash anything (ROMs, kernels, what have you) much more easily, but we'll get to that after you get the kernel, which is part of the process anyway.
These instructions are all repeated in paragraph 3a of Creepy's guide, and more information is written there, so I would recommend reading it thoroughly so you do understand. I know it's frustrating at first, but you'll get it, and you seem like the type to eventually get it right and understand what you're doing.
THANK YOU!!! I will try that tonight. That was very helpful info. So I CAN do this right from phone the? I saw there were some Apps that can do stuff like that but wasn't sure if they worked. I think I saw one linked to the superuser app. Ill keep you updated
Sent from a still, small voice with help from my Galaxy s2.
I also want a new rom also. I'm just trying to get there. LOL
Sent from a still, small voice with help from my Galaxy s2.
[Chinese accent] Have patience, Grasshopper.
Hello all. I am trying to get jellybean on someones vibrant. Its on froyo and its already rooted. What would be the best way to do this? Do I need a different bootloader? or can I just get clockwork and flash? What is the best way to get clockwork? any help would be very much appreciated. thank you.
I guess from what I've been reading, GB bootloaders are optional. If you decide to go ahead and flash it then follow the guide and you'll be fine. It takes around 10 seconds to flash.
Look in this section for the update.zip file. It will put Clockwork Mod Recovery on your Vibrant. It should be located in Woodrubes Repository, (look for it in the stickies).
Find a JB ROM you want to try. I have used Helly Bean and Paranoid Android. I like them both. PA has a lot more options if you're into that kind of thing.
Each ROM has its own set of instructions, so read them. Don't take this the wrong way, but the fact that you created this thread tells me you haven't done your research. So, before you go and brick your device, do some reading up. There are really great guides and other reading material in the stickies and all over really.
As always, if you need help... hit us up. We're always around.
You were just sliced bread before you were burnt by the toaster.
One more thing, go back to stock 2.1 using Odin, then root, get cwm recovery, then flash a new ROM.
No tickee, no laundry!
cm7
When the jb Roms first started to release most of them suggested to flash cm7 first to setup the system for install of jb Rom
I recently picked up a GP 4.2. I immediately got it rooted so now I'm running a 2.3.6 stock rom with root. What's the next step in terms of getting a recovery installed and maybe moving up to an ICS or JB rom? I've kind of poked around a bit but it's some what confusing with all the other types of GPs in the same area. Does anybody have a recovery and rom they'd recommend? Is using rom manager to push CWM feasible?
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
NapalmDawn said:
Thank you for the info Meta. I'm somewhere around the mid-high mid level with flashing and rooting but slogging through trying to find the right info for a GP 4.2 was getting a bit hectic. I think part of it was the way some people abbreviate the model compared to others. I just wanted to make sure I didn't brick the device.
I got it mainly for a perm, in-car music and GPS/navigation provider instead of always looking to my phone to do it. One thing I noticed about the rom, it mentions installing it via CWM. If I don't have CWM yet, can this rom get pushed by odin or do I have to get CWM first and then flash the rom?
Click to expand...
Click to collapse
you should flash CWM via odin first and then flash the ROM via CWM
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
MetaMav said:
I would recommend the ChaOS ROM/Kernel which includes CWM. It is one of the few available ROMs for this device right now but offers a lot of great features. You can also install an S3 or Jelly Bean theme with the ChaOS ROM. Here's the link to the ROM: http://forum.xda-developers.com/showthread.php?t=2279806. I do not believe using ROM manager to push CWM is feasible on this device. Also, CM7 will most likely make it on to this device very soon. I would recommend watching for that in the near future. I know it can be a hassle trying to weed through the Galaxy Player forums to find 4.2 information but it's all we've got. Hope this helps and welcome to the SGP 4.2 community!
Click to expand...
Click to collapse
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
NapalmDawn said:
Would the instructions here be the right thing to do?
http://www.youtube.com/watch?v=-MbHDbjph8A
Click to expand...
Click to collapse
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
Xenphor said:
Do you know if CM will come to the 3.6 as well? And from what I understand, to get CWM on the 3.6 you have to flash a custom kernel?
Click to expand...
Click to collapse
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
MetaMav said:
Yes. Those instructions are correct. However, you do not need to run the adb dev tool like the person does in the beginning of video in order to boot into download mode. You can just hold the power, home, and down-volume button to boot the phone into download mode before using Odin. Zaclimon's CWM kernel can be found here (along with the wifi fix): http://forum.xda-developers.com/showthread.php?t=2198444 and installed with the instructions in the youtube video.
From what I have read I know that SerkTheTurk is currently compiling CM for the 4.2. I would imagine either him or some other 3.6 dev will take up the task of CM for your device. And, the answer to your second question is yes, you do have to flash a custom kernel similar to how the 4.2 requires a custom kernel.
Hope that helps.
Click to expand...
Click to collapse
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Xenphor said:
Ok thanks. I also have a question regarding flashing kernels. In the linux world (and other os world), randomly changing your kernel is a big no no that would lead to major compatibility issues. I don't understand how people can mix and match kernels, roms, firmware, bootloaders, recoveries and everything else? There won't be conflicts?
Regarding the kernel available for the 3.6: what do I do if I encounter stability issues with it and, say, the upcoming CM7? I wouldn't be able to go back to my original kernel because I didn't have CWM to back it up in the first place. Won't I be stuck with a potentially faulty kernel?
Click to expand...
Click to collapse
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
NapalmDawn said:
In changing kernels in the android world, you have mixed results. There are times a kernel can cause some issues but for the most part (we're talking like 98%), if an XDA dev posts a kernel and lets you know you can use it, you can trust it. These devs no matter the device spend painstaking hours ironing things out. Also, many of them have a select group of people testing the kernel for faults and issues. In a very active community, if a well known dev posts a kernel, you can trust it. HOWEVER...no matter what we think or believe or what we're told, every device is a unique and beautiful snowflake. Back up back up back up BACK UP BACK UP BACK UP your stuff. If you want to be super ULTRA safe, take the back up and download it to your PC or somewhere safe.
Click to expand...
Click to collapse
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
Just flash the cwm kernel because its basically the stock kernel but with cwm, and it shouldnt brick but if it does you can flash the stock kernel back again
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Where could I find a stock kernel?
Xenphor said:
Where could I find a stock kernel?
Click to expand...
Click to collapse
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
SerkTheTurk said:
US version: http://forum.xda-developers.com/showthread.php?t=1885374
International: http://forum.xda-developers.com/showthread.php?t=1884071
Sent from my YP-GI1 using Tapatalk 2
Click to expand...
Click to collapse
Ok thank you. However, will this work with YP-GS1?
But about kernels, on the webpage where I downloaded the stock rooted rom http://tau.shadowchild.nl/attn1/?p=166 it says specifically that the Wifi module in system and kernel must MATCH. This is what I'm talking about in regards to kernel compatibility with roms. How do I know if a kernel I'm downloading will have changes applied to it that will work with another rom like with this stock rom/kernel?
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Well I had to flash this kernel http://forum.xda-developers.com/showthread.php?t=2198234 to get CWM on mine. I haven't actually flashed anything with CWM because there doesn't seem to be any good roms for the 3.6 unless CM7 comes out sometime. I used Odin to flash a stock rom from here http://tau.shadowchild.nl/attn1/?p=166
NapalmDawn said:
Well in order-I used odin to flash CWM. Once it rebooted, I saw the Galaxy SII boot anim. Used Rom Manager to have it boot to CWM. From there I flashed wifi fix, the rom and then the mod pack. My build number is gingerbread-ueld3. From what I can tell, I think I'm all done. At first I was like hrmmmmm. Doesn't look much different. When I hit the toggle bar though, I could tell it had changed. The process was all very simple after I got headed in the right direction with CWM. That was my only confusing start point for this.
Edit-my bad. The rom didn't take on the first flash. I could tell by the build number. Reflashing the rom and the s3 addons. Hrmmm. Might be boot looping. It's going through the comet and coming up to the white samsung, vibrates a few times after a bit and goes back to the comet with no sound.
Click to expand...
Click to collapse
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
NapalmDawn said:
Poop. I think I bootloped the sucker. I can use Odin to reflash the stock, rooted rom just like I did when I got it first rooted right? Do we have another rom for the 4.2 I could try flashing? Not sure why it has bootlooped. I even went back into CWM, did a factory reset, flashed only the rom (no addons) and same thing. Possible bad download? It is flashing from the internal SD as my CWM is not seeing my external SD.
Click to expand...
Click to collapse
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
Xenphor said:
Well that's my dilemma because in order to backup my kernel I first need to flash the custom kernel to get CWM. What do I do?
Click to expand...
Click to collapse
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
MetaMav said:
I have been meaning to post this on the dev thread for awhile. I thought this problem might only be for certain people but I think it applies to US and maybe non-EU devices. I believe that the ChaOS ROM will bootloop on US (YP-GI1/XAA) devices if you do not install ChaOS's Enhanced Stock ROM (http://forum.xda-developers.com/showthread.php?t=2279450) for whatever reason. I spent days trying to install his ROM and bootlooping.
The way I successfully installed (if I remember correctly):
-Do a factory reset of rooted stock ROM
-Boot to CWM (meaning you have already flashed the custom kernel) and install ChaOS's Enhanced Stock (put all install files on internal SD)
-Boot to CWM, wipe davlick cache under "advanced", wipe cache partition, and install the ChaOS ROM
-Wait a little while and your device should boot up properly
I hope this works for you. If it doesn't let me know and I can help you further. If this does work for you too then I will post this on the ROM's thread for other users.
SerkTheTurk said it very well, you do not need to worry, but if you also want to do a backup before you install the custom kernel you could use the adb tools on the computer to backup the device. I'm sure you could learn how to do that with a quick Google search.
Click to expand...
Click to collapse
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Xenphor said:
ell there's not really much point in backing up the kernel when I've already downloaded it on my computer.
I've since flashed KingOS rom and don't really notice any differences at besides a few color changes... what's all the hype about?
Click to expand...
Click to collapse
Xen-it seems GPlayer development is still fairly newish. the work you see from devs now are all ground work. For the 4.2 and 3.6, they seem a little less dev populated than the 4 and 5. People will build upon the work of early devs and eventually get kernels that can OC and maybe ICS and JB roms. At this stage, we likely won't see anything like ZOMG earth shattering until people spend time with the devices. Seems Serk is on his way to doing the best he can for 4.2 but I am not sure who is tackling 3.6
It's weird how roms for devices go. I learned this when I had a tbolt and shockingly saw a FUNCTIONAL JB rom for my old Eris while the tbolt was still hanging back in ginger land with not even a really good ICS rom let alone JB. I asked the Tbolt community-why? How is it the dinosaur Eris has JB and not us? It all depends on what the devs can do with the sources provided. Sometimes certain hardware points are sticky. you can have beautiful JB rom for a device that can't talk to the camera if the hardware source isn't made available (reference the HP TP for many years)
For now, flash what you're comfortable with and and learn what you do and don't like. Also learn if you want to play things safe and not experiment or take on potentially beta builds. For the tbolt, tackling an ICS rom was too dicey so I never did. On my new Rezound, I eat up JB roms as they are in much better shape