Hi
My phone is N910U and it's CSC code is BRI (Thailand)
I was waiting for lollipop update, but it seems that only some countries have received the update.
So I decided to chage CSC to whatever the New Zealand CSC is to get the official update.
My phone isn't rooted and it runs stock rom.
While I was trying to flash recovery.tar via odin, it shows an error:
<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> recovery.img
<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)
I used correct recovery file, and this happens when I want to flash autoroot too.
USB debugging on, download mode, stock USB cable, reinstalled driver
Does anyone know how to resolve this issue?
Also, can I just download New Zealand firmware and flash it via odin?
Will my phone not brick and be able to use it in the UK?
Any help would be very appreciated
EDIT: FIXED - Disable reactivation lock
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
absinthesummer said:
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
Click to expand...
Click to collapse
Thanks for your reply
the reactivation lock was enabled, so I disabled it. But it is still not working.
It shows slightly different error
<ID:0/005> Added!!
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I really have no idea what went wrong.
Do you have any clue?
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
absinthesummer said:
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried to root it first, and it gave me the same error(new one) as above.
I never had an issue when I was playing around with my SGS3 couple of years ago. Rooting, recovery, custom rom all flashed well via odin.
Any idea?
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
cosmostronomer said:
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
Click to expand...
Click to collapse
Very glad to hear it! That reactivation lock is the number one issue when odin fails (on this device anyway)
Related
Hello, I have tried updating my N9005 to the latest firmware 5.0 provided on Sammobile. After attempting to flash it via ODIN, the following error occurs:
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Retried this step several times, but i have received the same error.
Following a few instructions found on the XDA forums, I tried using PIT file in order to re-partition.
The phone now reboots but will not go past the first boot screen "Samsung Galaxy Note3 N9005".
I tried pulling out the battery and performing a factory reset (along with wiping caches), but the situation is still the same after rebooting the device.
Also I have noticed that upon accessing "recovery mode", a error stating " Failed to mount /system (Invalid argument)" error is displayed.
I'm pretty new at upgrading phones and I've bought this phone recently and was unaware of the consequences of flashing ROMS via Odin.
The initial fw. on the device was 4.4.2 Official Samsung. Is there any way that I can make the phone reboot normally with fw. 4.4.2? Or any other firmware for that matter?
Thanks in advance.
AndreiRonaldo said:
Thanks in advance.
Click to expand...
Click to collapse
Reflash the firmware again now via ODIN without the .pit file.
Joku1981 said:
Reflash the firmware again now via ODIN without the .pit file.
Click to expand...
Click to collapse
I've tried that several times without success. But the issue was fixed. Apparently the PIT file I was using did not match the ROM i was flashing. I just had to find a matching pair of both ROM and PIT and now I've successfully booted my device. Hope that this thread might help others in need for answers to similar questions.
Alright, this is taking alot more than i had expected, after finally managing to boot my device, I've noticed that flashed rom behaves awfully, my phone is stuttering, and i have no sound. Also, my IMEI is displayed as "Unknown" in the "Status'" section of the device's Settings. Any suggestion on how to fix this issue?
flash the stock the rom you have before
As the title says, I tried to downgrade from lollipop 5.0 to 4.2 because I've had several issues and I also wanted to get root. I think part of my mistake was I wiped data/factory reset before I flashed AP. Any help would be much appreciated, as I have been at this for the past five hours. I added some info below that might help below. Thanks
- I cannot boot into recovery and get the message (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again)
- CP is the only thing that will flash and CSC also fails
- model number is g900a AT&T
- I have used Odin 3.10.7 and 3.09, but no luck
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> persist.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk
Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies
VoltexYT said:
Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies
Click to expand...
Click to collapse
Kies and kies3 are both not recognizing my device. I heard it could be because of usb debugging, but I can't boot into my phone to check.
Allek84 said:
Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Both kies and kies3 are not recognizing my device.
Hello I recently rooted my phone on 5.1.1 (Lollipop) and everything went well no issues till last night when I tried to install xposed installer and ended up soft bricking (I think) my phone, where it will turn on to the samsung s6 edge + logo and just sit there and won't go any further. I found out how to flash to the original firmware using Odin 3.10.7 and with the stock firmware file.
now I put my phone into download mode and connect it to Odin, put the firmware file into the AP section and hit start.
Once I hit start I get a fail message and this :
<ID:0/003> Odin engine v(ID:3.1100)..
<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> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried different firmwares from different sites, different odin verions, USB ports please help
I tried uploading pictures and links to the firmware I used but apparently I need 10 posts before that so if you want to know anything else in order to help please ask.
am non rooted trying to flash a different firmware and I get the same. I remove the OEM lock but cannot flash anything
odin 3.10.7 works
You write SM-G925W8 that´s S6 Edge, not S6 Edge+!!! Try firmware for SM-G928W8!
Hello i have a problem with flashing anything with odin on my Samsung Galaxy S4 9505.
Whenever i try flashing ROM or recovery or whatever, it says this:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Also when i try to boot my phone normally or go to the recovery it says this:
"Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again."
I've downloaded Kies and tried to recover it but it says:
'GT-I9505' does not support initializing.
What i've tried so far:
flashing pit file with and without the rom.Tried multiple odin versions.Tried multiple rom versions.Tried flashing recovery CWM and TWRP.
Also the error i got "Firmware upgrade encountered an issue.Please select recovery mode in Kies & try again." was after i tried flashing official rom 4.4.2 downloaded form Sammobile(first i installed TWRP recovery wiped system data dalvic cache and booted in download mode ). I was previously using latest Android 5.0.1 official.
Is there any hope of unbricking my device?
Have you tried reinstalling your ADB driver?
Honestly, kies sucks. You don't need kies to have ADB driver installed. There is a package that install samsung drivers seperately.
Once you upgraded to a lollipop bootloader you can't just simply go back to a kitkat one. Samsung doesn't allow that.
Try using the back USB ports on your PC. Trust me, it can do wonders.
You could also try Heimdall.
well i think i've advanced abit now i get this:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
tried to reinstall the ADB driver and using the back ports.
Also is there any way to flash Official Samsung ROM true a custom recovery?Cuz i just managet to install TWRP recovery on it.
hollydamn i just tried flashing true odin Android 5.0.1 and it worked.But the wifi isn't working it just not letting me turn it on.
Why don't people understand when I say YOU CANNOT DOWNGRADE ?
i didn't downgrade it now i've installed 5.0.1.
simeon112 said:
i didn't downgrade it now i've installed 5.0.1.
Click to expand...
Click to collapse
Yes, but you tried to, even after I explicitly said you can't.
Your WiFi issues might be related to modem/kernel.
You could try flashing a different firmware.
I tied a differed one the wifi works now.Only when i turn on the mobile data and try to go to a random site it says Forbidden.I think i need to wait my carrier to send me the setting for the net...
Anyway THANK YOU very much!! <3
I have an i337m (North American version of s4) and you can downgrade from stock 5.01 to stock 4.4.2. I did this on 3 phones in order to use regionlockaway to sim unlock all three phones. Everything worked, including data and wifi.
I'd like to try a downgrade with a i9505 for curiosity sake but that particular model is not sold by carriers in Canada.
Good morning,
I purchased this phone a couple years ago specifically for being able to root and customize my phone, I wanted to go with Lineage OS, but wasn't available at the time so I went with Renovate. Last night I tried to move to Lineage but failed, in fact I couldn't install any custom firmware's even returning back to Renovate. In troubleshooting I reflashed a stock image back to the phone and now i'm back to stock and working, but when I try to flash TWRP I am unable to I am getting only stock firmwares are allowed, i'm thinking perhaps I flashed a locked stock firmware. Looking at the developer options OEM unlock is enabled. Any thoughts, or help pointing me to a stock firmware that I would be able to flash to TWRP with?
jleiss said:
Good morning,
I purchased this phone a couple years ago specifically for being able to root and customize my phone, I wanted to go with Lineage OS, but wasn't available at the time so I went with Renovate. Last night I tried to move to Lineage but failed, in fact I couldn't install any custom firmware's even returning back to Renovate. In troubleshooting I reflashed a stock image back to the phone and now i'm back to stock and working, but when I try to flash TWRP I am unable to I am getting only stock firmwares are allowed, i'm thinking perhaps I flashed a locked stock firmware. Looking at the developer options OEM unlock is enabled. Any thoughts, or help pointing me to a stock firmware that I would be able to flash to TWRP with?
Click to expand...
Click to collapse
The firmware has nothing to do with twrp so it's strange indeed. Can you get an Odin log from when you try to flash twrp? With this it's easier to identify why twrp won't flash.
callumbr1 said:
The firmware has nothing to do with twrp so it's strange indeed. Can you get an Odin log from when you try to flash twrp? With this it's easier to identify why twrp won't flash.
Click to expand...
Click to collapse
I'm hoping this is what you looking for, if not let me know how I can enable more logging
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 38 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<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> recovery.imghttps://mail.google.com/mail/u/0?ui=2&ik=059f10abc2&attid=0.1&permmsgid=msg-f:1637431265232865158&th=16b9530f6c52c786&view=att&disp=safe
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also included screen shot of developers options, and then what pops up on the screen after the flash.
https://hmp.me/cmul
https://hmp.me/cmuk
jleiss said:
I'm hoping this is what you looking for, if not let me know how I can enable more logging
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 38 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<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> recovery.imghttps://mail.google.com/mail/u/0?ui...865158&th=16b9530f6c52c786&view=att&disp=safe
<ID:0/006> RQT_CLOSE !!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also included screen shot of developers options, and then what pops up on the screen after the flash.
https://hmp.me/cmul
https://hmp.me/cmuk
Click to expand...
Click to collapse
Hmm the first screenshot, I've never seen before. Custom binary blocked due to remaining installment balance?! But from what I can see it maybe due to a network lock or OEM. Which stock firmware fo you have currently and what CSC?
callumbr1 said:
Hmm the first screenshot, I've never seen before. Custom binary blocked due to remaining installment balance?! But from what I can see it maybe due to a network lock or OEM. Which stock firmware fo you have currently and what CSC?
Click to expand...
Click to collapse
I'm back up and working thanks to @ZeroXO
I have the same problem, I cant root my Galaxy with TWRP, I have OEM botton ON but say when I try to flash TWRP custom bynary etc...
RMM STATE: NORMAL
KGSTATE : Checking
FRP LOCK: OFF
OEM LOCK: OFF
my CSC code is PCT Galaxy S8 SM-G950F Android Pie Security Patch 1 April 2019.
I want to root it with current Android Pie version, I try to Downgrade and i did it, but cant install TWRP.
Thanks in advance.