SM-T580 Potential Brick Issue - Samsung Galaxy Tab A series Questions & Answers

OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.

Thaser said:
OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.
Click to expand...
Click to collapse
You need to put it in download mode first.

I have done so with every attempt. It still continues to simply hang at 'initializing'.

Thaser said:
I have done so with every attempt. It still continues to simply hang at 'initializing'.
Click to expand...
Click to collapse
Post a screen shot of your download screen and odin log.

ashyx said:
Post a screen shot of your download screen and odin log.
Click to expand...
Click to collapse
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Thaser said:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/

zfk110 said:
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/
Click to expand...
Click to collapse
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..

Thaser said:
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Click to expand...
Click to collapse
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows

zfk110 said:
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Click to expand...
Click to collapse
Did the above, still no success. Stuck at initialization

Thaser said:
Did the above, still no success. Stuck at initialization
Click to expand...
Click to collapse
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.

ashyx said:
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.
Click to expand...
Click to collapse
I will second this. My laptop will not see Odin added at all for most of my devices. And out out of like 6 USB cables only 1 works for Odin downloading but good for everything else

Custom Binaries Blocked by FRP Lock
May I start you over with your diagnostics. Not initializing? Does this mean you cannot boot into recovery, at all? But can get into download mode which you cannot use?
Try booting to recovery and tell me if you see little red letters at the top left that say something about FRP lock. If this is your issue I'll explain what's going on with your device.
There are two types of FRP protection I've seen in this tablet. The first one most of us know of and it can be best described as being able to boot or power on compared to the other one which acts similar to a bootloop and does not power on.
This seems to be a common bug with the current Rootings applied to this device that are using CF-Root or a variation thereof. Samsung insisted that CF-Root shouldn't be used on this device and that's where the problem apparently comes from. The device owner is caught in a bootloop type of mode where the logo comes and goes and somehow accessing recovery is impossible. At the top left side of the screen in fine red letters reads, "Custom Binaries Blocked By FRP Lock. " This apparently shuts off the OEM unlock also leaving you with access to the Bootloader/Downloader, but Odin3 would refuse to flash even the official Firmware. Suddenly the impossible Hard-Brick comes to mind. Fortunately for all of us someone invented Odin3 and Samsung device owners rarely have to deal with a hard bricked device..
Here's what you need.:
Odin3.10 to Odin3,13. Either one works. The following file will give you Odin3.13.
The SM-T580 Binary 4 FRP Unlock file can be obtained here (this is a 1.98GB rar file):
https://drive.google.com/file/d/1Rip0qIGo-GbzFdH55s1vIpe6f1aqYKbD/view
Extract the file, preferably to a folder of its own that you create.
Prep device for flashing (boot to download mode), connect to PC and fire up Odin3. The first section should light up blue means you're connected. Click on AP, go to the extracted 3file and doublr click on the file starting with the word "unlock." Wait til Odin does it's checksum and then you can press start.
This will reset your device to factory!!
Now you're going to want to Bypass the Google Account and remove FRP which is the first FRP I mentioned.
Let me know how it goes for you..

Related

Help special case to flash stock rom in s7 edge 935a

Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Remove PIT file and try again.
From Edge of Galaxy Seven
Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Not knowing WHAT you are flashing, makes it a little harder to determine what is going wrong.
Go HERE and flash this in Download Mode. This is the latest Stock 935A ROM, This will wipe Everything on the device, and it'll be like it came brand new
norbarb said:
Remove PIT file and try again.
From Edge of Galaxy Seven
Click to expand...
Click to collapse
which is the pit file, sorry for dumb question
Darkboss10 said:
which is the pit file, sorry for dumb question
Click to expand...
Click to collapse
If I remember correctly you need to uncheck PIT in odin and this should help. BTW. What are you trying to flash?
From Edge of Galaxy Seven
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Darkboss10 said:
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Click to expand...
Click to collapse
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
so i do better go with the v4 bootloader and i will check if the pit file is uncheck, what should i put on the re-partition case of odin active or inactive?
by the way thanks for your help
kangi26 said:
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hey i did exactly as you told me , and for first time i guess i have an advance, i still get an error but at least a new error , check it out maybe you know what it is
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
any idea what can be?
i try to flash the G935a...PI2 rom bot without the CSC which i guess is the pit file right?
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
kangi26 said:
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
Click to expand...
Click to collapse
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Darkboss10 said:
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Click to expand...
Click to collapse
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
kangi26 said:
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
if you watch the top corner blue letters it says recovery booting....
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
I'm at a loss man, I'm sorry. I haven't seen that before, I dont get the "Samsung" part when I enter Recovery
Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
Can you post screen from download mode?
From Edge of Galaxy Seven
norbarb said:
Can you post screen from download mode?
From Edge of Galaxy Seven
Click to expand...
Click to collapse
There you go . By the way i should mention the phone only turns on download mode when plugged.
Darkboss10 said:
There you go . By the way i should mention the phone only turns on download mode when plugged.
Click to expand...
Click to collapse
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
You need to start by using the latest Odin, 3.12.3 for installing the original ROM. If you try to unlock, you need to go get the PrinceComsy version. PrinceComsy won't work for in-bricking a device, and if you have any of the stock versions of the ROM, you need the 3.12.3 version.
norbarb said:
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
Click to expand...
Click to collapse
I try that . Now i got this error but only on the phone screen and odin is stuck at initialization .. any idea what could be
i download the venom stock rom and the odin file he suggest but that odin is v 3.11.2 , so that was the one that trows me the odin protocol error, i try the same rom but with the v 3.12.3 odin , and it start working but it says fail at the on the recovery image, do that has to do something with my problem that the phone can boot into recovery mode?
here are the logs
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Erase)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1

