Develop Bugs

Samsung Calaxy Pocket Odin Problem

Hi guys..I am new here and i enter in this forum beacuse of a problem...my Phone is Samsung Galaxy Pocket...i root my phone and add a custom ROM called JellyblastV3..any way after lots of upadates for the ROM i saw that with the last update i wasnt able to enter my setting in the phone i decide to install jellyblast again...my phone stuck on boot screen in the logo on starup...i enter odin mode and from the PC and i had this dialog with the problem FAIL!....
<ID:0/065> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5300XXMD1_S5300OXXMD1_RST_S5300XXMD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/065> Odin v.3 engine (ID:65)..
<ID:0/065> File analysis..
<ID:0/065> SetupConnection..
<ID:0/065> Initialzation..
<ID:0/065> Get PIT for mapping..
<ID:0/065> Firmware update start..
<ID:0/065> Sbl.bin
<ID:0/065> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also try splitfus2...also when i wait lots of time 20-30 mins i turn the phone in the side and i can see the home screen but i cant sellect because the bootscreen logo is on my way i try wipe cache the data but nothing...i cant reinstall the jellyblast because because the phone dont 'see' the external sd...and 1 more detail..the last time my phone worked i try to unrooted with a zip file called unroot if this matters....i dont know what else to do..plz help....
P.S Sorry for my english...

I guess you soft bricked your phone. try flashing back to stock ROM.:good:

Pranjal.raze said:
I guess you soft bricked your phone. try flashing back to stock ROM.:good:
Click to expand...
Click to collapse
well...idk if i am soft bricked but i dont know if i am able to flash my stock ROM...i try many things...and i am still briked

Samsung tab 3 lite SM-T110 bootlooping and nothing helps so far

My SM-T110 is stuck in bootloop. I can use download mode and not recovery.
I have tried so far:
1) Start in recovery mode by pressing vol up, home and power buttons at once.. i get a dead android logo and "NO COMMAND"
2) Flash new firmware by downloading stock software and using ODIN for flashing. It fails.
3) Install TWRP and CWM - again both fail with ODIN.
I tried 3 different cables with odin but get same result.
I googled for days and had no luck so i hope you can help me.

ccsrichman said:
My SM-T110 is stuck in bootloop. I can use download mode and not recovery.
I have tried so far:
1) Start in recovery mode by pressing vol up, home and power buttons at once.. i get a dead android logo and "NO COMMAND"
2) Flash new firmware by downloading stock software and using ODIN for flashing. It fails.
3) Install TWRP and CWM - again both fail with ODIN.
I tried 3 different cables with odin but get same result.
I googled for days and had no luck so i hope you can help me.
Click to expand...
Click to collapse
what version of Odin are you using?
Give THIS version a try.
If it fails, post a screenshot of Odin.

I tried 3.09, 1.something and now yours 3.07.. still no luck. I cant upload a screenshot because im a new user. but thats what it says with 3.07
I have auto reboot and f reset time on. nothing else and i chose PDA which is for my region and for sm-t100
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110XXUANI9_T110SEBANH2_T110XXUANI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> timh.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> obm.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

ccsrichman said:
I tried 3.09, 1.something and now yours 3.07.. still no luck. I cant upload a screenshot because im a new user. but thats what it says with 3.07
I have auto reboot and f reset time on. nothing else and i chose PDA which is for my region and for sm-t100
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T110XXUANI9_T110SEBANH2_T110XXUANI9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> timh.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> obm.bin
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've seen other people have success by trying different cables or sometimes even other computers. Other than that, I have no other ideas.

Anybody else has any ideas ?

gr8nole said:
I've seen other people have success by trying different cables or sometimes even other computers. Other than that, I have no other ideas.
Click to expand...
Click to collapse
BTW Odin is written in white in download mode not red as others have.. and when i try to use odin the upper left corner goes paritially black.. like theres a black box covering half of the text there

ccsrichman said:
BTW Odin is written in white in download mode not red as others have.. and when i try to use odin the upper left corner goes paritially black.. like theres a black box covering half of the text there
Click to expand...
Click to collapse
And the text there is:
ODIN MODE
PRODUCT NAME: SM-T110
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
nothing else

