Hi, today I factory reseted my Samsung Galaxy Grand Prime [SM-G531M] from the settings app using the official rom. The thing is, when I booted the phone, it didn't show up the setup page, it just kept restarting, and every time that it booted up, it would show up "Custom binary blocked by FRP". I'm now trying to use Odin to fix this, but I don't know what to do. The process already failed two times and failed, showing this in the log: " <ID:0/004> system.img
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
When I boot my phone in download mode it now shos "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
I already tried kies but it never finished connecting to the phone.
I've tried 2 cables, both the original and another and tried 3 different USB 2.0 ports. I've also installed the newest drivers.
I would really appreciate if someone could help me.
Edit: I had previouslly installed TWRP and factory reseted my phone successfully more than once.
Related
Hi,
I am really new to this and basically stuck without a phone (noob move I know).
I wanted to upgrade to Kitkat and downloaded N9005XXUENB4_N9005DBTENB1_DBT and odin v3.09.
I started up in download mode and got the following failure:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I restore so I can even just start my phone. Currently I only get the error saying upgrade failed- connect to Kies. But I again being noob never setup kies backup before.
PLEASE PLEASE help.
Where do I get a stock firmware recovery to reflash
antz69 said:
Hi,
I am really new to this and basically stuck without a phone (noob move I know).
I wanted to upgrade to Kitkat and downloaded N9005XXUENB4_N9005DBTENB1_DBT and odin v3.09.
I started up in download mode and got the following failure:
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
How do I restore so I can even just start my phone. Currently I only get the error saying upgrade failed- connect to Kies. But I again being noob never setup kies backup before.
PLEASE PLEASE help.
Where do I get a stock firmware recovery to reflash
Click to expand...
Click to collapse
Flash NB4 again but this time also flash this pit file and check repartition. If phone is getting stuck at samsung logo upon reboot, boot to recovery and factory reset.
Well first what your model, this is n9005
is your download complete, did you have the drivers installed (kies installed but you need to kill it - in order to odin to work without issues)
go through this, page, it has detail procedure in odin flash of the same ROM.
http://androidromupdate.com/tag/n9005xxuenb4_n9005dbtenb1_dbt-zip/
@antz69 , hope that helps.
Hi everyone.
What happened to my phone is the weirdest thing and so far it seems nothing can work to fix it.
It's a GT-i9500 international model. Rooted and with KitKat 4.4.2.
How I messed things up:
- Was in Titanium Backup, tried to convert one game app I previously made "system app" back to "user app". The process was taking over 20 minutes... I figured must be some kind of a freeze. Then I held the power button to shut it off.
- I then powered on again, and realized that the device is not booting! There was no "Samsung" logo.
How I tried to fix it:
- I went to the CWM recovery and tried installing my latest backup (with a custom ROM). Did that after wiping all cache (with dalvik included) and data wipe system restore in CWM. After restoring the device that way -> It boots to "samsung" animation where it stays and gets warm when left for over an hour.
- I went back to CWM this time tried to flash the custom ROM again - so I picked the custom ROM zip file after wiping cache/system restore in CWM again and waited till it finishes. Rebooted the device -> It boots to "samsung" animation where it stays and gets warm when left for over an hour.
- Again in CWM tried to this time restore the stock rom which I have backed up with CWM after I have rooted the phone. -> The weirdest thing happened after restore. The phone booted into the carrier "boot animation", then it showed "Samsung gt-9500" (first time ever I've seen this screen on this device, it was never shown before), then it went once more to "samsung" letters being lit (but without the "samsung" boot animation with that purple thing and sound).
- I tried formatting the partitions within CWM except for the EFS and external SD partition and repeating each of the above all to no avail.
When I returned the stock firmware in third example (it was stock, but that backup made by CWM recovery ofc) CWM asked on reboot if I want to get back to stock recovery, I said no since I don't want to lose CWM esp now that the phone doesn't work as it should.
Currently I'm trying to:
- Flash stock firmware with ODIN through the download mode. Sadly so far I've seemed to have downloaded the Jelly Bean ROM instead of KitKat for it because ODIN gave me (nand write) error on flashing PDA and device showed:
check fail device:3 binary:2
So yeah, downloading firmware and will try ODIN with the KitKat one (the other I tried with ODIN didn't have version written in so that's why I assumed it must be KitKat too, took it from XDA guide, but seems it was JB after all).
I also want to stress that all previous steps in CWM were all done using KitKat builds so that couldn't be the problem.
So any of you have any idea what's going on with my phone?
I find it really weird that CWM which is supposed to restore phone in case of emergencies like this failed to do so. Perhaps nandroid backup would be a better choice next time? What do you think?
EDIT:
OMG this seem bad. Tried to flash through ODIN with another ROM and this is what I got:
<ID:0/007> Added!!
<OSM> Enter CS for MD5...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUFNC1_I9500YDDFNC2_I9500DDUFNA4
<OSM> Checking MD5 finished sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialization..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> param.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (Succeed 0 / failed 1)
---
Interestingly after this - now I don't have Chinese "download" mode anymore (the phone was bought through a friend and worked for over a year fine rooted btw) now it's in English... and, if I just try to boot it it says nicely:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
It would also seem recovery is gone too now... :/
hmm...
EDIT2:
Tried a different USB cable - same result.
Tried Odin 3.10 - same.
EDIT3:
WOW... the strangest thing!
So... after reading tons of threads I have found a suggestion to change the USB port. So I did (from USB 2.0 on my laptop to a USB 3.0 one if that matters). That's on org Samsung USB cable + reinstalled USB drivers to latest + ODIN 3.10. And then... it worked. Instead of "fail" on "system.img" this time it showed progress on the "system" stage. After a while it DID finish with a "PASS".
Next boot I was told that "Device memory damaged" and asked to factory reset it. Which I did. Next boot - Booted the first run settings and the system... next boot - booted the "Black Edition" (with different boot animation sound and then theme) and it's working now fine O_O will proceed to root it and then take care of everything again discarding the old backups and backing up stuff again.
Hi! I have problem
I flashed official LOLLIPOP for N9005 from Poland and everything went okay.
Then I stupidly tried to install TWRP via Odin and it seemed it caused an issue. It must have been wrong TWRP.
Now everytime I want to turn on, the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
I tried to flash once again LOLLIPOP ROM but there is an error:
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea what can I do?
I don't know if I made a minor mistake or a major mistake. I was trying to flash U Firmware and downloaded and tried to flash G935UUEU2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT. I can't tell you for sure what it said because the post I was reading said if it fails, it's no big deal, try again a few times. After a few failed attempts, I realized there were tons of different versions.
I finally downloaded what I believe is the the correct one, G935VVRU4API3_CL8875708_QB11198937_REV02_user_low_ship_MULTI_CERT, but when I went to flash it, in red at the top it says
volume size is too big 1152000 < 1369600
Odin : invalid ext4 image
and in Odin, the end says
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any fixing this or am I royally screwed? When I restart the phone, a blue screen comes up and says
Software Update Failed
Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update. (I don't have a Verizon Software Repair Assistant).
I'll be honest, at this point I just want a functioning phone! haha Thanks for your help!
re: messed up phone
bmccartney2004 said:
I don't know if I made a minor mistake or a major mistake. I was trying to flash U Firmware and downloaded and tried to flash G935UUEU2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT. I can't tell you for sure what it said because the post I was reading said if it fails, it's no big deal, try again a few times. After a few failed attempts, I realized there were tons of different versions.
I finally downloaded what I believe is the the correct one, G935VVRU4API3_CL8875708_QB11198937_REV02_user_low_ship_MULTI_CERT, but when I went to flash it, in red at the top it says
volume size is too big 1152000 < 1369600
Odin : invalid ext4 image
and in Odin, the end says
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any fixing this or am I royally screwed? When I restart the phone, a blue screen comes up and says
Software Update Failed
Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update. (I don't have a Verizon Software Repair Assistant).
I'll be honest, at this point I just want a functioning phone! haha Thanks for your help!
Click to expand...
Click to collapse
You need to use Odin3 to flash the proper official samsung
firmware for your s7 or s7 edge phone model.
You can find and download the firmware from http://sammobile.com
After successfully flashing the phone using Odin3 your phone will be
just like new.
The mistake you made is a very small one, flashing the official firmware
takes less than 15 minutes.
Good luck, have a great day!
.
This happened to me on my galaxy tab s2, same error in Odin and same result. Good news is it is fixable. I have no idea why the error happened, I just tried a different firmware, and the second one worked.
Hello all.
I'm having multiple problems with my Note 4.
Model is SM-N910F and the problems are:
Does not boot to OS
OS Flash works but does not do final stuff on the phone
When installing OS, it will just spit out failed to mount /efc (Invalid argument)
Tried Kies recovery, that fails too
Custom recovery does not work.
Is it safe to say that this device is officially dead and i should get a new phone?
JantsoP said:
Hello all.
I'm having multiple problems with my Note 4.
Model is SM-N910F and the problems are:
Does not boot to OS
OS Flash works but does not do final stuff on the phone
When installing OS, it will just spit out failed to mount /efc (Invalid argument)
Tried Kies recovery, that fails too
Custom recovery does not work.
Is it safe to say that this device is officially dead and i should get a new phone?
Click to expand...
Click to collapse
Flash 4files repair firmware with PIT file then do factory reset.
Get from link below
https://www.androidfilehost.com/?fid=24407100847294341
Extract thr file you will get 5 files ( BL/AP/CP/CSC/PIT
)
UPLOAD ALL FILES IN ODIN CORRECTLY AND GO TO ODIN OPTIONS CHECK "NAND ERASEALL".
HIT START
ONCE ODIN SHOWS PASS GO TO STOCK RECOVERY MAKE FACTORY RESET THEN REBOOT.
If this does not work then your eMMc chip need to replace from motherboard.
Hope this will help.
Trex888 said:
Flash 4files repair firmware with PIT file then do factory reset.
Get from link below
https://www.androidfilehost.com/?fid=24407100847294341
Extract thr file you will get 5 files ( BL/AP/CP/CSC/PIT
)
UPLOAD ALL FILES IN ODIN CORRECTLY AND GO TO ODIN OPTIONS CHECK "NAND ERASEALL".
HIT START
ONCE ODIN SHOWS PASS GO TO STOCK RECOVERY MAKE FACTORY RESET THEN REBOOT.
If this does not work then your eMMc chip need to replace from motherboard.
Hope this will help.
Click to expand...
Click to collapse
Hey Trex888.
ODIN fails with this message:
Code:
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Write)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So the eMMc chip is dead and needs to be replaced?
JantsoP said:
Hey Trex888.
ODIN fails with this message:
Code:
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Write)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So the eMMc chip is dead and needs to be replaced?
Click to expand...
Click to collapse
Try odin version 3.10.
Try restart your pc.
Make sure all files inserted correctly in odin.
Try different usb cable.
Do a factory reset from recovery before start flashing.
Trex888 said:
Try odin version 3.10.
Try restart your pc.
Make sure all files inserted correctly in odin.
Try different usb cable.
Do a factory reset from recovery before start flashing.
Click to expand...
Click to collapse
Did all that and no joy. Anything else i could try or should i just give up and get a new one?
JantsoP said:
Did all that and no joy. Anything else i could try or should i just give up and get a new one?
Click to expand...
Click to collapse
This method sounds weird but give it a try not kidding i am serious
Put your phone in a plastic airpack bag in freezer without battery for 2 or 3 hours or better if whole night then take out immediately go to download mode and flash stock firmware.
Dozens of note 4 users ware able to recover by this crazy method You can read more about this down below.
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Trex888 said:
This method sounds weird but give it a try not kidding i am serious
Put your phone in a plastic airpack bag in freezer without battery for 2 or 3 hours or better if whole night then take out immediately go to download mode and flash stock firmware.
Dozens of note 4 users ware able to recover by this crazy method You can read more about this down below.
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
Click to expand...
Click to collapse
Now that sounds weird
Will try it