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] Stuck on logo screen suddenly. Ideas?

Hi,
Last night my Galaxy S was low on battery, and I kept trying to turn it on for it to die right away (it was working as expected I guess)
This morning after I charged my phone it wouldn't turn on at all! It loads to the logo screen, makes that jingle sound and then holds and doesn't turn on.
I can get to recovery and download mode.
I put OCLF on like 2 months ago, but haven't modded/flashed ANYTHING since. It is very bizarre how it just died.
I'm wondering what my options are now. Obviously I would rather not loose all my personal files. Since I can get into download mode, can I just flash a new firmware? I'd like FroYo anyway, but I haven't got a clue what to do.
Great start to the year – !
Cheers,
Mitch
EDIT: I just decided to try the "Clear User Cache" option and then reboot to no avail. Now I can't get back into recovery mode!?!? Download mode still works. Huhh?? Is this expected? Have I lose Recovery Mode entirely now? Crap.

seeeems like an odin flash via the download mode is the only way. There are a few tutorials on this site and even tut vids on youtube so you should be fine if you just follow everything they do (as long as it works for them of course)

How do I know what version to flash? I have read a few tutorials and they all have started with "Dial x and check you have y" etc. Obviously I can't do any of that.
What is the *safest* firmware I can flash?
My phone currently has some optus variety.
Please forgive the noodish question.
Mitch

Where are you located? And who is your provider?

Hi,
I'm in Sydney Australia and my provider is Optus.
Thanks

Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You

m1tch37 said:
Hi,
I still can't get my phone working and am not clear how to proceed.
What would be the best firmware to flash to my Optus Galaxy S that bricked out of the blue? Should I just send it back to Samsung?
Thank You
Click to expand...
Click to collapse
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.

Sounds like you'll need to do a flash of a stock rom..
By the way, the old oclf had some issues that might lead to system corruption (unfortunately I'm not very sure exactly what it does, or whether it could lead to this problem). I'd suggest getting one of the newer lag fixes available here when you do get your phone running again

tragusman said:
Hey mate go to samfirmware and get I9000DTJG4 thats the stock optus rom once you get phone up and running then upgrade to 2.2.1.
Click to expand...
Click to collapse
tragusman has got it right. Depending on what the issue is, you'll either recover nicely or your phone is toast. Flash the above stock firmware and give it a shot. Note that you'll likely loose your data and settings.
If you're new to flashing firmwares, check the great reference guide on where to find Odin and how to use it (this is the app you'll use to flash the above firmware).
http://forum.xda-developers.com/showthread.php?t=723596
After flashing, try getting into recovery mode. If you can look for an error message under the standard menu. Can't get to d/l mode? You're probably in trouble. Get into recovery and see an error msg? Post the error here or google it for a solution. No error msg? You're probably ok - restart the phone.
Good luck.

Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch

m1tch37 said:
Thanks guys.
I'm about to try it now, but before I start potentially breaking my phone even more, I was just thinking: Could I just send it back to Samsung? Would they fix it, or identify right away I have changed something and void my warranty.
Mitch
Click to expand...
Click to collapse
If it's broke, you can't break it any more I've sent phones back in for support after flashing back stock firmware (flashing it after it "died").

[Q] Bricked L90

dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.

You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.

