Related
I tried to install the N9005XXUENA6 firmware using odin and this happened:
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
And now it's stuck on odin mode, please help!
arboy2 said:
I tried to install the N9005XXUENA6 firmware using odin and this happened:
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
And now it's stuck on odin mode, please help!
Click to expand...
Click to collapse
put it back in download mode and flash again
if not download it again you might of had a bad download
For some reason on the tutorial it says to select stuff that doesn't come with the rar, care to give me a step by step instruction on the Odin 3.09?
arboy2 said:
For some reason on the tutorial it says to select stuff that doesn't come with the rar, care to give me a step by step instruction on the Odin 3.09?
Click to expand...
Click to collapse
are you just flashing stock or stock and root
jaythenut said:
are you just flashing stock or stock and root
Click to expand...
Click to collapse
Right now just stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar 4.4.2
arboy2 said:
Right now just stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar 4.4.2
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=PurJfuEsA0s
heres a how to
jaythenut said:
http://www.youtube.com/watch?v=PurJfuEsA0s
heres a how to
Click to expand...
Click to collapse
Still does it for some reason :'(
I even closed kies like he said
I'll try downloading the firmware he included although it's the same one I think
arboy2 said:
Still does it for some reason :'(
I even closed kies like he said
I'll try downloading the firmware he included although it's the same one I think
Click to expand...
Click to collapse
Try this guide. Step by step! Even redownload this file! Like said above, you might got bad zip. did u check md5?
http://www.droidviews.com/android-4-4-2-kitkat-firmware-for-samsung-galaxy-note-3-sm-n9005/
Report back if it helped
I redownloaded the file and it still does it! ((
arboy2 said:
I redownloaded the file and it still does it! ((
Click to expand...
Click to collapse
Are you sure you followed this guide? http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Because i used this one and it worked perfectly. Didn't use any magic.
What Odin version you have? Is it v3.09? Have you installed all the drivers, samsung kies...
ryanrazer said:
Are you sure you followed this guide? http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Because i used this one and it worked perfectly. Didn't use any magic.
What Odin version you have? Is it v3.09? Have you installed all the drivers, samsung kies...
Click to expand...
Click to collapse
I tried following the guide and it still did it, using Odin v3.09, found a possible fix here http://forum.xda-developers.com/showthread.php?p=47287747 gonna download and try it
arboy2 said:
I tried following the guide and it still did it, using Odin v3.09, found a possible fix here http://forum.xda-developers.com/showthrea.php?p=47287747 gonna download and try it
Click to expand...
Click to collapse
ok, report back if helped. mean while http://forum.xda-developers.com/showthread.php?t=2619017&page=2
Try his solution. It was a simple usb trick. If u use usb 3.0 try 2.0 and if you use desktop comp try back usb not fron. Try restart the computer... I know those are all weak tips but i would try everything in your case.
Hope you fix it bro..
ryanrazer said:
ok, report back if helped. mean while http://forum.xda-developers.com/showthread.php?t=2619017&page=2
Try his solution. It was a simple usb trick. If u use usb 3.0 try 2.0 and if you use desktop comp try back usb not fron. Try restart the computer... I know those are all weak tips but i would try everything in your case.
Hope you fix it bro..
Click to expand...
Click to collapse
Already tried usb 2, didn't work and I would restart but I'm downloading that N9005XXUDMJ6_N9005OXADMJ4_BTU.zip rom
Same thing happened with me, after it froze in odin mode I took out the battery for 5 mins, then put it into download mode (bit fiddly holding in the buttons and pushing the battery in) the I flashed Cwm recovery using odin, and hey presto my phone came to life...
Sent from my SM-N9005 using xda app-developers app
Well I tried with that other firmware and :
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
on the phone it said: SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2
((((((
heeellllppp T_T
arboy2 said:
Well I tried with that other firmware and :
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
on the phone it said: SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2
((((((
heeellllppp T_T
Click to expand...
Click to collapse
Sorry to hear that.. waay beyond my knowledge. You might change the title (if possible) to smth like: "After flashing 4.2.2 NA6 - stuck in Download mode, help"
Might attract more people to help you, bro.
:/
ryanrazer said:
Sorry to hear that.. waay beyond my knowledge. You might change the title (if possible) to smth like: "After flashing 4.2.2 NA6 - stuck in Download mode, help"
Might attract more people to help you, bro.
:/
Click to expand...
Click to collapse
Might be a long shot but for some reason Odin says I9505 aka galaxy S4 instead of my note model, could it be it?
EDIT: No it's not it I saw here https://www.youtube.com/watch?v=PurJfuEsA0s it was the same, but what is it!!! ;_;
Why you don't try another PC?
Sent from my SM-N900 using Tapatalk 2
arboy2 said:
Might be a long shot but for some reason Odin says I9505 aka galaxy S4 instead of my note model, could it be it?
EDIT: No it's not it I saw here https://www.youtube.com/watch?v=PurJfuEsA0s it was the same, but what is it!!! ;_;
Click to expand...
Click to collapse
When you installed via odin, was there only 1 tar.md5 file (all in one) and you just added AP and flashed or did you have 3 files, flashing bootloader manually, rom manually and another one that i don't actually know what it is, like this guy http://www.youtube.com/watch?v=W0QcggQ5bAs
also, re-partition was ticked off?
When i was flashing i couldn't figure out why my ROM ZIP had only 1 file and the guy on youtube had 3 files, than i found tutorial that suited me (all in one installation)... i still don't know why are there 2 different procedures...
what CSC region of your phone?
-On 1st post you had ext4 error, more likely your is HK or Some Asia model with bad ext4. If in this case someone had own HK handset successful flash KK update.
PS: I think better way for more people to help. you should post your AP,CP and CSC of your phone.
Sent from my SM-N9005 using Tapatalk
Hi,
here following what I did on my Note 3 (SM-N9005 model ) and some information that may help to find a solution:
ROM installed on the phone (original stock no rooted): N9005XXUDMJ7_N9005PHNDMJ4_N9005XXUDMJ7 (Nederlands)
ROM I tried to install: N9005XXUENA6_N9005VFGENA4_N9005XXUENA2 (Vodafone Italy)
Tool used: ODIN 3.0.9
I flashed as usual by using ODIN the new Rom but quite at the end of the process I got a "Write failure" error.
I noticed that "write protection is set to enable and I don't know if it's the root cause of the brick.
I tried to restore the previous version but I got "Sw version error with fuse/bin error indication" and after that I tried againto install kitkat rom and process stop again with the following error:
ID:0/019> system.img.ext4
<ID:0/019> modem.bin
<ID:0/019> cache.img.ext4
<ID:0/019> hidden.img.ext4
<ID:0/019> FAIL! (Size)
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not able to start in recovery mode, I got always the screen ending with UDC start and the yellow triangle inviting me to recovery with kies (of course Kies doesn't work!)
I read several similar topics but I'm not an expert and the result has been a big headache :crying: !
Please help me ! Does anyone may post a procedure that I can apply to get my Note back ?
I really appreciate it
Thank You in advance
Em
epl2005 said:
Hi,
here following what I did on my Note 3 (SM-N9005 model ) and some information that may help to find a solution:
ROM installed on the phone (original stock no rooted): N9005XXUDMJ7_N9005PHNDMJ4_N9005XXUDMJ7 (Nederlands)
ROM I tried to install: N9005XXUENA6_N9005VFGENA4_N9005XXUENA2 (Vodafone Italy)
Tool used: ODIN 3.0.9
I flashed as usual by using ODIN the new Rom but quite at the end of the process I got a "Write failure" error.
I noticed that "write protection is set to enable and I don't know if it's the root cause of the brick.
I tried to restore the previous version but I got "Sw version error with fuse/bin error indication" and after that I tried againto install kitkat rom and process stop again with the following error:
ID:0/019> system.img.ext4
<ID:0/019> modem.bin
<ID:0/019> cache.img.ext4
<ID:0/019> hidden.img.ext4
<ID:0/019> FAIL! (Size)
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm not able to start in recovery mode, I got always the sceen ending with UDC start and the yellow triangle inviting me to recovery with kies (of course Kies doesn't work!)
I read several similar topics but I'm not an expert and the result has been a big headache :crying: !
Please help me ! Someone my post a procedure that I can apply to get my Note back ?
I really appreciate it
Thank You in advance
Em
Click to expand...
Click to collapse
First thing to realize. If you can get into Donwload mode, then your chances of full recovery from this issue are extremely high, so no worries.
Second, the write protection enabled feature is specifically for the bootloader itself to prevent the user from flashing a bootloader for another device and REALLY hard bricking it.
If I were in your shoes, I'd try another Stock ROM download. There are times where the ROMs get corrupted and don't flash correctly. I'd also reinstall the Kies drivers for windows, etc. just to make sure that they are working.
For some reason, not sure why, but people cannot flash Carrier firmware, you are better off trying the stock XEO Poland 4.4.2 then trying to switch across to Vodafone's FW
HERE is the XEO stock 4.4.2, try this and see.
EDIT: Write enabled etc has nothing to do with it afaik, if you are stuck on the screen inviting you to recovery with kies, it'll still let you flash the stock ROM -- Now this is all on the premise you don't have a HK Note version, I assume you do not.
donalgodon said:
First thing to realize. If you can get into Donwload mode, then your chances of full recovery from this issue are extremely high, so no worries.
Second, the write protection enabled feature is specifically for the bootloader itself to prevent the user from flashing a bootloader for another device and REALLY hard bricking it.
If I were in your shoes, I'd try another Stock ROM download. There are times where the ROMs get corrupted and don't flash correctly. I'd also reinstall the Kies drivers for windows, etc. just to make sure that they are working.
Click to expand...
Click to collapse
Thank for your hint.
Unfortunately PHN kitkat is not yet available so I'm downloading now XEO rom, I'll let you know
donalgodon said:
First thing to realize. If you can get into Donwload mode, then your chances of full recovery from this issue are extremely high, so no worries.
Second, the write protection enabled feature is specifically for the bootloader itself to prevent the user from flashing a bootloader for another device and REALLY hard bricking it.
If I were in your shoes, I'd try another Stock ROM download. There are times where the ROMs get corrupted and don't flash correctly. I'd also reinstall the Kies drivers for windows, etc. just to make sure that they are working.
Click to expand...
Click to collapse
radicalisto said:
For some reason, not sure why, but people cannot flash Carrier firmware, you are better off trying the stock XEO Poland 4.4.2 then trying to switch across to Vodafone's FW
EDIT: Write enabled etc has nothing to do with it afaik, if you are stuck on the screen inviting you to recovery with kies, it'll still let you flash the stock ROM -- Now this is all on the premise you don't have a HK Note version, I assume you do not.
Click to expand...
Click to collapse
XEO firmware has been successfully loaded :victory: !
Thank you very much to both of you for the suggestion !
In my shoes, what would you do now? Try again Vodafone rom or wait for Italian no brand 4.4 ?
epl2005 said:
XEO firmware has been successfully loaded :victory: !
Thank you very much to both of you for the suggestion !
In my shoes, what would you do now? Try again Vodafone rom or wait for Italian no brand 4.4 ?
Click to expand...
Click to collapse
As you are able to recover you can try BUT you might have another failure. As stated above carrier roms seem to fail for some reason.
If it does then you should be able to flash Poland 4.4.2 again to recover.
Are you willing to try again with the potential of bricking?
Definitely I don't try to update to carrier rom till the reason of failure will be discovered. As I own vodafone branded S-view cover and it doesn't work with xeo rom only doubt I still have is if in that rom vodafone removed S-view issue at least for their cover
I don't think so but maybe someone was able to flash it can clarify that Anyone ?
By the way is there anybody that was able to load successfully vodafone rom ? Please give me a feedback ?
Inviato dal mio SM-N9005 utilizzando Tapatalk
Hi guys, I'm new to this site. I have a specific problem that I can't seem to find the answer for.
My phone: At&t Samsung Galaxy S4 (I made a typo in the title... )
Model: SGH-I337
I had MF3 version/4.2.2
I used various threads to eventually root my phone.
I was very happy.
I had to use safestrap
I was happy with safestrap
I had my stock in the stock rom slot
I had [ROM] Google Edition 4.3 [Clean][Deodex][276MB][2013.11.21] in first slot.
I was very happy with it.
Here is the thread http://forum.xda-developers.com/showthread.php?p=47718525#post47718525
I made a stupid move when I was finally done, I had my phone rooted, I had everything I needed, but it wasn't enough...
I did something in the mount options area in safestrap.. switched my sd to internal memory
My phone has been in a boot loop ever since on Samsung Image
I had Slot 1 active when this happened.
When I'm in recovery mode, all the options, including wipe data/factory reset doesn't work
I tried using a pit file in Odin to fix/failed
I tried using Odin 3.09 with stock firmware I found in some threads to try and get factory/failed
I get this in Odin along with fail "All threads completed. (succeed 0 / failed 1)"
I really want to fix my phone.
Preferably I would like it to stay as mf3
Does anyone have a solution?
A link to a thread I missed?
Something more recent?
I also tried Kies, but it was giving me trouble, I'll try it again as a last resort.
I hope there's a solution.
Kies 3
Kies 3 didn't work as well with emergency upgrade.
worried
joeydija said:
Kies 3 didn't work as well with emergency upgrade.
Click to expand...
Click to collapse
SW Rev Check Fail fused 2 Binary 1
Whoa.
Here is the solution!
Place all files found in the zip he gives in Odin 3.09
Top - BL
Bottom - CSC
http://forum.xda-developers.com/showthread.php?t=2716482
Makes sense, makes sense?
WOWza, very happy.
:good:
I spoke too soon.
joeydija said:
Here is the solution!
Place all files found in the zip he gives in Odin 3.09
Top - BL
Bottom - CSC
http://forum.xda-developers.com/showthread.php?t=2716482
Makes sense, makes sense?
WOWza, very happy.
:good:
Click to expand...
Click to collapse
Failed at the end.. I guess that's not the right order.. farthest I've got so far though, now when I boot I see Odin.
[Not the God]
hoorah!
The solution. FINALLY.
The file order goes like this...
AP gets the biggest file size
The one that starts with Base Loader goes in BL
The one that starts with CSC goes in CSC
The last one goes in CP
[solved] happy
joeydija said:
The solution. FINALLY.
The file order goes like this...
AP gets the biggest file size
The one that starts with Base Loader goes in BL
The one that starts with CSC goes in CSC
The last one goes in CP
[solved] happy
Click to expand...
Click to collapse
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
of course
SnowDot said:
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
Click to expand...
Click to collapse
Download link: https://mega.co.nz/#!MwAhlDyC!UOnkMFsUSctakHRfE1Mr95c1ymVwy1wBPu2yiPerros
If you've never used this site before
It's kind of weird
Press the DOWNLOAD button, it's RED
Wait for 100%
When you reach 100% it either starts downloading by itself or you press the download symbol
Good luck!
Summon odin
SnowDot said:
Hey man, can I get a mirror to the files you used? I have the SAME EXACT ISSUE! Please and thanks!
Click to expand...
Click to collapse
Also, you can find Odin3 v3.09 here: https://www.androidfilehost.com/?fid=23321874045862094
Remember to run Odin3 v3.09 as administrator
Right click Odin3 v3.09, press Run as administrator
Make sure you have your USB connected to back of computer
Take out battery from device
Place battery back in
Hold Volume Down + Home Button + Power Button
When you see WARNING! press Volume Up
Plug in USB
Wait for Odin3 v3.09 to recognize your phone
Leave all default settings
Place files from mf3. Tar in slots
Press START and wait 5 minutes
Good luck!
Another Soft Bricked SGH-I337...
joeydija said:
Also, you can find Odin3 v3.09 here: https://www.androidfilehost.com/?fid=23321874045862094
Remember to run Odin3 v3.09 as administrator
Right click Odin3 v3.09, press Run as administrator
Make sure you have your USB connected to back of computer
Take out battery from device
Place battery back in
Hold Volume Down + Home Button + Power Button
When you see WARNING! press Volume Up
Plug in USB
Wait for Odin3 v3.09 to recognize your phone
Leave all default settings
Place files from mf3. Tar in slots
Press START and wait 5 minutes
Good luck!
Click to expand...
Click to collapse
Joey, thanks for the resources as there are so many broken links out there.
I'm having the same issue; however, I'm finding very little success flashing with Odin to return back to stock.
Following the same steps you've outlined above, I receive a the following from Odin:
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
and the following from the prompt on the S4 screen:
SW REV. CHECK FAIL : fused : 4, Binary : 2
Click to expand...
Click to collapse
I've tried multiple prescribed methods, including the one you outlined, using Kies, and using nkhater's method for Unbricking I337 posted here.
I'm not entirely sure what steps to take next but any thoughts would be greatly appreciated.
mythandier said:
Joey, thanks for the resources as there are so many broken links out there.
I'm having the same issue; however, I'm finding very little success flashing with Odin to return back to stock.
Following the same steps you've outlined above, I receive a the following from Odin:
and the following from the prompt on the S4 screen:
I've tried multiple prescribed methods, including the one you outlined, using Kies, and using nkhater's method for Unbricking I337 posted here.
I'm not entirely sure what steps to take next but any thoughts would be greatly appreciated.
Click to expand...
Click to collapse
The SW REV. CHECK FAIL : fused : 4, Binary : 2 error means you are trying to flash an earlier version than your phone had before. You'll need to flash the same version you were using before, either MK2 or NB1. You can find the ODIN TAR files for them in the General section.
777
DeadlySin9 said:
The SW REV. CHECK FAIL : fused : 4, Binary : 2 error means you are trying to flash an earlier version than your phone had before. You'll need to flash the same version you were using before, either MK2 or NB1. You can find the ODIN TAR files for them in the General section.
Click to expand...
Click to collapse
Thanks for helping that guy out,
I have a question...
What ROM would you recommend for a 4.2.2 MF3 At&t Galaxy S4 SGH-I337?
I've been using the ROM found in here.
I am new to the rooted world.
It's the first ROM I tried and I love it.
I can go a whole day with, at most, losing 25% battery life.
I love the minimalist aspects of it.
I don't know how to keep track of new ROMs for my build though.
I don't really want to change ROMs at the moment, because I have everything I need with this one,
but if you can give me some cool advice, that would be awesome.
Any help, information, would be appreciated.
-Joey
Hi all,
Have attempted to fix this multiple times, and I think I've boned myself pretty hard at this point. Here's the situation:
Rooted, Safestrap'd, flashed Jasmine. All was muy bueno, but then I attempted to turn on mobile hotspot and it destroyed my mobile data by connecting and disconnecting every half a second. Perhaps there's some baseband issue or something.
I've gone through all the steps on Verizon support, and read a bunch online, but I can't come up with a solution. I'm just trying to flash back to stock/unrooted to see if that fixes the LTE radio issue, don't want to pay for an Asurion device if I can avoid it. Please give me aid!
Right now, I have Kies3 on my Macbook, and Odin v3.07+ Kies3 on my VMware, and the completely correct stock ROM for my 4.4.2 device from what I can tell, labeled "N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5". Do I need to attempt to flash a PIT file as well?
Last night, Odin failed on me multiple times, and now I'm stick at the "Firmware upgrade issue encountered" screen. I can boot into Odin, but I still keep failing when I try to flash the PDA file listed above (don't need any other CSC since I'm in the US, right?).
Kies is all FUBAR'd on my VMware as it says my device is unsupported and asks to connect my "MSM8960" which is clearly not my device and I think might be the root of my issue (See what I did there?).
On my Mac, Kies just hangs on the "Connecting..." and never connects.
I've exhausted myself trying to figure this out and am half-ready to just spend $$ and get an insurance phone but c'mon, I know this just has to be a hardware issue, amirite? Thoughts? Thanks!
KyleLinden said:
Hi all,
Have attempted to fix this multiple times, and I think I've boned myself pretty hard at this point. Here's the situation:
Rooted, Safestrap'd, flashed Jasmine. All was muy bueno, but then I attempted to turn on mobile hotspot and it destroyed my mobile data by connecting and disconnecting every half a second. Perhaps there's some baseband issue or something.
I've gone through all the steps on Verizon support, and read a bunch online, but I can't come up with a solution. I'm just trying to flash back to stock/unrooted to see if that fixes the LTE radio issue, don't want to pay for an Asurion device if I can avoid it. Please give me aid!
Right now, I have Kies3 on my Macbook, and Odin v3.07+ Kies3 on my VMware, and the completely correct stock ROM for my 4.4.2 device from what I can tell, labeled "N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5". Do I need to attempt to flash a PIT file as well?
Last night, Odin failed on me multiple times, and now I'm stick at the "Firmware upgrade issue encountered" screen. I can boot into Odin, but I still keep failing when I try to flash the PDA file listed above (don't need any other CSC since I'm in the US, right?).
Kies is all FUBAR'd on my VMware as it says my device is unsupported and asks to connect my "MSM8960" which is clearly not my device and I think might be the root of my issue (See what I did there?).
On my Mac, Kies just hangs on the "Connecting..." and never connects.
I've exhausted myself trying to figure this out and am half-ready to just spend $$ and get an insurance phone but c'mon, I know this just has to be a hardware issue, amirite? Thoughts? Thanks!
Click to expand...
Click to collapse
You have a friend with a real PC?
Also, what error is Odin giving...and I'd use 3.09 rather than 3.07.
Sent from my Note 3 via Tapatalk
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
KyleLinden said:
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried a different USB cable or port?
KyleLinden said:
Started using 3.09 last night, still same issue. It thinks I'm plugging MSM8960 instead of a Note 3. Some research informed me that this is the USB reference to the Snapdragon chip inside. Still, weird.
Nope, no friends with Windows nearby. Would that really be an issue?
Odin Error- Fails after it hits this point:
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Yes...that really could be an issue. Odin goes directly to the hardware.. and in your case....there is no hardware...only a software emulation. Also...if memory serves me right (of course it might be serving me wrong), Odin uses .tar.md5 files not .img.ext4 files.
Sent from my Note 3 via Tapatalk
Interesting, makes sense. Will seek out a real Windows machine and try the new ports/cable and report back. You're right about the tar.md5 file extension, but that's what seems to generate in the dialog panel when I use the aforementioned stock ROM file.
Thanks for advice so far.
donc113 said:
Yes...that really could be an issue. Odin goes directly to the hardware.. and in your case....there is no hardware...only a software emulation. Also...if memory serves me right (of course it might be serving me wrong), Odin uses .tar.md5 files not .img.ext4 files.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
the indidual partitions boot, recovery, system within the .tar are .img files so that is not the problem.
Easter Day miracle.. I took out my old laptop, reinstalled a copy of windows 7, moved the stock ROM and the pit file I found to a USB drive, used the OEM cable, installed all drivers available for Samsung mobile devices, rebooted, and finally Odin was happy with me and decided to flash stock! Phones fixed! Thanks everybody.
Hi all ! Hope sb help me with this...
I updated my S4 i9500 to android 5.0.1 lollipop (XXUHOAA ) about 8 months ago. No problem untill 2 days ago my phone turned off itself then went to bootloop.
Now it just shows the s4 logo then restarts again all the time. SOMETIMES it turns on but after 4 or 5 seconds again turns off (not able to do anything during 4 seconds)
I CAN NOT access recovery mode. The recovery mode became a black screen and not able to wipe/factory reset.
Before I bring it to serviceman I want to see if u can help me with this(It's warranty is voided now)
WHAT I HAVE TRIED RECENTLY:
I tried to flash 4 different Roms using 3 different odin versions but no success
[flashing roms get the error "complete(write) operation failed" and by using the suitable PIT file I get the error "repartition operation failed"]
Also tried flashing 5-files-firmware (with pit file) but again "repartition operation failed"
I used 3 usb cables including the original one
I did all of those steps using 2 different laptops and also different ports
I'm sure the samsung drivers are installed[odin port comes blue or yellow]
I used SkipSoft ToolKit and one click unsoftbrick softwares but no success
Also used adb to factory reset phone but it doesn't detect my phone[ seems it needs to be turned on]
I removed simcard, format extra sd card, remove battery for a long time and.....
Is there anything I haven't tried yet?? Can somone help ? I appreciate any suggestion,Thanks
[[Sorry my English]]
Try flashing a custom recovery and then factory reset?
KennethHau said:
Try flashing a custom recovery and then factory reset?
Click to expand...
Click to collapse
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused
Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Sent from my unknown using Tapatalk
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
alimtale said:
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused
Click to expand...
Click to collapse
Is the Odin version the proper one for your phone?
Sent from my unknown using Tapatalk
Jchef said:
Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Is the Odin version the proper one for your phone?
Click to expand...
Click to collapse
Of course I did. I even downloaded different android versions (5.0.1,4.4.2,4.2.2) But non of them flashed
I remember I used Odin 3.0.9 to upgrade my S4 to 5.0.1 months ago but I tried different Odin versions (1.85,3.0.7,3.0.9) for in case.
Unfortunately,I face an error all the time that is related to Nand write corruption .
If you have flashed 4.2.2 it's a brick ,for sure.
ludoke said:
If you have flashed 4.2.2 it's a brick ,for sure.
Click to expand...
Click to collapse
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.
alimtale said:
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.
Click to expand...
Click to collapse
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
My phone turned off itself. I tried flashing firmware after the problem occurred. I don't think the problem is because of flashing 4.2.2
Deleted
Maybe it's the battery
ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
This is incorrect. You don't brick your phone when you try to flash 4.2.2. That's simply not possible.
dorian2kx said:
Maybe it's the battery
Click to expand...
Click to collapse
I have 2 batteries...both of them same result (bootloop)
alimtale said:
I have 2 batteries...both of them same result (bootloop)
Click to expand...
Click to collapse
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.
Lennyz1988 said:
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.
Click to expand...
Click to collapse
No it doesn't reboot while download mode.Maybe hardware damage but it sometimes turns on and I can access applications and settings for a short time (about 5 seconds)
I have rooted my device when upgraded to 5.0.1. And recently I unchecked "enable superuser" in the superuser app.( I have done this before many times without problem)
I guess there is a problem related to that because when my phone turned on I tried to check the enable option in the superuser but as soon as I touch the check box my phone turns off instantly
If your phone goes into download mode. I don't think it is bricked.
Sent from my unknown using Tapatalk
You cannot fix your phone by Odin because of the Secure Download enabled bootloader.
You will have to pay a JTAG repair service.
Android 5.0.1 is a crap, which replaces your bootloader with a secure-download featured one,
so you won't ever be able to have the control of your phone again!
@Killnolife: A little melodramatic? It's not a locked bootloader so he still has total control over the device. Come back with an AT&T or Verizon S4 and then complain about having no control.
OP, Lennyz1988's advice is sound. Follow it.
Well I got tired of trying to flash my device with Odin. Always error... The Only choice I have is to take the phone to the service center and see what they can do...I'll share the result...
I took my phone to service centers for repair, they said the hard is damaged and it takes about 100$ to replace that:crying: if I pay that much I'm not sure it wont damage again
So my phone is dead now on my table and I gonna buy a new phone (maybe s5 or z3). Hope no one experience this situation