Database Develop

[Q] How to unbrick my I9000

Hi,
Unfortunatelly I started playing with my I9000 without reading enough and bricked my phone completely (?). If anyone can help please do so.
Description:
1. I tried to flash with Odin new firmware but after flasing and rebooting got message "unable to update media ...." (or something like that) When powering on I got only welcoem screen with phone name
2. I wanted to repeat flashing but Odin could not start reflashing (I still could go into Download mode)
3. I found at xda forum [STOCK ROM] Odin3 One-Click Downloader,
but I didn't notice that it was for Captivate (I thought it is just another name for I9000,now I don't know why)
4. I reflashed my i9000 and after reflashing got only At&t screen turning on and off, without possibility to enter into download mode.
Actually I'm stuck with this situation I feel really stupid, but by mistake I did what I did.
Is there any chance to help ?
Thanx in advance.

according to some users, you might get lucky, and might be able to recover
let your phone stay on on that loop, wait until it turns itself off
then try the 3 button combo again
if all else fail, contact samsung tech support, which will simply send you back to your cell phone place

I'll try but I'm not very optimistic

Waiting doesn't help - I tiried all possible 3 or 2 button configurations unsuccesfully.
Anyone has any other idea if antyhing can be done with the issue ?

The exact same thing happened to me. There is nothing you can do except to bring it back to Samsung. I brought mine back and they have to replace the whole motherboard

what did you tell them? is it going to cost you?

diehard2222 said:
what did you tell them? is it going to cost you?
Click to expand...
Click to collapse
I told them my phone cannot boot. Can they help to reflash the FW and see if it helps. They did and said phone still cannot boot after reflashing. Hence they have to change the motherboard. I asked and they say it's under warranty...

The shop where I had bought my I9000 sent it to Samsung - I will see what they do with it.

I have flashed a vibrant with a i9000S software but the radio did not work quite well. Since the two have different keys, now i cant get it to boot mode. i was able to get into recovery mode via ADB but all i can do is use vol to go up or down and not select an option. the device wont even get out of recovery mode.
Any help will be greatly appreciated.

Same
I did the exact same thing and couldnt get it to go past the AT&T logo i took mine to the samsung authorised repair centre and after 3 days and 49 dollars they fixed it. I dont know how they did it because i couldnt get USB to reconginise or download mode or anything just stuck on white screen but they managed to get it up and running.
So even though it cost 49 dollars to fix it via software method it is better then spending 800 on a new phone or 300 for a new chip which they originaly qouted me. So there is hope with proffessional services

now, the magic usb plug is avaliable in ebay, it can turn your bricked phone into download mode in a few seconds. really good!!!

Hehe... ...the magic is one usb connector an 301 kohm resistor
Br:25011
h***://factoidz.com/how-to-unbrick-your-samsung-vibrant-galaxy-s/

[Q] Can't boot without Charger/Usb

Hello
I had some trouble with a bricked SGS for about 3 weeks ago but got it on the run again with some flashing help.
Now i have this strange problem. If i turn it off or if it just goes black out, which it has begun to do after i flashed it, then it can't turn on, it just show the sun looking loading icon and then a empty battery icon and then turns off.
I can't load recovery mode with the combo, but i can make the download mode combo work.
But if i connect the phone with the charger/usb i recognize it and show that it charging up. Now it boot and shows the Galaxy I9000 model no. image.
Had tried flashing newer versions From XXJPO -> XXJPY -> XWJS3 and both with and without pre-partition and it still occur.
Now the question: Does any of you experienced people know this problem and can it be fixed somehow ?
Thank you in advance

First i would liik to charge phone for 24 hours and also check with another battery .
jje

JJEgan said:
First i would liik to charge phone for 24 hours and also check with another battery .
jje
Click to expand...
Click to collapse
The battery don't seem to be defected. Once the phone is booted with a cable connected, it goes without problems. It just will not boot without a charging signal.

Bump - Still actual

Try using Block 2 Odin method here to go back first to Eclair and if that works test phone then upgrade to Froyo .
jje

