Database Users

Can't install anything with Odin

I never had problems with flashing new firmware. But yesterday I thought to flash the newest stock rom I9505XXUFNC4, and I got:
Nand write start!
Complete(Write) operation failed.
After that, I cannot boot anymore until I flash a Pit file. I also tried to install TWRP, CWM and the last rom. Nothing, nothing and nothing. Now my root is gone and my wifi doesn't work anymore.
I'm scared that when I factory reset the thing, that I can't install a new rom. Can someone 'please' advice me what to do? For example, can I install stock rom with ADB?

I would re-download the stock firmware and try again. Maybe try an older version
Sent from my SAMSUNG-SGH-I727

I downloaded it a few times. And the other version was working fine. But as you can read in my post: I can't install anything but the pit file.
Sent from my GT-I9505 using Tapatalk

choice2rejoice said:
I downloaded it a few times. And the other version was working fine. But as you can read in my post: I can't install anything but the pit file.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
So, it'll boot only of you flash the pit first in Odin?
Sent from my SAMSUNG-SGH-I727

When I try to flash something, I got that error. After that it's not booting anymore. 'Problem updating firmware' message. After flashing the pit, it's booting like normal.
I tried other USB ports and cable, as some people on the net ar suggesting, but that didn't worked.
Sent from my GT-I9505 using Tapatalk

choice2rejoice said:
When I try to flash something, I got that error. After that it's not booting anymore. 'Problem updating firmware' message. After flashing the pit, it's booting like normal.
I tried other USB ports and cable, as some people on the net ar suggesting, but that didn't worked.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'll have to say, I've never seen that before. I'm not sure what to tell you.
Sent from my SAMSUNG-SGH-I727

I guess that's why I can't find a solution
Sent from my GT-I9505 using Tapatalk

choice2rejoice said:
I guess that's why I can't find a solution
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Can you boot into recovery or download mode?
What recovery do you have installed?
I have a Galaxy S4 LTE-A E330SK and have had problems similar to that when trying to install an older firmware or same version on top of the version already on there. Recovery wouldn't boot, and if Android booted, everything would force close. (I like breaking my own phone just to see if I can fix it lol.)
Any time I had severe problems that would not enable me to boot or use Odin, I boot into Recovery, under Advanced, format System, Data, Cache, sdcard, media/sdcard and reboot. That erases everything (your operating system and everything on sdcard0) and if you are stuck on the Samsung Galaxy S4 logo, then you are good to go. Reboot into Download mode, connect your cable, and open Odin. (By the way I also found out you will get errors if you try to flash twice in a row without closing and reopening Odin, so keep that in mind.)
This I would consider a clean install of Android.
Now for the iffy part... Everybody says do NOT check the repartition box when you flash the new ROM. But what I do is make sure I have the correct PIT file for my firmware version. Add PIT file under PIT in Odin, add your firmware md5 file under PDA (or AP,) tick repartition, untick Auto-Reboot (my E330SK would automatically revert back to stock recovery with Auto-Reboot selected.) F Reset Time ticked, and Start. You should have no errors now.
There might be a better way without having to format those filesystems I've stated, but haven't found it. This way has always gotten me out of a sticky situation.
Keep in mind as well, I have never been able to downgrade to an older version of Android. So recommended if you try this do it with the same firmware or newer version that is currently on your phone.
---------- Post added 4th April 2014 at 12:02 AM ---------- Previous post was 3rd April 2014 at 11:56 PM ----------
choice2rejoice said:
I guess that's why I can't find a solution
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Might I mention I am using CWM Recovery as well

Yeah but I tried to install a new version and tried afterwards the current version on my phone. Tried as I already stated, several things to install and the only thing I could install, was the pit file.
Yesterday I installed CMW with Heimdall method. That worked. After that I install root from within CMW with ADB. And because I got an old backup, I didn't wanna go back that far and only flashed (with ADB) boot.img. Now I got a working phone.
I really want to update to latest firmware, but I'll try after the weekend. Don't want my weekend to be headached
Anyway. Thx for your response!
Sent from my GT-I9505 using Tapatalk

