Database Develop

[Q] I think its Bricked..and odin doesnt work

hey guys i have a captivate that i tried flashing and was successful then i tried again and the screen went black. im not sure if my battery died during the process or what but idk what to do. I cant get into recovery mode, i can only get into downloading mode but none of the odin's ive downloaded have recognized my device today. they worked fine yesterday. then i tried "hemidall one click" to try and get it back to stock but no luck. also when i try to power on I get the "Cornkernel" loading screen since that was the kernel i had loaded when it was working, but it fills the bar then shuts off. so it seems like im going to be at the mercy of a computer program since i am unable to access anything on the phone, right? I recently upgraded to gingerbread before all of the flashing of the new roms. all i want is to get back to either froyo or gingerbread, i dont really care, heck ill even take 2.1 at this point. if anyone knows whats going on and can help me thatd be great.
Thanks

Remember to use a rear usb hub for destop and run as admin. Heimdall will mess up your odin drivers.

You may also want to check out the captivate connection issues thread.
Also, to clarify further on prbassplayer's point about Heimdall, it will write its drivers over the drivers assigned to the USB port you are plugged into when it detects your phone. So if you have 4 USB ports and you use port 3 for Heimdall, it would look like this:
1 - Odin port
2 - Odin port
3 - Heimdall port
4 - Odin port
All this means is that you'll need to be aware of the port you used with Heimdall, or just reinstall the odin drivers (they'll overwrite the Heimdall setup).

OK so i tried what you mentioned in that thread on the connection issue and unfortunately it didn't work. is there a way i could start fresh? like delete all the drivers from my computer and then try it again, or do u not think that would work? im open to any ideas/suggestions right now because i hate having an extra paperweight and the thought of buying a new phone.

Don't know if this'll help or even why it worked for me but, when I had problems with odin recognizing my phone, I reinstalled/repaired samsung kies and odin would work for at least one flash.
Note: used full odin (not oneclick)
Good luck

hey guys thanks a bunch i finally got it to work. i had to use a different computer like you said. What a great feeling to have a functional phone again..
Thanks Again!!

So i got the phone back up and running android 2.1 and I would like to get it back to the stock 2.3 I had before the whole mess of rooting and stuff. but when i try to upgrade with kies or straight on the phone it ends up failing and telling me to try it again. any ideas why this is happening? or how to fix it.

blackjack54 said:
So i got the phone back up and running android 2.1 and I would like to get it back to the stock 2.3 I had before the whole mess of rooting and stuff. but when i try to upgrade with kies or straight on the phone it ends up failing and telling me to try it again. any ideas why this is happening? or how to fix it.
Click to expand...
Click to collapse
Kies sucks lol
look at my sig the first "go to" has the One Click Odin file to get you to stock and rooted 2.3 ...should take no more then 5 mins to do it

the link on that page for the 1 click odin doesnt work.

Try looking >>HERE<<. There are more one clicks there than you will ever need (hopefully)

Thanks I think I might try one of those. But considering what happened earlier in the week i want to clarify/ask a few ?s about that page. How do I know which Gingerbread to use of the 3 listed? How do I know whether or not to click the one with or without the bootloader? I'm new at this with android but I used to flash roms on my old windows mobile htc TILT.

blackjack54 said:
Thanks I think I might try one of those. But considering what happened earlier in the week i want to clarify/ask a few ?s about that page. How do I know which Gingerbread to use of the 3 listed? How do I know whether or not to click the one with or without the bootloader? I'm new at this with android but I used to flash roms on my old windows mobile htc TILT.
Click to expand...
Click to collapse
if you have never flashed GB bootloaders, you need to. Just oonce will work from that time forward. After you flash bootloaders, it's best to avoid them. A bad bootloader flash is one of the few things that will turn a Captivate into a paperwight. About which GB to use, I would say KK4. Its the same as the Official KK4 that was released. So to recap, flash bootloaders only once, then use no bootloader packages after that.

Im not sure if I unlocked them or not honestly. I know i had the phone rooted at one point and was running Cerberus rom. is there any way for me to check?

If you don't know, flash them.

ok i apologize in advance if this is a stupid obvious question..i got the odin one click and i was looking at the page u referred to me to and im wondering what the kernel is for? you cant place it in the odin one click obviously so is that just to keep things together or do i actually need it?

The kernel links are just to use if you want to root the stock rom. You have to use full Odin for those. Stick with the one click until you feel more comfortable in flashing AND do a lot research before your next flash.

so i got the KK1 gingerbread working and everything seems to work fine but now my data doesnt work. So I cant get ATT 3g or edge or anything the only internet i recieve is wifi. anyone know why this is? or how to fix it. ive tried a reboot and nothing ive tried changing the settings under network settings.

[Q] Forgot USB-debugging downgrading

Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh

emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?

arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:

emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]

th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..

SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:

emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!

[Q] Computer won't recognize device after flash

I am a beginner at this, so bear with me. I had an old HTC One lying around that was somewhat in a non-working state. Not as a phone anyway as it constantly lost service. Someone told me that it might perhaps be a software issue and if I rooted it and used a different ROM, it could fix my problem. So, for the first time, I gave it a shot. I tried a bunch of things, followed many tutorials, but I couldn't gain s-off on the device. Finally, someone said since my hboot was version 1.57, I would need to use sunshine to accomplish my goal. I did so and it worked. So now I followed another tutorial which showed how to make it a google play edition device. So I flashed the RUU and it failed the first time around. I tried again as the tutorial said I would have to only to get another error. My computer said it was waiting for a device. Basically my problem is that now when I'm in fastboot mode, my computer won't recognize it. When I boot it normally however, it acts like usual. I've visited other suggested threads on these forums, but to no avail. I've tried other chords, I've updated drivers, I've gone into the device manager and did just about everything suggested. So I've come here for one last try. If anyone could help that would be greatly appreciated.

