Related
Long story short, I've been haiving a bunch of problems, and someone pointed me to an update.zip file that might help me unroot my phone without needing a USB connection. When I go into recovery mode and select "install package", I get this message:
E:signature verification failed
installation aborted
Does anyone know what I may need to do in order to clear this up freaking problem?
first you might want to look at the stickies in general, thats what they are there for. if you dont find your issue SEARCH. 2 minutes of effort would have found you this http://forum.xda-developers.com/showthread.php?t=1052991
studacris said:
first you might want to look at the stickies in general, thats what they are there for. if you dont find your issue SEARCH. 2 minutes of effort would have found you this http://forum.xda-developers.com/showthread.php?t=1052991
Click to expand...
Click to collapse
Omg.. Another signature failed issue lol
Thanks for taking care of this one Studa
My apologies. I did look at the "related topics" that came when I did my post, but that one didn't come up. Guess I wasn't through enough.
I'm pretty new to all this, and I'll admit that part of that linked thread is a bit over my head so this may be another stupid question. My main issue is that I get an error trying to connect via USB, and it looks like all those fixes require Odin 1 click. Does one of those methods allow for the fix without a USB connection (I do think I have the ability to get a file from the computer to my phone via the external SD card).
Girevik said:
My apologies. I did look at the "related topics" that came when I did my post, but that one didn't come up. Guess I wasn't through enough.
I'm pretty new to all this, and I'll admit that part of that linked thread is a bit over my head so this may be another stupid question. My main issue is that I get an error trying to connect via USB, and it looks like all those fixes require Odin 1 click.
Click to expand...
Click to collapse
What you mean you get an error connecting the USB? Could you be more precise?
Also, the signature failed fix is quite easy. Tbh, you simply have to have your phone plugged in in debugging mode and run the .bat file.
Please explain your usb issue.
BWolf If the phone won't connect to usb he can't use the .bat
studacris said:
Please explain your usb issue.
BWolf If the phone won't connect to usb he can't use the .bat
Click to expand...
Click to collapse
I know, I know. I was saying for when/if it works. Duh
When I try to connect via USB I get a "USB Device Malfuctioned" error. (Which I HAVE searched on ) that I can't seem to find a fix for. I've tried it on 3 different computers, each with a different version of Windows, with the same result so don't think it's a driver issue.
I've done a factory data reset (several atually) and am still having problems, so I'd like to get a warranty replacement. But my phone is rooted so I'm worried about them voiding my waranty. Basically where I am now is tryign to find a way to unroot my phone without the USB so I can get it replaced. That lead me to the signature verifaction error and the shame of a premature post.
how loose are your ethics?
if your phone doesnt boot at all they can't tell if its rooted. a few 2 second bursts in the microwave should do it, don't do it any longer than that at a time. you don't wanna have any physical signs you just wanna fry the curcuits.
just PLAY DUMB and you should get a warranty replacement.
studacris said:
how loose are your ethics?
if your phone doesnt boot at all they can't tell if its rooted. a few 2 second bursts in the microwave should do it, don't do it any longer than that at a time. you don't wanna have any physical signs you just wanna fry the curcuits.
just PLAY DUMB and you should get a warranty replacement.
Click to expand...
Click to collapse
I'm not opposed to hiding the fact that it's been rooted, or if a fix I tried bricked it I'd be okay returning it, but I'm not sure I want to go as far as frying it in a microwave.
I've been looking for an ap in the market that would unroot for me, but so far none of the ones I've found have worked for me. Do I have no other options for something I could load directly to my phone via the SD card (I do have the ability to put something on my external SD card and transfer it over to the phone)?
Girevik said:
I'm not opposed to hiding the fact that it's been rooted, or if a fix I tried bricked it I'd be okay returning it, but I'm not sure I want to go as far as frying it in a microwave.
I've been looking for an ap in the market that would unroot for me, but so far none of the ones I've found have worked for me. Do I have no other options for something I could load directly to my phone via the SD card (I do have the ability to put something on my external SD card and transfer it over to the phone)?
Click to expand...
Click to collapse
no apps that i know of work for froyo to root/unroot without needing a computer and a working usb port ... what you will have to try is fix the 3e recovery manually. i dont think that update.zip will unroot, it just roots, but you could try. If that doesnt work go grab cognition rom from development flash that but while its in the process pop the battery out. if youre "lucky" you will either get a "phone....!....pc" screen or a hard brick in either case all eveidence will be erased.
this process will require some research and learning on your part...
Are you SURE you have the correct drivers for your computer? When I tried to use my phone on someone elsewhere computer the computer would not install it until I installed the samsung drivers from the odin one click post.
Can you get into download mode? Method varies based on build number or phone. Try turning your phone off, holding the two volume keys and plugging in usb, if you see a big yellow triangle with an android and a shovel you are in download mode. Once in download mode the computer will see your phone as a different device and install more drivers. If all that works, you can use odin one click to go back to stock.
Once back to stock your problem may be fixed anyway, if not it will be unrooted and you can return it to att. Morals intact.
Sent from my Captivate running FireFly
studacris said:
no apps that i know of work for froyo to root/unroot without needing a computer and a working usb port ... what you will have to try is fix the 3e recovery manually. i dont think that update.zip will unroot, it just roots, but you could try. If that doesnt work go grab cognition rom from development flash that but while its in the process pop the battery out. if youre "lucky" you will either get a "phone....!....pc" screen or a hard brick in either case all eveidence will be erased.
this process will require some research and learning on your part...
Click to expand...
Click to collapse
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
But like Studa said, you have some reading to do
quarlow said:
Are you SURE you have the correct drivers for your computer? When I tried to use my phone on someone elsewhere computer the computer would not install it until I installed the samsung drivers from the odin one click post.
Can you get into download mode? Method varies based on build number or phone. Try turning your phone off, holding the two volume keys and plugging in usb, if you see a big yellow triangle with an android and a shovel you are in download mode. Once in download mode the computer will see your phone as a different device and install more drivers. If all that works, you can use odin one click to go back to stock.
Once back to stock your problem may be fixed anyway, if not it will be unrooted and you can return it to att. Morals intact.
Sent from my Captivate running FireFly
Click to expand...
Click to collapse
I'm pretty sure on the drivers. I removed what I had and re-installed from a link I found online. From the searching I've done it seems that "Device Malfunctioned" error is the kiss of death. I've not found anyone yet who's recovered from that.
I remember getting into dowload mode when I did the update to 2.2 but don't recall the method. plugging in the USB cable with the volume buttons pressed just powers up the phone.
Girevik said:
I'm pretty sure on the drivers. I removed what I had and re-installed from a link I found online. From the searching I've done it seems that "Device Malfunctioned" error is the kiss of death. I've not found anyone yet who's recovered from that.
I remember getting into dowload mode when I did the update to 2.2 but don't recall the method. plugging in the USB cable with the volume buttons pressed just powers up the phone.
Click to expand...
Click to collapse
The method is actually a bit different then what he mentionned:
Unplug usb;
Pull battery;
Hold volume buttons (and keep holding no matter what);
Plug usb in your pc and then your phone;
Put the battery back in and wait until the android with a shovel shows up.
It can take a few tries too before it works.
studacris said:
what you will have to try is fix the 3e recovery manually.
Click to expand...
Click to collapse
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
BWolf56 said:
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
Click to expand...
Click to collapse
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
BWolf56 said:
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
But like Studa said, you have some reading to do
Click to expand...
Click to collapse
Hahaha I know this is a nice change.
But with his usb issues I doubt odin will ever recognize the phone.
Girevik said:
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
Click to expand...
Click to collapse
No flashing a rom doesn't require odin. And the manual fix should be on the sticky
Girevik said:
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
Click to expand...
Click to collapse
No, you actually shouldn't flash a ROM with the usb plugged in (UNLESS using Odin lol). I guess my point was that you could have Cognition on your ext sd card and flash it but didn't think about the signature failed.
studacris said:
Hahaha I know this is a nice change.
But with his usb issues I doubt odin will ever recognize the phone.
No flashing a rom doesn't require odin. And the manual fix should be on the sticky
Click to expand...
Click to collapse
You could always get Root Explorer and switch the recovery by yourself from your phone. That's actually what I did back when I was on 2.2 - Then again, you have to pay for Root Explorer and you have some more reading to do if you wanna take that path.
BWolf56 said:
No, you actually shouldn't flash a ROM with the usb plugged in (UNLESS using Odin lol). I guess my point was that you could have Cognition on your ext sd card and flash it but didn't think about the signature failed.
You could always get Root Explorer and switch the recovery by yourself from your phone. That's actually what I did back when I was on 2.2 - Then again, you have to pay for Root Explorer and you have some more reading to do if you wanna take that path.
Click to expand...
Click to collapse
1. I don't think you can flash from the external sdcard, he will have to download it with the phone itself to get it on the internal sdcard.
2. The root explorer method is the manual fix I'm talking about.
studacris said:
1. I don't think you can flash from the external sdcard, he will have to download it with the phone itself to get it on the internal sdcard.
2. The root explorer method is the manual fix I'm talking about.
Click to expand...
Click to collapse
That was imployed but Fine be that way! lol
So yea, OP - Beside all that Team confusion we're having here.. Go read/keep reading the Sticky about 3e recovery fix and if you think you can do it. Do the manual fix (getting Root Explorer and moving the recovery file by yourself) and get Cognition on your external and move it to your internal sd card.
(There I'm being clear Studa )
Hey there, i am feeling somewhat overwhelmed with all of the advice going on out there and need someone who can give me the answer to my specific problem hardware wise without breaking a sweat...
I flashed a froyo 2.2 rom onto my phone a while ago, recently all of my apps stopped working, and i could no longer install any apps.
Couple days ago i tried openning gmail and the screen went black and gave me the bzzzzzz...............................bzzz...bzzz...
vibrating error that you usually get when an app crashes.
Now the phone continues doing that even when booted up and stuff
It starts right after the S screen and repeats until the battery is removed.
My phone can't get into download or reset mode using the 3 button method so i bought a jig off of ebay, works like a charm.
however NOW, i cannot get the computer to see the phone; both when it is on and attached and in download mode and attached. Odin can't see it, neither can Kies.
If i can get either to see it, i can look up the flashing process to make sure everything is right.... but as of yet nothing i am doing is making a difference.
Thanks for any help
Ok, I'd focus on odin so disable Kies (in task manager processes - all the kies processes).
Then I would 1) reinstall the drivers (standalone ones) 2) Have a few versions of odin to try (like 1.3, 1.7 and ez odin) 3) Clean your usb port on the phone (and computer maybe too - whats the harm?).
Usually if you are sure the drivers are Ok then you should be able to odin working with a nice clean port. They are more sensitive to dirt/moisture or whatever than they should be.
Try that and let us know...
BTW Some people think that the order is important but I've never noticed that. I always have odin open and then connect it but cant hurt to try the other way around too.
Hey thanks alot,
I am at work right now but i am optimistic about trying that out lol.
Just so i know for when the time comes and if Odin works, what files do i need to flash it? .pit, .tar and anything else specific for Bell Canada?
I only ask because you are with Bell so it is probably a very simple answer for you. Otherwise I am sure i can find it elsewhere.
Thanks,
I'll keep you updated
Josh
Download the complete jl2 rom from link I posted yesterday (search my posts) with repartition ticked, then flash the kc1 rom from stock rom link on xda or at samfirmware.com and flash without repartition if you want the latest. You could just try the kc1 step but I you need to repartition.
Sent from my GT-I9000M using XDA Premium App
Hey man,
my phone has never been sent in for repairs or replaced...
I was reading one of your other posts and you advised another member to send it in and maybe they will replace/update hardware?
I have still had my phone for less than a year so sending it in will be no problem at all...
Should i flash to the latest myself or return to stock and send it in?
I really appreciate your help.
Thanks
Well he knows his is broken as he can see that his internal memory reads 0 (which means its cooked - ask me how I know...) and he was trying to fix it in a round about way. Or there was the guy who flashed a captivate rom - that was just a big no-no.
You might just have a corrupt partition or some other corruption in the file system. I seem to get that all the time and its a pain but very fixable .
Alright, sooo
-uninstall Kies
-install drivers only
-try to connect to Odin
-If succesful flash with Odin
-dance with joy
Got it, I will update you later when i get home.
Thanks
installed drivers on my work computer (32 bit windows xp) and nothing... I've tried phone off, phone on, phone in d/l mode... It doesn't pick up anything...
I can try it on my Windows 7 comp at home and see if that works but i'm wondering what the worst case scenario is just bringing into Bell and having them fix it... Am i looking at charges, warranty voiding, etc.. etc... to have it fixed or could i BS my way out of it?
Fuuuuuuuuuuuuuuuuuu
pretty sure i flashed the wrong firmware on my phone, when it boots up it says GT-I9000 not GT-I9000M.
It worked fine for like 6 months so i never questioned it... damn damn damn
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
I9000 firmware is completely compatible. The text you see is from the kernel which are always for i9000 unless you have one of the three bell firmwares. So that's not the issue.
Sent from my GT-I9000M using XDA Premium App
RogueCow27 said:
Not to be completely devious but i got an extended warranty that replaces the phone due to water damage, theft, etc. etc...
If there is no other way should i take advantage of that?
I would hate to jump to one of those actions but i am somewhat panicking becuase i made a super-noob mistake and effed up my phone....
Click to expand...
Click to collapse
I would keep trying. I have gotten warranty before and I was in the same predicament as you almost except I knew that the internal memory was dead. But that was also around the time when most of the I9000M models were dying. They might be checking more now.
If you get odin to flash a stock rom then you can go for it but by then you should be able to fix it.
Sent from my GT-I9000M using XDA Premium App
Alright i will keep trying.
As far as the firmware goes, my gf and i both have the same phone, but she kept heres official and i put custom roms on mine (just the 2.2 because it wasn't available)
We are both on bell canada so i asked her to boot up her phone and the beginning message on hers says GT-I9000M so it freaked me out lol
I will try on my home computer,
keep your fingers crossed for me
Alright, so Odin can now see my phone (it was the damn cord, my Win 7 comp couldnt see it but my xp work laptop can)
Which firmware would you recomend flashing? Stock gingerbread or a slight variation?
I am at work right now so i can wait a bit for a good response. It'd really help me out if you could provide links and tips to the best firmware out right now (i have no problem flashing a custom ROM if it is good).
Thanks alot,
Josh
Succesfully Flashes Gingerbread 2.3.4
Thanks for all your help!!!
how did you manage to see it in odin?
i have te same problem with restarting just after first screen (after flashing to gingerbread) but i cant see it in odin so i cant flash it again?
when i connect it when turned off, a small icon appears with usb connected sound but its still not visible.
Is it maybe my win7?
help, anyone please
Did you start in Download mod? Did you kill the Kies processes in you Win7 task manager ?
If yes, sometimes Windows takes time to install the drivers (be sure ton be connected to the internet), you should also close and relaunch Odin.
i launched download mode with sdk, and now i cant start it.
i went to another pc with xp. it installs drivers but odin cant recognize it.
Well i did it on my work XP computer becuase WIN 7 wasn't recognizing it. But it turns out the whole time the cable i was using would connect to charge, but not act as a pc connection.
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
everett1911 said:
I have a samsung captivate on the rogers network, and custom roms have been nothing short of a nightmare, with cyanogenmod being the only custom rom that correctly worked on my phone, and everything else either not booting at all, or booting and not letting me do much, and I've had it. I want to go back to the stock rom (which I downloaded off a megaupload link from a thread on this site), and I've already done it before, to repair my phone after it got so broken it wouldn't boot anymore, but this time it won't let me.
I noticed something odd. Normally, when a captivate with a stock rogers rom is booted, it shows the phone model number, then the animated rogers boot screen for about one second, and then the samsung galaxy s animated boot screenshows up, with the boot jingle, and then you use the phone.
Now, the phone inverts the boot screens, with the galaxy s animated screen showing up before the rogers one, and then the screen goes black where it should let me use the phone as usual. Only once was I able to see the regular lock screen and even then I couldn't use the touch screen at all.
I also often get stl10 errors after flashing the stock rom, and using the captivate pit file doesn't help either.
I tried flashing with both heimdall and odin and I have no idea what to do anymore. the stock rom is much more stable for my phone, and I miss it badly. it might be slower and also android 2.2, but at least it wouldn't self-corrupt like cyanogenmod does with my phone every 1-2 weeks.
I need your help with this. I obviously can't do it alone.
Click to expand...
Click to collapse
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
prbassplayer said:
Lets be clear you where on CM7 then tried other roms? then moved to stock? what roms wich stock and whats your build number?
Click to expand...
Click to collapse
last time I had bothered to update cyanogen, it was a week ago. I don't remember the exact nightly build. The other roms I tried were miui, apex and something else that wouldn't boot and which I deleted quickly (apex wouldn't boot either but I spent a couple hours trying to make it work). I wiped everything prior to flashing.
as for the stock rom, it's a stock rom for the SGH-I896 (I896UXJI2), my phone model. before, the stock rom worked fine. I just can't figure out why it's suddenly not working now.
anyone? I really want to put the stock rom back into my phone.
Are you using a PIT file when flashing? If not try using this one with that package then report back.
I've already did that with odin.
and just out of curiousity, what are pit files for?
everett1911 said:
I've already did that with odin.
and just out of curiousity, what are pit files for?
Click to expand...
Click to collapse
I dont know what it exacly does BUT I know if you want to repartition your phone and you are on a AOSP like CM7 or MIUI you need a pit.
P.i.t.
Partitioning
Information
Table
Lol makes sense now
Sent from my SAMSUNG-SGH-I897 using xda premium
studacris said:
P.i.t.
Partitioning
Information
Table
Click to expand...
Click to collapse
*windows user* so it's a bit like a batch fdisk?
if so, is the internal sd card itself supposed to be wiped clean? because it didn't happen when I used mine.
Ok so using the PIT file didn't work for you. I've seen several Samsung devices suffer from a problematic internal OneNAND in the past but never one a Captivate. It's always been a TAB, i9000 or Vibrant. Can you try flashing the base files used in the Serendipity ROM? It's the stock Gingerbread installed before flashing the Serendipity ROM itself. You can find them in that thread. It will help distinguish whether you have an actual issue or whether you just need some in depth CSC scripts to help clean it up. In general that ROM has a very nicely built CSC cleanup script that is able to correct what I call "partition bricking" on the Captivate, i9000 and Vibrant. Give it a shot and report back...
Also, if that won't work, I have been able to correct this via JTAG. PM me if it comes to that. If JTAG won't correct it, then it is indeed a case of a partially dead OneNAND. It's rare but does happen.
I'll give that CSC script thing a try. What's JTAG, by the way?
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
anyone, please?
everett1911 said:
nevermind, I figured out what jtag is.
Now, I'd like to know what the stl10 partition is for, since it's the one I get errors from the most when trying to flash back to the stock rom.
Click to expand...
Click to collapse
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
For2ndtwin said:
See here and here
dbdata.rfs ( /dbdata RFS Partition) /dev/block/stl10
cache.rfs ( /cache RFS Partition) /dev/block/stl11
I know these explanations r from i9000 threads, but hopefully it will give u the answer.
The "stl10" error was because the i896uxji2 firmware package that u were trying to flash, with the Repartition selected, does not contain the dbdata.rfs. But the i896uxjl1 firmware (Froyo) has the dbdata.rfs that u need to have when u select repartition. So, just use the link in my signature below to get to the Heimdall i896uxjl1. Select repartition and the other files, etc. and flash. U should be good to go. Then afterwards, u can go to uxji2 without the repartition, if u desire.
Thanks to hardcore for this explanation and solution.
Click to expand...
Click to collapse
thanks but I think it's too late. while trying to flash serendipity two days ago, I used the odin flasher that site linked to, and it flashed my phone with at&t's firmware, which somehow completely ruined my phone. now, the phone won't boot, and I can't enter download mode at all. I'm not sure even a usb jig would help, and right now I don't have money for that, so I'll have to wait till I do.
And if this doesn't work, then what? All the phone does is show a spinning little circle, immobile for 3 seconds, and the phone turns off. when I insert the battery (after pulling it out), the phone automatically starts with the same screen, same result. if I plug in the usb cable, it shows the charging battery indicator, freezes, and reboots. This repeats over and over, with no end at all, and since I can't enter download mode in any way so far, I can't do anything about that. It's so bad that not even windows detect my phone, and I've plugged it into two separate computers, so I know it's not just my pc pulling a trick on me.
The worst part is that since I was using wifi tether on my phone (hello, pdanet), now I'm without any internet (right now I'm typing this on my little sister's laptop, from my dad's place.)
So... yeah.
By the way, the heimdall link is for i897 phones, even in the post for i896 phones. Is there any risks my phone will react as badly as it did with the at&t firmware?
^ I've read good things about Heimdall. Btw, if ur phone has any signs of life, then a Jig should get u back into download mode.
The fact that it was at&t firmware has nothing to do with it. Running I897 firmware on an I896 is fine. **** you can run I9000 firmware...
so many days after, I still can't get it into download mode at all. all it shows is a spinning circle, a spinning circle and then the charging battery image for a second when the usb cable is plugged in, and the AT&T world logo when the battery is low.
I could go for a solderless usb jig but even then I don't have cash for that right now (next week.), so until then I'm screwed.
I tried everything minus the usb jig, looked for many threads on the topic, and nothing works. nothing.
no matter how many times I do the battery trick or the three finger salute or the odin stuff, and it still doesn't work.
so... yeah. that usb jig better damn work.
I'll call it magic
First, I'd like to thank 4-2ndtwin for providing a complete stock rogers rom.
Second: how does a usb jig work, really? my thing's computers, software and hardware in general but not to the point of knowing how capacitors, resistors and all that stuff works, so for me the usb jig bringing back my phone from firmware limbo... that's magic. seriously.
Ok I have a stock KB2 Cappy. I used Odin to flash back to 2.1 KB1 JF6
Then I used Odin 3 to flash a kernel so I can put on CM7. I am now stuck in the Boot screen.
I have no 3 button, I cannot get into download mode (my jig is homemade should i order one?)
I tried to change usb and remove the sim card to try odin again to get back into stock.
Nothing seems to work the only thing is my jig is not good either for DL Mode. I want to get back to stock so any suggestions. I tried heimandall did not work either.
I am really stuck on this galaxy s I897 screen.
Is the jig soldered? If its not make sure you are connecting the correct pins and use some black tape or something to isolate your fingers from the resistors (might screw up the actual ohms making it to boot up normally and not in to dl mode.
The bootloop was expected, you are supposed to check that you have a working button combo both before you flash the kernel (because it will bootloop and you boot into recovery and flash whatever) and before you ever flash cm7 because that is the only way to get into download mode besides a jig on aosp roms.
so, fiddle around with your jig some more and if you get it in download mode just flash the captivate gingerbread bootloaders, that will fix your button combo and allow you to proceed flashing cm7.
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
This is probably the easiest guide on how to make one. Layman Jig First one I did I butchered a pare car charger to make it. You can just grab one from MobileTechVideos.com for about $8.
AlphaJ1 said:
Hi Guys,
I have a similar problem. I am a total noob-I've had my I896 cappy (Canadian Rogers based) for about a year now; i fiddled with it on Saturday and also got the bootloop. I freaked out, and managed to further flash (out of frustration and confusion) the cappy with another wrong ROM, the I900. I managed to get it back into DL mode and tried flashing stock eclair or 2.2 froyo via ODIN. For some reason, whenever I start the flash (press start on Odin with the froyo 2.2 file on PDA), the progress fails at the factory section. I don't know much about jigs yet, but any tips would be greatly appreciated.
thanks
Click to expand...
Click to collapse
Hi guys,
Thanks for the link.
From what I understand, a jig is an improvised connection that allows your phone to go into DL mode. What if my phone is still capable of going into DL mode? My apologies, as I am at work.
Im not sure what you mean with your question. What the jig does is give the signal for it to go to download mode as was intended by samsung. Same theory on how your phone knows its connected to your computer, or the wall or the car charger. Its by manipulating the current between 2 pins. Keep in mind your phone should always be capable of going in to download mode assuming the hardware is working and your bootloaders are in working order.
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Read my post after yours...
studacris said:
Chord in the back of the PC directly attached to the motherboard NO EXTERNAL HUBS, right click on Odin run as admin.
Once you have it working READ AND UNDERSTAND WHAT YOU'RE DOING, BEFORE DOING ANYTHING ELSE TO YOUR PHONE
Click to expand...
Click to collapse
^What he said. If that fails could be a faulty cable.
AlphaJ1 said:
I believe I read it on a different website that as long as your phone can go into download mode, then it is only "soft-bricked," meaning it can still be recovered using ODIN. I don't know If I was misinformed or not. I guess my question is, since my phone is still able to go into download mode, but the flash is still failing, did I DL the wrong ROM, or was the copy of Froyo 2.2 I DL'd corrupt? If so, is there a reliable source/site where I can download Froyo or Eclair?
I hope that makes more sense.
Click to expand...
Click to collapse
You are correct, if you can get into download mode you are not bricked. Make sure you are using the usb cord that came with your phone, plugged directly into the back of your computer. Make sure your SIM card is out, you're logged in as an administrator, and that you start odin before you plug your phone in.
If it still doesn't work, try another computer and/or another cord.
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
That is a practice from way back in the winmo days, sometimes the flash would corrupt the Sim itself. Not the case anymore for the most part. I'm with you never take mine out either.
Thanks guys, I will try this at home; hopefully it works.
prbassplayer said:
Why do people say take sim out? Ive never taken it out and had no issues. Just curious.
Click to expand...
Click to collapse
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
apbthe3 said:
I say it because, while I've never had it screw up the SIM itself, I had a situation where I forgot to remove it and then couldn't get odin to complete a flash on several attempts, resulting in a soft brick that I couldn't flash out of. As soon as I removed the sim, Odin flashed without an issue.
Coincidence? Maybe, although I didn't change anything else. If it possibly keeps me from repeating this terrifying event, though, I'll just keep doing it
Click to expand...
Click to collapse
Did you get a red "FAIL" message on ODIN? Because thats what I got several times. My buddy also tried and he got the same thing. The green progress bar completes up till about 80 percent and gives up on me. I'll try taking out the SD and SIM cards when I get home, hopefully it works.
Hi guys, little update:
I found this on the forums and used it:
http://forum.xda-developers.com/showthread.php?t=731989
Anyways, this worked after my second try. Interestingly enough, it worked once i removed the Sim card, which is what apbthe3 suggested..great! I'm just glad my phone is no longer bricked. Minor issue though, my phone is now an AT&T phone, but unfortunately, I am a Canadian Samsung user. New problem now. My phone is no longer rooted (never was actually, but was bricked in the process), I'm happy it works, but i need to know if there are any Canadians out there that know how to revert my device back to Rogers.
Any help would be great. Anyways, the link I provided works great, so its a great resource for our American friends.
Why don't you look at Cognition 4.x.x? Froyo stock ish looking rom tweaked out the ass very fast. Good rom.
Look in development. There are a couple of threads there just for Rogers users.
Ok so I purchased an i9000M that was advertised as broken (got it for cheap) to see if I could get it going for my step daughter. I turn it on.... I get the samsung boot screen and goes black when it should be booting OS.
Windows still recognizes it somewhat. If I look in device manager under "portable devices" It shows a "j" and "k" drive that are identified as i9000 and i9000 sd or something like that. Although Windows sees it.... It wont mount these drives unfortunately.
Things I've tried ( Before someone suggests I use a JIG............. It doesn't and will not work on this phone)
USB JIG (tested and working on my Hercules)
SD Card Partition (EXT4 and FAT32) because I suspect borked internal storage
SD Card Partition (ReiserFS and FAT32) Still nothing......... then I realized the phone probably wasnt rooted
3 button combos ( every single combination) nada
plugging in USB cable while holding volume up and down...
ADB Reboot recovery/download ( not recognized because I cant turn on debugging)
ETC ETC ETC........
I have been searching google for hours for some kind of clue as to what can be done other than JTAG repair and All I come up with (no matter what site im on) is " Use a USB JIG" duhhhh Its getting rather annoying.
Im no stranger to flashing ( no expert) but this one has me stumped. I was considering buying a RIFFbox anyways but I thought maybe some experienced users out there might be able to suggest something.
My hope is that something can be done with the J and K drive that was mentioned. Perhaps I can format and somehow push a rom straight to the internal storage without any assistance from the phone itself...... I know..... wishful thinking. or perhaps boot straight from external SD???? That would be interesting!
More to this.... I realize this question has probably been asked a million times because it seems to be a common issue on this phone but I suppose my long winded question really boils down to my last paragraph which I havent seen suggested yet.
EDIT: I have a Windows 7 AND kubuntu 12.04 dual boot if any suggestions require linux
Any help would be greatly appriciated.
kibosh1981 said:
Any help would be greatly appriciated.
Click to expand...
Click to collapse
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
xsenman said:
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
Click to expand...
Click to collapse
Thanks. i will have a look and experiment tomorrow.
I'll report back my progress
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
taz0697 said:
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
Click to expand...
Click to collapse
As I mentioned.... no download mode, therefore.... No ODIN. Unless someone has some magical way to make it work otherwise. The computer knows its an I9000 at least. Kies says its in the wrong mode and I have no UI so debugging is out of the question.
Also: Xsenmen. I was unable to get any of the tools to connect. In one section you mention that AndroPlatina attempts to connect while booting? I was unable to get this to happen. I even tried the "heat trick" to no avail