Hi. My Galaxy tab A 9.7 fell to the ground and no longer turns on. No recovery, no download mode. Only it detected by windows as qualcomm hs-usb qdloader 9008. I tried to flash stock rom using odin. But only odin 1.87 and 2.10 detect it as COM and after click on start button they stuck for a minute and then show the below messages:
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1).
What should I do?
Related
i keep gettin this error below does anyone know how to fix it?
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
You didn't have your tab in download mode. Completely power off your tab. Then at the same time push power and volume down and hold until black screen has a yellow image. That is download mode, and now, start odin, and connect your tab. One of the rectangles will turn yellow and say COM....You are ready to flash!
I attempted the Jellyblast v3 custom rom on my rooted galaxy y, but it seems i made an error and now my phone seems to be bricked. When I try to reboot it i just get the repeated 'S' logo. I tried using odin to flash the stock rom but it fails every time and i get this:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I was wondering if anyone could give me some advice on what I should do next
danjonrin said:
I attempted the Jellyblast v3 custom rom on my rooted galaxy y, but it seems i made an error and now my phone seems to be bricked. When I try to reboot it i just get the repeated 'S' logo. I tried using odin to flash the stock rom but it fails every time and i get this:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I was wondering if anyone could give me some advice on what I should do next
Click to expand...
Click to collapse
do you get a yellow port mapping?
mjz2cool said:
do you get a yellow port mapping?
Click to expand...
Click to collapse
Yes i do
danjonrin said:
I attempted the Jellyblast v3 custom rom on my rooted galaxy y, but it seems i made an error and now my phone seems to be bricked. When I try to reboot it i just get the repeated 'S' logo. I tried using odin to flash the stock rom but it fails every time and i get this:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I was wondering if anyone could give me some advice on what I should do next
Click to expand...
Click to collapse
Maybe the files are corrupt.
Press THANKS please?
danjonrin said:
I attempted the Jellyblast v3 custom rom on my rooted galaxy y, but it seems i made an error and now my phone seems to be bricked. When I try to reboot it i just get the repeated 'S' logo. I tried using odin to flash the stock rom but it fails every time and i get this:
Added!!
Odin v.3 engine (ID:8)..
File analysis..
SetupConnection..
Can't open the serial(COM) port.
All threads completed. (succeed 0 / failed 1)
I was wondering if anyone could give me some advice on what I should do next
Click to expand...
Click to collapse
Run kies first...
Then close kies and then install firmware through odin ...
It will work......
Sent from my GT-S5360
danjonrin said:
I attempted the Jellyblast v3 custom rom on my rooted galaxy y, but it seems i made an error and now my phone seems to be bricked. When I try to reboot it i just get the repeated 'S' logo. I tried using odin to flash the stock rom but it fails every time and i get this:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
I was wondering if anyone could give me some advice on what I should do next
Click to expand...
Click to collapse
did u get yello icon in odin
softbrick my s4 but still able to access download mode
I have TWRP backups( boot.emmc.win.md5,cache.ext4.win.md5,data.ext4.win.md5,efs.ext4.win.md5,recovery.emmc.win.md5,sd-ext.ext4.win.md5,system.ext4.win.md5)
I got the idea of installing TWRP in download again since it's not booting up in recovery mode
but it's keeps saying FAIL!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
tried changing ports? Try ports that are directly connected into the motherboard
Sent from my GT-I9500 using Tapatalk 4 Beta
Paras Lehana said:
tried changing ports? Try ports that are directly connected into the motherboard
Sent from my GT-I9500 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Is usb debugging enabled on the phone, closed Kies (also in windows tray manager), what odin version are u using (try 3.04 cause 3.07 is buggy),
try downloading TWRP again maybe its corrupted.
terryspanky said:
softbrick my s4 but still able to access download mode
I have TWRP backups( boot.emmc.win.md5,cache.ext4.win.md5,data.ext4.win.md5,efs.ext4.win.md5,recovery.emmc.win.md5,sd-ext.ext4.win.md5,system.ext4.win.md5)
I got the idea of installing TWRP in download again since it's not booting up in recovery mode
but it's keeps saying FAIL!
Removed!!
Added!!
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Removed!!
Added!!
Click to expand...
Click to collapse
Do u have a proper root?
Edit : u can try rooting again and then flash recovery
.
gee2012 said:
Is usb debugging enabled on the phone, closed Kies (also in windows tray manager), what odin version are u using (try 3.04 cause 3.07 is buggy),
try downloading TWRP again maybe its corrupted.
Click to expand...
Click to collapse
changing the usb port do the trick.
Now tried to root and install openrecovery-twrp-2.6.0.0-jfltexx/CSB_signed_Fusion3_EUR_0325_V2 from odin and it says pass on all of them.
But when I'm trying to boot up in teamwin, the twrp logo will show up then it will turn black screen, vibrate a moment and automatically restarts to samsung galaxy s4 screen....
I can't seem to make twrm to work...
I think I have messed up my kernel when I install Abyss kernel for gt-I9505 then it bricked after I install I9505XXUBMF4_modems.tar via mobile odin..
any suggestions?
I'm downloading the PDA for my country and It's taking some time to get finished.
I realized I posted this on the wrong section I have just re-posted it in the tmobile galaxy note 3 section, I apologize for my mistake, Please delete thread as it is in the wrong section.
Hello, I am new here this is going to be my first post.
I installed CWM from rom manager a while ago on my rooted note 3 N900T it was on kitkat 4.4.2 then I tried rebooting into recovery mode and then it wouldn't go in it would keep restarting, then after I did a battery pull now I get: ( Firmware upgrade encountered an issue. Please select recovery mode in kids & try again)
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KEANEL LOCK: 0X0
KNOX WARRANTY VOID: 0XL
QUALCOMM SECUREBOOT: ENABLE (CSB) AP SWAREV: S2, T2, A2, A3, P2
WRITE PROTECTION: ENABLE
VDC START
So I tried connecting to kies it wouldn't detecting it would just say "connecting" I tried on my mac osX mavericks and also on VMWare windows 7.
I tried to download the stock firmware and flash it via odin to come back to stock and thought maybe that would fix it but it keeps giving me a error.
I have the usb drivers installed as it detects the device, I am sure I have downloaded the correct firmware for the phone.
this is the firmware I downloaded: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
I tried using odin 3.07 and 3.09 both and ran it as administrator.
I checked the "time reset" also the "auto reboot" as mentioned, I tried adding it in pa in 3.09 and pda in 3.07
This is the error I get while trying to flash the rom: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Unfortunately that is what I get from odin sometimes it goes further down and then stops but most of the times i get this, I've tried using the original 3.0 usb cable with different usb ports and also another normal micro usb cable, both gives me the same error, I have tried to use JODIN as well on my mac but my device doesn't detect on that therefore i used my VMware windows 7 32bit. I tried that while I had kids installed on my computer and then I read that kies doesn't go well with odin so I uninstalled kies and tried again but no difference.
Could someone please help me out, I have been trying to fix this for 2 days I am a college student and I work part time, so it is very frustrating not to have a phone to use for work and college.
malimt said:
Hello, I am new here this is going to be my first post.
I installed CWM from rom manager a while ago on my rooted note 3 N900T it was on kitkat 4.4.2 then I tried rebooting into recovery mode and then it wouldn't go in it would keep restarting, then after I did a battery pull now I get: ( Firmware upgrade encountered an issue. Please select recovery mode in kids & try again)
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KEANEL LOCK: 0X0
KNOX WARRANTY VOID: 0XL
QUALCOMM SECUREBOOT: ENABLE (CSB) AP SWAREV: S2, T2, A2, A3, P2
WRITE PROTECTION: ENABLE
VDC START
So I tried connecting to kies it wouldn't detecting it would just say "connecting" I tried on my mac osX mavericks and also on VMWare windows 7.
I tried to download the stock firmware and flash it via odin to come back to stock and thought maybe that would fix it but it keeps giving me a error.
I have the usb drivers installed as it detects the device, I am sure I have downloaded the correct firmware for the phone.
this is the firmware I downloaded: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
I tried using odin 3.07 and 3.09 both and ran it as administrator.
I checked the "time reset" also the "auto reboot" as mentioned, I tried adding it in pa in 3.09 and pda in 3.07
This is the error I get while trying to flash the rom: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Unfortunately that is what I get from odin sometimes it goes further down and then stops but most of the times i get this, I've tried using the original 3.0 usb cable with different usb ports and also another normal micro usb cable, both gives me the same error, I have tried to use JODIN as well on my mac but my device doesn't detect on that therefore i used my VMware windows 7 32bit. I tried that while I had kids installed on my computer and then I read that kies doesn't go well with odin so I uninstalled kies and tried again but no difference.
Could someone please help me out, I have been trying to fix this for 2 days I am a college student and I work part time, so it is very frustrating not to have a phone to use for work and college.
Click to expand...
Click to collapse
Known issue in vmware on Mac. Use parallels, bootcamp, or a real windows machine.
Sent from my leanKernel 3.0 powered stock 4.4.2 (NE6) SM-N900T
toastido said:
Known issue in vmware on Mac. Use parallels, bootcamp, or a real windows machine.
Sent from my leanKernel 3.0 powered stock 4.4.2 (NE6) SM-N900T
Click to expand...
Click to collapse
Thanks so much man, You were right, I un-installed VMWare and then installed parallels desktop 9 and then from then I flashed the stock rom using odin 3.07 and boom wallllla I'm back on my 4.4.2 stock rom. thanks thanks thanks
Galaxy S5 SM-G900F running Lollipop (BOE5) rooted with CF-Auto-root worked fine for about 5 months until few daus back. After device restart it entered download mode with message "Could not normal boot; ddi: mmc_read" failed. It does not boot into recovery either, instead it enters the Download mode with the error messages. Any flashing attempt with Odin stops at "Odin : flash read failure" on the device and the "There is no PIT partition" error on Odin on PC. Is the device really hard bricked and cannot be repaired via Odin or similar?
Things I have tried so far:
-flashing Lollipop and KitKat stock ROMs with Odin
-flashing TWRP and stock recoveries with Odin
-booting with SD with S5 debrick.img (boots into DM with errors)
-flashing PIT file only and PIT file together with stock ROM
-different Odin versions, different USB ports
Odin output when flashing ROMs:
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOJ1_G900FOXX1BOJ1_G900FXXU1BOJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin output when flashing PIT:
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Unfortunately cannot add picture link wtih DM errors.
Bump thread, maybe someone has dealt with a similar case and found a solution that is not a motherboard/device replacement.
This thread says it could be due to a faulty USB port or cable
http://forum.xda-developers.com/showthread.php?t=2659635
Try a different PC
http://forum.xda-developers.com/showthread.php?t=2283919
Try a different cable etc
*Detection* said:
This thread says it could be due to a faulty USB port or cable
http://forum.xda-developers.com/showthread.php?t=2659635
Try a different PC
http://forum.xda-developers.com/showthread.php?t=2283919
Try a different cable etc
Click to expand...
Click to collapse
Thanks for the links. Tried all USB ports and available cables with same results. Will try different PC, when I'll have the chance.
The mmc_read failed message when booting into Download Mode is what bothers me. Could it be a reason to suspect a hardware problem?
Yea it could be, but best to rule out everything else first
Does it say that on the actual phone, or just ODIN?
If just ODIN, it could still be anything from the Phone > USB cable > PC
If it says it on the phone, without being connected to the PC/USB, then yea it's gonna be something on the phone
*Detection* said:
Yea it could be, but best to rule out everything else first
Does it say that on the actual phone, or just ODIN?
If just ODIN, it could still be anything from the Phone > USB cable > PC
If it says it on the phone, without being connected to the PC/USB, then yea it's gonna be something on the phone
Click to expand...
Click to collapse
It says it on the phone when it is not connected to PC. After (unsuccessful) flash on phone appears lines "MMC: mmc_read failed" and "ODIN: flash read failure".
DroidTim said:
It says it on the phone when it is not connected to PC. After (unsuccessful) flash on phone appears lines "MMC: mmc_read failed" and "ODIN: flash read failure".
Click to expand...
Click to collapse
I have a same issue with my g900f any solution plz