Develop Bugs

[Q] please help me guys my phone stuck on recovery

hi my phone interputerd while updating and i get firware upgrade encountered an issue.kies cant see my phone i downloaded stock room and flash it through odin as below
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ3_N7100OJVALJ2_N7100XXALJ2_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> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<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)
<ID:0/003> Removed!!
odin passed
phone went back to firware upgrade encountered an issue please select recovery mode in kies
please help

elaria1984 said:
hi my phone interputerd while updating and i get firware upgrade encountered an issue.kies cant see my phone i downloaded stock room and flash it through odin as below
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ3_N7100OJVALJ2_N7100XXALJ2_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> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<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)
<ID:0/003> Removed!!
odin passed
phone went back to firware upgrade encountered an issue please select recovery mode in kies
please help
Click to expand...
Click to collapse
What recovery are you using?
Stock?
If yes..
Try getting TWRP or CWM..
You can reboot to system through them or flash a rom or something..
Sent from my GT-N7100

Mohammed779 said:
What recovery are you using?
Stock?
If yes..
Try getting TWRP or CWM..
You can reboot to system through them or flash a rom or something..
Sent from my GT-N7100
Click to expand...
Click to collapse
i can only access download mode cant access cwm
please guys help

At first try another firmware (a newer one than N7100XXALJ3...)
If it doesn't chage try a factory firmware but normally this error message just means that you have to flash an 'one package' firmware.

Memphis_ said:
At first try another firmware (a newer one than N7100XXALJ3...)
If it doesn't chage try a factory firmware but normally this error message just means that you have to flash an 'one package' firmware.
Click to expand...
Click to collapse
i have tried 5 roms all the same in odin it pass phone try to reboot and go back to that message connect to kies for recovery.
any thoughts ?

Did you try a factory firmware?
A restore from Kies could be possible but I never tried: http://forum.xda-developers.com/showthread.php?t=2088809

Memphis_ said:
Did you try a factory firmware?
A restore from Kies could be possible but I never tried: http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
not all devices supprted in kies to do the above.
i cant find the factory firmware i wrote in google but i i didnt get anything could you please giude me from where to get it.
my device is GT-N7100

elaria1984 said:
not all devices supprted in kies to do the above.
i cant find the factory firmware i wrote in google but i i didnt get anything could you please giude me from where to get it.
my device is GT-N7100
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5

Memphis_ said:
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
Click to expand...
Click to collapse
i know i am asking tooo much please bare with me i dont know which one to donwload can i donwload anyone ? what is the diffrents between the three ?

elaria1984 said:
i know i am asking tooo much please bare with me i dont know which one to donwload can i donwload anyone ? what is the diffrents between the three ?
Click to expand...
Click to collapse
N7100XXDMB2 => not PIT file so forget it
N7100XXDLL7 => PIT file OK
N7100XXDLJ2 => PIT file OK
But DLJ2 doesn't have some important fixs so take the firmware XXDLL7.

Memphis_ said:
N7100XXDMB2 => not PIT file so forget it
N7100XXDLL7 => PIT file OK
N7100XXDLJ2 => PIT file OK
But DLJ2 doesn't have some important fixs so take the firmware XXDLL7.
Click to expand...
Click to collapse
thanks man the download didnt fininsh yet . once done i will get back with the result hope hope it will work

thanks man it didnt work i took it to samsung this morining they will fix it they charged me 40 $

Sorry mate...

[Q] Trouble with CF root and TWRP, should I factory reset?

Hi folks, I am trying to either install CF auto root or install TWRP recovery for my Verizon Galaxy note 4. I have the SM-N910V so I thought I wouldn't have any problems. When trying CFs auto root it fails and the log looks like this,
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-trltevzw-smn910v.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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I installed an update from samsung a few days ago. Could this be my problem? Do I need to factory reset to get the unlocked bootloader back?

skateguy1234 said:
Hi folks, I am trying to either install CF auto root or install TWRP recovery for my Verizon Galaxy note 4. I have the SM-N910V so I thought I wouldn't have any problems. When trying CFs auto root it fails and the log looks like this,
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltevzw-trltevzw-smn910v.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> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I installed an update from samsung a few days ago. Could this be my problem? Do I need to factory reset to get the unlocked bootloader back?
Click to expand...
Click to collapse
If you don't have a Developer Edition then you cannot root. Only the Developer Edition Note 4 can be rooted, not the retail version. If you did not buy your Note 4 directly from Samsung, not Verizon, then you have the retail version, not the Developer Edition. If your phone was advertised as "unlocked" and you did not buy it from Samsung, then you have a carrrier "unlocked" phone, not a bootloader unlocked phone.

