[Q] [i9505]: Won't boot into any OS / Recovery; only Download Mode - Galaxy S 4 Q&A, Help & Troubleshooting

Hello,
My Galaxy S4 (i9505) won't boot into Recovery or Android. It only boots into Download Mode.
Before this failure when everything worked fine i updated xposed to it's latest version, then i had to reboot the system. It rebooted normally then when unlocking the screen Android 4.4.2 (GoldenEye ROM) froze. I pulled the battery out and retried it.
Next try: Same thing. The third time it even didn't want to show the lock screen, only up to the bootanimation, then my phone rebooted itself.
Xposed shouldn't be the problem here?​
I tried flashing a new rom, had troubles going into recovery so i flashed a new/other one with Odin (from PhilZ touch to TWRP) and then reinstalled my OS whis is GoldenEye and Ktoon kernel from extsd.
I didn't wipe data which i could see in recovery because i thought i don't want to loose anything, so i rebooted.
Then the next big problem, it doesn't boot android, stuck at Samsung Galaxy S4 GT-I9505 splash screen. Recovery won't come up, stuck at booting recovery. Flashed the newest PhilZ touch with Odin: nothing, same result.
I downloaded a stock ROM (I9505XXUGNF1_I9505YBTGNF2_I9505XXUGNF1_HOME.tar) from SamMobile and flashed it several times with my Notebook and PC, both running Windows 8.1
Samsung Drivers are installed.
I used Odin with and without PIT file, turned Auto Reboot off and flashed over again, tried a PreRooted Knox Free ROM (I9505XXUFNC9) but nothing works :/
Found a full wipe rom, so i flashed this. Yep my data are gone, but my phone is still dead...
Also removed my SIM and SD before booting to ensure that this is not the problem.
And Odin shows no error:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Does something like eMMC Sudden Death exist on Galaxy S4 like it was on the Galaxy S3 and Note II?? :/, i hope not​
So does anybody know a solution how to fix my phone and get it running again? Don't want to loose my baby

raph6280 said:
Hello,
And Odin shows no error:
Click to expand...
Click to collapse
Is same "no error" shown in ROM flash? You presented screen info from recovery flash only.
I think that you messed with bootloader, so "resurrection" ROM would be needed...

Sounds to me like a hardware failure.
Xposed has nothing to do with being unable to enter the recovery.
Try flashing Philz again, make sure to uncheck auto-reboot. If it really won't boot and also flashing stock roms won't work, then you just had bad luck. Nothing you did that caused it. It's failed hardware then.

spamtrash said:
Is same "no error" shown in ROM flash? You presented screen info from recovery flash only.
I think that you messed with bootloader, so "resurrection" ROM would be needed...
Click to expand...
Click to collapse
Yes flashing with Odin works fine without any error but the device won't boot even with a clean stock rom in PDA
Is there any "resurrection" ROM or something similar?
Try flashing Philz again, make sure to uncheck auto-reboot. If it really won't boot and also flashing stock roms won't work, then you just had bad luck. Nothing you did that caused it. It's failed hardware then.
Click to expand...
Click to collapse
Flashed it without auto-reboot and still half dead :/
When it's a hardware failure how is it handled by Samsung with the knox warranty void flag because custom ROM and so on?

raph6280 said:
Is there any "resurrection" ROM or something similar?
Click to expand...
Click to collapse
It was for 4.3, here.
However with all KNOX mess, I am unsure if anything exists/leaked to us for 4.4.2.
Hmmm... you can try flashing the stock ROM with PIT file and repartition...

spamtrash said:
It was for 4.3, here.
However with all KNOX mess, I am unsure if anything exists/leaked to us for 4.4.2.
Hmmm... you can try flashing the stock ROM with PIT file and repartition...
Click to expand...
Click to collapse
Thanks, already tried this and over this i flashed the newest 4.4.2 ROM, i tried soo much but this beast won't come alive...
I will try it again with a pit, used one yesterday but that didn't work, eventually i'll find another to try that, i hope this makes a difference but my hopes are already gone :/

