Hi,
I've read through some threads but cant find anything on how to get my computer to recognise my phone. My phones dead but the computer does recognise that something has been plugged in. I've gotten as far as installing RELINK HS-USB QDLoader (9003) by downloading as advised in other posts but can't get past this stage.
I just need to get the picture off the phone as they weren't backed up. Is there anything I can do?
Thanks,
Ziggy
Try with a debrick image.
What's a debrick image and how do I get one? Thanks
http://forum.xda-developers.com/galaxy-s4-mini/help/debrick-img-hard-bricked-i9195-n-dload-t3052063
http://forum.xda-developers.com/showthread.php?t=2625628
arco68 said:
http://forum.xda-developers.com/galaxy-s4-mini/help/debrick-img-hard-bricked-i9195-n-dload-t3052063
http://forum.xda-developers.com/showthread.php?t=2625628
Click to expand...
Click to collapse
Thanks. I've gotten to Boot Recovery Mode but I can't tell what to do from hear. The instructions suggest that this isn't what I was aiming for. The full message is:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS
COPY FROM T-FLASH
BOOT RECOVERY
WRITE 139008 sectors
FLASH WRITE FAILURE
ddi: mmc_read failed
ODIN MODE
PRODCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM SATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LBS: Ox30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
What do I do from here?
Related
Hi,
I'm a newbie to this, but i tired following a few recommended stuff off this thread and
still nothing please help.
Got a sph-l710 that wont turn on,
i tried a few debricking images one got it to vibrate with this on screen
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 159488 sectors..
FLASH WRITE FAILURE
ODIN MODE
PRODUCT NAME: SPH-L710
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit:0
BOOTLOADER AP SWAEV: 2
then when i run it through odin
it reads ODIN: flash read failure in red
Please help
I've been reading many threads over the last 3 days, and I can't get back my SM-N9005.
My N9005 (Portuguese TPH) bricked doing a firmware update from 4.4.2 N9005XXUGNG1 (Portuguese TPH) to 5.0 Lollipop N9005XXUGBOB6 (Poland XEO) with Odin 3.09. Odin said success (PASS), but phone never rebooted.
Solution #1: http://forum.xda-developers.com/showthread.php?t=2531224 Thanks @msmercy42 I learned a lot from it but none of the N9005 unbrick.img worked for me.
Solution #2: http://forum.xda-developers.com/showthread.php?t=2625332 Thanks @ValenteL finally my N9005 goes into ODIN/Download mode.
However, I belive that solution #2 isn't going as smooth as it should. This is what I get when I get the phone to start from SD card:
Code:
[COLOR="Lime"]BOOT RECOVERY MODE[/COLOR]
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
BOOT RECOVERY. .
WRITE 163840 sectors. .
[COLOR="Red"]FLASH WRITE FAILURE[/COLOR]
ddi : mmc_read failed
[COLOR="red"]ODIN MODE[/COLOR]
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
[COLOR="Gray"]QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
And then, Odin recognizes the phone.
Now I'm able to get Odin to recognize the phone, but I can't do anything with it. I've tried:
- flashing 4.4.2 N9005XXUGNG1 (Portuguese TPH) again - FAIL (see attachments) Phone outputs two lines, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
[COLOR="Red"]ODIN : flash read failure[/COLOR]
- flashing N9005XXUGBOB6 (Poland XEO) again - FAIL
- flashing PIT files (tried 3 different ones) - FAIL Phone outputs another line, after UDC START:
Code:
[COLOR="Gray"](...)
WRITE PROTECTION: Enable[/COLOR]
[COLOR="Red"]UDC START[/COLOR]
MMC: mmc_read fail
I wasn't able to get any unbrick.img from a N9005 Lollipop yet. Is this the final solution for my problem? Since I'm able to get to odin mode, shouldn't this unbrick be enough? What does it mean "mmc_read fail"?? Any help?!?! I don't know what else to do...
Thanks!!
sorry, wrong location... already started a new thread on 9005 Galaxy Note 3 proper location.
http://forum.xda-developers.com/galaxy-note-3/help/help-sm-n9005-hard-bricked-sd-partial-t3070743
Moderator: please delete this one, i'm sorry for the inconvenient.
Hi guys,
I was trying to find out how to restore my phone because it's dead after receiving and installing the last firmware (Netherland PHN 4.4.2 stock ROM-there was no Custom ROM) by OTA. It was working for few days but after that my phone began restarting and finally it stopped work at all. I wasnt able to turn in on, charge it or simply connect to pc (PC didnt recognized driver - qhsusb_dload) there was no respond so it was completely dead.
I found some solution with debrick image here on forum, but when i putted debrick.img (found some for I9195 android 4.4.2 on web) into sd card via win32diskmanager and inserted it into my phone i was able to get some respond by a phone.
Withou debrick image on sd cart i can't turn my phone on at all but with inserted debrick image i have a chance to turn it on but with some kind of boot loop.
Boot loop:
BOOT RECOVERY MODE (Green row)
CHECK BOOT PARTITIONS.
COPY FROM T-FLASH.
BOOT RECOVERY..
WRITE 139008 sectors.
REBOOT
And it repeats all the time.
With SD Card PC can recognised samsung drivers for my phone but odin can't connect.
I dont know what i did once time but i get another message when odin was able to recognise it
BOOT RECOVERY MODE (Green row)
CHECK BOOT PARTITIONS.
COPY FROM T-FLASH.
BOOT RECOVERY..
WRITE 139008 sectors.
FLASH WRITE FAILURE (Red row)
ddi: mmc_read failed
ODIN MODE (Red row)
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
But i'm not able to get into this anymore.
Last status is repetitive first bootloop and i cant get further.
I dont know what to do, to repair my phone or if its completely dead (mean eMMC fail).
Can someone help me with this issue or know some solution
Thanks in advance
hello guy's, my samsung today work's fine and from one hour not work at all - dead, i try to turn on no lucky, enter recovery no lucky, enter download mode not lucky
i found on forum about debrick.img and put on 16GB card, and phone vibrate and turn on but stuck like on the pictures mmc read failed, any sugestion, all the best
http://postimg.org/image/ar0zp4olp/
http://postimg.org/image/h3g4yyrnx/
gigidel said:
hello guy's, my samsung today work's fine and from one hour not work at all - dead, i try to turn on no lucky, enter recovery no lucky, enter download mode not lucky
i found on forum about debrick.img and put on 16GB card, and phone vibrate and turn on but stuck like on the pictures mmc read failed, any sugestion, all the best
http://postimg.org/image/ar0zp4olp/
http://postimg.org/image/h3g4yyrnx/
Click to expand...
Click to collapse
Sounds like the emmc memory is dead. Try to use these debrick images that I had taken from my i9195 some time ago. Extract first. https://drive.google.com/file/d/0B_vlSjY0nNrkX001ZUs4ZUF6dXc/view?usp=sharing
https://drive.google.com/file/d/0B_vlSjY0nNrkSFRVUERoTkF5cnM/view?usp=sharing
thanks a lot Mountains788, i try this two debrick.img, but no lucky, still the same mmc read failed
gigidel said:
thanks a lot Mountains788, i try this two debrick.img, but no lucky, still the same mmc read failed
Click to expand...
Click to collapse
I had the same issue, 2days ago (also so an Galaxy S4 mini).
I solved it by holding the 'volume down + home button' while connecting/disconnecting the phone to my/from laptop.
I have the same problem
When i put the sdcard with debrick image in my phone, It says:
BOOT RECOVERY MODE
CHECK BOOT PARTITONS..
COPY FROM T-FLASH..
BOOT RECOVERY..
WRITE 139008 sectors..
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9190
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
And when i connect it to pc to flash by odin, it says "There is no pit partition"
When i put the pit file in odin, it says the same
What should i do?
Did you get it to work? I have the exact same problem with the same phone (GT-I9190) !!!!
My sister's S4 mini suddenly died, I cannot open the smartphone nor go on Recovery or download mode.
I used a debrick.img found here on xda put on a externaSD and manage to enter the download mode, then i try to flash a stock rom but it got stuck during the process (i leave odin running for hours without any success).
After that, when i retry the process this is what i got on screen:
Code:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS. .
COPY FROM T-FLASH. .
WRITE 139008 sectors. .
FLASH WRITE FAILURE
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-I9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
BOOTLOADER AP SWREV: 2
CSB-CONFIG-SLB: 0x30
WRITE PROTECTION: ENABLE
I try to flash different .pit file found here on xda for the i9195 but if i try to flash (using Odin 3.13 or even odin 1.85) it says
Re-Partition operation failed or There is no PIT partition.
Any other idea i can try?
Maybe another .pit file for i9195 and a firmware that work with it?
Thanks to everyone
Goku_ssj3 said:
My sister's S4 mini suddenly died, I cannot open the smartphone nor go on Recovery or download mode.
I used a debrick.img found here on xda put on a externaSD and manage to enter the download mode, then i try to flash a stock rom but it got stuck during the process (i leave odin running for hours without any success).
After that, when i retry the process this is what i got on screen:
I try to flash different .pit file found here on xda for the i9195 but if i try to flash (using Odin 3.13 or even odin 1.85) it says
Re-Partition operation failed or There is no PIT partition.
Any other idea i can try?
Maybe another .pit file for i9195 and a firmware that work with it?
Thanks to everyone
Click to expand...
Click to collapse
I think her EMMc chip is probably dead, so needs replacing (new motherboard)