I9505 bootloader flash odin complete(write) error (SOLVED)

Okay so I was trying to update my bootloader and modem using the tutorial I found here. But odin refused to install it and left me with a softbricked device. Now I have tried to flash the new bootloader again, the old bootloader, changed pc, changed usb cord and port, tried heimdall but still not working. Now it starts to install the bootloader and odin log goes like this
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
Any help?
It's possibly because the bootloader you are trying to flash is not compatible with your S4 model.
If you can't flash the bootloader separately, flashing a stock ROM package may work. Also, try a different Odin version and also another Windows.
Yeah I tried to flash the stock rom but the same thing happened. I have tried 3 different odin versions and 2 windows.
Could this be because I've changed my usb port? Odin seems to always disconnect my phone after failing and then reconnects again.
Google and download PIT file GT-I9505
Flash bootloader with pit file selected
@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.
Strephon Alkhalikoi said:
@4shared: Nice advertising. PIT files are a weapon of last resort, thus we want to make sure there is no alternative before recommending it.
@varvainenkalas: Return to download mode and read the model number in the upper left corner. We need to make sure you don't have a Frankenphone before continuing.
Click to expand...
Click to collapse
It says Product name: GT-I9505
Good. The USB port on the device could cause this if it's damaged or defective. You want to check its connections in the device and also clean the port with a bit of rubbing alcohol to be safe.
Yes I got it solved. I don't know how but I think that the problem was that both usb cables I tried were damaged though they worked before. I tried third usb cable and the same error came up then I tried again and it flashed the stock succesfully. How can I mark this solved?
Go to your first post and change the title. If you can't do that, add a line to the post noting that the problem was resolved.

Samsung S8 bricked, odin not flashing stock firmware

