Recovery menu issue with GT-I9000M - Galaxy S I9000 Q&A, Help & Troubleshooting

Hey guys, I'm fairly new to Android, and even smart phones in general, but I need a bit of assistance.
I bought a phone from a friend in Canada, the GT-I9000M.
I live in Australia, and I'm trying to unlock it to work here. I wasn't having much success with getting root of the phone etc, so I decided to have a look at cyanogenmod.
I have followed this wikipedia article by every character: wiki.cyanogenmod[dot]com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
However, the phone acts a bit odd. It'll boot up, show the cyanogenmod splash screen, then load to a recovery menu, but then the text will fly up very fast, and the phone just reboots itself in an endless loop. I managed to get a photo of the menu before it rebooted itself, and found this (Link to an external image, since I can't post them yet):
dl.dropbox[dot]com/u/203420/DSCF2542.jpg
And this is where I'm stuck. I have the cyanogenmod update zip on the SD card, but it seems to give a "SD card marker not found", and resort to looking on the phones internal memory (Which obviously fails).
I've tried a few other things, like flashing the boot.img file instead of the zImage (Which actually gets me further than just the zImage, which sits in the galaxy S splash screen).
Any help would be greatly appreciated
Regards,
Dan

Have you tried reflashing the phone with the KG3 firmware?

Have you tried reflashing the phone with the KG3 firmware?
Click to expand...
Click to collapse
same problem here... CyanogenMod wiki articles have instructions for I9000 and the T959, but not the I9000M. I'm looking for a kernel zImage with CWM recovery for the I9000M.
As for the KG3, I've found a 3-files version, but couldn't manage to flash it with Heimdall...

This is not bad, I had this when trying to boot one of my ports.
To fix:
1. Flash custom kernel through Odin (devil, semaphore for example)
2. Now directly boot into recovery, which should now be cwm.
3. Flash desired ROM and wipe data/factory reset, clear dalvik, cache etc.
4. Boot up!
Sent from my GT-I9000 using xda premium

Related

[Q] Stuck in CWM recovery after Doc ROM install, help?

