Hi all, My S3 GT-I9300 international edition, bought on Amazon from some German place, orignal stock Samsung no mods went into a boot loop Xmas day (yeah, what a present!).
I could then go into recovery mode and cleared the cache. Still boot loop AND I could NO LONGER get to recovery mode, but can get into Download Mode just fine. So there is hope...
I read this tread http://forum.xda-developers.com/showthread.php?t=1457458
I am hoping this is the way to go for me. Experts may comment, please.
I am looking for kernel AND pit files. Where can i get them?
I tried using Siyah-s2-v5.0.1 but do not have a PIT file for it.
When I try to use it heimdall says I do not have the right PIT file:
"
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
ERROR: Partition corresponding to -kernel argument could not be located
"
I am on OS X with heimdall working fine.
Please help if you can and know more.
thank you so much
E
Using this rom:
I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME
and the Siyah-s2-v5.0.1 kernel, I can do:
heimdall flash --primary-boot boot.img --verbose
OK
heimdall flash --recovery recovery.img --verbose
OK
but nothing else. I cannot do:
heimdall flash --kernel zImage --verbose
it says:
ERROR: Partition corresponding to -kernel argument could not be located
Boot loop is flash stock rom via Odin.
Stay away from pit files .
jje
Sent from my GT-N8013 using xda premium
culurciello said:
Using this rom:
I9300XXELL4_I9300O2UELL1_I9300BWELK1_HOME
and the Siyah-s2-v5.0.1 kernel,
Click to expand...
Click to collapse
Why are you using siyah s2 kernel if you have an s3 maybe thats the reason you got into bootloop
Sent from my GT-I9300 using xda premium
LOL
1. download an stock rom from www.samfirmware.com
2. dont make the same mistake as you did with before download a SIII rom instead of an SII rom...
3. Use ODIN to flash to a stockrom AND NEVER FLASH .PIT FILES with ODIN unless YOU reallyyy need it.
4. now keep it or move to a custom ROM for the SIII and not SII AKA S2
and for the rest i wish you an merry christmas and a early happy new year
haydar100 said:
and for the rest i wish you an merry christmas and a early happy new year
Click to expand...
Click to collapse
thank you and you too!
I am on with Odin now and this guide:
widefide.com/mobile/galaxy-s3-boot-problem-solution
I think I need a PIT file because of the errors:
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried the pit file here
widefide.com/mobile/galaxy-s3-boot-problem-solution
and the stock rom :
I9300XXALE8_I9300O2UALE5_I9300BWLE5_HOME.tar.md5
still nothing I cannot seem to get Pit partitioning to work
PS. Yes I did make a huge mistake with the S2 kernel... how silly!
Service Centre required before you totally destroy the phone .
jje
phone is already dead due to component problem: Samsung KMVTU000LM eMMC(16GB)+MDDR(64MB) NAND Flash
see thread here:
on: forum.xda-developers: showthread.php?t=1993044
CASE CLOSED
thank you all for your help
took me 3 days to figure all of this out...
I have a Mt8s s2 stuck on yellow triangle, he don't know what version was on it originally, I tried the latest version BTU from sam firmware via Odin but its still the same, Ive looked at this post http://forum.xda-developers.com/showthread.php?t=1146532 and tried downloading the files from the link but I got some kind of installer loading all sorts of crap onto my computer, got it all uninstalled again and found the file I777UCKH7-CL503881-Parts-NoBL.7z to try but when I unzip it I get 5 files 3 ending with img, one with bin and another called zimage that Odin doesn't recognize.
Any hope for this phone, please advise what should be my next step.
Thanx
smspop said:
I have a Mt8s s2 stuck on yellow triangle, he don't know what version was on it originally, I tried the latest version BTU from sam firmware via Odin but its still the same, Ive looked at this post http://forum.xda-developers.com/showthread.php?t=1146532 and tried downloading the files from the link but I got some kind of installer loading all sorts of crap onto my computer, got it all uninstalled again and found the file I777UCKH7-CL503881-Parts-NoBL.7z to try but when I unzip it I get 5 files 3 ending with img, one with bin and another called zimage that Odin doesn't recognize.
Any hope for this phone, please advise what should be my next step.
Thanx
Click to expand...
Click to collapse
go HERE download latest firmware for your country and flash via pc odin. you will need to use 7zip or win rar to decomile the download and you will be left with ONE md5.tar file to use in odin. hope helped good luck
gaosphappy said:
go HERE download latest firmware for your country and flash via pc odin. you will need to use 7zip or win rar to decomile the download and you will be left with ONE md5.tar file to use in odin. hope helped good luck
Click to expand...
Click to collapse
As stated above I tried the latest version BTU from sam firmware via Odin ( CODE_I9100XXLSJ.tar ) (
CSC_HOME_OXX_I9100OXXLS1.tar ) ( MODEM_I9100XXLS6.tar ) is how it extracts and I flashed them with odin but still the same and wont boot to recovery, just boots to download mode.
still stuck on yellow triangle after flashing latest but it wasn't one package as above flashed code = pda modem = phone csc in csc in Odin. ?
That's jb leak.
PDA: LSJ
PHONE : LS6
CSC : LS1
Sent from the little guy
gastonw said:
That's jb leak.
PDA: LSJ
PHONE : LS6
CSC : LS1
Sent from the little guy
Click to expand...
Click to collapse
Can you point me to a full rom (single file) to flash via Odin I could try, as stated every version I have flashed it flashes with no errors but immediately boots back to yellow triangle cannot get it into recovery mode either to try to wipe the cahe and factory reset.
Am using a Jig to get it into Factory/Download mode which shows
Factory Mode
Product Code GT-i9100
Custom Binary Download Yes (1counts)
Current Binary Custom
Please Advise, Thank you.
Just tried this one
I9100XXKF2_I9100OXAKF2_I9100XXKF2.tar
<ID:0/021> Added!!
<ID:0/021> Odin v.3 engine (ID:21)..
<ID:0/021> File analysis..
<ID:0/021> SetupConnection..
<ID:0/021> Initialzation..
<ID:0/021> Get PIT for mapping..
<ID:0/021> Firmware update start..
<ID:0/021> boot.bin
<ID:0/021> NAND Write Start!!
<ID:0/021> Sbl.bin
<ID:0/021> param.lfs
<ID:0/021> factoryfs.img
<ID:0/021> zImage
<ID:0/021> hidden.img
<ID:0/021> cache.img
<ID:0/021> modem.bin
<ID:0/021> RQT_CLOSE !!
<ID:0/021> RES OK !!
<ID:0/021> Removed
But still get the same result.
Jb leak is a full ROM, which is what you need right now.
Make sure it's an I9100.
Get a couple of SII genuine cables.
Get 3 versions of Odin.
Reinstall kies.
Try all usb ports.
Try another pc/laptop.
Disable antivirus.
Sent from the little guy
UPDATED NAND FIX 2015
First of all I saw Some people saying Nand Write Fail And No Fix
Can Do it....!
Cygwin For Windows
NotePad++
7Zip
AABox
Odiin
your brick (i mean phone)
Stock Firmware or any TAR with 4file better
USB Drivers and all SAmsung Drivers
Getting Ready
Please Dont use Aabox Vit Packet 1 or SupperSS Nand if you are doing this Method
Cygwin - use as Linux Shell
Cygwin For windows
NotePad++ - for Editing All CodesNote Pad ++ Download
7 Zip for Open zipAnd Extracting Tar Md 5 and zips download here
AABOx for Verify and Sum CodingAA-box is need for coding rom for tar and its download link is not available at because of Under Maintenance and update. Its Ok i will guide you the coding manually
OdinWe Need Odin .85 or 65 if you have " AAbox 2 " its solved. odin3 1.85 download
UPDATING WAIT...!
//----------------------------------Below is old Post 1---------------------------------------------//nand write start fail on odin soluction
Tired of flashing with odin and fail....
What you need
Rom or firmware tar
Cygwin for windows
7zip
Odin3 1.3v
Device correct pit file
A good brain
Extract all files on tar to cywin home folder
Open cygwin and cd home
Then tar your files in this order
1.slb or blm or your bin file
2.boot
3. Modem
4. Cache
5. System
6.recovery
7. Others
Tar command
tar -c slb.bin modem.img cache.img system.img xxx.img xxxi.mg xxxxx.img >> repair.tar
And enter
Wait to finish
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Then flash it
Enjoy...
Note- Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
Press thanks if you done.
Mod Edit:- : Links Removed & Thread Closed.
ErickNoz said:
nand write start fail on odin soluction
Tired of flashing with odin and fail....
What you need
Rom or firmware tar
Cygwin for windows
7zip
Odin3 1.3v
Device correct pit file
A good brain
Extract all files on tar to cywin home folder
Open cygwin and cd home
Then tar your files in this order
1.slb or blm or your bin file
2.boot
3. Modem
4. Cache
5. System
6.recovery
7. Others
Tar command
tar -c slb.bin modem.img cache.img system.img xxx.img xxxi.mg xxxxx.img >> repair.tar
And enter
Wait to finish
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Then flash it
Enjoy...
Press thanks if you done.
Click to expand...
Click to collapse
Hey Erick, thanks for this. i was gonna post on XDA about that F.. NAN Write Start error that's been plaguing my soft bricked phone for days now.
I am all willing to try your solution but can you explain how you got to try that in the first place? What did you find about the NAND Write error that made you try this?
I am at best a journeyman at flashing phones, and what i heard so far on this error is that it was related to a hardware error: bad usb ports, bad cables, etc. Are you saying it is not related to hardware at all? - and what are the chances i brick my phone for good if i get one step wrong in your solution?
Updated
eniac0 said:
Hey Erick, thanks for this. i was gonna post on XDA about that F.. NAN Write Start error that's been plaguing my soft bricked phone for days now.
I am all willing to try your solution but can you explain how you got to try that in the first place? What did you find about the NAND Write error that made you try this?
I am at best a journeyman at flashing phones, and what i heard so far on this error is that it was related to a hardware error: bad usb ports, bad cables, etc. Are you saying it is not related to hardware at all? - and what are the chances i brick my phone for good if i get one step wrong in your solution?
Click to expand...
Click to collapse
Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
ErickNoz said:
Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
Click to expand...
Click to collapse
wow, i would not have figured that out, but it certainly explains why that error has started appearing so often in different threads and sites now.
I had stopped trying various ways to flash my phone to avoid doing something stupid but i think I'll give your method a try now that i understand where it comes from. I am not super eager to mess with pit files but i believe to have found the right one so I'll give it a try.
Thx.
eniac0 said:
wow, i would not have figured that out, but it certainly explains why that error has started appearing so often in different threads and sites now.
I had stopped trying various ways to flash my phone to avoid doing something stupid but i think I'll give your method a try now that i understand where it comes from. I am not super eager to mess with pit files but i believe to have found the right one so I'll give it a try.
Thx.
Click to expand...
Click to collapse
You are welcm... keep in mind friend don't us bad or different pit files u will be bricked.
Always keep in mind to have a breathing phone... if its dead .....you will have to use it as a paperweight.
So use correct pit
Use correct sbl and other bin files to flash
Ur bootloader or download mode is for wake up from sleep.. not done if dead.
If you press thanks button that my secret
ErickNoz said:
nand write start fail on odin soluction
Tired of flashing with odin and fail....
What you need
Rom or firmware tar
Cygwin for windows
7zip
Odin3 1.3v
Device correct pit file
A good brain
Extract all files on tar to cywin home folder
Open cygwin and cd home
Then tar your files in this order
1.slb or blm or your bin file
2.boot
3. Modem
4. Cache
5. System
6.recovery
7. Others
Tar command
tar -c slb.bin modem.img cache.img system.img xxx.img xxxi.mg xxxxx.img >> repair.tar
And enter
Wait to finish
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Then flash it
Enjoy...
Note- Nand fix error has 2 main reasons first is bad nand system... means when you flash a tar its writed or copied to device in a format eg: ext4 yaffs mtd or etc bt if your partion on devices is ext4 and you are tring to flash a mtd it will fail . Now some phone have been convected to internation like m110s to i9000 or m250s to i9100. So its file system also convected so ..... its done... with a perfect pit file. Go it..
And second is your tar file. If its compress highly it will try to stop or get slow to untar so timer out to flash.
Then stop as nand write. Flash it again with a new tar with same file remake tar again that's all..
Press thanks if you done.
Click to expand...
Click to collapse
Hi
Thank you for your possible solution. Unfortunately, I have never used Cygwin before, and I am not sure how to follow your steps. Is there any chance you could write the procedure in a little more detail?
I have been ROM Flashing for a while, but I have not tried this method for solving the NAND write problem. I have been trying to deal with this, since the KitKat release came out, but now, becaue I cannot upgrade, some of my apps have stopped working.
Thank you!
msl said:
Hi
Thank you for your possible solution. Unfortunately, I have never used Cygwin before, and I am not sure how to follow your steps. Is there any chance you could write the procedure in a little more detail?
I have been ROM Flashing for a while, but I have not tried this method for solving the NAND write problem. I have been trying to deal with this, since the KitKat release came out, but now, becaue I cannot upgrade, some of my apps have stopped working.
Thank you!
Click to expand...
Click to collapse
Can I know you device history before nand write
ErickNoz said:
Can I know you device history before nand write
Click to expand...
Click to collapse
I have a Samsung Galaxy N8000 bought in China about 2 years ago.
When I first got it, a flashed a couple of cyanogen honeycomb ROMS on there, but I since then reverted back to the original, especially since I got the notice that the N8000 would receive the KitKat upgrade. I reverted to a 4.1.2 ROM found on SamMobile and installed that one, german one I believe.
However, when I tried to do the OTA updates to Kitkat, the system updater downloads the package, starts the install, fails around 27% and reverts back to whatever was on before. Updating via KIES bricks the device, and flashing the ROM via odin gets the NAND write error.
Last time I did this, I ended up flashing the factory stock rom on the device using Odin 1.85 and then I have done the OTA upgraded up until 4.1.2 which I have now.
I have attached some screenshots, I hope they will give you the rest of what you might need. Let me know if there is anything else specific that you are looking for
Here is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Woooow Nand write
msl said:
I have a Samsung Galaxy N8000 bought in China about 2 years ago.
When I first got it, a flashed a couple of cyanogen honeycomb ROMS on there, but I since then reverted back to the original, especially since I got the notice that the N8000 would receive the KitKat upgrade. I reverted to a 4.1.2 ROM found on SamMobile and installed that one, german one I believe.
However, when I tried to do the OTA updates to Kitkat, the system updater downloads the package, starts the install, fails around 27% and reverts back to whatever was on before. Updating via KIES bricks the device, and flashing the ROM via odin gets the NAND write error.
Last time I did this, I ended up flashing the factory stock rom on the device using Odin 1.85 and then I have done the OTA upgraded up until 4.1.2 which I have now.
I have attached some screenshots, I hope they will give you the rest of what you might need. Let me know if there is anything else specific that you are looking for
Here is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Wooow this is the correct nand write fail caused by md5 or tar prob.
Only Use odin1.87 or 1.3 version
And untar ur md5 or tar firmware
Then tar back with the given order by me above 1st post.
It will be ok. Realy...
ErickNoz said:
Wooow this is the correct nand write fail caused by md5 or tar prob.
Only Use odin1.87 or 1.3 version
And untar ur md5 or tar firmware
Then tar back with the given order by me above 1st post.
It will be ok. Realy...
Click to expand...
Click to collapse
Hi
But, if it was a problem with the md5 or tar file, wouldn't everyone else also have the same problem? This md5 is from sammobile, it should be an official Samsung release, and I am sure thousands of others are using it.
Secondly,
How do I untar the file exactly, I have never done this before, I am not familiar with the software you describe in the original post.
Do you know where I can find instructions on doing this, or would you have time to write a very quick instruction ?
It sounds like I have to take the file apart and put it back together again.
Update
msl said:
Hi
But, if it was a problem with the md5 or tar file, wouldn't everyone else also have the same problem? This md5 is from sammobile, it should be an official Samsung release, and I am sure thousands of others are using it.
Secondly,
How do I untar the file exactly, I have never done this before, I am not familiar with the software you describe in the original post.
Do you know where I can find instructions on doing this, or would you have time to write a very quick instruction ?
It sounds like I have to take the file apart and put it back together again.
Click to expand...
Click to collapse
Use Cygwin for tar and untar
Install cygwin first google it
Or
Use Tar box by AFx
Hi, I downloaded a ROM from sammobile and I don't have all those files.
My files are:
boot.bin
cache.img
factoryfs.img
hidden.img
modem.bin
param.lfs
sbl.bin
zImage
Should I do like you said until the 4 (because I have the first 4 files from the tar command) and then write the others or I need to find one ROM that have system and recovery?
I hope my pit files is right too.
And another question:
I don't understand everything from this:
Now odin tick repartition update bootloader reset and autostart and pit
Pda your repair tar
Click to expand...
Click to collapse
1- Tick repartition
2- Update bootloader
3- Click reset
4- tick Auto reboot
5- Choose the downloaded pit file
6- Choose the created tar into PDA
Is it right? If yes, could you explain the "update bootloader" ?
Thanks
[Query] to same problem
eniac0 said:
Hey Erick, thanks for this. i was gonna post on XDA about that F.. NAN Write Start error that's been plaguing my soft bricked phone for days now.
I am all willing to try your solution but can you explain how you got to try that in the first place? What did you find about the NAND Write error that made you try this?
I am at best a journeyman at flashing phones, and what i heard so far on this error is that it was related to a hardware error: bad usb ports, bad cables, etc. Are you saying it is not related to hardware at all? - and what are the chances i brick my phone for good if i get one step wrong in your solution?
Click to expand...
Click to collapse
Hi There,
I have been struggling with same problem.. NAND WRITE FAIL
I had initiated a thread too in this context.
Want to know, if your attempt on device solved the problem ?
Thanks
Hi, ultimately no, i was able to depackage the rom but not fix it. It didn't have all the same components mentionned by erick and i wasn't sure how to compensate for the missing ones, were they mandatory, missing because obsolete, i don't know.
It gave me hope but it ended nowhere. Also all experts i contacted were not able to fix it and samsung won't even touch it because it was rooted.
I am thinking about putting a bounty on xda here to hire some help.
didnt fix n7100
Hi I couldnt find the boot.bin on extracrting 3 different md5 files. However, i did the steps as told but didnt work i make the repair.tar with cygwin .
vmware fusion for macos
Had the same issue using a virtual machine via vmware fusion for macosx. I switched for parallel desktop then flashed the last stock firmware and right pit file (repartition thicked).
At first boot possible boot loop on Samsung logo but resolved by wipe data / factory reset with stock cwm.
My phone's issue ended up being the eMMC chip busted. Had the phone repaired for about 150$, which i thought was cheaper than a new Note 2.
Solution
msl said:
I have a Samsung Galaxy N8000 bought in China about 2 years ago.
When I first got it, a flashed a couple of cyanogen honeycomb ROMS on there, but I since then reverted back to the original, especially since I got the notice that the N8000 would receive the KitKat upgrade. I reverted to a 4.1.2 ROM found on SamMobile and installed that one, german one I believe.
However, when I tried to do the OTA updates to Kitkat, the system updater downloads the package, starts the install, fails around 27% and reverts back to whatever was on before. Updating via KIES bricks the device, and flashing the ROM via odin gets the NAND write error.
Last time I did this, I ended up flashing the factory stock rom on the device using Odin 1.85 and then I have done the OTA upgraded up until 4.1.2 which I have now.
I have attached some screenshots, I hope they will give you the rest of what you might need. Let me know if there is anything else specific that you are looking for
Here is the Odin Log
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I had the same problem until 5 minutes ago and you can solve it by:
Going to
-Developer options-
Allow "USB debugging"
Uncheck the "Veify apps via USB" box
Let me know if it works
Kind regards
SM-N910C
4.4.4
Odin3 v3.07
CF-Auto-Root-trelte-treltexx-smn910c.tar.md5
Svenarchy said:
I had the same problem until 5 minutes ago and you can solve it by:
Going to
-Developer options-
Allow "USB debugging"
Uncheck the "Veify apps via USB" box
Let me know if it works
Kind regards
SM-N910C
4.4.4
Odin3 v3.07
CF-Auto-Root-trelte-treltexx-smn910c.tar.md5
Click to expand...
Click to collapse
I can't acces developers options because my device is soft bricked. I downloaded the jelly bean firmware because that what firmware the device was on (I believe) a year ago when I rooted the device for a co worker the link is here http://galaxynote3root.com/galaxy-note-3-stock-firmware/ any help would be marvelous so I can unbrick this darn phone TIA
I dont understand these instructions they are too advanced. The title of this post looks very promising as I am basically in an emergency to get my phone fix due to the NAND write fail issue but the OP does not state any helpful information including download links, where to get the files from, which files they are, what to do rather than one word instructions :S - We come on here expecting to get help (and to help others) so please somebody reply to me on what I have to do to get this fixed. (ask me for details if you are kind enough to help)
Thank you.
hey guys,
I don't have a recovery mode (getting white screen instead). only download mode.
I downloaded the correct firmware and tried install and it failed (in system.img) and requested a PIT file.
I downloaded the PIT file and it got failed again.. I tried to install this twrp thing and still not good.
This is what I get when I try to install pit + twrp (auto reboot, re-partition and f. reset time are checked):
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
Edit:
I've tried with the nand checked aswell and got this:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea?
Thank you guys!
Have you tried different cables, are you using a USB port on the motherboard?.
The drivers work because it sees the phone in odin.
Are you loading the stock firmware AND the pit file at the same time?.
If you can answer yes to all of those then it's a bin job.
I don't recommend trying to flash a pit and TWRP at the same time. I only recommend using a pit file, when necessary, with stock firmware.
shivadow said:
Have you tried different cables, are you using a USB port on the motherboard?.
The drivers work because it sees the phone in odin.
Are you loading the stock firmware AND the pit file at the same time?.
If you can answer yes to all of those then it's a bin job.
Click to expand...
Click to collapse
Yes, tried a different cable.
Yes, I used a USB port on the motherboard
Yes it's a stock, and tried separately and didn't work.
Damn
audit13 said:
I don't recommend trying to flash a pit and TWRP at the same time. I only recommend using a pit file, when necessary, with stock firmware.
Click to expand...
Click to collapse
I tried to use only the pit but all i get is that error. It didn't matter if I used a TWRP / stock firmware.
Don't flash using only the pit file.
Flash twrp or stock ROM without pit.
If flashing the stock firmware on its own fails or it says about a pit partition in odin then load both the pit file and the stock firmware at the same time. If it fails to flash them you can safely assume the phone has a corrupt nand and is dead.
You can also try flashing older versions of the recovery, twrp or cwmr. The last official cwmr was the most stable for me and helped me recover from a f*ked twrp that caused the e:failed to mount errors.
If it can take a flash of any type it might be recoverable. Just because it fails a flash doesn't mean its dead dead, just borked beyond the usual capability of the average Joe bloggs..
I would recommend, just for the fact it can't get any worse than what it already is, find the stock firmware in separate files along with the last official cwmr and flash them one by one and when you get the fail errors you'll know exactly what part of the nand is faulty. Basically just mess with it until you kill it. If it jumps into life in the meanwhile then you got lucky and should put a ticket on the lottery!.
Hope this helps inspire a bit of confidence!.
audit13 said:
Don't flash using only the pit file.
Flash twrp or stock ROM without pit.
Click to expand...
Click to collapse
I tried it, didn't manage to succeed.
shivadow said:
If flashing the stock firmware on its own fails or it says about a pit partition in odin then load both the pit file and the stock firmware at the same time. If it fails to flash them you can safely assume the phone has a corrupt nand and is dead.
You can also try flashing older versions of the recovery, twrp or cwmr. The last official cwmr was the most stable for me and helped me recover from a f*ked twrp that caused the e:failed to mount errors.
If it can take a flash of any type it might be recoverable. Just because it fails a flash doesn't mean its dead dead, just borked beyond the usual capability of the average Joe bloggs..
I would recommend, just for the fact it can't get any worse than what it already is, find the stock firmware in separate files along with the last official cwmr and flash them one by one and when you get the fail errors you'll know exactly what part of the nand is faulty. Basically just mess with it until you kill it. If it jumps into life in the meanwhile then you got lucky and should put a ticket on the lottery!.
Hope this helps inspire a bit of confidence!.
Click to expand...
Click to collapse
Hahaha thanks mate, I guess I'll just give up and deliver this phone the place it belongs - hell!
Thanks for the help tho, It will be easier to win the lottery as you wrote