Hello,
I'm trying to recover from a soft brick from flashing TWRP on my G950U, but odin isn't able to write stock firmware. Here's the log:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4813 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003>
<ID:0/003>
<ID:0/003>
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
The firmware I'm trying to flash is G950USQS3CRE2_G950UOYN3CRE2_SPR.zip from sammobile.
I've downloaded the samsung USB drivers, my phone is in download mode, and I'm getting this error with different cables, ports and computers.
Any ideas on what I can try?
Check odin version..use latest version.
PeterParker said:
Check odin version..use latest version.
Click to expand...
Click to collapse
Is 3.13.1 not the latest version? I couldn't find anything beyond that, but there's also a version called Prince Comsy Odin, which also gave a similar error.
joebhakim said:
Hello,
I'm trying to recover from a soft brick from flashing TWRP on my G950U, but odin isn't able to write stock firmware. Here's the log:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> Total Binary size: 4813 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003>
<ID:0/003>
<ID:0/003>
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
The firmware I'm trying to flash is G950USQS3CRE2_G950UOYN3CRE2_SPR.zip from sammobile.
I've downloaded the samsung USB drivers, my phone is in download mode, and I'm getting this error with different cables, ports and computers.
Any ideas on what I can try?
Click to expand...
Click to collapse
1. Boot into download mode screen by pressing power button + volume down + Bixby button.
2. Press volume down to restart phone.
3. Quickly press the power + volume down + Bixby button and go back into download mode .
4. Press continue 5. Congratulations full working now. Try firmware flash and it should wok.
pokoo2 said:
1. Boot into download mode screen by pressing power button + volume down + Bixby button.
2. Press volume down to restart phone.
3. Quickly press the power + volume down + Bixby button and go back into download mode .
4. Press continue 5. Congratulations full working now. Try firmware flash and it should wok.
Click to expand...
Click to collapse
Thank you for the suggestion. When I try this, the "Security Error: This phone has been flashed with unauthorized software..." screen comes up after I restart, instead of the second download mode. Am I doing this wrong?
Also, I've been holding down volume UP + bixby + power while flashing, or else odin is failing at <ID:0/003> SetupConnection..
Some other stuff I tried:
Using heimdall on linux, but I get "ERROR: Failed to send handshake!" I'll try it again on another linux distro
Flashing different firmware versions, all for G950U sprint, flashing TWRP...
Using Samsung Smart Switch and Kies v3 (both report unsupported device) and Kies v2 (it gets stuck on "connecting", until it eventually reports that the device is not responding)
Some other error messages I'm getting with odin, seemingly depending on what button combination I'm pressing and whether I unplug replug the usb before flashing:
<ID:0/008> Complete(Write) operation failed.
...
<ID:0/005> Can't open the serial(COM) port.
I think I'm running out of options. Does anyone have any more ideas?
Is that the latest firmware? Try restarting your PC and use the latest odin. I realised heimdall doesn't work so I used vmware to run windows with latest odin and last firmware file and it worked. I was using the exynos version though. I had downloaded the stock rom from xda but that won't flash and checked sammobile for latest firmware, that one worked fine !
ItsmYarD said:
Is that the latest firmware? Try restarting your PC and use the latest odin. I realised heimdall doesn't work so I used vmware to run windows with latest odin and last firmware file and it worked. I was using the exynos version though. I had downloaded the stock rom from xda but that won't flash and checked sammobile for latest firmware, that one worked fine !
Click to expand...
Click to collapse
I believe it's the latest firmware for sprint. I've restarted my PC, and odin's version is 3.13.1 (which I believe is the latest). I'm currently trying a different, earlier firmware just in case that works.
I literally had the same error, I don't quite remember what I did but it was a frustrating two days of trial and error when I got this phone two weeks back, afaik it was just a wrong firmware file so give that old firmware a try
ItsmYarD said:
I literally had the same error, I don't quite remember what I did but it was a frustrating two days of trial and error when I got this phone two weeks back, afaik it was just a wrong firmware file so give that old firmware a try
Click to expand...
Click to collapse
Will do. Do you know if anyone other than Sammobile hosts them? They limit upload speed so it takes four hours between each attempt
edit: https://updato.com workds pretty well
pokoo2 said:
1. Boot into download mode screen by pressing power button + volume down + Bixby button.
2. Press volume down to restart phone.
3. Quickly press the power + volume down + Bixby button and go back into download mode .
4. Press continue 5. Congratulations full working now. Try firmware flash and it should wok.
Click to expand...
Click to collapse
Thank you so much!! That saved my life!!!!!

Unable to flash anything on Samsung Galaxy S4 GT-I9515

Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?

Note 3 stopped booting, goes straight to Download screen with mmc_read failed message

