Hi, I successfully flashed my T-mobile Vibrant about twelve months ago to a custom 2.2 Froyo rom (Trigger 3.2 Final). It's a great rom and EVERYTHING works. However lately I've read rave things said about newer roms such as ICS passion. It's been a while and I'm still a noobie at this so my question is:
What is the easiest way to get to ICS passion from my current custom Froyo rom ? Thanks ~ Chris
hi,
Its very easy to get ICS running on your vibe. There may be various ways to proceed. I ll give you what I did (AFTER failing for 5-6 times )
Odin back to stock (It may be not necessary. But I started from the beginning which is better AFAIK )
Then stored ICS ROM (ICZen which in my case) and update.zip (CWM) on internal SD
then flashed GB Bootloaders (It also may/ may not necessary. But I did it b/c I already had many failed attempts)
Then flashed CM7 first
After that flashed ICS on top of it
Worked at last for me
NOTE: Please read relevant instructions provided by ROMs b/c flashing one may differ from flashing another.
You can find more information if you run into problems in my thread [SOLVED]Cannot install ICS ROM--please HELP
link: http://forum.xda-developers.com/showthread.php?t=1752937
tc
Happy Flashing
You may just want to read this before flashing ICS. http://forum.xda-developers.com/showthread.php?t=1580902
Sent from my SGH-T959 using Tapatalk 2
^^^ Truth
And I would suggest staying away from Passion. It is based on 4.0.3 and there was a pretty significant code upgread when ICS went to 4.0.4.
IIRC, Passion is the last ROM that still uses 4.0.3 and is probably why it is dead now (but for some reason lives in infamy on YouTube and Google Search).
Haarsh's way works just fine but here is another method as another option too.
Thanks
Thanks for the replies. This is why I subscribed to the forum.
mmm... I see a few pitfalls ahead.
Background info from me is that I can't use Odin on my Linux computer. Never really got into Heimdall. I flashed my first rom by downloading the rom zip file and put it on my phone's internal sd card then let clockwork do the rest, ie nandroid backup and flash the rom from the update zip. I'd like to do the same again.
Ok, it's my understanding that anything above 2.2 needs the GB bootloader so the first step is to install that over my Trigger rom. I think Trigger would still run with the GB bootloader at that stage. Next download an update zip of a rom of my choice, put it on my phone's sd, then flash it with Clockwork.
Seems to me that should work or am I missing something I wonder ?
You can flash the GB bootloader. Its backward compatible so it will work with any ROM currently available.
Download the .zip of the ROM you want, and any Gapps if applicable. Then just follow the instructions on page 1 of the ROM (OP).
The usual would be Wipe Data/Factory Reset, Clear Cache, Clear Dalvik. Flash ROM, flash Gapps, restart. The instructions will tell you all you need to know.
If something goes wrong, give us a shout. That's what we're here for.
help me plz
hi mate i know this is quite outdated maybe but im searching for Samsung T959 stock rom Froyo 2.2 that i search everywhere but didnt find. Can you help me for any link ?
or please suggest me someone.
Thanks in advance.
castan said:
Hi, I successfully flashed my T-mobile Vibrant about twelve months ago to a custom 2.2 Froyo rom (Trigger 3.2 Final). It's a great rom and EVERYTHING works. However lately I've read rave things said about newer roms such as ICS passion. It's been a while and I'm still a noobie at this so my question is:
What is the easiest way to get to ICS passion from my current custom Froyo rom ? Thanks ~ Chris
Click to expand...
Click to collapse
Related
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,
Hey I luckily got my hands on 9100 and not the 9100g. As there are too many roms I got confused on which one to flash. I downloaded miui ics version and flashed it via CWM it got stuck on boot logo. I had a nandroid so I just restored it back
The phone is on 2.3.6 so can I directly flash ics roms via CWM? It's rooted. I like cyanogen but I have heard its got bad camera app. Can someone guide me to the best roms and also to some must have apps for a rooted phone. SGS2 is my first REAL android experience.
And also the phone runs real hot.
PS : I have used search button.
Hang on to your stock for a week, then Westcrips 1.2 (4.04) gets released.. use the time in between talking on your stock phone, and reading up the 1900 pages on that rom
There is no perfect or right ROM.you have to test what fits you best.
Try different ROMs and kernels and you will find your personal perfect ROM.
I tried many different GB and ics roms and my personal favourite is Turkbey ROM v37 SE.
Very stable, fast and awesome looking
zarz123 said:
Hey I luckily got my hands on 9100 and not the 9100g. As there are too many roms I got confused on which one to flash. I downloaded miui ics version and flashed it via CWM it got stuck on boot logo. I had a nandroid so I just restored it back
The phone is on 2.3.6 so can I directly flash ics roms via CWM? It's rooted. I like cyanogen but I have heard its got bad camera app. Can someone guide me to the best roms and also to some must have apps for a rooted phone. SGS2 is my first REAL android experience.
And also the phone runs real hot.
PS : I have used search button.
Click to expand...
Click to collapse
So, using that search button, you must have found the dozens of posts saying that going from GB to ICS ROMs, if you're stuck in boot logo or boot looping, then to try a full wipe, right???
Maybe not.
zarz123 said:
Hey I luckily got my hands on 9100 and not the 9100g. As there are too many roms I got confused on which one to flash. I downloaded miui ics version and flashed it via CWM it got stuck on boot logo. I had a nandroid so I just restored it back
The phone is on 2.3.6 so can I directly flash ics roms via CWM? It's rooted. I like cyanogen but I have heard its got bad camera app. Can someone guide me to the best roms and also to some must have apps for a rooted phone. SGS2 is my first REAL android experience.
And also the phone runs real hot.
PS : I have used search button.
Click to expand...
Click to collapse
I would say go Cynaogenmod their ics rom is running very stable, but it is a matter of personal taste, but as a first time custom rom i would stick with Cynagonmod. You can find the latest release here. As for flashing roms while on 2.3.6 will be fine, just make sure you do a nandroid backup and do a data wipe, cashe wipe befeor flashing as this will cause bootloop.
I can recommend hydrogen-ics with latest siyah kernel because it is my current setup
If you are new to rooting and flashing roms then i would recomend get more experience before flashing a custom kernel. Although i do use siyah kernel and it's wicked, so if you do venture into kernels as well i would recomend Siyah kernel the same as gent.xda
stay on ur stock rom ,untill u kno ur phone well an read xda too,an abt roms there is no perfect rom (define perfect)i don think anything is perfect///////well as for roms spikes,omega,ics remix,hydrogen are good ,cm9 is always updating but if ur a teck geek miui ,cm9 is it...........cheeeerz
This GalaxyMOD looks good: http://forum.xda-developers.com/showthread.php?t=1482372 and it's your neighbor from Mumbai.
There is no best ROM it's like everything in life depends on the needs...
Read / backup / Flash and return to back up if needed
Since this is a discussion and not "plz can i haz the best ROM"
Post what rom you're on and the reason for it!
Thread closed.
Hey all. Quick question for ya. I am going to flash one of the JB roms to my wifes galaxy tab 10.1 this weekend.
She is currently running task's honeycomb rom. She has been running that for a good 5 months now.
What order do I proceed to get her to JB??
Must I flash an ICS rom first then flash a JB rom??
Do I need to flash a JB bootloader or an ICS bootloader?? If so where can I find them. Been searching the forum with no luck.
Any other info would be greatly appreciated. Specifically the orders or anything I have overlooked.
Thanks in advance,
Nycorduroy
not mandatory to have an ICS step, you can directly go to JB.
you just need CWM, you probably already have it if you are running task's rom.
backup your app (titanium is a great tool in my opinion)
copy rom file to your tab
make a full wipe (+cache +davilk)
flash rom
reboot and enjoy
nycorduroy said:
Hey all. Quick question for ya. I am going to flash one of the JB roms to my wifes galaxy tab 10.1 this weekend.
She is currently running task's honeycomb rom. She has been running that for a good 5 months now.
What order do I proceed to get her to JB??
Must I flash an ICS rom first then flash a JB rom??
Do I need to flash a JB bootloader or an ICS bootloader?? If so where can I find them. Been searching the forum with no luck.
Any other info would be greatly appreciated. Specifically the orders or anything I have overlooked.
Thanks in advance,
Nycorduroy
Click to expand...
Click to collapse
This does not belong in the Development section. All questions need to be put into the Q&A section. Please do that from now on.
With that said, I am not sure about the bootloader but you probably need to update your version of CWM recovery, and you can find out about that as well as the bootloader stuff in the threads for CM10/JB. Pershoot's threads are probably a good place to look as well.
Edit: well someone got to it first, follow their instructions as well
nycorduroy said:
Must I flash an ICS rom first then flash a JB rom??
Click to expand...
Click to collapse
Yes, Pershoot stated in Android 4.1.1 - CyanogenMod 10 Preview thread that you need to have a US HC or ICS bootloader in order not to have charging SODs. If you have a US bootloader you should be fine if not flash a stock US HC or ICS rom via Odin before you flash CM10 (you'll loose all data on the tab). Alternatively there are flashable US bootloaders but I've never tried one. I can't put the links because search feature is is temporarily unavailable.
Finally, You could still get charging sods and some wifi problems etc. even if you came from a US bootloader. Pershoot says a small minority will face these issues no matter what. A hard reset fixes these issues temporarily. If you could wait a little bit more a new cm10 is on the way with 3.1 kernel which is supposed to work fully functional. But still, I think current CM10 is the best rom available right now.
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