Ok so I really hope I am posting logically here.....
I have searched Hi and low for a solution to for sure working way to do this....
I am currently using the Avatar Rom Nightly Build 3.1 for I9100.
Other Specs:
Android Version 4.2.2
Baseband Version I9100MUGLD3
Kernel Version 3.0.64-CM-gac24beb
[email protected] # 2
CPU ARMv7 Processor Rev 1 (V71)
Build Number cm-i9100-userdebug 4.2.2 JDQ39E 502 dev-keys
I want to change my boot-logo... (NOT my boot animation) I want to do so in a way that I will not brick my phone (obvs) Everything I have seen was saying not to do unless you do not care about your phone, or it was very unclear if it would work for my version....
I did look in to the boot logo changer app in play store but it said i did not have the correct Kernel..... Can I change the kernel without messing up my avatar rom? (I don't Think So)
Any information regarding how i can change my boot logo would be awesome... I want to change the one that says samsung galaxy SII gt-i9100 right before the boot animation (in my case avatar rom animation)
Change to dorimanx 9.xx kernel and try. Changing kernel wont mess up your rom unless you flash the wrong type of kernel.
andrewwright said:
Change to dorimanx 9.xx kernel and try. Changing kernel wont mess up your rom unless you flash the wrong type of kernel.
Click to expand...
Click to collapse
Do you know where I can find this? Also is flashing a kernel same procedure as flashing a ROM? PDA through Odin then cwm install from zip?
Google dorimanx its so easy mate. And yes flash zip through cwm or tar through odin. Dont bother using odin unless you have to.
And if I flash the kernel it won't mess with my aviator ROM functions at all. I've read up that kernels basically distribute resources so my fear is that if I change it, that it will change resource paths making things like the theme packages, boot animation etc stop working...
No it wont stop them working. Wouldn't say try it if its going to mess things up. Just look out for sods with dorimanx. "Sleep of death" if you dont like it reflash rom with no wipe and stock kernel will be restored :thumbup: if it dont boot after flash wipe cache and dalvki cache then reboot. If it still dont boot then factory reset. Shouldn't come to having to do a factory reset though. :thumbup:
Ok thank you, Just worked a 13 hour night shift. Will be home to give this a shot in a couple minutes though.... Will post results shortly
Ok so the app I wanted to use is SGS2 BootScreen Changer By Hellcat.
I downloaded the dorimanx Kernel.. It installed no problems yet (Knocking on wood... I dont like the sound of SOD) So far it did not alter the phone much... Phone seems to run A LOT Slower now....
Also the SGS2 BootScreen Changer app is still saying....
"The kernel you are currently running is missing the filesystem driver required to access the flash partition containing the bootscreen image(s)!
Due to this, this app can not work while running on this kernel.
Possible solutions to this situation are being worked on."
Whats the app called? Slower? Let it settle down. Phone and kernel will be talking to each other so give it some time to make a judgment on that. Shame the app still dont work:thumbdown: il have a look and see what I can find out and report bk to you mate. :thumbup:
andrewwright said:
Whats the app called? Slower? Let it settle down. Phone and kernel will be talking to each other so give it some time to make a judgment on that. Shame the app still dont work:thumbdown: il have a look and see what I can find out and report bk to you mate. :thumbup:
Click to expand...
Click to collapse
Ok. I have only used avatar rom.... I am fresh blood to this world lol. So I am still quite unfamiliar with everything...
The app is called SGS2 BootScreen Change By Hellcat.
I am more than open to other suggestions as well.. This was just the only app i could find that does this....
Have just tested on rom my atm which is biftor v11 with apollo kernel and works ok. Boot screen is my profile pic am thinking it may be to do with 4.2.2 custom rom mate. Il still have a look and see whats up. Have you emailed hellcat? He will be the best and quickest way to find out whats up.
Thank you again for all your help, I am gonna have to get some sleep now though as I must return to work tonight (early at that for a regional communications meeting that makes my night a 14 hour shift) Anyways I will check back as soon as I awake from deep hibernation lol.
Id love to see some type of desktop program for doing this or an all in 1 boot manager that will allow me to manage the boot logo, animation, and shutdown. This would be awesome and if it transferred everything through ADB Automatically thatd be 100X better, too bad i am illiterate in making this myself
I found a kernel made by hellcat that allows you to change boot logo, but i do not know which one i would need.....
http://forum.xda-developers.com/showthread.php?t=1182922
Dont even try to use them. Forget that thread.
Ya there's no kernels there for me was just wondering why for old but not for new.... Might just have to give up on this
alright so i just tried using root tool box pro to back up bootlogo as well as boot animation and it fails to do so... So im assuming my Avatar rom has changed where they are located...
I was able to use the root toolbox to disable the animation though... weird.
Post to dev on avatar rom and ask were it is
Anyone else have any input to this problem? ?
andrewwright said:
Post to dev on avatar rom and ask were it is
Anyone else have any input to this problem? ?
Click to expand...
Click to collapse
Where would i do this? I went to avatarrom.com but all they have there is to submit a feature request.... But nothing to email them or anything. I have searched avatar rom on here as well but only get information no way to contact...
I may consider changing roms if i can find something as editable.....
How familiar are you with Avatarrom to know the features list?
Is it this rom?? Ask there if it is mate
That's it. Do you have a link?
Related
Hello Guys !!!
I have been using serendipity and ultimatum rom with siyah kernel 3.2.4 for quite some time .. I'm a sucker for changing DPI to lower like 215-220 as I don't like big icons covering all screen space..
Yesterday I read somewhere that NEAK has better battery life as compared to siyah, so I tried to flash that.. however to my surprise I found that it just got hanged as sammy boot screen and didn't even boot.
Then just to test, I also tried cherripicker kernel and faced same issue with that too. then finally I reflashed my siyah and everything was back to normal and booted as it should.
My question is, has anyone noticed this issue before where only siyah supports multi-dpi and no-other sammy kernel ? Forgive me if its something that is understated somewhere and I missed it, but I found it kinda surprising as it should be something supported with all kernels...
xxr0x0rxx said:
Hello Guys !!!
I have been using serendipity and ultimatum rom with siyah kernel 3.2.4 for quite some time .. I'm a sucker for changing DPI to lower like 215-220 as I don't like big icons covering all screen space..
Yesterday I read somewhere that NEAK has better battery life as compared to siyah, so I tried to flash that.. however to my surprise I found that it just got hanged as sammy boot screen and didn't even boot.
Then just to test, I also tried cherripicker kernel and faced same issue with that too. then finally I reflashed my siyah and everything was back to normal and booted as it should.
My question is, has anyone noticed this issue before where only siyah supports multi-dpi and no-other sammy kernel ? Forgive me if its something that is understated somewhere and I missed it, but I found it kinda surprising as it should be something supported with all kernels...
Click to expand...
Click to collapse
I kind of doubt that it's the multi-dpi issue and it's more of a problem with ExTweaks settings. Before you flash a different kernel, I would clear all your ExTweak settings (under CWM > Kernel Specific) then wipe Dalvik and Cache, and then flash.
tocirahl said:
I kind of doubt that it's the multi-dpi issue and it's more of a problem with ExTweaks settings. Before you flash a different kernel, I would clear all your ExTweak settings (under CWM > Kernel Specific) then wipe Dalvik and Cache, and then flash.
Click to expand...
Click to collapse
I followed ur instruction word to word and still no go... so I guess I am right ..
Thanks for ur input though ..
xxr0x0rxx said:
I followed ur instruction word to word and still no go... so I guess I am right ..
Thanks for ur input though ..
Click to expand...
Click to collapse
Your flashing something wrong, Kernels have no support of DPI.
Its the ROM, and the applications that are affected by DPI change
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
aspen1135 said:
Hi I'm currently on the root box ROM with the siya kernal and wanted to flash a different one but no matter what I do I get an error before unloading the package. I came across this problem before and the solution was to just reflash aokp. I believe the logic was, siya was not compatable to open the package or something and needed cwm. However I can't find a flashable zip of cwm default kernal and I do not have a computer to access for Odin at the moment. Someone please, point me in the right direction...
Click to expand...
Click to collapse
I would use Heimdall to flash if possable also i would flash Siyah's new kernel also check the md5 to verify the rom you are trying to flash sometimes during download things get goofed after that make sure you wipe everything data/cache/dalvik and then try flashing your rom
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
This link explains how to edit build prop to get rid of status errors.
http://forum.xda-developers.com/showpost.php?p=24266658&postcount=471
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Phalanx7621 said:
You're trying to say yer getting the status 7 error. I think that's what I've gathered. Just do the same thing you did before, if u happen to have Tasks 7.3 version available flash that. It's a build. Prop problem with your phone showing a different model number than i777 because you are /were on a ported rom with i9100 showing as the model number. Flashing this version of tasks rom sets your build. Prop back to i777. U could actually use any rom that is based on i777 firmware although they may have scripts to check if your current build. Prop is i777 or not and may not let u flash it. The 7.3 version of tasks AOKP has those script asserts removed and it doesn't check what yer running which makes it great for situations like this. U can download tasks 7.3 AOKP by googling dev.host task AOKP I think. I haven't tried but someone said it's still up there. Or I could be completely wrong and status 7 error isn't what yer getting. In which case ignore this wall of text and go about your day. Lol,
Sent from Team Pirate Headquarters.
Click to expand...
Click to collapse
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
aspen1135 said:
First off, this was the reply I was kinda looking for, thnx. Second, don't tell me what to do *****. third, if what your saying is true, I should be able to flash the shoshock ROM and then have no problems with flashing anymore?
Click to expand...
Click to collapse
Cause I'm trying right now. Wish me luck I'll report after I'm done with excessive flashing
RatusNatus said:
Status 7 = incompatible CWM
Just flash the STOCK kernel.
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
MotoMudder77 said:
Why you keep stating this garbage? its caused by build.prop.
flashing from CWM 5.xxx to 6.xxx is not a problem.
Click to expand...
Click to collapse
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
gregsarg said:
Unsupported CWM image ...
Your CWM or TWRP is not compatible with your rom...
Flash the CWM from the "everything " thread ...
Then try again ....it seems this version is the most stable ....IMHO
Edit :
It's non touch ...but it's rock solid ...g
Click to expand...
Click to collapse
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
RatusNatus said:
Are you telling me that flashing the stock CM kernel wont solve the problem? Are you sure?
The Instalation checks the build.prop to know if your cwm image is good to go.
If not, it MEAN that your version of CWM is unsupported.
Did you flashed the ROM ??? LOL
This is from closed threats:
"You are most likely using an unsupported recovery refer to OP for proper recovery"
http://forum.xda-developers.com/showpost.php?p=30623016&postcount=218
"I'm pretty sure that the solution for this problem is to update CWM. Or even better, use TWRP."
http://forum.xda-developers.com/showpost.php?p=30622934&postcount=217
Click to expand...
Click to collapse
This problem has been occurring for a long time now. And has nothing to do with your version of cwm. It has to do with the script IN THE ROM YOU ARE FLASHING. If it has the script in the rom to check what phone model u have, and it detects something other than what it should, it basically says "hey! This guy doesn't have our phone! Stopppp!" And won't let u flash. Status 7 error. To fix this, either manually remove the script that checks for this in the rom yer flashing, modify the build.prop in the rom yer currently ON to reflect the model number of the rom u want to flash, or flash another rom that already has this script checking removed to get your build.prop to reflect the new model number u want it to show. Either way none of it has to do with your version of cwm.
Sent from my SGH-I777 using Tapatalk 2
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...and thanks for unresume my resume.
Sent from my SGH-I777 using xda app-developers app
RatusNatus said:
So why flashing the cm9 kernel and Not the ROM deal with that?
Are you sure that a kernel hás nothing to do with?
Im not just telling that, thats what i did and it works.
Im here sharing this info.
Tell me, did you tryed that to tell here that it wont work?
Just flash another kernel without the touch cwn.
...
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
You had a different issue then. most likely just a corrupt recovery. as there are NO problems flashing from one version of CWM to the next.
The common status 7 error, is caused by the updater.script searching the build.prop. as stated a million times in almost every thread.
Hi All
1st of the usual apology if this info is already out there, been searching for a while but cant seem to find the needed info.
Galaxy S2 i9100
UK T-Mobile
ICS 4.0.3
Kernel 3.0.15-I9100BVLPD
Questions
1. How do i know if a certain rom i want to try is comparable for my phone ? Can i use any ROM for an I9100 or do i need to look for BVLPD or what ?
2. Seeing as my phone is a paid monthly sub to UK-T-Mob, do i need to have a t mobile compatible ROM ?
3. .........errrr. well i had more Q's but my minds gone blank :cyclops:.. ill post more when i remember.
Many Thx
Peace
AnubuRe said:
Hi All
1st of the usual apology if this info is already out there, been searching for a while but cant seem to find the needed info.
Galaxy S2 i9100
UK T-Mobile
ICS 4.0.3
Kernel 3.0.15-I9100BVLPD
Questions
1. How do i know if a certain rom i want to try is comparable for my phone ? Can i use any ROM for an I9100 or do i need to look for BVLPD or what ?
2. Seeing as my phone is a paid monthly sub to UK-T-Mob, do i need to have a t mobile compatible ROM ?
3. .........errrr. well i had more Q's but my minds gone blank :cyclops:.. ill post more when i remember.
Many Thx
Peace
Click to expand...
Click to collapse
You can flash any ROM you like, your carrier won't notice it. The only thing that may not work is the modem, but guess what? there's plenty of modems you can flash
Keep in mind that once you modify your ROM your warranty will be voided, so back it all up just in case.
If your device is I9100, then look for I9100's ROMs.
AnubuRe said:
Hi All
1st of the usual apology if this info is already out there, been searching for a while but cant seem to find the needed info.
Galaxy S2 i9100
UK T-Mobile
ICS 4.0.3
Kernel 3.0.15-I9100BVLPD
Questions
1. How do i know if a certain rom i want to try is comparable for my phone ? Can i use any ROM for an I9100 or do i need to look for BVLPD or what ?
2. Seeing as my phone is a paid monthly sub to UK-T-Mob, do i need to have a t mobile compatible ROM ?
3. .........errrr. well i had more Q's but my minds gone blank :cyclops:.. ill post more when i remember.
Many Thx
Peace
Click to expand...
Click to collapse
1. You can use any I9100 rom if its a UK phone. Just dont try and flash a I9100x rom.
2. See #1.
Please dont make your next questions be silly ones like "how do I root my phone" or "how do I flash a rom", These questions have obviously already been asked/answered already and also covered in sticky topics/guides.
All you need to do is reboot into download mode, flash Siyah kernel, wipe data and then flash whatever rom you choose via recovery.
Ok, cool, many thx guys... & yeah i've backed up my data & efs all ready..
Now i'm gonna go rom crazy for a bit.
lol TheATHEiST.. i was gonna ask just those Q's and ask whats the best rom ?. joke.. i've been reading up on how to do. phone is rooted via the easy not needing an insecure kernel method. gonna try Siyah & a duel boot.
Peace
AnubuRe said:
Ok, cool, many thx guys... & yeah i've backed up my data & efs all ready..
Now i'm gonna go rom crazy for a bit.
lol TheATHEiST.. i was gonna ask just those Q's and ask whats the best rom ?. joke.. i've been reading up on how to do. phone is rooted via the easy not needing an insecure kernel method. gonna try Siyah & a duel boot.
Peace
Click to expand...
Click to collapse
Good luck.
Don't go bricking now.
Thx G
I have another Q if anyone knows: i'm currently trying out duel boot, but tried one and it wouldn't work and am looking for others to try but not sure if they are comparable or not with duel boot.. so heres my question
The backup i made from the recovery in CWM before trying any ROMS, is it a ROM or just a backup like a ROM ? if i try another rom without duel booting and dont like it or it messes up will my backup put phone EXACTLY back how it was ?
Thx
AnubuRe said:
Thx G
I have another Q if anyone knows: i'm currently trying out duel boot, but tried one and it wouldn't work and am looking for others to try but not sure if they are comparable or not with duel boot.. so heres my question
The backup i made from the recovery in CWM before trying any ROMS, is it a ROM or just a backup like a ROM ? if i try another rom without duel booting and dont like it or it messes up will my backup put phone EXACTLY back how it was ?
Thx
Click to expand...
Click to collapse
It's a back up, you can't dual boot a back up. It's just sitting there for a....rainy day.
What ROMs are you trying? what kernel are you using?
Some kernels don't support dual boot, as well as some kernels don't support certain ROMs (like JB leak).
Go ahead and do some research on this matter, you got a lot of material to go around.
gastonw said:
It's a back up, you can't dual boot a back up. It's just sitting there for a....rainy day.
What ROMs are you trying? what kernel are you using?
Some kernels don't support dual boot, as well as some kernels don't support certain ROMs (like JB leak).
Go ahead and do some research on this matter, you got a lot of material to go around.
Click to expand...
Click to collapse
Hi again, i must have not been clear in what i meant. (i did edit my previous post to make it clearer but it said i have to wait 5 mins cus i'm a new member.. despite being registered for over 1 yr. my edit must have failed)
i know a backup cant dual boot, what i was asking is; the backup i make in CWM "before" attempting to mess with any ROMs, is it in its itself a ROM ? (or just a none zipped backup).. i was also asking after trying a ROM, if i didn't like it or it messed up my phone would the original backup i make put my phone back EXACTLY as it was ?
In the past few hrs i've tried to dual boot using the Siyah kernel..
1 SuperNexus 2.0 rom http://forum.xda-developers.com/showthread.php?t=2076650 stuck on boot saying com.adroid stopped working (or something)
2. SlimBean ROM,, same error
3. Resurrection Remix rom.. it asked which kernel & modem i wanted to install so i aborted.
Due the these errors thats why i asked the above question, that IF i go ahead & try a ROM on its own without dual booting, will my backup put phone how it is now using the backup i made in CWM if things go wrong ?
Thx again for anyhelp
I still would like to try & dual boot but i may leave that for another time & just try a straight rom.
Peace
Another Q, is there a thread that lists all\most or a lot of ROM's, searching is killing me.. and as XDA is sooooooooooo bit i know a thread with them all could be right under my nose.
Thx
AnubuRe said:
Hi again, i must have not been clear in what i meant. (i did edit my previous post to make it clearer but it said i have to wait 5 mins cus i'm a new member.. despite being registered for over 1 yr. my edit must have failed)
i know a backup cant dual boot, what i was asking is; the backup i make in CWM "before" attempting to mess with any ROMs, is it in its itself a ROM ? (or just a none zipped backup).. i was also asking after trying a ROM, if i didn't like it or it messed up my phone would the original backup i make put my phone back EXACTLY as it was ?
In the past few hrs i've tried to dual boot using the Siyah kernel..
1 SuperNexus 2.0 rom http://forum.xda-developers.com/showthread.php?t=2076650 stuck on boot saying com.adroid stopped working (or something)
2. SlimBean ROM,, same error
3. Resurrection Remix rom.. it asked which kernel & modem i wanted to install so i aborted. gold
Due the these errors thats why i asked the above question, that IF i go ahead & try a ROM on its own without dual booting, will my backup put phone how it is now using the backup i made in CWM if things go wrong ?
Thx again for anyhelp
I still would like to try & dual boot but i may leave that for another time & just try a straight rom.
Peace
Click to expand...
Click to collapse
Lol, that was some snappy typing.
If things goes south, yes, everything goes back the way it was by the time you backed it up.
What kernel are you using again? Here, have a look.
Thx
I'm using the Siyah kernel.....
Yeah i used the guides linked from that thread but i only tried the 1st method (didn't work) ... now i know my back up is good i think ill go ahead & try the 2nd method.
Thx again G
Good luck man.
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