[Q] Beginner Note 3 flashing failed.....please help..... - Galaxy Note 3 Q&A, Help & Troubleshooting

Hey guys,
I'm a noobie to flashing my phone and have attempted to do so, with no success and now my device is bricked.....so i'm looking for a handout here before I totally give up and see if the local Verizon store will help me at this point.....
Here's the story,
I attempted to installed a custom ROM using Safe strap, but couldn't get it to take. So, I then decided I no longer wanted my phone rooted. Downloaded an MD5 file, and used ODIN to attempt to flash it back to stock. Hit start in ODIN, then immediately got an error message, and now my phone only says that a firmware installation has failed and use the backup program.
Ok, so I tried downloading the MD5 file again and still have the same results. I keep getting the following screen when I attempt to flash it via ODIN on my phone:
ODIN MODE
Product Name: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: OxO
KNOX WARRANTY VOID: Ox1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A3, P1
WRITE PROTECTION: Enable
UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
So I have no idea what i've done here by poking at it......and have no idea what to do now besides crawl for help and ask for forgiveness at Verizon.....
I'm currently downloading the latest MD5 file from Sammobile.com in a last attempt. The previous MD5 files were obtained via other sites.
Again, any help is appreciated.....

moparman20 said:
Hey guys,
I'm a noobie to flashing my phone and have attempted to do so, with no success and now my device is bricked.....so i'm looking for a handout here before I totally give up and see if the local Verizon store will help me at this point.....
Here's the story,
I attempted to installed a custom ROM using Safe strap, but couldn't get it to take. So, I then decided I no longer wanted my phone rooted. Downloaded an MD5 file, and used ODIN to attempt to flash it back to stock. Hit start in ODIN, then immediately got an error message, and now my phone only says that a firmware installation has failed and use the backup program.
Ok, so I tried downloading the MD5 file again and still have the same results. I keep getting the following screen when I attempt to flash it via ODIN on my phone:
ODIN MODE
Product Name: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: OxO
KNOX WARRANTY VOID: Ox1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A3, P1
WRITE PROTECTION: Enable
UDC START
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
So I have no idea what i've done here by poking at it......and have no idea what to do now besides crawl for help and ask for forgiveness at Verizon.....
I'm currently downloading the latest MD5 file from Sammobile.com in a last attempt. The previous MD5 files were obtained via other sites.
Again, any help is appreciated.....
Click to expand...
Click to collapse
You tried downgrading your bootloader. Flash your latest if you can find it.

Thank you for the help!
Is there any possibility I could ask for some help as to where to find the bootloader file? I'm assuming you find and download the file, then add it under the BL box in ODIN, in addition to checking the [Phone Bootloader Update] box?
Again, thank you for the help, I have no idea what to do next other than what you have helped with......and no phone now due to my own incompetence.....

moparman20 said:
Thank you for the help!
Is there any possibility I could ask for some help as to where to find the bootloader file? I'm assuming you find and download the file, then add it under the BL box in ODIN, in addition to checking the [Phone Bootloader Update] box?
Again, thank you for the help, I have no idea what to do next other than what you have helped with......and no phone now due to my own incompetence.....
Click to expand...
Click to collapse
If you have the N900V firmware file to upgrade to, the bootloader will automatically be flashed in the PDA all-in-one file. No firmware comes without a bootloader already inside.
Just flash the latest firmware using Odin (if you can) and then everything will be flashed as a new system except your data which may remain.

nicholaschum said:
If you have the N900V firmware file to upgrade to, the bootloader will automatically be flashed in the PDA all-in-one file. No firmware comes without a bootloader already inside.
Just flash the latest firmware using Odin (if you can) and then everything will be flashed as a new system except your data which may remain.
Click to expand...
Click to collapse
Got it. So, most likely what's happening is the MD5 (Frimware file) i'm trying to flash has an older bootloader than what's already on the phone, so i'm getting the error message telling me this. In essence, the phone is telling me i'm trying to downgrade and not allowing it.
I have located a new Frimware file via sammobile.com by typing in my model number (N900V) and the date was April 2014 for the file. Hopefully this is the right one, otherwise, I have no idea what to do next......as this is the latest file I can find by my limited experience/means.
So, once the download completes (not a paid member on sammobile) in about an hour, i'll give it a shot via ODIN and hopefully it works this time.
I will keep this thread updated as to the success/failure. Again, thank you for the help.......I have no idea what to do at this point other than take it in to the store and get scolded by them. Hopefully this MD5 file from sammobile is the right one

