Develop Bugs

error when flashing ROM via Odin

hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

Mashari_F said:
hi, i'm trying flash a ROM to note 10.1 p605, it has Singapore ROM originally and im trying to flash German ROM
i get this error in Odin every time i try to flash:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P605XXUAMJ2_P605OJVAMI3_P605XXUAMJ1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
1) Have you tried to use an other usb port?
2) do you use the original usb cable?
3) do you have all the samsung drivers installed?
4) make eure that samsung kies is not running in the background
Hope it helps you
Gesendet von meinem SM-P600 mit Tapatalk

Got the same problem, so recovered it from kies
Skickat från min SM-P605 via Tapatalk

Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.

ronaldphl said:
Hi... Anybody have a solution for this problem? Have the tablet returned from a service and tried to flash the recovery but it just doesn't work.
THanks a lot for any help.
Click to expand...
Click to collapse
Is it giving you a FAIL after flashing , or doesn`t show up after a successful flash.
If it doesn`t show up after flashing , re-flash but untick "Auto-Reboot" within odin before flashing & restart manually after flashing.

I have a "Fail after flashing" - complete (Write) - operation failed in Odin

Which odin
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck

FSkyman said:
Hi,
When flashing with oder it depends on the package which oder will work.
At my p 605 the 1.86 version was working without probs.
The best is to use the Oden which is coming together the Roms Zipfile.
I hope this info helps please let me know.
Good luck
Click to expand...
Click to collapse
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well

Recovery Flashing
ronaldphl said:
I tried all the possible combination... different Odin... different cables and ports... it just didn't work.
Since I read from a old post that flashing a original rom thru Odin helps... and i tried... Odin works and the rom can be flashed without prompting the signature verification failed error.
I suspect if Samsung has done something to make the recovery image fails...
I tried flashing the recovery using the stock recovery too and it failed as well
Click to expand...
Click to collapse
Now I am confused are you talking about recovery or rom ?
The only recovery I could get to work was the TWRP - this Zip file comes with a Odin that works.
Cwm philz are not working.
But keep in mind as soon you installed twrp your knox counter is tripped.
For rom flashing you have to wipe your tablet and then follow these instructions xxxx://www.droidgator.com/update-galaxy-note-101-sm-p605-android-43-xxubmj9-firmware/.
Before starting backup your tab then everything should be fine.