First of all I hope this is in the right place: I did do a search but still couldn't find any help.
Here's my problem:
After getting a (delicious) taste for customisation after rooting and lagfixing, I decided to give custom ROMs a go. Hours of indecision passed and ultimately I settled on Doc and Stefunel's magical ROM. Due to currently being on 2.1, I chose to follow the set of instructions provided on the page for doing so.
All was well up until the very final step. When rebooting the phone through ClockworkMod Recovery, instead passing the Samsung boot screen into the Android system, the phone boots into CWM recovery. I've tried doing another factory reset, and reinstalling the ROM to no avail. I've also tried mounting "/mnt/sdcard" in order to place another ROM to flash from, but I keep getting a message telling me to insert a disk (what happens when you don't mount).
That's pretty much all there is to it. I'd be massively grateful for any help!
-anti
If you have made a backup of your apps then flash the JPY with Odin and then make factory reset in recovery mode. Then root with CF Root 1.3 (Or something like that) and flash CWM Recovery. That's what I would do.
Sent from my GT-I9000 using XDA App
from the recovery menu try wipe cache and dalvik, and reboot

Trying to load a custom rom, wth am i doing wrong?

Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
First thing i would recommend is : uninstall rom manager. It causes more problems. If you did a search on these forums you would find loads more tales of woe re rom manager.
Second thing is: have look through the dev section, at the instructions for installing clockwork recovery. Then look for the appropriate rom for your device.
But whatever you do, uninstall rom manager
Sent from my thingymajig
Isn't ROM manager ClockworkMod?
I searched Clockworkmod on the market and when installed the icon says ROM Manager though...
o2sys said:
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
Click to expand...
Click to collapse
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
TheATHEiST said:
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
Click to expand...
Click to collapse
i did following the tutorials, its how I went that far to begin with. Sorry for being a newb and maybe not fully understanding it thats why I am asking for help, not to spoon feed me...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
o2sys said:
...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
Click to expand...
Click to collapse
Have you tried booting into CW Recovery manually and running the KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip (like the instructions say)?
Your thread header says you are using ROM Manager and trying to run the update.zip package.
ROM Manager _should_ work, but maybe stick with instructions especially if you're having issues.
Yes I have tried going into Recovery manually as I stated in my original post.
I always flashed with SGS kernel flasher as it seemed to work well.
Then I tried manually going to Recovery w/o CWM and gets stuck at boot screen as well.
I tried WITH CWM and same stuck at boot screen.
Tried wiping data through Recovery, through the UI (Settings then ect, ect) and several other combos trying to load the custom ROM.
All I am successul is at rooting, then flashing the kernel. Then no matter which step I tried if i reboot it will get stuck at the SAMSUNG boot screen.
Even if I just turn it off and then turn it back on, after the flash, it will get stuck at the boot screen.
I downloaded the kernal flash directly from the link of the first page. And if the kernal file was courrupt i don't think the flash would go successfully.
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Sorry to hear you are having problems. I am also sorry for the rudeness on this forum. Although I seldom post I read it daily. Here is what I would try;
1. The issue may be with the file name update.zip if you can, rename it to anythingyoulike.zip on you computer and then copy it to your SD card. You may even have to take the card out of your tab to do this (delete the update.zip once the file is renamed). Once the renamed file is on the SD card try to reflash.
2. Have you tried to start again using Odin? There is a good clip on you tube about this. As long as the tab at least starts to boot it is not bricked. Feel free to PM me for any additional help.
Good luck.
tigercorp said:
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Click to expand...
Click to collapse
When I use SGS to flash, it reboots and i can see in settings that it has been flashed.
If I use Heimdall, it flashes then gets stuck at the boot screen.

Download/Recovery Mode ok, BUT cannot bootup

I was running on froyo before I started process, and now I cannot boot up. This is what I did:
First I used the step 1 in the cyanogenmod wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide) to install the ClockworkMod Recovery, everything is fine, until the final reboot step. after the ATT screen, the screen get into total unrecognized mode, and the unit will restart, and so on and on, in a loop.
Then I tried to use the speedmod-K13E with GB bootloader one click, and I still can't get into the system, but now it just stuck at the Galaxy S samsung screen, after the ATT screen, and no loop, just stuck.
Any suggesstions? Is there a stock rom I can restore back to using the external sd card? the internal sd card currently only has the cyanogenmod 9 on it. I have going through the different posts for the past two days, got really confused. If someone can point me to a step by step guide, or something similiar, really appericiated.
BTW, the recovery mode has the following:"ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK
I'm on windows 7 32bit. And I donot need to save any data on the phone. It can be wipe clean.
Did u try rebooting into cwm recovery and try to re install the rom again ?
U may need GB bootloaders as well for cm 9 (?? I'm not sure though)
Sent from my SAMSUNG-SGH-I777 using xda premium
If you still want to run cm9 try flashing a more recent kernel inn recovery. look in the Dev section for glitch kernel or devil kernel (i like devil) they have a more recent version of cwm that should work. I haven't used this method with cm9 but it worked with aokp.
Sent from phone with app
well.. my advice is try reflashing to the stock rom using the one click in this thread [Stock ROMs](OneClicks Master Collection)+[Kernels (Stock & w/ CWM)]+[Modems] UPDATED
(kk4 reccomended)
download one of the odin one click there, and flash your rom back to stock gingerbread, oh yeah, choose the rom without the bootloader.
if that doesn't get you anywhere, please reply to my post.
lan_baba said:
I was running on froyo before I started process, and now I cannot boot up. This is what I did:
First I used the step 1 in the cyanogenmod wiki (http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide) to install the ClockworkMod Recovery, everything is fine, until the final reboot step. after the ATT screen, the screen get into total unrecognized mode, and the unit will restart, and so on and on, in a loop.
Then I tried to use the speedmod-K13E with GB bootloader one click, and I still can't get into the system, but now it just stuck at the Galaxy S samsung screen, after the ATT screen, and no loop, just stuck.
Any suggesstions? Is there a stock rom I can restore back to using the external sd card? the internal sd card currently only has the cyanogenmod 9 on it. I have going through the different posts for the past two days, got really confused. If someone can point me to a step by step guide, or something similiar, really appericiated.
BTW, the recovery mode has the following:"ClockworkMod Recovery v2.5.1.0 SpeedMod ULFK
I'm on windows 7 32bit. And I donot need to save any data on the phone. It can be wipe clean.
Click to expand...
Click to collapse
You should be good to go. You should be on GB bootloaders. Just reflash CM9 in CWM.
Solved.
For some unknown reason, I can net get ODIN to communication with my device, I tried multiple device, and it seems ODIN just does not work.
I used the 3rd post in your link, with Heimdall I successfully installed the KK4 and then I used the cyanogenmod wiki again, this times it works. It seems the old stock rom won't work for the wiki, must use the new stock rom.
Thanks for all the helps, guys.
irfarf said:
well.. my advice is try reflashing to the stock rom using the one click in this thread [Stock ROMs](OneClicks Master Collection)+[Kernels (Stock & w/ CWM)]+[Modems] UPDATED
(kk4 reccomended)
download one of the odin one click there, and flash your rom back to stock gingerbread, oh yeah, choose the rom without the bootloader.
if that doesn't get you anywhere, please reply to my post.
Click to expand...
Click to collapse
lan_baba said:
Solved.
For some unknown reason, I can net get ODIN to communication with my device, I tried multiple device, and it seems ODIN just does not work.
I used the 3rd post in your link, with Heimdall I successfully installed the KK4 and then I used the cyanogenmod wiki again, this times it works. It seems the old stock rom won't work for the wiki, must use the new stock rom.
Thanks for all the helps, guys.
Click to expand...
Click to collapse
you're welcome,
glad i can help

[Q] (Yet Another) Boot Loop Problem in Installing CM7 on GalaxyS I9000 [SOLVED]

YABLP (Yet Another Boot Loop Problem)
Hi,
I'm having a devil of a time installing CM7 on my GalaxyS I9000. Description of my procedure and problem below.
I've been beating my head against a wall for a week so any help GREATLY appreciated.
-John
Phone: Galaxy S "I9000"
Trying to Flash: CM7.2.0 using CWM Recovery
What I did:
Flash stock ROM w/ODIN v1.85 - OK
Wipe Data/Wipe Cache
Flash ChainFire (CF-Root-XX_OVA_JVU_2.3.6-v4.3-XWM3RFS.tar) w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.2.0-galaxysmtd.zip from CM site)
Flash completes in just a few seconds - much too quick!
Phone reboots automatically
Now stuck in boot loop
Screens in boot loop:
1. GalaxyS/GTI9000/Samsung
2. GalaxyS/Cyanogen(mod)
3. CWM menu scrolls by too quickly to read
Back to 1.
Tried Heimdall but complained about missing XML file
Tried installing "Datafix". Would not install (says not compatible with device)
Tried STFW: many reports of same problem but no solutions seemed relevant & appropriate
Clues:
After CF flash, disk use as follows
/system: used 27.3M, free 9.4M (97%) (seems pretty full)
/data: used 47M, free 1916M (2%) (seems pretty empty)
Me thinks maybe /system is too small/full to accept update?
This is the 3rd I9000 I've flashed. First 2 went Ok but this time it failed although identical files/procedures used (I think).
HELP!
I've seen a similar problem on my I9000 - I think the CWM scroll complains about "can't mount /data".
I'm in a similar position, I can't get anything to flash and boot though : http://forum.xda-developers.com/showthread.php?t=1967982
This happens pretty much every time you flash any kind of CM rom from stock. All you need to do is flash CM7, it will go in to bootloop with various text scrolling through thats too fast to read. You just pull battery while in the bootloop. Then replace battery, three button combo to recovery and flash the same CM7 zip again. This time the install will take a while longer. Afterwards flash gapps and reboot and you should be good to go.
I tried this - but same result, just spins round on the CM boot screen
Where do the wipe data and wipe cache commands fit in to this? Before/after both installs?
I don't normally bother with gapps - just trying to get it loaded. Does that make a difference?
Also, no SIM card in at all during all this...
IT WORKED!
Bless you BandiBp!
I'll be sending my first-born by return mail (please don't tell my wife
Yeah that happens because its flashes a kernel with a new partition system. Dunno why only a few roms warn people about this.
Sent from my GT-I9000 using xda premium
You're welcome mate, yeah the reasons are the new partition changes on different roms. I agree that rom flashers should be warned in advance about this. Would reduce problems A LOT. My general rule is if a Rom installs in under 5 secs, then you should always flash again.
Anyways have fun.