Also a newbie with the Tab TM-110
Hi there
Since we are not many here with our device i thought i should send you a message.
Unfortunately i do not have a solution for your problem but maybe it helps if you take a look at what i experienced so far.
I hope you can find my Thread by my profile.
Have you tried to use a different PC yet for flashing with Odin? Would be interesting to know if it helped.
So. Don`t give up. There will be a solution. :good:
Naturestone

I'm having the same issue, anyone can help?

same error GT-I8200 2ND partition error

Samsung Galaxy Note II stuck in the black screen

Dear all,
Thanks in advance. My friend have a Galaxy Note II, which stuck at the black screen with the word "Samsung GALAXY Note II GT-N7100". I try to go into recovery mode (Up, home and power button), it able to go inside with an android logo, but without selections for reset or recovery.
I then try to go into Download Mode (Down, Home and Power button), it seems able to go inside the mode with all the product name etc listed inside. While searching for the solution, i tried these:
http://forum.xda-developers.com/showthread.php?t=1896696
I try the first part which is flash a stock rom... but from the Odin interface, it stated there is no pit partition. I then turn off the phone and redo the procedure. When i try to start download the rom, this time it stated complete (write) operation failed.
I am not really familiar with these flash and odin and etc, just try my luck... but it seems no luck. Can anyone give me some advise on how to fix this? Thanks...
If further details is needed, just let me know, cause i am not sure what should information i should provide.
Thanks again....
** By the way, i realize that when ever i try to switch off the phone, it will automatically switched on but still stuck at the welcoming screen... it wont let me switch off.. **

xiaoyaotaigong said:
Dear all,
Thanks in advance. My friend have a Galaxy Note II, which stuck at the black screen with the word "Samsung GALAXY Note II GT-N7100". I try to go into recovery mode (Up, home and power button), it able to go inside with an android logo, but without selections for reset or recovery.
I then try to go into Download Mode (Down, Home and Power button), it seems able to go inside the mode with all the product name etc listed inside. While searching for the solution, i tried these:
http://forum.xda-developers.com/showthread.php?t=1896696
I try the first part which is flash a stock rom... but from the Odin interface, it stated there is no pit partition. I then turn off the phone and redo the procedure. When i try to start download the rom, this time it stated complete (write) operation failed.
I am not really familiar with these flash and odin and etc, just try my luck... but it seems no luck. Can anyone give me some advise on how to fix this? Thanks...
If further details is needed, just let me know, cause i am not sure what should information i should provide.
Thanks again....
** By the way, i realize that when ever i try to switch off the phone, it will automatically switched on but still stuck at the welcoming screen... it wont let me switch off.. **
Click to expand...
Click to collapse
post a picture of your download mode.. does it say model number is n7100?

It does shows N7100. Is there anything i can do to save this note II?
I can't find a way to upload a photo here...
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: Yes (4 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNDX WARANTY VOID: 1
AP SWREV: A2

I suggest downloading the stock firmware from here: http://www.sammobile.com/firmwares/database/GT-N7100/
Flash the firmware using Odin: http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969

audit13 said:
I suggest downloading the stock firmware from here: http://www.sammobile.com/firmwares/database/GT-N7100/
Flash the firmware using Odin: http://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
Click to expand...
Click to collapse
Hello, i downloaded from the sammobile and flash the firmware using Odin 3.04. The first time, it come out an info as below:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMF2_N7100OLBDMD2_N7100DXDMF1_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>
<ID:0/003> There is no PIT partition.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Next, i click START again, this time with the info below:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMF2_N7100OLBDMD2_N7100DXDMF1_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
May i know what should i do now to further troubleshoot this issue?
Thanks in advance

Samsung Galaxy Note 2 N7100

Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!

alex2003881 said:
Hello,
First, my note 2 stuck at boot logo.
When i try to enter recovery stuck about 15 seconds on logo after that says with red failed to mount /efs (no such file or directory) ; failed to mount /system (no such file or directory); failed to mount /cache (no such file or directory) ; failed to mount /cacahe/recovery/last_recovery (no such file or directory) ; failed to mount /data (no such file or directory).
I read that it would be something about a "rescue fireware" was a topic on the XDA forum but no link was not working.
Please help me fast!
Thx!
Click to expand...
Click to collapse
Same happened to my phone too and no luck. still stuck! Someone help please!

If you can boot into Odin mode, flash a stock rom from sammobile.com.

audit13 said:
If you can boot into Odin mode, flash a stock rom from sammobile.com.
Click to expand...
Click to collapse
I tryed this no result

What happened when you used Odin? Post the Odin log?

audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
Nand write fail. Or Sometimes, complete write operation failed!

audit13 said:
What happened when you used Odin? Post the Odin log?
Click to expand...
Click to collapse
When i try to put rescue firware with odin says setup connection after that fail.
Tomorrow i'm going to samsung official service.
I'll comeback with edit!

karanvirkohli said:
Nand write fail. Or Sometimes, complete write operation failed!
Click to expand...
Click to collapse
What does the log actually say? It probably failed when trying to flash a certain file.
Did you try different USB cables and USB ports?

Flash repair firmware
4 file
Sent from my GT-N7100 using Tapatalk

Hey, sorry for hijacking your thread.
I have the same problem. I tried many different scenarios and I couldn't fix it. I gave up and went to Samsung and after 48hs I called finding out that they refused to fix it. Talked to the IT guy and he said he has no idea how to fix it and told me the only fix is to change the whole motherboard and he said its not suggested to do so as its expensive. I have no idea what I should do. I flashed custom recovery, stock recovery. Tried to separate the whole firmware and flash it piece by piece using the skipsoft tool. I tried flashing PIT files with custom recovery, stock recovery, stock rom I have tried multiple PIT files from multiple websites.
This happens when I try flashing stock rom downloaded by samfirm or sammobile.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
If I to flash a PIT file using any of the scenarios mentioned above I get this ( the 4 files repair rom in this example )
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_XEF_N7100OXADLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
It will keep doing this forever until I unplug the cable. I'm running stock Kitkat 4.4.2 but all methods I find are for older versions with different bootloaders yet I still tried them as there are no recent fix from what I can find.

In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?

audit13 said:
In the first situation, the sboot.bin causes an error because the bootloader in the ROM is older than the phone's current bootloader.
Did you try flashing the latest stock ROM from sammobile.com using Odin 3.07 in the PDA slot? Sammobile.com ROMs should only be unzipped once to yield a tar.md5 file and flashed in the PDA slot.
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Yes I did all that. Same error. If I extract the tar file and do another odin flashable tar using skipsoft tool it doesnt work, removing one file at a time didnt work either. I tried the latest on sammobile, the latest on sammobile for my country, and the latest from Samfirm for my country. I also tried using SmartSwitch and Kies recovery using the serial number and model number and they don't recognise the phone during downloading like about 60% of downloading it will show an error that it doesnt recognise it.

When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?

audit13 said:
When flashing the sammobile.com tar.md5 file in Odin's PDA/AP slot, do you receive an error message? If yes, what is the error?
Click to expand...
Click to collapse
Same exact error of post #10
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNL1_N7100OJVFOD1_N7100XXUFOA1_HOME.tar.md 5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)

The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?

audit13 said:
The ROM being flashed has a bootloader that is too old or the ROM is not meant for the phone.
The model # for the phone has been confirmed as being a gt-n7100 on the Odin screen?
Click to expand...
Click to collapse
Odin screen that is in download mode ? Yes it says GT-N7100.

You're using the latest ROM for the phone? Which country?

audit13 said:
You're using the latest ROM for the phone? Which country?
Click to expand...
Click to collapse
Yes. Egypt. I have used both latest on sammobile and download by using samfirm. I have tried both of them. I have tried indian and few other countries all lead to the same error.

Are you using the original Samsung cable?

audit13 said:
Are you using the original Samsung cable?
Click to expand...
Click to collapse
It is not the one that came with the phone but it is one that I bought from Samsung. I also tried few other cables that came with LG and Asus phones.

[Expert Help Needed] Unwritable T210 after Odin installation

Hello there,
I have a problem with my T210 that I'm unable to fix. I've tried them all but it did not change at all.
So, starting things off, the problem started after flashing T210XXBOA3 using Odin. I've booted and did the setup process, all working fine till there. Then back to Odin I've flashed t210-TWRP 3.0.0. After that, I went into recovery before booting up and I did the mistake of letting TWRP install the root (I have the app to install the root but no root). So I've booted the device again and I was greeted by the system again, but with the difference that it seems unable to save any change to any part of the memory, and after 15 seconds to 1 minute it will always restart.
Whatever setting you change before it reboots, it is forgotten and always starts up at the same state as before. Even if you add a file to the memory, after a reboot it disappears.
Same goes from the recovery. Wiping, installations or whatever else will show as progressing properly, but the system will be unchanged after you reboot.
I've tried all I can think off:
- Odin: Most of the time it will give out "Nand write start fail". However, when the installation actually starts it shows the process till completion, but again no changes at all when you start the system.
- TWRP: Factory reset no changes, Advanced wipe with all selected no changes, wipe+zip installation (using sd for the files) no changes, data format no changes. I even tried to manually send the commands for a wipe using the terminal, but no changes
It will always show as if the commands were applied and files deleted (even checking with the file manager), but as soon as you reboot it is back to the original state.
- I even tried using the factory reset built in the setting, but when you click on erase everything it does not send the command.
- Lastly, I've tried to disconnect the battery hoping that a discharge would affect the situation in any way. It didn't
So here is the status.
Please hit me with any suggestion to fix this issue.

D4V3an0n said:
Hello there,
I have a problem with my T210 that I'm unable to fix. I've tried them all but it did not change at all.
So, starting things off, the problem started after flashing T210XXBNH4_T210OXABNH4 using Odin. I've booted and did the setup process, all working fine till there. Then back to Odin I've flashed t210-TWRP 3.0.0. After that, I went into recovery before booting up and I did the mistake of letting TWRP install the root (I have the app to install the root but no root). So I've booted the device again and I was greeted by the system again, but with the difference that it seems unable to save any change to any part of the memory, and after 15 seconds to 1 minute it will always restart.
Whatever setting you change before it reboots, it is forgotten and always starts up at the same state as before. Even if you add a file to the memory, after a reboot it disappears.
Same goes from the recovery. Wiping, installations or whatever else will show as progressing properly, but the system will be unchanged after you reboot.
I've tried all I can think off:
- Odin: Most of the time it will give out "Nand write start fail". However, when the installation actually starts it shows the process till completion, but again no changes at all when you start the system.
- TWRP: Factory reset no changes, Advanced wipe with all selected no changes, wipe+zip installation (using sd for the files) no changes, data format no changes. I even tried to manually send the commands for a wipe using the terminal, but no changes
It will always show as if the commands were applied and files deleted (even checking with the file manager), but as soon as you reboot it is back to the original state.
- I even tried using the factory reset built in the setting, but when you click on erase everything it does not send the command.
- Lastly, I've tried to disconnect the battery hoping that a discharge would affect the situation in any way. It didn't
So here is the status.
Please hit me with any suggestion to fix this issue.
Click to expand...
Click to collapse
Hello I will try to help you
Go to this link and download repair firmware for your tab
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=12003
Open Odin and tick erase
Select csc, pda, etc from the firmware you have downloaded
This will fix the fimware
Sorry for bad English

sasi2006166 said:
Hello I will try to help you
Go to this link and download repair firmware for your tab
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=12003
Open Odin and tick erase
Select csc, pda, etc from the firmware you have downloaded
This will fix the fimware
Sorry for bad English
Click to expand...
Click to collapse
HI,
Thank you for your answer. I tried what you said, but I am unable to.
My device is now acting differently than before. As I said with Odin it gave "NAND write start fail" most of the time, but after multiple attempts, it would go through the flashing process.
I'm now always getting instead a "Complete (write) operation failed"
here is the log of two following attempt:
Code:
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006> ERASE_SECTOR: 0
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> PBL.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ps. there is a Removed/added between the two because if you don't the process would get stuck at SetupConnection indefinitely
pps. also sometimes at the second attemp it will also say "There is no PIT partition" right before the "Complete(Write) operation failed" error
I've tried to change USB port, change the cable, reinstall drivers (the device seems to be recognized correctly), change the version of Odin (from 1.3 to 3.13.1), and even do multiple attempts during the same Odin session as some suggest that would solve the "Complete (write) operation failed".
However, the problem persists.
What next?

D4V3an0n said:
HI,
Thank you for your answer. I tried what you said, but I am unable to.
My device is now acting differently than before. As I said with Odin it gave "NAND write start fail" most of the time, but after multiple attempts, it would go through the flashing process.
I'm now always getting instead a "Complete (write) operation failed"
here is the log of two following attempt:
Code:
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006> ERASE_SECTOR: 0
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> PBL.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 1536 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Erase...
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ps. there is a Removed/added between the two because if you don't the process would get stuck at SetupConnection indefinitely
pps. also sometimes at the second attemp it will also say "There is no PIT partition" right before the "Complete(Write) operation failed" error
I've tried to change USB port, change the cable, reinstall drivers (the device seems to be recognized correctly), change the version of Odin (from 1.3 to 3.13.1), and even do multiple attempts during the same Odin session as some suggest that would solve the "Complete (write) operation failed".
However, the problem persists.
What next?
Click to expand...
Click to collapse
Try using another USB and Odin 3.10
Edit:Try flashing only bootloader and tell me

sasi2006166 said:
Try using another USB and Odin 3.10
Edit:Try flashing only bootloader and tell me
Click to expand...
Click to collapse
I've tried with all the USBs that I have.
With Odin 3.10 it is the same. Same error same log.
I've also tried flashing only the bootloader, but no difference.
edit: I would like to underline that USB debug works for the few minutes that the device stays turned on. Is there anything I could try through there?
edit2: I've also now tried with all four of the firmware versions that are available at the provided link. Same Complete(write) error tho.

D4V3an0n said:
I've tried with all the USBs that I have.
With Odin 3.10 it is the same. Same error same log.
I've also tried flashing only the bootloader, but no difference.
edit: I would like to underline that USB debug works for the few minutes that the device stays turned on. Is there anything I could try through there?
edit2: I've also now tried with all four of the firmware versions that are available at the provided link. Same Complete(write) error tho.
Click to expand...
Click to collapse
First Try unistalling root and in flash firmware with odin
Edit:Try flashing Android 4.1 and tick erase all
Link android 4.1 4 file firmware:
https://androidfilehost.com/?fid=24499762636002697

Fixed?

sasi2006166 said:
Fixed?
Click to expand...
Click to collapse
Sorry for the late reply.
The root is not installed. As I said the TWRP installed an app as a system to install the root, but I have no root. I have no way to remove the app as the recovery is unable to apply any change to the system.
I've tried to install 4.1.2, but usual Odin error.

D4V3an0n said:
Sorry for the late reply.
The root is not installed. As I said the TWRP installed an app as a system to install the root, but I have no root. I have no way to remove the app as the recovery is unable to apply any change to the system.
I've tried to install 4.1.2, but usual Odin error.
Click to expand...
Click to collapse
Try flashing custom stock rom
Edit: First try flashing recovery, and flash fimware

May not make any difference, but I always had better luck with Odin 3.07. You can grab it HERE.
Also, keep in mind that if you have flashed the KitKat bootloader, you can not go back to the 4.1.2 firmware.

sasi2006166 said:
Try flashing custom stock ROM
Edit: First try flashing recovery, and flash fimware
Click to expand...
Click to collapse
Flashing a recovery gives out the same Complete(write) failure.
Custom stock ROM flashed by recovery go to the completion of the process, but they do not change a thing to the system. Is there any custom ROM for odin?
gr8nole said:
May not make any difference, but I always had better luck with Odin 3.07. You can grab it HERE.
Also, keep in mind that if you have flashed the KitKat bootloader, you can not go back to the 4.1.2 firmware.
Click to expand...
Click to collapse
With the 3.07 version of Odin, I've managed to get the other weird problem that I've mentioned at the start of my tread. The flashing will go to completion, but the system is unchanged.
Here is the log flashing T210XXBOA3 (4.4.2) with erase:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T210XXBOA3_CL3952694_QB3792367_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_T210XXBOA3_CL3952694_QB3792367_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ILO_T210ILOBNI2_CL2813887_QB2395848_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> PBL.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> param.lfs
<ID:0/006> loke_2nd.bin
<ID:0/006> loke_pxa988.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> NVM.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The system and bootloader currently installed are 4.4.2 T210XXBOA3. The same I was trying to install.
Edit: on that note here is another attempt flashing T210XXBNH5 with same results, no changes to the system:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_T210XXBNH5_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_T210XXBNH5_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_T210XXBNH5_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OJV_T210OJVBNH1_2432755_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> PBL.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> param.lfs
<ID:0/006> loke_2nd.bin
<ID:0/006> loke_pxa988.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> NVM.img
<ID:0/006> radio.img
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/004> Removed!!
<ID:0/004> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

Ok, let's focus on one thing at a time.
When you say "no changes to the system", does that mean you still can't write to storage and the device still reboots?
One thing to remember is that flashing through Odin does not wipe memory, so your settings and data will remain intact.
I recommend trying this: Flash stock 4.4.2 firmware. Do not attempt any custom recovery yet. Boot into system and do a factory reset, or boot into stock recovery and do factory reset.
If you can get that to work; then you can try adding the custom recovery and root.

gr8nole said:
Ok, let's focus on one thing at a time.
When you say "no changes to the system", does that mean you still can't write to storage and the device still reboots?
One thing to remember is that flashing through Odin does not wipe memory, so your settings and data will remain intact.
I recommend trying this: Flash stock 4.4.2 firmware. Do not attempt any custom recovery yet. Boot into system and do a factory reset, or boot into stock recovery and do factory reset.
If you can get that to work; then you can try adding the custom recovery and root.
Click to expand...
Click to collapse
When I say nothing has changed I mean it in every way. For example, in the last attempt, I've used a different build version of the system, but the one installed is still the same one. Every setting is the same and the Superuser.apk (that is probably the one causing problems and installed as a system app) is still there every time. I even tried flashing Cwm recovery through Odin, and even though the process went through I still have TWRP.
Besides, I was using Odin nand erase in many of my attempts, and if I'm not mistaken that should format the content.
Moreover, I've mentioned before that not even the changes to the system did while the device is booted, such as setting changes, are kept. As soon as you reboot, it is back to the previous state.
About factory reset: Factory reset through the system does not work, it just reboots. Through TWRP recovery I've tried everything as mentioned in the main thread: factory Reset, Advanced wipe with system selected as well, Format data, manual wipe using shell commands. TWRP will go through the process, but no changes made. (I've tried again now just for the sake of completion but the result is the same).

I have an idea
Flash twrp and boot to recovery
Go to advanced-file manager
Go to system-app or priv app and find superuser.apk
Click on it and delete
And re flash the firmware

sasi2006166 said:
I have an idea
Flash twrp and boot to recovery
Go to advanced-file manager
Go to system-app or priv app and find superuser.apk
Click on it and delete
And re flash the firmware
Click to expand...
Click to collapse
Tried before and tried again now with your exact process, no changes.
I've also tried before to delete it (apk and data folder) using twrp terminal, twrp file manager and adb shell with usb debugging. No changes at all. (with those three methods I've also tried manually applying a factory reset but as usual no changes at all.)

D4V3an0n said:
Tried before and tried again now with your exact process, no changes.
I've also tried before to delete it (apk and data folder) using twrp terminal, twrp file manager and adb shell with usb debugging. No changes at all. (with those three methods I've also tried manually applying a factory reset but as usual no changes at all.)
Click to expand...
Click to collapse
With Odin try flashing ONLY PDA and BOOTLOADER

sasi2006166 said:
With Odin try flashing ONLY PDA and BOOTLOADER
Click to expand...
Click to collapse
No use, same result.

D4V3an0n said:
No use, same result.
Click to expand...
Click to collapse
Hey you have fixed?
Make screen recording and share
sorry for bad english

sasi2006166 said:
Hey you have fixed?
Make screen recording and share
sorry for bad english
Click to expand...
Click to collapse
still not fixed

has anyone got any idea on how to fix it