Related
Hello,
My Galaxy s2 is stuck in boot loop, I can see only the GS2 logo.
It went into this situation after holding down power button trying to turn it off.
Tried to remove battery and nothing changed.
Entered recovery mode and did wipe cache and then reboot.
It went past the initial logo, showed samsung animation and then it went back to samsung logo boot loop. It never went to samsung animation again.
From that point on it does not boot to recovery mode, it shows the android robot with the spinning cog for a while and then it goes back to the samsung logo boot loop.
The phone can go to download mode without problem. I have not tried to install a stock firmware through odin, since I would like to get a backup of the sms messages from the phone first. I already have backup of pics, contacts, etc so I dont care about anything else besides the sms.
The phone was running the latest spanish stock JB version
GT-I9100 Galaxy S II
PDA: I9100XWLSD
CSC: I9100FOPLS4
MODEM: I9100XXLS8
Added: 2013-02-03
The only modifications to stock were
. Root when it was running ICS
. CSC change from EUR to FOP (so that it auto upgraded to JB from ICS)
The phone retained root after the auto JB upgrade
Do you know if there a solution to this situation? I am still under warranty so I can take it back to samsung so I would like to avoid installing CWM recovery kernel that would make them immediately reject service due to warranty void.
thank you in advance!
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Hopper8 said:
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Toliver said:
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Click to expand...
Click to collapse
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Hopper8 said:
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Click to expand...
Click to collapse
Ok then, I will give it a try and see how it goes. Another solution that I was thinking about is to try to install CWM through odin (i'm not sure if it's possible though) then boot into CWM and get backup through it. Then if I apply a stock firmware through odin, this would remove CWM and install the stock recovery kernel back, correct?
Yes, that's possible. You can flash Philz kernel via Odin, it's stock kernel only with root CWM. Other than that its the same. You could do that procedure using his kernel. When you flash stock rom via Odin then yes, you'd get rid of the custom recovery.
Depending on what you want to do (warranty etc) read up about the flash counter and then triangle away.
Sent from a galaxy far, far away
regarding the 1-part firmware, I downloaded from sammobile the I9100XWLSD_I9100FOPLS4_FOP.zip.
The zip archive contains a tar.md5 file I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 and a dll file SS_DL.dll.
So I should use only the tar.md5 in the PDA section of odin, right? should I keep this dll in the same folder as the tar.md5 in case odin needs it?
Also does it make any difference which odin version should I use?
thaks again
Well I suppose it can't hurt to put it in the same directory, but I don't know if it really does anything. Yes, flash it in the pda section.. Which version? Take your pick. I usually use 3.0.4 but have also used others. Click my signature if you want a zip file with a few versions.
Sent from a galaxy far, far away
I tried flashing the same rom as it was installed but nothing changed, after the first boot I see the robot with the cog, a thin progress bar filling below it and then it goes to boot loop. No luck getting into recovery, still the same symptom... Besides the sms backup I am thinking about how to recover it, should I try installing 4.0.3 that was the factory default? Any more ideas??
thanks again
The odin log seems clean though, no error or anything else
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> boot.bin
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> zImage
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Hopper8 said:
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Could you provide more details on how to do a factory reset from stock recovery? Do you mean to flash 4.0.3 via odin? Or is it some options in odin that would enforce factory reset?
More details are to search for it mate. It's covered so many times that it's just plain spoonfeeding if I'm to post it.
Sent from a galaxy far, far away
Eventually I made it work by installing the 4.0.3 EUR via odin. I did not allow it to boot into the OS, as soon as it finished flashing via odin, I rebooted into recovery mode. This time it went in successfully. Then I used the CWM recovery kernel that just runs from the sd (it does not install) and got the full backup. Later on by using nandroid manager I recovered the sms messages + more (apps, etc). Thanks for all the help!
Hey Guys,
I'm sure all of you get lots of these questions, however I have been trying for a couple of days to get this S3 going so I can just asking for help.
My main issue is I cannot flash any ROM's via Odin.
Here is some background infomation:
I started with a stock Galaxy S3 GT-i9300 International 16GB model.
Flashed the correct version of Cyanogen Mod for my Model/Sub Model.
I install this rom by flashing CWM (Clock Work Recovery Mod) and installing the update.zip from my external SD card.
I have done this before with other Samsung devices, No big deal, just factory rest and wipe the davik cache and flash the new ROM.
Well I decided to backup the original ROM via CWM's backup option. The backup completed fine but I backed it up to the phones internal storage instead of my External SD card. The new ROM worked fine till it ran out of space. So I selected the Delete option back in CWM to remove the backup file, rebooted the phone only to find I was still using 8 or so GB of storage.
So my phone was not happy. No room to download updates or save new pictures, etc.
This week I decided to flash the stock ROM back over the phone. For some reason the firmware was incorrect for that model or something was wrong with the phone.
After looking around I decided to flash a .pit file for the Galaxy S3, One problem, I did not know that different storage sizes of S3's have different .PIT files. However it flash and I still could not restore my phones ROM.
So after a few days of looking around I downloaded the stock ROM from Sam-Mobile.com for my phone and country and download GT-I9300_mx_20120220 PIT for for what I read and understood was for a 16GB GT-I9300.
So the new PIT file flashes fine, however I still cannot flash any new ROMS. I have tired the stock rom from Sam-Mobile or trying to flash Recovery-cwmtouch-6.0.3.2-GTI9300.tar (clock work recovery mod).
None of these flash. Odin3.04 just sits on "NAND Write Start!!" and there is a blue "downloading" bar that is across the screen and that's it.
Nothing else happens. I have also attached a screen shot of this.
I have a water damaged 16GB GT-i9300T that I have used to create a .PIT file from Heimdall, But that sits there for about 10 Min before Odin says "Unable to get pit map"
I have also tried this: http://forum.xda-developers.com/showthread.php?t=1916796
I get all the way to shorting out the resistor (R313) on the PCB but the phone does not turn on and fails to display "SD Card Mode"
So, can anyone help me?
I know it might be a long shot but at this point I'm willing to try anything. Any ideas would be much appreciated.
Cheers
Mitchell
Flashing just a pit file usually results in a hard brick.
You can try a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=2665989794768393
But you probably need a new motherboard.
Thanks for that!, The recovery firmware failed to flash but the pit file flashed allowing me to install Cyanogen Mod.
Thanks for your help on this one :good:
boomboomer said:
Flashing just a pit file usually results in a hard brick.
You can try a rescue firmware:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=2665989794768393
But you probably need a new motherboard.
Click to expand...
Click to collapse
I. Need help to...my s3 its stuck at samsung logo. I dont have recovery. Just download Mode..i try to flash pit and no flash. Roms nand write fail. Some pits just say get pit mapping but nothing happens. Kies dont flash just 0%...how can i unbrick the iPhone please need help
Did u fix !!!
leo_hacker82 said:
I. Need help to...my s3 its stuck at samsung logo. I dont have recovery. Just download Mode..i try to flash pit and no flash. Roms nand write fail. Some pits just say get pit mapping but nothing happens. Kies dont flash just 0%...how can i unbrick the iPhone please need help
Click to expand...
Click to collapse
Did u fix ur phone??? same problem happend me
You're using the original Samsung USB cable?
audit13 said:
You're using the original Samsung USB cable?
Click to expand...
Click to collapse
yes.
What file is failing in Odin?
jtk585 said:
Did u fix ur phone??? same problem happend me
Click to expand...
Click to collapse
For getting error when flash in Odin no matter what kind of error. Just need to flash out and repartition it for pit file and you get back yours phone back. The problem is the pit file must be suit to flash your phone. If not no matter how you flash it still the same.
Yumiko87 said:
For getting error when flash in Odin no matter what kind of error. Just need to flash out and re-partition it for pit file and you get back yours phone back. The problem is the pit file must be suit to flash your phone. If not no matter how you flash it still the same.
Click to expand...
Click to collapse
thanks.
i tried many time. i try to do partition also. that time partition error is occur.
i connect with kies, i tried recovery , firmware not downloadind to my device it's stuck on 0 % , then i use that download original firmware that file in odin v3.9 , to v 11 :laugh: tried all odin. i think emmc is corrupted..!!
anyway my phone is bricked so i used every button on odin ...:laugh::laugh:
i tick T.Flash ,that time no error occur, downloaded , but nothing happened.
thanks. any chance to enable debugging mode in recovery mode.
jtk585 said:
thanks.
i tried many time. i try to do partition also. that time partition error is occur.
i connect with kies, i tried recovery , firmware not downloadind to my device it's stuck on 0 % , then i use that download original firmware that file in odin v3.9 , to v 11 [emoji23] tried all odin. i think emmc is corrupted..!!
anyway my phone is bricked so i used every button on odin ...[emoji23][emoji23]
i tick T.Flash ,that time no error occur, downloaded , but nothing happened.
thanks. any chance to enable debugging mode in recovery mode.
Click to expand...
Click to collapse
So now you still able to go download mode without error? I mean when you connect to odin it's work for You?
Yumiko87 said:
So now you still able to go download mode without error? I mean when you connect to odin it's work for You?
Click to expand...
Click to collapse
thanks
download mode working perfectly . all time.
odin only install my device when i tick T.flash. i cant install normal way
after installation nothing change. that is it.
actually i don't know what is the use of T.Flash :laugh:
thanks
jtk585 said:
thanks
download mode working perfectly . all time.
odin only install my device when i tick T.flash. i cant install normal way
after installation nothing change. that is it.
actually i don't know what is the use of T.Flash [emoji23]
thanks
Click to expand...
Click to collapse
So the installation successful until come out with pass in Odin? But it's doesnt change is revert to download mode?
Yumiko87 said:
So the installation successful until come out with pass in Odin? But it's doesnt change is revert to download mode?
Click to expand...
Click to collapse
yes PASS..! but nothing change on device
if i going to change motherboard, is my device work?
can i install any country firmware ?
bcoz motherboard get under 30 dollar. i know how to fix
so total cost is 30 cowboy:
i forget say one thing, when i choose boot loader file BL sboot.bin file is stuck... freeze.....
jtk585 said:
yes PASS..! but nothing change on device
if i going to change motherboard, is my device work?
can i install any country firmware ?
bcoz motherboard get under 30 dollar. i know how to fix
so total cost is 30 cowboy:
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726
Click to expand...
Click to collapse
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726[/QUOTE]
thanks..
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is happening my device.
i think emmc is corrupted or my bootloader is locked.. nothing write on
jtk585 said:
Pls refer to this before you go for hardware issues.
http://forum.xda-developers.com/showthread.php?t=2120726
Click to expand...
Click to collapse
thanks..
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sboot.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is happening my device.
i think emmc is corrupted or my bootloader is locked.. nothing write on [/QUOTE]
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.
The sboot.bin file is not flashing because the rom is either not for the phone or the phone bootloader is too new.
Are you a using the original USB cable?
audit13 said:
The sboot.bin file is not flashing because the rom is either not for the phone or the phone bootloader is too new.
Are you a using the original USB cable?
Click to expand...
Click to collapse
Thanks..
yes dude
Original USB Cable
S3 GT-I9305 LTE
Kit kat 4.4.4. EVR EE Europe international Firmware
i did root this phone
i think bootloader not allowed to write anything on it or corrupted
what you think ??
---------- Post added at 09:59 AM ---------- Previous post was at 09:56 AM ----------
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.[/QUOTE]
can i use this pit or firmware on my GT-I9305 device
is it work?
thanks
jtk585 said:
Thanks..
yes dude
Original USB Cable
S3 GT-I9305 LTE
Kit kat 4.4.4. EVR EE Europe international Firmware
i did root this phone
i think bootloader not allowed to write anything on it or corrupted
what you think ??
---------- Post added at 09:59 AM ---------- Previous post was at 09:56 AM ----------
Try both:http://cloud.tapatalk.com/s/580ff78a7f0a7/N9005XXUENB4_N9005DBTENB1_DBT_PIT.zip
http://cloud.tapatalk.com/s/580ff790b5dbe/SM-N9005 OXX pit.zip
If still failed sry to tell you need to change motherboard aredy. As I faced such issues on my n3 and I able to recovery well using my pit files via Odin without fail. So might be your hardware problem aredy.
Click to expand...
Click to collapse
can i use this pit or firmware on my GT-I9305 device
is it work?
thanks[/QUOTE]
This will only for n9005. Not 9305.
I will not go into detail but suffice to say I was running my Samsung Galaxy S3 GT-I9300 on a stock Samsung Android 4.1.2 ROM and it was rooted and had a custom CWM Recovery.
I then flashed to CM 10.0.0 but encountered problems and tried to revert to my original ROM. This resulted in my phone displaying the initial black background boot screen with the words "Samsung Galaxy SIII GT-I9300". It stuck there and I could not switch it off nor could I get into Recovery Mode.
I was able to get into Download mode and connect to Odin to reflash my original ROM but Odin continually got stuck in the process at "Setup Communication" and on the odd occasion it got past that it then stuck on "Get Pit Mapping".
After much research of this and other forums found one lone article about Samsung introducing new ROMS from July 2013 onwards which had efs2 and that once upgrading to an efs2 ROM you could not go back to a previous efs1 ROM which I think I tried to do.
I eventually decided therefore to bite the bullet and I downloaded GT-I9300.pit and flashed it using Odin with Re-Partition selected. I was then able to flash Samsungs latest Android 4.3 (I9300XXUGMK6) ROM for the I9300.
The result is that whilst the phone is again fully functional I am unable to install a custom recovery nor can I root my phone.
I thought that if I used the GT-I9300.pit file it would re-partition the phone as a I9300 should be partitioned but it seems I was wrong.
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
matrixmainframe said:
I am happy with my phone now that I have recovered it but would like to be able to backup my rom but I need root to do that. Does anyone know what I have done with my phone and are you able to advise as to how I might now root it again?
Thanks
Click to expand...
Click to collapse
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
ag4751 said:
After flashing the stock rom when coming from a custom rom is always best to do a factory reset to clear the phone.
You can root with CF auto root from my signature it works perfectly well on stock 4.3 MK6, then use TWRP or Philz recovery both are in the Dev section
Click to expand...
Click to collapse
When I try to flash a recovery or try to root I get the following.
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-m0-m0xx-gti9300.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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
As you can see from the above it looks as though the process falters at "<ID:0/003> Get PIT for mapping.." which would appear to have something to do with the fact that I had to re-partition using GT-I9300.pit and that is what prompted my question in the first place.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
matrixmainframe said:
When I try to flash a recovery or try to root I get the following.
It appears to me that the GT-I9300.pit file has altered my partitions in a non I9300 way despite having I9300 in the filename and that is why I posted the question in the hope someone would know what I had done and hopefully know a way I could either reverse what I had done or suggest a way to root despite my apparently new partition format?
Click to expand...
Click to collapse
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
ag4751 said:
Have a look here then you my be able to recover your device, it is Korean based so will default to KOR not BTU but it could repair the PIT problem if that is what you have.
Click to expand...
Click to collapse
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
That problem in Odin might be related to incorrect drivers for your phone.
Remove any kies or Samsung softwares and reboot pc. Reinstall kies and connect phone 2 pc for drivers install. Then try a different usb port to flash smth on the phone.
Trimis de pe al meu GT-I9300 folosind Tapatalk
matrixmainframe said:
Please read my initial post(#1).
I have already recovered my phone and it is working correctly on Samsung Official Stock 4.3 ROM (Android 4.3 - I9300XXUGMK6) EXCEPT that I cannot flash a custom Recovery nor can I root the phone. I have several apps that only operate on a rooted phone so just rooting it without a custom recovery would suffice.
If someone tells me that it is no longer possible to root my phone then I will be disappointed but I can live with it. I just thought someone might know the answer.
Click to expand...
Click to collapse
I think i had the same problem with rooting and done reinstalling drivers and change the port so it is now rooted.
Also try unticking autoreboot then after the instalation is done disconnect the phone and remove/reinsert battery and boot to recovery so the auto root files start to install...
Of course everything you do is at your own risk...
BR
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.
Hi Guys, have spent last 6 days on the forums, endless hours of reading and downloading hours of different firmwares day and night and trying everything i possibly could before finally resorting to posting a thread as i have now completely given up. I am a bit of noob to the forums but have been using this place for many years and with quite a lot of success with many samsung phones over last few years upto my very own note4 recently, but this galaxy s6 edge seems to have defeated me.
plz plz plz help, any help and info much appreciated.
i am trying to fix this phone for my 16 year old cousin who gave it to me in a bricked state and not quite sure exactly what he had done to it, as hes not too sure what he was trying to do whilst trying to root or install a new rom/firmware.
have tried many stock firmwares from sam-mobi site but odin just fails to flash them, then having read many threads have realised that it must be something to do with bootloader or boot locked and maybe im trying the wrong firmware, problem is i dont know what firmware is on there before it was given to me in this bricked state.
then tried the twrp flash which seemed to do something as now the screen shows
RECOVERY IS NOT SEANDROID ENFORCING
so did more reading on this issue and tried various things from different threads and post fixes but still stuck. and kept getting the red sw rv binary or something message in the fone after each failed flash
then read somewhere to get the Indian stock firmware version and delete the MD5 part of the file and then extract and delete the img file named hidden and then repack using the toolkit from here which creates new tar file. then re flashed again odin. but still no success as now getting get pit file error from odin
:crying::crying::crying::crying::crying::crying:
i now have the blue screen that says
"an error has occurred while updating the device software. Use the emergency recovery function in the smart switch pc software"
I have tried smart switch too but cant get fone to recognise or connect to software.
I can get into download and odin mode no problem but the information showing on there seems to be different to what i remember first seeing when the fone was given to me, as few days back the knox warranty void was showing as 0 but now showing as 1 (0x304) i remember current binary being : SAMSUNG i think but now showing as : Custom
I Just tried flashing the following stock rom as it came from sam-mobi : G925FXXU2COH2_G925FBTU2COH3_BTU
and now getting this from odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
so do i need the pit file now too? or a firmware download that has all the BL AP CP CSC files seperately? im sure i tried this a few days ago too with all the seperate files in odin but no joy
what do i need to do just to get this phone back to stock and up an running??
I am not bothered about rooting or what version of firmware it is, just as long as we can get the fone working again.
is it something to do with knox being triggered ?
is it something to do with wrong bootloader or something ?
or am i just flashing the wrong files ?
sorry about the long essay, just letting you guys know as much info as possible as to what i have done so far and maybe help in diagnosing where i have made mistakes or gone wrong.
all help much appreciated and many thanks in advance, please guys let me know what im doing wrong or what i need to do right?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just tried the firmware from another post on here, the megaman download link which gives firmware files for both galaxy s6 and galaxy s6 edge.
once extracted it gives the 4 seperate files for odin
BL
AP
CP
CSC
just tried that and now getting the same pit file error....
what pit file do i need and can i use any pit file for any firmware as most firmwares come without the pit files and u just select the ap or pda file and just flash.
where can i get the correct stock firmware for SM-G925F galaxy s6 edge with the pit file too? and the do i need to tick or check the re-partition in odin?
plz plz plz plz someone help
From sammobile got this firmware G925FXXU2COH2_G925FBTU2COH3_BTU and extracted to get the following file below
G925FXXU2COH2_G925FBTU2COH3_G925FXXU2COH2_HOME.tar.md5 thats the extracted file i get after using winzip
also tried using with this pit file ZEROLTE_EUR_OPEN_HIDDEN100M.pit
tried all above in odin
and now i get this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLZ PLZ PLZ PLZ someone help???:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
also now have the red message in phone screen
[CW] SW REV. CHECK FAIL. DEVICE: 3, BINARY :2
SEE IMAGE BELOW
should i be trying 5.02 stock firmwares ? or 5.1.1 stock firmwares from sammobile site?????????
1. what phone? G925F (or FD/K/I/T/L/S)?? 2.which country??? 3. Branded or unbranded??? 4. Android 5.0.1 or 5.1.1??? ....if you know what kind it is then you download right firmware and flash it with odin.
It is a SM-G925F
I am currently in Uk
Not sure what branded it is but im not bothered just as long as i get it working again..
And im not sure what firmware version it was before it got to this state...
It was given to me in this bricked state so not sure what version it was on or what version of software it is...
I just assumed from many past experiences just to get a stock version of firmware for this handset and flash with Odin, have been doing the same for many many years from sammobile site... But this just doesn't seem to be working
I noticed you tried using COH2/3 firmware file, that's not old, but there are newer out there.
So, have you already tried with a more recent firmware? It's not necessary for it to be an UK firmware (I'm italian and I flashed a French, English and Poland firmware on my branded 925F, so don't worry).
There's the possibility that your phone actually uses a fw that's newer than COH2, so Odin check fails.
Then, first of all download one of the most recent firmwares (this is great, for example http://www.sammobile.com/firmwares/download/62435/G925FXXU3QOLB_G925FWFA3QOL1_XFA/) and try to flash it.
If it doesn't work, we'll try to get a different solution...
Thats what i was considering doing next but not sure which firmware to go for...
I was coming to the conclusion that no matter what firmware im trying to flash that ifs not going to work as something must be missing or wrong with the fone before it can just be flashed as it doesn't seem to be taking any flashed firmware...
Like maybe it was rooted before and needs unrooting or something?
Or maybe it can only take a certain type of older firmware as doing so much reading ive come across something about locked bootloaders and not being able to downgrade back or something?
Im just so confused and lost now after 6 days of trying all sorts..
Surely there is an easy way? Someone out there definitely knows please?
I am coming to the harsh realisation that it is definitely something to do with my bootloader?
after much more reading im realising that i am in some sort of bricked mode because of the bootloader that maybe on there is part of 5.1.1 firmware...
can i reflash or just fix my bootloader with correct bootloader files ? or is there correct stock firmware for the bootloader that maybe on my phone??
i dont know what firmware or bootloader is currently on phone so where can i go from here please ?
what bootloader for stock firmware?
I also have no recovery mode???
i cant get into any recovery mode?
im thinking my bootloader files are wrong which is why i cant flash the correct stock firmware files.
can someone pleae tell me if my thinking is correct
is there any sepcific bootloader and modem files that i need to flash first and then the relevant or correct stock firmware files to flash in odin?
what im asking is that do i have to flash the correct bootloader files and then a specific stock firmware file for that bootloader?
and what do i do about having no recovery mode?
all i want is the phone to get back to stock and working please ???
Nicolò98 said:
I noticed you tried using COH2/3 firmware file, that's not old, but there are newer out there.
So, have you already tried with a more recent firmware? It's not necessary for it to be an UK firmware (I'm italian and I flashed a French, English and Poland firmware on my branded 925F, so don't worry).
There's the possibility that your phone actually uses a fw that's newer than COH2, so Odin check fails.
Then, first of all download one of the most recent firmwares (this is great, for example http://www.sammobile.com/firmwares/download/62435/G925FXXU3QOLB_G925FWFA3QOL1_XFA/) and try to flash it.
If it doesn't work, we'll try to get a different solution...
Click to expand...
Click to collapse
Just downloaded and tried the firmware u posted in above link....
1st attempt :
odin passed it and started flashed,, it was actually doing something for a few minutes much better than normal and seemed like it was flashing the file, i got really happy as never got it to work this much before as it would usually just fail within a few seconds but then about a few minutes later at abut 40% the green bar at almost halfway through it failed again :crying::crying::crying:
it failed whilst doing something with the system file stage
2nd attempt:
thought i wud just try it again and this time it went almost all the way and at around the end 99% and green bar almost finished at end in odin and could see the download bar on the fone almost finished on the fone too it failed again at the hidden file stage
DAMN MAN !!! FELT LIKE IT WAS ALMOST THERE
see odin log below :crying::crying::crying:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<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> cm.bin
<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)
Okay so i edited the tar.md5 file from above posters recommended firmware and removed the file named hidden and repacked it using the unified android toolkit to create another flashable tar file but this time obviously without the hidden img file inside
used odin to try and flash the newly created tar file....
it failed about 6 times all at different stages, sometimes at begining and sometimes halfway through and sometimes towrards end..
on 7th attempt i changed usb port and it successfully flashed and passed the file.
phone rebooted and is now just stuck at the samsung galaxy s6 edge logo powered by android stage
havent touches the phone since in the hope it might just load up and start as usually after a flash it does take foerever to boot up again....
or am i mistaken? and because the hidden img file has been removed from the flash it wont continue???
is there a way or do i need to re flash just the hidden img file ?
shall i create a tar file from the hidden img file and if so which tab wud i need to flash it in odin?
I'm just reposting my answer from your other thread. Try flashing Odin falshable philz recovery. There is always hope if u can boot into recovery.
Ok so nothing happened after i successfully flashed the created tar file with the hidden img file removed.
Just stuck at samsung logo.
Then tried samsung smart switch pc software...
Usually wud always crash at 98% downloading to phone stage but this time went all the way and completed 100%
Phone went to reboot and now stuck in continuous reboot
Keeps rebooting at samsung logo stage...
What the hell an i doing wrong?
Or where is the flash process going wrong?
icecoolpsyco said:
Okay so i edited the tar.md5 file from above posters recommended firmware and removed the file named hidden and repacked it using the unified android toolkit to create another flashable tar file but this time obviously without the hidden img file inside
used odin to try and flash the newly created tar file....
it failed about 6 times all at different stages, sometimes at begining and sometimes halfway through and sometimes towrards end..
on 7th attempt i changed usb port and it successfully flashed and passed the file.
phone rebooted and is now just stuck at the samsung galaxy s6 edge logo powered by android stage
havent touches the phone since in the hope it might just load up and start as usually after a flash it does take foerever to boot up again....
or am i mistaken? and because the hidden img file has been removed from the flash it wont continue???
is there a way or do i need to re flash just the hidden img file ?
shall i create a tar file from the hidden img file and if so which tab wud i need to flash it in odin?
Click to expand...
Click to collapse
The bootloop after odin is a tipical issue.
When I encountered it, i rebooted into recovery mode (stock recovery) by holding Volume Up + Home + Power, then I wiped data, cache and dalvik.
So, if s6 is still rebooting:
Presso Volume Down + Power until the screen goes black, then speedly press Volume Up + Home + Power.
If these method doesn't work, flash twrp recovery by odin, wipe data, system, cache, dalvik and flash a custom rom (xtrestolite suggested, just cause it's only 480 mb).
Reboot into custom rom and then do whatever you want!
Thanks for that...
Will try that now...
But i cant get into any recovery mode?
Shall i just flash twrp recovery in odin? Where shall i place the flash file in odin? In AP?
And then where shall i flash the custom rom u suggested as this phone doesnt have removable SD memory card
Can i just flash the custom rom in odin too?
icecoolpsyco said:
Thanks for that...
Will try that now...
But i cant get into any recovery mode?
Shall i just flash twrp recovery in odin? Where shall i place the flash file in odin? In AP?
And then where shall i flash the custom rom u suggested as this phone doesnt have removable SD memory card
Can i just flash the custom rom in odin too?
Click to expand...
Click to collapse
First find the Odin flashable file of twrp, then flash it using Odin (AP). Download the Rom and transfer it to a flash drive. Twrp supports otg. Connect it to your phone using otg cable. Restart your phone and swiftly press the volume up+home+power button to boot into recovery. Mount otg from Mount option. And install the Rom.
Ok got most of that so far and makes sense i think.
But is there any other way if i dont have an otg cable?
icecoolpsyco said:
Ok got most of that so far and makes sense i think.
But is there any other way if i dont have an otg cable?
Click to expand...
Click to collapse
After booting into recovery, connect it to a pc. It should recognize the phone. Transfer the Rom to the internal storage.
---------- Post added at 05:17 PM ---------- Previous post was at 05:10 PM ----------
If that doesn't work too, you can use adb method. I have never used that method but I know you can do it.
Thanks... Will try that now and update soon...
What is the adb method? Via pc?
Can anyone point me in the right direction of the best place and latest twrp file?