[Q] Bad ODIN Flash on i957 - Stuck at AT&T Splash Screen

This happened on an i957. There's a sub-forum for that device, but it's a development sub-forum; wasn't sure which place to post this.
The short of it:
I ODIN flashed a TAR for the official UCLK4 firmware for my i957, but I dropped the TAR in ODIN's PHONE slot instead of its PDA slot. Upon rebooting, my tablet now freezes at the AT&T's Rethink Possible splash screen.
I re-flashed the UCLK4 firmware in ODIN's (proper) PDA slot after I realized my mistake (after doing some research in the i957 sub-forum), but I'm still stuck at the AT&T logo.
Anyone have any recommendations?
The longer version:
I've been running AOKP (JB) on my i957 for a few weeks. It's a huge improvement over Samsung's Honeycomb ROM... but I was only-ever able to get HSPA+ working; was never able to get LTE. Today I saw that Samsung finally released the an ICS ROM for the i957. I wanted to try it out, but I wasn't able to "update" AOKP to UCLK4 using Kies.
I found the flashable TAR for UCLK4 on SamMobile.com, so I downloaded it and followed a walk-thru (on another site) that said to drop the TAR in ODIN's Phone slot. (It seemed weird, but I didn't question it.) I flashed the firmware in ODIN's Phone slot, rebooted, and got stuck on AT&T's Rethink Possible splash screen.
It didn't take long to realize I was following bad advice, and that I should have flashed with ODIN's PDA slot, so I...
Flashed UCLK4 in ODIN's PDA slot. I still had the same problem. I could never get past the AT&T Rethink Possible splash screen.
I tried to re-flash the stock kernel on top of UCLK4, following the instructions here, but that resulted in my tablet hanging after the Samsung boot logo, but before the AT&T splash screen.
I re-flashed UCLK4, and now I'm back to the Rethink Possible splash screen.
I'm still able to get into Download mode, so I don't think I'm bricked... but I'm not sure what I need to do. (Maybe I can use ODIN to reflash a proper PHONE file? Can anyone help me produce this file?) Does anyone have any recommendations?
Same problem. Thought I'd give the official I957 ROM a try, Kies won't work, and when I flashed with Odin, I got stuck at the AT&T splash screen. I did not make the mistake with the PDA / PHONE file on the first run. I did try to flash again with Odin, no change.
The tar file should have included a kernel; a new kernel version is part of the HC -> ICS upgrade process. And the kernel from that other post is probably an HC kernel, which won't work with the stock ICS ROM.
I had the same problem I installed twrp recovery and wiped everything, factory reset, etc then installed ics with Odin and it worked fine after that.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Thanks!
I didn't even have to do the re-install. I rebooted into the stock recovery (power + volume up) and wiped cache and did a factory reset. Came right up into the setup screen.
Great! That would have taken less steps. But whatever way you do it it seems the factory reset is necessary.
Sent from my SGH-I727 using xda app-developers app
i installed the HC stock then flashed this and it worked. i also had the hangup problem but that fixed it.
jd1639 said:
I had the same problem I installed twrp recovery and wiped everything, factory reset, etc then installed ics with Odin and it worked fine after that.
Click to expand...
Click to collapse
Thanks! I did a factory reset and wiped my cache and everything is working now. I feel a little ridiculous for not trying that on my own...
In the panic of the moment, I (somehow) just assumed that recovery wouldn't work. One should never assume that!
Thanks
Thanks a lot! I did a factory reset and wiped out my cache and everything is working fine now. :good:

Categories

Resources