I was on Slim ICS and downloaded an update (2.8) which was to include a wifi toggle fix. After downloading directly to my phone, I tried to install it and it started looping (kernel then into recovery). I could not stop it in recovery. It would loop through the boot up and then I could see the recovery and but it said something about not being able to read zip file (corrupted download?). It just kept looping.
I was able to get Odin to work once (that is why I get the AT&T screen). Now, I can get Odin to recognize my phone but I cannot get beyond that. I have tried to reflash kernels that have worked before (assuming that I needed to start over). But Odin just sits there with the tar file in the pda section (for well over five minutes). Working on a Windows 7 machine (64-bit).
My phone's current status is that it is frozen at the AT&T screen (from the boog kernel without bootloaders - since I was on gingerbread before). I can get into download (volume buttons, plug in USB).
FYI, in the past I had flashed Continuum, Andromeda3, Mosaic IX, Fusion ICS, and Slim ICS, without a problem other than a soft brick or two that I was able to fix using Heimdall. (I am realizing I know/knew enough to be dangerous)
Am I "bricked" or can it be repaired.
Any direction as to what to do right now would be greatly appreciated.
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Red_81 said:
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Click to expand...
Click to collapse
I will try it again but I did try once with Odin and after about ten minutes, I cancelled the process (hopefully that did not add to my problems). It seemed to be hung up on the message, "Do Not Turn Target Off," but there was no process started.
Try a heimdall one click then. It might solve the issue.
Red_81 said:
Try a heimdall one click then. It might solve the issue.
Click to expand...
Click to collapse
Red_81,
Thank you!
Heimdall worked (http://forum.xda-developers.com/showthread.php?t=1300843)! Although I loaded the version that contains bootloaders, it actually flashes the kernel first and then give you the opportunity to flash again installing the bootloaders. Since the phone worked after the first flash, I did not bother doing a second flash. Now, back to Slim ICS!
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Red_81 said:
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Click to expand...
Click to collapse
Heimdall worked but I was left with two problems. One was that the Kernel installed by Heimdall did not have CWM in it, which I need to flash Slim ICS.
The second problem is that my computer will not recognize my device when I try to use Odin since Heimdall installs different drivers (I have read about how to covert to Odin and/or uninstall/replace the drivers, but it is hard to find that time given family and job obligations).
Since Heimdall did work to fix my original problem work, I found a package to install Apex 12.4 (http://apex.merseine.us/installation/) on my phone. I did this so I can have a working copy of CWM in order to re-flash Slim ICS.
Given the travails of the last two days, I may wait a battery charge or two on Apex (lots of customization but higher battery drain, which is why I went from Fusion ICS to Slim in the first place).
Anyway, thanks again for your help.
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Red_81 said:
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Click to expand...
Click to collapse
Believe me, I tried seven ports on three different computers with two different cords (my Kindle cord is actually the most dependable ).
I then searched for a Heimdall package that had CWM. It has a Talon kernel with CWM 3.0.x and I can get into recovery with the option of installing from my internal sd card.
I just have to wait for my nerves to settle (and this is a very fash gb rom and I have had no issues yet).
Related
My Captivate is only about a week old. After getting it, I immediately rooted it and installed stock Froyo, but wasn't satisfied with the battery life or performance. So I installed Darky's 7.5 ROM (nowipe version using the 'wipe data + cache' option in CWM) along with the glitterball kernel and JL3 modem. Performance and stability were excellent, but battery life was abysmal, even with no apps running and the CPU capped between 100MHz and 800MHz using SetCPU (which is plenty fast on this ROM). I'm talking about 10-15% drain per hour while on standby, packet data, wifi, bluetooth, GPS, and sync all off.
I attempted to flash back to stock to try other ROM's, but Odin one-click simply bricked my phone to the point where I needed a hardware jig. After much work, I was able to flash Cognition using the regular Odin and then use CWM to restore my phone back to the Darky's ROM state with all my data and apps intact. Battery life is still terrible though. I've tried several methods to revert my phone to a stock kernel, including Odin one-click, Odin with 3-button fix, and regular Odin loading various stock ROM PDA and PIT files.
The furthest I was able to get was a phone with a working recovery menu that gave me 'Kernel Panic' right after the AT&T logo. Otherwise, the phone would be completely bricked (no button combinations) and I'd have to reset it using the jig. However, flashing a custom ROM that *doesn't* require reverting to stock first (Odin-flashable), or restoring a backup from CWM works just fine every time, no matter how badly I brick the phone. It's just stock ROM's and kernels that I can't get to boot or install properly.
I'm running out of ideas, because this battery drain is unacceptable and my ROM choices are severely limited. I did try flashing some ROM's over Darky's (JPY) without the revert-to-stock step, but I always get weird problems like missing phone, message and contacts apps.
I would really appreciate it if someone could help me out.
You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App
mcord11758 said:
You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I have re-downloaded both Odin and the files to flash multiple times, confirmed by the '(1)' tacked onto the filenames in my download folders. My procedure:
1. Extract Odin and PIT file (if flashing with a PIT).
2. Run Odin as Administrator, select PDA tar/md5 file (and PIT file if applicable). Untick 'Auto Reboot'.
3. Put phone into download mode using volume button combo (or hardware jig if Odin already bricked my phone).
4. Plug phone in. Phone recognized immediately by Windows and Odin.
5. Click start in Odin. Procedure always completes successfully.
6. Battery pull and unplug phone. Put battery back in and turn phone on. If flashing a stock ROM, phone either gets kernel panic, or is bricked and all button combos are disabled.
The files I used for stock flashing were found in the Odin one-click + master clear thread and the Odin one-click button combo fix thread (which uses a PIT and PDA file). I used Odin 3 v1.0 when flashing PDA files (had no problems flashing cognition ROM or non-stock kernels).
For the one-click versions, I followed the above procedure (minus the selection of PDA/PIT files). One-click always bricks, regular Odin will either brick or cause kernel panic when flashing a stock ROM or kernel, depending on PDA/PIT files and the previous state of the phone.
When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App
mcord11758 said:
When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.
GGXtreme said:
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.
Click to expand...
Click to collapse
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App
mcord11758 said:
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm on AT&T. Odin files I've tried include:
Odin3 v1.3.exe (bundled with Odin3.ini and s1_odin_20100803.pit)
Odin3_v1.0.exe (bundled with PIT.pit and used with PDA.tar)
Odin.exe (bundled with PIT.pit and PDA.tar for Cognition)
I897UCJF6-final-OCD-REV0.exe
All of the Odin executables (with the exception of the one-click) work fine flashing Cognition and I9000_reoriented_v2.3.0.tar (xcalib kernel), but not with the included PDA.tar files. When I say 'work fine', I mean flash the phone into a workable, non-bricked state, since Odin never throws me any errors or failures.
*bump*
Is this hopeless? I've asked about this elsewhere, and no one seems to have any suggestions. My phone has been up and running fine on multiple different custom ROM's and kernels, but it still bugs me that I can't flash back to stock if needed. Also, any suggestions on improving battery life are very welcome.
After searching around for a bit, it seems that Captivates from batches 1008 to 1010 cannot be flashed back to JF6 using any version of Odin. The closest that can be achieved is JH3 using Odin 1.7. This is pretty disappointing.
Oh well, I guess I have no luck with technology. Unless anyone feels like throwing battery life suggestions at me, this thread can be closed/deleted I guess.
The battery probably just needs calibrating.
There are.multiple threads in the forum on this and I would be happy to point.you to them, bit.I am on the phone app and its a little more.difficult to do so.
Sent from my GT-I9000 using XDA App
Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe
http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.
cappysw10 said:
Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe
Click to expand...
Click to collapse
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
avgjoegeek said:
http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.
Click to expand...
Click to collapse
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.
GGXtreme said:
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.
Click to expand...
Click to collapse
intriguing the somewhat random button combo issues on some newer builds of phone
newter55 said:
intriguing the somewhat random button combo issues on some newer builds of phone
Click to expand...
Click to collapse
I can't remember if it did, but I think the actual issue is that my phone came with JH7 (not JF6) and is actually incapable of running older firmware due to some difference in the hardware/build. That's why flashing stock JH7 seems to work fine.
This is how the story goes, bear with me.
I had an ATT Captivate 1012 running on S7 but it was rebooting on me during phone calls. I decided to go back to stock with odin oneclick as I had read it works with 1012s but the process hung. I managed to recover and flashed back to stock JH2 with the non-one-click version.
I followed this guide by Breakin' Ranh
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I had used it successfully to get to stock before many times.
This is where I think I screwed up, please correct me if im wrong.
I thought that taking me back to JH2 would restore my bootloaders and allow me to install the 3buttonFix.zip via CWM over stock JH2, but after installing that zip my phone didnt boot up since.
The 3ButtonFix.zip I used was from this thread http://forum.xda-developers.com/showthread.php?t=1134443 . Via CWM, not Odin.
My battery was not at 100% (checked with a friend's phone and it was at about 24% so I'm not sure if that was the issue.
The question is, wouldnt have flashing to JH2 wipe out the bootloaders S7 installed (i9000 GB loaders if im correct)
I can only think of few things and would appreciate, if possible, your thoughts about these, all in an effort to learn more about the process and to reduce my chances of hardbricking again (Got a new captivate, 1010 this time)
1) JH2 bootloaders are clearly not compatible with that 3ButtonFix.zip because it perhaps assumes an underlying JF6 base? I was on JH2 when i flashed the 3ButtonFix.zip linked above
For future reference, should i then go JH2->JH7
This is the JH7 i have used before the 'accident'
(it is linked in the thread above)
I897UCJH7 Firmware
http://www.ponack.net/designgears/JH7_OTA.zip
2) The JH2 .tar provided in that thread did not /*correctly*/ install all? captivate bootloaders?
3) The flash to stock with the above guide didnt clear out my bootloaders successfully. The first time i tried to flash with odin oneclick it failed so i had to start over with the non-oneclick, that's how i managed to successfully get into JH2.
4) Perhaps flashing with a low battery (30% or so) ruined the install of 3buttonFix.zip?
Maybe I botched my flash via odin only to ruin it further with 3buttonFix.zip via CWM.
Would you recommend heimdall for all my (new) flashing endeavours? I _reaally_ don't want to go through the jtagging/phone replacement experience again.
Would have flashing the Odin version of 3buttonFix have prevented this? or maybe using heimdall to get back to stock?
What do you recommend i do to avoid these problems in the future? Stay away from 3ButtonFix.zip and just use a usb jig (finally got one *AFTER* hardbricking).
TL;DR
I read on the forums that people have bricked by ruining their sbl.bin by coming from a gb bootloader. But I was under the impression (apparently incorrect) that flashing to stock (Any stock froyo/eclair?) would prevent such issues. What do you think went wrong?
Sorry for the 20 questions :|
Thanks!
-XercesBlue
That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Did you even try the button combos BEFORE you flashed the fix? You shouldn't have needed it at all...
Just forget that the 3 button "fix" even exists.
studacris said:
That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Click to expand...
Click to collapse
Thank you for your reply studacris.
So the I897UCJH2.tar package I linked to does not contain bootloaders? If so this makes muuuuch more sense now. Should I find a package that contains those "stock" bootloaders to restore the phone into a stock state then ?
Will the packages linked at the bottom of this thread work then?
http://forum.xda-developers.com/showthread.php?t=731989
The "The internal beta's are NOT one-click, please read the linked threads
UPDATE: I897UCJH2 (Internal BETA)" ?
Do you have any ideas how that one is different from the I897UCJH2.tar I flashed following Breakin' Rahn's. If you follow the link you will see they link to the same files I had used during my first hardbrick.
Reading some more I stumbled upon your old reply,
http://forum.xda-developers.com/showpost.php?p=13581072&postcount=1798
So, If i get this right and to reiterate
For 1010s to get back to stock+bootloaders
1) OneClick (http://forum.xda-developers.com/showthread.php?t=731989)
OR
Use the internal betas "I897UCJH2 (Internal BETA)" linked at the bottom of the same thread ??
2) Do this http://forum.xda-developers.com/showthread.php?t=995143
If you run into a bootloop
OR this
http://forum.xda-developers.com/showthread.php?t=963403
?
I hope you understand how I can be a bit confused here.
I had no luck previously with OneClick on my 1012. Maybe the 1010 is different but i doubt it. The process hung at some point and had to start over with Breakin'Rahn's guide. Finally got to stock by perhaps without bootloaders.
---
As for the combos, when on s7 the combos worked. Volume down+power worked as expected for dl mode volume up + power for recovery. Upon flashing the new package I lost them leading me to assume incorrectly I was at a new factory mode.
The power down, remove battery, hold power, put battery, plug usb did not work either when on JH2. Of course, me being new at this I might have missed something.
only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.
studacris said:
only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.
Click to expand...
Click to collapse
Great, thank you for taking the time to read/reply!
Yes, I am definitely staying away from 3buttonfix.
XercesBlue said:
Yes, I am definitely staying away from 3buttonfix.
Click to expand...
Click to collapse
BUT, Im on a 1010 and the vol up + vol down and power buttons wont get me into recovery.
What method should I use to get into recovery?
If you have the gingerbread bootloaders the combo will work. The combo is in the secondary bootloader...
Similar to Masterslackers issue.
The phone was originally a stock Optus Éclair 2.1. About 6 months ago I decided to customize the i9000 with a custom Froyo 2.2.1 Rom (Doc's Rom Docs_XWJS3_Wipe-v9_1) from “The ROM Kitchen”. It worked really well and was much faster and responsive..
Yesterday, I decided to look at a move to Gingerbread and cook another ROM @ the ROM Kitchen, this time a Gingerbread 2.3.4 iteration.
The phone was rooted so I used Rom Manager to get into recovery mode where I could flash my new, Doc's JVR_No_Wipe-v8-00-08-22-10-09-4e6a8e4e86718.zip Rom.
All seemed to go well, but after the Flash, as the phone booted the first screen became filled with 100s of random coloured lines, then it transitioned to the normal Samsung start animation, but soundless.
After booting, I noticed that I no longer had a notification bar where battery, time, signal strength etc. was normally displayed atop the screen. I tried several different launchers to see if that was the issue, but to no avail. I tried to enable the notification bar using Go Launchers gesture setting (no go)
I tried rebooting the phone over and over, the notification bar would not return.
I was starting to lament my decision to flash when the following occurred.
I tried to re-enter recovery mode via ROM Manager to install a different ROM, but the phone bypassed it and then hung @ the Samsung I9000 logo screen. I then had to power the phone off before it would reboot into its UI. I could no longer reach recovery mode by any means.
Because I was getting nowhere and I had read that after flashing a new rom, root would often be lost, so I tried rerooting with "XXJVP-Complete-Rooting-Package" from
http://androidadvices.com/how-to-root-galaxy-s-on-android-2-3-4-xxjvp-firmware/ This also failed but it has also left me with a soft bricked phone.
The phone will not boot up or boot into recovery now, however It would still boot into (3 button) download mode.
I have tried various versions of Odin from v1.0 to v4.28 to ReFlash the phone back to life but with no success yet.
Using Odin, the phone hangs with no sign of progress and reports the following when left for 30minutes or so.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
Anyone have any suggestions that might help to get the phone back.
Thanks, TeZ
So you didn't flash stock gingerbread before flashing custom rom? so you should first flash stock jvr and do hard reset after booting. Then you are safe to flash cwm capable kernel and custom rom.
For the odin problems, maybe you have kies running in background? Kill all kies processes and try again.
And I'd suggest reading all guides found in romkitchen thread..it saves lots of trouble. Hope that can fix your phone
Sent from my GT-I9000 using xda premium
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Thanks for that, I did install kies after I bricked it, in the hope (probably missguided) that it would somehow help. Uninstalling
bigmadpete said:
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
Click to expand...
Click to collapse
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Your post looks promising, I'm going to try this method out and see where it leads. I'll reply back with the outcome, many thanks
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
bigmadpete said:
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
Click to expand...
Click to collapse
Thanks for the info, running out of time today, will try for tomorrow
When moving from a froyo (2.2) rom to gingerbread, (2.3), you need the gingerbread bootloaders or you'll get all sorts of crap when turning on your phone (ie what you have).
Use odin to flash back to froyo, or flash a gingerbread firmware that comes with bootloaders. (I would recommend going back to froyo first to make sure everything is ok, since flashing bootloaders is a bit risky, as messing it up can permanently brick your phone)
cobrasixtysix said:
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
Click to expand...
Click to collapse
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Ok, here's where I'm at:
For the sake of simplicity I will detail what gave positive results rather than a tirade of what didn't.
Uninstalled Kies, rebooted
As instructed, went to:
http://forum.xda-developers.com/showthread.php?t=1102881
downloaded: Odin v1.82
downloaded: Gingerbread 2.3.3 (Australia and New Zealand)
XWJVN/XXJVQ/XSAJV5/Sbl (CSC: XSA): Download (150 MB) (Build date: Sun Jul 10 11:30:54 KST 2011)
Loaded up Odin and followed instructions.
Flash went ahead as normal and I now have a working phone again, thanks to you DSGE, I'm a very happy man
So I now have Gingerbread 2.3.3 installed and running.
My only issue's now is, that.
1. Half my apps dont work now or force close even after a reinstall.
2. Some apps won't install at all IE; my fav launcher; Go Launcher
3. I no longer have root access so Rom Manager and Titanium backup wont work.
4. My Backup Pro, works after I rewrote the correct path to the External Sd, but do I want to do that just yet? and just how much data should I reinstate so I don't corrupt the new system?
What should I do now?
Install busybox?
do a hard reset?
Flash a different Rom that will work for me?
Thanks so very much for all the good advise.
Cheers
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
bigmadpete said:
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
Click to expand...
Click to collapse
OK, latest update:
Everything is working fine including all my progs.
Like you say, I just need to root it now.
Can you point me to the correct files to root?
Thanks
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
bigmadpete said:
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
Click to expand...
Click to collapse
Seems to relate to 2.1 to 2.2.1 didn't see any mention of 2.3.3. I'm afraid I'll stuff the phone if I use the old root files.
In normal running mode ODIN sees the Cappy, but when I switch to download mode it doesn't see it any more. I am trying to put my phone back to factory default so I can install CM7 but running into all kinds of problems. I did get the base system reinstalled using a One Click JAR that I found here on XDA. The phone seems to be ok with that.
ADB doesnt think there are any devices attached either when I am in download mode.
I did also try the Heimdall install methods and used their drivers, but that doesnt work either
All I am trying to do so far is get CWM installed
Any ideas?
Did you ever use Heimdall?
MarkWorsnop said:
In normal running mode ODIN sees the Cappy, but when I switch to download mode it doesn't see it any more. I am trying to put my phone back to factory default so I can install CM7 but running into all kinds of problems. I did get the base system reinstalled using a One Click JAR that I found here on XDA. The phone seems to be ok with that.
ADB doesnt think there are any devices attached either when I am in download mode.
I did also try the Heimdall install methods and used their drivers, but that doesnt work either
All I am trying to do so far is get CWM installed
Any ideas?
Click to expand...
Click to collapse
If you used a one-click jar file, I believe you used Heimdall, as Odin-based one-clicks would be .exe files. That being the case, if one of the one-click heimdalls worked, other ones should work as well.
If you don't mind me asking, which one-click did you use? What rom were you on when the other one worked, and what rom are you on now?
I installed this "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" to get it to work in what I think is a factory default.
I am now trying to get the downloading to be recognized by Odin or Heimhall or anything/.
They all see the phone in normal mode but when in download they do not see it
Have you tried all of the USB ports on your computer? If you're on a desktop, make sure it's one of the ones in the back (directly attached to the motherboard). Also, if you haven't rebooted your computer, do that, and then see if the UCKB2 one-click sees your device.
You can also try the full heimdall package, as that has a tool that will quickly check to see if it sees a device in download mode.
ODIN doesnt see Cappy
Looks like the drivers from Heimhall mess up the ODIN drivers. I removed the drivers from System Drivers that the Heimhall installed and now the ODIN seems to see the device again.
Now I need to figure out what I need to put on the device to make it work
MarkWorsnop said:
I installed this "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" to get it to work in what I think is a factory default.
I am now trying to get the downloading to be recognized by Odin or Heimhall or anything/.
They all see the phone in normal mode but when in download they do not see it
Click to expand...
Click to collapse
einstall the Samsung drivers. The zadig driver you installed for Heimdall causes problems with dl mode if you then try to use Odin.
mrhaley30705 said:
einstall the Samsung drivers. The zadig driver you installed for Heimdall causes problems with dl mode if you then try to use Odin.
Click to expand...
Click to collapse
I just figured this out. Now what CWM file does ODIN want? After all of this I am lost! I will start back at the first post on adding CWM I guess...!!
It's going to want a kernel with CWM baked into it, or you can flash the JF6-based one click file to get back to stock without the 3e recovery error. From there you can just root, then copy the rom you want to install to your internal SD card. Rename it "update.zip", and flash that.
If memory serves me correctly, that's the simplest way to flash from Eclair. You can also try to Odin in a CWM-friendly Froyo kernel, or copy the cwm file out of the AIO captivate toolbox (copy it out, don't directly use the tool).
To get cwm, use a kernel with cwm as jimtheiss said, in a tar format. Older Talon kernels were in tar, as was Speedmod, and I think xcal's reoriented kernel had a tar version.
Open Odin, use the pda slot for the kernel, uncheck reboot. Connect phone. When the yellow box lights up, hit start. When completed, pull the battery,reinsert battery, use button combo to get in recovery.
jmtheiss said:
It's going to want a kernel with CWM baked into it, or you can flash the JF6-based one click file to get back to stock without the 3e recovery error. From there you can just root, then copy the rom you want to install to your internal SD card. Rename it "update.zip", and flash that.
If memory serves me correctly, that's the simplest way to flash from Eclair. You can also try to Odin in a CWM-friendly Froyo kernel, or copy the cwm file out of the AIO captivate toolbox (copy it out, don't directly use the tool).
Click to expand...
Click to collapse
I can't seem to find Eclair with CWM. I did find a I897UCJF6-final-OCD-REV0 EXE with ODIN built into the EXE but whatever happens on that version ODIN didnt see the phone.
The ODIN 1.85 sees the phone, but I do not know what to download and what there downloaded file goes in ODIN.
I also ran the JAR file again and it did get back to 2.2 but then I dont seem to be able to get CWM working.
All I wanted to do it put CM7 on the phone. I guess I have to have Eclair or Froyo first to get the CM7? I think that is what I read. I havent tried it from GB
I would suggest following mrhaley's directions about flashing the kernel.
And here is the speedmod kernel.
MarkWorsnop said:
I can't seem to find Eclair with CWM. I did find a I897UCJF6-final-OCD-REV0 EXE with ODIN built into the EXE but whatever happens on that version ODIN didnt see the phone.
The ODIN 1.85 sees the phone, but I do not know what to download and what there downloaded file goes in ODIN.
I also ran the JAR file again and it did get back to 2.2 but then I dont seem to be able to get CWM working.
All I wanted to do it put CM7 on the phone. I guess I have to have Eclair or Froyo first to get the CM7? I think that is what I read. I havent tried it from GB
Click to expand...
Click to collapse
My 2 cents....if you have so much difficulty using Odin/Heimdall, I would highly recommend staying away from CM7 or MIUI until you are really comfortable flashing stuff without hiccups. CM7 and MIUI are quite different beasts, compare to the ROms ur flashing.
chappatti said:
My 2 cents....if you have so much difficulty using Odin/Heimdall, I would highly recommend staying away from CM7 or MIUI until you are really comfortable flashing stuff without hiccups. CM7 and MIUI are quite different beasts, compare to the ROms ur flashing.
Click to expand...
Click to collapse
The only thing he needs to flash with Odin/Heimdall is the kernel to get cwm. Its the same for most other GB roms. After you get cwm, its just flashing from cwm, with an extra factory reset and ROM flash.
Hi Guys, I have a SGS i9000M, and I used this forum post http://forum.xda-developers.com/showthread.php?t=1379650 to install CWM and ICS 4.0.3. I also installed Semaphore Kernel 1.2.0. It was working great for a month until I was messing with the Semaphore settings and enabled Bigmem, then when I rebooted it was stuck on the Semaphore Kernel screen, I couldn't get into CWM, but I could get into Downloading Mode.
I Run Odin 1.85 and select my I9000UGKG3-homebinary.tar file to go back to stock and when I do, I get the message: Cannot open the specified file (Line 1876). I have downloaded 3 different versions of that file, so I know it's not the file.
I've tried every combination of buttons I can, but it's not going into CWM, I just get the black screen of death whenever I reboot any way other than into Downloading Mode.
Can anyone please help me? Thanks!
*Edit: I flashed the PIT, PDA, CSC of the JVP Rom from the above linked post, and got it going, flashed chainfire, it works fine up until then, but when I install the ICS zip, it just flashes some installing stuff, then reboots, over and over, never completing, please help! I've tried different downloads of ICS 4. To repeat: It works fine installing Gingerbread and chainfire, but ICS gets stuck in a loop during install!
I remember something similar when I first flashed to ICS.
I just popped the battery out for a bit, not too long, and then re-flashed the ICS ROM. I was using the teamhacksung rom.
You could try flashing cm9 nightly (galaxysmtd), and Google Apps, and the cm7-kg3 modem.
I can't emphasize enough that you have to read, read, and re-read so that you do it exactly as written. There are lots of youtube videos that may aide you seeing what the "word instructions" mean.
Persist and you will get there.
As the the op says in the second thread of the link you quoted:
if your upgrade to ICS fail
do not despair...
just repeat the Odin steps to get back to KG3 stock + CWR
and flash another ICS build
A further thought may be that you do a factory reset at the beginning of your process. Make sure anything precious is saved to your external sd card.
Hi there, thanks for your reply. I will try your suggestion of the factory reset at the beginning. *Edit: tried, and same problem. When I go to flash stock rom I9000UGKG3, error Line 1876.
The problem i'm having is I can't flash back to KG3 stock, when I try to flash I9000UGKG3-homebinary.tar file to go back to stock, I get the message: Cannot open the specified file (Line 1876). All I can do is load the JVP rom. I have tried multiple different downloads of my I9000UGKG3 stock rom.
I've left the battery out overnight, and tried to flash all different versions of ICS multiple times. I do agree with the 'try again and wait' theory that goes with this stuff, because it works, but in this situation, it gives me the same error 1876 every time, I can't flash back to stock. That might be why I can't install ICS.
I was able to do all of this first time before and ran ICS 4.0.3 with Semaphore Kernel for a month before I messed it up.
Anyone know any other ways to get back to stock?
Thanks!
Hi,
Here some stuff I had in my notes, I'm just copy/pasting, excuse the repitition.
Ditch the i9000m stock rom (which is UGKG3 2.3.3, the one you're probably using) and flash JVT (2.3.5) stock rom, then flash CF-root for JVT. The Bell i9000m will run on the International i9000 firmware and this should get you out of the bootloop.
http://forum.xda-developers.com/show....php?t=1102881
Follow the instructions on here. Use the JVT 2.3.5 PDA, KG3 modem, and csc...its the canadian one. And you might as well repartion with 512 pit. All this can be downloaded on the link above. After you do all that you will have the latest gingerbread firmware. Now you can root with a JVT kernal like semaphore or CF root. There are also a bunch of custom roms you can use on JVT not much if anything for I9000m . The only thing you need from I9000M is the modem and csc....otherwise your cell coverage will suck. I assume you already have odin, if not its available on the above link aswell.
I remember ODIN flashing JVU before going to ICS. Just wanted to see what the value pack was all about.
PDA - use JVT/JVU
Phone - KG3
CSC - KG3
PIT - 512
Re-Partition - ON
Auto Reboot - ON
F. Reset Time - ON
---------- Post added at 01:47 PM ---------- Previous post was at 01:36 PM ----------
Here was something else in my notes:
Recovery
Mounts and storage - Format cache, data, and system
Flash stock
Hiya, thanks again for your reply. I also live in BC, Vancouver.
I will try your further suggestions, thanks so much for sharing your notes.
The link included seems to be dead, any chance to find the thread it would have pointed to?
Cheers.
Here it is:
[Firmwares]Official I9000/I9000M Firmwares collection [Latest: XWJW6, XWJW5, XXJW4]
I'm in Kelowna-fornia.
fixed - ICS install issue
That's sweet, Kelowna is a nice area :>
Well, I worked my butt off for almost two weeks, 4 hours a night.
I should start off by saying I still cannot boot to Clockwork Recovery with any button combination, i've tried all the usual suspects and then some atleast 50 times, probably way more. The only way I can is once in awhile a miracle occurs and it reboots to Clockwork Recovery 5 (the blue text themed one), or if I install CF-Root and use to reboot into recovery in it's options.
I should also mention that whenever I do get into Clockwork Recovery, it's like version 3, with the orange text theme. And I don't know if it helped, but I am now using Odin 1.87 instead of 1.85.
I was finally able to flash stock by flashing the 4 separate files, 512 Pit, PDA, Phone, and CSC rather than flashing the UGK3homebinary.tar.
I tried multiple different versions of Gingerbread with CF-Root to try to get ICS or CM9 working, JVT, JW1, JVU, all of them worked, but the same thing happened when going to install ICS, and even CM9, the install would start, once it got to the part where it says "Rebooting if necessary" on the ICS or CM9 install, it would reboot, show the install beginning again, then reboot at the same spot, infinitely. I made sure to try atleast 50 times so I could bypass the suggestion of trying again.
During this process the phone was acting very buggy, you know what I mean, restarting, freezing, force stops, mounting storage issues. I went into the options and set the phone to factory default, also during another miracle one time it booted to the stock android recovery, you know the one with like 4 options. Format, Wipe, go back, reboot. I formatted and wiped from there as well. These two things seemed to help alot, and the phone was less buggy and more willing to receive my treatments.
After browsing some more, I found this kernel cleaner, i'm surprised no one in the forum mentioned it to me, perhaps they were angry I hadn't discovered it on my own. In any case it's called 'Ultimate Kernel Cleaning Script - 4.0 [MIUI/CM7 and SAMSUNG]', there is one for Samsung Roms and one for CM roms, and all you do is run it to clean out the old before installing ICS. Link: http://forum.xda-developers.com/showthread.php?t=1166954
Ok, so I am now I am excited, this tool looks like my answer. I flash stock, install JVT rom with CF-Root for JVT, (I run my sweet kernel cleaner zip I found) and go for ICS 4.0.3 install.....and same thing happens, sigh. Flash stock again, and oh what's this? I found another custom ICS Rom I can try, remICS http://forum.xda-developers.com/showthread.php?t=1687727
Ok, so I flash stock again, install JVT, CF-Root for JVT, install remICS and....D'oh! Same thing, it's rebooting........but wait, this time it's rebooted into Clockwork Recovery 5 on it's own without any keypress, instead of looping. What a great time for that Miracle! (This only happened 3 times in about 60 hours of working on the phone!) Ok, but what to do now? Well, ICS didn't really install, it just started to, maybe i'll try to restart the install from in here! Choose install zip, this time I chose remICS only because so far it had the lesser fail rate - I didn't want to mess up this golden opportunity, I know it's just a different version of Clockwork popping up, but when anything different than the same failures happens, you don't want to waste it. It's installing....complete! Do I dare risk installing a customer kernel and destroying all of my progress? Yes! Install Semaphore 1.2.6 for ICS, working great!
So, I don't know if it was the kernel cleaner, the remICS, or the miracle Clockwork 5 boot, but I don't want to take anymore chances, that's how I got here, fiddling with what's working great already.
I probably didn't need to post this, but I wanted to recount my experience for anyone else having a similar problem. I have now been running stable with all my apps installed for 12 hours. I would like to have stock ICS with phone rooted, but I don't want to take any chances. This remICS custom rom is very nice, speedy and alot of the bloatware removed, along with some killer SGS3 menus and layout.
I would like especially to thank my Canadian friend for helping me :victory: