So obviously i didn't do enough research before i started playing with my phone, and i'm sorry if my question has been asked a hundred times but i have done alot of reasearch and i still can't get it to work.
I succesfully installed a custom rom some months ago (resurection i think) and i wasn't happy with it (some bugs). So i wantet to install FOXHOUND Revolver Ocelot but then weird things started to happen. It all ended with a boot loop but i got it back to normal thanks to the sticky (http://forum.xda-developers.com/showthread.php?t=1457458). Now i have tried to install various CWM.tar via Odin so i can flash FOXHOUND Revolver Ocelot (http://forum.xda-developers.com/showthread.php?t=1162715). But everytime i try to install CWM it just hangs at boot screen with the yellow triangle and doesn't go any further. If i press Vol up + home + lock the phone restarts to the same boot screen and it stays there. If i shut off the phone it reboots and hangs at the boot screen.
So my question is really, from the point i'm at now (fixed brick with the aforementioned sticky) what should i do? Install a different kernel? (suggestion?) ROM manager (which?), root and then flash FOXHOUND Revolver Ocelot?
This is the info from About phone after i have followed the sticky to unbrick phone, if its interesting:
Model Number: GT-I9100
Android version: 4.0.3
Baseband version: I9100XXLPH
Kernel version: 3.0.15-I9100XXLPH-CL118559 [email protected]#3
Build number: IML74K.XXLPH
Try flash kernel via Odin for example syiah its good kernel ans that should fix when u flash go to cwm vol up+home+pwr button and wipe delvik and fix permission and boot
Sent from my GT-I9100 using xda premium
stopro said:
Try flash kernel via Odin for example syiah its good kernel ans that should fix when u flash go to cwm vol up+home+pwr button and wipe delvik and fix permission and boot
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks for the help. I tried to flash the siyah kernel via Odin, and I got a pass and all seemed good. I reboot my phone, SGSII bootscreen, then siyah bootscreen, then black and nothing. Tried multiple times. Booted into recovery and wiped dalvik and fixed permissions. Same thing still. This also happened when i tried to flash the Dorimanx kernel yesterday.
Am I doing something wrong?
MajorWobble said:
Thanks for the help. I tried to flash the siyah kernel via Odin, and I got a pass and all seemed good. I reboot my phone, SGSII bootscreen, then siyah bootscreen, then black and nothing. Tried multiple times. Booted into recovery and wiped dalvik and fixed permissions. Same thing still.
Am I doing something wrong?
Click to expand...
Click to collapse
in recovery try wiping cache partition then Dalvik cache after that do fixpermission then reboot system and see
Sun90 said:
in recovery try wiping cache partition then Dalvik cache after that do fixpermission then reboot system and see
Click to expand...
Click to collapse
Didn't work. But i had the rom on the sdcard so just went to recovery and installed in, now it works. So i don't quite now what the problem was, but when I installed the Revolver ROM all is working.
Thanks for the help guys, really appreciate it.
Related
Ok so my Galaxy S2 i9100 arrived today!
I began by flashing VillainRom 1.1 and then decided to give Litening Rom a try, fired up odin, selected the rom and hit start. It completed but instead of rebooting the phone has gone into an endless reboot cycle, just showing the boot screen over and over.
I pulled the battery and am reflashing now, it that doesn't work where do I go from here?
Cheers
Edit: Nope, still not booting up properly
You go to the OP of the VillainROM thread and read the words in big red letters.
nobnut said:
You go to the OP of the VillainROM thread and read the words in big red letters.
Click to expand...
Click to collapse
So if I reflash VillainRom then enter recovery, wipe user data and THEN install Litening Rom it should work?
Or have I permanantly screwed my phone?
Edit: So I reflashed Villain and it booted up fine, I went into recovery as suggested and selected wipe user data. After that finished I held the power button down until the phone turned off, then booted into downlaod mode and flashed litening. Same problem occurred, I tried this two more times but both to no avail.
What am I doing wrong?
Cheers
flash to stock KE7, then boot into recovery, select wipe data/factory reset and wipe cache, boot into download mode, flash lite'ning rom, then then it should work 100%.
oh and btw, as long as you can boot into recovery/download mode, your device isn't bricked.
kaukassus said:
flash to stock KE7, then boot into recovery, select wipe data/factory reset and wipe cache, boot into download mode, flash lite'ning rom, then then it should work 100%.
oh and btw, as long as you can boot into recovery/download mode, your device isn't bricked.
Click to expand...
Click to collapse
Sorry to seem like a noob here... but a few quick questions, What does KE stand for exactly and where can I downlaod a stock version from? Cheers
KE means after KD but before KJ ,just as A is before C .
Stock roms dev page .
jje
kaukassus said:
flash to stock KE7, then boot into recovery, select wipe data/factory reset and wipe cache, boot into download mode, flash lite'ning rom, then then it should work 100%.
oh and btw, as long as you can boot into recovery/download mode, your device isn't bricked.
Click to expand...
Click to collapse
Worked brilliant, thanks
I had a similar problem, but I solved it by just booting into recovery mode, wiping data(/factory reset) and dalvik cache and then just flashing then ROM through "download" mode.
I did not have to flash any stock ROM prior to that. Just these two simple steps!
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
i have the exact same problem!
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
rembrandtlnx said:
try download it again. Sound like a corrupted package
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I tried and got the samething. I also tried a different cm nightly and got the same results.
InFa_ReD_1 said:
I tried and got the samething. I also tried a different cm nightly and got the same results.
Click to expand...
Click to collapse
me2 only stock roms work for me =(
I think there was an issue with the version of CWM used on the CF-roots since it's been modified by CF and because it's an older version.
After you've rooted with CF, try flashing a kernel on there with a newer version of CWM on there (I used codeworkx's kernel from the Cyanogenmod wiki I've attached below with CWM 4.0.1.4).
Once this kernel is on there, then try flashing the CM7 ROM as per this thread. I prefer flashing from recovery myself, but it's your call.
Make sure you flash it twice in a row if you're having issues.
The problem, as stated above is that cf root kernel installs a modified version of CWM that won't work with CM7. Another thing is you have to flash a stock KH3 because KI3 has the new bootloader (unless you flashed KI3 with the old bootloaders). Then, you have to flash the codeworkx kernel so you get a compatible version of CWM. Once in CWM clear data factory reset + clear cache partition + clear dalvik cache (from advanced).
THIS IS IMPORTANT: Flash the ROM from sd card and when finish do not reboot device, just flash it again without wiping anything in between, just 2 consecutives "install from sd card". When this is done you can reboot the system and then enter again to CWM to flash the google apps .zip file that you can download from the CM7 thread.
Hope this helped. When I flashed CM7 i had exactly the same problem and went back to stock cause it was a pain in the ass to flash it fr the first time. But once you get in CM7, everything becomes great and easy, and you can update the nighlies directly from ROM manager without doing any wiping. You just can't use ROM manager when getting to CM7 for the first time.
InFa_ReD_1 said:
Hi there, I need your help and advice please.
Here’s my problem. My phone is the SGS2 running KI3 rooted with CF-root KI3 flashed the secure kernel and then flashed the zImage so I still have root CWM and to get rid of the yellow triangle. I have downloaded CM nightly 88 to my laptop and transferred it to my S2 via usb cable into the download folder.
Here’s where the problem comes into play when I run CF’s CWM and choose reboot into recovery I do a wipe/factory reset / wipe cache and update via sdcard, I pick the cm88 from the download folder and it starts to update and then stops. I reboot and it’s stuck on the Samsung S2 page (boot loop). I then have to get into the recovery and restore my phone to the previous state. Can someone help me I would like to try the CM’s custom rom but don’t know what I’m doing wrong? Thanks.
Click to expand...
Click to collapse
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
droidphile said:
DO NOT use cf-root to install CM7. It's stated by Codeworkx a lot of times in CM Q&A thread. Just flash his kernel to get cwm.
http://forum.xda-developers.com/showthread.php?t=1118693
Now you have the original cwm recovery (from Koush). Boot into recovery, Wipe data, cache, dalvik.
Install CM7 twice in a row without rebooting.
Then flash gapps (without rebooting) http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip.
Now reboot. Wait for a few mins since system has to build dalvik cache. And you're all good to go
Worried about yellow triangle? Get a usb jig.
Siyah kernel 2.0 supports CM7 and miui. So....have fun.....!!
Click to expand...
Click to collapse
Thanks. Can i flash the orginal CWM over top the CF CWM?
InFa_ReD_1 said:
Thanks. Can i flash the orginal CWM over top the CF CWM?
Click to expand...
Click to collapse
I did it and didn't have any problems, just follow the steps as I posted above.
tomascunill said:
I did it and didn't have any problems, just follow the steps as I posted above.
Click to expand...
Click to collapse
Great thanks for the help it worked I'm now running CM7. One thing though I can make calls but have lost my network connection. Can someone help me with this? Sorry for all the questions I'm new to the whole smartphone business. Thanks.
Ok all fixed up thanks for all your help.
I recently got a galaxy player 5 international with froyo. I rooted it with no problems, but when I tried to flash a kernel with cwm recovery it would get stuck in a boot loop unless i went into the cwm recovery mode. I noticed that the kernel I used, rumirand's r14, was based off of GB and thought that might be my problem. I tried updating my firmware to GB using WT Ho's custom rom, and now it just hangs on the samsung logo, but I can still get into cwm. I made sure to wipe both caches and wipe data before installing the rom. Is this fixable or have I turned it into an expensive paperweight?
Did you try a factory reset?
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Chris4evernoob said:
Did you try a factory reset?
Click to expand...
Click to collapse
Now or before installing the rom? I did a factory reset before installing, but I haven't done one since.
DZonikg said:
I am not expert but i tried the same with R14 kernel and bricked but done the same with R13 and it worked .
Click to expand...
Click to collapse
I just flashed the R13 kernel, but I'm still in the same situation.
Instead of flashing a new kernel there should be factory reset option on the first set you have or in "mounts and storage"
I had this problem once and I managed to solve it flashing a full rom (like 2.3.5 rooted and with rj kernel). It seems some users are having problems when flashing only the kernel. After you solve the problem, flash back group rom.
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
jnmaster said:
I just tried the rom+kernel. It said it was successful but it must not have been because it was hanging on boot again, and now it won't respond to the power button. If I plug it in to the computer it gets an image of a battery turns off and repeats.
Click to expand...
Click to collapse
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
WT Ho said:
Can you go back to CWM after flashing rom+kernel? If yes, usually it is a matter of wiping the data and Dalvik cache. Which ROM+Kernel did you flashed?
Click to expand...
Click to collapse
No, I'm not able to get a response from the power button.
I used the ROM + kernel you posted http://forum.xda-developers.com/showthread.php?t=1446774
Followed instructions to flash KlassicRom and am now bootlooping.
Installed Steve's Kernel and booted into CWM where I made a backup.
Then back to odin to install KlassicRom R5 - no errors but on reboot just bootlooped.
After waiting 15 minutes with bootlooping, I booted into CWM to restore. Restore indicated success but on reboot, now just get Samsung boot screen with Steve's android guy in the corner. Stuck on boot.
I can still reboot into CWM and Odin recognizes the player when in download mode, so I'm hoping it's recoverable.
Anyone available to guide?
Thanks in advance for any help!
DCoy
Boot into CWM and
wipe cache
Factory Reset
go to advance and Wipe Dalvick Cache
then exit CWM and reboot.
Tried the wipes before. Did so again.
No errors reported with Wipe Cache
No errors reported with Factory Reset
Wipe Dalvik Cache reports:
Dalvik Cache wiped.
E:unknown volume for path [/sd-ext]
Reboot hangs at Steve's Android guy and Samsung again.
R5 don't work with steve's kernel. It only works with klin kernel or terrasilent.
Sent from my YP-G1 using xda premium
zaclimon said:
R5 don't work with steve's kernel. It only works with klin kernel or terrasilent.
Sent from my YP-G1 using xda premium
Click to expand...
Click to collapse
Downloaded and Odin Flashed R3
Odin reported PASS
on reboot, bootlooping again.
Booted into CWM and Wiped Cache, Factory Reset, and Wiped Dalvik, then reboot.
Bootlooping still.
Same error messages as before when boot hung:
No errors reported with Wipe Cache
No errors reported with Factory Reset
Wipe Dalvik Cache reports:
Dalvik Cache wiped.
E:unknown volume for path [/sd-ext]
Then bootlooping.
US or international, if US there is a stock but rooted ROM on here somewhere (not the full restore using heimdall), i'll look for it later that you can use to flash back with odin then boot into STOCK recovery and wipe data and factory reset that is what got me out of the bootloops when I first started flashing.
here is the link if your running the US model http://forum.xda-developers.com/showthread.php?t=1512331&highlight=stock+rooted+4+0
Downloaded the stock rom. Odin flashed. Booted into stock recovery and did factory reset/wipe.
Rebooted to joy. Thanks!
Might wait a bit before trying to flash the custom rom again.
DavidCoy said:
Downloaded the stock rom. Odin flashed. Booted into stock recovery and did factory reset/wipe.
Rebooted to joy. Thanks!
Might wait a bit before trying to flash the custom rom again.
Click to expand...
Click to collapse
Flash the terrasilent kernel and use that version of CWM to make a backup, its a much newer version and backs up things the older misses, also don't have the USB cable connected to the player when your in CWM thats what seamed to throw me into the bootloop, As long as you stick to Klins ROMs only (not using any of those CM7's or anything based off CM7) what you just experienced and solved with the "stock" ROM flash is the worst case scenario when flashing only variations of Klin's ROM with Odin.
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
SynGates said:
Hello, I hope this is the right group.
I have spent the last 2 days trying to get JB working on my SGS2. I previously had ICS Hydra h2o 1.4.1 ROM on my device.
The troubles started when I tried booting into CWM recovery. The phone wouldn't go past the yellow triangle so I had to use ODIN to flash stock Samsung ICS ROM on the phone to get it working again. I have since tried multiple JB ROMs with different kernels but most of them get past the yellow triangle but then stop on logos varying between kernels. I am also unable to boot into CWM recovery and must flash a CF-Root kernel using ODIN to get into recovery.
It is strange that this happens only with JB ROMs and I have no trouble installing Hydra h2o again through recovery.
I always use the same method of installing ROMs through CWM:
- wipe data/factory reset
- wipe cache
- wipe dalvik
- install .zip from sdcard
I have also tried fixing permissions before and after flashing ROMs, nothing seems to get me into the OS.
One ROM, Vanilla RootBox, I have found to sometimes boot all the way into the OS but the system frequently freezes and is unstable. Looks amazing tho.
Do you have any ideas on how I could get JB ROMs working with my SGS2? Is there anything I am missing?
Click to expand...
Click to collapse
Follow this:
-boot to CWM recovery
-wipe data /factory reset
-wipe dalvik cache (under advanced)
-format /system (under mount and storage)
-flash ROM
-flash Gapps (for jelly bean)
-fix permissions
-reboot phone
Done
Swyped from my Samsung Galaxy SII
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
Nope
Swyped from my Samsung Galaxy SII
SynGates said:
Thank you for the reply, but that method does not seem to work either.
One thing I have noticed though is when I select wipe data/factory reset it reports an error formatting /sdcard/.android_secure.
Is this something that could be causing my problems?
Click to expand...
Click to collapse
which kernel u were into while flashing the JB rom?
Use siyah or dorimanx kernel it works fine for me must be your kernel
Sun90 said:
which kernel u were into while flashing the JB rom?
Click to expand...
Click to collapse
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
SynGates said:
When I'm flashing I'm using XLPB kernel with CF-root. That's the kernel I flash to get into CWM when the ROMs misbehave.
Click to expand...
Click to collapse
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Sun90 said:
try this.
after flashing Cf-root kernel from ODIN.
1) flash the .zip file of siyah kernel v3.5.2 for S2, dwnld the same Here.
2)after that reboot into siyah kernel recovery.
3) wipe data/factory reset, then wipe cache and dalvik.
4) flash the JB rom zip file(Vanilla root box).
5)reboot ur phone and see.
ps- before doing wipes and rom flash do please backup ur exsisting rom once ur into siyah kernel recovery first
Click to expand...
Click to collapse
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
SynGates said:
Gives me Kernel panic or stops at the triangle loading screen. Seems the only way to get into CWM is through CF-root.
Click to expand...
Click to collapse
Use a newer version of siyah or dorimanx, they should work fine
Sent from my GT-I9100 using xda app-developers app
I have tried three versions of syiah, including 4.1.4 but I will try dorimanx and report with the results.
edit: dorimax kernel is the same.
One thing I noticed tough is whenever I wipe dalvik cache the system reports "unknown volume for /ext-sd blablabla" - maybe this is connected to my problem?
I am at a complete stop...
No JB kernels seem to work whatsoever. Is there any wit to flash the bootloader? Or is that even possible?
I really would like to get JB working on my device.
There must be something about the previous state of my phone, some files or folders that are in the way or are missing or somewhat. Is there any way to completely reset the phone? Not just factory resetting it since that is not working.
edit: Progress! These are my steps:
- Downloaded fresh stock Samsung ROM and another version of CF-root.
- Flashed stock ROM and then CF-root kernel.
- Booted into recovery and did the whole wipe.
- Flashed .zip twice (don't know if that did the trick or what)
- Wipe dalvik cache and fix permissions.
After that the phone booted normally and I'm now running ResurrectionRemix with Android 4.1.1, hoping it wil be awesome as ****.