JJEgan said:
Try using Block 2 Odin method here to go back first to Eclair and if that works test phone then upgrade to Froyo .
jje
Click to expand...
Click to collapse
That happened to me a while back and I couldn't find a fix for it. Ended up doing the above and it resolved it.

Z3icon said:
Hello
I had some trouble with a bricked SGS for about 3 weeks ago but got it on the run again with some flashing help.
Now i have this strange problem. If i turn it off or if it just goes black out, which it has begun to do after i flashed it, then it can't turn on, it just show the sun looking loading icon and then a empty battery icon and then turns off.
I can't load recovery mode with the combo, but i can make the download mode combo work.
But if i connect the phone with the charger/usb i recognize it and show that it charging up. Now it boot and shows the Galaxy I9000 model no. image.
Had tried flashing newer versions From XXJPO -> XXJPY -> XWJS3 and both with and without pre-partition and it still occur.
Now the question: Does any of you experienced people know this problem and can it be fixed somehow ?
Thank you in advance
Click to expand...
Click to collapse
i agree wiv the suggetions frnds given.galaxy is hard to brick.i did all sort of unusual things an even uptodate lol.don worri m8 jus flash to older stock and hard reset.check the connectivity pins,to b clean even the battri pins.somtimes its best u format ur eternal xd on pc an format.and giving another hard rest makes things better.i had once formated my int sd on pc and the phone had emptied,then i flashed and things worked fine.personally sticking to stock rom is better if u dont wan troubles,cause every custom rom has som drawback an needs a lil knownledge to tweak it up.check kies if ur on it,i recomend download the recovery driver in it.hope u get some help.cheeeerzzzz

Same here...
Hello everyone,
I too have the same issue as stated in the first post.
I even had issue sometimes that when boot up.
The USB notification icon wouldnt turn off even if i wasn't connected.
Some threads suggested that I clean the USB port, which i did and nothing changed, even if it looked a little bit dirty in there (Hard to say since it is really small).
Now the USB port looks just as new but same issue: I cant power on the unit witout having it connected with a power cord.
Also, when offline in download mode, Odin detect the unit and I can flash my device (Which I did yesterday by flashing UGJH2 re-partition and UGJL2 not re-partition) but when boot up, I can't make it to sync up with the computer. No sync possible (Also now I'm not rooted anymore).
The unit is under warranty but since it is unlocked with a tool that needed rooting to lock back, abviously I would need to be rooted again but to do it, I need to be able to sync it with my PC (No cant do here).
I have some engineer at work that offered me to check it out for me, they think it is related with the USB port, but I'm worried about the warranty seal. I found how to disasemble it but does anybody knows where it could be located on the I9000M from bell (Vibrant)? Does it have one?
Anybody have any better suggestion or a second opinion, please?
Its my 3rd Galaxy S from Bell and Samsung is now the last company I would think when buying a new mobile.
EDIT: Did the Block 2 Method and now it doesnt even want to boot at all (Did the JPY_JPY_JPY.tar part), now it shows the loading sign even faster and the battery doesnt even show it self at all.

Hello again people!
Got my friend engineers to open the phone and they didnt find anything that would cause my issue (Also no warranty label...).
Does anybody knows how to root a Galaxy S with Froyo without a PC?
I want to return my phone to Bell Canada under warranty but my phone is unlocked and I want to lock it back before sending it back and I need to be rooted to do so...
Thanks for your help!

I got the same problem here. Could someone tell me more on this. What is this Block 2 ODIN method?

this problem can be caused by water or sweat that got inside the case of your sgs.
the biggest hole in the case is micro-usb port) i think condensation accumulated there and locked some contacts.
try to disassemble the phone and carefully clean and dry it.
this helped me.

[Q] Help screen wont respond after root mishap

