Related
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DXLH1_S7500OLBLF1_S7500DXLH1_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> system.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
thank
thanhdeptrai said:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DXLH1_S7500OLBLF1_S7500DXLH1_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> system.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
thank
Click to expand...
Click to collapse
unninstall kies and all your usb drivers then install samsung drivers but NOT KIES
thanhdeptrai said:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DXLH1_S7500OLBLF1_S7500DXLH1_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> system.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
thank
Click to expand...
Click to collapse
i use odin 3.09 and always succesfull in flashing a stock rom. i always failed in other version:good::victory:
thanhdeptrai said:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DXLH1_S7500OLBLF1_S7500DXLH1_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> system.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
thank
Click to expand...
Click to collapse
It is a driver problem...
You can try to use another version of odin like 3.04 or 3.07 or 3.09 if reinstalling drivers will not work
I have got stuck in a boot loop, i forgot to make a backup in PhilZ Touch Advanced CWM Recovery and i've tried to restore to the original file with Odin3 V. 3.09 and
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T310UEUAMH2_T310XARAMH2_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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this pops up. I have done the download mode and http://forum.xda-developers.com/showthread.php?t=2618798 tried using this tool so i could go to the stock firmware so far nothing is working. PLEASE HELP
Hello,
I have been trying to install TWRP on my T-mumble S7, no luck. I have the lastest version of odin, and have played round-robin with the usb ports. This is my Odin log
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> recovery.img
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would awesome
Did you root first?
Sent from my SM-G930F using Tapatalk
T-Mobile US? You have the Snapdragon processor?
Then as far as I know it is not possible to flash custom Recovery...
I've been trying for more than 2 weeks now to get my phone back to working condition, I finally decided to just register and ask, maybe I'll get lucky right?...
So, I've been using all kinds of threads found mainly on this site thus far. A few from other sites but mainly here, it seems like the trusted place online for this kind of stuff. I had rooted my phone without much knowledge prior to doing so, and was very careful with it after root. Then one dark day... I was uninstalling something and hit cancel. From there, my troubles began. Soft bricked, freezes at logo.
https://forum.xda-developers.com/gr...files-sm-s920l-straight-talk-verizon-t3411688
This thread here is the last place I was looking to fix my phone, but just couldn't get it to work. Finally got my phone to at least show up in odin, I'm pretty sure that's only because I fired up a virtual PC which installed win. 7 drivers (The OS I wanted to emulate so I could see my phone again). I didn't have to actually install the OS on my virtual PC, the simple installation of the program and the win7 setup (I'm pretty sure at least) made my phone recognizable by odin. Here are the details:
On Downloading Screen -
Odin Mode
Product Name: SM-S920L
Current Binary: Samsung Official
System Status: Custom
Reactivation Lock(kk): On
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, H1, R1, A1, P1
Secure Download: Enabled
Secure Check Fail: Boot (Has changed many times, I've seen system, recovery, and boot so far. I usually don't pay attention though, so possibly more)
With Odin using files from the above thread and other threads, the furthest I have gotten was with a combination of files in the above thread. It actually started writting, but then failed. Generally doesn't get that far.
Here are several attempts I've made in the last half hour
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.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> system.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.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Removed!!
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> stock.sm-s920l.recovery.tar.md5 is invalid.
<OSM> End...
<ID:0/003> Added!!
<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.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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.
<OSM> All threads completed. (succeed 0 / failed 1)
I have the ability to start the phone with options to use system recovery, clear cach, etc. Actually, it's probably smarter to just restart my phone and list my options so you know exactly what is showing.. Before I do, I sometimes leave the SIM card in, sometimes have it out. Doesn't seem to make a difference.
Reboot System Now
Apply Update from ADB
Apply update from external storage
Apply update from Cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
I've tried nearly every combination of things I could think of, and it remains the same. I've read several threads saying my problem is the reactivation lock, yet most of those threads had someone saying they fixed theirs in some unique way. If anyone at all knows step by step what I need to do, please please let me know. I'm running a windows 8.1 (Recently upgraded from win. 8 with several notable problems (missing system files/drivers))
Thank you in advance! If any extra info is needed, please let me know. Please keep in mind that until I soft bricked my phone, the most I knew about phones beyond your typical user was that rooting existed, and the stuff you could use/do after rooting was awesome, until I accidentally hit cancel.
(Almost forgot to mention, my wife has exact same phone/model as I do. Can something be done knowing that? I just, can't do anything that would risk her phone's operating condition)
I don't know how! But I think I got a little further!
<ID:1/003> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:1/003> Odin v.3 engine (ID:3)..
<ID:0/004> File analysis..
<ID:1/003> File analysis..
<ID:0/004> SetupConnection..
<ID:1/003> SetupConnection..
<ID:1/003> Initialzation..
<ID:1/003> Get PIT for mapping..
<ID:1/003> Firmware update start..
<ID:1/003> system.img.ext4
<ID:1/003> NAND Write Start!!
<ID:1/003> Transmission Complete..
<ID:1/003> Now Writing.. Please wait about 2 minutes
<ID:1/003> Receive Response from boot-loader
<ID:1/003> FAIL! (Auth)
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 2)
<ID:1/003> Removed!!
<ID:0/004> Added!!
I feel like I'm talking to myself but oh well, if someone see's this and knows how to help, worth it. I think I made more headway (think).
<ID:0/004> Removed!!
<ID:0/003> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Now I need to learn more about the pit file (I think I read it had something to do with partitioning the phone correctly) but not sure where to look for this file
I've now downloaded Android Studio, in case that opens my options for me
Hi !
I`m not much knowledgeable into samsung Odin unbrick methods but what I can suggest first is to perform all the Odin commands on a clean installed windows system
Sometimes failures occurs from window`s side and Odin won`t tell you that , it will just say "fail"
Don`t use emulated operating systems , some commands aren`t recognized on virtual systems
And no , other similar device won`t help you , the only files you can use are those officially provided by manufacturer
Also be sure you use an original usb data transfer cable
Good luck !
I'm very sure. My wifes phone, again same exact phone to the model, connects to the computer just fine. Also, I'm not trying to do anything at all from a virtual PC. That initially was my plan, but then upon setting up the vpc, windows 10 started recognizing my devices. I believe that has something to do with the files installed to run the old drivers supporting windows 7. Either way, I don't even launch the virtual pc app anymore yet alone run it. I have aquired so many files now that people, here and there, have made available for my phone. Recently I read that it's possible Odin can't install then because those files came from the same phone but different country, and I guess cross country sharing of these kinds of files was restricted somehow. Lately I've been attempting to understand flashboot and android studios. Flashboot is over my head, ever so slightly. Studios is way over my head. I somehow, no clue how I did it, sideloaded (I think it's called) something from studio to my phone. Don't know what it was, didn't help, seemingly hasn't hurt either. No change. I feel this has a solution, I just don't know how to come about it. I've scoured these forums, there is a stock kernal in one of these threads, along with a I believe a stock recovery. Don't know how to go about flashing them. I'm way too new at this. I've been to tutorials, guides, taken leaps of faith on not so sure about this flashes (which didn't matter because I havn't successfully flashed a single thing with Oden, the phone is in the exact same state as when it first started freezing on tracphone screen. Sadly, I feel like unless someone gives me instructions a toddler could understand fixing my problem, or remote assists me, I am not going to have a phone for a long time Take a look at how much **** I've accumulated lol. Odd, screenshot is not working. There are min. 50 files, some duplicates that I wanted in certain, multiple folders. Programs for flashing and recovering. Files for my phone. There's just so much lol.
my phone is kinda stuck on bootloop with the same error in red letters "Could not do normal boot , invalid kernel length" , sadly the usb debbuging option wasn't turned on before the problem sowhenever i try flashong stock rom it doesn't work , if i try flashing ap bl csc cp , i get re partion operation failed and if i check the box it also fails saying couldn't open specified file , but when i try to flash only ap i get another error which is Complete(Write) operation failed. any solution pls ?
K1RA10 said:
my phone is kinda stuck on bootloop with the same error in red letters "Could not do normal boot , invalid kernel length" , sadly the usb debbuging option wasn't turned on before the problem sowhenever i try flashong stock rom it doesn't work , if i try flashing ap bl csc cp , i get re partion operation failed and if i check the box it also fails saying couldn't open specified file , but when i try to flash only ap i get another error which is Complete(Write) operation failed. any solution pls ?
Click to expand...
Click to collapse
Try flashing without using the re-partition option, just flash the firmware files without changing any of the settings and options in Odin, Odin's default settings should be all you need.
Droidriven said:
Try flashing without using the re-partition option, just flash the firmware files without changing any of the settings and options in Odin, Odin's default settings should be all
Droidriven said:
Try flashing without using the re-partition option, just flash the firmware files without changing any of the settings and options in Odin, Odin's default settings should be all you need.
Click to expand...
Click to collapse
so after some tries my problem can be summarized as, if i flash all the firmware ( AP+CSC+BL+CP) i get the re partition error but when i flash only AP ia get the complete(write) operation failed , also i can't flash twrp recovery cause ot says frp lock on, any solution?
Click to expand...
Click to collapse
K1RA10 said:
so after some tries my problem can be summarized as, if i flash all the firmware ( AP+CSC+BL+CP) i get the re partition error but when i flash only AP ia get the complete(write) operation failed , also i can't flash twrp recovery cause ot says frp lock on, any solution?
Click to expand...
Click to collapse
Yes, I understand what you said in your first post.
Are you selecting the "re-partition" option in Odin when you flash the firmware or are you not selecting the "re-partition" option when you flash the firmware? You should not be getting the re-partition error unless you are using the re-partition option when you flash the firmware, if this is what you are doing, try flashing without using the re-partition option.
Try finding the newest version of engineering firmware for your specific model number, if one exists for your model and is available to the public. Engineering firmware can be used to fix the FRP lock. Do some Google searching to learn how to use the engineering firmware to fix FRP lock.
Droidriven said:
Yes, I understand what you said in your first post.
Are you selecting the "re-partition" option in Odin when you flash the firmware or are you not selecting the "re-partition" option when you flash the firmware? You should not be getting the re-partition error unless you are using the re-partition option when you flash the firmware, if this is what you are doing, try flashing without using the re-partition option.
Try finding the newest version of engineering firmware for your specific model number, if one exists for your model and is available to the public. Engineering firmware can be used to fix the FRP lock. Do some Google searching to learn how to use the engineering firmware to fix FRP lock.
Click to expand...
Click to collapse
so now that i have tried the engineering firmware (combination file) , i still get the re partition error even tho i have this option unchecked in odin , and when i try to flash stock firmware or latest firmware i get the complete write error
this is what i get wheen i flash stoock rom,( re partition is unchecked)
<ID:0/003> Removed!!
<ID:0/003> 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..
<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:0/003> File analysis..
<ID:0/003> Total Binary size: 3364 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is what i get when i check the re partition
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3364 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 2006)
<OSM> All threads completed. (succeed 0 / failed 1)
-----------------------------------------------------------------------------
now flashing with latest rom
re partition unchecked :
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4019 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
re partition checked :
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4019 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 2006)
<OSM> All threads completed. (succeed 0 / failed 1)
-----------------------------------------------------------------------------
flashing only ap without and after adding pit file :
<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:0/003> File analysis..
<ID:0/003> Total Binary size: 3826 M
<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.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3826 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
K1RA10 said:
this is what i get wheen i flash stoock rom,( re partition is unchecked)
<ID:0/003> Removed!!
<ID:0/003> 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..
<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:0/003> File analysis..
<ID:0/003> Total Binary size: 3364 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is what i get when i check the re partition
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3364 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 2006)
<OSM> All threads completed. (succeed 0 / failed 1)
-----------------------------------------------------------------------------
now flashing with latest rom
re partition unchecked :
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4019 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
re partition checked :
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4019 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Can't open the specified file. (Line: 2006)
<OSM> All threads completed. (succeed 0 / failed 1)
-----------------------------------------------------------------------------
flashing only ap without and after adding pit file :
<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:0/003> File analysis..
<ID:0/003> Total Binary size: 3826 M
<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.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3826 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It seems to be connecting and disconnecting, are you sure that you are using a good cable and have it securly connected to the device? It also seems to be having trouble finding or loading your PIT file. You may have to download a PIT file for your specific device model number, if it is available for download.
Let me do some searching to see what your specific errors that it is reporting mean and I'll post here with what I find.
Droidriven said:
It seems to be connecting and disconnecting, are you sure that you are using a good cable and have it securly connected to the device? It also seems to be having trouble finding or loading your PIT file. You may have to download a PIT file for your specific device model number, if it is available for download.
Let me do some searching to see what your specific errors that it is reporting mean and I'll post here with what I find.
Click to expand...
Click to collapse
about the connection and disconnecting issue, it's cause when i flash and it doesn't work i have to get out of download mode and get back in, that's why it appears as added and removed, and about the pit file i found one and loaded it but as you see re partition error, thank you for the efforts
K1RA10 said:
about the connection and disconnecting issue, it's cause when i flash and it doesn't work i have to get out of download mode and get back in, that's why it appears as added and removed, and about the pit file i found one and loaded it but as you see re partition error, thank you for the efforts
Click to expand...
Click to collapse
Have you tried turning off antivirus? It can cause a myriad of errors in Odin.
Droidriven said:
Have you tried turning off antivirus? It can cause a myriad of errors in Odin.
Click to expand...
Click to collapse
i turned antivirus off and tried to flash stock rom i got this new error :
<ID:0/003> 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:0/003> File analysis..
<ID:0/003> Total Binary size: 3248 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
----------------------------------------------------------------------------
while flashing twrp gives :
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 22 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the phone saying Custom Binary(RECOVERY) Blocked By FRP Lock
K1RA10 said:
i turned antivirus off and tried to flash stock rom i got this new error :
<ID:0/003> 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:0/003> File analysis..
<ID:0/003> Total Binary size: 3248 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
----------------------------------------------------------------------------
while flashing twrp gives :
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 22 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the phone saying Custom Binary(RECOVERY) Blocked By FRP Lock
Click to expand...
Click to collapse
K1RA10 said:
i turned antivirus off and tried to flash stock rom i got this new error :
<ID:0/003> 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:0/003> File analysis..
<ID:0/003> Total Binary size: 3248 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
----------------------------------------------------------------------------
while flashing twrp gives :
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 22 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and the phone saying Custom Binary(RECOVERY) Blocked By FRP Lock
Click to expand...
Click to collapse
Can you still boot into stock recovery? If you can, factory reset your device while in recovery then boot into download mode. Flash the stock firmware, this time try enabling the "re-partition" option in Odin. Then, if you have a copy of your PIT file, select the PIT tab in Odin and place the PIT file in its slot then click Start to begin the flash.
Droidriven said:
Can you still boot into stock recovery? If you can, factory reset your device while in recovery then boot into download mode. Flash the stock firmware, this time try enabling the "re-partition" option in Odin. Then, if you have a copy of your PIT file, select the PIT tab in Odin and place the PIT file in its slot then click Start to begin the flash.
Click to expand...
Click to collapse
i can only boot into dowload mode
Hi;
My friend installed a wrong TWRP for Note 9 N960N and Later.
In the screen appears that’s message:” Could Not normal boot invalid kernel length”
I pull all buttons Vol Up + Power, Vol down + Power, Vol Up + Bixby + Power, Vol down + Bixby + Power, and nothing happened. Stay in the Sam message:” Could Not normal boot invalid kernel length”
Please Any Help?