This i9100g doesn't belong to me. It belongs to a friend..
Here's what he told me he did:
1)Did an OTA update to the GB stock ROM
2)Phone restarted and got stuck at the logo. (It was that way when I got the phone from him)
What I did to try and fix it:
1) Flashed a ClockWorkMod Recovery kernel (GT-I9100G_ICS_ClockworkMod-Recovery_6.0.1.2.tar) using ODIN
2) Data wipe .. Cache wipe .. Wipe /system /cache /data...Wipe Dalvik
3) Flashed CM10 (cm-10.0.0-i9100g)
4) Reboot System. It didn't work.
So again,
2) Data wipe .. Cache wipe .. Wipe /system /cache /data...Wipe Dalvik
3) Flashed CM9 (cm-9.1.0-i9100g.zip)
4) Reboot System. Things don't work out yet again.
Here's what happens:
Phone shows the exclaimation mark at boot along with the initial logo and goes directly into CWM recovery
I think this is because I am on a GB bootloader. How do I get an ICS bootloader? Is it safe to flash the stock ICS Rom over CM10 i.e., to follow this guide without messing things up (http://forum.xda-developers.com/showthread.php?t=1619571). Is there something that can be done apart from this to get CM10 working?
Related
Howdy,
Yesterday my Gtab started booting up only into ClockWorkMod recovery mode. I know of no changes beforehand.
I have:
1) Cleared cache
2) Cleared Dalivck Cache
3) Reflashed my rom (BL1.2 CyanogenMod7.2.0-RC0 BUILD98 REPACK 2.3.7 GWK74)
4) Reflashed the kernel (pershoot)
5) Reflashed CWM
6) Verified the Volume Up button isnt stuck
I have not done a full wipe yet.
Any ideas outside of trying to wipe the whole thing?
Coldfirex said:
Any ideas outside of trying to wipe the whole thing?
Click to expand...
Click to collapse
See this thread.
Hi Guy,
I got a BIIIGGG problem.
After doing some VERY quick research i decided to get started by rooting and installing VillainROM, which worked lovely...no probs, however because there was a lack of themes (the main reason i rom'd the phone), I was swayed to go for Cynogen.
After downloading CM7.1 and installing through CWM my phone will not boot.
I have tried to do a factory reset through CWM, wipe the cache, and reinstall VillainROM but to no effect and stupidly i didnt backup my data.
Any advice on what i can do or have I bricked my phone?
What does the screen show? Can you get into download mode or recovery? Have you tried flashing the rom twice? This worked for me in the past.
Ricey
yep i can get into recovery and download mode, but when i boot the phone no joy
Ive tried installing the rom several times
Try formatting /data, /cache and /system from CWM recovery before flashing the new ROM.
If that doesn't help flash a stock ROM from Intratech's thread in the dev section via Odin.
1st- Boot into recovery.
2nd- wipe data/factory reset
3rd- wipe cache
4th- go to advanced/ wipe dalvik cache
5th- go to mounts and storage - format/system
6th- go to install ROM from SD card - select the ROM you'd like
7th- reboot system DO NOT TOUCH MAY TAKE A WHILE
8th- let it sit for 10 minutes once its booted so all the cache can build back up
9th- reboot, set up, and enjoy!!
Hope this helps!
Enzopreme you are a legend many thanks indeed
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
Install via ClockworkMod (do not use ROMManager for initial install):
1.Make sure you're running a rooted device.
2.Root your device and install ClockworkMod Recovery (http://forum.xda-developers.com/show....php?t=1118693)
3.Do a Nandroid backup!
4.WIPE (wipe data/factory reset + wipe cache partition) - do it for real.
5.Install the ROM from internal sdcard using ClockworkMod Recovery.
6.Do not reboot! We mean it - do nothing except choose zip and continue next step (if you come back to us with permission issues in install, we will know you did not read the directions and will call you an idiot). If it just plain hangs, reboot directly back into ClockworkMod recovery and continue at the next step.
7.Install the ROM from internal sdcard using ClockworkMod Recovery, again (due to a bug in the install).
8.Reboot
9.Install the Google Addon through ROMManager which is easiest, but you can
download the gapps.zip and install via ClockworkMod recovery instead.
Click to expand...
Click to collapse
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Seconding the question as well as noting that it also occurs with Arif-Ali's nightly compiles.
did you wipe cache and dalvik cache after flashing cm7?
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
No, you dont need.
golcheck said:
did you wipe cache and dalvik cache after flashing cm7?
Click to expand...
Click to collapse
I did. I tried "messing" with CWM any which way and even flashed a stock rom in odin (and appropriate CF root). Nothing short of flashing Siyah (and probably any other kernel that supports CM7 except the one in the update zip) lets CM7 boot.
Net.silb said:
About a month ago I wanted to try out CM7 and see what it's worth.
I went to this thread: http://forum.xda-developers.com/showthread.php?t=1176411
I was using a stock GB ROM and rooted with CF-root kernel.
I downloaded the stable build and followed these instructions:
When My phone booted it got into a bootloop.
I could not boot into recovery, I could only boot into download mode.
I searched the web and on one forum website I saw that someone encountered the same problem and after he encountered the bootloop he booted into download mode and flashed Siyah Kernel via Odin and his phone booted successfully.
I followed what he did and my phone booted into CM7.
After that I went on to other ROMs.
Two days ago I was running CM9 and I wanted to flash to CM7, so I downloaded CM7 nightly build #115 and did the following:
1) My phone was rooted with CWM. (CM9)
2) Wiped data, cache and dalvik.
3) Flashed the ROM twice.
4) Flashed GAPPS.
5) Rebooted.
6) "Samsung Galaxy S II with !" Screen.
7) "Kernel Panic" screen.
8) Took battery out.
*Tried booting into CWM with no success.
9) Booted.
10) Stages 6, 7 & 8.
11) Booted into download mode.
12) Flashed siyah kernel via odin.
13) CM7 working!
So there is my story!
I have also seen other people with the same problem, so it is not just me.
And here are my questions:
1) Why did these problems happen (kernel panic or bootloop)?
2) Why does Siyah Kernel fix these problems?
3) How can I prevent the bootloop/kernel panic from happening in the future (without flashing Siyah)?
Click to expand...
Click to collapse
I fixed it.
This is how:
1. Make a CWM Backup.
2. Use Odin to flash I9100XXKI3, including the PIT (re-partition)
3. Flash this kernel (PDA section) and the old Bootloader (Bootloader section) with Odin.
4. Boot into CWM recovery and flash cm7+gapps.
5. Use Advance Restore in CWM to restore your /data partition if you want to.
I'm 90% certain that the problem was ICS's partition layout (PIT file).
I'm currently getting strange issue while flashing ROM from CWM recovery and in process of finding solution for the same. Meanwhile, I thought it would be better to create a thread so that anyone else who has same issue as me will find it useful or someone who has solution can guide me.
Phone Details
S2 with 32GB Class 4 memory card
Issue Description/Repro Steps
Issue started when I moved from CheckROM v6(GB-Siyah 2.6.1) to I9100DXLP9 (4.0.3).
Steps:
1) Flashed DXLP9 through ODIN(went smoothly), rooted with CF root v5.4 given in http://forum.xda-developers.com/showthread.php?t=1544487 thread.
2) Used Triangle away to reset binary counter
3) Rebooted in recovery, wiped data/cache/dalvik cache, now while wiping dalvik cache I got an error E:unknown volume for path [/sd-ext], but dalvik cache got wiped.
4) Now flashed Foxhound ICS ROM and rebooted.
5) Bootloop
6) Again repeated Steps 1-3
7) Now flashed Hydrogen ICS 4.0.4 and reboored..still bootloop
8) went to download mode, Repeated steps 1-3 again
9) Now, decided to investigate this issue little in detail and noticed that while wiping data partition through CWM was giving this error:
Failed to mount /data/.android_secure
So, this was the culprit, if data partition isn't getting wiped that means CWM is not able to write on it either but ODIN is
10) So, to experiment flashed Hydrogen ICS through CWM -> rebooted phone -> checked that bootloop was still there -> put phone in download mode and Flashed Siyah 3.1.2
11) Voila!!!! phone booted successfully with Hydrogen ICS ROM, also strangely binary counter was not increased
But Step 11 is still a workaround for ROM flashing issue, I still need to flash kernel separately after flashing ROM.
Any suggestions/questions are most welcome
Hoping to resolve this issue soon!!!
Try this:
1 Wipe data, wipe cache, wipe dalvik,
2 Install from sd card in CWM this http://forum.xda-developers.com/showthread.php?t=1363738.
3 Install the rom.
You may have to format /system by going under "mount and storage"
davidsgs23 said:
Try this:
1 Wipe data, wipe cache, wipe dalvik,
2 Install from sd card in CWM this http://forum.xda-developers.com/showthread.php?t=1363738.
3 Install the rom.
Click to expand...
Click to collapse
Hmm..this kernel cleaner seems interesting..will try it out and let you know results
@htmltiger
Tried that already..but no avail. Issue still persists!!!
factory wipe the crap,install stock via odin,,,make things right instead of experimenting.....then come wiv prblm....hope u got tht...
sumitpathak;26165805
[B said:
Issue Description/Repro Steps[/B]
Issue started when I moved from CheckROM v6(GB-Siyah 2.6.1) to I9100DXLP9 (4.0.3).
Steps:
1) Flashed DXLP9 through ODIN(went smoothly), rooted with CF root v5.4 given in http://forum.xda-developers.com/showthread.php?t=1544487 thread.
2) Used Triangle away to reset binary counter
3) Rebooted in recovery, wiped data/cache/dalvik cache, now while wiping dalvik cache I got an error E:unknown volume for path [/sd-ext], but dalvik cache got wiped.
Reflash a CWM and Root Kernel should have been the next step
same problem format cache system and data
.and factory reset
jje
Click to expand...
Click to collapse
@JJ
Already tried those steps..still result is same.
I'm beginning to think that somehow data partition has become corrupt(same like Siyah rc6 issue) and it can only be flashed via ODIN. Still, mystery is how my binary counter is not getting increased when I Flash kernel via odin
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.