raph6280 said:
... but my hopes are already gone :/
Click to expand...
Click to collapse
Well, if your phone is:
a) dead (no warranty void in download mode)
b) covered by warranty
you could claim repair via Service Centre

spamtrash said:
Well, if your phone is:
a) dead (no warranty void in download mode)
b) covered by warranty
you could claim repair via Service Centre
Click to expand...
Click to collapse
I can boot into Download Mode, so sadly warranty void is shown
Bought my S4 over Amazon, hope they can do something.

raph6280 said:
I can boot into Download Mode, so sadly warranty void is shown
Bought my S4 over Amazon, hope they can do something.
Click to expand...
Click to collapse
Well, you shall learn the lesson... I have no idea how it looks in your country... in mine, I have the phone insurance bundled with Platinum bank account, and it is a very nice policy, covers "whatever happens". I have to pay a fee of 50 pounds per claim, and then I have repair/replacement.

I think it's not to bad, they repaired the small hardware issue which I caused on my old HTC for free and "updated" the software which I also had unlocked and rooted
Hope with that Samsung it is the same, eventually they see that this could be a hardware failure

raph6280 said:
Yes flashing with Odin works fine without any error but the device won't boot even with a clean stock rom in PDA
Is there any "resurrection" ROM or something similar?
Flashed it without auto-reboot and still half dead :/
When it's a hardware failure how is it handled by Samsung with the knox warranty void flag because custom ROM and so on?
Click to expand...
Click to collapse
If Linz is located in Austria, then the shop where you bought it from has to repair it. No rooting, custom rom can free them from their obligation. That is regulated by EU-law.

Related

Massive problems with new cyanogenmod 10.2

