So I tried to flash modem (GSM_Modem_XXUEMJ5_and_LTE_Modem_XXUBMH1.tar) before installing OmegaROM 13 to my i9505, Odin failed with message "Complete(Write) operation failed" while flashing it. Now... if I just turn phone on it boots into Download mode with message "Firmware upgrade encountered an issue..." and tells me to run Kies, which I've done and Kies also fails while flashing modem (Kies downloads and flashes I9505XXUBMG4_I9505OPSBMG2_I9505XXUBMG4_HOME image). Tried to flash original Optus ROM and it also fails while flashing modem:
...
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
thanks.
Different usb cable, different usb port, different pc, reinstall drivers, make sure kies is not running in the background.
Lennyz1988 said:
Different usb cable, different usb port, different pc, reinstall drivers, make sure kies is not running in the background.
Click to expand...
Click to collapse
Why do you think it's a usb/driver/pc/etc?! It doesn't flash modem ONLY.
mcFactor said:
Why do you think it's a usb/driver/pc/etc?! It doesn't flash modem ONLY.
Click to expand...
Click to collapse
Take the advice and just give it a try
99% of the time this is the reason for a failed flash
Obagleyfreer said:
Take the advice and just give it a try
Click to expand...
Click to collapse
Just tried. As I thought it doesn't make any difference for me.
UPD. tried on two more computers in office. one didn't work, second one did the job. now what I don't understand is why did it happen? I mean I was flashing new ROMs for ages using same computer an home, then something went wrong and Odin and Kies have failed flashing SAME file from different ROMs (that was modem) on on 3 different computers...
Related
Phone is working fine, but Odin says "There is no PIT partition" when I try to flash.
I have a GT-I9505 with the MDA version firmware, region EVR.
I've flashed it previously, successfully, to the latest ME2 firmware, but then I installed Chainfire3D which soft-bricked it.
I recovered using Kies firmware recovery, did a factory reset/cache wipe, have rooted the phone again... but now Odin won't flash the phone!
It says "There is no PIT partition", and when I try to re-partition using the PIT file from this thread, it just says "complete(write) operation failed".
I've tried Odin 1.8, 3.04, 3.07... all the same.
The phone is currently working fine and is rooted! I just want to flash to a newer firmware, is all.
Any thoughts?
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
I was doing both those things. Strangely, it worked when I used another computer! Thanks anyway.
I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.
0reo said:
I am having similar problems. Any other suggestions?
I'm trying to root my S4 for the first time. Just had the S4 factory reset itself before starting this attempt.
Seems like the USB connection keeps resetting. I don't have this problem on any other device and I've tried swapping USB cords as well as USB ports. Tried both USB 2.0 and 3.0 ports. I keep getting the same problems. I've even tried including the PIT file for re-partitioning. Even the Kies connection keeps resetting. Kies trouble shooting the USB connection resulting in reloading some drivers but that didn't have any effect.
ODIN output below:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Removed!!
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Added!!
<ID:0/010> Removed!!
<ID:0/011> Added!!
<ID:0/011> Removed!!
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Removed!!
<ID:0/011> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/011> Added!!
Now, searching lead me to a thread for I think the S3 and they were saying these kinds of problems were defective motherboards on the phone. Do I need to take my phone back to Verizon for warranty replacement? It's not even a week old yet.
Click to expand...
Click to collapse
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin
samersh72 said:
uninstall driver then re-install it. make sure kies is not running. flash pit file with the firmware in odin
Click to expand...
Click to collapse
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
NO NEED to check it. a lot of users brick their phones and can not boot to check usb debugging. so they went directly to odin flash and it was good to go :good:
0reo said:
For the record, I just convinced the local VZW store to swap me a NIB S4 as a warranty replacement. The new S4 is giving me the exact same problem so in all likelihood the phone is not my problem.
Going to try removing and reinstalling the drivers on the PC again.
Does USB debugging need to be checked / unchecked for ODIN to work?
Click to expand...
Click to collapse
Hi,
USB debugging needs to be ticked.
OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?
0reo said:
OK, I uninstalled and reinstalled the drivers and still get the same problems. Any other ideas?
Click to expand...
Click to collapse
Hi,
Did you reboot your PC?
malybru said:
Hi,
Did you reboot your PC?
Click to expand...
Click to collapse
Yes, a number of times at every stage one would think it would make any difference. It didn't make any difference.
I did finally get my phone rooted. While I can't say for certain, it seems like the S4 needed to be booted normally, then connected via USB, then let Win7 auto install several drivers, then I initiated bhp090808's all-in-one root tool which rebooted the phone into ODIN mode. ODIN was then successful.
Contrast that with having the S4 disconnected from USB and manually booting into ODIN mode, then connect USB, then let Win7 install drivers, then initiate ODIN to start. That sequence gave me all the problems.
Thanks for the replies though. I do appreciate your willingness to help.
Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1
On pit partition found
samersh72 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND.
Click to expand...
Click to collapse
aa
---------- Post added at 08:53 AM ---------- Previous post was at 08:48 AM ----------
samersh72 said:
Flash .pit file with the firmware, not alone make sure re-partition is ticked
Sent from my Galaxy using xda premium
Click to expand...
Click to collapse
mpalka said:
Solved same problem this way:
1) Connected phone by original cable directly to rear USB port
2) Turn off Kies (no need to uninstall)
3) Stopped 2 kies processes which still run even if kies is off.
4) There must be item "Samsung Android Phone" and cascaded item "Samsung android ADB interface" in device manager.
5) Enable USB Debugging in phone.
6) I had unchecked item "Check installed apps from ADB by USB" - Not sure if it is necessary.
7) When you connect phone there has to be popup with question: "Allow USB debugging from this computer?" followed by computer signature.
Check always, answer yes.
8) Use old Odin 3 V. 1.85
i9505+stock firmware+win7sp1
Click to expand...
Click to collapse
]I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND
Sagar6699 said:
I flashed cm 10.1 on my SAMSUNG Galaxy Ace Plus.Now I want to come back to my stock rom . I downloaded the stock rom and I am trying to flash it using ODIN.But I get the message that ON PIT PARTITION FOUND
Click to expand...
Click to collapse
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046
Re-Partition
samersh72 said:
flash pit with the firmware http://forum.xda-developers.com/showthread.php?t=2065046
Click to expand...
Click to collapse
Thanks!!
But now there is another problem........
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S7500DDLD1_S7500ODDLD2_S7500DDLD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009>
<ID:0/009> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLZ HELP!!!!!!!!
probably solve with this
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,
Thanks for that suggestion. Switching to the back USB ports worked for me.
pisicutumic said:
Well I did thgis ... searched another firmware mewer same carrier .. and I rebooted the Pc ..Nothing
But on a forum external some dude sayd ok .. If you use front USB ports theese are coted as external USB and they don't are recognized as internal USB hubs so change to a back side usb and will work I did and now after waiting like 5 minutes the process started my phone is under process restarting now ... And Voloa .. the new firmware,
Click to expand...
Click to collapse
Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
and me as well!
thanks alot! :laugh::laugh:
yanivnn said:
and me as well!
thanks alot! :laugh::laugh:
Click to expand...
Click to collapse
And me too!
Moritzio said:
Thanks for that suggestion. Switching to the back USB ports worked for me.
Click to expand...
Click to collapse
For me too, you are genious!
Hello, I tried to flash the official lollipop rom to my i9505, and during the flash, the phone got disconnected somehow(although cable was attached).
So I'm trying to flash again, ODIN recognizes device, and phone can still go to download mode, but the problem is that when I connect to odin, the phone keeps connecting and disconnecting, and odin keeps saying:
Added!!
Removed!!
Added!!
Removed!!
I tried 2 different computers, and 3 different microUSB cables.
So I can't really flash it like that, and since the previous flash failed I can't flash a custom rom from microSD either.
I wanted to flash a new ROM because I was having problems with my phone(it kept frozing, when I called people, no sound, battery was draining really fast and more).
Does anyone know what I can do, or is my phone useless now?
Hello Guys,
I'm in trouble with a G900M device, after a OTA update, it stay in bootloop, but i cannot enter in a recover mode, when i try flash any room in Odin (various versions) don't work and i receive a message on the screen:
" ODIN: flash read failure"
" ERROR: there is no a pit binary"
"SECURE CHECK FAIL : PIT"
" ODIN: flash read failure"
i have tryied to flash de pit file from this forum, and another in the internet, bot i had the same message.
can anyone help me ?
Thx.
The messages you are getting would indicate this is Odin not communicating with the device, so it's probably a PC end problem....
There is a basic checklist for odin flashing, the chances are you are probably doing everything correctly, but it won't hurt to make sure....
1) which version of Odin are you using. (3.10.7 is usually the best for the S5)
2) do you have the Samsung USB drivers installed on your PC. (You will get them when you install Kies)
3) Which version of Windows are you using. (From Windows Vista onwards you need to run Odin as administrator and Odin has had problems with Windows 8)
4) Do you have firewalls/antivirus disabled.
5) have you killed all Kies processes in task manager. (Kies interferes with Odin)
6) Are you using a primary USB socket on the pc. (A USB socket connected directly to the motherboard instead of one that runs through a 'hub')
7) are you using an official Samsung USB cable. (Other, cheaper, non branded cables are known to cause issues)
http://i.imgur.com/rVnFwJM.jpg
i've tryed to flash again whit Samsung USB 3.0 cable, and have the same trouble, i'm using windows 10, and have tested much versions for odin.
What about Kies? Have you installed it? It will give you the latest USB drivers.....
Also I'm wondering if you using Windows 10 is the problem.....it's a new OS and I'm not sure if Odin is 100% compatible yet.
If you have access to an older pc it could be worth giving it a try on that.....
I have an old XP laptop that I use whenever I flash a device......I refuse to get rid of it....lol
http://i.imgur.com/rVnFwJM.jpg
i'd installed Kies, samsung smart, drivers around internet forums and nothing, (i uninstall each item rsrs)
now i have tested at windows XP computer and odin return it:
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device screen returns:
" ODIN: flash read failure"
" ERROR: there is no a pit binary"
" SECURE CHECK FAIL : PIT"
" ODIN: flash read failure"
using two different cables (a xperia Z2 cable and 3.0 usb for samung S5 )
no longer know what to do...
My S5 is dead?
lombardy said:
My S5 is dead?
Click to expand...
Click to collapse
You can use Kies Firmware Recover instead of flash via Odin.
kies returns the same error at device screen, i'm now thinking for the trouble is in logicboard.
Sorry fella, I'm pretty much out of ideas if you want to remain stock.....I know of a website where you can get engineer or repair firmwares for the S5.....but I've already checked and they don't do one for the M variant. I don't suppose there's any way you can take it to a service centre is there?......
Have you thought about trying out a custom rom setup?
http://i.imgur.com/rVnFwJM.jpg
hi guys. I need your help for my issue. I have a galaxy s4 i9515. Since few days ago i am not able to turn it on no more. when i try it go only on download mode (it is also impossible to me boot on recovery mode). I have tried to flash stock firmware or twrp recovery from odin but every time odin says to me FAIL (after "NAND Write Start"). Could anyone suggest me a solution? thanks
The possible solution would be to try everything from changing the USB cable and USB port to trying a whole new PC and operating system.
Pwnycorn said:
The possible solution would be to try everything from changing the USB cable and USB port to trying a whole new PC and operating system.
Click to expand...
Click to collapse
i have already tried these solutions. I have read on internet that i could try a deep clean or maybe using pit file. but i could not find the repair firmware for lollipop. if you could hepl me i will thank you
Which file is failing to flash when using the stock ROM? Posting the Odin log may offer a possible solution.
it is the log...
Enter CS for MD5
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin engine v(ID:3, 1101)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDonwload..
aboot.mbn
NAND Write Start!!
FAIL!!
If I'm not mistaken, aboot is something related to the bootloader.
Yes, aboot.bin is not flashing because you need to try different USB cables, USB 2.0 ports, Odin versions, the ROM is not for the phone, and/or the bootloader on the phone is newer than the bootloader in the ROM.
audit13 said:
Yes, aboot.bin is not flashing because you need to try different USB cables, USB 2.0 ports, Odin versions, the ROM is not for the phone, and/or the bootloader on the phone is newer than the bootloader in the ROM.
Click to expand...
Click to collapse
First of all thanks for your interest. Well, i have tried different usb cable and odin version. The model i am sure is 9515 and i have downloaded the latest version of the fw from sammobile. I will try using another pc but if it will not help me what could i do?
Did you confirm the model # is 9515 in download mode?
audit13 said:
Did you confirm the model # is 9515 in download mode?
Click to expand...
Click to collapse
Yes i am sure
Since you are sure of the model number and ROM, the phone could have a defective memory chip.
So i have to send it at samsung center?
Is the phone still under warranty? If it is and the know counter has been changed from 0 to 1, the service centre may not fix it under warranty.
If there is no warranty on the phone, take it to a cell shop to see if they can force flash the phone using jtag or programming box.
Okok thanks man. However is not still under warranty
Hi,
I have a Galaxy s4 I9505 on which I try to flash a new bootloader with Odin, so a tar file containg only aboot.mbn, sbl1,sbl2, sbl3,mpn,tz.
I'm pretty sur that the current one is a 4.2.2 and I want to upgrade to a 5.0.1.
So I put my phone on USB debugging mode, boot in download mode, select the bootloader.tar (which is compatible with my phone) in the BL field of ODIN which I launched as admin, , connect my phone which is correctly detected by Odin and then start to flash. The problem is that it always fails with this message:
Code:
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have the correct samsung drivers, I tried on different PC (windows 7/10), different USB ports and USB data cables, but I have always the same error message. The only thing that I did not try is to flash with the original samsung USB cable which I read in other forums that could be the cause.
I also say that ODIN works with no problem on the same phone when I flash any stock ROM (downgrade, upgrade) or any recovery file, so that's why I don't think that the cable could be the reason.
I'm not really sure if my bootloader is unlocked but I guess it is otherwise flash would not be possible, but I have no way to see of it is unlocked or not.
I don't see what else could be the reason, write access persmission?
Thx.
try older Odin version....
mbaier said:
try older Odin version....
Click to expand...
Click to collapse
Hi, thx but I should have added also that in my first post, I think I tried every possible version of Odin from 1.83 to 3.12, no luck...
I know you said you have tried it on different PCs and USB ports, but does this mean you also tried the rear ports?
I know most PCs nowadays have front ports for convenience so maybe you haven't tried that option. Rear vs front does seem to make a difference.
Pwnycorn said:
I know you said you have tried it on different PCs and USB ports, but does this mean you also tried the rear ports?
I know most PCs nowadays have front ports for convenience so maybe you haven't tried that option. Rear vs front does seem to make a difference.
Click to expand...
Click to collapse
Yes I did
Try to flash the entire stock Rom from Sammobile.com rather than just the bootloader.
You confirmed the model # in download mode?
audit13 said:
Try to flash the entire stock Rom from Sammobile.com rather than just the bootloader.
Click to expand...
Click to collapse
already done also..it starts by flashing aboot.mbn and so fails exactly the same way..
You confirmed the model # in download mode?
Click to expand...
Click to collapse
Sorry, what do you mean by that? I don't see anything to confirm.
Boot into download mode. Is the model # gt-i9505?
Since the aboot.mbn is not flashing because the ROM is not for the phone, the bootloader in the phone is newer than the bootloader in the ROM, or you need to use the original USB cables.