Sir,
Please wait until mods will move this thread to the device specific forum.
For reply or more questions please register an account on XDA forums.
Stand by
Good luck

Thank you for your assistance in moving my thread to the correct location. I'd also like to note that I read quite a few articles where people seem to have the same problems as I have or have had, but none of them seem to help. Just so you know I didn't run straight for the post option and actually put some effort into finding my solution before hand.

[Q] ****URGENT****Please Help

Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.

[OP] Photo of Camera Issue
Here is a photo of what I mean by the Camera color dilation. Demonstrated by a couple of Multi-Color Expo markers.

Download the G900A_Downgrade_to_NCE.tar from here:
https://www.androidfilehost.com/?fid=23622183712464416
Use Odin 3.09 and flash in AP slot. Once it is done then take the OTA for NG3 then OA1
Thanks to @muniz_ri

Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.

ElectricBiskitz said:
Tried it once before. It didn't work, ended up with a bootloop after flash of NCE.
Click to expand...
Click to collapse
Did you use the same file from the link I provided?
Sent from my SAMSUNG-SM-G900A

I have used the same link you provided.

ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
*UPDATE*
Fingerprint scanner does not work anymore either. Camera fixes itself if you change a setting and put it back.

[OP] It's Fixed!
ElectricBiskitz said:
Recently, I have recovered from a bootloop when trying to install an older stock Android for my SM-G900A. I now have the original, UCU1ANCE 4.4.2 Firmware. I flashed it through a stock OA1 Kernel with Odin 3.09. Here's the issue.
I need all the help I can receive because I am desperate at this point.
[PROBLEMS!]
1. With my sketchy way of installing an older version, I triggered Knox which keeps telling me to reboot my device, but since it can't repair it on it's own, it continues to give me this error no matter what I do.
2. I've already tried to do the procedure where you Backup all info through Kies, format device, then Recover, but for some reason I can't even connect my device to Kies, it keeps telling me my device is not supported, I've also tried everything in that area to fix it. Still no luck whatsoever.
3. When I try an OTA update, it downloads, tries to install, but when it returns to the home screen it continues to tell me that the process was interrupted by something and it could not be installed.
[OTHER BUGS]
1. Every time I reboot or turn on my device, the WIFI does not automatically connect. It is my personal network and there's no doubt it should work.
2. Camera. When I open the camera, the color of the picture is dilated. The colors that should be where they are, are instead randomly scattered about the image, making those (what should be colored) areas black and white.
As I said I am in desperate need to find these things fixed. I can't find any solutions online for these. It seems like I'm the only person in the world with these problems, and it's not fair. If anyone can give me a solid solution, I would love you forever. THANK YOU.
Click to expand...
Click to collapse
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.

ElectricBiskitz said:
Thank you for helping me with my problems. I did realize when I came back to the forum a couple of hours ago that my NCE download was only a kernel and not a firmware. I flashed the link provided and voila! It's fixed. I hope others that may have this problem can use this guide as an example. Because let's face it, you're living on the edge with an Android.
Click to expand...
Click to collapse
I have the same issue exactly it says my bootloader is fused or something I have to flash the newest kernel to get it too boot up . I think I tried this already but can't hurt to try again .

Restore LG G4 LS991ZVC back to stock??

My lease is up got my Sprint G4 and of course I gave it ROOT a couple years ago. I have looked at several restore options but I am confused on which method I should use. I downloaded LGUP but the message I recieved was no handset found which obviously poses an issue. I am able to transfer files on my PC, but it won't set a PORT....when connected. I figured its the drivers so I downloaded the LG United thing but phone still is not recognized. I tried on my laptop and got the same thing.
Another issue is does anyone know where I can download the proper firmware to flash? From what I read, it looks like I can go back to LS991ZVB but I can't find it anywhere.
So my issues are:
PC won't recognise phone for LGUP
Can't find LS991ZVB firmware
I really need help. I just want to reset this phone and give it back to Sprint and be done with it. I haven't rooted a phone since this one so I'm a newbie all over again.

Try looking at the mellowmallow discussion thread. It explains how to get the phone to ZVB, I think.

dj10000 said:
My lease is up got my Sprint G4 and of course I gave it ROOT a couple years ago. I have looked at several restore options but I am confused on which method I should use. I downloaded LGUP but the message I recieved was no handset found which obviously poses an issue. I am able to transfer files on my PC, but it won't set a PORT....when connected. I figured its the drivers so I downloaded the LG United thing but phone still is not recognized. I tried on my laptop and got the same thing.
Another issue is does anyone know where I can download the proper firmware to flash? From what I read, it looks like I can go back to LS991ZVB but I can't find it anywhere.
So my issues are:
PC won't recognise phone for LGUP
Can't find LS991ZVB firmware
I really need help. I just want to reset this phone and give it back to Sprint and be done with it. I haven't rooted a phone since this one so I'm a newbie all over again.
Click to expand...
Click to collapse
If ure just giving it back. To them screw it just factory reset it. And maybe hide . wait a minute. Ure not on zvb or c rooted. Not possible just give it back to em. No worries either way.