menu buttons messed up after flashing revolution rom - AT&T Samsung Galaxy S II SGH-I777

I have the AT&T version of the galaxy s2. I rooted it earlier and everything was working fine with the stock rom. Then i downloaded the revolution rom because it seemed pretty popular. After flashing the rom my menu buttons at the bottom of my phone are all messed up.The search button and back button dont work at all then the home button actually works as the back button instead of the home button. So im guessing the revolution rom is made for one of the internaional galaxy maybe? Can anyone help me? Even other rom suggestions would be freat because im really not liking the feeling of this one, especialy with my buttons all messed up. thank you ahead of time.

Just flash hellraiser overtop of the rom and it will fix all the buttons.

Unless you get the ROM out of the dev forum for the AT&T SGS2 you probably shouldn't flash it unless you have a really good idea of what you are doing. With my limited experience I would suggest flashing stock and starting over with a ROM designed for the right phone. If you read the hellraiser thread it is really an alpha release and there is a lot of debugging and testing going on.
Sent from my SAMSUNG-SGH-I777 using xda premium

Related

Vibrant Froyo issues

I´ve just flashed my Vibrant to the Eugene´s unbrickable froyo rom and so far I have a couple of issues. I´d like to see if anyone else has them and if they can be resolved.
- Android beyboard is not available.
- The home button functions now as the back button.
Did anyone experience something like this? How did you solve it?
thanks
Rafa
rawfa said:
I´ve just flashed my Vibrant to the Eugene´s unbrickable froyo rom and so far I have a couple of issues. I´d like to see if anyone else has them and if they can be resolved.
- Android beyboard is not available.
- The home button functions now as the back button.
Did anyone experience something like this? How did you solve it?
thanks
Rafa
Click to expand...
Click to collapse
That is an EXTREMELY old version that wasn't even for the vibrant initially..
KA5 is the newest (Find it in the development section..) (Which is for the vibrant)
The problem is that for some reason I´m not able to flash via recovery mode. I can only flash using a TAR rom with Odin. From what I´ve been seeing there aren´t many TAR updates of roms out there
Rafa, That rom is really used only for flashing back stock now. Typically if you had say a Nero 4.1 rom and wanted to go back to stock. If your phone got frozen trying to go Nero>>>Stock JFD you would instead do this:
Flash from NERO to Unbrickable froyo by Eugene then Stock.
Take Master's advice the Newest roms out are in the DEVELOPMENT section
Look them over the newest is the KA5 rom, but the Axura, the Einharjar and Nero are all very good and you would be very happy with any of them.
hope you're not in all that flooding in Rio State
good luck
rawfa said:
The problem is that for some reason I´m not able to flash via recovery mode. I can only flash using a TAR rom with Odin. From what I´ve been seeing there aren´t many TAR updates of roms out there
Click to expand...
Click to collapse
Make sure it is properly rooted, and you have rom manager, it the rooting is corrupted, then you could have that problem
Thanks, fellas. I´m going to get Rom Manager and try it again. At the moment I have Eugene´s rom and whenever I try to use the recovey mode to flash a different rom (I´ve downloaded Nero V3, which is supposed to be very stable and fast) I cannot select "reinstall packages"...actually I cannot select any option as the ON button doesn´t seem to respond (only the volume rocker buttons).
Oka1, thanks for your kind words. That was very thoughtful of you. Luckly where I live was not afected at all by the rain.
One more question, is there anything wrong with the official roms (http://samsunggalaxysforums.com/sho...firmwares-for-Samsung-Galaxy-S-I9000-Download) ?
Not per se but, i am not sure on which Galaxy format Brazil uses, e.g. which Build
It could be the I9000/ (T-mobile (959)) or could be 897 etc, so make sure the phone and the build are compatible with the Rom you want to flash. Remember some service providers customize the phone
Espero que ajude, boa sorte
Mine is 959, so I´m thinking the official froyo roms on that website won´t work properly for me.
p.s - getting good with the portugue, hey

[Q] What the hell is wrong with my I9100?

Hey guys,
Im having some troubles with my device and I thought you guys could help me resolve it.
Ok so, whenever i flash a stock Samsung ICS rom on my SII, my home-button doesnt function anymore and pressing the power button turns off my device without giving any options menu. I flashed to stock XXKH3 XXKI3 XXKL1 etc and then back to ICS but the buttons just dont work. Im sure i have the GT-I9100 the package says so and the sticker under the battery in the device itselves also says i9100. Now another weird thing, theres a rom in the Android development thread well its actually a backup of someones ICS rom and whenever i restore that ROM and i boot the phone the home button actually works again, but still a no go for the power button. I flashed wit .pit format system/data/cache everything.
Do you guys have any idea whats wrong with my Device?
Cheers.
ICS = test rom alpha beta not released by Samsung not fully working for testers only .
As your warranty is now void i suggest flash stock rom clear custom rom counter and test .
jje
Try cm9 I haven't experienced any similar problems with that
Sent from my GT-I9100 using XDA App
It is unstable. Wait for stable ver. Or official ICS

5.0 Kernel/ROM/Odin Help

Skip to second paragraph for main problem, Third for main question
I am so hungry to get my hands on ICS, and I will do anything to get a rom, but not sacrifice my camera. So for a while a was literally switching back and fourth between stock rom and paranoid android (4.0.4) just to take a picture. But recently, I tried out ICS Crumble, based on AOKP, and I switched back because it was the slowest and buggiest rom I have used on any device, even when I tried other AOKP roms.
So I switched back to Paranoid android via CWM Recovery, but usually I use ROM Manager, since it back ups the stock rom automatically, but I was mad so I used CWM Recovery, and forgot to do a backup...So I tried flashing the stock rom, and pre-rooted version of the stock rom, but all it says is "Installing update, Installation aborted". I am wondering: where to find 2.3.6 odin update (I tried searching, no luck), if I can download a 4.0.4 kernel along with my 4.0.4 rom to get the camera back, or how do I get the camera back.
The main question is: HOW DO I GET THE CAMERA BACK, THAT IS ALL I WANT AND NEED. If I can't, well you now know a Galaxy Player is up for sale, and I will just get myself a Nexus 4 off ebay (only place you can get it). And please reply, Ieft this out of the Q&A since my other questions gone unreplied, depsite all the view the've got, if I can't get it back, just tell me, the iphone will come into your house and rob you if you dont....
coolwiththecool2 said:
Skip to second paragraph for main problem, Third for main question
I am so hungry to get my hands on ICS, and I will do anything to get a rom, but not sacrifice my camera. So for a while a was literally switching back and fourth between stock rom and paranoid android (4.0.4) just to take a picture. But recently, I tried out ICS Crumble, based on AOKP, and I switched back because it was the slowest and buggiest rom I have used on any device, even when I tried other AOKP roms.
So I switched back to Paranoid android via CWM Recovery, but usually I use ROM Manager, since it back ups the stock rom automatically, but I was mad so I used CWM Recovery, and forgot to do a backup...So I tried flashing the stock rom, and pre-rooted version of the stock rom, but all it says is "Installing update, Installation aborted". I am wondering: where to find 2.3.6 odin update (I tried searching, no luck), if I can download a 4.0.4 kernel along with my 4.0.4 rom to get the camera back, or how do I get the camera back.
The main question is: HOW DO I GET THE CAMERA BACK, THAT IS ALL I WANT AND NEED. If I can't, well you now know a Galaxy Player is up for sale, and I will just get myself a Nexus 4 off ebay (only place you can get it). And please reply, Ieft this out of the Q&A since my other questions gone unreplied, depsite all the view the've got, if I can't get it back, just tell me, the iphone will come into your house and rob you if you dont....
Click to expand...
Click to collapse
I'm no expert at this, but only a gingerbread ROM would get your camera to work. I recommend flashing this custom ROM. and flashing the correct kernel.
http://forum.xda-developers.com/showthread.php?t=1465144
http://forum.xda-developers.com/showthread.php?t=1445840&highlight=daily
Hopefully this helps.
Thanks I'll try it later today
Sent from my YP-G70 using xda app-developers app
Flash chip rom..its closest look to ICS ..all other like ICS keyboard ,ICS camera and so on you can download from market
Sent from my Nexus 7 using xda app-developers app
Keep in mind that using the ICS camera app, that there is no zoom-in / zoom-out function. The Galaxy player 5 does not support it.
What do you mean by that
Sent from my YP-G70 using xda app-developers app
coolwiththecool2 said:
What do you mean by that
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
The camera on our Galaxy Player 5.0 cannot zoom in.

[Q] supernexus 2.0 f****ed up my phone

I had SuperNexus 1 (jelly bean 4.1.1) on my phone for a long time and it was all great until one day it started flipping out. i mean literaly it started switching screens and all kinds of essential os apps started not responding and i got messages like : keyboard stopped responding, or launcher stopped responding. every second, it was unbearable. so i did a factory reset but it didn't help. so i went online to download and flash the same rom i used (SuperNexus 1) when i saw that they came up with SuperNexus 2.0 (jelly bean 4.2.1) so i downloaded it and flashed it. the install was successful until the phone booted, the home button was dead and my back button became my home button, in addition the keyboard looked strange. and when i made calls, all the other person could hear was loud Jettery noise like someone hammering. so i tried to re-install the rom or install SuperNexus 1 again but no matter what rom i flashed it gave me the error: assert failed status 7 something like that. and it displayed code on my screen. now i can replace the rom, my buttons are messed up and i dont know what to do any more i even tried replacing my CWM to CWM touch 5.8.1.5 please please help i cant use my phone and it's the only one i got:crying::crying::crying:.
thanks for reading sorry about the length of my post i wanted to give as much detail as possible. my phone is Samsung Galaxy S II GT - I9100
Did you try to return STOCK SAMMY's ROM ?
CuBG said:
Did you try to return STOCK SAMMY's ROM ?
Click to expand...
Click to collapse
i'm really a noob with android. the only android i used was super nexus and i'm unfamiliar with STOCK SAMMY's ROM or any other roms for that matter.
U shud try neatromlite with jeboo kernel..
Sent from my GT-I9100 using xda app-developers app
vzdemon said:
i'm really a noob with android. the only android i used was super nexus and i'm unfamiliar with STOCK SAMMY's ROM or any other roms for that matter.
Click to expand...
Click to collapse
Then I suggest you go do some reading before jumping in and doing anything else.
TheATHEiST said:
Then I suggest you go do some reading before jumping in and doing anything else.
Click to expand...
Click to collapse
i found a suggestion to re-install my kernel how do i find the one that will work with my phone and my rom.
back up & re flash, hell of an activity.
I don't know what to put here...any ideas?
vzdemon said:
I had SuperNexus 1 (jelly bean 4.1.1) on my phone for a long time and it was all great until one day it started flipping out. i mean literaly it started switching screens and all kinds of essential os apps started not responding and i got messages like : keyboard stopped responding, or launcher stopped responding. every second, it was unbearable. so i did a factory reset but it didn't help. so i went online to download and flash the same rom i used (SuperNexus 1) when i saw that they came up with SuperNexus 2.0 (jelly bean 4.2.1) so i downloaded it and flashed it. the install was successful until the phone booted, the home button was dead and my back button became my home button, in addition the keyboard looked strange. and when i made calls, all the other person could hear was loud Jettery noise like someone hammering. so i tried to re-install the rom or install SuperNexus 1 again but no matter what rom i flashed it gave me the error: assert failed status 7 something like that. and it displayed code on my screen. now i can replace the rom, my buttons are messed up and i dont know what to do any more i even tried replacing my CWM to CWM touch 5.8.1.5 please please help i cant use my phone and it's the only one i got:crying::crying::crying:.
thanks for reading sorry about the length of my post i wanted to give as much detail as possible. my phone is Samsung Galaxy S II GT - I9100
Click to expand...
Click to collapse
Home key not working, back key becoming home key, and assert failed status 7 all indicate to me that you either flashed a ROM meant for an SGH-I777 onto a GT-I9100, or flashed a ROM meant for a GT-I9100 onto an SGH-I777.
Do you happen to be an AT&T customer in the US? Did you get your Galaxy SII from AT&T? If you answered yes to both these questions, then you ABSOLUTELY DO NOT have a GT-I9100, and are in the wrong sections.
AT&T's Galaxy SII model (SGH-I777) has a separate forum.
vzdemon said:
i found a suggestion to re-install my kernel how do i find the one that will work with my phone and my rom.
Click to expand...
Click to collapse
By reading. Which you obviously havet done otherwise you wouldn't have flashed incorrect rom to your device.

[Q]So I have a rooted YP-GI1. What's next?

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

Categories

Resources