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,
So I've never flashed this device before, and I got it today but I'd like a custom ROM flashed to it.
Could someone point me to the following:
-A working ODIN link for this device
-A custom ROM (GB) that has all working features (camera, etc) and is built for the INTL 5.0 version (I've been looking at this: http://forum.xda-developers.com/showthread.php?t=1465144)
-A guide for getting CWM recovery.
Cheers.
This thread has all the info you are looking for.
http://forum.xda-developers.com/showthread.php?t=1720457
I personally have used the Eryigit rom you linked and it works fine.
Have fun.
I would stay away from Cyanogen and its variations right now if you want everything to work. CM7 has issues with wifi (and other stuff) and CM9 has no HW Acceleration -kernel issues.
Pretty much any rom based on stock is a safe bet.
rjwil1086 said:
I would stay away from Cyanogen and its variations right now if you want everything to work. CM7 has issues with wifi (and other stuff) and CM9 has no HW Acceleration -kernel issues.
Pretty much any rom based on stock is a safe bet.
Click to expand...
Click to collapse
Thanks, but still, how do I get CWM recovery? I couldn't see much in the above thread.
abtekk said:
Thanks, but still, how do I get CWM recovery? I couldn't see much in the above thread.
Click to expand...
Click to collapse
Check in the custom kernel section and download the kernel according to your device.
Look in the thread cvcduty posted in the custom kernel section. The kernels have CWM packaged with them. You'll need Odin to flash them. If you search the forums you'll probably find a link for Odin... or google it
Make sure you use the rigth kernel for your specific device. The 5" and 4" are different and there are two versions of the 5". Not sure if there is more than one version of the 4" or not.
rjwil1086 said:
Look in the thread cvcduty posted in the custom kernel section. The kernels have CWM packaged with them. You'll need Odin to flash them. If you search the forums you'll probably find a link for Odin... or google it
Make sure you use the rigth kernel for your specific device. The 5" and 4" are different and there are two versions of the 5". Not sure if there is more than one version of the 4" or not.
Click to expand...
Click to collapse
Thanks mate, that's what I wasn't sure about. If I happen to flash the wrong kernel I can overwrite it with the correct one as usual, correct? and it's Odin3 v1.3 I need, isn't it?
All sounds right to me. Even with a bad kernel you'll have download mode to fall back on.
rjwil1086 said:
All sounds right to me. Even with a bad kernel you'll have download mode to fall back on.
Click to expand...
Click to collapse
Thanks, just flashed it and got a boot loop.
Edit: Could be because I flashed a GB kernel while still on froyo, I best revert to stock kernel and do a KIES update first
Edit2: Tried to go stock but still a boot loop -_-
This has gone, extremely well...
/sarcasm
I just downloaded Odin 1.3 and flashed Entrophy's DD as we discussed. No issues on my device - as i anticipated because this is how I did mine initially. Which model do you have? Another question, did you try to boot into CWM after you flashed the kernel (VolUp + Power). If you can get into CWM then your good to flash whatever ROM you want, even if the Stock ROM is boot-looping.
rjwil1086 said:
I just downloaded Odin 1.3 and flashed Entrophy's DD as we discussed. No issues on my device - as i anticipated because this is how I did mine initially. Which model do you have? Another question, did you try to boot into CWM after you flashed the kernel (VolUp + Power). If you can get into CWM then your good to flash whatever ROM you want, even if the Stock ROM is boot-looping.
Click to expand...
Click to collapse
Sorted, thank you for your help and clearing things up for me.
rjwil1086 said:
I would stay away from Cyanogen and its variations right now if you want everything to work. CM7 has issues with wifi (and other stuff) and CM9 has no HW Acceleration -kernel issues.
Pretty much any rom based on stock is a safe bet.
Click to expand...
Click to collapse
i went to look and i think im blind but which are based on the stock rom? and which is the best ?
harts830 said:
i went to look and i think im blind but which are based on the stock rom? and which is the best ?
Click to expand...
Click to collapse
I just installed this:
http://forum.xda-developers.com/showthread.php?t=1579774
It's a rooted stock GB ROM with a custom kernel. Supports both USA and International devices.
http://forum.xda-developers.com/showthread.php?t=1720457
Check out this thread again. It has most of the ROMs listed as "Stock Based" or "CM Based". I'm running GB.XXKPH.WT-0.4.0 for Galaxy Player 5.0 Intl & US and it seems to be a good one. Several people like Eryigit-GB-2.3.
On another note, I'm actually trying to continue ambrice's development on CM7 but can't get my build to boot.
I still run a stock ice cream, I'm officially going to root it and put a custom fw on it. It would be a miracle at this point if they updated it.
What is the closest to the s3 rom? I'm guessing its shostock3? I really want a stock rom, with all the samsung apps. I know people ask all the time what the best rom is etc etc, but is my assumption correct here? i777 here.
my only fear is that shostock will be worse on battery life than an official one, but at the same time, that could be a false notion with me.
Thank you for any input.
justanother1020 said:
I still run a stock ice cream, I'm officially going to root it and put a custom fw on it. It would be a miracle at this point if they updated it.
What is the closest to the s3 rom? I'm guessing its shostock3? I really want a stock rom, with all the samsung apps. I know people ask all the time what the best rom is etc etc, but is my assumption correct here? i777 here.
my only fear is that shostock will be worse on battery life than an official one, but at the same time, that could be a false notion with me.
Thank you for any input.
Click to expand...
Click to collapse
With any custom ROM you should get better battery life as opposed to the stock ICS ROM, as there are kernel bugs that drains battery at a faster than normal pace.
There is also an issue with the stock kernel that can permanently brick your phone (do NOT perform a factory reset or wipe of any sort unless/until you have replaced that kernel!!)
SHOstock3 can get awesome battery life.
so is shostock3 the only rom that gives me jelly bean + touchwiz 5 ? and the samsung apps ? I saw the music player is the same as the s3 etc??
Thank you
justanother1020 said:
so is shostock3 the only rom that gives me jelly bean + touchwiz 5 ? and the samsung apps ? I saw the music player is the same as the s3 etc??
Thank you
Click to expand...
Click to collapse
Look in the development section for others but shostock3 is one of the most solid ones. Flash it and try it for yourself.
Sent from my CLEAN Note ll
so is there any other rom that give you a more stock s3 experience other than shostock?
Thank you
justanother1020 said:
so is there any other rom that give you a more stock s3 experience other than shostock?
Thank you
Click to expand...
Click to collapse
Here's my suggestion: make a nandroid backup, flash SHOstock3 and see whether you like it or not.
I installed Fromaroot and rooted the phone. I'm trying to get CWM on there now.
I was trying to do it without odin and without using a computer much. Did I mess up the process doing the fromaroot, it did succeed. All I have now is the android recovery(which i'm guessing isn't much help?).
I'm trying to install shostock, but it looks like i already need a kernel that has CWM already on the phone before I install that? I don't want stuff that is already iterated to me repeated, and have the thread locked.
But can I use mobile odin pro to install a kernel with CWM? or should I really be using the computer right now to do all of this?
Thank you
justanother1020 said:
I installed Fromaroot and rooted the phone. I'm trying to get CWM on there now.
I was trying to do it without odin and without using a computer much. Did I mess up the process doing the fromaroot, it did succeed. All I have now is the android recovery(which i'm guessing isn't much help?).
I'm trying to install shostock, but it looks like i already need a kernel that has CWM already on the phone before I install that? I don't want stuff that is already iterated to me repeated, and have the thread locked.
But can I use mobile odin pro to install a kernel with CWM? or should I really be using the computer right now to do all of this?
Thank you
Click to expand...
Click to collapse
Assuming the root process worked correctly, then you *can* use Mobile Odin (pro or lite) to install a custom kernel containing ClockworkMod Recovery. For more detailed information, please see the guides linked in my signature.
even though it says I already need a kernel that has CWM to install shostock on the official page?
sorta came off as most people will have already been flashed etc.
the last thing i want to do is brick my phone on the first attempt. Also what kernel should I flash, there is so much outdated info out there. I dont see anyone on here mention fromaroot but it worked perfectly, maybe it's a bit of a newer tool.
justanother1020 said:
even though it says I already need a kernel that has CWM to install shostock on the official page?
sorta came off as most people will have already been flashed etc.
the last thing i want to do is brick my phone on the first attempt. Also what kernel should I flash, there is so much outdated info out there. I dont see anyone on here mention fromaroot but it worked perfectly, maybe it's a bit of a newer tool.
Click to expand...
Click to collapse
Read the 1st link from creepyncrawly's signature to get started.
Simple rule to follow. Look what version of Android your phone is running now, and then read the related posts for flashing kernel, ROM, CWM, etc. That's how I did it. This phone is almost 2 years old and of course outdated info is floating around.
For me, it took less than an hour to root/flash the phone, but days to read through all related posts.
justanother1020 said:
even though it says I already need a kernel that has CWM to install shostock on the official page?
Click to expand...
Click to collapse
I'm not sure what you're getting at here.
You started out with stock 4.0.3 (or 4.0.4.) Your stock kernel contains stock 3e recovery, which you can not use to flash custom firmware. So, to put custom firmware on the phone, you need to first flash a kernel containing CWM Recovery. (There is no stand alone recovery on this phone. The recovery is built right into the kernel.) You can do that by several methods. Using Mobile Odin is the quickest and easiest. It's almost fool proof.
And yes, the phone is starting to show it's age, and the guides are getting a little out dated. But the information is still good. What is important is understanding the process. You (and everyone) should understand exactly what you are doing before you modify your phone. Once you understand the process, you are much less likely to make a paper weight.
For a custom kernel, use one of the ones linked in the OP of the thread for 4.0.4 ICS, UCLL6 plus root which is also linked in my signature.
sorta came off as most people will have already been flashed etc.
the last thing i want to do is brick my phone on the first attempt. Also what kernel should I flash, there is so much outdated info out there. I dont see anyone on here mention fromaroot but it worked perfectly, maybe it's a bit of a newer tool.
Click to expand...
Click to collapse
Just to recap, to go from stock to custom firmware
1. root
2. install a custom kernel containing CWM recovery. It should be a recovery that works with your current system.
3. use CWM recovery to flash the firmware of your choice.
4. profit
Thanks guys,
I've actually flashed a few phones for my friends, read up and 20 mins later i was off an on.
This was a bit more of a trouble for me though. Tons of ways to do it, many versions of this phone, half the time i would be reading and be like, damn this is not for the i777 can't take any chances.
i'm going to put that kernel on there , and then flash shostock3 , seems to be the closest thing to an s3 like experience on this phone.
I was / still am, heavily worried about battery life, something keeps telling me this is like going to cut my battery in half, i blame the experience on the t mobile g1, where i put all these roms on my friends phone and it just sucked away the battery.
Hopefully shostock3 does a good job though! ICS just isn't cutting it anymore
justanother1020 said:
...I was / still am, heavily worried about battery life, something keeps telling me this is like going to cut my battery in half, i blame the experience on the t mobile g1, where i put all these roms on my friends phone and it just sucked away the battery.
Hopefully shostock3 does a good job though! ICS just isn't cutting it anymore
Click to expand...
Click to collapse
Not to worry! See attachment.
Admittedly, this was very light usage. But it gives you an idea what is possible.
Oh, and this is the stock battery that came with the phone in Oct. 2011. No telling how many charge cycles on it. At least 4-500.
got shostock3 on it, runs beautifully
battery life so far is just as good or even better than stock, lots of bloatware gone.
Thank you to everyone.
Fromaroot > 4.0.4 custom kernel (mobile odin) > shostock did the trick, couldn't be easier, if you ever really motivated and didn't mind waiting a bit, i guess you could do that whole process with just the phone.
only thing i used the computer for was transferring files.
and now 4 days later the official one comes out!
Everyone lost hope, even me!
I'm tempted to try it out, but at the same time, i'm quite happy with shostock3
justanother1020 said:
I'm tempted to try it out, but at the same time, i'm quite happy with shostock3
Click to expand...
Click to collapse
mr-cook has a modified stock version. It's stock system plus root and busybox, and the jebo kernel. So if you wanted to try it out, you could make a nandroid backup of SHOstock3, try out the cooked rom, and if you don't like it, go back real easy.
Stock s3 experience
justanother1020 said:
so is there any other rom that give you a more stock s3 experience other than shostock?
Thank you
Click to expand...
Click to collapse
Try the Alliance Rom, it has the Samsung app store and you register with Samsung when you first boot up.
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
I Get a notification about the update to version 4.4 BETA 1 of Paranoid Android rom, after downloaded, i flash it via CWM normaly, then flash gapps, but when the phone reboot it stucked at the Galaxy S2 boot logo, and it can boot into recovery, only download mode, but when i open odin to flash CWM but odin can't access the phone and i can't flash, i tried to install usb driver but not success, so what can i do now, please help!
Sorry for my bad English
1) Your English is better than a lot of native English speakers I know.
2) Hopper8's 'Odin troubleshooting' thread stickied in General has all the info you need to get a successful Odin flash. Find the thread, try as many of the troubleshooting steps as many times as you need to in order to get a successful flash.
However, don't try one or two things from the thread, come back here & say 'But I tried some of the stuff in the thread & it didn't work. That thread covers this issue from every possible angle, and it's often persistence that fixes these. There's no easy fix in this situation because we're not there looking over your shoulder seeing what you're doing/not doing, and there's nothing which isn't in the thread that can be suggested in this situation.
So...I've (and Hopper has) given you the tools to get your phone fixed, up to you to fix it now.
@nguyenducanh did you manage to fix this?
I have been speaking with the dev (ayysir) of ParanoidAndroid, 4.4beta1 for S2 had a bug with the kernel. The ROM wouldn't boot at all with the stock kernel, but would with any compatible custom kernel (Dorimanx, Gustavo, Apolo -correct versions of these).
The dev has uploaded a new build now which fixes the problem, so if you've managed to recover your phone the new build is safe to use (tested by me)
Hopper8 said:
@nguyenducanh did you manage to fix this?
I have been speaking with the dev (ayysir) of ParanoidAndroid, 4.4beta1 for S2 had a bug with the kernel. The ROM wouldn't boot at all with the stock kernel, but would with any compatible custom kernel (Dorimanx, Gustavo, Apolo -correct versions of these).
The dev has uploaded a new build now which fixes the problem, so if you've managed to recover your phone the new build is safe to use (tested by me)
Click to expand...
Click to collapse
Ok, tks u, i fixed my phone via odin, and i'm using c-rom v6.6, i will try newest pa now because i'm a big fan of pa
nguyenducanh said:
Ok, tks u, i fixed my phone via odin, and i'm using c-rom v6.6, i will try newest pa now because i'm a big fan of pa
Click to expand...
Click to collapse
Good job, I like to hear that someone recovered their phone using that guide and odin :good: make sure you re-download the ROM, you need the build on 0605, not 0604. 0604 is busted, but 0605 is good
Hopper8 said:
Good job, I like to hear that someone recovered their phone using that guide and odin :good: make sure you re-download the ROM, you need the build on 0605, not 0604. 0604 is busted, but 0605 is good
Click to expand...
Click to collapse
Ok, using 0605 now, and missing see through option
nguyenducanh said:
Ok, using 0605 now, and missing see through option
Click to expand...
Click to collapse
That's because of the new theme engine... I saw something on google+ about that. I think it's planned to be re-implemented but may take a while due to complexity..
Hopper8 said:
That's because of the new theme engine... I saw something on google+ about that. I think it's planned to be re-implemented but may take a while due to complexity..
Click to expand...
Click to collapse
I hope "see through" will come back in the next update