linasj said:
You have probably the worst case of them all. I suggest you to take your phone to warranty and see if they can replace it (because there probably isn't any way to fix it). If your warranty is void, then, I'm afraid, you will have to get a new device. I have had this issue myself, and it was solved only by replacing whole internals of the phone. Good thing that I still had my warranty, so it didn't cost anything. Good luck.
Click to expand...
Click to collapse
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?

wmosquini said:
but this happened to you because of flash ROMS? How long on average it took for you to get the unit back?
Click to expand...
Click to collapse
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.

linasj said:
Yes. I tried to flash a ROM (which requires an unlocked bootloader), but for some reason the bootloader wasn't actually unlocked, and flashing a ROM caused the device to be bricked. This is probably what you would call a hard-brick.
In my case, replacement took a little more than a week. But this could differ from country to country.
Click to expand...
Click to collapse
But in time to take the assistance, you said what about it? The unit stopped working alone?

wmosquini said:
But in time to take the assistance, you said what about it? The unit stopped working alone?
Click to expand...
Click to collapse
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.

linasj said:
Exactly. Since the device cannot be turned on, I don't think they have any way of checking if it was rooted or tampered with in any way. So your best bet is to just play dumb and tell them your phone doesn't boot up. That helped me to get it fixed for free.
Click to expand...
Click to collapse
Legal, tomorrow I will even take the guarantee to solve as fast as possible. Really the device not the sign of life at all. I will inform you that the device was carrying at night and just when I catch him in the morning, he was like that.
Thank you for your help. : D

My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck

bacitoto said:
My first L90 didn't have a functional GPS, was brand new (1 week), problem was I rooted in the first day
Factory reset, hid superuser app, got a new l90
Gud luck
Click to expand...
Click to collapse
hard reset does not remove all traces of root. There is RCT checking. u can be sure that have no traces of root when RCT was reset. On kit kat we have chance to reset it without reflashing. But on 5.0 only reflash
---------- Post added at 11:17 ---------- Previous post was at 11:11 ----------
wmosquini said:
dear, sorry the English, but I need a help from you.
I made the installation of IMG extracted the KDZ and did flash the recovery, however, now my machine not the sign of life, the computer does not detect the device, the device does not turn on, not of any sign of life. already tried in various corners anything to help me have some solution. I did the procedure based on the stock rom flash D405 with img extracted files. After that the only active device the display if I put to load without the battery, which displays the battery with a question mark. The device does not enter download mode, does not go into recovery, does not display anything, as if completely dead. Does anyone have aware and know any solution to the problem? Note: I've tried the LG flahs tools, it does not detect the device.
Click to expand...
Click to collapse
Did u flash it from 5.0 or 4.4? This problem may have solve without service center. But if u have warranty, it must not worry u.

@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.

No, I don't think I ever got this message.
Sent from my LG-D405N using XDA Free mobile app.

pick.orion said:
@linasj
Hello, I just want to know that while booting, did your phone show the message "Secure booting error"?
I am getting this message at the LG logo and then device just shuts off.
Click to expand...
Click to collapse
In my case, the device did not care and neither carried, gave no sign of life. I sent him for assistance in less than one week they made the repair by warranty.

Need help with stucked S7

Hi
I recently tried to root my phone from this guide: devs-lab.com/root-samsung-galaxy-s7-s7-edge
I followed the instructions and flashed this file from ODIN:
Samsung_G930x_QC_Rooted_BOOT.TAR
The file transferred ok and when the phone started rebooting it just stopped with a fault message on the screen.
Now the phone is stucked and i can't get contact with Odin. Odin recognizes the phone on the port but i cant flash to the phone.
The only way i have a chance to install on the phone now is with SD-card, because i am able to get to the recovery mode.
But when i try to install new stockware i just get signature failed message.
Does anyone know how i can get out of this mess ? I know its possible to turn of the signature check, but i cant get any options like this in the menu ..... BTW the phone is a G930F
I would really appreciate all help !
Thanks
Tom

Tom-72 said:
Hi
I recently tried to root my phone from this guide: devs-lab.com/root-samsung-galaxy-s7-s7-edge
I followed the instructions and flashed this file from ODIN:
Samsung_G930x_QC_Rooted_BOOT.TAR
The file transferred ok and when the phone started rebooting it just stopped with a fault message on the screen.
Now the phone is stucked and i can't get contact with Odin. Odin recognizes the phone on the port but i cant flash to the phone.
The only way i have a chance to install on the phone now is with SD-card, because i am able to get to the recovery mode.
But when i try to install new stockware i just get signature failed message.
Does anyone know how i can get out of this mess ? I know its possible to turn of the signature check, but i cant get any options like this in the menu ..... BTW the phone is a G930F
I would really appreciate all help !
Thanks
Tom
Click to expand...
Click to collapse
Which fault message are you receiving?
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
Which fault message are you receiving?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Hi,
I dont remember exactly the fault message because my phone has been sent to service. But i will get it back in a couple of days. Then i will tell you the entire message. But is was something about kernel fault....
The service center says i have to replace the main board on the phone which cost almost the same as a new phone....
But i'm sure the main board is not broken...
Tom

Tom-72 said:
Hi,
I dont remember exactly the fault message because my phone has been sent to service. But i will get it back in a couple of days. Then i will tell you the entire message. But is was something about kernel fault....
The service center says i have to replace the main board on the phone which cost almost the same as a new phone....
But i'm sure the main board is not broken...
Tom
Click to expand...
Click to collapse
Blah that's never good. Though I don't always trust things HAVE to be replaced at the hardware level. But it is what it is. Hopefully when you get it back all will be working for you! Unless it was just a bad chip, failing at the same time you were trying to write the new files to memory?
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
Blah that's never good. Though I don't always trust things HAVE to be replaced at the hardware level. But it is what it is. Hopefully when you get it back all will be working for you! Unless it was just a bad chip, failing at the same time you were trying to write the new files to memory?
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Well....
Actually i'm hoping to fix the phone withouth replacing the main board since it is so expencive.
So i asked them to return it withouth replacing. Because as long as i can get the phone in recovery mode its not broken. I just need to get pass Samsungs signature verification somehow... Then i can install new firmware...
Still hoping to get help. I will post the error message as soon as i get the phone back,
Thanks so far
Tom

Tom-72 said:
Well....
Actually i'm hoping to fix the phone withouth replacing the main board since it is so expencive.
So i asked them to return it withouth replacing. Because as long as i can get the phone in recovery mode its not broken. I just need to get pass Samsungs signature verification somehow... Then i can install new firmware...
Still hoping to get help. I will post the error message as soon as i get the phone back,
Thanks so far
Tom
Click to expand...
Click to collapse
I think I did the same thing when I first got the Phoenix, and did not research and do not turn the OEM Unlock feature on. I messed up things and through a lot of reflashing and panic searching, got mine to come back.
I since have seen others post issues that sound horrible but have been recoverable. We'll help you try to figure it out once you get the phone back.
Sent from my SM-G930P using Tapatalk

POWerSUrgeSW3 said:
I think I did the same thing when I first got the Phoenix, and did not research and do not turn the OEM Unlock feature on. I messed up things and through a lot of reflashing and panic searching, got mine to come back.
I since have seen others post issues that sound horrible but have been recoverable. We'll help you try to figure it out once you get the phone back.
Sent from my SM-G930P using Tapatalk
Click to expand...
Click to collapse
Hi, i finally got my phone back.
Been trying different things like installing new firmware by using the SD-card. And also by using ADB, since the phone allows me to install software through ADB.
But no matter what i do the phone tells that signature verification failed.
I think one fault i did when installing the twrp custom recovery from ODIN i forgot to press the key combo and it started up with the original bootloader. Then it got stuck with the error screen i told you about.
I have uploaded a picture of the error message below.
If anyone knows how to get by the signature verification test then maby i could be able to install new firmware....
Thanks again, i will be grateful for any tips that could help me !
Best Regards
Tom

Tom-72 said:
Hi, i finally got my phone back.
Been trying different things like installing new firmware by using the SD-card. And also by using ADB, since the phone allows me to install software through ADB.
But no matter what i do the phone tells that signature verification failed.
I think one fault i did when installing the twrp custom recovery from ODIN i forgot to press the key combo and it started up with the original bootloader. Then it got stuck with the error screen i told you about.
I have uploaded a picture of the error message below.
If anyone knows how to get by the signature verification test then maby i could be able to install new firmware....
Thanks again, i will be grateful for any tips that could help me !
Best Regards
Tom
Click to expand...
Click to collapse
Good NEWS !!!!!
I managed to get the phone working again...
What i did was:
Holding the volume down, home and power button at the same time. When the phone went black i plugged in the USB cabel from the computer.
The error message came up 2 - 3 times but i kept holding the buttons.
Eventually it went into download mode and i used ODIN to flash the firmware...
I hope this could solve the problem also for others facing similar issues.
Thanks to BWolf56 who posted in a forum here. His tips fom 2011 .... helped me.
Regards
Tom

Tom-72 said:
Good NEWS !!!!!
I managed to get the phone working again...
What i did was:
Holding the volume down, home and power button at the same time. When the phone went black i plugged in the USB cabel from the computer.
The error message came up 2 - 3 times but i kept holding the buttons.
Eventually it went into download mode and i used ODIN to flash the firmware...
I hope this could solve the problem also for others facing similar issues.
Thanks to BWolf56 who posted in a forum here. His tips fom 2011 .... helped me.
Regards
Tom
Click to expand...
Click to collapse
Great to hear... Good luck from here on out!
This is a good sign not to listen to tech support. They don't know, or mess with this stuff, as much as us!
Happy flashing and hope no more scares from here on out...
Sent from my SM-G930P using Tapatalk

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!