Hi All,
Australin Optus GT-I9305 (4G/LTE Ver).
Android 4.1.2
Download mode: Binary dowload 3 - Current binary Official - System status Official
I tried to root my SGS3 today with Odin however I used the wrong root from my old Note 2 which caused the screen to do weird things and then the screen would not boot up or respond. I have reinstalled the stock software on it with Odin and now the phone starts up but still does not respond to my touch's.
I can boot into recovery and download mode no problem. I have cleared the cache and performed a factory reset still no response from screen. I am stuck in the first set up screen atm the menu key, back & home key all make sounds when I touch them.
If I unroot the phone will it fix this issue? if so how?
Is the phone gone/dead/unfixable?
Or can I use USB OTG to control the phone so I can use triangle away and return for warranty?
I also think USB debugging is off as well as I cannot get into the phone.
Any help will be really appreciated thanks guys.

Although extremely similar in hardware the screen's digitalizers are different causing issues like this instead of a plain brick that you would get if you tried a I9300 firmware. Try using Samsung Emergency Restore on Kies.
If that doesn't work then you may have to send it into a repair center as you could have, put bluntly, ****ed it.
Sent from my GT-I9305 using xda premium

I've read of several cases where people have used Roms or recoveries intended for the Note 2 on their S3 and it literally fries the screen.
It allows too much current through or something like that.
I think you will need to get a new screen mate.

Non responsive touch screen T710

Hi,
I have a T710 that's about 6 months old and had fairly light use.
Yesterday after charging up to 100% while off, it turned on only for the touch screen to fail to respond. The capacitive keys and fingerprint sensor and physical buttons all work perfectly, the tablet boots normally, and even responds to OK Google - but no touch is registered on the screen at all.
There is no screen protector on it and it has not been dropped or damaged. I noticed a day or two ago when playing a game that the screen was a little slow to respond, but put this down to maybe greasy fingers or a laggy game.
It is currently running a stock 5.01 Rom, although there was an update or week or two back - but I've had it working since then.
This happened once before about 3 months ago and I was in the process of returning it when I flashed a stock ROM through ODIN, which solved the problem and it worked fine until yesterday - this seems to suggest that it's not a hardware issue.
Before I go down the Odin process again and hence wipe it, are there any other things I can try that might work?
I've never rooted and the Knox counter is not tripped, so I could send it back under warranty, but that will mean sending it away and as I imported it from Hong Kong I don't know if Samsung will raise an issue (I'm UK based).
Previous googling when I had the issue before found a post or two suggesting that it was something to do with charging after letting it run down that led to others seeing the same issue - but can't find anything in this forum.

You don't need to wipe anything to flash with odin.
Just flash the latest stock firmware as is.
The easiest way to discover if it is hardware or software is to simply install TWRP.
However that will trip knox and potentially void the warranty.
The other test is to boot in safe mode.
Hold VOL DOWN while booting to the OS.

ashyx said:
You don't need to wipe anything to flash with odin.
Just flash the latest stock firmware as is.
The easiest way to discover if it is hardware or software is to simply install TWRP.
However that will trip knox and potentially void the warranty.
The other test is to boot in safe mode.
Hold VOL DOWN while booting to the OS.
Click to expand...
Click to collapse
I didn't realise that Odin flashing didn't wipe! Useful to know thanks.
I connected a mouse with a OTG lead last night so was able to back up what I wanted with Smartswitch - I then tried the device reset through smartswitch, which does wipe.
Unfortunately, that didn't resurrect the screen, so I've tried a couple of different ROMs through Odin since, with similar lack of success
Unfortunately, I don't want to find out that it needs warranty repair after installing TWRP and possibly getting that repair rejected because of a knox trip. Has anyone had experience of returning a knox tripped device with a screen fault and their response to it?
I'm going to let the battery run down fully and recharge to see if anything changes - as that is what seemed to work last time (don't ask me why though!)

Question SM-G998B Bricked

Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?

Seems different?
Well I would try Odin and an official ROM anyway, no pain no gain right?

What exactly were you doing before this occured?

You try the old delete usb driver, restart computer, install usb driver then restart computer and restart phone and try again.

