I have searched around and have found anyone with quite my same problem.
Here's my issue, my girlfriends Captivate wont enable USB Debugging in Download Mode. It works fine when the phone is booted into the OS but the AIO toolbox wont recognize USB debugging in Download Mode.
The phone is currently running fine with Precision. It's is just having some force close issues. But currently I am stuck on this ROM because of the lack of Debugging in download mode.
I have tried two different W7 computers. One is 32bit Professional and one is 64bit Ultimate.
I have tried uninstalling and reinstalling the USB drivers but to no avail.
Debugging mode had nothing to do with dl mode, what are you trying to do?
Edit: ok reading your comments again, are you having problems getting odin to recognize your phone?
CM7
Flash back to stock, but it never completes. Do I need to flash back to stock in order to flash a new rom? Because that seems to be what I have picked up.
No you do not have to flash stock. You are on precision, what kernel? What are you looking to flash?
CM7
finakechi said:
Flash back to stock, but it never completes. Do I need to flash back to stock in order to flash a new rom? Because that seems to be what I have picked up.
Click to expand...
Click to collapse
In my knowledge, flashing back to stock is best way to flash new rom..to avoid any complications...but you flash new rom without going back to stock as well
I think you should use ODIN3 V1.7 or v1.3 to flash back to stock...Its better and tested way to flash back to stock...
I used AIO and i bricked my phone...but the developer of AIO said u should use version 2.5 as its more reliable then version 3.0
I am using the SuckerPunch #50 100HZ Kernel (which come with 3.5). And I haven't quite decided which ROM I will use yet now. I was going to try cognition.
About the whole flashing back to stock thing, I just noticed a lot of the directions for the ROMs mention it.
Flashing back to stock is largely an old need that still its used by many. When custom kernels with built in lag fixes started coming about you where advised to either disable lag fix before switching roms, or flashing stock. This was because the recovery in the kernel could not under stand the ext 4 partition the lag fix was using. Most of the built in recoveries in the roms out there today now can understand the partition, because of this flashing stock is not necessarily needed. That being said I am not sure what kernel cognition uses and if this would hold true.
There are more threads of people soft bricking their phone using odin than there are any other issues. All that being said I would not be flashing roms if you can not get your arms around odin. God forbid something does go wrong you need to be able to recover.
CM7
No I am not worried about flashing in Odin. i have a Fascinate and have never had any real issues (save for one). I just never saw any of the "flash back to stock" issue in the Fascinate forums. Is this lag fix the same as the Voodoo lagfix I use on my Fascinate?
Yes I understand they are different phones so I wont be trying to flash one ROM from one phone to another. i just meant the concept behind it.
Cognition uses stock KB1 kernel with voodoo lagfix and CWM
Sent from my Captivate using XDA Premium
I you use Odin 1 click to stock. Never had any issues in over 100 flashes to stock. I rarely use it now because most roms install scripts remove any of the old rom fragments. Odin is a useful tool if something goes wrong during a flash and your getting fc's all the time. Simply hold volume and plug it in and go. I strayed away fro AIO toolbox due to multiple reports from it bricking their phone.
If the toolbox doesn't work just use Odin and all will be will. Its the easiest version of Odin there is (in my opinion)
Sent from my Captivate using XDA Premium
You can also boot in recovery and re flash the rom. Wipe the dalvik cache and fix permissions if your getting FC's.
Sent from my Captivate using XDA Premium
finakechi said:
No I am not worried about flashing in Odin. i have a Fascinate and have never had any real issues (save for one). I just never saw any of the "flash back to stock" issue in the Fascinate forums. Is this lag fix the same as the Voodoo lagfix I use on my Fascinate?
Yes I understand they are different phones so I wont be trying to flash one ROM from one phone to another. i just meant the concept behind it.
Click to expand...
Click to collapse
Lag fix doesn't affect USB debugging.
Sent from my Captivate using XDA Premium
If I am following you, it sounds like odin does not see the phone in debugging mode.
I had am issue where odin would only see the phone in sync mode, and I could not get my computer to see the folders on the phone in mass storage mode.
I reinstalled the drivers and everything was fine after that.
Related
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
tomween1 said:
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
Click to expand...
Click to collapse
For your daughter's Captivate , did you try rebooting the phone and getting back onto recovery mode to see whether it was just a weird recovery boot ? LOL idk , I never heard of that one , but it may be fixed through a simple reboot . IF that doesn't work , try flashing another kernel through Odin + Download Mode .
For your Captivate , once you get to download mode , flash DG's stock Captivate Eclair (It has the 3-button mode fix , just in case you might not have it or ... just in case) . If that goes great , then install Rom Manager to get CWM , then start flashing again .
Yeah I'm kinda skipping steps , but you said that you've flashed before , so it should be a piece of cake to fit in the pieces together .
There are also other methods like Master Clearing , flashing another stock ROM , etc. but the method I posted has always helped me in tight situations .
BTW , does your captivate have the 3-Button combo ?
dayloooo said:
For your daughter's Captivate , did you try rebooting the phone and getting back onto recovery mode to see whether it was just a weird recovery boot
Click to expand...
Click to collapse
Yes I tried several times. Always getting the same options, always excluding sdcard option.
dayloooo said:
IF that doesn't work , try flashing another kernel through Odin + Download Mode
Click to expand...
Click to collapse
Why would I flash a different kernel to stock Froyo?
dayloooo said:
There are also other methods like Master Clearing
Click to expand...
Click to collapse
This is where I was when the catastrophe hit!
dayloooo said:
BTW , does your captivate have the 3-Button combo ?
Click to expand...
Click to collapse
FYSA yes It does....did
tomween1 said:
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
Click to expand...
Click to collapse
flash the leaked odin froyo from designgears REV02. you should fine after that
Which can be found here: http://www.megaupload.com/?d=QL6NX702
1. Open that .exe found in the .zip in the link above. (Make sure you run the .exe!)
2. Put your phone into download mode.
3. Plug in the USB.
4. The program (Odin One-Click) should find the phone.
5. Basically follow the only option you get, and it'll be done for you automagically (apart from 'Master Reset', which you might want to do AFTER you finish resetting it back to stock).
tomween1 said:
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
Click to expand...
Click to collapse
I dont think anyone that responded actually understood what you were saying, possibly myself included.
First part(daughter), froyo 2.2 stock has 3e recovery that requires a signed update.zip. You need to root it to install the modded 3e recovery in the dev section that removes the signature verification. OR flash it back to 2.1 with oden(yes downgrade it to upgrade it). Im sure there are other methods, those are just 2 i can think of off the top of my head.
Then you can install cwm with a cwm update.zip that is floating around the captivate forums.
From there you can install any rom with the normal methods.
Second part(you), odin bricks phones. Its not talked about very much but its easy to do. Your usb cable was probably loose, or bad, and cause an error and your phone soft bricked. Once you get the jig, pop it in get into download mode - start odin - connect the phone to the pc - wait for odin to detect it - flash 2.1 - flash serendipity.
If im understanding your problems correctly.
venomio said:
(apart from 'Master Reset', which you might want to do AFTER you finish resetting it back to stock).
Click to expand...
Click to collapse
Meaning after a new rom is no longer wanted? It's already stock.
So what you want to do is to Master Clear the Stock ROM before you install the new custom ROM on to it. This will prevent any possible problem coming up while flashing. (Of course, it will clear all data in your internal SD).
whiteguypl said:
Your usb cable was probably loose, or bad, and cause an error and your phone soft bricked
Click to expand...
Click to collapse
You hit the nail on the head I was half way through Odin when my computer made the disconnect sound and then reconnected immidiatly I kinda figured I was [email protected]@k?$ at this point. This was different though, because I've been able to come out of soft boots befiore. No doubt I was playing w/ fire thoes times
Thats exactly why I wanted to get a jig before I started any of my ROM flashing. I had an issue when I started Recovery Mode would just prompt restart and other things off the bass menu, when I tried to back up.
I had to flash 2.1 Eclair and then master Wipe it. Then I was able to do anything to.
Sucks you bricked it. EVERYONE Bricks one time at least one electronic device.
<--PSP Bricker
I am working on a friend's captivate (att) and I have him running cognition ROM right now. Unfortunately, it still sucks and he hates his phone. I want to flash cyanogenmod to the phone, but I need to restore it to stock first (I think). I am trying to use AIO tool to flash the phone to stock, but ODIN hangs when I start it. Is there another way to switch ROMS without flashing back to stock first? I don't have to flash to stock with my Optimus V, so why it the Captivate such a PITA phone to mess with? Please help me. I am tired of my buddy complaining about his phone every day.
super coffee said:
I am working on a friend's captivate (att) and I have him running cognition ROM right now. Unfortunately, it still sucks and he hates his phone. I want to flash cyanogenmod to the phone, but I need to restore it to stock first (I think). I am trying to use AIO tool to flash the phone to stock, but ODIN hangs when I start it. Is there another way to switch ROMS without flashing back to stock first? I don't have to flash to stock with my Optimus V, so why it the Captivate such a PITA phone to mess with? Please help me. I am tired of my buddy complaining about his phone every day.
Click to expand...
Click to collapse
If the phone doesnt have the gb bootloaders then you can flash CM7 using any kernel with clockworkmod recovery.
Sent from my SGH-I897 using XDA Premium App
I really wouldn't recommend CM7 if your friend isn't into phone development on his own, especially the nightly builds. However, if you're dead set on doing that, just do it without the AIO tool. Flash to stock with Odin one-click and root the phone some way (superoneclick is preferred) and then just follow the steps. Well, you actually don't require stock so long as your phone is rooted and not running GB bootloaders, but it's always safe to just go back to stock anyways.
For some reason though, ODIN will not flash to stock. Sometimes it will get as far as flashing modem.bin, but then it just hangs. It made it all the way to filesystem.rfs once, but again, it hung up. What is going on here? Is it my PC or do these phones just do that?
It could be a variety of problems. I'd reinstall the drivers and ODIN on your computer, because something may not have installed correctly. I know that I've never had any issues going back to stock with ODIN.
Now after failing so many times to flash the phone, I can't even get it to go into download mode anymore. I am using the volume up+volume down and plug usb method, but that all of a sudden will no longer start the phone. I am afraid that I may have bricked it. Any ideas?
super coffee said:
Now after failing so many times to flash the phone, I can't even get it to go into download mode anymore. I am using the volume up+volume down and plug usb method, but that all of a sudden will no longer start the phone. I am afraid that I may have bricked it. Any ideas?
Click to expand...
Click to collapse
Is it doing anything? Showing any power?
Sent from my SGH-I897 using XDA Premium App
super coffee said:
Now after failing so many times to flash the phone, I can't even get it to go into download mode anymore. I am using the volume up+volume down and plug usb method, but that all of a sudden will no longer start the phone. I am afraid that I may have bricked it. Any ideas?
Click to expand...
Click to collapse
Try the ADB method, instructions on this page:
http://forum.xda-developers.com/showthread.php?t=884364
If all else fails, building a jig is very easy and cheap. My best guess is you had something installed incorrectly on your computer and when ODIN tried to do its thing it froze and then "software-bricked" your friend's captivate.
Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...
Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again
I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.
For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA
TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business
*removed double post
studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.
You have to hit enter at the Right moment, it takes practice
Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA
Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA
If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.
Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )
How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.
Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA
Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.
When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium
I have an issue, I was updating my Captivate to 2.2 with Odin3 One Click and that worked fine, then for some reason I cannot explain I tried to use Odin to upgrade to 2.3 (the blow fish one) flashed the image then got the restart with the blowfish and then used Odin to complete the process as per the instructions and got soft brick, I fixed this with the one click unbrick, then it went into a boot loop.
The loop is AT&T screen then fuzzy colours and a restart (like a graphics card has gone haywire).
I can get into the download mode by removing the battery, plugging the USB cable in holding the volume buttons then installing the battery the download mode appears but Odin is not picking up the phone.
When it is in the loop I can get Odin to identify the phone but when I try to go into download mode it won’t identify it. I have tried with adb and it does the same thing.
Any suggestions? I have looked at the forums for a long while so my apologies if this has already been covered.
Have you installed the necessary drivers on your computer?
Sent from my glitched ICS Captivate using XDA App
You may want to also take a look at the "Captivate Connection Issues" thread - it has some steps to help get you connected in download mode.
Once you have it connected, you can probably safely flash a Gingerbread stock rom to get back to a clean place to start flashing from.
Hi,
Yes forgot to mention that I have installed the correct USB drivers, Odin picks up the phone during the loop so that tells me that the Cable is fine and the drivers are working. I will try to re-install them just to be safe.
Thanks I will look through the connection issues threads and see if that helps, I am at work at the moment so will be later in the day.
The garbled bootscreen happens when you try to run gingerbread with froyo bootloaders. You must have chosen a bootloader free package. Instead, for your first time flashing to GB (and first time only), use a package with bootloaders
Sent from my CM9 ICS i897 Captivate
Haplo Nash said:
... upgrade to 2.3 (the blow fish one) ...
Click to expand...
Click to collapse
What is this blow fish one that you speak of? Korockinout13 is correct that you are getting the garbled screen because of an incorrect bootloader. You may be having issues because the ROM you flashed might be an i9000 based ROM and you will need different drivers.
DISCLAIMER: It's still earlier early and I haven't had all my coffee yet. Please correct my logic if it is wrong.
Red_81 said:
What is this blow fish one that you speak of? Korockinout13 is correct that you are getting the garbled screen because of an incorrect bootloader. You may be having issues because the ROM you flashed might be an i9000 based ROM and you will need different drivers.
DISCLAIMER: It's still earlier early and I haven't had all my coffee yet. Please correct my logic if it is wrong.
Click to expand...
Click to collapse
I believe the blowfish one he's referring to is the Fugu Root method.
About One-Click UnBrick
This Software:
Will work on all Samsung devices which use Odin3
Is a single, portable executable
Is the first one-click anything for our devices on Linux
Works on Mac
Works on Windows
Is open source
Is programmed in Java
Deploys and installs Heimdall for your OS
Is super easy to use.... Only one button!
Click to expand...
Click to collapse
The bolded line is why ODIN no longer detects your phone. The Heimdall driver has been installed. You can either go grab a Heimdall one click from here or remove the Heimdall driver (trying another USB port may work) and then try using ODIN again.
Yes it was the Fugu Root's one and I didnt update to a Gingerbread bootloader before I flased it onto my phone.
Thank you for all your help, I will never mess around with my phone at 2am again.
I managed to get Odin to pick up the phone and was able to re-load FROYO and will start again.
Do Apex ROM Heimdall one-click flash with bootloaders enabled. Most painless process.
This is my first post so ill try to make it the least noobish that i can.
This is the current state of my phone
Device : Samsung I897
Firmware :2.3.5
Baseband : I897UCKK4
Kernel : 2.6.35.7-I897UCKK4-CL614489
Rom and Kernel flashed and method : Andromeda w/ Ursa Minor using Odin3 v 1.7
I got to this build from my original 2.2 froyo build about a week ago. I made a mistake out of haste when I was flashing the Ursa Minor kernel and whatever i did lead to me soft-bricking my phone. After that, every time i booted my phone it would be stuck at the Ursa Minor screen but it was still detected via usb by my computer. I was able to use ADB to reboot into recovery mode and then I tried wiping all data/cache. Unfortunately that made matters worse as when i rebooted it i was stuck at the same screen and this time the phone was NOT detected via usb by my computer.
At this point I made a jig and booted the phone into download mode and was able to use Odin 1-click to wipe my phone and return it to stock. This left my phone unbricked and it booted into GB 2.3.5 this time and not Froyo 2.2 like I had it originally. Its functional for the most part except for these issues.
1. None of the button commands work to boot into recovery/download
2. The boot animations are very laggy plus i see a very unpleasant screen of rainbow artifacts/blocks (the artifacting only lasts a few seconds)
3. And finally, no matter what i try USB debugging mode will not connect and I cant use it. **
**Things i tried: Every button command, every usb slot, re installing drivers and rebooting pc; over and over and over.
I've spent the past 24 hours, albeit with some sleep, scouring not only XDA, but any forum i can find, for answers. Unfortunately everything I've found has either been a solution for a different issue entirely or it just didnt work on my phone. Im not entirely sure what to do at this point. I can still enter download mode with my jig so i've thought about flashing a new kernel with odin3 but im hesitant as I dont want to mess around with my phone anymore until im certain about it.
I guess the overall question is what could possibly be happening that USB debugging wont work but USB mounting does work? On top of that, what would be a wise course of action after this? I suspect that my kernel is the issue here, but that guess is almost purely pedantic. If anyone can help or provide any advice i will be forever grateful!
All will be fixed if u Odin 1 click the KK4 WITH the GB Bootloaders included...http://forum.xda-developers.com/showthread.php?p=18370912. Instructions and info are included with the download.
If u wanna move on to a Developer's Rom after u flash the Stock KK4 with Bootloaders, then use Red_81's [Utility] KK4 Easy Root that u can find in the Dev forum.
Sent from my SGH-I777 using xda premium
4-2ndtwin said:
All will be fixed if u Odin 1 click the KK4 WITH the GB Bootloaders included.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
This will be ok even if i already flashed the GB bootloaders when I first tried flashing andromeda?
(Ooops on the thx. Fingers movin to fast.)
Ur #2 above --- The pixelated screen u see means that u did not flash the GB Bootloaders.
Sent from my SGH-I777 using xda premium
WalkerTex said:
This will be ok even if i already flashed the GB bootloaders when I first tried flashing andromeda?
Click to expand...
Click to collapse
Well 4-2ndtwin beat me to it.
My fingers r in ninja mode lol
Sent from my SGH-I777 using xda premium
I have a side question now. Would the lack of those bootloaders be a reason why my jig doesnt seem to be working now? Been trying for the past hour using the three resistors w/ scotch tape method but not results...
Edit- Nevermind, i got it into download mode from adb somehow.