thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
I know that people don't need much of an incentive on these forums, but happy to even go as far as paying a reward to fix this
Only had the phone for a day...
I read about others that have bricked their new N3 trying to root it, and, losing their warranty in the process, (it's the first thing they check).
Seems as if most of the educated folks on this site are waiting for a safe procedure, (and I'm gonna follow their lead).
Good luck my friend, I hope you didn't ruin a $700 device :crying:
K, I had a similar problem. I accidently left KIES running in the background. Kies and ODIN don't play nice together. If you left Kies running it can cause havoc while trying to flash and seems to cause ODIN to fail no matter what version.
Thought I'd bricked my phone for a little while too...
amnesia said:
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
Click to expand...
Click to collapse
It's much more helpful when trying to troubleshoot the failure if you actually paste the full log from Odin. The "write protection enabled" thing is not part of the problem. That's bootloader protection and you want it on, because it protects you from flashing the wrong device bootloader and bricking your device.
If you can still get into download mode, you have nothing to worry about. In general, it's good to redownload the ROM again, make sure that it passes the md5 check, reboot, and reflash.
You don't have a brick. So you are lucky. Boot into download mode and flash N9005 ROM, preferably same one or later version.
Here - http://samsung-updates.com/device/?id=SM-N9005
Get for your region or any other one. Cheers!
And yh! UNINSTALL KIES! Leaving the drivers
Hi there,
This is what I get in Odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
thanks for that, I've gone ahead and downloaded the KSA version since I bought mine in Qatar and there was no Qatar ROM.
Just to be clear, what's the best way to flash it to my phone?
In my case I didn't have KIES running. I've also uninstalled it to be sure.
Kies seems to be useless since it doesn't event detect the note 3 as a supported device.
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Are you trying to Root ur phone or Flash Stock ROM?
Same problem.
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Sothai said:
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Click to expand...
Click to collapse
Are you running 4.4 or 4.3?
Which root method are you using?
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Sothai said:
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Click to expand...
Click to collapse
Download and extract this file and flash through included odin.
amnesia said:
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Click to expand...
Click to collapse
KSA has Jellybean 4.3 up to now that means u r trying to flash 4.3, before root process on which version u were, jelly bean or kitkat, I am not sure but your phone is seems to be for Singapore.
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Sothai said:
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Click to expand...
Click to collapse
It's about 20 meg in size. It contains odin and the cf auto root tar file.
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Sothai said:
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Click to expand...
Click to collapse
Yes use the one in the bundle.
Can you boot your phone in download mode though?
Related
Hi guys and girls,
I'm new to this forum and new-ish to flashing roms and rooting my phone (SGS4 i9505 jfltexx i9505xxUBMGA), so I apologize If I've posted this in the wrong thread for starters.
I've been jumping between Samsung's stock ROM and Cyanogenmod 10.1/10.2 ROMs.
I can't remember exactly what I did wrong for my phone to be soft bricked, but I can list a few possibles and my device information to see if anyone can spot the problem;
CF-AUTO-ROOT jflte-jfltexx-gti9505
CM-10.2 Nighty Jfltexx
GAPPS
openrecovery-twrp-2.6.3.1
recovery-clockwork 6.0.4.4
PhilZ Touch 5.18.9-i9505
Now when I try boot my device I get told to boot recovery mode in samsung kies .. Which I've tried but it doesn't bring up any device in the list. I've tried it whilst my phone is in download mode, recovery mode and where it displays I've got a firmware issue.
I've tried flashing new recovery files and also I tried flashing "XSS-I9505XXUBMGA-20130924140120.home.tar" via Odin.. All seems to fail
I'm running out of ideas and options and I'm not the wisest guy so if any of you criticize me for my poor knowledge It'll be pointless as I wouldn't be here writing this in the first place If I didn't know that already.
I've never had a problem flashing custom ROMs and recoverys before, this is the first time. I've not selected no stupid options in Odin such as Re-Partition. I stick to the Auto Reboot and occasionally the F. Reset Time. Every guide I look at tells me different.
Below is a list of my devices original stock details:
kernal version
3.4.0-1081224
[email protected] #1
build number
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
Any help, files, guides on how to solve this problem given to me would be VERY appreciated.
Also, I'm not sure if this is a kernal problem. But my battery has recently appeared to be draining rather quickly and It'll display "low battery" warnings at about 30% instead of the usual 14%. And It'll also shut down thinking its out of battery at about 16%, then I turn it back on and it says like 30%. Sometimes once its fully died, I place it on charge and after a matter of minutes it says its at 50%... I guess fully draining and leaving my battery on charge for 24 hours may fix that problem?
Please help!
EDIT: I think USB debugging is disabled, but I cannot get into my phone settings to enable it now?
My download mode screen says "Write protection: Enabled".
Just download stock firmware from sammobile and flash with Odin.
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Just download stock firmware from sammobile and flash with Odin.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I've looked on sammobile but there isn't a i9505xxubmga?
Ipasah said:
I've looked on sammobile but there isn't a i9505xxubmga?
Click to expand...
Click to collapse
here you go
http://www.sammobile.com/firmwares/1/?model=GT-I9505&pcode=BTU#firmware
Really do appreciate it - I'll get downloading that now and I'll let you know how it goes.
As for the debugging mode? Is there a way to enable USB debugging from recovery or download mode?
Also, can I only get xxumbga for my device? xxuemj7 and xxudmh8 are also being show in that link you sent me. Would they not work?
Ipasah said:
Really do appreciate it - I'll get downloading that now and I'll let you know how it goes.
As for the debugging mode? Is there a way to enable USB debugging from recovery or download mode?
Also, can I only get xxumbga for my device? xxuemj7 and xxudmh8 are also being show in that link you sent me. Would they not work?
Click to expand...
Click to collapse
no need to enable usb debugging to flash with odin.
mj7 and mh8 had a secured bootloader with knox (for more info read here), once flashed, you can not downgrade
samersh72 said:
no need to enable usb debugging to flash with odin.
mj7 and mh8 had a secured bootloader with knox (for more info read here), once flashed, you can not downgrade
Click to expand...
Click to collapse
Seems like my bootloader isn't knoxd yet, which i guess makes easier for me to resolve my softbrick problem.
Damn hotfile downloading at 200kb/s. Hopefully I'll have my phone fixed before tomorrow, kinda waiting on a phone call for a job interview lol.
I'm flashing the stock version to my phone now, and it appears to be stuck at the BOOT part.
It is a 2.4GB file though so I'll leave it doing it overnight I guess.
What I got so far:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMH1_I9505XXUBMGA_HOME.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> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
Click to expand...
Click to collapse
EDIT - Anyone got any idea how long this takes roughly? It's been stuck on BOOT for about an hour now.
My device displays this in the download mode whilst trying to flash this stock firmware.
ODIN MODE
Product name: GT-i9505
Current binary: Samsung official
System status: Custom
CSB-CONFIG-LSB:0x30
Write protection: Enabled
START [224,1440]
Click to expand...
Click to collapse
UPDATE: Tried flashing the stock firmware with two different versions of ODIN, in different USB slots, and they both failed with the same reason as before. Writing had failed. I'm running out of ideas and really hope I haven't permanently bricked my phone...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Bump - Need my phone fixing today really, considering anything as long as it works again.
Now it appears like I've got the knox warranty due to trying to fix my phone over Kies .... which failed -.-
Odin mode
Product name: GT-I9505
Current binary: Samsung official
System status: customer
Knox kernel lock: 0x0
Knox warranty void: 0x0
CSB-CONFIG-LSB:0x30
write protection: enabled
eMMC BURST MODE: enabled.
Click to expand...
Click to collapse
HELP ME
same ensingsb
I'm gonna try install this version from Samsung Kies off the Sammobile.com website now:
Model: GT-I9505
Country: United Kingdom
Version: Android 4.3
Changelist: 1765174
Build date: Tue, 15 Oct 2013 07:21:56 +0000
Product Code: BTU
PDA: I9505XXUEMJ7
CSC: I9505BTUEMJ8
MODEM: I9505XXUEMJ7
Click to expand...
Click to collapse
Appears to be my only remaining method of fixing my phone....
Even tried PIT file and re-partitioning now and STILL fail..
I know I shouldn't try things unless I'm 100% sure, but that's the best help I'm getting right now.
The internet has no answers for my problem, and it appears neither does the community of this forum.
One £400 house brick, ****ing brilliant stuff.
Ipasah said:
Even tried PIT file and re-partitioning now and STILL fail..
I know I shouldn't try things unless I'm 100% sure, but that's the best help I'm getting right now.
The internet has no answers for my problem, and it appears neither does the community of this forum.
One £400 house brick, ****ing brilliant stuff.
Click to expand...
Click to collapse
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
if not, flash a pre-rooted firmware http://forum.xda-developers.com/showthread.php?t=2250824
samersh72 said:
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
if not, flash a pre-rooted firmware http://forum.xda-developers.com/showthread.php?t=2250824
Click to expand...
Click to collapse
Tried all of those steps many times over.
Is there a point in trying to root my rom when my phone doesn't even get to the bootloader?
Soon as i turn it on i get told theres a firmware issue encountered. I can still get to download mode, but not recovery mode.
EDIT: I dont even know what ROM is on it right now, everything is a mystery to me now, I'm relying purely on the XDA communities help now. As far as I'm aware, I've got a brick.
Sorry I'm giving up trying to find an answer myself now.
If anyone out there actually knows how to fix it, please enlighten me as I haven't the foggiest.
I'll try include as much details as I can ..
Recovery mode doesn't work
Download mode does work
Soon as i turn the device on I get the "Encountered firmware issue" problem
I've tried using many different versions of Odin
I've tried using different USB ports
I've tried using a different USB cable
I've tried using a different PC
I've tried flashing all sorts of recoveries such as TWRP, CWM, PhilZ.
I've tried flashing all sorts of custom and STOCK ROMs
I've tried re-partitioning using a PIT file
Click to expand...
Click to collapse
I've tried EVERYTHING I can possibly think of..
The problem appears to be that my phone WONT let ANYTHING write to it.
Thus making it impossible to flash ANYTHING therefore leaving me stuck with a waste of metal and plastic.
I have the Samsung Galaxy S4 LTE i9505 Jfltexx .. Not sure what ROM is on it, not sure what Kernal, not sure what firmware .. I haven't a clue
Just help me dear god please.
Ipasah said:
Tried all of those steps many times over.
Is there a point in trying to root my rom when my phone doesn't even get to the bootloader?
Soon as i turn it on i get told theres a firmware issue encountered. I can still get to download mode, but not recovery mode.
EDIT: I dont even know what ROM is on it right now, everything is a mystery to me now, I'm relying purely on the XDA communities help now. As far as I'm aware, I've got a brick.
Click to expand...
Click to collapse
try to flash a pre-rooted firmware from the link i gave
samersh72 said:
try to flash a pre-rooted firmware from the link i gave
Click to expand...
Click to collapse
Not gonna lie, i'm not even sure which one I should be downloading from the link you provided.
I dont even know If my device is still under xxubmga or not anymore.
Now I get:
Odin Mode
Product name GT-i9505
current binary samsung official
system status custom
knox kernel lock 0x0
knox warranty void 0x0
csb-config-lsb 0x30
write protection enabled
emmc burst mode enabled
Click to expand...
Click to collapse
and now when odin fails it says
start [224,1440]
sw rev. check fail : fused : 3, binary : 1
Click to expand...
Click to collapse
Ipasah said:
Now I get:
and now when odin fails it says
Click to expand...
Click to collapse
hmmmm.... emmc burst!!!!
samersh72 said:
hmmmm.... emmc burst!!!!
Click to expand...
Click to collapse
If it helps, I couldn't care less about the warranty?
I'd just like my phone to work again, I don't care on what ROM whether it be custom or stock.
:crying::crying::crying: I can`t flash my S4 SGH-M919V with odin, i try to flash any firmware lollipop 5.0.1 of GT-I9505 that is the same thing and others firmwares of 4.4.4 of the same model but always send me FAIL abort the operation.
I don`t know why when I put my s4 in odin mode show this information in small letters:
ODIN MODE
PRODUCT NAME: SGH-M919V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
MMC BURTS MODE: Enabled
One question the last lines maybe is the problem write protection enabled or not? if is yes the problem how i can fix it for flash any firmware on my s4 thanks for your time (if this post is in the wrong section please change thanks again) i hope solutions XDA-Developers
http://forum.xda-developers.com/galaxy-s4-tmobile is where you need to go for issues with your device, as that forum has far more people familiar with your S4. This is the international S4 forum.
Now, regarding Odin, you should be using a recent version of Odin (current is 3.10), the original cable connected directly to the computer, not using a hub, and not have Kies running. You may also need Samsung's drivers if you haven't installed Kies or downloaded them from Samsung, so if you haven't already downloaded them, do so. That said, attempting to flash an I9505 ROM to your device is automatically going to fail. Odin verifies the model number and other parameters in the S4 before it allows a flash to proceed. Naturally, the model numbers don't match and thus flashing the ROM will not work.
Write protection and MMC bursts modes are supposed to be enabled, so you can eliminate that as a concern.
Thanks for your anwer bro but so to try install a firmware of the same model of mine and the same error
Post your Odin log, so we can see where it fails.
This is mi phone information: i have install Albe95 rom
AP:I9505XXUHOA7
CP:M919VVLUFNH3
CSC:I9505OXAHOA7
This is the Error with any versión of odin and any firmware stock forma this model or :
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUHOB7_I9505YXYHOB5_I9505XXUHOB7_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:17)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl1.mbn
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Any solution? Thank s
I read some post and say it that write protection is enable never can't flash any firm help
Seriously? After telling you that you cannot install an I9505 ROM on your device and explaining why you can't, you're still trying?
YOU CANNOT INSTALL AN I9505 ROM ON A T-MOBILE S4! All attempts to do so will automatically fail. The only stock ROMs that will work on your device are T-Mobile ROMs.
What part of the above do you not understand? Tell me now so I can dumb things down.
i m understand all above OK
this log show with any firmware for the phone or t-mobile firmware men i triying to install stock firmwares for my mobile ok and don`t work of any way but thanks for your time and help :good::good::good: i waiting for more solutions or i read the link than you put above
@LE_17: I apologize for snapping. However I thought I had made it reasonably clear that you could not install an I9505 ROM on your device. Apparently this wasn't the case. In any event, your ROM is here.
that s ok bro no problem
thank s for your time but the link of the firmware that you post i have in my PC downloaded and when i flash it send the same error i dont know why :crying::crying::crying:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Strephon Alkhalikoi said:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Click to expand...
Click to collapse
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Try to flash the latest version from here.
http://www.sammobile.com/firmwares/database/SGH-M919V/#firmware
if it fails, try different usb port and different usb cable.
Try using the latest version of Odin (v3.10.6) and see if you can flash the correct firmware for your rom.
http://forum.xda-developers.com/showthread.php?t=2711451
Try using a different USB port if its failing again and make sure your USB drivers are up to date
Ok man i try it thanks for your time and answer post the result
Lennyz1988 said:
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Click to expand...
Click to collapse
Well color me silly. I did miss that, and I'm sure the OP did too as he mentioned already having that ROM.
LE_17 said:
Ok man i try it thanks for your time and answer post the result
Click to expand...
Click to collapse
If you're trying to flash the official Lollipop update for the S4, use the Canadian version. I tried using the Rogers version (as Videotron uses Rogers' network) from SamMobile and it worked perfectly well. I was even able to change my CSC to Rogers and get the update through Kies.
Disclaimer: If you choose to try this, it is at your own risks. I cannot be held responsible if your phone gets damaged in any way nor can I guarantee the results.
No need for this anymore! The SGHM919V has gotten the Lollipop update this morning.
All,
I've spent the better part of the last two days trying with zero success to downgrade my Verizon Galaxy S4 SCH-I545 from 5.0.1 to 4.4.2. I've read dozens of pages on various forums, both on general instructions for the procedure as well as pages relating directly to the fault I'm seeing. In short, I get the Complete(Write) operation failed error in Odin. The reason I'm trying to do this is a general disappointment in Lollipop, it has slowed the phone down (I need to kill off all apps at least once a day just to keep performance up) and I've enjoyed none of the "benefits" of Lollipop on the phone. It's been so bad I've deliberately ignored all requests my Tab 4 makes to upgrade to Lollipop.
I've tried the firmware reflash using Odin 3.04 as well as 1.85. I've tried both versions on two different computers, one running Windows 7 Home, the other running XP. I've run them standard, and on Win7 as Administrator. Fresh reboots. The Win7 has Kies (not running) and the WinXP computer has never had Kies, just downloaded the current Samsung USB drivers. I've tried running two different firmwares downloaded from Sammobile, on each machine, with every combination I can think of. I'm using the factory USB cable plugged directly into the motherboard on each machine. I've varied the moment I plug the phone into the cable based on various recommendations, waiting until Odin is already running, or getting the phone in download mode first then plugging in, etc. I've also tried re-running the update again immediately on failure, and again after rebooting the phone back into Download mode, trying multiple times in a row without closing down Odin, and then alternately restarting everything after each failure. Basically I've tried pretty much everything I've read, and it feels like I'm following the rules of an old gypsy woman, if I update the phone at midnight while swinging a dead rooster over my head, standing on my left foot only, all will go ok. Only nothing goes ok.
This is the complete error I get in Odin 3.04:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The first four lines happen almost immediately. Then it seems to wait or hang for about 45 seconds (meanwhile one CPU maxes out), afterwards the rest of the lines pretty much spit out instantly. On the phone the display changes slightly, one little tick mark appears on the progress bar, then nothing else. The phone appears to be locked and needs a very long hold of the power button to shut off. These symptoms appear identical regardless of which computer I use, or which version of Odin I use, which makes me suspect the phone is the culprit rather than the software/hardware of either computer. I figure if I had, for example, a corrupted firmware file it would fail somewhere down the line in the install, or even after it's dumped the file to the phone.
One thing that worried me (and I NEVER found any mention of this in any directions) is the amount of available space on the phone. With the bloatware on the phone (7.07GB of "miscellaneous files"?!?) I only have 2.76GB free on the internal memory, and the firmware file is 2.4GB. I'm assuming that it all needs to copy to internal memory first. After my first failed attempts I checked space available and I had less than 2.4GB free. After clearing cache and a few apps I got it up to 2.76GB.
USB debugging is on, battery level is full or high on the phone, reactivation lock is off, the phone connects to either computer just fine and interfaces with Windows Explorer, I can see and access files on the phone via My Computer without any error.
I saw one page describing using Heimdall as a wholly different idea, it seemed MUCH more complex and my gut reaction is it looks like it would be easier to brick the phone. Is there some manual way I can dump the firmware to the phone and get it to read the file such that it doesn't require a computer?
Anything else to suggest? In general I still like the phone and don't have a great deal of interest in upgrading, but it's getting frustrating enough that I'm considering junking the phone.
Thanks in advance,
Ryan
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
GDReaper said:
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
Click to expand...
Click to collapse
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Diddler77 said:
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Click to expand...
Click to collapse
Got pissed and disconnected it after about 45 minutes. Switched to my desktop/Win7 machine. With the bigger monitor I could see that the whole time it was sitting on "Leave CS" it wasn't doing a thing, it now gave me the option to hit the 'Start' button at the bottom of the screen. I LOVE applications that don't let you resize to fit odd sized monitors (like my old Netbook).
So, I hit 'Start', and it pretty much immediately fails. Some of the error messages are differerent though, here's the whole thing:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I find most interesting is the 5th and 4th line from the bottom, Write start followed by FAIL! (Auth). I interpret it as Odin failed to get authorization from the phone to perform the write function. Any other ideas? Going to try Odin 3.10.6 next.
Diddler77 said:
Going to try Odin 3.10.6 next.
Click to expand...
Click to collapse
Yeah, same problems on both computers, both new versions of Odin. Did notice something this time around on the phone's screen that I hadn't noticed before, though it seems to happen in all versions of Odin. Two lines appear on the phone when I hit 'Start' in Odin:
START [224,1440]
SW. REV CHECK FAIL : FUSED : 8, BINARY : 6
The numbers after FUSED and BINARY are very difficult to read. Above is my best guess. Any of them may be a 0 or an 8.
Thanks!
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
GDReaper said:
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
Click to expand...
Click to collapse
That I have not tried. From what I gather I need a PIT file specific to the model. Any idea where I can get it? In terms of the end result, what's the difference between using the PIT and re-partitioning compared to what I've been trying? Like, why do both options exist?
Thanks!
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
GDReaper said:
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
Click to expand...
Click to collapse
Dont the firmwares originally come with pit files ?
Deathvirus said:
Dont the firmwares originally come with pit files ?
Click to expand...
Click to collapse
From what little I gather from the simple Odin instructions page, some firmwares are packaged with additional files. The two versions I've downloaded from sammobile for my device type only contained a single tar.md5 file when unzipped.
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader. The bootloader being locked is primarily designed to prevent root, but it also has the effect of preventing downgrades. If it didn't have that capability, users could simply flash a bootloader that could be compromised, obtain root, and remove the bloatware.
You posted your question in the International S4 forum, and international devices don't lock their bootloaders, which is why no one has really picked up on this until now. The only reason I picked up on the possibility of it being your bootloader is because I own an international device yet live in the US, so I'm acutely aware of the locked bootloaders foisted upon us by AT&T and Verizon.
It is my understanding that Odin fails after trying to flash aboot.mbn because the ROM being flashed has a bootloader that is older than the bootloader currently installed on the phone.
Some models of the s4, such as the Canadian version (sgh-i337m) can be flashed from stock LP to stock KK using Odin without issue.
You're right about the age of the bootloader being a reason why downgrading fails. You're also right that most devices can downgrade without issue. However, the OP's device is not one of them. He happens to have one of the models with a locked bootloader, and to the best of my recollection, the locked bootloader means you cannot downgrade, period.
Strephon Alkhalikoi said:
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader.
Click to expand...
Click to collapse
If this is true, I'm really ticked off. What a waste of time. You'd think that somewhere, on ANY of the forums and websites someone would have mentioned that my device is crippled in this manner. Every single site makes Odin sound like the silver bullet.
Why is there even firmware available for Verizon GS4's then?
Understand I'm not ungrateful for the advice, I do appreciate it. Just venting.
-sigh-
100% true, and it's not limited to Verizon either. AT&T also locks the bootloader. As to mentioning it, it likely is mentioned in the AT&T and Verizon S4 General forums, but you won't find that information here. As I mentioned, this is the International S4 forum, and we don't have locked bootloaders to deal with.
I know it sucks, but this is what we deal with in the US. That's why for my next device I went with a Nexus.
I don't have a PIT file for OF4 firmware on the SM-S975L (Straight Talk variant) so the downgrade failed as for OP, I'm stuck in download mode with a yellow triangle.
Yeah, Verizon released this phone to Straight Talk evidently. I'm locked tight and basically hard bricked. Wicked pissed, too. Since Kies says phone model not supported. CANNOT restore.
Nexus it probably is. This phone was a waste of money.
Or at least...that was until I found a hack that let me install the old Jellybean kernel! http://forum.xda-developers.com/gal...ariant-of4-t3279890/post64511525#post64511525
Only problem is, sure, you can get your kitkat kernel back, but I wasn't successful probably because NB1 firmware was Verizon firmware at the time of my flash so my CSC didn't work, but since they're both JellyBean I got root. But as long as they're the same carrier my hack should work. Link me your firmware, I can let you try. It'll trip the hell out of KNOX though. I used Odin 3.07. It requires some by-hand hex editing. When you gain root you can disable Knox to flash other things with SuperSU.
@LupineDream: Of course you weren't successful in changing kernels. The SM-S975L is not a CDMA (i.e. Verizon) phone, but uses T-Mobile towers. The SCH-R970G is the other Straight Talk S4 and it used Sprint as a carrier. Verizon does not allow MVNOs access to their LTE network, which is how you can tell that you're NOT on Verizon.
The bootloader on Straight Talk S4 devices is not locked down like the OP's bootloader. Otherwise it would not be possible to install custom ROMs to the device. I have a distinct feeling that your hack will not work. Not because it's incorrect as you clearly had success, but because of the locked bootloader on the device, which is designed to prevent the very thing you successfully accomplished on your Straight Talk device.
To restore your phone to working condition, download the S975L firmware from sammobile and flash it through the BL slot in Odin. Then sell it and get a Nexus.
Hey, if I found a workaround for obtaining root on the ATT variant, users of that phone now have an fstab and an (almost complete) list of partitions and mount points for a device tree. So I hope that information at least made their lives better. In knowing they can indeed flash a kernel with said workaround. The device list, fstab, and mount points are all in my root guide now. Since after reflashing the boot image by itself the device boots again and has maintained root status, though with broken WiFi which can be fixed with a custom kernel. Oh well, at least users of my phone get a custom ROM., at least if you've got the ATT variant. All the info is in my thread for ATT variants. I' don't have my stock kernel, however. But it isn't an issue as for what I've provided, I think its enough to get a custom one for the ATT variants. Still going to sell and get my Nexus. But left it with a bang I suppose. I'll hack a locked bootloader until I'm blue in the face if it means I got root. You are indeed right, though. It isn't for ME to keep around, but please note that before I was even able to flash a kernel, I had to hack it. It was displaying secure boot status and would not allow flashing of anything. I was told they where all locked. I was never able to root OF4 before because of "locked conditions" where NB1 refused to flash before my hack.
I'm going shopping soon. Maybe I'll get the Verizon variant on the side to see if I can force my way in through another one of these types of loopholes. After all, my device would not flash a kernel before I did what I did to it...I was able to disable knox and allow kernel flashing by doing so. Through SuperSU. That bit was set before I did what I did to the device. All it takes is flashing of the NB1 kernel to Verizon through tricking knox it's official firmware and enough know-how to get the system to boot well enough to be able to inject root.
My device still won't flash non-official firmware or recovery. Because of a verification check in the kernel. I tried. Sig fai on kernel. But, now that Knox can be disabled, all it takes is an if/of dd flash of modified aboot in adb and then anything is possible at that point. I looked into loki_tool for always passing signature check passed to hardware knox. And clearing out EERAM before knox gets a chance to react. Loki'fied aboots satisfy knox pretty well I'd say.
The ROM displayed there iis for the Verizon variant by the way. I found Verizon-related apks in system.img.ext4. Even without the modem, it still won't flash. Have a download, rename it, extract the tar and hex edit look through the file. Yep, that's a verizon variant ROM.
One question, however, is does hardware knox do a checksum on aboot? That would pretty much make this argument a moot point.
Ask Chainfire. He needed to know about how Knox functioned so he could get SuperSU to disable it.
Recently I have received Galaxy S5 from my friend. It's model name as SM-G900F under battery. Have Single sim port and one imei. But when I switch on starting with "Samsung Galaxy S5 Duos" logo and started normally. After that when check the product details on "About Device", Product Name as SM-G900FD. But there's no two sim slots. and also showing two imei's when dial *#06#. Seems to be someone has done something. So now I want to take it back to original situation. Is it possible? Needs to convert G900F. Please if some one can help me. :crying:
eranda84 said:
Recently I have received Galaxy S5 from my friend. It's model name as SM-G900F under battery. Have Single sim port and one imei. But when I switch on starting with "Samsung Galaxy S5 Duos" logo and started normally. After that when check the product details on "About Device", Product Name as SM-G900FD. But there's no two sim slots. and also showing two imei's when dial *#06#. Seems to be someone has done something. So now I want to take it back to original situation. Is it possible? Needs to convert G900F. Please if some one can help me. :crying:
Click to expand...
Click to collapse
u can make it over Kies with Firmware Update and Initialization u need the model nr and the seriel nr there .. That i would do but if u not want kies u can also flash a stock G900f rom with odin .. b4 conect make phone off and remove battery for 10 sec .. then insert and go to download mode and flash the rom with odin
4Smoky said:
u can make it over Kies with Firmware Update and Initialization u need the model nr and the seriel nr there .. That i would do but if u not want kies u can also flash a stock G900f rom with odin .. b4 conect make phone off and remove battery for 10 sec .. then insert and go to download mode and flash the rom with odin
Click to expand...
Click to collapse
Thank you for valuable reply. I didn't try yet first step. But I tried second. This is I got error message.
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please Please help me
I tried here flash Android 6. But my mobile currently run Android 5. So do I wanna flash Similar rom?
eranda84 said:
Thank you for valuable reply. I didn't try yet first step. But I tried second. This is I got error message.
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please Please help me
I tried here flash Android 6. But my mobile currently run Android 5. So do I wanna flash Similar rom?
Click to expand...
Click to collapse
lol some think is not normal
what is written in download mode !!!
ty to flash 900f with another stock rom ( if no work ty with to change pit to successful )
popmpopm said:
lol some think is not normal
what is written in download mode !!!
ty to flash 900f with another stock rom ( if no work ty with to change pit to successful )
Click to expand...
Click to collapse
if you don't mind can you get me steps? Which region pt file? (KLTE_EURO_OPEN?)
No help?
Boot into download mode (Volume Down & Home & Power)
See which model it says there, that is the model you can trust
*Detection* said:
Boot into download mode (Volume Down & Home & Power)
See which model it says there, that is the model you can trust
Click to expand...
Click to collapse
It's G900FD. But this is only have single sim slot. And behind the battery compartment it says 900F.
So seems to be this is modified.:crying::crying:
if anyone can help me i'll help him / her to buy a beer
Use Kies 3
eranda84 said:
if anyone can help me i'll help him / her to buy a beer
Click to expand...
Click to collapse
Im also a G900F owner and I've been in a similiar situation. Download and install Samsung Kies 3(if you hadn't yet), just as the first reply said. On your S5, enter the Download/Odine mode by pressing VolDown+Home+Power Button and connect to PC with your USB. Open Kies 3, go Tools>Firmware upgrade and initialization. In the pop-up windows enter your model name, in your case I suppose its SM-G900F. You'll be asked for the serial number of your phone which is underneath the battery. Its written something like S/N: .... If correct, Kies will start downloading the correct firmware. The process is pretty much automatical, so just wait
After it is done, remove the USB, and the phone will (hopefully) reboot into latest stock version.
eranda84 said:
It's G900FD. But this is only have single sim slot. And behind the battery compartment it says 900F.
So seems to be this is modified.:crying::crying:
Click to expand...
Click to collapse
Forget stickers and firmware model numbers, they can all be modified to look like a different model, usually G900F
If your phone says G900FD in download mode, then your phone is G900FD, or at least the board is
*Detection* said:
Forget stickers and firmware model numbers, they can all be modified to look like a different model, usually G900F
If your phone says G900FD in download mode, then your phone is G900FD, or at least the board is
Click to expand...
Click to collapse
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
heisenberg281 said:
Im also a G900F owner and I've been in a similiar situation. Download and install Samsung Kies 3(if you hadn't yet), just as the first reply said. On your S5, enter the Download/Odine mode by pressing VolDown+Home+Power Button and connect to PC with your USB. Open Kies 3, go Tools>Firmware upgrade and initialization. In the pop-up windows enter your model name, in your case I suppose its SM-G900F. You'll be asked for the serial number of your phone which is underneath the battery. Its written something like S/N: .... If correct, Kies will start downloading the correct firmware. The process is pretty much automatical, so just wait
After it is done, remove the USB, and the phone will (hopefully) reboot into latest stock version.
Click to expand...
Click to collapse
Hey man, this is pretty cool until it's started installed to mobile, but it's not continue. Because below error message appeared on mobile with red letters.
"secure check fail : pit" what should I do now? Please need assistance. :good:
keithross39 said:
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
@ *keithross39* hey sir, please help me on this.... :crying::crying::crying:
There are only three things we can be sure of right now.
1) It's not the FD variant simply because of the lack of a second sim slot.
2) It's not the H variant because the H variant wouldn't run the FD firmware.
3) Your device is ONE of the Qualcom quad core single sim variants.
Now....Here's the tricky part. You say your device has 2 imei numbers.....If you start flashing firmwares that are written to work with a single sim card, one of those IMEI numbers is probably going to get deleted.....If it's the wrong one, you're well and truly stuffed. So you need to find a way to back them up.
Most IMEI/EFS backup utilities require root access.
For now, you're going to have to treat your phone as if it actually *IS* the FD variant and find a root method that works on that variant.
Then once you have root, you can make that all important IMEI/EFS backup.
Once you have that, *then and only then* will it be time to think about how to return the OS to a single sim configuration.
Edit.....
This thread.....
http://forum.xda-developers.com/showthread.php?t=2829293
Gives info about rooting. But beware, if you haven't already done so, rooting will trip KNOX which will torpedo any idea of warranty repair.....
Edit 2....
This should help with the IMEI/EFS backup.....
http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325
(It works on my 900F)
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
There are only three things we can be sure of right now.
1) It's not the FD variant simply because of the lack of a second sim slot.
2) It's not the H variant because the H variant wouldn't run the FD firmware.
3) Your device is ONE of the Qualcom quad core single sim variants.
Now....Here's the tricky part. You say your device has 2 imei numbers.....If you start flashing firmwares that are written to work with a single sim card, one of those IMEI numbers is probably going to get deleted.....If it's the wrong one, you're well and truly stuffed. So you need to find a way to back them up.
Most IMEI/EFS backup utilities require root access.
For now, you're going to have to treat your phone as if it actually *IS* the FD variant and find a root method that works on that variant.
Then once you have root, you can make that all important IMEI/EFS backup.
Once you have that, *then and only then* will it be time to think about how to return the OS to a single sim configuration.
Edit.....
This thread.....
http://forum.xda-developers.com/showthread.php?t=2829293
Gives info about rooting. But beware, if you haven't already done so, rooting will trip KNOX which will torpedo any idea of warranty repair.....
Edit 2....
This should help with the IMEI/EFS backup.....
http://forum.xda-developers.com/galaxy-s3/development/efs-samsung-tool-universal-support-t2602325
(It works on my 900F)
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
1) Yes. That's pretty sure me too.
2) Not a H variant
3) Yes.
As I mentioned first post there's two IMEI numbers. But none of those not similar to sticker under battery compartment. (Not match with any of those)
I have rooted mobile using "CF-Auto-Root-klte-klteduosxx-smg900fd". And it's successfully rooted.
And I did IMEI/EFS backup using "Samsung Tool". Now what should I do as a next step?
First thing to do is copy that backup 'off device'......If you have a removable micro sd card, copy it to that.....If not copy it to your pc or even cloud storage.....it's no good having a backup stored in device if the in device storage is formatted in my next suggestion......which is to flash not only a firmware, but a pit file too. I'd suggest using sammobile or samsung updates for the 900F firmware (the F variant firmware is as good a place to start as any) and the resources of XDA to locate the correct pit file. You can check here for pit files.....
S5 pit files (3rd post)
http://forum.xda-developers.com/showthread.php?t=2737448
But as it is now 3.52 AM where I am, I'm going to bed.....My kids will be up in about 4 hours so I need to get *some* sleep.....lol
Final edit for tonight......
As an alternative, you could forget about a firmware entirely, and go the custom rom route......just a thought.....
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
First thing to do is copy that backup 'off device'......If you have a removable micro sd card, copy it to that.....If not copy it to your pc or even cloud storage.....it's no good having a backup stored in device if the in device storage is formatted in my next suggestion......which is to flash not only a firmware, but a pit file too. I'd suggest using sammobile or samsung updates for the 900F firmware (the F variant firmware is as good a place to start as any) and the resources of XDA to locate the correct pit file. You can check here for pit files.....
S5 pit files (3rd post)
http://forum.xda-developers.com/showthread.php?t=2737448
But as it is now 3.52 AM where I am, I'm going to bed.....My kids will be up in about 4 hours so I need to get *some* sleep.....lol
Final edit for tonight......
As an alternative, you could forget about a firmware entirely, and go the custom rom route......just a thought.....
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Ok thank you sir and Hats off. :good:
Have a Good Night
I have tried everything but again failed in Re-partition. Now only one left. That's run a custom rom. Will see CM13 and back to stock rom.
But anyone can help me on pit file failed, please help me.
keithross39 said:
@*Detection* if it was hardware wise an FD it'd have 2 physical sim card slots, the OP says there is only one. In this case, download mode is wrong.....there's something else going on here. And before the OP does *anything* else I'd advise him to back up his IMEI/EFS folder, I've a feeling it's gonna be *critically important* that he does this......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Never to date have we seen or heard of download mode being wrong, and CF AR for the G900FD just worked for OP
And if it turns out to be wrong, we both have a LOT of threads to edit when we have told other members to always trust download mode
To my knowledge, there is no way to reprogram the chip on the board to change the model number in download mode, maybe the phone is a fake
@ OP - can you post a photo of the back of the phone, with the back cover removed, so we can see the physical location of the SIM slot?
Edit out the IMEI etc if it shows on a sticker
Before I start my explanation, this phone is NOT rooted and never has been (every article I have found so far relates to the phone being rooted)
I have a N910F Galaxy Note 4 mobile phone. Until yesterday morning it worked fine when I started experiencing major lag up until the point where the phone would become unresponsive. To get the phone to work again I had to take the battery out and put it back in 4/5 times before the phone would come back on but after a few minutes the lag returned. Then after it had happened a few times the phone restarted itself and went into download mode with two messages in the top left corner, one reading 'could not do normal boot' and the other 'ddi: mmc_read failed'. After taking the battery out again I got the phone to boot normally again but the lagging and freezing kept happening. I downloaded the stock firmware from sam mobile overnight and tried to flash it using Odin but got a 'failed' message immediately after starting the process.
I then used Samsung Kies to download and reinstall Touchwiz. I thought I had solved the problem but it has not, I barely got through the initial setup before the lag started again. I booted into recovery mode and noticed a red message at the bottom reading 'dm_verify verification failed'. I decided to reboot the phone but it has now restarted itself back into download mode with the mmc_read error message again.
Can any of the wise people on here help me out? As previously mentioned this phone has never been rooted (KNOX warranty 0x0) and until yesterday it functioned perfectly fine. I've spent the last 24 hours searching the internet with the hope that I wouldn't have to reach out for help but found nothing that could help
neils0911 said:
Before I start my explanation, this phone is NOT rooted and never has been (every article I have found so far relates to the phone being rooted)
I have a N910F Galaxy Note 4 mobile phone. Until yesterday morning it worked fine when I started experiencing major lag up until the point where the phone would become unresponsive. To get the phone to work again I had to take the battery out and put it back in 4/5 times before the phone would come back on but after a few minutes the lag returned. Then after it had happened a few times the phone restarted itself and went into download mode with two messages in the top left corner, one reading 'could not do normal boot' and the other 'ddi: mmc_read failed'. After taking the battery out again I got the phone to boot normally again but the lagging and freezing kept happening. I downloaded the stock firmware from sam mobile overnight and tried to flash it using Odin but got a 'failed' message immediately after starting the process.
I then used Samsung Kies to download and reinstall Touchwiz. I thought I had solved the problem but it has not, I barely got through the initial setup before the lag started again. I booted into recovery mode and noticed a red message at the bottom reading 'dm_verify verification failed'. I decided to reboot the phone but it has now restarted itself back into download mode with the mmc_read error message again.
Can any of the wise people on here help me out? As previously mentioned this phone has never been rooted (KNOX warranty 0x0) and until yesterday it functioned perfectly fine. I've spent the last 24 hours searching the internet with the hope that I wouldn't have to reach out for help but found nothing that could help
Click to expand...
Click to collapse
Is your phone still under warranty?
Sent from my SM-N910G using Tapatalk
neils0911 said:
Before I start my explanation, this phone is NOT rooted and never has been (every article I have found so far relates to the phone being rooted)
I have a N910F Galaxy Note 4 mobile phone. Until yesterday morning it worked fine when I started experiencing major lag up until the point where the phone would become unresponsive. To get the phone to work again I had to take the battery out and put it back in 4/5 times before the phone would come back on but after a few minutes the lag returned. Then after it had happened a few times the phone restarted itself and went into download mode with two messages in the top left corner, one reading 'could not do normal boot' and the other 'ddi: mmc_read failed'. After taking the battery out again I got the phone to boot normally again but the lagging and freezing kept happening. I downloaded the stock firmware from sam mobile overnight and tried to flash it using Odin but got a 'failed' message immediately after starting the process.
I then used Samsung Kies to download and reinstall Touchwiz. I thought I had solved the problem but it has not, I barely got through the initial setup before the lag started again. I booted into recovery mode and noticed a red message at the bottom reading 'dm_verify verification failed'. I decided to reboot the phone but it has now restarted itself back into download mode with the mmc_read error message again.
Can any of the wise people on here help me out? As previously mentioned this phone has never been rooted (KNOX warranty 0x0) and until yesterday it functioned perfectly fine. I've spent the last 24 hours searching the internet with the hope that I wouldn't have to reach out for help but found nothing that could help
Click to expand...
Click to collapse
Welcome to XDA!. Hope this helps, let the forum know one way or other. Gl https://forum.xda-developers.com/showpost.php?p=70652492&postcount=10
hello pls help
[/PHP]hello my name is salem i have galaxy note 4 n910f n my phone get masseges error n then i flash new room from odin but the rrom not work n when i open download manger there is masseges that mmc read failde
n when i need to install any room in odin type me this
ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXS1DPC2_N910FOXA1DPB5_N910FXXU1DPB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
after that i put the pit file n the same
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Removed!!
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
pleas help me pls :crying::crying::crying::crying::crying::crying::crying:
Amar.B said:
Is your phone still under warranty?
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
No unfortunately it isn't. I'll have to approach Samsung for help if I can't figure it out but they will charge me for the repair.
neils0911 said:
No unfortunately it isn't. I'll have to approach Samsung for help if I can't figure it out but they will charge me for the repair.
Click to expand...
Click to collapse
Yeah you will pay fees for the entire motherboard plus service .. there's workground for this problem in general fourms..
Found it
https://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
Sent from my SM-N910G using Tapatalk
Amar.B said:
Yeah you will pay fees for the entire motherboard plus service .. there's workground for this problem in general fourms..
Found it
https://forum.xda-developers.com/note-4/general/emmc-bug-fix-tried-sm-n910g-sm-n910p-sm-t3468721
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice I may try this method, I'm just not sure it would work as Odin instantly failed when I tried using it the first time. I just can't help thinking that one error is causing the other so I'm not which one I should actually be trying to fix. I even saw a video on YouTube that claimed that one of the errors is a hardware fault with the charging flex cable inside the phone. Who knows he may be right.
Thanks again I might try odin again but if it fails again I will have to restore Touchwiz via Samsung Keis again just to get the phone into a bootable state
neils0911 said:
Thanks for the advice I may try this method, I'm just not sure it would work as Odin instantly failed when I tried using it the first time. I just can't help thinking that one error is causing the other so I'm not which one I should actually be trying to fix. I even saw a video on YouTube that claimed that one of the errors is a hardware fault with the charging flex cable inside the phone. Who knows he may be right.
Thanks again I might try odin again but if it fails again I will have to restore Touchwiz via Samsung Keis again just to get the phone into a bootable state
Click to expand...
Click to collapse
Download repair firmware for your model from www.tsar3000.com this repair firmware comes with pit file.
Before flashing firmware put your device in freezer without battery for atleast 1 hour.i know it sounds crazy but it really solve the issue.
Flash firmware and do factory reset from stock revovery and your device will be completely fine.
Trex888 said:
Download repair firmware for your model from www.tsar3000.com this repair firmware comes with pit file.
Before flashing firmware put your device in freezer without battery for atleast 1 hour.i know it sounds crazy but it really solve the issue.
Flash firmware and do factory reset from stock revovery and your device will be completely fine.
Click to expand...
Click to collapse
That is a strange one but I'll give anything a go, i'll try this method when I get home from work today...if you don't mind me asking why place the phone in the freezer? and do you know what causes these issues?
neils0911 said:
That is a strange one but I'll give anything a go, i'll try this method when I get home from work today...if you don't mind me asking why place the phone in the freezer? and do you know what causes these issues?
Click to expand...
Click to collapse
Motherboard sometimes acting crazy because note 4 has heating issues all the time because of 1440p 2k screen with old snapdragon 805 processor.i am not exactly sure why it works when put in freezer but many users successful with this even they fix their hard bricked devices and emmc_fail devices.
So give it a try and be patiant.tty this again and again when you have enough time once it wotks do a factory reset from recovery and your device will be normal.
Ok there seems to be quite a few new threads regarding this issue in the last few days. I'm downloading the repair firmware now from the website you recommended so i'm going to put my phone in the freezer once it has finished
Trex888 said:
Motherboard sometimes acting crazy because note 4 has heating issues all the time because of 1440p 2k screen with old snapdragon 805 processor.i am not exactly sure why it works when put in freezer but many users successful with this even they fix their hard bricked devices and emmc_fail devices.
So give it a try and be patiant.tty this again and again when you have enough time once it wotks do a factory reset from recovery and your device will be normal.
Click to expand...
Click to collapse
Sorry noob question here, do I not flash the PIT file? I've only ever used Odin to root phones before or flash full a full 'all in one' firmware file
neils0911 said:
Sorry noob question here, do I not flash the PIT file? I've only ever used Odin to root phones before or flash full a full 'all in one' firmware file
Click to expand...
Click to collapse
You have to load pit file along with firmware same time together you cannot flash pit file alone.
In odin there is PIT tab click on it and upload pit file then go to odin options check "nand eraseall" then upload firmware AP tab after that go to device download mode and connect device to pc viab usb cable and HIT START IN ODIN.
once odin pass go to stock revovery and wipe cache wipe data factory reset.
That all you have to do.
Trex888 said:
You have to load pit file along with firmware same time together you cannot flash pit file alone.
In odin there is PIT tab click on it and upload pit file then go to odin options check "nand eraseall" then upload firmware AP tab after that go to device download mode and connect device to pc viab usb cable and HIT START IN ODIN.
once odin pass go to stock revovery and wipe cache wipe data factory reset.
That all you have to do.
Click to expand...
Click to collapse
What about BL, CSC and CP files? Do I need to put those in or just the AP? Ive put the pit file into that tab
neils0911 said:
What about BL, CSC and CP files? Do I need to put those in or just the AP? Ive put the pit file into that tab
Click to expand...
Click to collapse
Looks like you have 4 files repair firmware.
In odin load each file saprately
Load BL,AP,CP,CSC, all 1 by 1 and for PIT there is a tab on top PIT file you can load.
Trex888 said:
Looks like you have 4 files repair firmware.
In odin load each file saprately
Load BL,AP,CP,CSC, all 1 by 1 and for PIT there is a tab on top PIT file you can load.
Click to expand...
Click to collapse
Yeah I have all of them as it was one zip file from the website. Sorry to bother you again
neils0911 said:
Yeah I have all of them as it was one zip file from the website. Sorry to bother you again
Click to expand...
Click to collapse
It failed this was the bottom log from from odin:
<ID:0/003> Now Writing.. Please wait about 2 minutes
<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)
neils0911 said:
Ok there seems to be quite a few new threads regarding this issue in the last few days. I'm downloading the repair firmware now from the website you recommended so i'm going to put my phone in the freezer once it has finished
Click to expand...
Click to collapse
Try post #3, it did worked for me.
mangui said:
Try post #3, it did worked for me.
Click to expand...
Click to collapse
I'll give it a go but it sounds like the same process I've now done twice using Keis. It allows the firmware to reinstall but then the lagging/error messages continue. I'll try it anyway though, thanks
neils0911 said:
I'll give it a go but it sounds like the same process I've now done twice using Keis. It allows the firmware to reinstall but then the lagging/error messages continue. I'll try it anyway though, thanks
Click to expand...
Click to collapse
Well, it worked for me when Odin failed. Unless you actually have harware damage there should be a way to recover. GL