Related
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.
Hi, attached is a picture of what my tab is displaying after an unsuccessful root attempt. Can anyone tell me what it means and how to solve this?
Thanks
It's soft bricked. Grab the stock rom for your tab, load up odin or heimdall and flash back to stock, should be good to go from there.
And indeed everything is back to normal. Thanks a lot
I have a VZW SCH-I800 and used CWM to "Flash a custom recovery image" with the intent on getting gingerbread on my tab. I followed the steps from the unlockr...which now my tab has CWM 3.0 and my camera doesn't work, my accelerometer doesn't respond when turning the device, my auto brightness doesn't work, and when i have new mail it doesn't show the number on the icon. (just what i have noticed so far.) Since I have CWM installed is it possible to flash a stock ROM, say from a ZIP file on the SD card? Or is it more complicated. As i said the ultimate goal was to get to Gingerbread, but I will now settle for a working stock ROM.
Help is much appreciated!
The kernel for the CWM to work, will soft brick your tab with the stock software. Your best option is to Odin or Heimdall back to stock and root from there.
Sent from my SPH-D700 using xda premium
Do you know where i can find the Stock kernel?
You'll have to find the stock VZW rom, and flash the whole thing, or you could just pull the kernel out of the .tar file if you have something else in mind for just the zImage.
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.
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).
so I soft bricked my p1000 by attempting to download and install the latest cm9 nightly (i'm pretty sure i tried to flash a bad zip.
it starts up, gets to the samsung galaxy tab logo and hangs until i force it to power off. I CAN enter download mode but not CWM recovery.
I would very much like to recover the data that is currently on my tab or i would simply restock as all of the unbricking guides suggest, but alas, I want my data.
I have a known good working rom image .zip on the internal flash. so I would like to just attempt to flash that, but I can't seem to access CWM recovery.
From what I gather, cwm recovery is a function of the kernel, so then, at this point I would very much just like to flash one of the modern cm9 cwm recovery-enabled kernels via odin OR a known good cm9 install package via odin.
does anybody know how I can go about doing this?
that is why I always use heimdall.
extract the boot.img from good package and
heimdall flash --kernel ./boot.img --recovery ./boot.img
I do realize that this is what the thanks button is for, but somehow that doesn't seem to be enough. thanks to your instruction, I was able to immidiately get my p1000 back online up and running. THANK YOU so very much! *super internet high five*!!