This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
My trusty Galaxy Note 3 N9005 32GB has been giving me a few minor file errors recently, so I re-installed from a nandroid backup (ROM is MagMa NX VX PCE 6.0.1) with Phantom kernel) and it's been great for a few weeks now, performing better than ever in fact.
However yesterday, I glanced at the phone mid-afternoon (after using it fine all day listening to music and reading emails, etc) and it had reverted to the Download screen, reporting "Could not do normal boot, ddi : mmc_read failed."
I can't get into Recovery or use ADB, so I ran Odin on my PC and it showed the device as Added, so I thought I'll re-upload TWRP so I can at least get into Recovery and see what's going on, but although Odin started sending the TWRP .tar file normally, it quickly reported "Get PIT for mapping ... There is no PIT partition". The phone screen showed "UDC START" then "MMC: mmc_read fail". The USB port and USB cable are the same ones I've been using for some recent adb pull backups so they should be OK.
I tried installing a new PIT file (first from a previous backup of my own setup, and then from generic versions for this device) but Odin with AutoReboot, Re-Partition, and F.Reset Time ticked showed:
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone showed:
UDC START
MMC: mmc_read fail
I then tried downloading a 4files repair installation of a stock Lollipop ROM (the most recent I could find for this device, N9005ZSUGPJ2) and used Odin to install the included PIT, AP, BL, CP and CSC files, with Nand Erase All selected too:
<ID:0/007> Odin engine v(ID:3.1101)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This time, the phone showed:
UDC START
MMC: mmc_read fail
ERASING USERDATA PARTITION...
I could really do with some expert help or advice here from anyone who knows more about these things than I do... or do I have an unexpected brick on my hands? Thanks!
Andre
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
here is the procedure you have to follow...
PLEASE.....DO NOT skip ahead, just follow my instructions in sets,
Here are the Files you NEED to download:
Odin3 v3.10.zip
CHARGE the device to 100% Battery BEFORE beginning!
Download and extract the Files.
Open ODIN, place each of the Files in corresponding boxes:
BL = BL
AP = AP
CP = CP (MODEM)
CSC = CSC
Please select these Check-boxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS Clear
START!!
After it reboots, WAIT 10 Minutes, Skip the Wizard and perform a Factory Data Reset!
rayman95 said:
I'm afraid that your phone memory died...this error is a corrupted memory flash
if 4 files + pit doesn't work...which version did you get????
Click to expand...
Click to collapse
Which phone version, or which 4files?
Phone is a Galaxy Note 3 N9005 (UK 32GB).
File was from https://zfirmware.com/download-samsung-repair-firmwares/ , version http://www.mediafire.com/file/9ux01...3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
I was hoping to be able to use this device until the Note 10 is released, but maybe I'll have to settle for an S10+. Problem is, I prefer my nice Note 3 to anything they have released since (removable battery, no stupid curved-edge display, proper physical front buttons away from the main screen, a bigger - OK, wider - display than anything since, etc)
Andre
andrewilley said:
This is a continuation of a discussion in the TWRP support thread as it's getting a bit off-topic for that thread.
Click to expand...
Click to collapse
From my own experience, this problem is a manufacturing defect that affects a lot of samsung devices produced from Q3 of 2014 until Q2 of 2015. The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
However, I managed to fix a Galaxy S5 with the method I already described. And that has been presented as a momentary solution by several xda users, like here.
I wrote : momentary solution because this error is definitely a hardware failure, a fixed device will only work for a random period then the problem will get worse until the device become completely unusable.
Fortunately, you can buy a new motherboard for less than 30euro. And that's what I recommend you to do.
andrewilley said:
Galaxy-Note3-N9005-Full-Factory-rom-5.0-N9005ZSUGPJ2.zip[/url] . I guess I could try an earlier KitKat version, or if you have any better suggestions, but it's looking less and less hopeful.
Andre
Click to expand...
Click to collapse
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
zlazaar said:
The error starts to appear generally after 2 years of use. Note 4 is the most affected, including mine who died last year.
Click to expand...
Click to collapse
I've been noticing a few file-read errors over the last 5 months or so, which I put down to bad blocks even though e2fsck -cfv showed zero errors. I thought a reformat and nandroid restore had fixed it, but obviously if the problem is lower down that might just have been delaying the inevitable. I suspect that installing a new mobo would not really be a good long-term plan as that could just as easily have the same issue (as they'll all be 4+ years old by now).
rayman95 said:
this firmware is not for european device but asian... you must find another one, or try kitkat, otherwise I can send you mine, french one
N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware
Click to expand...
Click to collapse
I'll try the KitKat version (normally I'd look for a BTU version, but beggars can't be choosers as the saying goes). If I can at least get it running for now and restore my backup via TWRP then I can do a more relaxed and controlled switchover to an S10+.
Andre
Whatever I try, I can't get a new PIT file to re-partition the memory:
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 2252 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
Phone shows MMC: mmc_read fail
Does anyone have a known good PIT file for the UK Note 3 N9005 32GB, along with a matching BL/AP/CP/CSC combo (any ROM version would do) that they would be willing to either upload or point me to?
Thanks,
Andre
I guess I probably should treat this device as a brick now and get it replaced, no other suggestions?
Andre
sammobile forum ??
JJEgan said:
sammobile forum ??
Click to expand...
Click to collapse
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
andrewilley said:
Thanks for the tip. I did ask nicely in their forums, but got a very terse response that they don't discuss devices that have been rooted.
Andre
Click to expand...
Click to collapse
i send you my french files....
take here my files...
Thanks, I'll download and give them a try when I get back on home wi-fi. I fear I'll probably get the same results, but at least I'll have tried everything before giving up on it.
Andre
File downloaded, thank you. There doesn't seem to be a matching PIT file in there though, just the BL, AP, CP and CSC. Is that correct? As stated earlier in the thread, the PIT seems to be corrupted on my device, so was hoping for all 5 files to match...
Andre
rayman95 said:
take here my files...
Click to expand...
Click to collapse
I did try the 4files in your ZIP, but without a new PIT file I got the same partitioning error as before:
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Andre
the pit HERE...
good luck..
rayman95 said:
the pit HERE...
good luck..
Click to expand...
Click to collapse
Many thanks for all your help, but still dead even with the correct PIT I'm afraid.
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 2340 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I guess this phone is on its way to the Great Home for Expired Technology in the Sky.
Andre
Just read some user not this phone replaced eMMC chip.
From Aliexpress

Categories

Resources