jpcalhoun said:
If you don't have a Developer Edition then you cannot root. Only the Developer Edition Note 4 can be rooted, not the retail version. If you did not buy your Note 4 directly from Samsung, not Verizon, then you have the retail version, not the Developer Edition. If your phone was advertised as "unlocked" and you did not buy it from Samsung, then you have a carrrier "unlocked" phone, not a bootloader unlocked phone.
Click to expand...
Click to collapse
Thanks a lot for the reply. I have read on a few sites that the model SM-N910V was indicative of the developer model. I guess that is not the case? If not I hope someone is able to figure out a root solution. Is it possible that updating the samsung software from NI1 to NJ5 could lock the bootloader?

front
front

skateguy1234 said:
Thanks a lot for the reply. I have read on a few sites that the model SM-N910V was indicative of the developer model. I guess that is not the case? If not I hope someone is able to figure out a root solution. Is it possible that updating the samsung software from NI1 to NJ5 could lock the bootloader?
Click to expand...
Click to collapse
Yes if you're using the wrong firmware. There is a version that is safe for the Developer Editon in that it does not "touch" the bootloader. Look in the Android Development section of this forum.

skateguy1234 said:
Thanks a lot for the reply. I have read on a few sites that the model SM-N910V was indicative of the developer model. I guess that is not the case? If not I hope someone is able to figure out a root solution. Is it possible that updating the samsung software from NI1 to NJ5 could lock the bootloader?
Click to expand...
Click to collapse
The retail device's bootloader is already locked.

Help ... I HAVE THE DEVELOPERS EDITION and now I'm getting this exact same message/problem!

Stupid question, sorry, but I bricked my phone and I'm stumped...