After trying and trying and trying, finally one of the USB ports let me push the new firmware (NC9) to my phone! (with Odin). After that my sd-card was unmounting itself all the time and giving errors as filesystem not recognized and being blank. Location methods didn't work correct etc.
Yesterday I managed to flash the NC4 firmware, and all is working well now!
Sent from my GT-I9505 using XDA Premium 4 mobile app

Device is bricked!!!!!

Please help! I'am using model SM-N900. Today, I wanted to downgrade from my 5.0 custom ROM to stock 4.4.2. I downloaded the 4.4.2 firmware and opened ODIN. I selected AP mode and selected the .tar.md5 file I extracted and it loaded it up. I booted the phone into download mode. I selected auto reboot and F. Reset time. I clicked start and it started. It went along well until it got to system.img in which it stopped and failed. Now I tried a lollipop image, and it came up with the same result. I tried flashing the TWRP image and it flashed successfully. I was able to boot into TWRP and use it. I now tried flashing a custom rom. I tried a AOSP lollipop rom, 5.0 TW rom, and a 4.4.2 TW rom and they all booted to a black screen. I'am now desperate to fix my seemingly bricked device so somebody out there, please help! Thanks in advance.

I also tried flashing a bootloader I found somewhere in XDA for the N900 and I'm still able to flash TWRP and use it and access download mode but it hasn't changed my problem.

justinxfan said:
I also tried flashing a bootloader I found somewhere in XDA for the N900 and I'm still able to flash TWRP and use it and access download mode but it hasn't changed my problem.
Click to expand...
Click to collapse
What bootloader was you using and what one have you tried to flash
Sent from my SM-N920F using Tapatalk

I'am not sure what bootloader I was trying to use before but I was on a custom lollipop TW rom so maybe its a lollipop bootloader? I flashed the one linked here: http://forum.xda-developers.com/galaxy-note-3/general/safe-to-downgrade-ll-to-kk-sm-n900-t3016966

UPDATE
TWRP factory reset and other wipe functions except cache wip are no longer working the wipe completes with a blue error. Was it because I accidentally checked nand erase all in TWRP?

justinxfan said:
UPDATE
TWRP factory reset and other wipe functions except cache wip are no longer working the wipe completes with a blue error. Was it because I accidentally checked nand erase all in TWRP?
Click to expand...
Click to collapse
Iv an idea you flashed wrong bootloader so I would download stock lollipop Rom no root make sure you flash bootloader and modem too so download to your pc and use Odin make sure you haven't enabled reactivation lock
Sent from my SM-N910F using Tapatalk
---------- Post added at 11:37 PM ---------- Previous post was at 11:25 PM ----------
justinxfan said:
UPDATE
TWRP factory reset and other wipe functions except cache wip are no longer working the wipe completes with a blue error. Was it because I accidentally checked nand erase all in TWRP?
Click to expand...
Click to collapse
If you tried to come From a lollipop bootloader back too kk I'm afraid new motherboard Is what your looking at
Sent from my SM-N910F using Tapatalk

Device has been fixed!!!!
YESSSSSSSS
I downloaded a pit file for my device and used it along with my kitkat firmware. This time, the flash succeeded and my device booted to a message saying data is corrupt. I did a factory reset from recovery and rebooted. The device successfully booted up and now I'm up and running again and downloading all my apps and stuff. No need to swap motherboard!

congratulations mate
justinxfan said:
YESSSSSSSS
I downloaded a pit file for my device and used it along with my kitkat firmware. This time, the flash succeeded and my device booted to a message saying data is corrupt. I did a factory reset from recovery and rebooted. The device successfully booted up and now I'm up and running again and downloading all my apps and stuff. No need to swap motherboard!
Click to expand...
Click to collapse
congratulations

justinxfan said:
YESSSSSSSS
I downloaded a pit file for my device and used it along with my kitkat firmware. This time, the flash succeeded and my device booted to a message saying data is corrupt. I did a factory reset from recovery and rebooted. The device successfully booted up and now I'm up and running again and downloading all my apps and stuff. No need to swap motherboard!
Click to expand...
Click to collapse
You had a result there
Sent from my SM-A800F using Tapatalk

