Hello. I have bricked i9300, International Version. It is currently stuck on batterry with spinning icon. Can't boot it.
Can't boot to recovery. Only to download mode.
In download mode can't flash anything using Odin - Always gives NAND Write error.
When I try flashing PIT I am stuck at Get PIT for Mapping.
Tried:
Different Odin Version (3.13, 3.12, 3.07, 3.05, 1.85)
Different Cables, Ports etc.
Nothing works.
In the download mode is:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
When I try flashing with Odin, nothing on phone happens.
CSC, ROM, etc. I don't know them. This phone was brought in Czech Republic, and was probally locked to T-Mobile (because boot animation). But any sim worked. Cant get the info now because bricked.
Thanks
How did the phone brick?
It could be a defective internal memory chip that is causing the problem.
audit13 said:
How did the phone brick?
It could be a defective internal memory chip that is causing the problem.
Click to expand...
Click to collapse
Also think that. Turned it off at night and left it charging. Btw it can be also sw problem because the phone was in awful state before.
It could be an eMMC problem. Mine died a week ago. Mine would boot into download mode and recovery mode. TWRP couldn't mount any partitions at all. Flashing firmware with Odin or repartition using pit file didn't work.
greglarson said:
If you are interested in GS3 and eMMC hacking you will love this talk.
Oran Avraham gives great history, explanations and hacking details on this problem.
Talk: 34C3 - eMMC hacking, or: how I fixed long-dead Galaxy S3 phones.
https://media.ccc.de/v/34c3-8784-emmc_hacking_or_how_i_fixed_long-dead_galaxy_s3_phones
Click to expand...
Click to collapse
I tried this guide, but the eMMC firmware dump sha256 sum didn't match the sample sum provided in the guide and I decided to proceed anyway. Mine is probably permanently dead now. You can ask someone to pull the 0xf7 firmware. Just be careful
Thanks for answers. I got it. It got suddenly bricked. It is 80% sure emmc dead. I am not interested in repairing because costs. Thanks for everything
Related
Hi all,
Samsung Galaxy S3 GT-I9300, UK, Orange
All stock firmware, updated to JB Novemberish time
Recovery mode works
Download mode works
PC will not recognise as mass storage, but Odin will recognise that an S3 is connected
So my S3 came down with sudden death before Christmas (annoyingly just 3 days before the fix came out) - it's stuck at the boot screen flashing 'Samsung' over and over. I can get into both recovery and download, USB mass storage fails but I think Odin recognises it's a phone. Tried all the very basic fixes like taking the battery out, wiping the cache, etc., haven't done a factory reset yet as I'm trying to save my data if possible as my backups failed.
I want to try flashing the phone with stock to see if this will fix it/possibly fix it without wiping my data at the same time (not much to lose if it's just going to be reset otherwise anyway) but I'm completely new to all of this and only learnt what the words Odin and flashing mean in the past few weeks.
So my questions are:
1) Should I flash the whole stock firmware found on Sammbile or just the boot recovery .tar file, what's the difference between these files and what is a 'resurection rom'?
2) If I should flash the whole stock, should I flash the ICS firmware that came with my phone or should I try the new ELLA one as it's an update not a downgrade?
3) Can someone walk me through which file goes in which Odin box please - PDA, PHONE, BOOTLOADER, etc.
Simple & thoroughly explained answers appreciated
if it's a sudden death, there's no way of recovering the data
Katanaqui said:
Hi all,
Samsung Galaxy S3 GT-I9300, UK, Orange
All stock firmware, updated to JB Novemberish time
Recovery mode works
Download mode works
PC will not recognise as mass storage, but Odin will recognise that an S3 is connected
So my S3 came down with sudden death before Christmas (annoyingly just 3 days before the fix came out) - it's stuck at the boot screen flashing 'Samsung' over and over. I can get into both recovery and download, USB mass storage fails but I think Odin recognises it's a phone. Tried all the very basic fixes like taking the battery out, wiping the cache, etc., haven't done a factory reset yet as I'm trying to save my data if possible as my backups failed.
I want to try flashing the phone with stock to see if this will fix it/possibly fix it without wiping my data at the same time (not much to lose if it's just going to be reset otherwise anyway) but I'm completely new to all of this and only learnt what the words Odin and flashing mean in the past few weeks.
So my questions are:
1) Should I flash the whole stock firmware found on Sammbile or just the boot recovery .tar file, what's the difference between these files and what is a 'resurection rom'?
2) If I should flash the whole stock, should I flash the ICS firmware that came with my phone or should I try the new ELLA one as it's an update not a downgrade?
3) Can someone walk me through which file goes in which Odin box please - PDA, PHONE, BOOTLOADER, etc.
Simple & thoroughly explained answers appreciated
Click to expand...
Click to collapse
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
Fail to actually pick up your problem .
USB drivers ???
jje
chap rriespr
JJEgan said:
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
Fail to actually pick up your problem .
USB drivers ???
jje
Click to expand...
Click to collapse
Ahh thanks, I had a read of a few of these but I missed the 'for the ultimate noob' one
I've got the USB drivers installed correctly on my pc, I think the phone just won't boot up far enough to do whatever it does to be mass storage at its end.
I've tried pulling my files via ADB as well and nothing.
My problem is there doesn't seem to be a way of getting my data off my phone onto my pc as my phone won't boot. So as a long shot, I'm trying to fix the booting problem by flashing it, hopefully without wiping any data, so then I could boot properly and rescue my files.
My question is what would be the best way to go about attempting this: flashing the whole stock firmware file, or just the boot loader file?
SD means a dead phone impossible to do anything with .
Download mode yes then flash stock firmware via Odin ..
jje
JJEgan said:
SD means a dead phone impossible to do anything with .
Download mode yes then flash stock firmware via Odin ..
jje
Click to expand...
Click to collapse
I thought SD meant a soft brick, ie. stuck in bootloop but with the possibility of recovery/download modes, whereas a dead phone is hard bricked?
Ok thanks
Sd means "softbrick" or "sudden death" depending on who abbreviates it.
Sudden death is a full hardware brick ( no chance of recovery), softbrick can be fixed through recovery, download mode and/or jig
Sent from my GT-I9300 using xda premium
Hello xda community,
mainly my problem is in my Samsung Galaxy S3 (international) device, it's bricked !!!
Device: Samsung Galaxy S3 [international] 16GB
ROM: N.E.A.R 1.2 [ http://forum.xda-developers.com/show....php?t=2126059 ]
Kernel: N.E.A.K. Kernel 2.5
Yesterday i downloaded the Note 2 keyboard for Samsung s3, but after i flashed it i realized it was for the leaked rom, so apparently
it didn't work, and all was normal, after about 30 minuites, i was browsing on my device, the device suddenly restarted so it first shows
the first screen: Samsung Galaxy S3 Logo .... but nothing else ... Stucked on that screeN ... i'm pretty sure it's not from the keyboard ...
-restarted my device [returned to SGS3 Logo]
-removed battery [returned to SGS3 Logo]
-tried to enter recovery mode (CWM) [returned to SGS3 Logo]
-removed external SDCARD
-removed SIM nothing happened still stuck on that logo.
i can only enter the download mode so I :
-tried to flash a stock rom [4.1.2 and 4.1.1] using Odin [ with 3.07, 3.04, 1.85 versions], but odin keeps on saying FAILED with red color.
- downloaded the RESCUe FIRMWARE, followed the steps assigned here : [http://forum.xda-developers.com/show...35&postcount=6 ],
but odin says : failed to partition, invalid PIT.
- downloaded the CheckROM EvoHD [http://checkrom.com/threads/resurrec...%84%A2-v4.896/], ODIN > FAILeD
- found this thread [http://forum.xda-developers.com/show....php?t=1916796 ] and started with the steps assigned in the .pdf file but when I tried to flash the bootlaoder >>>> FAAAIL
NOW I THINK THE PROBLEM RESIDES IN THE FILE SYSTEM, i tried to re-artition with the below PITs,
- PIT section: I tried to re-partirion the device with three different files:
1) with the PIT: [http://invisiblek.chickenkiller.com/...-i535-16gb.pit ] i found it form here [http://forum.xda-developers.com/show....php?t=2075861 ]
2) with the PIT : [GT-I9300_mx_20120329.pit] , I downloaded it from xda (can't find the link).
3) and the PIT file that comes with the Rescue Firmware.
ALWAYS stuck on: "Get PIT for mapping" > after googling and xda-ing I 1) tried another cable, 2) changed the compatibilty to windows XP in the ODIN settings, 3) tried on an XP desktop >>> but still the same message "Get PIT for mapping ... "
That's all, i really appreciate it if anyone could find me a sloution for this issue.
-[ THNAKS IN ADVANCE ]-
Hmm seems to me more like a hardware failure of some sort.
So you flashed a bootloader and it failed? But you still can power up your device and go into download mode?
that`s also weird because normally if you screw up the bootloader your device shouldn`t be powering on at all (happened to me once with my old phone).
Did you have any other weird behavings of your phone? Like unusual freezing before the device rebooted?
Scarface1991 said:
Hmm seems to me more like a hardware failure of some sort.
So you flashed a bootloader and it failed? But you still can power up your device and go into download mode?
that`s also weird because normally if you screw up the bootloader your device shouldn`t be powering on at all (happened to me once with my old phone).
Did you have any other weird behavings of your phone? Like unusual freezing before the device rebooted?
Click to expand...
Click to collapse
Scarface1991 > my S3 just stuck on that logo screen, and there is noway to flash anything, as i mentioned upward: when i flash anything Odin keeps on telling me " FAIL " ... I don't think that the bootloader is screwed, because the device is powering up, and whenever I tried to flash anything it keeps on saying FAIL but only when i try to re-partition the device using a PIT file it do some processing and then on Odin will stuck on " Get PIT for mapping "
-[ BY MISTAKE I POSTED THIS THREAD IN THE !9305 TROUBLESHOOTING SECTION >>> AND I COPIED THE BELOW REPLIES FROM THERE AND DELETED THAT POST ]- -[ 15/4/2013 ]-
Cundis said:
First, this is the wrong place if you have the i9300. This is for i9305.
It's not cool when this happens. Excactly this happened to my mothers S3 also while it was in her pocket and not being used.
Only thing I could get it into was download mode. Otherwise stuck on Samsung screen. I did'nt try to flash something on it because she was afraid of her warranty.
When she brought it to the store they told her the motherboard needed to be replaced. Was not repairable at all they said. She was not rooted and got it for free.
If you live in EU there is a new law that states that rooting does not void guaranty. They have to proove that it was the root process that caused the brick.
I really hope you'll be able to solve this out!
Click to expand...
Click to collapse
> hhh my bad,
first thank you for your concondolences , and am afraid this is the only solution, but lets say the motherboard is corrupted or whatever > the whole device even shouldn't power up ... i don't know, i hope there is a solution for this ...
Reads to me like wrong firmware or kernel flashed and destroyed PIT partition .
A JTag repair may be cheaper than a Samsung repair .
quote
If you live in EU there is a new law that states that rooting does not void guaranty. They have to proove that it was the root process that caused the brick.
FACT that is not a new law and applies only to the vendor of the phone does not apply to any third party warranties like Samsung's limited warranty .
FACT if you are in the EU and your phone vendor says no warranty its rooted . You will have a job to get them to accept EU law and may need to take them to court .
Personally i would just act dumb and say you think it has the sudden death syndrome problem that's p[posted all over the web .
jje
Hello All!
My first post here, even though I have long been a lurker. I hope I'm posting in the right place. If not, apologies, and Mods - please redirect me, and I shall re-post in the correct place.
Phone: SAMSUNG GALAXY S3 GT-I9300 International version
Last known installed/running OS: Official SAMSUNG JB ROM (Unsure WHICH version) after having run on CM 4.4 for a couple of weeks.
PROBLEM:
a few months after going back to stock, Phone suddenly developed issues of random reboots. These would happen at any point in time, with no predictability whatsoever. One fine day, it rebooted, and wouldn't get past the Samsung splash screen. Pulling the battery and trying to restart phone resulted in the same stuck at Samsung logo issue.
Left the phone alone for a couple of months after this as I had a spare, but finally decided to try and revive the S3.
Phone does not charge when connected to charger. At least, it shows no visible signs of it. It DOES, however, try booting itself when plugged in, but gets stuck on the first screen of ODIN Download mode, instead of the Samsung logo splash screen as it used to earlier. Also note that this screen it gets stuck on is a pixellated screen, not the clear normally seen screen when entering ODIN mode.
The Vol UP, Home and power button combo brings me to this very same screen, there is no recovery menu to be seen, as would be normally. The Vol DOWN, Home and power button combo brings me to the regular clear ODIN mode as usual.
The headings at this screen read:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
I have read through most posts regarding similar issues on XDA as well as other forums, and tried flashing stock firmwares (single AND multiple part ones) through ODIN, with no success. The error i always get is as in the attached screen captures.
I've tried ALL versions of ODIN, and many PIT files. All were failures.
So, is this a dead for all purposes phone, or do I still have hope since ODIN mode is still available?
I don't think USB debugging was checked before bricking, because ADB toolkits just keep waiting for phone to be detected.
All drivers are up to date and installed correctly. Kies is not installed.
Any help is welcome.
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
I have a Device here which seems to have the same or at least a similar problem, however, i got it for free from someone else to experiment with, so there is no urgent need to repeir it.
I tried flashing a pit and erasing nand, but when i start to do it, odin just gets stuck at "erasing", if i try to flash a full firmware it just hangs at "getting pit for mapping" so i assume the nand is gone for good... however, i have one more dead s3 arround that seems to have a burned cpu, probably i manage to solder over the nand or the cpu
rp158 said:
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
Click to expand...
Click to collapse
ODIN stays at "Setup Connection" without any progress. I've left it overnight a few times, just to ensure I was giving it enough time.
When the cable is pulled, it reads "there is no pit partition"
@Mohanms04: I suppose, it's hardbricked
rp158 said:
@Mohanms04: I suppose, it's hardbricked
Click to expand...
Click to collapse
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Mohanms04 said:
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Click to expand...
Click to collapse
Try this recovery firmware, if not the jtag is required.
http://forum.xda-developers.com/showpost.php?p=30087735
My GT-I9300 international galaxy S3 gone brick itself, all of a sudden its stuck at the boot screen (white samsung ... text). I was using Cyanogen Rom 12 Unofficial Lollipop 5.1 for around 3 weeks (Everything Works Fine with few Lags and Reboots rarely in a day). I used various method's from noob to expert solution but didn't find success
Tried to reboot into recovery but no go, when i hold the buttons it just continues to reboot and reboot, only showing the white text.
Tried to reboot into download mode and that worked, i though fhew, i got a breath and not all is lost(Phone itself).
In Download mode,
It says : Product name = (Blank)
Custom Binary Download = No
Current binary = Samsung Official
System Status = Custom​
Tried to recover with kies, but it complains that it cannot install new firmware (after i downloaded the firmware, extraction, and all instruction followed).
Tried with odin (several original roms with my region and the one from kies) but with no luck, odin complains "There is no PIT partition.".
Tried to repartition with GT-I9300_mx_20120329.pit but then it does SET pit and hangs on "Get PIT for Mapping".
Tried One Click Method but failure is what resulted.
Didn't Tried JIG Method (will buy if nothing works).
Is there any chance to save my phone ? I'm getting really desperate here.
:fingers-crossed:A Beer is sure to one that gets my problem solved :good:
---Waiting for Good---​
So you just rebooted without changing ANYTHING before and then the device was stuck like you explained?
Have nearly the same problem.
Was using the original Samsung firmware. One day I want to power it on and I had the loop. It stucks on the white Samsung texts.
I cannot go in recovery mode, but I can go into Download mode. But whatever I try, there is no chance to flash an image with or without any pit-file. Always "There is NO Pit--Partition."
And: In my download mode, the product name is there. "GI-9300", no blank in my case.
Is there any chance to save our phones? :\
Thanks!
Did u try installing only a cm kernel through odin
This should bring you recovery
Bad news, blank PRODUCT NAME in download mode implies either broken motherboard, or at least broken eMMC, to the point that bootloader can't read board name.
Hard brick, don't waste your time, unless you want to replace eMMC or motherboard, which is currently not worth the money.
where to get PIT?
prabhu1980 said:
Did u try installing only a cm kernel through odin
This should bring you recovery
Click to expand...
Click to collapse
What is a cm kernel and where do i get it?
//edit: Cyanogenmod Kernel? I tried to patch "Kernel_Odin_I9300XXEMG5.tar.md5" with Odin, but it's still the same error. "There is no Pit-Partition".
JustArchi said:
Bad news, blank PRODUCT NAME in download mode implies either broken motherboard, or at least broken eMMC, to the point that bootloader can't read board name.
Hard brick, don't waste your time, unless you want to replace eMMC or motherboard, which is currently not worth the money.
Click to expand...
Click to collapse
In my case, it's not blank. It shows: PRODUCT NAME: GT-I9300
So I think, there is still a chance, right?
Nobody got an idea?
EDIT: Nevermind.
Model: SM-G900T (T-MOBILE, USA, 16GB EDITION)
My Samsung Galaxy S5 is rooted. But I am not sure what caused my phone to get stuck in the bootloop. As I have been rooted for about 2 years and its been working fine. Also I was not manually installing any updates, mods or anything of the sort. Just tried to turn on my phone one day and it was stuck on the boot screen ( Samsung logo).
When I try to go to recovery mode I get the error:
Movinand checksum confirmation fail
If I try to install stock firm ware I get(odin):
There is no pit partition
If I try to install pit partition with the firmware or twrp I get(odin):
Complete (write) operation failed
Also whenever I try to flash with odin on my phone I get the error:
Mmc_read fail
Anyone know what might be the issue? Been tryingd to fix my phone fore quite awhile now.
Also sorry I didn't post any pictures! I'm going try and get 10 posts as quickly as I can so I can post some pictures.
Any advice is appreciated! Thanks!
-aj
ajxabstract said:
Model: SM-G900T (T-MOBILE, USA, 16GB EDITION)
My Samsung Galaxy S5 is rooted. But I am not sure what caused my phone to get stuck in the bootloop. As I have been rooted for about 2 years and its been working fine. Also I was not manually installing any updates, mods or anything of the sort. Just tried to turn on my phone one day and it was stuck on the boot screen ( Samsung logo).
When I try to go to recovery mode I get the error:
Movinand checksum confirmation fail
If I try to install stock firm ware I get(odin):
There is no pit partition
If I try to install pit partition with the firmware or twrp I get(odin):
Complete (write) operation failed
Also whenever I try to flash with odin on my phone I get the error:
Mmc_read fail
Anyone know what might be the issue? Been tryingd to fix my phone fore quite awhile now.
Also sorry I didn't post any pictures! I'm going try and get 10 posts as quickly as I can so I can post some pictures.
Any advice is appreciated! Thanks!
-aj
Click to expand...
Click to collapse
Do you want the good news or the bad news first?
The bad news- it's a hardware issue. And of course being a hardware issue there's no fixing it. Mmc stands for multimedia card. So your entire internal storage/partitions are probably dead.
The good news though- the s7 is out.......
Darn, is there a test to know if it is a hardware issue for sure? Im mostly worried about important data I still have on the phone. Is there at least some hope to recover it ?
-thanks
Aj
ajxabstract said:
Darn, is there a test to know if it is a hardware issue for sure? Im mostly worried about important data I still have on the phone. Is there at least some hope to recover it ?
-thanks
Aj
Click to expand...
Click to collapse
I can confirm it is indeed a hardware issue. An MMC read fail error means there was an error reading a file or files on the MMC chip. This could mean the entire storage chip is dead, or it could mean (and this is less likely based on the use patterns described) one or more parts of the chip were corrupted.
Either way, you won't be able to get anything off that phone, sorry. If you have an SD card in the phone, it should be fine.
If you're looking for new phones, I suggest a Nexus, they're easier to root and always get Android updates.