Related
Hello, I recently acquired a note 2 n7100 and I have been trying to restore it. However, every time I try using odin, it gives me the that I the frimware upgrade encountered an issue error. I used the pit, but now it goes to the splash screen but nothing after that... Just a black screen. What should I do? I have been at this for hours and I am losing my mind!
Anyone have a solution? I am dying here!
EDIT: I got to the screen with the android on it and the little spinning ball in him, but then it just keeps booting to the android figure with the spinning globe. Any ideas?
You ll need to be more specific with your problem. Did you aquire the phone in working state? What were you trying to do. What did you do to achieve that? What was the results. What did you do to compansate that ? Etc....
Sent from my GT-N7100 using xda app-developers app
Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used
dr.ketan said:
Try rebooting recovery (vol up+home+power)
wipe cache and data
if not works, input full details with complete odin log
and which ROM and pit file you have used
Click to expand...
Click to collapse
Hello doc! I used the n7100 16gb pit you made and I am using the united arab stock rom, that is the only one that allows me to get to the android screen instead of a black screen. I tried the recovery button combo but that did not let me get into recovery.
I can update with my odin log when I get home. It all passes, nothing fails... So I guess I really dont know what is wrong with it.
Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin
dr.ketan said:
Ok, try flashing stock recovery (get from here )
if you can flash it correctly then try rebooting in recovery and wipe cache and data.
otherwise post log of odin
Click to expand...
Click to collapse
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!
minnieman said:
Thank you! Where do I find the log? Also if I can get this working I will definitely donate!
Click to expand...
Click to collapse
The area which shows getting pit for mapping in odin application and all.
Sent from my GT-N7100
Ok, I tried flashing the recovery but that didn't work. I tried flashing the stock rom via odin again and it came up with the connect to kies error until I put the 16gn pit in and now it is back to the android figure with the spinning orb... Enclosed is the log, any other ideas? I am at a loss for words here.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB5_N7100OJVDMB1_N7100XXDLK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
UPDATE: nevermind, it officially bricked so I am sending it in to be resurrected. Thanks for the help anyways doc!
Well it is flashing normally. Find a rom that will factory reset your phone.
Sent from my GT-N7100
Model: SGH-T999V (Wind Mobile)
Firmware Rom: Cyanogenmod 10.1.3 (IIRC, might have been 10.1.2)
So, last night I plugged my phone in to my computer to charge. I walked away to do some other things, and when I came back a few minutes later I found it rebooting, or at least trying to. It seemed to be stuck in a loop. It would vibrate and show the Samsung logo, and then show the model logo (in my case "Samsung Galaxy SIII" with the cyanogenmod logo on the bottom half of the screen). After this, it would vibrate twice with around a two second delay between each vibration. Then it would show the Samsung logo, the model logo, and vibrate twice again, repeating indefinitely. The only thing that stops the loop is pulling the battery.
At this point I'm thinking that there's a problem with the battery. I kept it plugged in to my computer for a little while while it tried to boot, hoping that it just needed to be charged. After this didn't work, I tried charging it with a portable battery pack I had and used a different cable. Still nothing. Then, I found a spare battery that I had and replaced the one I had been using. That didn't work either, the phone continued doing the same boot loop.
I don't believe that the problem is a faulty power button, since it doesn't start trying to boot until I either plug it in to charge or I press the power button myself. I can't seem to enter recovery mode. Whenever I try, it shows the initial Samsung logo screen with "Recovery Booting...." in small blue text in the top left corner of the screen, but then proceeds to reboot again.
I am, however, able to enter download mode. I decided to try and flash my stock firmware, hoping that would fix the problem. I put my phone in download mode, opened odin, and it seemed to recognize my phone. I loaded the .md5 file and hit start, but almost immediately it showed 'FAIL'. This is what it said in the message box:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
At this point I have no idea what else I can do. I hope it's not a hardware failure, but it's starting to look like that's the case. Is there anything else I can try, or is my phone just dead? And, if it is dead, does anyone know the exact cause?
CM is your rom, not your firmware. The firmware is what we generally refer to as everything but system, kernel and recovery. Do you know what your current firmware build is?
Are you certain you downloaded the Wind version of the firmware?
I could be wrong but from the Odin output it looks like you have pre 4.3 firmware. If so, try using any other build and see if it flashes.
Judging from the symptoms you described, it is possible you could be looking at a hardware failure. Possibly the SoC, but more likely the memory. If you cant get Odin to flash anything the possibility of this becomes greater.
Try other firmware with Odin. Try with and without re-partition checked. (This will wipe all your data)
Try flashing TWRP via Odin. If that makes recovery work you may then be able to factory reset and flash a rom again.
Try different usb cables and ports. Try another computer as well if nothing else is helping.
Beyond all of that, im not sure theres gonna be much you can do.
Argh, I always seem to get ROM and firmware mixed up. Anyway, If I'm understanding this correctly I'm pretty sure that my firmware was 4.2.2. I definitely downloaded the wind version of my stock firmware. I also found on my computer 4.0 firmware that I'd downloaded a couple years ago. I tried flashing that with odin and got the same result. Then I tried it with re-partition checked and it failed again with this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I guess that's that then. Luckily I had backed up all my photos last week on a whim.
Out of curiosity, did you use a PIT file when repartitioning, or did it use the one in the device? Whichever it is, try the other as well. I believe the pit files are in the General section.
I used the PIT file on my device when I first tried to repartition. I downloaded the PIT file that you were talking about and tried again:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you try flashing recovery only? And does odin see the devices COM port in the top left?
Did you try different ports and cables?
Odin does see the COM port. I just tried flashing TWRP and odin said that it passed, but I'm still not able to boot into recovery mode. I have tried using another port but I don't have another cable on me.
Well if it said it passed the recovery flash, the cable and port are probably ok.
Im not really sure there is much else you can do tbh. Its sounding more like a hardware problem at this point.
Sorry I dont have anything better to tell you, but if I think of anything else you could try ill let you know.
Hey everyone ,I need some help to solve my issue , I have galaxy note 3 n900t Tmobile ,few months ago I have root my phone and I have my rom manager app purchased so I used it to flash their recovery ,phone worked fine ,few days ago after rebooting it went to download mode by itself and kept restating and going to download mode over and over and did not boot.
So I tried vol up+home+pwr it instead going to recovery it happened same thing it went to download mode and reboot and over and over ,so I pulled out battery and using buttons I went to download mode and when asked to continue or cancel I picked cancel and phone restarted and without problems booted up and works ,I use stock rom 4.4.2 .
And story got worst now ,since everything seems to be fine phone works right ,its not ,It wont go to recovery mode anyway using rom manager or button way,using odin 3.7 and 3.10 no matter flashing any recovery file FAIL, flashing stock firmware FAIL at aboot ,using Kies to update firmware FAIL ,I tried all What I know and nothing helps odin shows me that writing memory fail ,I have not tied to use nand memory erase ,and reboot since I have not use that ever and im scared to do it since phone kinda work I dont want to brick it ,so if anyone know how Please advise ,Thanks
odin massage :
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUDNE6_N900TTMBDNE6_N900TUVUDNE6_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> aboot.mbn
<ID:0/005> __XmitData_Read ..
<ID:0/005> XmitData Fail..
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
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
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