So I followed the instructions here i found on google by searching "how to how to root s6 edge plus", second link down... and it was a bad idea. Now my phone will boot, and show the lock screen for a second or two, and then just reboot. So I'm stuck in a bootloop. I'm fairly new to the android rooting scene (I've been jailbreaking iPhones sice 2007). What do I do? I tried restoring the default firmware in Odin but it didn't work. HELP!

hereisalex said:
So I followed the instructions here i found on google by searching "how to how to root s6 edge plus", second link down... and it was a bad idea. Now my phone will boot, and show the lock screen for a second or two, and then just reboot. So I'm stuck in a bootloop. I'm fairly new to the android rooting scene (I've been jailbreaking iPhones sice 2007). What do I do? I tried restoring the default firmware in Odin but it didn't work. HELP!
Click to expand...
Click to collapse
Your phone is not bricked.
Best bet is to odin flash the official stock firmware and then go into recovery mode.
When in recovery do a factory reset.
Then reboot the phone.
After doing the above the phone will work fine.
Good luck,
Have a nice evening.
Sent from my SM-G928T using Tapatalk

Thank you for responding. I've done that, and it's failing. I tried to post a screenshot but XDA won't allow me since I"m a new user. So here's a transcript:
<ID:0/003> Added!!
<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> 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> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Perhaps I'm not using the right file? I have 20150409165121\G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5 if that means anything.
Thank you again for your help.
Misterjunky said:
Your phone is not bricked.
Best bet is to odin flash the official stock firmware and then go into recovery mode.
When in recovery do a factory reset.
Then reboot the phone.
After doing the above the phone will work fine.
Good luck,
Have a nice evening.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse

hereisalex said:
Thank you for responding. I've done that, and it's failing. I tried to post a screenshot but XDA won't allow me since I"m a new user. So here's a transcript:
<ID:0/003> Added!!
<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> 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> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Perhaps I'm not using the right file? I have 20150409165121\G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5 if that means anything.
Thank you again for your help.
Click to expand...
Click to collapse
Here is the correct firmware and download link for the S6 EDGE+ phone.
https://www.androidfilehost.com/?fid=24052804347822287
Good luck.
Sent from my SM-G928T using Tapatalk

Misterjunky said:
Here is the correct firmware and download link for the S6 EDGE+ phone.
==========================================================
Good luck.
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
Thank You! Now, if I do get my phone back up and running, how can I root it? I don't need any custom ROM or anything, I just want root permissions.

hereisalex said:
Thank You! Now, if I do get my phone back up and running, how can I root it? I don't need any custom ROM or anything, I just want root permissions.
Click to expand...
Click to collapse
Yes you can, follow the link below for full instructions .
http://forum.xda-developers.com/s6-edge-plus/development/arter97-kernel-galaxy-s6-edge-plus-t3189913
Good luck..
Sent from my SM-G928T using Tapatalk

It's still not working. It will boot up, play the T-Mobile jingle, and show me the lock screen, and then reboot after about half a second. This repeats indefinitely. Please help?

Verizon Note 4 Will not flash in Odin

Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it

pfcland said:
Alright i did a major mess up on my phone , Alright so i was rooted and was on CM13 well i decided to go back to stock rom so i downloaded the lastest Firmware and use odin to flash it and while it was flashing it failed . So i pulled the battery and restarted the phone and now i am hit with the ( Your device didn't update succesfully. Use the Verizon Software repair assistant to repair your deivce ) So i did that and it fails at 84% So i tryed reflashing again via odin and i keep getting failed well when i tryed flashing CF-Auto root to just see if it did anything it failed but when i booted the phone up it went stright to the samsung logo and boot looped so i was ok so i went into recovery and tryed to wipe /factory reset but keep getting a error .
So my thing is idk what to do i have tryed flashing via odin and it keeps failing i get this
Code:
<ID:0/007> 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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
and that is the lastest firmware from sam mobile
if anyone can help me i really appericate it
Click to expand...
Click to collapse
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?

SirLaughsalot said:
I don't know if you tried already, but perhaps you could simultaneously flash a PIT file (hsbadr has a post over this) and a stock firmware image in ODIN. This should fix any borked partitions, if there are any. If this doesn't work, then I'm afraid I can't help you further. You'd have to wait on someone more knowledgeable than me. Or, you can take it into a verizon store or best-buy and ask for help there?
Click to expand...
Click to collapse
Were can i find this post at

ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?

pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting

Bren123 said:
Is this on first boot go through set up and when your on the home screen power off the phone then power it on and if you were on cm 13 and flashed it with TWRP you tripped Knox so if powering off doesn't work then you can't get rid of it without rooting
Click to expand...
Click to collapse
Yea it shows it on first boot shows a lock that is unlocked

pfcland said:
Yea it shows it on first boot shows a lock that is unlocked
Click to expand...
Click to collapse
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk

Bren123 said:
OK complete setup when it gets off verizon screen then power it off and power it back on
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Ok it is gone thanks alot man

Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.

Bren123 said:
Download this app called Samsung phone info from Google play and look at Knox warranty void if it shows up with 0x1 your warranty is voided I'm not sure if there is a way to reset it back to 0x0.
Click to expand...
Click to collapse
it shows Ox1 but i am not worried about it because my phone is paid off

pfcland said:
it shows Ox1 but i am not worried about it because my phone is paid off
Click to expand...
Click to collapse
Oh OK cool.
Sent from my SM-N910V using Tapatalk
---------- Post added at 04:38 AM ---------- Previous post was at 04:37 AM ----------
pfcland said:
Ok it is gone thanks alot man
Click to expand...
Click to collapse
Your Welcome. [emoji3]
Sent from my SM-N910V using Tapatalk

pfcland said:
Alright that actually worked it flashed and did not fail , Thanks alot your a life saver now my second question is When i boot the Phone Up and it shows the picture Samsung Galaxy Note 4 Andriod how do i get the Custom part on it to go off with the lock ?
Click to expand...
Click to collapse
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<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> 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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!

droiddude414 said:
I'm at the exact point as he was but I haven't been able to try verizon software update assistant yet. However, I'm not able to install the PIT and TAR he used. Here's what I get. Any ideas? Under options I have the first three checked (auto reboot, re partition, f reset time).
<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> 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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<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> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
EDIT 1: Unchecked auto reboot and switched COM PORTS and it worked! THANK YOU!!!
Click to expand...
Click to collapse
Do this
Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
1. Extract odin into a desktop folder
2. Extract the tar from the zip and place it in the odin folder .
3. Place the PIT file inside the odin folder
4. Open odin folder
5. Run odin
6. In the left you should see some menues click on the one that says PIT
7. Now browse for thr PIT file and select it
8. Now Click on the AP button and select the TAR file in the odin folder .
9. Wait for it to load
10. Now make sure the re partition is not check marked .
11. Now click start and it should flash succesfully.
It will reboot and show the lock screen but one you reboot again it should be gone
Hope this helps

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
lugnuttz said:
Bren123 (or anyone who can help), I am having a same type of problem flashing in Odin. I would like to put my phone back to kitkat, back when it was smooth and fast. When I have tried to flash with Odin it failed everytime, however it was an older version of Odin v3.10.7. I have a stock kitkat rom from Sam mobile. Can I load it with the newer Odin and the Pit file you shared links for? Any help would be appreciated!
Click to expand...
Click to collapse
I tried again with the never version of odin and it still does not work for me. This is what I get:
<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> 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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help me get my phone back to kitkat???
I can only flash marshmallow, or now lollipop v5.11, after following the instructions above. I still can't get the kitkat firmware to work.
Please help!

Bren123 said:
ok first make sure you are using this odin https://www.androidfilehost.com/?fid=312968872162493207
Make sure you use this pit https://www.androidfilehost.com/?fid=95784891001613364
Then make sure you are using this tar https://www.androidfilehost.com/?fid=24411628330026105
Extract odin and put it any where then extract the tar from the zip and go to the odin I uploaded in the left theirs a tab labeled pit click that and click pit in that tab select the pit i gave you than go to AP and and go to where you extracted that tar and select it wait for it to check MD5 it may stop responding just wait than click start and wait for it to flash than you should be on stock unrooted lollipop
Click to expand...
Click to collapse
thank you, this helped me out when my odin got stuck for 30+ minutes.

I use to have a Note 4 Verizon good cell, but I then change it to a T-Mobile N910T unlock easer to flash them no boot-loaders are blocked, but thats just my saying.

I went through the process ... i have root and i can only install a 5.1.1 rom for the life of me i am unable to flash any 6 or 7 roms ... ideas?

Get write failure
I know this has been a couple years but I am in the same boat . I went through the steps and I get a flash write failure?
It happens after about 40 seconds into
system.img.ext4
ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> FAIL! (Write)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Need help un-bricking my kids tab 3 7.0 SM-T210R...

Hi guys, bit of a noob here...I messed up my kids tablet.
It was running NoleKat 2.X, previous to that was running stock 4.4.2.
In an effort to get tablet back to stock to clear up some bootloop issues - used odin to flash stock 4.1.2 it worked no problem except Samsung update to 4.4.2 would no longer work...
so I break out odin again and grab what I think is the right stock 4.4.2 Rom from sammobile....try to flash it, it fails and now tablet only boots straight into recovery <3e>.
I tried wipes from recovery they all fail due to some make_extf4fs failed on dev block.
adb sideload will crash when ROM transfer gets to about 70%.
tablet will not take any other ADB commands
Smart switch and Kies will not reconize tablet say its unsupported - works fine on another tablet.
I can get it into odin mode but odin will fail no matter what I try and flash...works fine to flash second tablet I have.
Any suggestions or do I need a new tablet.
Plaz

I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat

plazomat said:
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
Click to expand...
Click to collapse
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
So when I flash twrp 2.8.0 it , the progress bar goes all the way green then fails after a few seconds here is the oding log...
<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> 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> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help RealWelder...
Plaz

And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz

plazomat said:
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<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
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
Click to expand...
Click to collapse
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ

plazomat said:
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
Click to expand...
Click to collapse
Hi i have the same problem can u help me pls?

Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<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)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to samsung ( I think) recovery....
Plaz

plazomat said:
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<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)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to recovery....
Plaz
Click to expand...
Click to collapse
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz

plazomat said:
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
Click to expand...
Click to collapse
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thanks RealWelder you are awesome to still be supporting these old beaters - gonna try this in the morning when I get some time....
Plaz

Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz

plazomat said:
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
Click to expand...
Click to collapse
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.

gr8nole said:
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
Click to expand...
Click to collapse
Thanks gr8nole - tried flashing the 3.0.0 TWRP still no joy - keeps booting into stock (ithink) recovery. I pulled it from your file repo on Android file host.
I say I think cause the font is so big and the display is in landscape mode.
Plaz

RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Gave it a go with your ROM...still recovery boot loop as suggested by gr8nole.
Here is log..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> system.img
<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)
Thanks again
Plaz

Hi Gents, still messing with this when I have time and no joy...
Can't get a custom recovery to stick, odin flashes file but when device reboots just goes back to stock recovery...
Any clues.
Plaz