My note 3 failed during odin firmware update to KitKat 4.4.2 - Galaxy Note 3 Q&A, Help & Troubleshooting

Now I can’t install firmware or go into recovery mode but I can still get to download screen.

okizen said:
Now I can’t install firmware or go into recovery mode but I can still get to download screen.
Click to expand...
Click to collapse
Cant you go to the download screen and set ODIN away again?
Thats how I did it.

trubster said:
Cant you go to the download screen and set ODIN away again?
Thats how I did it.
Click to expand...
Click to collapse
Hi trubster, I've reset odin and my phone into download mode several times. The odin update process starts off ok but always fails when it reaches 'SYSTEM'.

okizen said:
Hi trubster, I've reset odin and my phone into download mode several times. The odin update process starts off ok but always fails when it reaches 'SYSTEM'.
Click to expand...
Click to collapse
What message is ODIN giving in the white text box?
have you tried re-downloading the ROM? I used the MEGA link and it worked fine.
N9005XXUENA6_N9005OXXENA5_XEO.zip is the one you need if it is for the N9005, you need the stock 4.4.2 FW before you can put CFW on

trubster said:
What message is ODIN giving in the white text box?
have you tried re-downloading the ROM? I used the MEGA link and it worked fine.
N9005XXUENA6_N9005OXXENA5_XEO.zip is the one you need if it is for the N9005, you need the stock 4.4.2 FW before you can put CFW on
Click to expand...
Click to collapse
These are the messages I get from odin (from the beginning).
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
I should also mention that I has tripped my Knox to 0x1as I've always got on without one but I doubt if that would be the cause.

That file seems to be different, are you using a N9005?
https://mega.co.nz/#!jZYkyY5a!HfiJlXRgp_ZGWoQncFNWeEn5FnY_0i9iFb23EGfg2Nk
Thats the file I used first, put it in the PDA or AP box on odin and click start.
Should have no problems with it as it is an "Official" Sammy Rom

If you have a Hong Kong note you need to have a read around, If not, grab XEO firmware flash via odin 1.85 or 3.07

trubster said:
That file seems to be different, are you using a N9005?
https://mega.co.nz/#!jZYkyY5a!HfiJlXRgp_ZGWoQncFNWeEn5FnY_0i9iFb23EGfg2Nk
Thats the file I used first, put it in the PDA or AP box on odin and click start.
Should have no problems with it as it is an "Official" Sammy Rom
Click to expand...
Click to collapse
Sorry trubster, I missed out a part of the message in odin.
This is the FULL message in it's entirety.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_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> 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!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
I've also tried the firmware from your link but unfortunately the results were the same.

I didn't experience this on my N9005 while updating, but I experienced this before on my S3, it was due to corrupted firmware file.

Please help me!!! Please!!!
okizen said:
sorry trubster, i missed out a part of the message in odin.
This is the full message in it's entirety.
<osm> enter cs for md5..
<osm> check md5.. Do not unplug the cable..
<osm> please wait..
<osm> n9005xxuena6_n9005oxxena5_n9005xxuena2_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> 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!!
<id:0/003> added!!
<id:0/003> removed!!
I've also tried the firmware from your link but unfortunately the results were the same.
Click to expand...
Click to collapse
i am also having this problem
it seems i cant flash other firmware other than poland fw...
I want ro revert back to ksa firmware or anygood fw since poland svoice isnt working fine<< sorry for bag english
please help me
i have flash my fw with kk italy, and spain but to luck,,, still having the same result... Failed!!!
Please please

u have to download hungry firmwar from sammobiles.com..it will b ok.and tick update boot loader must

clowrid1128 said:
i am also having this problem
it seems i cant flash other firmware other than poland fw...
Click to expand...
Click to collapse
I had the same problem... Just try to flash with this version of ODIN:
https://mega.co.nz/#!RVVXSYiY!6lynzTh-II8o8rvfYkdZzrYa_7m2F-CKgtItMZA66v4

I had the same problem today.The solution is here http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
Now i am with german kit kat (DBT) and everything is ok !!!!!! :good::good::good:

Help me (SAM SM-N900S)
<ID:0/023> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N900SKSU0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N900SKSU0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_SKT_N900SSKT0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N900SKSU0GPI1_CL9178490_QB10835717_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/023> Removed!!
<ID:0/028> Added!!
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> FAIL!
<ID:0/028>
<ID:0/028> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/028> Removed!!
<ID:0/028> Added!!
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> FAIL!
<ID:0/028>
<ID:0/028> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/028> Removed!!
:crying:

Why are you flashing Kitkat ??
What phone have you got and what have you done before .
PIT showing as no partition fail .

Related

Phone is not rooting

Hello!
I just update my n900 to android 4.4.2 (Rusia) and it get installed OK, but when i download the CF AUTO ROOT method to root the device as i did with 4.3 it stuck in the "cache.img" and after a few minutes it gives me an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-ha3g-ha3gxx-smn900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am using all the correct files and when i reflash 4.4.2 it works fine, but not root
Any idea?
yamwt said:
Hello!
I just update my n900 to android 4.4.2 (Rusia) and it get installed OK, but when i download the CF AUTO ROOT method to root the device as i did with 4.3 it stuck in the "cache.img" and after a few minutes it gives me an error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-ha3g-ha3gxx-smn900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am using all the correct files and when i reflash 4.4.2 it works fine, but not root
Any idea?
Click to expand...
Click to collapse
Use this method http://forum.xda-developers.com/showthread.php?t=2614787

[Q] Cricket sasmung s4 bricked HELP!!

Alright so I bricked my s4 while rooting it, It says something happened when updating the firmware, I did what people said use odin and flash to stock but i keep getting the error
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> R970CVVUFNC6_R970CCRIFNC6_R970CVVUFNC6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
If anyone could help that would be great!
arkk431 said:
Alright so I bricked my s4 while rooting it, It says something happened when updating the firmware, I did what people said use odin and flash to stock but i keep getting the error
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> R970CVVUFNC6_R970CCRIFNC6_R970CVVUFNC6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
If anyone could help that would be great!
Click to expand...
Click to collapse
Hi,
What stock you had and what stock rom are you trying to flash?
also check this thread
http://forum.xda-developers.com/showthread.php?t=2265477
Its the stock file for the cricket schr970c and that threads for model specific only.
arkk431 said:
Its the stock file for the cricket schr970c and that threads for model specific only.
Click to expand...
Click to collapse
Sorry mate
i did not realice you had an S4 cricket , the thread i gave you is not for your device..

[Q] Odin: Need i9505 Pit File

Hey Guys,
please help me, i just bricked my phone i cant boot in Rom/Recovery, only in Download Modus i can boot, but when i want to reflash a recovery (Like TWRP) it says:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM>I9505XXUHOF2_I9505OXAHOF2_DBT.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
So i downloaded an older i9505 PIT File and tried it again, but then this comes:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOF2_I9505OXAHOF2_DBT.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Samsung Galaxy S4 GT-i9505 - Android 5.01
Im using Odin v 3.09
Firmware: Germany
So i think i need a PIT File for my Version of Firmware: (Newest)I9505XXUHOF2_I9505OXAHOF2_DBT
I dont know if Im right...
Thanks for Help!
lolmann101 said:
Thanks for Help!
Click to expand...
Click to collapse
Use other USB cable or the original of Samsung.
Joku1981 said:
Use other USB cable or the original of Samsung.
Click to expand...
Click to collapse
Hello,
I tried it with the original S4 cable & with some others (HTC, NoName, etc.). It doesnt work!
lolmann101 said:
Hello,
I tried it with the original S4 cable & with some others (HTC, NoName, etc.). It doesnt work!
Click to expand...
Click to collapse
Then other USB port.
Zipped and attached PIT file for I9505XXUHOF2_I9505OXAHOF2_DBT
Downloaded directly from Samsung Kies.

Odin3 Error | Note 4

Hi,
I am trying to go back android 5 from 6. So I download the custom 5.1.1 rom. But odin keeps failing. ( Usb driver is fine. )
Galaxy Note 4 SM-910CQ - 32GB
HTML:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I have the same problem. Mine stops at system.ext4 write.
we both need help pls guys
I need help too,
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Hi friends, I just figured it out....
What you need to do is Download the Stock 6.0.1 Rom from SamMobile and flash it thru Odin, and that's it !!
Hope this works for you as worked for me!
5
Thank you for respond but I am not asking for 6.0.1 Rom
I want to go back to Android 5 from 6.
You cannot flash a custom ROM with ODIN . Use TWRP for that. And for going back to Lollipop, you need to flash a suitable Bootloader and Modem first.
looks like I need to google it...
what about cyanogenmode ? anyone of you used it before (note4)
opticon107 said:
I need help too,
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
I just f,gured it by myself.
dont flash the 1st file from odin only flash the file

Constant Reboot cycle