SirDigbyCC said:
Hey guys, second time this issue has happened now for me but seems worse now. I used posts from here to resolve back in March when device got stuck in a boot loop after an OTA update, I managed to use Odin and a firmware from Sams Mobile to flash the phone and get it working again.
This time seems different though, I haven't tried the above steps yet, but none of the drives are mounting in the android recovery menu, which makes me think the device is going to need replacing. Anyone else come across this?
Click to expand...
Click to collapse
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something

flairepathos.info said:
there is never a bricked device for good just keep searching using very device speacific info, check on youtube and search the names exactly as the ypop up there will always be something
Click to expand...
Click to collapse
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.

To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.

SapphireEX said:
Looks like he bricked his bootloader's storage access driver, which AFAIK is unrecoverable unless download mode / sahara / etc is fine, but if the board is refusing to mount data while in the bootloader, it's safe to bet the rest of the modes are ****ed.
Click to expand...
Click to collapse
Oh I see the issue now you need to wipe all and re-flash full firmware when flashing the device using Odin
if that doesn't work flash the partitions with the kernel drivers and system partition
I had a similar issue with my current mtk phone and it was because the boot/preloader partition bilieved i had flashed the wrong firmware for my device(it was just a different firmware release for my phone
Just to be safe some ota updates break wehn the bootloader is not unlocked (when updationg from say android 8(oreo) -9(pie)...)
especially because of code errors in the update, cache/vendor partition being too full after downloading update

SirDigbyCC said:
To answer a few of your questions in one go:
When I flashed it before it was back in end of Feb so a good while ago.
Just before it went into this boot loop it was working normally playing music in my pocket while doing gardening.
Using ODIN this time failed as I don't think it could access any of the drives.
Click to expand...
Click to collapse
If you're telling the truth, and it wasn't a bad module / firmware / etc, it is possible your eMMC got too hot and melted some solder. I've seen it happen before.
You'll want to diagnose everything you can. If you're on Windows, does it recognize a USB device or a COM device? If linux, does lsusb return anything useful about it?
If it's not being detected, and multiple wires doesn't change anything, are you able to access sahara mode / download / DFU? If so, go to those and try again.
If you are lying, and this is a bad firmware flash / OTA brick, you'll need to tell us otherwise we'll be going in circles.

So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?

SirDigbyCC said:
So ODIN does recognise the device when in android recovery mode i choose the bootloader, but when starting it, it fails. I'll give it longer tomorrow but my inclination is it's a chip failure. I don't know hot to tell if it was a bad firmware flash, but the first (and only) time I flashed it was back in late Feb / Early March, and I have been using it fine with many OTA updates since then using the phone normally since. Before the boot loop I was playing music via Bluetooth speaker but the battery died while gardening, which the battery died on so played music directly on the phone (no update or anything) and the music stopped halfway through the song and it was in a boot loop.
I am taking the phone in for repair on Wednesday but it's really frustrating because I legitimately want to get to the route cause of the issues. I am covered by Samsung Care +, but I feel like if I screwed up the first flash, it's still only as a result of that first OTA update going wrong in the first place. Does that make sense?
Click to expand...
Click to collapse
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.

SapphireEX said:
I'm going to call hardware failure. It's extremely rare that any device will do what yours is doing without a bad firmware flash.. It's possible you had an OTA and it auto updated, then broke, but I doubt it.
Click to expand...
Click to collapse
I appreciate the vote of confidence, I don't think it was an OTA update that did it this time, it usually requests to do updates which I highly doubt I would have pocket approved through a flip case only short after pressing play on Spotify.

So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!

SirDigbyCC said:
So I have taken it into Samsung for repair and they have confirmed it's a hardware issue that feels vindicating!
Click to expand...
Click to collapse
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!

shriom_manerker said:
how much are they charging for the repair though? probably a motherboard replacement ? boy thats not going to be cheap!
Click to expand...
Click to collapse
It was free, turned out to be a hardware issue internally so I think covered by warranty as I have Care+ which has an excess of £40 which they didn't make me pay. They also replaced the screen due to some dead pixels, and the battery! Happy days!
Thanks all for your suggestions!