What exactly does a pit file do though? When I selected it it selected the re-partition option which everybody says not to use but it was the only way my device is successfully up and running again. Why do you think flashing the .pit file along with my firmware file worked?

justinxfan said:
What exactly does a pit file do though? When I selected it it selected the re-partition option which everybody says not to use but it was the only way my device is successfully up and running again. Why do you think flashing the .pit file along with my firmware file worked?
Click to expand...
Click to collapse
basically a pit file increases partition size and as yours had corrupt data the system couldn't read or rite to it so pit file allowed you to install your rom I can't believe you got away with it normally bootloader doesn't forgive but glad you sorted things
Sent from my SM-A800F using Tapatalk

Thanks a lot!

S5 G900F ( Firmware upgrade Encountered an issue )

Hi, folks i tryed updating my rom yesterday with twrp recovery 2.8 and when i wiped cache etc... i wiped my system and now it say's i don't have a OS and when i try and flash with odin downgrading it says " EXT4 " error near the ned in odin. Any help would be appreciated. Thanks alot

asuncion66_66 said:
Hi, folks i tryed updating my rom yesterday with twrp recovery 2.8 and when i wiped cache etc... i wiped my system and now it say's i don't have a OS and when i try and flash with odin downgrading it says " EXT4 " error near the ned in odin. Any help would be appreciated. Thanks alot
Click to expand...
Click to collapse
((( When i start the phone normally i get ( Firmware upgrade encountered an issue ) i don't know what to do :/

Either flash a custom ROM from TWRP, or flash a stock ROM with ODIN & flash the PIT file with it

*Detection* said:
Either flash a custom ROM from TWRP, or flash a stock ROM with ODIN & flash the PIT file with it
Click to expand...
Click to collapse
Thanks for your reply! i have tryed flashing 2 or 3 roms with odin and all i get is ( EXT4 FAIL ) and on me phone screen not enough room or something! i can't get into twrp now all i get this the ( firmware upgrade encountered a issue :/ not sure what to do...

Did you flash the PIT file with the stock ROM in ODIN?

*Detection* said:
Did you flash the PIT file with the stock ROM in ODIN?
Click to expand...
Click to collapse
Yes i tryed do i need a certain pit file ? i'm based in the UK on network 02 please can you post me a link to a pit file and original stock rom for this phone thanks again.

The twrp say this because you clean system folder. To fix it, you need just download The official samsung rom.zip, put it in your sd card, and install normally with twrp.

PIT
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Get the stock ROM from sammobile . com
Go to the firmware section and search for G900F
Get the BTU version
---------- Post added at 14:01 ---------- Previous post was at 14:00 ----------
necromisty said:
The twrp say this because you clean system folder. To fix it, you need just download The official samsung rom.zip, put it in your sd card, and install normally with twrp.
Click to expand...
Click to collapse
No you don't, you can't flash stock ROMs with TWRP, you have to use ODIN

*Detection* said:
PIT
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Get the stock ROM from sammobile . com
Go to the firmware section and search for G900F
Get the BTU version
---------- Post added at 14:01 ---------- Previous post was at 14:00 ----------
No you don't, you can't flash stock ROMs with TWRP, you have to use ODIN
Click to expand...
Click to collapse
Thanks alot to the above users for helping e i will try this out and report back. You are so very kind.

Flash the PIT file and the stock ROM at the same time from ODIN

***SOLVED***
Thanks alot folks for your help i am now back on 4.4.2 kitkat but i lost everything. I can't thank you enough peeps on here.

Good stuff
Good idea to make a backup in TWRP before flashing anything custom next time, then you can always restore if you break it again

*Detection* said:
Good stuff
Good idea to make a backup in TWRP before flashing anything custom next time, then you can always restore if you break it again
Click to expand...
Click to collapse
Yeah i sure will this time around. Thanks for taking the time to help me.

No probs

hi i have the same problem but which stock rom do i use for my phone
Also in Odin do I put the pit file in the pit tab it warned me to not to

Soft Brick??

Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi

Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?

Same issue as well on my sm-g985v Verizon variant
Flashed an update to work out minor lagging bugs and soft bricked my S7. Can access bootloader and recovery. Beyond that, the phone gets there but with black screen and it is sputtering off and on. Tried reflashing stock firmware with odin, and its not taking. Running into a permission error while trying to write the image. Anyone here have any ideas?

sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Feyaad said:
Hi there, I have same issue, have s7 edge sm-G935F stuck at logo. I downloaded 2 different firmware from z3x box(shell) and if keep failing when using odin (latest) and also getting error when using Samsung tool.Also I can't get in the phone menu to check the baseband..can only get model from download model.any advice to this?
Click to expand...
Click to collapse
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?

LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-edge/development/recovery-official-twrp-hero2lte-3-0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
Click to expand...
Click to collapse
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...

sidi adam said:
Hello,
Thanks for your message. I tried everything you said exept that i used odin 3.12.5
But still the black screen...
Click to expand...
Click to collapse
What rom you tried to flash?
Are you on the right bootloader and modem?

Well I have the Odin latest version already..but I can't know which is the correct baseband or county..only the model I know when it's in download mode..

sidi adam said:
Hello all,
Today I updated a custom ROM on my rooted Phone (android 7) . In the aroma installer i select no root. After a good restart i though i root my Phone true Odin. I was thinking it went all good till it was stuck on te Galaxy s7 edge black screen. I couldnt do nothing. After that i was thinking to flash to stock. Every time i try to flash true Odin it give me fail.
Please help me.
Best regards Sidi
Click to expand...
Click to collapse
So you flashed a beta firmware, the name of which you don't feel is necessary information.
OK. Shame I hate popcorn. How about INFORMATION instead?!

LyLu said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...

I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc

Moodruid said:
It was my understanding it was already in the package. Questioning that one now. Where do i look for that? And thank you for responding back. Downloading your first suggestions as i type this...
Click to expand...
Click to collapse
When downloading original firmware there should be 4 files when unzip.
1 for each of the options in Odin, without the last one named home.
Some of the custom roms comes with bootloader and modem, but NOT ALL.
Most times you have to flash the right bootloader and modem in Odin beforehand to get the phone to boot.
Im unsure of what has happened because I have never run into issues myself.
If you can not get the phone to boot with firmware from Sammobile and Odin flash I am out of options.
If I do experience a problem like this I would:
-install bootloader and modem according to the custom rom used. Try and flash these with odin more than ones, if not working.
-if no recovery, try flash recovery again
-try flash another custom rom then another custom rom
-return to stock firmware downloaded trough Sammobile
If none of these options work im out of things to do, sorry
The times I have experienced phone stuck on Samsung logo, it has been because of bootloader and/or modem.
Flashing the right ones have always fixed the problem.
That said, I have never experienced problems with returning to stock firmware trough Odin, maybe one time.
And this time my firmware download was corrupted.
---------- Post added at 06:13 AM ---------- Previous post was at 06:00 AM ----------
sidi adam said:
I have downloaded two non branded firmware for the Netherlands from samdroid. I had unpacked the zip and flashed the files. For the csc selection I put the one named home csc
Click to expand...
Click to collapse
This is wrong, you should use the file named only CSC.
Home_CSC, is to keep your setup on phone as is.
I also remember that you have to remove the meta data directory, and then repack firmware or the install will stop.
And this is also NOT a good option if you use another firmware than the original on phone.
Installing firmware with Odin, always use BL, AP, CP and CSC.
Try this and forget about the Home_CSC.
I don't have anymore info, sorry

Thank you very much. I will try it. I will let you know.

Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,

Moodruid said:
Gentlemen, my appreciations and thanks. Was able to finally get the stock firmware to grab. After more time disecting the problem i learned about and was able to uncover the maintenance boot screen. There it had the option to do usb debug . Once i hit that, next flash finished fully. It must of reser in the dev options after the initial root. Damn, i was sweating balls for a bit thinking i must of hard bricked it somehow. I will take it throufh the toot process later today glitch free i imagine. Thanks again for assisting,
Click to expand...
Click to collapse
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work

LyLu said:
Usb debugging should always be turned ON when flashing..........!
Tis is like common knowledge in here.
Anyway glad things work
Click to expand...
Click to collapse
How will you get to turn on USB debugging when the phone can only booth into download model?

Feyaad said:
How will you get to turn on USB debugging when the phone can only booth into download model?
Click to expand...
Click to collapse
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button

LyLu said:
Buy pressing and holding power and volume down key, until you get to the screen.
Same procedure as download mode, but without the big button
Click to expand...
Click to collapse
OK great..will try it..thank you

luly said:
Is this a 935F? Where did you download the orginal firmware from and what version of Odin u use?
When I root my phone I always use the steps from this thread.
http://forum.xda-developers.com/s7-e...0-0-0-t3334084
Have never run into issues.
Flash twrp trough Odin first, let the phone start
Boot into TWRP, format phone with the options you have to type YES, then install dm-verity force encryption disabler
Now restart TWRP
Then flash the Supersu file from the thread.
Now restart phone
---------- Post added at 10:44 PM ---------- Previous post was at 10:42 PM ----------
Download orginal firmware fro sammobile, unpack and flash with Odin 3.12.3.
Download the firmware from your area, the one that comes with your phone.
Use the right regional code and everything when you download firmware.
Also, have you guys flashed the right bootloader and modem beforehand?
Click to expand...
Click to collapse
Even this thread is old:
Thank you so much, bricked my phone unknowingly flashing custom recovery using a defektive usb port struggling to get it working again. This worked like a charm.
Don´t understand why the orthers did struggle with that method.

how to back up system and efs partition? someone teach me please

please anyone teach how to back up system and efs, i dont wanna brick my other devices,so i need to learn this stuff
My reason:
ive bricked my s6 edge+ because of lossing efs partition, i always have the error
"E: Failed to mount efs (invalid argument)"
please anyone

https://forum.xda-developers.com/showthread.php?t=2508866

I have one question. Can I somehow root my phone when it boots only in recovery mode and efs partition is lost?

Kingkhone said:
I have one question. Can I somehow root my phone when it boots only in recovery mode and efs partition is lost?
Click to expand...
Click to collapse
maybe dude, try to download CF-auto root for your device

Root would be useful if the phone can boot the ROM; otherwise, root would not be useful without a working ROM.

audit13 said:
Root would be useful if the phone can boot the ROM; otherwise, root would not be useful without a working ROM.
Click to expand...
Click to collapse
Well first of all, I'm not a pro in these particular situations, but how should I fix this error? My phone wasn't rooted when I got this error. There is no OS in my phone and I cannot install any custom ROM because of this error. ODIN always fails, I tried to install ROM using TWRP, but I get the same error. I read almost every article in this website and tried a lot of methods, but none of these didn't help me. Is there any more way I can fix it?

What point does Odin fail at .Nand Write ??
Sent from my SM-N930F using XDA-Developers Legacy app

Almost every time it fails at hidden.img. I tried to fix that renaming "hidden.img" file to "hidden.img.tar", but it doesn't work.

Kingkhone said:
Almost every time it fails at hidden.img. I tried to fix that renaming "hidden.img" file to "hidden.img.tar", but it doesn't work.
Click to expand...
Click to collapse
try to unpack your md5 via 7zip or winrar or any other app in pc then remove the hidden.img then repack the others without the hidden.img then flash via odin. sorry for bad english, try to pm me for clearly explaination
what exactly is your model number? ill send you a file and try to flash it

My phone is Samsung Galaxy S6 SM-G920F. I'm a little bit confused now When I have deleted that hidden.img file and flashed the other ones, I get the other odin fail on recovery.img. Did I ruin my efs partition? If I did that, when I somehow boot my phone, will I loose my IMEI and I won't be able to use my wifi and the other stuff? Thank you for help.

This is not S6 forum you are in the wrong forum this is Note 3.
Sent from my SM-N930F using XDA-Developers Legacy app

i've pm you, but also try to visit this www.facebook.com/gsmserviceremote

JJEgan said:
This is not S6 forum you are in the wrong forum this is Note 3.
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Well, sorry about that, I saw that this article is new so you could help for both of us, because we are facing the same problem.