I picked up a nice used Samsung Galaxy Tab with no sim card for my wife. The boot screen says it's for AT&T but she just uses it on Wifi and no intention of using it on 3G.
I figured I would upgrade it to ICS, and I thought I was on the right track until I tried to flash CWM 6 from the following Wiki link. Now it's in a loop and says "Connected by AT&T", shows a thin line across the screen, and then reboots.
I used this page for what I did:
Wiki: Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide
Can someone help me out so my wife doesn't kill me?
Before I attempted rooting, I attempted to upgrade with Kies but it told me the device was not compatible. It has Froyo 2.2 installed.
Try to restock using overcome method.
Follow the link in my signature.
Sent from my GT-P1000 using xda app-developers app
What did you install after the (kernel with) recovery? The wiki says the following:
After the kernel is installed, the Samsung stock 2.3 ROM will not boot anymore.
This goes for 2.2 too.
Boot into recovery, and install the zip of the ROM that was copied to memory. That ought to work. If not, like priyana said, restock to Overcome, and try the wiki instructions again.
If you're restocking with the Overcome files, you could just stop after the first part, and install only the stock ROM (JQ1 Gingerbread). Or continue after that and install Overcome, that's a good modified Gingerbread.
I have tried getting into recovery mode, but it just continues looping and rebooting.
What are the correct steps to get into recovery mode?
I have tried Power, Volume Up, Home but nothing works.
Basically, when I power it on, it just loops and I can't get to a point to even start the Overcome or see recovery mode in order to copy anything.
ableeker said:
What did you install after the (kernel with) recovery? The wiki says the following:
After the kernel is installed, the Samsung stock 2.3 ROM will not boot anymore.
Click to expand...
Click to collapse
I was unable to install anything else after the CWM6 flash. That's when it started looping.
Thanks!
You guys saved the day. That "Overcome Experience" pdf was nicely done. It took me a little while to get my bearings in it, but I finally found the section about re-stocking to Gingerbread.
I was able to successfully install the GB version and then I installed the CM9 on the Wiki page I mentioned earlier.
I really appreciate the help and direction you provided. My wife will be happy and I can live another day.
Related
Hi,
I really need some help as I began to get crazy about this.
I also have to mention it's my first time into Root/Mod/Custom/etc...
I Have a GT-I9000M (BELL) with Android 2.2 (version FROYO.UGJK4) Kernel 2.6.32.9
I successfully Rooted the phone with Superoneclic (Have Super User app in menu)
I Installed Rom Manager 3.0.0.0 Then authorized sudo when prompted to do it.
After that in the recovery menu of Rom Manager i've downloaded the Clockworkmod thing. (2.5.1.2)
I've tried to boot into clockworkmod but I got the standard Recovery Boot from Samsung instead. (tried to re-install rom manager to see if work but no)
I also tried to install it by using the update.zip version got here http://www.multiupload.com/5CUIK88JM0 and put it at the root of the internal sd.
Booted into the Samsung Recovery Boot and press apply Update.zip then i got
the following error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborded
(Tried Twice still nothing new)
The goal of all this is to install Darkys_v6.0_Gingerbread_Edition_Voodoo_signed seen here: http://forum.xda-developers.com/showthread.php?t=814091
What do I do wrong???? Help me please i'm tired of the Android Froyo version from Samsung+Bell
To get ClockWorkMod compatibility, you need to use ROM Manager to start them.
This way, Voodoo recognize it's CWM recovery, intercept the call to the update.zip and install Ext4 wrappers.
If the new version is not yet available in ROM, be patient
I found the recovery app doesn't work very well. I suggest installing a kernel with CWM , that's compatible with Bell hardware? via Odin and you're good to go. From recovery menu you can do anything, including a full backup.
Supercurio I Need Help
MOD EDIT: Teranox, our forum rules specifically state that non-engish posts are allowed only if an english translation is provided as well. Please add that here, or the post will be removed
supercurio this one is for you:
What is voodoo
i'm using Rom Manager but notjing seems to work. even OCLF
it's like even if i'm rooted i can't do anything....
can't use lagfix
can't use le clockworkmod
can't use le rom de darky....
you seem enough advance in android to answer me (I saw you post & video on the Nexus S ported to SGS)
Thank you to answer me
You must be in 2e recovery for CWM
Sent from my GT-I9000 using XDA App
jsen said:
You must be in 2e recovery for CWM
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
How to get from 3 to 2e? I'm on JPO 2.2. Thanks
It is not the first time i heard about 2e recovery and cwm
thing is: i'm new to all of this. Can someone explain me what those 2 things mean and do?
Do you mean that i have everything to do it right but there is something i do wrong or forgot?
mirzahodzic said:
How to get from 3 to 2e? I'm on JPO 2.2. Thanks
Click to expand...
Click to collapse
You can find the thread called 'CFroot' at the android development section.
Download the correct version based on your current firmware and follow the instructions there. When you are done, your recovery would be 2e.
Sent from my GT-I9000 using XDA App
My only concern after had read cf-root post is that none of the zip package offer somethong for ugjk4
Teranox said:
My only concern after had read cf-root post is that none of the zip package offer somethong for ugjk4
Click to expand...
Click to collapse
Sorry dude, the only solution would be to flash to an Eclair ROM (which by default has a 2e recovery) or flash Froyo which is supported by CFroot.
I have the same issue as well. Wanted to try Darky's v6.0 rom, however stucked in getting to CWM since I'm on 3e. I did look at CFRoot, but nothing stated for JK4.
Teranox said:
Hi,
I really need some help as I began to get crazy about this.
I also have to mention it's my first time into Root/Mod/Custom/etc...
I Have a GT-I9000M (BELL) with Android 2.2 (version FROYO.UGJK4) Kernel 2.6.32.9
I successfully Rooted the phone with Superoneclic (Have Super User app in menu)
I Installed Rom Manager 3.0.0.0 Then authorized sudo when prompted to do it.
After that in the recovery menu of Rom Manager i've downloaded the Clockworkmod thing. (2.5.1.2)
I've tried to boot into clockworkmod but I got the standard Recovery Boot from Samsung instead. (tried to re-install rom manager to see if work but no)
I also tried to install it by using the update.zip version got here http://www.multiupload.com/5CUIK88JM0 and put it at the root of the internal sd.
Booted into the Samsung Recovery Boot and press apply Update.zip then i got
the following error:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborded
(Tried Twice still nothing new)
The goal of all this is to install Darkys_v6.0_Gingerbread_Edition_Voodoo_signed seen here: http://forum.xda-developers.com/showthread.php?t=814091
What do I do wrong???? Help me please i'm tired of the Android Froyo version from Samsung+Bell
Click to expand...
Click to collapse
This Might Work.... Although I Have A Different Phone (Cdma Hero), But Had A Similar Issue....
The Way I Was Able To Correct My Problem Was To Re-Install A Older Version Of "Rom Manager" (Let Me Know If You Have or Need A Older Version, I Keep'em All Now!! Lol!!
Also In "Rom Manager" I Would Try To Flash Alternate Recovery, And Then Clockwork Recovery Right After!! Make Sure It Says *Current Recovery* -And- *Latest Recovery* (Up At The Top) Then Try To Boot Into Recovery!!
PM Me If You Need More Help!!
Sent from my HERO200 using XDA App
Fresh Start
Ok well I got a good night of sleep so i'll resume where I am
I learned yesterday the following:
CMW: Clockworkmod
OCLF: One Clic Lag Fix
Now what I could try is to get back to Original Firmware of the GT-I9000M (Eclair) and from then what I've understood is that I don't need 2e recovery? Am I right?
From then I could install Darky without anything.
By going back this way will i'll stay root of will I have to root again?
If all this is right, how do i go back to eclair? can it be done via the 3e recovery menu or I have to flash? Is so I don't know anything about odin and the way it work so i'll need your help loll
rafi92 said:
Sorry dude, the only solution would be to flash to an Eclair ROM (which by default has a 2e recovery) or flash Froyo which is supported by CFroot.
Click to expand...
Click to collapse
here's what I did now:
Used Odin and Flashed my firmware to the previous one (2.1 Eclair.UGJH2)
Re-rooted
Re-installed Rom Manager
When in recovery mode i see 2e but it's the recovery from Samsung. Can't see the CWM......
Think i'm pretty close compared to yesterday from Darky 6.0 but STILL NEED CMW lolll
Fist timer Root and Flash never easy lolll
OK GUYS GOOD NEWS!!!!
Don't know what I did but CWM WORK NOW!!!!
What i've read somewhere is to never open the zip files (what i did). Got the idea of flushing them and download it again. This time it worked.
Gonna let you know when running Darky
----!!!!WORKING!!!!----
I Have Darky 6.0 Running on my Bell GT-I9000M!!!!!
First I want to thanx everyone of you who helped me out! You've been a great help.
Also I want to get the summary of my actions so Others could take advantage of this thread.
-Froyo version FROYO.UGJK4 (that is the official GT-I9000M update from BELL Mobility) was painfull to do anything so I downgraded to the eclair.UGJH2 (that is the Original Firmware from Bell)
First I've Rooted my phone using Superoneclic 1.5.5.0 that you can find here:
http://forum.xda-developers.com/showthread.php?t=803682 (enable debuging mode on the phone in Settings-applications-developpement-debuging) then plug the phone and on superoneclic press ROOT...wait and follow indications
Then went to ODIN 1.7 that you can find here
http://www.general-search.com/fileinfo/20192867
You can find the BELL 2.1 firmware
here http://www.multiupload.com/ZNBT2RY5Y0 Password is samsung-firmwares.com
In odin i've used the 512.pit file (place it in the Pit section)
Then placed the 2.1 Firmware in the PDA section.
Took care Repartition, auto-reboot, F.Reset Time check box was check.
Booted in download mode (to get it right with odin i've booted in recovery first: Vol Up+Home+Power when bootscreen appear released it. After Pressed on Reboot now and immediatly pressed Vol DOWN+HOME+Power) I GOT THE BIG YELLOW LOGO OF ANDROID and in ODIN i got the Yellow icon appeared.
At this moment I've pressed START in odin and waited. The phone was acting like when updating through Kies.
When finished I was on ECLAIR
After, I've Re-Rooted the phone with superoneclic again.
Installed Rom Manager
Downloaded the CMW (CLockworkmod) that you can find here:
http://www.multiupload.com/5CUIK88JM0 (DON'T OPEN THIS ZIP BECAUSE IT WILL BREAK THE SIGNATURE NEEDED TO VALIDATE THE FILE)
I've placed the update.zip file (CMW) at the root of the internal SD Card of the phone and rebooted into recovery mode. I went on the apply update.zip (first time it was not working, then second time it worked)
At this moment I was on Android 2.1, Rooted, and CWM Recovery was working.
To Install the Darky's v6.0 Gingerbread Edition, I've downloaded it here:
http://www.multiupload.com/YPQVS4WO9C (ONCE AGAIN DON'T OPEN THE ZIP)
I've placed it at the root of the phone (same place than update.zip)
Opened Rom Manager, and selected Install a Rom from SD Card.
I've selected the zip File and applied it.
Phone went into recovery mode by itself then started installing Darky. (took like 5 minutes but it is said to be between 5-10 minutes so...)
HURRAY I'M ON DARKY CUSTOM ROM!!!!
PS: (at boot screen GT-I9000M will change to GT-I9000), Boot Screen Animation will also change for the Nexus One Boot animation.
Took me a day and half from Noob to This but hope other Bell user (or SGS user) will find their solution here.
Now let me alone I have to play with my new toy lolll
Just got back home. I will follow your footsteps. Do you have 850 mhz band ?
You with Bell ? Any problem making and receiving calls using Darky's rom ?
Followed your steps. Now I'm running Darky's v6.0 rom.
Even if it's a Bell phone, i'm using it on rogers.
I don't have any band problems(yes i have the 850 band). In fact, since i'm on Darky it look like if the wifi and phone antenna is far better. I got reception in places i wasn't before...and can even say GPS lock my position accuratly in less than 10 sec
Everything is.better since darky run on my phone
Sent from my GT-I9000 using XDA App
Hey, can you please clarify the ODIN steps? I have the exact same problem seen here.
I've completed up until where you put the phone in download mode. I set up ODIN as described, then connected my phone via USB, then enetered Download mode - but I only get a yellow icon on the phone, not in ODIN. Have I gone wrong somewhere?
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.
My brother rooted his Captivate 6 months ago or more. He kept the stock ROM, and now would like to try a custom ROM. Unfortunately, he doesn't remember much about what he did. He said he downloaded a program, plugged in his phone, and it rooted him.
I assumed that I should be able to boot into recovery and flash a ROM from there. I looked up how to boot into recovery, and tried the 'hold down vol/up and power on' approach. Instead of a recovery menu, it goes directly to some kind of update screen with this text:
movi-check start..!!
... <lines removed>
install default apk files please wait
I've searched for these lines, and cannot find why this is coming up. I did find that this should have ended with a message that the install finished, but after leaving it for 10 minutes, it seemed to just reboot. Perhaps the message did come up, and then it immediately rebooted.
Does anyone know why the phone is in this state where there is no recovery menu? If I install ROM Manager and flash ClockworkMod is that likely to work and not cause harm?
Need a little more info... is it stock 2.1 or 2.2? If it's Froyo 2.2 then the stock recovery is tricky to get around if you're new to flashing or modding.
jack man said:
Need a little more info... is it stock 2.1 or 2.2? If it's Froyo 2.2 then the stock recovery is tricky to get around if you're new to flashing or modding.
Click to expand...
Click to collapse
Thanks. It is stock 2.2.
I am not new to flashing, and I'm comfortable with adb and other tools. I'm just not familiar with the Samsung Captivate.
Is the screen that comes up with 'movi_check' the stock recovery? it appears to be automatically trying to update something.
Probably just be easier to use Odin to flash stock 2.1 and root and get recovery on it. Then you can flash any (2.2) ROM you want on it, or you could use Odin or Heimdall to flash Gingerbread onto it (recommended). There are tutorials all in the development section.
Sent from my SGH-I897 using XDA App
Reamer09 said:
Probably just be easier to use Odin to flash stock 2.1 and root and get recovery on it. Then you can flash any (2.2) ROM you want on it, or you could use Odin or Heimdall to flash Gingerbread onto it (recommended). There are tutorials all in the development section.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
If its a newer build it wont like 2.1 (alot of newer builds bootloop with 2.1). If your captivate is one of the newer builds and has the 3e recovery here is a guide to get past it.
As to flashing Gb you will need GB bootloaders wich carries risk. Please READ on how too and risk that may happen. Its a small risk but you can hard brick the phone if you mess up bootloaders or if the booloader fails to flash.
Another option is flashing KB1 2.2 froyo and using Desing Gear's Cog 4.x.x kernel. You will have clock work mod. There's a ton of ways to do it most of wich are in the forums already so search and if you have doubts ask
prbassplayer said:
If its a newer build it wont like 2.1 (alot of newer builds bootloop with 2.1). If your captivate is one of the newer builds and has the 3e recovery here is a guide to get past it.
As to flashing Gb you will need GB bootloaders wich carries risk. Please READ on how too and risk that may happen. Its a small risk but you can hard brick the phone if you mess up bootloaders or if the booloader fails to flash.
Another option is flashing KB1 2.2 froyo and using Desing Gear's Cog 4.x.x kernel. You will have clock work mod. There's a ton of ways to do it most of wich are in the forums already so search and if you have doubts ask
Click to expand...
Click to collapse
It crossed my mind that newer builds wouldn't like 2.1, but I wasn't 100%, that's why I recommended going to GB. Just reading the instructions a few times and being prepared the risk is very low to hard brick. Just make sure to know exactly what you're doing when you choose which files for the primary and secondary boot loaders.
But said person is asking info on something as simple as rooting, Hence there are easier less evasive ways to get past 3e.
prbassplayer said:
But said person is asking info on something as simple as rooting, Hence there are easier less evasive ways to get past 3e.
Click to expand...
Click to collapse
Just to clarify, I'm not asking about rooting, but about flashing and the recovery console. I'm an EVO user, and I just don't know the idiosyncrasies of the Captivate.
Am I correct that the messages I get when trying to go to recovery (starting with movi_check start) are normal, and that after those messages I should get the recovery console? If so, it seems to be stuck on the "install default apk files please wait" step, as this doesn't seem to complete.
I do see the steps on how to flash, and can follow them carefully, but since I am not getting the recovery console, I am not sure what might be wrong.
glenwill said:
Just to clarify, I'm not asking about rooting, but about flashing and the recovery console. I'm an EVO user, and I just don't know the idiosyncrasies of the Captivate.
Am I correct that the messages I get when trying to go to recovery (starting with movi_check start) are normal, and that after those messages I should get the recovery console? If so, it seems to be stuck on the "install default apk files please wait" step, as this doesn't seem to complete.
I do see the steps on how to flash, and can follow them carefully, but since I am not getting the recovery console, I am not sure what might be wrong.
Click to expand...
Click to collapse
You can't flash a rom with stock recovery. You need clockwork mod wich can be achieve by using rom manager (needs root) or flashign with Odin a kernel that has it built in
prbassplayer said:
You can't flash a rom with stock recovery. You need clockwork mod wich can be achieve by using rom manager (needs root) or flashign with Odin a kernel that has it built in
Click to expand...
Click to collapse
Thanks for your help. I do understand I can't flash with stock recovery.
Both the 'Read BEFORE flashing' and the 'How to Install a custom ROM' guides instruct to install clockwork mod. I am aware that installing a new recovery needs to be done before flashing on probably any device.
I guess my primary confusion was whether the 'movi_check start' verbage is normal to see when I am trying to go to Recovery before installing Clockwork. Another google search finally found a hit that says it is normal to see this. I'm still not clear whether I should be concerned that it hangs on the "install default apk files" step.
Since it hangs, I don't ever get any kind of recovery menu, so it wasn't obvious to me that I was actually in the stock recovery.
Assuming this doesn't indicate any issues, I'll proceed with the instructions and all should be well.
Well I hope you are able to work it out. ^^
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
Hello all.
I'm trying to update my phone (a rooted Samsung Galaxy S - GTi9000), to Cyanogenmod Nightly build. I have Mobile Odin and Rom Manager installed. And have downloaded the latest Cyanogenmod Nightly.
I have read some tutorials, but I seem to be stuck on two parts:
1) When I try to get into the clockworkmod boot recovery, it doesn't work and boots into the android recovery instead.
2) In mobile odin, when I find my file and load it, it doesn't load anything in the main list that says "kernel, system, dbdata", etc. It just says "none" in all of them.
From looking at some youtube vids at least some of them should load...right?
Now, I may well be doing something simple wrong (hopefully!), but I'm fairly new to all this and its kinda getting to me. Plus, trying to get my head around all the jargon is a bit of a challenge!
If someone would kindly take the time and patience to kindly guide me in the right direction, I would be very, very appreciative! :thumbup:
Also, because of these problems, I haven't tried flashing any roms yet for fear of bricking...
why you dont take cwm via 3 button combo?
there you can add zip and let it install.
Did you read any tutorial? I read about 5h and then i flashed it with problems and i knew what to do. Such questions should be answered in good ones.
Yes, I have tried the 3 button combo. But when I press them it takes me to the stock android boot recovery and not the CWM recovery.
I have Rom Manager installed, shouldn't this give me CWM recovery, or am I going about this wrong?
KieranY8 said:
Yes, I have tried the 3 button combo. But when I press them it takes me to the stock android boot recovery and not the CWM recovery.
I have Rom Manager installed, shouldn't this give me CWM recovery, or am I going about this wrong?
Click to expand...
Click to collapse
Flash a semaphore GB kernel to solve your problem from My Android Collections
Got it sorted guys.
Thankfully it was a simple fix. I removed the battery briefly earlier, but nothing happened. Took it out for a good 30-40 seconds and it finally booted into CWM Recovery!
I'm now on ICS.
Thanks a million for trying to help me.
The learning curve is beginning to flatten out!
:thumbup:
Try To reFlash
I Think that it would be best to flash the 3 odin files on again