Hey guys just looking for any help if at all possible.
My install has been anything but smooth. I had many issues actually getting cyanogenmod on to the phone in the first place ( seems the help out there doesn't really cover the international i9505 very well, where it does you often just hit a brick wall)
In anycase i finally got it onto the phone and was looking for an explanation as to why the phone is not detecting my carrier. I mean its just not detecting it at all. I have made some strange findings when looking through the phone. It doesn't know what baseband i'm on for example.
Now for the real problem. After all the hassle of getting CM onto the phone i decided to reboot it to see if that would pick up my carrier. Now the phone takes AGES (2-5 mins) to boot up, some times it hangs. The phone functions fine when it boots.
I used CWM recovery to install CM because TWRP just would not work, infact CWM recovery was a pain in the arse too, the only way i could get it to boot into recovery mode was to download the rom manager app and use its widget to boot into recovery because manually trying it just resulted in multiple hangs.
This is the first time i have rooted/flashed an android device so i may be making some rookie errors here but this is bordering on stupid now.
Cwm and which version?
Sent from my GT-I9505 using xda app-developers app
mkhattat said:
Cwm and which version?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
i9505-cwm-recovery-6.0.3.2-4. Its the 28th's nightly also. Im trying to get it to see my o2 version of the s4. I installed gapps from zip straight after CM but i havn't used it. might the problem be there?
i have reinstalled CWM and flashed a new CM nightly from here.
http://forum.xda-developers.com/showthread.php?t=2317040
I still cant get access to my mobile network (UK o2). When i flash cyanogen it says please insert sim yadayada. Any help on this would still be very much appreciated :crying:
Possibly a corrupt EFS partition? If you flash stock ROM can you get signal and baseband back?
Sent from my GT-I9505 using XDA Premium HD app
TouchWiz king of ROMs ..... dont careeee CM bla bla bla
This is really bad im still in need of help sadly. I am trying to flash stock firmware from sammobile.com. It has the o2 uk one i need. I am using odin to do it following this guide youtube dot com/watch?v=hZTTTk7vbVM
The problem now is that it fails to flash (using odin 3.06) . Kies doesnt even recognise my device....this is a disaster so far
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505O2UBMG1_I9505XXUBMF8_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> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So i have soft bricked my phone. It wont boot up instead it gets to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" Kies doesnt recognise my phone so thats out.
I cant get into recovery mode it just gives the same message. In download mode when i try to use odin to flash the previously mentioned stock rom it fails. Im at a loss and i am badly in need of help now
Try this sir. Post #9 http://forum.xda-developers.com/showthread.php?p=46143562
Sent from my GT-I9505 using xda app-developers app
phrazersco said:
So i have soft bricked my phone. It wont boot up instead it gets to a screen that says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" Kies doesnt recognise my phone so thats out.
I cant get into recovery mode it just gives the same message. In download mode when i try to use odin to flash the previously mentioned stock rom it fails. Im at a loss and i am badly in need of help now
Click to expand...
Click to collapse
User Odin version 1.85
Sounds to me like you have a corrupted EFS, just as the poster above mentioned. Did you do a full wipe before you tried to Odin back to Stock ROM?
donalgodon said:
Sounds to me like you have a corrupted EFS, just as the poster above mentioned. Did you do a full wipe before you tried to Odin back to Stock ROM?
Click to expand...
Click to collapse
no i have not done a full wipe. I have been on holiday for the past week and got home yesterday. Im still looking for a fix for this people!
phrazersco said:
no i have not done a full wipe. I have been on holiday for the past week and got home yesterday. Im still looking for a fix for this people!
Click to expand...
Click to collapse
Look no further, because the full wipe is the fix, like it or not.
My newbness is screwing me here i know it. The phone is fresh from the o2 shop so i dont have anything to lose, how do i do a full wipe?
I have had some progress on my own. I downloaded a new .tar stock firmware from sammobile, the BTU version. This time odin flashed it no problem what-so-ever. So if anyone reading this gets the same problem mine was with the o2uk firmware on sammobile.
I have a new problem though, the phone just doesnt get past the samsung logo at boot. it doesnt freeze as i can see the blue glow round the samsung logo pulse but it just never boots. left it for ah hour after first flashing and nothing. I removed battery etc etc but wont get past this point. Is this full wipe easy to do?
phrazersco said:
My newbness is screwing me here i know it. The phone is fresh from the o2 shop so i dont have anything to lose, how do i do a full wipe?
I have had some progress on my own. I downloaded a new .tar stock firmware from sammobile, the BTU version. This time odin flashed it no problem what-so-ever. So if anyone reading this gets the same problem mine was with the o2uk firmware on sammobile.
I have a new problem though, the phone just doesnt get past the samsung logo at boot. it doesnt freeze as i can see the blue glow round the samsung logo pulse but it just never boots. left it for ah hour after first flashing and nothing. I removed battery etc etc but wont get past this point. Is this full wipe easy to do?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset. It'll cure your problem. The first boot can take a long time, 5 minutes, so let it do it's thing
jd1639 said:
Boot into the stock recovery and do a factory reset. It'll cure your problem. The first boot can take a long time, 5 minutes, so let it do it's thing
Click to expand...
Click to collapse
Thanks guys im back into my phone and its all working normal again!
Did i do something wrong by rooting then installing cyanogen mod the way i did? i mean it worked i just didnt have my phone network. kept saying insert SIM. was i supposed to unlock the carrier or something? i though cyanogen did all that.
Still looking for that last bit of advice people. Is there something i should have done before rooting/flashing to unlock my phone from o2uk or was i correct in thinking CM10.2 unlocked the phone also? if i was incorrect is there any help i can be given with respects to this? Thanks again.

[Q] [i9505] HELP! - Soft bricked device

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.

[Q] brick after flashing kitkat

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

[Q] Can i restore to stock from odin att galaxy s5?

Please Help i tried flashing stock with odin for ATT Galaxy S5 But it said failed and i dont know what to do, I want to get rid of root, also i tried rebooting and using a root application but they all crash.
Joshua.n said:
Please Help i tried flashing stock with odin for ATT Galaxy S5 But it said failed and i dont know what to do, I want to get rid of root, also i tried rebooting and using a root application but they all crash.
Click to expand...
Click to collapse
Are you using the latest stock firmware?
1monday said:
Are you using the latest stock firmware?
Click to expand...
Click to collapse
Yes I got it from here http://samsung-updates.com/device/?id=SM-G900A
Did you perform a wipe/factory reset in recovery before flashing?
Also, since you tried to flash and failed, are you no longer able to boot normally? If you can, have you tried unrooting via supersu?
1monday said:
Did you perform a wipe/factory reset in recovery before flashing?
Also, since you tried to flash and failed, are you no longer able to boot normally? If you can, have you tried unrooting via supersu?
Click to expand...
Click to collapse
OK I'm fully unrooted from super su, I tried to factory reset but there is a font that is still stuck on and the boot up says custom, please help!
Joshua.n said:
OK I'm fully unrooted from super su, I tried to factory reset but there is a font that is still stuck on and the boot up says custom, please help!
Click to expand...
Click to collapse
Sounds like the Knox counter. The system status displays as custom when Knox detects that you are running a custom ROM. What ROM were you running before you unrooted? By successfully flashing the latest stock firmware, the status should switch to official. However, once the Knox counter is tripped, there is no way to reverse it as of yet. So your device will always report that it was once modified even after a full unroot and flashing back to 100% stock
1monday said:
Sounds like the Knox counter. The system status displays as custom when Knox detects that you are running a custom ROM. What ROM were you running before you unrooted? By successfully flashing the latest stock firmware, the status should switch to official. However, once the Knox counter is tripped, there is no way to reverse it as of yet. So your device will always report that it was once modified even after a full unroot and flashing back to 100% stock
Click to expand...
Click to collapse
But I just want to flash a stock rom to get rid of the font when i tried before with odin on pc it failed Any idea?
Have you tried flashing stock after you did the factory reset?
1monday said:
Have you tried flashing stock after you did the factory reset?
Click to expand...
Click to collapse
No but ill try again, Downloading fresh stock right now
Joshua.n said:
No but ill try again, Downloading fresh stock right now
Click to expand...
Click to collapse
I'll wait to hear results...
Joshua.n said:
But I just want to flash a stock rom to get rid of the font when i tried before with odin on pc it failed Any idea?
Click to expand...
Click to collapse
Lots of ideas, but you aren't good at answering questions. We can't see your phone, we have no magic wands. You will only get good advice if you describe your situation better. We are trying to help you & it would be in your best interests to provide a lot more detail.
What do you mean by "font"?
Paste the exact Odin error message for us
What is your Knox status?
If you don't know, boot to download (Odin) mode & it will say 0x0 or 0x1 on the screen
You linked to a firmware site, not a specific firmware. What is your firmware version?
You didn't answer the question about wiping the cache
Odin can be fussy about USB. Did you try usimg a different USB cable & port?
And ideally, describe step by step how you tried to flash with Odin.
.
1monday said:
I'll wait to hear results...
Click to expand...
Click to collapse
Thank you so much for helping me out btw, I really appreciate it
fffft said:
Lots of ideas, but you aren't good at answering questions. We can't see your phone, we have no magic wands. You will only get good advice if you describe your situation better. We are trying to help you & it would be in your best interests to provide a lot more detail.
What do you mean by "font"?
Paste the exact Odin error message for us
What is your Knox status?
If you don't know, boot to download (Odin) mode & it will say 0x0 or 0x1 on the screen
You linked to a firmware site, not a specific firmware. What is your firmware version?
You didn't answer the question about wiping the cache
Odin can be fussy about USB. Did you try usimg a different USB cable & port?
And ideally, describe step by step how you tried to flash with Odin.
.
Click to expand...
Click to collapse
Font as in the text on the apps on the home screen and words in ceartain apps
If i get another fail i will paste the error
Knox says 0x0
firmware is 4.4.2
how do i wipe the cache?
No but im pretty sure its not the usb port
I put my phone into download mode, Then plugged it in opend odin pc. clicked Ap And Directed path to the .tar.md5 And hit start
Joshua.n said:
Thank you so much for helping me out btw, I really appreciate it
Click to expand...
Click to collapse
No problem man. Although, fffft does make a valid point. Providing a detailed summary of your experience and circumstances would go a long way in helping to solve the issue. I also wondered what you meant by "font", what your Knox counter reads, and what the Odin error message reads
---------- Post added at 08:22 PM ---------- Previous post was at 08:18 PM ----------
Joshua.n said:
Font as in the text on the apps on the home screen and words in ceartain apps
If i get another fail i will paste the error
Knox says 0x0
firmware is 4.4.2
how do i wipe the cache?
No but im pretty sure its not the usb port
Click to expand...
Click to collapse
Wiping the cache can be done in recovery. And although your usb port may be perfectly fine, trying another one solves the problem in some cases so it is worth a try
This is the error
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is the font I mean
Joshua.n said:
This is the font I mean
Click to expand...
Click to collapse
Have you simply tried changing the font in Settings?
Settings > Display > Font > Font Style
Joshua.n said:
Font as in the text on the apps on the home screen and words in ceartain apps
If i get another fail i will paste the error
Knox says 0x0
firmware is 4.4.2
how do i wipe the cache?
No but im pretty sure its not the usb port
I put my phone into download mode, Then plugged it in opend odin pc. clicked Ap And Directed path to the .tar.md5 And hit start
Click to expand...
Click to collapse
Thanks for the extra detail. And good to hear that your Knox flag is normal (0x0).
One more question for you.. this is an original ATT (SM-G900A) phone, right? Not something else e.g. a TMobile S5 with ATT firmware? Or an unlocked ATT developer model?
You want to change the system font
Setings menu > Device > Display > Font > Default
(a factory reset + successful flash would also default the font)
To clear the cache, pull your battery out for ten seconds to assure that your phone is off. Then go to the recovery mode (volume up + home + power)
You will see an onscreen menu that will include a choice to wipe your cache
Now about your failed flash. Odin can be picky, but with a little patiemce and a few tries you can get it to flash. The Odin error you had is "Auth" or authorization fail. That could be caused by several things. Make sure that you are flashing the same version firmware as is on the phone if you can. Do not flash an older version.
That error can also be caused by a borderline USB cable or timeout (PC under load or using USB hub for example). Turn off your PC antivirus temporarily.. and don't game or use the computer for anything else during the flash. And maybe try a different cable and USB port just in case.
Here is a good flash method:
Backup any files, etc that are important to you
Then do a system reset (this will delete user files!)
Settings menu > General > Backup & reset > Factory data reset > Reset my device
Then clear the cache from recovery mode (vol up + home + power)
Then reboot to dowload mode
Ensure that you have Auto Reboot and F. Reset checked in Odin,
& try flashing Odin again
If it still fails, then do not close Odin
Remove the phone battery and USB cable for ten seconds, then go to download mode again and try running the flash again. It will almost always work the second time, even though it failed the first time.
There are more aggressive settings that we can use to force a flash if we have to. But try this normal way above first. And a differemt USB cable if you have to.
.
fffft said:
Here is a good flash method:
Backup any files, etc that are important to you
Then do a system reset (this will delete user files!)
Settings menu > General > Backup & reset > Factory data reset > Reset my device
Then clear the cache from recovery mode (vol up + home + power)
Then reboot to dowload mode
Ensure that you have Auto Reboot and F. Reset checked in Odin, & try flashing Odin.
If it fails, then do not close Odin
Remove the phone battery and USB cable for ten seconds, then go to download mode again and try running the flash again. It will almost always work the second time, even though it failed the first time.
.
Click to expand...
Click to collapse
:good: Excellent advice. I wish this was incorporated into an unroot/restore message in the towel root thread. I can not even count how many times I have had to give this method to folks running into issues reverting to stock on the ATT variant.
bailey37821 said:
:good: Excellent advice. I wish this was incorporated into an unroot/restore message in the towel root thread. I can not even count how many times I have had to give this method to folks running into issues reverting to stock on the ATT variant.
Click to expand...
Click to collapse
I have tried this as well, but my baseband is: G900AUCU2ANG3 and the only file I can find on SamMobile and elsewhere is apparently an older version (G900AUCU1ANCE). Thus, my attempt to Odin this back to stock is failing.
Anyone have any thoughts as to how I can proceed? My Odin counter is 0x0, so that's good. However, the status is showing custom and even though I know for sure that I could get the local AT&T device center to reflash it to stock, I'm not sure they would because of the "custom" status.

Help fixing dm_verification & mmc_read failed

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

Categories

Resources