hi everyone,
well i really have a BIG PROBLEM here :crying: im trying to flash my gt-i8190 but i cant? i get a red writing on download mode it say " movi_write card_status:2 " i can't understand what is that mean...and the phone never want to boot...it bootloop in "samsung galaxy S III mini" and turn off and on...and i cant enter to recovery mode...i tried many roms and tried flashing PIT file and tried PARAM file too but nothing happen....and this what odin say:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190XXAMG4_I8190OJVAMH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> STE_boot1.img
<ID:0/004> STE_boot2.img
<ID:0/004> modem.bin
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
i really need to understand the problem and the cause of that red writing...i hope my question will be replied..
thanks
hi, even I am facing the same problem from past several days, I tried flashing stock rom and pit file but nothing is happening, if anybody knows the solution to this please let us know
Hi, I'm having exactly the same issue as above.. The phone can't boot in recovery and in system... It boots in download mode and I tried to flash everything via ODIN: official ROMs, custom ROMs, Stock recovery, Custom Recovery, Param, pit files.. but they seem to have no effecto on the phone.. since when I boot in download mode it says that no custom firmware is loaded, but the official samsung..
Please help us to solve this brick!
Hi, it seems like the NAND flash is dead, or at some point damaged, as far as I understood, it told you that it can't write in one memory block. Sorry for that.
Maybe you try to flash another firmware versions?
What happens if you put an alternative update.zip on it's internal/external memory (MTP may work on bootloader startup, Samsung's logo).
hello....i'm facing the same problem...tried everything ppl above had done and still nothing....the phone died suddenly..
hope it's not a hardware problem
any help is welcomed ....thanks
Related
Hi,
my girlfriend just came back from China with a P1000 from her friend. As the whole device was running on chinese language and for some strange reason it was not possible to enter System Setting to change the language, I decided to flash her the latest firmware and just make a fresh start. (i'm a flash veteran on my SGS since 2 years, so I know how to use Odin)
I downloaded the P1000XWJQ8 from Sammobile, fired up Odin and flashed the new ROM with repartition enabled.
The procedure went through without errors:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> cache.rfs
<ID:0/003> hidden.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
At the end of it the device didn't auto-boot as expected, it just stayed there with a black screen!!!!!!
Disconnecting and reconnecting it triggers in Odin the REMOVED and the ADDED lines but nothing happens.
I cannot switch on, cannot go into download nor recovery, the device just seems to stay dead :-(
My next idea was trying to pull the battery but apparently the battery is glued to the casing, so before I do more damage, I better start asking here.
Hope someone can help, my girlfriend will kill me if I can't repair this damn thing...
EDIT: after having closed Odin on the PC I tried to connect the device again and it started to play the startup song and Win7 started to install the new drivers from the new firmware. 7 out of 9 found drivers installed correctly, 2 instead failed.
But nothing changed to the vegetarian state of the P1000
EDIT 2: now, after 12 hours wait, the device doesn't do anything anymore when I connect it to the PC, no USB connect, no sign of adding it in Odin. It seems like the charging mechanism doesn't work anymore either. The deivce appears totally dead.
Did you see my thread http://forum.xda-developers.com/showthread.php?t=1769144? This problem is totally the same as mine.
Is yours rooted? Coz it says here http://www.teamovercome.net/p1000/?page_id=17 that :
[REQUIRED FOR FROYO-BASED TABS ONLY:] Your Tab must be rooted. (Please look for SuperOneClick root method as it’s usually the safe bet! But for more information on rooting, please refer here: http://forum.xda-developers.com/showthread.php?t=812367)
Click to expand...
Click to collapse
I hope someone can help us, or else, no choice but to bring this to service center.
itenos said:
Hi,
my girlfriend just came back from China with a P1000 from her friend. As the whole device was running on chinese language and for some strange reason it was not possible to enter System Setting to change the language, I decided to flash her the latest firmware and just make a fresh start. (i'm a flash veteran on my SGS since 2 years, so I know how to use Odin)
I downloaded the P1000XWJQ8 from Sammobile, fired up Odin and flashed the new ROM with repartition enabled.
The procedure went through without errors:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P1000XWJQ8_P1000XXJPZ_P1000DBTJQ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> cache.rfs
<ID:0/003> hidden.rfs
<ID:0/003> modem.bin
<ID:0/003> factoryfs.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
At the end of it the device didn't auto-boot as expected, it just stayed there with a black screen!!!!!!
Disconnecting and reconnecting it triggers in Odin the REMOVED and the ADDED lines but nothing happens.
I cannot switch on, cannot go into download nor recovery, the device just seems to stay dead :-(
My next idea was trying to pull the battery but apparently the battery is glued to the casing, so before I do more damage, I better start asking here.
Hope someone can help, my girlfriend will kill me if I can't repair this damn thing...
EDIT: after having closed Odin on the PC I tried to connect the device again and it started to play the startup song and Win7 started to install the new drivers from the new firmware. 7 out of 9 found drivers installed correctly, 2 instead failed.
But nothing changed to the vegetarian state of the P1000
Click to expand...
Click to collapse
MarlX said:
Did you see my thread http://forum.xda-developers.com/showthread.php?t=1769144? This problem is totally the same as mine.
Is yours rooted? Coz it says here http://www.teamovercome.net/p1000/?page_id=17 that :
I hope someone can help us, or else, no choice but to bring this to service center.
Click to expand...
Click to collapse
hey guys, are sure your gtab is P1000??
see the back cover, and chek your gtab model to make sure.
qm4n76 said:
hey guys, are sure your gtab is P1000??
see the back cover, and chek your gtab model to make sure.
Click to expand...
Click to collapse
Yes, 100% sure, my one is a P1000. As wrote in EDIT2 my device now seems to be totally dead
Hello Friends!
I have bricked my s5830i ace, while I wanted to return to stock with odin. Unfortunately I didn't check USB debugging, so I couldn't flash it.
The problem is the following:
-Usb debugging isn't checked=>Can't flash=>Can't unbrick
Please help me! If i connect the phone to the first USB, odin says: Operation(Write) failed...or something...I can't try now.
Or when I connect to the second USB, odin says: Connecting(or something like that) and stucks...
Please help me! I'm very nervous, and I don't want to bring it to service!
You're my last hope
(If you need details, I could have a look at flashing process, and messages)
Well, how did you brick it? Seems like you flashed the wrong firmware (a firmware for 5830 without the 'i')
If that's the case and odin is stuck at setting up connection, then bad luck. A jtag (if you know someone with one) or service center are your options.
I'm sad to hear that. I wanted to flash the official 2.3.6 from samfirmware. If I know well, I should use Odin 1.84, or 1.85 and the file, which I have downloaded should be under PDA section...
Does your ace still go into download mode?
If so, it might be fixed by flashing the correct firmware.
Make sure to have your firmware in your pc root (C:/) since i've read that it helps.
I've put the correct firmware (Samfirmware S5830i Hungary Telenor)...It boot into download mode without any problem. I haven't tried to put the md5 file to the root, but I will try it soon. Thanks. I hope It's a good idea.
But I think I should check USB debugging in settings, but I can't do this, because It's bricked
coda00 said:
But I think I should check USB debugging in settings, but I can't do this, because It's bricked
Click to expand...
Click to collapse
As far as I'm concerned, usb debugging doesn't matter when flashing via odin. Edit: confirmed, since in download mode the system isn't loaded, there's nothing to debug.
Most odin problems occur when using wrong firmware, wrong .ops file or filename, when drivers aren't installed, or when not running odin as admin.
Okay....nothing worked.
I've tried everything, which you've said.
Odin write me every time:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLD3_S5830iBTULC1_S5830iXXLD2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl.bin
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's all...I tried everything...maybe my last chance is the service
OK.....news...
I've tried to remove the Rafael.Baugis kernel, and I got new message from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXLD3_S5830iBTULC1_S5830iXXLD2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> BcmCP.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> boot.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response form LOKE
<ID:0/004> system.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response form LOKE
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
WOW...
Problem solved
I've found a multi package here:
http://forum.xda-developers.com/showthread.php?t=1822109
It helped me...my phone is unbricked again
And of course I've flashed the stock rom too.
I have a Note N7000, It is rooted with Philz Touch 5. I had issues with it last friday where it would restart when trying to start any random app.
Thought it weird, maybe it's the last app to be put on - but no. Went into the phone and cleared the cache in Philz Touch 5. After this the phone would not start again.. much to my disappointment.
I have downloaded Odin3 v1.87 and have downloaded the attachment from this thread. http://forum.xda-developers.com/showthread.php?t=1354888
i have also purchased a JIG from this Ebay ad. http://www.ebay.co.uk/itm/141209048811?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
The JIG doesn't work, ODIN can read my phone when it's plugged in - and has successfully done the PDA & BOOTLOADER tasks.
I hope & feel that I can bring my phone back to life - I would someone to help me to understand what next steps I can take to do this.
Thanks for all your help in advance..
Can you boot into recovery?
Azeazezar said:
Can you boot into recovery?
Click to expand...
Click to collapse
I unfortunately can't get it to do anything.. I am hoping there's something I can do that i haven't tried.
marmyte said:
I unfortunately can't get it to do anything.. I am hoping there's something I can do that i haven't tried.
Click to expand...
Click to collapse
What the PDA and bootloader task? How did you do it?
nokiamodeln91 said:
What the PDA and bootloader task? How did you do it?
Click to expand...
Click to collapse
Used C:\Users\Stev\Downloads\removeyellowtriangleNEW\2-ZSLPF.tar for BOOTLOADER
And C:\Users\Stev\Downloads\removeyellowtriangleNEW\1.tar for the PDA
All went well -
<ID:0/004> Added!!
<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> Sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Added!!
<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> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> Sbl.bin
<ID:0/004> param.lfs
<ID:0/004> Sbl.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
Used Odin3 v1.87
EDIT
I just noticed those files are from triangleaway. NOT the stock rom. What you flashed is to remove the big yellow triangle at boot.
Download Stock GB or Jellybean, and flash those with odin. That should fix your phone.
Can you put me in the right direction for the stock roms, I've tried a download for uk vodafone but it goes to hotfile with a warning message
Thanks.
marmyte said:
Can you put me in the right direction for the stock roms, I've tried a download for uk vodafone but it goes to hotfile with a warning message
Thanks.
Click to expand...
Click to collapse
Why did you even flash those files? Go to www.sammobile.com and download a firmware. Then flash it using Odin. Just use the PDA tab to flash the rom.
It failed, can i try to flash with an older rom?
You can flash any rom from that site. i recommend avoiding the ICS roms though.
marmyte said:
It failed, can i try to flash with an older rom?
Click to expand...
Click to collapse
How where why?
Using Odin3 v1.85
It gets to this stage and... How long does it take?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000VODLT4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
marmyte said:
Using Odin3 v1.85
It gets to this stage and... How long does it take?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000VODLT4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
Click to expand...
Click to collapse
There is some connection problem with phone and PC.. so kill all kies processes.. run odin as admin.. reboot into download mode and try again.
killed all kies processes.. run odin as admin.
Got this..
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000XXLT9_N7000XXLT3_N7000VODLT4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Help please:crying:
marmyte said:
killed all kies processes.. run odin as admin.
Help please:crying:
Click to expand...
Click to collapse
Flash a tar version of Philz kernel like XXLTA or DDLSC. using odin. The power off the device and boot into recovery. This should get you into CWM. Format system, data, cache and preload. Then reboot into download mode and flash this rom again OR you can flash any custom TW or CM rom.
I'm really sorry, but I don't understand what you've just said - can you make it any easier for a novice like me
marmyte said:
I'm really sorry, but I don't understand what you've just said - can you make it any easier for a novice like me
Click to expand...
Click to collapse
go to this link and in post 3.. there is download for TW kernels. download the latest tar version.
boot the phone to download mode and select the tar kernel in PDA and flash it. Odin will say KERNEL.. If it completes. power off the device and try to boot into recovery.
Odin successful - but can't boot into recovery..
marmyte said:
Odin successful - but can't boot into recovery..
Click to expand...
Click to collapse
Why not? Power off the device. In fact remove the battery for a couple of seconds.. Then put it back. Press volume up home and power together till you see the N7000 logo and let go..
Tried it.. Nothing happens - but i can touch the screen and it'll vibrate?
Hello everyone reading this
before you reading this im a lilltle bit noob so yeah
yesterday i rooted my s5mini g800f and installed cm 12.1 on it everything went fine
this day either i wanted to go back to the stock rom so i downloaded stock android 4.4.2 for s5mini g800f
i went to odin flashed it but when i try to flash it this happens
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G800FXXU1ANL1_G800FVFG1ANL2_G800FXXU1AOC1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
so it failed but when i started up my phone it said
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again
so it did that but keys said to me that my phoe wasn't a supported device i think that kies said that because i installed a custom rom and rooted my device
but now i can't use my device i hope simebody can help me i dont know what to do
i can't get into recovery mode and the file size of the stock rom is 2.2 gb
i hope you guys can help me! much apprecheated
sorry for bad languege im not english
Thanks
Did you try to reflash with Odin ? Or flash a custom recovery and wipe all data ?
ok so we both have note 4s and i rooted both of our phones many months ago. i put poprocks v.13 on both phones and everything worked out fine. well over time that rom became outdated so i decided to update the phones. i updated mine to N910TUVU2EPE3_N910TTMB2EPE3_N910TUVU2EPE3_HOME.tar modem and the overdrive rom. had a few hick ups but over all went fine and my phone works great. so i decided to upgrade hers tonight. i put her phone into download mode and started odin. loaded the N910TUVU2EPE3_N910TTMB2EPE3_N910TUVU2EPE3_HOME.tar.md5 and hit start. well it failed and now the phone wont do anything. no matter what i do in odin it fails. ive tried cf-auto root it fails to. phone under download mode says blocked by r/l. odin usally stays stuck on setup connection. any ideas how to get this thing working again before she kills me?
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<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> cache.img.ext4
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Delete the .md5 and just leave it as .tar
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
assuming you ment delete the md5 from the name of file. it didnt work.
just tried cf-root with odin on her laptop and same result. seems like this phone is a paperweight. im completely dumb founded. we have the exact same phones and i did hers the same way as mine. hers failed on the first step and now it looks like im buying her a new phone. this thing wont do anything at all. it can go into download mode but no matter what you try to load through odin fails.
osiris999 said:
just tried cf-root with odin on her laptop and same result. seems like this phone is a paperweight. im completely dumb founded. we have the exact same phones and i did hers the same way as mine. hers failed on the first step and now it looks like im buying her a new phone. this thing wont do anything at all. it can go into download mode but no matter what you try to load through odin fails.
Click to expand...
Click to collapse
Do you use hangouts (google) or Skype (chat)?
It seems it would be easier to help via one of those mediums.
osiris999 said:
just tried cf-root with odin on her laptop and same result. seems like this phone is a paperweight. im completely dumb founded. we have the exact same phones and i did hers the same way as mine. hers failed on the first step and now it looks like im buying her a new phone. this thing wont do anything at all. it can go into download mode but no matter what you try to load through odin fails.
Click to expand...
Click to collapse
Dupe
I was finally able to fix this thing using Samsung smart switch emergency recovery.
osiris999 said:
I was finally able to fix this thing using Samsung smart switch emergency recovery.
Click to expand...
Click to collapse
Glad you got it working. Looks like reactivation lock was turned on on hers but not yours. I always keep it off on my devices as I would forget to check.
Sent from my SM-N910T using XDA Free mobile app