moparman20 said:
Got it. So, most likely what's happening is the MD5 (Frimware file) i'm trying to flash has an older bootloader than what's already on the phone, so i'm getting the error message telling me this. In essence, the phone is telling me i'm trying to downgrade and not allowing it.
I have located a new Frimware file via sammobile.com by typing in my model number (N900V) and the date was April 2014 for the file. Hopefully this is the right one, otherwise, I have no idea what to do next......as this is the latest file I can find by my limited experience/means.
So, once the download completes (not a paid member on sammobile) in about an hour, i'll give it a shot via ODIN and hopefully it works this time.
I will keep this thread updated as to the success/failure. Again, thank you for the help.......I have no idea what to do at this point other than take it in to the store and get scolded by them. Hopefully this MD5 file from sammobile is the right one
Click to expand...
Click to collapse
The MD5 single file should be the AIO file that you only need to flash through AP, and it will handle everything by itself.

The file from sammobile.com flashed perfect! I have a phone again, thank you so much! I see my KNOX counter is still set to 0x1, I assume that will always indicate it has been tampered with?

moparman20 said:
The file from sammobile.com flashed perfect! I have a phone again, thank you so much! I see my KNOX counter is still set to 0x1, I assume that will always indicate it has been tampered with?
Click to expand...
Click to collapse
Yeah KNOX 0x1 is permanent. No problem, next time just use the Thanks button!

Related

[Q] SM-N900K Stuck on Odin Mode "“Firmware upgrade encountered an issue"