Thanks for your effort in helping me out...
Before I sent my tablet for servicing... I restored the tablet with Kies to the original factory setting and rom as I HAD rooted my P605 and flashed a custom rom before. [Although the Know count is 0*1 anyway.... but the service centre was kind enough to fix my tablet as it's a hardware failure instead of anything to do with the ROM ]
When I got my tablet back and tried to flash the TWRP into it, this problem surfaced. And I read from another post that some say flashing a Samsung original rom could help I tried but to no avail. Still I am waiting and looking for a solution.
I tried Odin 3.04 3.07 and 1.85 with the two versions of TWRP but still none of them work.

Cant flash Stock firmmware
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?

nihalvm said:
Hi Guys
Tried all methods in the fourms but i am still not able to flash stock firmware from odin.
this is the error i get.
I am trying to update using Odin 3.09 as well as 3.07. but it is failing while writing system.
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> system.img.ext4
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? Is this because this shows Write Protection : Enable?
Click to expand...
Click to collapse
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3

aelaan said:
---
Might you recall what the firmware version was before you started to flash this one?
I am also trying to recover from NC3 back to MJ4XAC and it is not allowing me to finish, Kies also does not recover the tablet. It looks like one of the filesystems is in a different state. With TWRP there are options to perform CHMOD on the file systems but I figure I have been mocking around long enough and for some reason beyond my experience the system is not responding.
Can you still get into ADB mode? That might be an option to see if you can gain access?
Click to expand...
Click to collapse
Although it failed, I was able to recover using kies and use tablet as normal without data loss. It might be because at that point I had not rooted my tab and system state was still original in odin.
By the way I was on MJ4 xsa(AUSTRALIA) trying to install NC2 TGY(HONG KONG).
Now I have rooted it and have I installed NC2. I am still not sure what the issue was. But the only thing I did different was, first was using a virtual machine, but now did in an actual windows machine.
Can you please try this? If you can, install back NC2 using odin. Boot it once, then try recovering using kies. Kies recover mode gets your latest firmware based on your serial number. Not what firmware you are running.
Please post back the result. Interested to know the outcome.
Sent from my SM-P605 using XDA Premium 4 mobile app
---------- Post added at 08:38 AM ---------- Previous post was at 08:33 AM ----------
Khazaad said:
Is the sm-p605v (verizon) synonymous with sm-p605 for technical purposes? I am having identical problems with lt03ltevzw. Odin 3
Click to expand...
Click to collapse
I don't think it is. Although the specs are the same, read somewhere that the internal partition structure for carrier branded firmware are different to generic. Don't remember where I read that. But can't confirm that either.
Sent from my SM-P605 using XDA Premium 4 mobile app

[Q] Stock note 2 bootloop

Hi, so my cousin gave me her note 2 and told me to fix it! its basically on a bootloop so first thing i thought of was to flash stock firmware,
So i did that and the Samsung logo just flashes for eternity :| she hasn't done anything like rooting etc.
So i downloaded the UK stock firmware(her note 2 is the THR) but it's still in bootloop!
I can't get into recovery to wipe data! when i hold the key combos, it just keeps rebooting (samsung note II - n7100 black and white one)
(I actually needed help flashing the rom but not its fixed i need help with this and i didn't want to make another thread)
should i try to use put and re-partition?!

kamranhaghighi said:
Hi, so my cousin gave me her note 2 and told me to fix it! its basically on a boot loop so first thing i thought of was to flash stock firmware
so i downloaded the UK firmware (although i have no idea what country it is, but it doesn't make difference right?!)
and it gave me this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ1_N7100OXXALJ1_N7100XXALIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Added!!
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> system.img
<ID:0/009> NAND Write Start!!
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should i do ?
i have windows 8 and odin 3.09
Edit: I got the firmware from here :
http://www.cnet.com/how-to/how-to-restore-a-galaxy-note-2-from-rooted-to-factory-settings/
My country's firmware is not available anywhere
Click to expand...
Click to collapse
Hello ,
many months ago I had a problem to install a Samsung rom. For me the solution was :
Download firmware from sammobile
Use Odin PC 3.07 (It doesn't work with 3.09 version I don't know why )
I hope that can help you.

gb61 said:
Hello ,
many months ago I had a problem to install a Samsung rom. For me the solution was :
Download firmware from sammobile
Use Odin PC 3.07 (It doesn't work with 3.09 version I don't know why )
I hope that can help you.
Click to expand...
Click to collapse
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ1_N7100OXXALJ1_N7100XXALIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> system.img
<ID:0/009> NAND Write Start!!
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
it might be because i'm using UK firmware.
Iran's firmware isn't available!
(i used 3.04 but its old anyway !)
I'm driven crazy i will just wait for an answer :|

kamranhaghighi said:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXALJ1_N7100OXXALJ1_N7100XXALIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> system.img
<ID:0/009> NAND Write Start!!
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> cache.img
<ID:0/009> hidden.img
<ID:0/009> modem.bin
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<ID:0/009> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
it might be because i'm using UK firmware.
Iran's firmware isn't available!
(i used 3.04 but its old anyway !)
I'm driven crazy i will just wait for an answer :|
Click to expand...
Click to collapse
It should be good to try with Odin more recent if you can.
Iran firmware on the image .

How did you find it i saw that website too but i couldn't find the firmware!
I will try odin 3.07 and post results

gb61 said:
It should be good to try with Odin more recent if you can.
Iran firmware on the image .
Click to expand...
Click to collapse
YEAH! it worked ! thanks so much but i'm afraid it will not work, im still on samsung lighting up and down but i only waited like 1min, it had this problem expect it would not boot at all!
EDIT: ok flashing stock didn't help. i still got bootloop, any idea how to fix this?!
i also can't get into recovery, it only gives me a red led when i hold volUp+Home+power!
i did a few things now i can't even flash the old one with 3.0.7, gives the same error it did on 3.09 , i give uP! somebody help me :|

gb61 said:
It should be good to try with Odin more recent if you can.
Iran firmware on the image .
Click to expand...
Click to collapse
flashing the one i got from sammobile gives me this:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMC3_N7100OJVDMC1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> sboot.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
edit: sounds like it is because its an old firmware!
now i can't even flash the UK with 3.07!

should i make a new thread for my bootloop? (i still got bootloop after going stock)

kamranhaghighi said:
should i make a new thread for my bootloop? (i still got bootloop after going stock)
Click to expand...
Click to collapse
Hello,
have you try to install a custom rom ?

gb61 said:
Hello,
have you try to install a custom rom ?
Click to expand...
Click to collapse
No!

kamranhaghighi said:
No!
Click to expand...
Click to collapse
Have you see in the link in the edit of my last post ?
At this moment you can't acces to recovery ?

gb61 said:
Have you see in the link in the edit of my last post ?
At this moment you can't acces to recovery ?
Click to expand...
Click to collapse
I just saw it now, and no i can't get into recovery, i will read the link you gave me tomorrow, im super tired today! and also have an exam

my guess is the eMMC chip has failed, or the partition is corrupted. Yoiu might try and flash the PIT but i suspect that wont work. This type of failure is unfortunately quite common from my experience. My Note 2 had the same problem and still cant find a fix.

grwalker said:
my guess is the eMMC chip has failed, or the partition is corrupted. Yoiu might try and flash the PIT but i suspect that wont work. This type of failure is unfortunately quite common from my experience. My Note 2 had the same problem and still cant find a fix.
Click to expand...
Click to collapse
sorry for your note 2!
hope its no longer like that in note 3 and 4 :! (i got the note 4!)

kamranhaghighi said:
sorry for your note 2!
hope its no longer like that in note 3 and 4 :! (i got the note 4!)
Click to expand...
Click to collapse
Hello,
try that :
Install a recovery with Odin PC
download original CWM note 2 :https://mega.co.nz/#!rY1DmZ7J!JzeUWnC-X1_0jO42aoydRAYakgPQMo9RgHqAHyRGWyI
download TWRP : https://mega.co.nz/#!jNdQwaib!BdXte5RXjPVg7YLVjHS6WjbMZzfS-DJk6IPW6jPvyWs
Download a custom rom for Note 2 :
copy and paste CWM ,TWRP and custom rom on your SdCard
Install CWM with Odin PC , if doesn't work try with TWRP.
If it works , install the rom with recovery
I hope that will help you.

gb61 said:
Hello,
try that :
Install a recovery with Odin PC
download original CWM note 2 :https://mega.co.nz/#!rY1DmZ7J!JzeUWnC-X1_0jO42aoydRAYakgPQMo9RgHqAHyRGWyI
download TWRP : https://mega.co.nz/#!jNdQwaib!BdXte5RXjPVg7YLVjHS6WjbMZzfS-DJk6IPW6jPvyWs
Download a custom rom for Note 2 :
copy and paste CWM ,TWRP and custom rom on your SdCard
Install CWM with Odin PC , if doesn't work try with TWRP.
If it works , install the rom with recovery
I hope that will help you.
Click to expand...
Click to collapse
i'm also going to check re-partition and use pit file. is that a good idea?

i can't get into twrp, cwm either, it just reboots from white n7100 logo and it tries too boot os the next time!

kamranhaghighi said:
i can't get into twrp, cwm either, it just reboots from white n7100 logo and it tries too boot os the next time!
Click to expand...
Click to collapse
Have you follow this steps ?
How to Install ClockworkMod Recovery 6.0.4.4 on Galaxy Note 2 N7100
Download Odin v3.09.
Extract Odin zip file and you will get Odin3 v3.09.exe along with few other files.
Power off your Android device. Wait 5-6 seconds for vibration to confirm complete switch off.
Now, put the Galaxy Note 2 N7100 in Download Mode by pressing and holding down the Volume Down, Home and the Power button together. A warning screen will come up; press Volume Up button to enter Download Mode.
Now run Odin3 v3.09.exe (see Step 3) as an Administrator because Admin privileges is required to complete the process smoothly (only applicable Windows Vista and higher).
Now connect your device to your PC using USB cable. An “Added!!” massage will appear in Odin’s message box. If you don’t get the same then you should try another USB port (try USB port located in back in your desktop PC). If that too don’t work then you should reinstall the driver. If you successfully see the “Added!!” message in Odin then you are ready to go in next step. You should also see COM port with a number in Yellow if you successfully added your device.
Click the AP Button, and select that .tar.md5 file that you downloaded earlier. If you are using old Odin then add the file to PDA button.
In Odin window, make sure only Auto Reboot and F. Reset Time checkboxes are selected.
Double check everything that we mentioned in Step 7 & Step 8 above. Now, once satisfied hit the START button to begin the flashing process.
Once flashing completed, your Galaxy Note 2 N7100 will restart and soon you will see a PASS message with green background in the left-most box at the very top of the Odin. You can now unplug the USB cable to disconnect your device from computer.

kamranhaghighi said:
i can't get into twrp, cwm either, it just reboots from white n7100 logo and it tries too boot os the next time!
Click to expand...
Click to collapse
Ok,
we try to install a full wipe rom :
Download this zip : https://mega.co.nz/#!KN1QiZyJ!tKkqdUSYOtuLI4_4TRe8ZpXsHb3G608KsJd5XNf6EhU
Extract the files = 4 .tar and 1 .pit
Put this file in odin like in the picture = FLASH WITH PIT (RE-PARTITION)

gb61 said:
Ok,
we try to install a full wipe rom :
Download this zip : https://mega.co.nz/#!KN1QiZyJ!tKkqdUSYOtuLI4_4TRe8ZpXsHb3G608KsJd5XNf6EhU
Extract the files = 4 .tar and 1 .pit
Put this file in odin like in the picture = FLASH WITH PIT (RE-PARTITION)
Click to expand...
Click to collapse
ok thanks! btw in the process of doing this i gave myself a nice electric shock 0_0 it came from 2 connectors from back of the device ! i got pass anyway
edit: it will take an hour~ i will post results when its done!

Soft Bricked, No recovery Galaxy Pro 8.4

Hello guys.
Im new to this forum and I have to say it is amazing but, unfortunately, nothing available could helped me.
My Galaxy Tab Pro 8.4, I believe, is soft bricked, I cant access recovery mode. I have tried flashing Stock ROM, TWRP (again), CWM, CF_Autoroot. I even opened the tablet and removed the battery but it still didnt work.
I had CM12 installed and it prompted me to install a nightly, so I did. After the process was done and the tablet booted I kept getting the error and pop up saying "Unfortunately, Google Play services has stopped working."
So, I tried to install Gapps again but it just made it worst this time. So, I tried backing up (I believe I didnt wipe or whatever is called before backing up) and after this my tablet wont work.
The tablet turns on only when plugged in. I can only see three different screens - battery with loading unanimated loading icon, splash screen, and I can enter download mode. I tried to use Kies but that didnt work.
I read on one forum that maybe it could that the NAND rw was corrupted but I do not know how to fix it. Also, something about the kernel, but I do not want to mess anymore without somebody's expertise.
I have looked everywhere but I couldnt find anything, so I decided to post and see if anyone would help me. Thanks in advanced.

Still...
Jessooca said:
Boot into download mode.
download Odin here: ...
download your latest stock rom. here ...
Use Odin to Flash the stock tar or md5 {whichever it is} in Odin flash it in the PDA slot, don't check anything just put the stock tar or md5 in that slot it should do it's thing. wait for it to check the file and flash away.
Let me know what happens
-- if it bootloops after you've flashed it, just boot into stock recovery and do a factory reset. Then reboot and it should boot back up good as new.
*On a side note, some people forget to extract the md5 file from the file they download so if Odin doesn't find your stock rom you downloaded, make sure the md5 doesn't need extracted.
Since you've got Download mode, we can get you back up and running.
Click to expand...
Click to collapse
Hello, I want to thank you for taking your time and helping me but unfortunately it still dont work. After it is done flashing successfully, the tablet auto reboots and stays stuck in the splash screen until I unplug it or enter download mode again. I cannot enter custom nor stock recovery mode. If I hold the necessary keys to enter recovery mode it only shows the splash screen, if I keep holding the keys down it turns off an immediately turns on into the splash screen.
Thanks for your help, though.
Below is the Odin message (though I do not think you need it):
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T320UEU1ANK1_T320XAR1ANK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Thanks!
Jessooca said:
Give me just a few minutes and i'll tell you what to do next, you're almost there!
Click to expand...
Click to collapse
Ok, I will. Again, I really want to thank you for helping me, and even if we cant fix it I will be very grateful.

Thanks Jessooca, fixed my Galaxy tab 2 pro
Jessooca said:
Boot into download mode.
download Odin here: http://androidhost.org/get/PVAIv
download your latest stock rom. here: http://www.mediafire.com/download/ul9d01zlrq3dl72/T320UEU1ANK1_T320XAR1ANK1_HOME.tar.md5l
Use Odin to Flash the stock tar or md5 {whichever it is} in Odin flash it in the PDA slot, don't check anything just put the stock tar or md5 in that slot it should do it's thing. wait for it to check the file and flash away.
Let me know what happens
-- if it bootloops after you've flashed it, just boot into stock recovery and do a factory reset. Then reboot and it should boot back up good as new.
*On a side note, some people forget to extract the md5 file from the file they download so if Odin doesn't find your stock rom you downloaded, make sure the md5 doesn't need extracted.
Since you've got Download mode, we can get you back up and running.
Click to expand...
Click to collapse

Yes I do, but your suggestion fixed my issue and felt you deserved the credit.

[SOLVED] ODIN Flash failed (for downgrade, custom-to-stock, etc)

Hey there awesome people!
I have been weeping over my N3N refusing to accept Stock firmware I was downloading.
I followed these steps to flash the stock firmware I would download:
Flashing STOCK firmware (via ODIN):
Put phone off / battery pull
Download ODIN (this one or whichever is newest at the time you read this)
Open up ODIN (as Administrator on Windows PC)
Press and HOLD DOWN the Volume Down [AND] the Home buttons. THEN Press the POWER button. On the screen it will show, press Volume UP to go to DOWNLOAD mode
Plug your phone into the PC and ODIN will show you (in the log) that a device has been Added!
Click the AP button and navigate to your downloaded firmware.
Let ODIN finish the MD5 check and then press START to start flashing
So, at this point, your ODIN will either be showing PASS or FAIL.
If it shows PASS, you're good to go. Skip to Installing a recovery.
If it shows FAIL, read the Log (displayed in the program's left hand side) and observe this:
Code:
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Before showing FAIL!, the last thing it should've listed should be hidden.img
If yours didn't show this, it probably didn't flash the phone upto this point. What we want is for the boot.img, recovery.img, system.img, modem.bin and cache.img to have been flashed to the phone.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Fear not It still worked!
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Installing a custom recovery:
Download a recovery (I use TWRP Materialized )
Unzip it and re-open your ODIN (if your ODIN was still open, hit the RESET button)
Do a battery pull on the phone, and boot into DOWNLOAD mode again.
Connect the phone to the PC. ODIN should show in the Log that a device has been added.
Click AP button and navigate to where your Custom recovery is.
After ODIN finishes MD5 check, hit START and let the Custom recovery be flashed.
After this is done, boot into recovery by holding down the Volume Up [AND] Home buttons then pressing Power button.
Go into recovery and wipe Data, Cache and Dalvik (factory reset) and reboot the phone.
BOOM! You'll see the Samsung logo doing its thing and we'll be good to go!
Leave a thanks if this helps :highfive:
Shoutout to @rihawi who pointed this trick out in this post!

boydee said:
What we do now is just flash a recovery to the phone (we will be replacing the stock recovery that stock ROM comes with), (or root it) and we'll be good to go.
Click to expand...
Click to collapse
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?

mcpossity said:
Okay. I had the Odin Fail because I was trying to downgrade to a firmware with earlier bootloader and as you described I installed TWRP. But now I still get the same error in Odin when trying to install this firmware even with TWRP in place... What should I do?
Click to expand...
Click to collapse
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)

boydee said:
List for the steps you're taking to install. I fear that we might have gotten lost somewhere along the way.
The idea is to FIRST install the firmware, THEN install TWRP, then reboot (TWRP should be the last thing you install.)
Click to expand...
Click to collapse
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
When it shows FAIL!, it means that the bootloader it is trying to flash is older than what the phone already has. You will probably find that you are stuck here when you're coming from LL to KK or JB, or from a newer KK to an older one.
Click to expand...
Click to collapse
This is where I'm at right now.

mcpossity said:
Your post title says "for downgrade". So I have a firmware with, let's say, bootloader binary version 3 installed. I want to downgrade to an older firmware which has bootloader binary version 2. I can't just flash the older firmware, because Odin fails. So I was following your guide to install TWRP to somehow downgrade through that, but it doesn't work.
This is where I'm at right now.
Click to expand...
Click to collapse
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:

odin fail
xda-developers LOGIN REGISTER search plus
Join the Experts
Post Preview:
i used odin3 v3.12.7
this is what appears on the log tab.
Added
Odin engine v(ID:3.1207)
File analysis
setupconnection
initialization
get pit for mapping
firmware update start
NAND write start
Singledownload
sboot.bin
cm.bin
Fail
Complete(write) operation failed
all threats completed. (success 0/ failed 1)
how can i fix this. please help..
please send me message @
[email protected]
facebook- fed refalbor
please. i badly need your help. i am using samsung j7 2016 (j710gn)

Fai always on installing at same way you said
Dear xdas .. I trying the same to download the firmware for the Gt-N5100 at the same steps you explain before but always failed , note that I try that to try resolve the wifi problem after last update, so cannot install firmware and that is the result of ODIN, please let me know if any result here:<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..
<ID:0/005> Odin engine v(ID:3.1207)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

not helpful. you only flashed the recovery and not the whole system file. flashing the system file will took you a minute while the error on takes less than a second.

After i do the odin recovery it showed PASS . but after that phone tried to restart and the samsung logo came on thrice flashing and gone OFF . Now the phone is in dead mode. Please help me to help to resolve this. My phone is samsung note 2(GT7105)

hi, if i flash firmware via odin, programs and files on internal memory will erase or not? thanks

Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??

Cyclone53 said:
Hi, i was flashing an older version of android to my Samsung Galaxy S7 Edge, using odin, i entered all the files in Odin and it was working fine up until it was almost finished and i accidentally bumped my phone and Odin displayed a FAIL immediately... lol wow i am such a idiot. I disconnected, reconnected, tried to re-run Odin again, it told me it failed right away so theres no fixing it with Odin anymore. I tried restarting phone, i somehow got it to restart but it doesnt show samsung logo or anyting, i just see a Recovery Booting... in the top left corner of screen in tiny letters... i can get it into download mode but nothing else. I dont know what to do, somebody help me out here. How do i fix this??
Click to expand...
Click to collapse
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...

Secure boot fail
Im getting a secure boot fail after update. Ive tr8ed just AP and odin says boot fail. Phone says secure boot fail. And ive tried all ap,bl,csc,cp and i get from odin re partition fail and again on phone secure boot fail. Is there a way to maybe bypass secure boot. Oem is not optional and it will fail trying the combo rom for factory binary as well. Before the update i was ablento flash everything basically regardless of csc and verison.

Hello,
I downgrade and i tried many stock ROMs (marshmallow and lollipop) and checke all youtube videos, nothing is working. I always i got error. So i want to ask if with your instructions you managed to install stock marshmallow ROM from stock nougat on A510F just because you additionally chose "Re-Partition" and "Phone Bootloader Update" ?
Thanks.
zool_80 said:
Hello, I got a very similar issue on my phone. I spent more than a week trying to find a solution and everytime I got a FAIL. This morning I got a PASS! here is what I did:
_ Use odin v3.12.7 with administrator priviledges.
_ In options I checked: Autoreboot, Re-Partition, F.Reset Time and Phone Bootloader Update.
_ I loaded BL, AP, CP and CSC Files (it was CSC and not Home_CSC).
_ I started the phone in transfert mode (home, volume down and start button). And then press volume up to activate the transfer mode.
_ I connected the phone to the computer and the Phone appeared in ID:COM.
_ I pressed "Start".
And this time the transfer did not fail. It took several minutes and then the phone rebooted and I got the welcome screen as good as new.
I don't know if it worked because I selected "Re-partition" and "phone bootloader update" this time or if it's because I downloaded the lastest stock rom from samsung I was able to find at present (maybe both). But I am so happy now.
Good luck to you and BE CAREFUL because Re-Partition and updating the bootloader could definitely brick your phone...
Click to expand...
Click to collapse

boydee said:
That's okay! it's perfectly fine for it to FAIL!
Flash it again and copy/paste the ODIN Log here for me to see and advise on what you should do next.
Cheers! :highfive:
Click to expand...
Click to collapse
hello guys, sorry, i'm new here.. i've just faced the problem with my phone.. idk why my phone was stuck, i've tried to remove the battery and tried to restart, it seemed the same, just stuck on samsung logo. i tried to enter to recovery mode, it failed. i've tried to install the original stockrom and it's failed..
here the problem and condition:
1. stuck on samsung logo
2. can't enter recovery mode
3. only download mode can be use
i've tried the stockrom but in odin said...:
<ID:0/021> 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/021> Odin engine v(ID:3.1101)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> SingleDownload.
<ID:0/021> spl.img
<ID:0/021> NAND Write Start!!
<ID:0/021> sboot.bin
<ID:0/021> sboot2.bin
<ID:0/021> param.lfs
<ID:0/021> boot.img
<ID:0/021> recovery.img
<ID:0/021> system.img
<ID:0/021> cache.img
<ID:0/021> hidden.img
<ID:0/021> SPRDCP.img
<ID:0/021> FAIL!
<ID:0/021>
<ID:0/021> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what should I do?
need help, please.. thanks

a few days ago my Samsung bootloop, I found a solution. Download the latest firmware for your Samsung, which is suitable for your country. enter download mode, just flash AP, later he will install and reboot. when rebooted later if it isn't mistaken it appears no modem / radio (I forgot). enter download mode again, flash CP only. then device will reboot and enter recovery default. in recovery select wipe factory. and my samsung will reset again. I hope this helps you.

hi my problem is this
<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/008> Added!!
<ID:0/008> Odin engine v(ID:3.1401)..
<ID:0/008> File analysis..
<ID:0/008> Total Binary size: 952 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> spl.img
<ID:0/008> sboot.bin
<ID:0/008> sboot2.bin
<ID:0/008> param.lfs
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i cant flash stock firmware for my samsung galaxy core prime, smg360hu but it stucks at system.img then fails always. help me please

Hi,
Just decided to use Odin v3.14 to update my Australian spare Samsung SM-G900iwith Indian G900IDDS1CSA1 firmware as it was a later build, seemed to proceed OK but finished with <OSM> All threads completed. (succeed 1 / failed 1.
It had previously been updated to G900IDVU1CQJ2_G900ITEL1CQJ2_G900IDVU1CQJ2_HOME.tar.md5 which was working perfectly.
<ID:0/003> Added!!
<ID:1/004> 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.1401)..
<ID:1/004> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:1/004> File analysis..
<ID:0/003> Total Binary size: 2496 M
<ID:1/004> Total Binary size: 2496 M
<ID:1/004> SetupConnection..
<ID:0/003> SetupConnection..
<ID:1/004> Initialzation..
<ID:1/004> Get PIT for mapping..
<ID:1/004> Firmware update start..
<ID:1/004> NAND Write Start!!
<ID:1/004> SingleDownload.
<ID:1/004> aboot.mbn
<ID:1/004> sbl1.mbn
<ID:1/004> rpm.mbn
<ID:1/004> tz.mbn
<ID:1/004> sdi.mbn
<ID:1/004> NON-HLOS.bin
<ID:1/004> boot.img
<ID:1/004> recovery.img
<ID:1/004> system.img.ext4
<ID:1/004> cache.img.ext4
<ID:1/004> hidden.img.ext4
<ID:1/004> modem.bin
<ID:0/003> Complete(Write) operation failed.
<ID:1/004> RQT_CLOSE !!
<ID:1/004> RES OK !!
<ID:1/004> Removed!!
<ID:1/004> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
Click to expand...
Click to collapse
Can I retain the updated build and just use ODIN to replace what failed?
Any suggestions GREATLY APPRECIATED.
Cheerz

Hello, there is 'firmware upgrade encountered an issue' thing on my samsung. I plugged to pc and pc sees the device but odin stuck at initialzation or fail. Any suggestion?

G Morn Folks I m stuck in the same situation thought different phone mode. this is M205F. Odine FAILS @ Recovery.img
Background
Latest Stock ROM of Samsung Maisk Rooted nd TWRPed. Wanted to downgrade to ANdroid 9 from 10 after realizing severe restrictions of the latter.
Odin 14x ( wtith Chinese verbiage @ start up screen ) used and used 2 Versions of stock ROMs.
Tried AP solo & AP + HOME_CSC COmbos
Both FAIL and leave me with ocean blue screen message "an error has occured while updating the deivce software..Use he emergency recovery function in the smart switch sw." and smart switch isnt recognizing my mob either.
Where do I go from here ?

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