I have a Galaxy Tab A 8" (SM-T380) which just received a security update (2019-11-30) and now it just constantly reboots -- gets to the logo screen and then just reboots again. Tried using the hardware reset (needle hole) and it didn't even recognize it. Tried holding the Power+VolUp button to get to the recovery screen and that initially displays the blue "Installing system update" screen for a split-second and then it shows a blue Error screen for a another split-second and then goes back to the reboot cycle again.
Looking for some recommendations. The balance of the post describes what I've tried but I found this page which describes applying a custom recovery. Is that my best next option?
I ran Odin3 and, while I couldn't get it into the recovery screen, I was successful getting it to the download screen. I downloaded the FW update (XAR-T380DXU3CSK1-20191125134039) from SamFRew. This page on using Odin said I only needed the AP file, so I selected the AP file and after the MD5 was confirmed clicked start but it failed (see below).
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img.lz4
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Further searching led to this page which says you always need to flash all four files. This FW download didn't include the CP (modem) file but I selected the BL, AP, and HOME_CSC and clicked Start again. It says it succeeded (see below) but it is still just back to the reboot cycle.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> aboot.mbn.lz4
<ID:0/003> sbl1.mbn.lz4
<ID:0/003> rpm.mbn.lz4
<ID:0/003> tz.mbn.lz4
<ID:0/003> devcfg.mbn.lz4
<ID:0/003> cmnlib.mbn.lz4
<ID:0/003> keymaster.mbn.lz4
<ID:0/003> apdp.mbn.lz4
<ID:0/003> msadp.mbn.lz4
<ID:0/003> NON-HLOS.bin.lz4
<ID:0/003> lksecapp.mbn.lz4
<ID:0/003> sec.dat.lz4
<ID:0/003> boot.img.lz4
<ID:0/003> recovery.img.lz4
<ID:0/003> system.img.ext4.lz4
<ID:0/003> persist.img.ext4.lz4
<ID:0/003> userdata.img.ext4.lz4
<ID:0/003> modem.bin.lz4
<ID:0/003> adspso.bin.lz4
<ID:0/003> cache.img.ext4.lz4
<ID:0/003> Home Binary Download
<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> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
AdvApp said:
I have a Galaxy Tab A 8" (SM-T380) which just received a security update (2019-11-30) and now it just constantly reboots -- gets to the logo screen and then just reboots again. Tried using the hardware reset (needle hole) and it didn't even recognize it. Tried holding the Power+VolUp button to get to the recovery screen and that initially displays the blue "Installing system update" screen for a split-second and then it shows a blue Error screen for a another split-second and then goes back to the reboot cycle again.
Looking for some recommendations. The balance of the post describes what I've tried but I found this page which describes applying a custom recovery. Is that my best next option?
I ran Odin3 and, while I couldn't get it into the recovery screen, I was successful getting it to the download screen. I downloaded the FW update (XAR-T380DXU3CSK1-20191125134039) from SamFRew. This page on using Odin said I only needed the AP file, so I selected the AP file and after the MD5 was confirmed clicked start but it failed (see below).
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img.lz4
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Further searching led to this page which says you always need to flash all four files. This FW download didn't include the CP (modem) file but I selected the BL, AP, and HOME_CSC and clicked Start again. It says it succeeded (see below) but it is still just back to the reboot cycle.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> aboot.mbn.lz4
<ID:0/003> sbl1.mbn.lz4
<ID:0/003> rpm.mbn.lz4
<ID:0/003> tz.mbn.lz4
<ID:0/003> devcfg.mbn.lz4
<ID:0/003> cmnlib.mbn.lz4
<ID:0/003> keymaster.mbn.lz4
<ID:0/003> apdp.mbn.lz4
<ID:0/003> msadp.mbn.lz4
<ID:0/003> NON-HLOS.bin.lz4
<ID:0/003> lksecapp.mbn.lz4
<ID:0/003> sec.dat.lz4
<ID:0/003> boot.img.lz4
<ID:0/003> recovery.img.lz4
<ID:0/003> system.img.ext4.lz4
<ID:0/003> persist.img.ext4.lz4
<ID:0/003> userdata.img.ext4.lz4
<ID:0/003> modem.bin.lz4
<ID:0/003> adspso.bin.lz4
<ID:0/003> cache.img.ext4.lz4
<ID:0/003> Home Binary Download
<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> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Did you try flashing CSC not HOME_CSC? that will wipe your device which might bring you out of the bootloop.
I did not. I ended up sending it back to Samsung for repair.

Categories

Resources