I have a Korean model Note 3 that I rooted a while back. Tonight I updated the firmware over Kies, everything went fine, then tried to re-root using the same method I previously used (CF Auto root). Obviously a mistake.
Now my phone is stuck on Odin Mode, displaying the "Firmware upgrade encountered an issue" screen. (It actually displays it in Korean but it's the same screen).
Here is what it says:
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
After I unsuccessfully attempted use CF Auto Root is also says "Unsupport dev_type" in red at the bottom.
The biggest problem I'm having is that I don't know what to flash. The SM-N900K seems to be an uncommon model, at least in the English speaking world. In fact, when I first rooted I couldn't find the appropriate file for this model so I used the N900 or N900s (which is another Korean model), I can't remember which.
If anyone has any suggestions for how I can fix this, it is greatly appreciated.
More
Update: I flashed the Cf Auto Root for the SM-N900S .
Now I am no longer stuck at the "Firmware upgrade encountered an error mode" but at the regular Odin download mode. Also able to access recovery mode. Still unsure of how to get my phone back track.
Update again:
Was able to install the SM-N900S Clockwork Mod. However, still unable to boot normally. Any help appreciated
Is there any chance I can get back into my phone the way it was, without losing all my data? Or will I need to do a factory reset?
Flash the latest firmware for this model
Sent from my LT26i using Tapatalk
Coolmfarshard said:
Flash the latest firmware for this model
Sent from my LT26i using Tapatalk
Click to expand...
Click to collapse
I am unable to find firmware for SM-N900K, and am wary that if I flash the SM-N900S firmware, it will mess up the phone somehow (they are for different carriers)
You should wipe data/cache partition/dalvik.... and try flashing a custom rom. Sees if it boots up then
Sent from my SM-N9005 using Tapatalk
I was able to install Lidroid ROM successfully, but after reboot it returns to the same Odin Mode screen as before.
dadaclonefly said:
I was able to install Lidroid ROM successfully, but after reboot it returns to the same Odin Mode screen as before.
Click to expand...
Click to collapse
I guess the only way is to wait the official firmware for sm-n900k(KT).
Can you give a picture of the screen at all.... Best bet is goto samfirmware and find the latest firmware for your phone and flash with Odin... If that don't work.. Try the sm9005 mj7 firmware. ... Though Not sure if it will make things worse or not
Sent from my SM-N9005 using Tapatalk
alom5 said:
Can you give a picture of the screen at all.... Best bet is goto samfirmware and find the latest firmware for your phone and flash with Odin... If that don't work.. Try the sm9005 mj7 firmware. ... Though Not sure if it will make things worse or not
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I can't give a picture of the screen but this is what it says:
Could not do normal boot
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
Below that there is the green Android logo and it says Downloading Mode (in Korean) and Do not turn off (in Korean)
Edit: Also, samfirmware.com does not have firmware for the SM-N900K unfortunately, only the SMN900S. Does anyone know where I can download other Korean firmwares?
If I try to flash SM-N900S Firmware my phone says the same as before, with the following at the bottom:
SECURE CHECK FAIL : sbl1
So it looks this in download mode:
Could not do normal boot
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
SECURE CHECK FAIL : sbl1
Have you tried kies since you had this error? I had problem before and it said to use kies to restore.
It looks like the bootloader... and you may have to wait until you find the original firmware. ..
What version of odin are you using? I use 3.09 ... Try that if you are on a older version.
Sent from my SM-N9005 using Tapatalk
alom5 said:
Have you tried kies since you had this error? I had problem before and it said to use kies to restore.
It looks like the bootloader... and you may have to wait until you find the original firmware. ..
What version of odin are you using? I use 3.09 ... Try that if you are on a older version.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I've tried both 3.09 and 1.85 versions of Odin. And Kies won't recognize the device, unfortunately.
dadaclonefly said:
update: I flashed the cf auto root for the sm-n900s .
Now i am no longer stuck at the "firmware upgrade encountered an error mode" but at the regular odin download mode. Also able to access recovery mode. Still unsure of how to get my phone back track.
Update again:
Was able to install the sm-n900s clockwork mod. However, still unable to boot normally. Any help appreciated
Click to expand...
Click to collapse
good stuff ...
In case anyone happens on this thread while trying to resolve a similar issue, the resolution was that I was unable to fix it on my own. I took it to the Samsung Service Center and they reinstalled the original firmware despite the Knox warranty having been tripped.
dadaclonefly said:
In case anyone happens on this thread while trying to resolve a similar issue, the resolution was that I was unable to fix it on my own. I took it to the Samsung Service Center and they reinstalled the original firmware despite the Knox warranty having been tripped.
Click to expand...
Click to collapse
Did they reset the knox for you?
Sent from my SM-N9005 using Tapatalk
sm n900k
dadaclonefly said:
I have a Korean model Note 3 that I rooted a while back. Tonight I updated the firmware over Kies, everything went fine, then tried to re-root using the same method I previously used (CF Auto root). Obviously a mistake.
Now my phone is stuck on Odin Mode, displaying the "Firmware upgrade encountered an issue" screen. (It actually displays it in Korean but it's the same screen).
Here is what it says:
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
After I unsuccessfully attempted use CF Auto Root is also says "Unsupport dev_type" in red at the bottom.
The biggest problem I'm having is that I don't know what to flash. The SM-N900K seems to be an uncommon model, at least in the English speaking world. In fact, when I first rooted I couldn't find the appropriate file for this model so I used the N900 or N900s (which is another Korean model), I can't remember which.
If anyone has any suggestions for how I can fix this, it is greatly appreciated.
Click to expand...
Click to collapse
I have the same sm n900k.. I successfuly rooted it using sm n900s..via odin.. also the CWM recovery from 900s.
Can I reroot again doing the same procedure via odin because I have unrooted it via supersu .. can I also re install CWM recovery since I updated it at Rom Manager and it show different version now.but it ia still working..
by the way can you post the link of the Lidroid rom you use for sm 900k if it worked out well..thanks!!
im about to get a Note 3 from olleh KT and it is sm-n900k version. also i have messed up a phone trying to root before and took it to kt and a few days they gave me back my phone in working order. they dont seem to care to much if u ruin your phone by software problems. but has any one found how to root note 3 sm-n900k version so i can try it out?
thedawg03 said:
im about to get a Note 3 from olleh KT and it is sm-n900k version. also i have messed up a phone trying to root before and took it to kt and a few days they gave me back my phone in working order. they dont seem to care to much if u ruin your phone by software problems. but has any one found how to root note 3 sm-n900k version so i can try it out?
Click to expand...
Click to collapse
That depends on which exact firmware version you are on.
Pop over to the Galaxy Note 3 Korean Users Thread for more info!
Try this one for SMN-N900K : http://pan.baidu.com/s/1jGA1F98
Tested to be working.

my phone us stucked after att pushed an update!

please help. I had wifi on last night at home, i saw att pushed through an update but I couldn't stop it. it says updating management files.
when the phone tried to reboot, I got stuck on
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION ENABLE
EMMC BURST MODE ENABLED
Downloading... do not turn off target!! screen
please help, what should i do now?
I take it that it won't reboot now? Do you know what firmware version you were on before the ota update?
Sent from my Nexus 5 using XDA Free mobile app
hotwell said:
please help. I had wifi on last night at home, i saw att pushed through an update but I couldn't stop it. it says updating management files.
when the phone tried to reboot, I got stuck on
Could not do normal boot.
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION ENABLE
EMMC BURST MODE ENABLED
Downloading... do not turn off target!! screen
please help, what should i do now?
Click to expand...
Click to collapse
Is there a blue bar on the bottom?
Download Odin and choose a package from
http://forum.xda-developers.com/showthread.php?t=2616221
I would choose NB1 tr rootable version
http://forum.xda-developers.com/showthread.php?t=2674223
Reflash your firmware, you will loose all data but hey, your phone will work again
autonomousperson said:
Download Odin and choose a package from
http://forum.xda-developers.com/showthread.php?t=2616221
I would choose NB1 tr rootable version
http://forum.xda-developers.com/showthread.php?t=2674223
Reflash your firmware, you will loose all data but hey, your phone will work again
Click to expand...
Click to collapse
You're probably right. But are you sure he's not on mdl firmware? It would really suck if he is and he updated to nb1
Sent from my Nexus 5 using XDA Free mobile app
True, I guess he can just restore to MDL firmware...
He was in the middle of a update so I was just assuming that the BL is already locked
i don't remember the firmware. it was rooted with towelroot. it gets stucked with the screen that says downloading, do not turn off. no loading bar.
Just do a factory restore with odin... You will loose all your data! But I dont see any other way unless you have a unlocked bl and a custom recovery.
autonomousperson said:
Download Odin and choose a package from
http://forum.xda-developers.com/showthread.php?t=2616221
I would choose NB1 tr rootable version
http://forum.xda-developers.com/showthread.php?t=2674223
Reflash your firmware, you will loose all data but hey, your phone will work again
Click to expand...
Click to collapse
i tried to recovery with odin nb1 tr rootable version. when everything was completed, it says failed. on the screen, i see a msg telling me to get on recovery mode and connect to kies for recovery. I connected to kies, nothing can be detected... help please
finally got it to work! after i ran nb1 tr rootable version, it failed, then i did more digging and ran pit from this thread! http://forum.xda-developers.com/showthread.php?t=2404970
got it to work!
I guess your partitions were messed up if you needed to flash a pit file to fix it
autonomousperson said:
I guess your partitions were messed up if you needed to flash a pit file to fix it
Click to expand...
Click to collapse
before i flashed pit, i tried to flash stock firmware as suggested. no go. then flashed pit, it booted. root was removed. samsung keyboard failed to load. i tried to flash the stock firmware again but it still crash and failed to boot. i had to flash pit again... help please!!!
hotwell said:
before i flashed pit, i tried to flash stock firmware as suggested. no go. then flashed pit, it booted. root was removed. samsung keyboard failed to load. i tried to flash the stock firmware again but it still crash and failed to boot. i had to flash pit again... help please!!!
Click to expand...
Click to collapse
Did you try to root it afterwards? I thought you got it to work. What did you do to kill it?
autonomousperson said:
Did you try to root it afterwards? I thought you got it to work. What did you do to kill it?
Click to expand...
Click to collapse
omg! finally flashed stock firmware!!! my oem cable was bad!!!!! I used another cable!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! took me a whole week before I had time to fix this bs! thank you everyone for your supports!
Haha I was just about to suggest that.. You have no idea how many times ive flipped tables trying to figure out what drivers are not working when it was the cable all along

Trying to root desperatly Galaxy Note 3 already under Lollipop

Hello everybody
I have Galaxy Note 3 SM-N9005 (purchased in France), That has never been rooted, and which is already under Lollipop (regular updates by Samsung)
I would like to root it in order to be able to use some apps that only work under rooted devices.
I went through all the forums, tried all I could, but didn't succeed.
I tryed :
Towelroo
t, but it seems it doesn't have the stratedy for this version or this android version
Kingroot, but it seems it doesn't have the stratedy for this version or this android version
Via Odin, CF-auto-root, but I always get a "FAIL"!
Via Odin, CWM- recovery , but always get a "FAIL" or Odin bugs..
Via Odin, Twrp, but always get a "FAIL" or Odin bugs..
I'm not an expert at all, but really tried my best... I seems there ar elots of things to root a GN3 under Kikkat, but it is more difficult to root when it is already under Lollipop..
Would you have any advice?
Thanks in advance,
Christian
kri72 said:
Hello everybody
I have Galaxy Note 3 SM-N9005 (purchased in France), That has never been rooted, and which is already under Lollipop (regular updates by Samsung)
I would like to root it in order to be able to use some apps that only work under rooted devices.
I went through all the forums, tried all I could, but didn't succeed.
I tryed :
Towelroo
t, but it seems it doesn't have the stratedy for this version or this android version
Kingroot, but it seems it doesn't have the stratedy for this version or this android version
Via Odin, CF-auto-root, but I always get a "FAIL"!
Via Odin, CWM- recovery , but always get a "FAIL" or Odin bugs..
Via Odin, Twrp, but always get a "FAIL" or Odin bugs..
I'm not an expert at all, but really tried my best... I seems there ar elots of things to root a GN3 under Kikkat, but it is more difficult to root when it is already under Lollipop..
Would you have any advice?
Thanks in advance,
Christian
Click to expand...
Click to collapse
Update drivers on pc and the latest odin also make sure your cf is for lollipop and your reactivation lock is off failing that try the latest firmware or a prerooted one
HYBRID
Yeah make sure the drivers are installed on PC! If you are on an updated version of Windows 7 or 10 as soon as you connect the phone to your PC the drivers will be automatically downloaded for your phone, unless you have Windows auto update disabled.
When you are connecting the phone to Odin you SHOULD see the connection confirmation message as in com0, com1 or whatever. See the attached screenshot if that helps.
And I have no idea about those root methods, but for rooting a N9005 it's extremely easy. Just download TWRP from here, https://twrp.me/ Flash it with Odin. Download the .tar image obviously as you are using Odin. Then download this Super SU zip and flash via TWRP, https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
A bit better..
Hello.. Thanks to both of you.. There is a little bit progress..
Indeed, there was an issue with the reactivation lock.. Then I succeeded in installing some files.. some failed some succeeded.
I tried the CF-auto-boot and CWM. Then I also tried to run the SuperSU file..
However, I'm not sure all is working ok..
- When I use the Root Checker Basic, it says "Congratulations!, Root access is properly installer on this device.
- However, I installed Titanium backup, and a windows ask me "Requete Super Utilisateur"... However, I cannot click on neither "Refuse" or "Authorize"...?? (Same issue with Greenify!)
So At the end, I don't really what is installed, what is not, what is working! How should I proceed to make sure I can use such app, such as Titanium backup, Greenify, JuiceDefenders, etc?
- When I press Start/Home/VolDown, I get :
"Odin Mode
Product name : SM-N9005
Current Binary : Custom
System status : Custom
Reactivation Lock : Off
Knox Warranty Void : 0x1 (4)
Qualcomm Secureboot : Enable (CSB)
RP Swrev S2, T2, R2, A3, P3
Secure download : Enable
UDC Start"
- When I press Start/Home/VolUp, I get the file attached.
Thanks in advance for your help!
Christian

hardware or software issue ...help

my note 3 model is n9005 it's charge normaly with the notification led working 100% but when i boot it, it doesn't boot it Freezes for a second on the samsung note 3 n9005 and turn off again i tried to format it via recovery and it doesn't boot too it Freezes again on recovery booting and then to odin download mode with these massages : could not do normal boot.
ddi : mmc_read failed
odin mode
prouduct name: sm-n9005
current binary: samsung official
system status: custom
reactivation lock: 0x0
knox kernel lock: 0x0
knox warranty void: 0x0
qualcom secureboot: enable (csb)
rp swrev: s2, t2, r2, a3, p3
write protection: enable
udc start
if someone have any idea please help
make it the boss said:
my note 3 model is n9005 it's charge normaly with the notification led working 100% but when i boot it, it doesn't boot it Freezes for a second on the samsung note 3 n9005 and turn off again i tried to format it via recovery and it doesn't boot too it Freezes again on recovery booting and then to odin download mode with these massages : could not do normal boot.
ddi : mmc_read failed
odin mode
prouduct name: sm-n9005
current binary: samsung official
system status: custom
reactivation lock: 0x0
knox kernel lock: 0x0
knox warranty void: 0x0
qualcom secureboot: enable (csb)
rp swrev: s2, t2, r2, a3, p3
write protection: enable
udc start
if someone have any idea please help
Click to expand...
Click to collapse
need more information than that.
ok..
have you installed stock rom via ODIN from fresh ? or just trying to recover what is installed on the phone ?
if NOT odin then you need to flash stock rom again via odin and test again.
if YES then may be, may be it is hardware related (last option to consider).
BUT you need to do the steps above. then we can only reach on a proper solution.
dark_phoenix said:
need more information than that.
ok..
have you installed stock rom via ODIN from fresh ? or just trying to recover what is installed on the phone ?
if NOT odin then you need to flash stock rom again via odin and test again.
if YES then may be, may be it is hardware related (last option to consider).
BUT you need to do the steps above. then we can only reach on a proper solution.
Click to expand...
Click to collapse
i tried all of this but nothing worked, i even tried to fix it via samsung customer service, but they said ''you need to replace the motherbord '' so if you know what's the bad chip that's the cause of all of this i'll be thankful
make it the boss said:
i tried all of this but nothing worked, i even tried to fix it via samsung customer service, but they said ''you need to replace the motherbord '' so if know what's the bad chip that's the cause of all of this i'll be thankful
Click to expand...
Click to collapse
probably a corrupted partition due to some error.
try getting a .PIT file for N9005,
and flash it via odin along with stock rom.
1. search google -- there are various PIT files on SamMobile. Download the N9005 hlte BTU version.
2. here is another link for you
https://forum.xda-developers.com/showthread.php?t=2550823
and which version of rom are you trying flashing ?
dark_phoenix said:
probably a corrupted partition due to some error.
try getting a .PIT file for N9005,
and flash it via odin along with stock rom.
1. search google -- there are various PIT files on SamMobile. Download the N9005 hlte BTU version.
2. here is another link for you
https://forum.xda-developers.com/showthread.php?t=2550823
and which version of rom are you trying flashing ?
Click to expand...
Click to collapse
i tried (samsony) one, specifically the 5.0 lollipop official rom , here is odin when i tried flashing it with the pit file. https://photos.app.goo.gl/vGc9vBP8xDcxgYRT7 ,
the download also have these new messages : MMC: mmc_read fail
odin : flash read failure
make it the boss said:
i tried (samsony) one, specifically the 5.0 lollipop official rom , here is odin when i tried flashing it with the pit file. https://photos.app.goo.gl/vGc9vBP8xDcxgYRT7 ,
the download also have these new messages : MMC: mmc_read fail
odin : flash read failure
Click to expand...
Click to collapse
change cables. (may be cable is somehow not working properly.)
use updated ODIN version. ( you are using old version)
use this PIT file. this is TGY version. (Android 5.0)
https://forum.xda-developers.com/showpost.php?p=67773525&postcount=16
after then flash stock firmware. (preferably TGY one.)
if nothing works even now... then your mmc chip is corrupted and need to be replaced. the chip only if you can or the whole motherboard.
there is no harm in trying anything now, to revive it. so just do everything. don't lose hope. may be it will work.
dark_phoenix said:
change cables. (may be cable is somehow not working properly.)
use updated ODIN version. ( you are using old version)
use this PIT file. this is TGY version. (Android 5.0)
https://forum.xda-developers.com/showpost.php?p=67773525&postcount=16
after then flash stock firmware. (preferably TGY one.)
if nothing works even now... then your mmc chip is corrupted and need to be replaced. the chip only if you can or the whole motherboard.
there is no harm in trying anything now, to revive it. so just do everything. don't lose hope. may be it will work.
Click to expand...
Click to collapse
i tried that and the same error , so i guess then it's the emmc chip . but i still want to know the cause of it's death . do you have any idea ?!
make it the boss said:
i tried that and the same error , so i guess then it's the emmc chip . but i still want to know the cause of it's death . do you have any idea ?!
Click to expand...
Click to collapse
hmm..
that i don't know yet.
but in my opinion, if the emmc chip/motherboard is dead/corrupted/broken then it should not be detected by odin at all.
if it is being detected then it can be survived. but hey it is just an hypothesis.
imo the partition corruption chances are high like 85-95%. that can be repaired by available PIT file.
but i don't know any further than that.
and btw you didn't mentioned how it got corrupted ?
dark_phoenix said:
hmm..
that i don't know yet.
but in my opinion, if the emmc chip/motherboard is dead/corrupted/broken then it should not be detected by odin at all.
if it is being detected then it can be survived. but hey it is just an hypothesis.
imo the partition corruption chances are high like 85-95%. that can be repaired by available PIT file.
but i don't know any further than that.
and btw you didn't mentioned how it got corrupted ?
Click to expand...
Click to collapse
it's just died on me, i was changing the sim card and .... the phone won't start again , but, i'll try to re solder the chip and i'll tell you if it worked ! . thanks tho :good: :laugh:

[Q] T580 Tab A 10.1 Wifi- final suggestions for unbricking?

I am still having hope I can recover my bricked Tab A. If there are any other suggestions than what I have tried, I would love to know!
I have attempted flashing, multiple times, stock ROMs, custom ROMs, stock boot and recovery files, CF Autoroot all unsuccessful at getting to boot.
:crying:
I can only boot into Download mode:
Product Name: SM-T580
FRP Lock: Off
System Status: Custom
Current Binary: Custom
Secure Download: Enabled
Warranty Void: 1 (0x0500)
AP SWREV: B:-1 K:1 S:2
I can flash the T580UEU4CRK5_T580XAR4CRK7_XAR AP and CSC Files but not the Bootloader curiously.
I can flash twrp-3.2.3-4-gtaxlwifi-OMNI6 but the device will not boot into Recovery Mode. (couintless attempts.)
I was hoping if I could get into TWRP then I could wipe the cache etc. but attempts have been fruitless.
I am all out of ideas.....
Flutterfly said:
I am still having hope I can recover my bricked Tab A. If there are any other suggestions than what I have tried, I would love to know!
I have attempted flashing, multiple times, stock ROMs, custom ROMs, stock boot and recovery files, CF Autoroot all unsuccessful at getting to boot.
:crying:
I can only boot into Download mode:
Product Name: SM-T580
FRP Lock: Off
System Status: Custom
Current Binary: Custom
Secure Download: Enabled
Warranty Void: 1 (0x0500)
AP SWREV: B:-1 K:1 S:2
I can flash the T580UEU4CRK5_T580XAR4CRK7_XAR AP and CSC Files but not the Bootloader curiously.
I can flash twrp-3.2.3-4-gtaxlwifi-OMNI6 but the device will not boot into Recovery Mode. (couintless attempts.)
I was hoping if I could get into TWRP then I could wipe the cache etc. but attempts have been fruitless.
I am all out of ideas.....
Click to expand...
Click to collapse
Try this thread https://forum.xda-developers.com/galaxy-tab-a/themes/mod-twrp-odin-t3650215 . And if you come to recovery do factory reset. Then reboot. Maybe help.
Thanks, I started reading this thread last night and attempted to download but the mirrors didn't work.
Download
[2x1]MOD_SM-T580XXU4CRK5_with_twrp-3.2.3-4-gtaxlwifi_and_patched_boot_with_disabled dm-verity, forced encryption disabled, Selinux permissive _without_CSC.zip
for the Samsung Galaxy Tab A 10.1 (2016)(SM-T585), by repey6
response: dc3.androidfilehost.com sent an invalid response.
Can you check the links? Thanks again!
Flutterfly said:
Thanks, I started reading this thread last night and attempted to download but the mirrors didn't work.
Download
[2x1]MOD_SM-T580XXU4CRK5_with_twrp-3.2.3-4-gtaxlwifi_and_patched_boot_with_disabled dm-verity, forced encryption disabled, Selinux permissive _without_CSC.zip
for the Samsung Galaxy Tab A 10.1 (2016)(SM-T585), by repey6
response: dc3.androidfilehost.com sent an invalid response.
Can you check the links? Thanks again!
Click to expand...
Click to collapse
Links work. Change your browser.
I use chrome, latest version/ any other suggestions? I can get your other links to download
Got it thank you! Stupid antivirus
Thanks Repey6 for your assistance, The device still will not flash a bootloader file. Any ideas what could be causing this failure or if it's fixable?
The process fails at the write phase "param.bin".
Flutterfly said:
Thanks Repey6 for your assistance, The device still will not flash a bootloader file. Any ideas what could be causing this failure or if it's fixable?
The process fails at the write phase "param.bin".
Click to expand...
Click to collapse
2nd entry at DuckDuckGo:
https://forum.xda-developers.com/galaxy-s3/help/odin-flash-sboot-bin-param-bin-nand-t3546535
Does flashing CF-AutoRoot succeed?
No,
virsys said:
2nd entry at DuckDuckGo:
https://forum.xda-developers.com/galaxy-s3/help/odin-flash-sboot-bin-param-bin-nand-t3546535
Does flashing CF-AutoRoot succeed?
Click to expand...
Click to collapse
When I tried autoroot, I get a PIT file error. and it fails.
Flutterfly said:
When I tried autoroot, I get a PIT file error. and it fails.
Click to expand...
Click to collapse
Providing screenshots of Odin's process in the different scenarios (flashing stock, custom, twrp, autoroot) / logs would help.
Could be a hardware damage as well. Then you will have to RMA it.
Flutterfly said:
Thanks Repey6 for your assistance, The device still will not flash a bootloader file. Any ideas what could be causing this failure or if it's fixable?
The process fails at the write phase "param.bin".
Click to expand...
Click to collapse
Your device is showing a bootloader revision of -1.
This is incorrect. Which is why you're having issues flashing any boot loader.
Something similar happened to another member who ended up with a rev -2 bootloader and had similar issues on another device.
He managed to fix it after some messing and got it booting again.
If I find the thread I'll post it.
https://forum.xda-developers.com/galaxy-tab-a/help/help-tab-t380-oreo-flashing-t3857266
This is what I have done before successfully with a different Samsung Galaxy Tablet and I unbricked that particular tablet. I used Kies to restore the original stock ROM to the tablet and I re-rooted it by using Odin and flashed the correct TWRP to the tablet. If you can get TWRP to work on anything I'd have to say that your technically rooted even without Supersu or Magisk.

Categories

Resources