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.
Related
Hello all,
A friend of mine has a galaxy note 2 from AT&T. I'm not clear as to what exactly he did but he says he had it unlocked and had custom firmware on his phone and the phone did an update on its own and locked up, but by looking up on the Internet all signs point to a soft brick. The phone only turns on and displays firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. My dumb as volunteered to help him as I thought how hard could this be? Anyway Kies failed to help. Secondly I followed the instructions on here as far as downloading Odin, downloaded stock firmware, downloaded Samsung drivers. I plug it in a all appears good in Odin. Mp5 file checks OK and once it starts running there is even a progress bar on the phone showing its downloading but once it gets to the end it fails every time. The screen on the phone displays
Odin Mode
Product name sgh-I317
Current Binary Samsung official
Current status: custom
Knox warranty void: 1
RP SWREV: A3
SW REV: invalid magic string
Any help would be appreciate I've almost had it with attempting to help. He apparently didn't know what he was doing now I obviously don't know what I'm doing.
Thatguycurt said:
Hello all,
A friend of mine has a galaxy note 2 from AT&T. I'm not clear as to what exactly he did but he says he had it unlocked and had custom firmware on his phone and the phone did an update on its own and locked up, but by looking up on the Internet all signs point to a soft brick. The phone only turns on and displays firmware upgrade encountered an issue. Please select recovery mode in Kies and try again. My dumb as volunteered to help him as I thought how hard could this be? Anyway Kies failed to help. Secondly I followed the instructions on here as far as downloading Odin, downloaded stock firmware, downloaded Samsung drivers. I plug it in a all appears good in Odin. Mp5 file checks OK and once it starts running there is even a progress bar on the phone showing its downloading but once it gets to the end it fails every time. The screen on the phone displays
Odin Mode
Product name sgh-I317
Current Binary Samsung official
Current status: custom
Knox warranty void: 1
RP SWREV: A3
SW REV: invalid magic string
Any help would be appreciate I've almost had it with attempting to help. He apparently didn't know what he was doing now I obviously don't know what I'm doing.
Click to expand...
Click to collapse
Sounds like you are trying to install a version of the firmware that is older than the one that was on there. What is the build version that you are trying? What step is it failing at in Odin? I'd recommend getting the newest version of 4.4.2 to avoid the risk of trying to downgrade.
Odin fails right at the end. I see a green progress bar on the phone as well as on my pc screen. I'm at work right now so I'm not too sure as to exactly what or where it fails. What firmware do you recommend I attempt to place on it? Thanks for your reply also, I appreciate it.
Thatguycurt said:
Odin fails right at the end. I see a green progress bar on the phone as well as on my pc screen. I'm at work right now so I'm not too sure as to exactly what or where it fails. What firmware do you recommend I attempt to place on it? Thanks for your reply also, I appreciate it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal.../rom-att-i317-ucucne5-mj4-stock-odex-t2802189
es0tericcha0s said:
http://forum.xda-developers.com/gal.../rom-att-i317-ucucne5-mj4-stock-odex-t2802189
Click to expand...
Click to collapse
Which one do I pick?
Ok...update....
After using Odin to put this firmware on AT&T UCUCNE5 i317 Stock ODIN Note 2 the phone actually rebooted when finished and seemed like everything was normal. However it shows Samsung Keyboard has unfortunately stopped working every ten to fifteen seconds and will not stop. I tried clearing data and cache of the Samsung keyboard app and that did not work. I tried factory and data reset of the phone as well as wipe partition cache and none of that worked. Any suggestions?? I couldn't do anything so I
managed to use a Bluetooth keyboard to go to play store and download new keyboard app but I'm using my google account for that and I personally don't want him having my account on his phone.
I apologize for all the troubles, I'm trying to help him out and didn't realize I was in over my head with no experience on this.
Thatguycurt said:
Ok...update....
After using Odin to put this firmware on AT&T UCUCNE5 i317 Stock ODIN Note 2 the phone actually rebooted when finished and seemed like everything was normal. However it shows Samsung Keyboard has unfortunately stopped working every ten to fifteen seconds and will not stop. I tried clearing data and cache of the Samsung keyboard app and that did not work. I tried factory and data reset of the phone as well as wipe partition cache and none of that worked. Any suggestions?? I couldn't do anything so I
managed to use a Bluetooth keyboard to go to play store and download new keyboard app but I'm using my google account for that and I personally don't want him having my account on his phone.
I apologize for all the troubles, I'm trying to help him out and didn't realize I was in over my head with no experience on this.
Click to expand...
Click to collapse
You'll need to install a custom recovery, use that to wipe the system partition and data reset again then immediately reboot to Download Mode and reinstall the NE5 update.
You sir have been very helpful and I can't thank you enough. I was clueless coming into this thinking I could help my friend effortlessly but that was not the case. I've never had the intentions of rooting a phone or placing a custom mod on one but honestly now I'd like to try it lol!! With your help and this website I was able to fix his phone. I can't thank you guys enough. You're awesome!!!
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.
This is my first post to a forum, so please bear with me...
So a few days ago, a friend of mine got a Verizon Samsung Galaxy S4 from someone, for free. He got it for free because the screen's glass is cracked a bit, and the phone is bricked; the previous owner didn't know what to do with it. I decided I would try to fix it, because if I do, I might be able to buy it off him and give it to my little sister, who currently has a dying iPhone 5C.
When I turn on the phone, it boots, showing the samsung logo, showing the red Verizon screen, and playing the boot tune. Then, just when you'd expect it to go to the OS, it shows a screen which at the top reads "Device memory damaged". Below that, it says "The data partition has been corrupted. You need to reset your phone to factory defaults. This will erase all your data." And below that is a button, which says "RESET PHONE". Tapping on it does nothing.
I have worked with android phones before (rooting, ROMs, locked bootloaders, bricked phones; even all these things on a Galaxy Gear smartwatch), and I know what the data partition is. I remembered that the recovery on samsung phones have an option to wipe the data partition. So I tried to access the recovery menu by holding Power, Home, and Vol+ when the phone is off. It doesn't work either . It shows the Andy robot laying on its back with a door open on its belly, with a warning icon popping out. So the recovery is dead...
I thought I could try to fix the recovery by flashing it with Odin :fingers-crossed:; Didn't work. It is blocked because the phone can't verify version . Then, after a little more research, I realized I might be able to fix the recovery by flashing a whole stock ROM. I don't know what firmware the phone is running, because I can't ask the previous owner. So I tried a few KitKat ones, and they were all rejected by the phone. Then I booted the phone back up, and I realized the RESET PHONE button acted like it was part of a Lollipop UI (There is a darker circle that extends from the part of the button where you tap). So I went back into download mode and tried to flash the 2 OTA versions of Lollipop (OC1 and OF1). The error this time was "SW REV. CHECK FAIL : fused : 8 , Binary : 6". This may or may not be the error I got before with the KitKat ROMs. I don't remember, and I'm not at my desktop to try the old ROMs.
After looking up this error, I found no exact results, but there were ones with a similar error. People said that it means a ROM is being flashed that is too old to pass the downgrade prevention system. I've been trying to flash what seems to be the latest firmware revision for this phone (OF1). Any ideas? Are the OSs I'm trying to flash somehow too new for the phone (even though I've tried all of the stock Lollipop ROMs. Should I give the phone back to my friend and tell him it's dead?
Thanks in advance!
I can't post images because I haven't posted here (or on any forum, for that matter) before.
Well, it seems really bad but you can try Samsung Smart Switch or Verizon Wireless Software Upgrade Assistant to repair the phone, else way JTag it's another option
Fuse 8 is OF1
Matthew M. said:
Fuse 8 is OF1
Click to expand...
Click to collapse
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
you probably needed to flash a lowship odin tar and repartition
Legitsu said:
you probably needed to flash a lowship odin tar and repartition
Click to expand...
Click to collapse
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
evanzolman said:
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
Click to expand...
Click to collapse
a normal odin tar will not fix a bad partition regardless of the .pit you need a tar that s a _user_Low_ship todo a full format odin was failing because the partitions where screwed and you weren't using the correct image
go to sammobile.com they have all the s4 all variants roms.
evanzolman said:
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
Click to expand...
Click to collapse
I am not aware of a definitive guide on the fuses. I found it by trial and error
Envoyé de mon SM-G903F en utilisant Tapatalk
Hi guys.
My uncle gave me his Galaxy S3 GT-i9300, asking me to fix it. The reason is that when turned on it is stuck at the Samsung Galaxy S3 logo, without booting to the system. I can boot to Download Mode, speaking about it later. I can boot to recovery, but it gives a lot of errors about can't mount partitions or directory and files not found (such as the photo below in the attachments). Searching a while I understood that these errors are caused by broken partitions. I've successfully booted in Download Mode, but I can't flash any file with odin. If using the .pit file to repartion the eMMC, it stucks to "Get Pit For Mapping" step or it fails with "Re-partition operation failed", it depends on the Odin version I use to do it. I've let the computer to his things with the "Get Pit For Mapping" for over a night, without success. Still stuck. I've tried to flash stock boot.img, stock recovery.img and various other single images from the Stock Firmware downloaded from Sammobile. I've also tried to flash twrp and cwm. No succes, all of them stock at a certain percentage. Boot and Recovery Image always fail at 2/3 of the operation with "Complete(Write) operation failed". Neither "Nand Erase all" option works, it also fails.
I've tried so many things, including booting from the SdCard short-circuiting a resistance ç(found a giude about it on xda), no success also with this. I can't neither flash bootloader or so.
Tried to flash change cable, change port or so. I've also changed computer, no success.
My idea was to boot into TWRP (my favourite custom recovery) to save at least the photos and the music, and then flash the stock firmware.
I actually can't resolve this. Can you please help me? All help will be appreciated.
P.S.: I could try to ADB Sideload the rom, but I couldn't find .zip packages of official OTA updates.
P.P.S.: Is there a way to pull out files through ADB Sideload? I couldn't find one...
Thanks, EmaMaker.
It really looks to me like the internal memory chip has failed.
audit13 said:
It really looks to me like the internal memory chip has failed.
Click to expand...
Click to collapse
Agreed. All options have been exhausted. It's dead.
As for the adb question, only if you have a working recovery that is adb enabled like twrp or cwm..
audit13 said:
It really looks to me like the internal memory chip has failed.
Click to expand...
Click to collapse
Oh come on, it can't be dead after a trivial recharge...
My s3's memory chip is still alive after 6 years and only the power button broke. And my new s3's main board (which was produced in 2012 as by written on the board) works perfectly.
Isn't there a way of completely erase the memory and reflash it, without problems?
I could make a friend change the emmc for me, replacing it with my old main board's one. Once an emmc is extracted and works as a stand-alone chip, can i try to recover files from it?
There are many s3 users whose phones are completely functional after many years of use but failed memory chips in any phone is possible.
I have a nexus 5, Samsung s4, and Samsung note 2 with defective internal memory chips. These were given to me by family and friends to use for parts. Before taking them apart, I tried everything I could to flash the phones without luck.
By normal means the phone is f00ked. Once you get to the point where it asks for pit file 9 times out of 10 the nand is corrupt. The problem is how sd memory works in the first place and its inherent flaws. That is why some phones work forever while others can die within days.
As the phones were built in many different factories using many differently sourced parts the chances of "Sudden Death Syndrome" is quite high. Some manufacturers actually purchase prebuilt cheap Chinese phones and rebrand them as their own.
If you wanted to change the nand I'm not sure if any of the chips are married to each other so that's a risk in itself. You can swap the board out with a salvage phone. You can try jtag. All of which could cost you the same as buying another s3. They are too cheap nowadays.
If you want a wierd example, my stock rooted s3 borked royally from turning off in the middle of the night due to no power. Turned it on and it puked a load of errors "e: unable to mount /****". I flashed the latest official cwm and then flashed the stock recovery and as I rebooted thinking that it was dead it booted to os!. All errors solved!. Lost root completely but at least I could flash it back to stock and start over.
That was when I started to see a pattern on the forums where twrp was the common denomination between the cases of borked phones so I googled it and there is documentation on twrp github which states the same but the cause is currently unknown. This is where I always state to be careful rooting your phone in the first place as twrp is the only recovery for nearly all phones, it has an inherent fault that no-one knows the cause of and it can lead to a dead phone. Where any other recovery is available I'd recommend that over twrp. I also noticed that the most common combo is twrp and custom roms as THE most likely to go tits up across all devices. If you must root keep it stock root.
Otherwise if twrp didn't kill it then its genuinely a dead nand, probably faulty at birth and it was a matter of time. I honestly think Samsung cheaped out on parts for the s3 and that is why so many fail.
shivadow said:
By normal means the phone is f00ked. Once you get to the point where it asks for pit file 9 times out of 10 the nand is corrupt. The problem is how sd memory works in the first place and its inherent flaws. That is why some phones work forever while others can die within days.
As the phones were built in many different factories using many differently sourced parts the chances of "Sudden Death Syndrome" is quite high. Some manufacturers actually purchase prebuilt cheap Chinese phones and rebrand them as their own.
If you wanted to change the nand I'm not sure if any of the chips are married to each other so that's a risk in itself. You can swap the board out with a salvage phone. You can try jtag. All of which could cost you the same as buying another s3. They are too cheap nowadays.
If you want a wierd example, my stock rooted s3 borked royally from turning off in the middle of the night due to no power. Turned it on and it puked a load of errors "e: unable to mount /****". I flashed the latest official cwm and then flashed the stock recovery and as I rebooted thinking that it was dead it booted to os!. All errors solved!. Lost root completely but at least I could flash it back to stock and start over.
That was when I started to see a pattern on the forums where twrp was the common denomination between the cases of borked phones so I googled it and there is documentation on twrp github which states the same but the cause is currently unknown. This is where I always state to be careful rooting your phone in the first place as twrp is the only recovery for nearly all phones, it has an inherent fault that no-one knows the cause of and it can lead to a dead phone. Where any other recovery is available I'd recommend that over twrp. I also noticed that the most common combo is twrp and custom roms as THE most likely to go tits up across all devices. If you must root keep it stock root.
Otherwise if twrp didn't kill it then its genuinely a dead nand, probably faulty at birth and it was a matter of time. I honestly think Samsung cheaped out on parts for the s3 and that is why so many fail.
Click to expand...
Click to collapse
Thanks for your exausting answer. I will search more about jtag in the next days. I tried to flash both twrp and cwm, none of them worked.
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