Solve it.
boot into recovery and flash the rom again or factory reset
Solve.
Oh my lord. Finally i'd done it by myself. Now my phone live back!!! Anyway, thanks for the help man. I appreciated it. =)
henrylhp said:
Oh my lord. Finally i'd done it by myself. Now my phone live back!!! Anyway, thanks for the help man. I appreciated it. =)
Click to expand...
Click to collapse
Share the solution?) It's always interesting!
Oh, hmm, i can't start my phone before because i follow a guide that teach how to upgrade firmware, and download file with it, but it teached me to click at the Re-partition, and the firmware file that he ask me to download, got problem. So, after i follow what he teached, and my upgrade failed. That's make my phone can't boot or works. AFter that i keep on searching and searching, and found that i don't have "cache" or others setting inside my phone, and that's all are inside the" PIT" file, so i download a PIT file, and install it with Odin, by put it in the "PIT" setting, but don't click at the Re-partition. Haha, now, my phone live back. =) Of course, i download others firmware version too, and install it again.
PIT file?
henrylhp said:
Oh, hmm, i can't start my phone before because i follow a guide that teach how to upgrade firmware, and download file with it, but it teached me to click at the Re-partition, and the firmware file that he ask me to download, got problem. So, after i follow what he teached, and my upgrade failed. That's make my phone can't boot or works. AFter that i keep on searching and searching, and found that i don't have "cache" or others setting inside my phone, and that's all are inside the" PIT" file, so i download a PIT file, and install it with Odin, by put it in the "PIT" setting, but don't click at the Re-partition. Haha, now, my phone live back. =) Of course, i download others firmware version too, and install it again.
Click to expand...
Click to collapse
Where did you get the PIT file?
Hello,
as you stand tablet / GT-N8000 / went out like battery fell while trying to turn it on again started to load only the logo Samsung.Put some rom, but the result was the same. After trial runs as he showed me ... / images /.
Now I want to find
PIT: GT-N8xxx_note10.1.pit
PDA: CODE_N8000xxxxxx_....tar
PHONE: MODEM_N8000xxxxxx_....tar
CSC: CSC_Oxx_N8000xxxxxx_....tar
so I can flash through Odin a stock of rom, but I searched the internet and so I could not find any files. Can someone if you have to tell them no Pap somewhere and get them pulled or if there is another option to fix this .....
Greetings!
Thanks in advance for your help!
did u backup your efs before? if no, the easiest way to solve it is send the device to Samsung sc.
No, not backup. If anyone can upload the four files.
mukito said:
No, not backup. If anyone can upload the four files.
Click to expand...
Click to collapse
Firmware from sammobile.com .
PIT is dangerous wrong PIT = dead phone .
Title says EFS and CSC problems ????
jje
JJEgan said:
Firmware from sammobile.com .
PIT is dangerous wrong PIT = dead phone .
Title says EFS and CSC problems ????
jje
Click to expand...
Click to collapse
Well I think so because what is seen in the photos is that there is no CSC file. However, to install in Odin requires 4 second file, and until then I can only try to fix EFS ... or wrong ...
I can not get no rom to go, all charged to the logo of Samsung and there. So look for PIT and other files.
ODIN just requires the 1 file to flash - PDA. This is the rom, .tar file you wish to flash... You don't require a pit file however, I might as well hand a child the key to the gun cabinet, go here - http://forum.xda-developers.com/showthread.php?t=2268735 to find a pit file.
Again, you put pit file in pit file part and the rom .tar file into pda to flash.... CSC and Modem are included...
This still may not fix your tablet as it looks for the previous information first...
Hi hope you guys can help me. I recently bought an unlock s7 but it has the three network start up screen and three bloatware on it. I downloaded the latest BTU firmware from sammobile and tried to flash it using odin hoping that this would give me a fresh unbranded firmware. When i try to flash the files (AP,BL,CSC and CP) it stops at "NAND Write start' in the dialogue box and "set partition' at the top box. What am i doing wrong? What have i to do to install the unbranded BTU firmware? Thanks in advance
Have you solved this issue ?
I have the same problem now, trying to flash an official stock rom on my S7 and it also gets stuck at "Nand write start".
Try to flash official firmeware without hidden.img inside.
That solved the issue on galaxy s6 series.
Correct me if i'm wrong.
juli.freaky said:
Try to flash official firmeware without hidden.img inside.
That solved the issue on galaxy s6 series.
Correct me if i'm wrong.
Click to expand...
Click to collapse
Thanks @juli.freaky, I will give that a try as well.
I also got another possible solution to try to flash the PIT file first.
I will try both solutions
Hope this will help.
You loose all your data if you flash a firmeware with the pit if i'm right but i'm not sure. If you flash the stpck rom without hidden.img you won't loose your data.
That's the situation on the galaxy s6 but i'm not sure how it proceed with the galaxy s7
Best regards
juli.freaky said:
Hope this will help.
You loose all your data if you flash a firmeware with the pit if i'm right but i'm not sure. If you flash the stpck rom without hidden.img you won't loose your data.
That's the situation on the galaxy s6 but i'm not sure how it proceed with the galaxy s7
Best regards
Click to expand...
Click to collapse
Thanks for the heads up, but I don't mind losing my data as I will create Titanium backups first before I flash
I will try it later this week, as I need to have a full functioning phone right now.
But I will surely post my findings here, so others can find the solution in the future.
speedme said:
Thanks for the heads up, but I don't mind losing my data as I will create Titanium backups first before I flash
I will try it later this week, as I need to have a full functioning phone right now.
But I will surely post my findings here, so others can find the solution in the future.
Click to expand...
Click to collapse
Before you flash the BTU firmware have a look at this thread relating to the Identify Unsaved Numbers option here as your not in the UK, you may need to modify the others.xml as mentioned in the last post otherwise the option will be grayed out.
With your phone connected to you PC in developer options turn off USB Debugging then turn it on again and see if the message pops up on your phone to Authorize your PC it can reset the authorization which will allow Odin to work properly, use Odin 3.10.7.
Check in developer options that OEM Unlock is turned on then when you boot into download mode make sure FRP is Off.
was having same issue, came here for the answer, tried some of the mentioned things that didn't work but when downloaded the latest odin and flashed with it, it was worked like a charm.
also the post above mine is very helpful. so do read it.
S6 FIDO G920W8 stuck on NAND WRTE
I am looking for immediate assistance on NAND write stuck. Please reccomend me right verision of boot loop and modem. I am going crazy when my phone does not register sim card, no imei and does not work with Z3X Box.
Thanks
1. get the odin 3,11 not the one from samsung site
2. try a diferent CSC, that helped me today
juli.freaky said:
Try to flash official firmeware without hidden.img inside.
That solved the issue on galaxy s6 series.
Correct me if i'm wrong.
Click to expand...
Click to collapse
I have the same problem.
How can I do this?
We just picked up a pristine unlocked S6 for my wife as a replacement for her beat up old Iphone. The device ran perfectly once it was charged up. I set up WiFi and downloaded a few apps from the Play Store and all seemed perfect. The big UPGRADE message came up, telling me it was due for what I assume was the newly released Android 7 upgrade, and I stupidly said yes. Something must have gone wrong, as the download and install took way less time than I would have thought correct. The phone now bootloops continuously, about every 30 seconds, making it impossible to reach whatever ROM may still be there. I am able to reach Recovery, and Download mode no problem. Numerous wipes and factory resets have done nothing. I downloaded a Lollipop 5.0.2 ZIP, specific to Bell, the MD5 checked out OK. Sammy USB drivers are good. I can connect with Odin but the upload fails right away at sboot.bin.
Am I causing myself problems by trying to flash a stock Bell ROM on an unlocked phone? The ROMS are hard to find and most are stored in pay for use sites that literally take 12 hours to download if the user doesn't set up an account. Any suggestions as to how I can get this back running again, or is it bricked? I've spent about 8 hours on Google and trying everything I could find, and nothing I've come across has worked.
Alternatively, I'm fine with rooting and flashing a custom ROM (I've been doing them for years), though the boss would prefer to stay stock. Trouble is, without access to an existing stable ROM on the phone, I can't see how I can root in the first place. Are some ROMS flashable without rooting, and if so, what are some good ones? Would I simply load them into Odin and flash to the phone?
Thanks in advance.
jp071848 said:
We just picked up a pristine unlocked S6 for my wife as a replacement for her beat up old Iphone. The device ran perfectly once it was charged up. I set up WiFi and downloaded a few apps from the Play Store and all seemed perfect. The big UPGRADE message came up, telling me it was due for what I assume was the newly released Android 7 upgrade, and I stupidly said yes. Something must have gone wrong, as the download and install took way less time than I would have thought correct. The phone now bootloops continuously, about every 30 seconds, making it impossible to reach whatever ROM may still be there. I am able to reach Recovery, and Download mode no problem. Numerous wipes and factory resets have done nothing. I downloaded a Lollipop 5.0.2 ZIP, specific to Bell, the MD5 checked out OK. Sammy USB drivers are good. I can connect with Odin but the upload fails right away at sboot.bin.
Am I causing myself problems by trying to flash a stock Bell ROM on an unlocked phone? The ROMS are hard to find and most are stored in pay for use sites that literally take 12 hours to download if the user doesn't set up an account. Any suggestions as to how I can get this back running again, or is it bricked? I've spent about 8 hours on Google and trying everything I could find, and nothing I've come across has worked.
Alternatively, I'm fine with rooting and flashing a custom ROM (I've been doing them for years), though the boss would prefer to stay stock. Trouble is, without access to an existing stable ROM on the phone, I can't see how I can root in the first place. Are some ROMS flashable without rooting, and if so, what are some good ones? Would I simply load them into Odin and flash to the phone?
Thanks in advance.
Click to expand...
Click to collapse
Just use Samsung smartswitch software to restore firmware.
Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?
forumber2 said:
Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?
Click to expand...
Click to collapse
He tried to downgrade from marshmallow to lollipop that's why it failed.
sofir786 said:
He tried to downgrade from marshmallow to lollipop that's why it failed.
Click to expand...
Click to collapse
I know that, I want be sure that he/she didn't do anything (like wiping /data) expect trying to downgrade. I'll write my procedure according that for get the device back up and running without any data loss.
And he/she shouldn't use Smart Switch to restore the firmware in first place, it will cause data loss.
forumber2 said:
I know that, I want be sure that he/she didn't do anything (like wiping /data) expect trying to downgrade. I'll write my procedure according that for get the device back up and running without any data loss.
And he/she shouldn't use Smart Switch to restore the firmware in first place, it will cause data loss.
Click to expand...
Click to collapse
Ahh right okay, so using smart switch wipes internal storage? Anyhoo I won't ask too much now don't wanna hijack the post, do your thing
sofir786 said:
Ahh right okay, so using smart switch wipes internal storage? Anyhoo I won't ask too much now don't wanna hijack the post, do your thing
Click to expand...
Click to collapse
Thanks for the quick responses everyone. Apologies, it was very late when I made the OP, and I forgot to mention that I had tried both Kies AND Smartswitch. When I connected the phone while it was bootlooping, and for the brief period while whatever ROM was showing before the reboot, Smartswitch connected with it, but immediately fired back that "USB file transfer is not allowed...". There does seem to be some, or all, of a ROM there, but it is still in the setup stage, which is expected after a full factory reset. I don't have time to go in and enable USB Transfer as it reboots well before I can get into Settings. When I connect while it was in Download mode, SS seems to hang on "Connecting to your device" then fails.
"Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?"
SM-G920W8 yes. After the Odin problems, per my original post, I also tried, based on suggestions all over the interweb, a wipe, as well as resorting to a factory reset, through the stock recovery. Nothing worked, the bootloop continues, and the factory reset causes the system to go into setup mode. In the 30 seconds between reboots, I don't have time to get into the ROM to make changes like enabling USB transfer/debugging before it reboots again.
"He tried to downgrade from marshmallow to lollipop that's why it failed"
I assumed, when I first clicked the button and caused the problem, that I was UPGRADING from whatever ROM was properly installed, to Android 7.0/Nougat. This failed and induced the bootloop. I then thought I would try and install Lollipop through Odin, which brings up the sboot.bin fail. From your comment, should I try to find a Nougat 7.0 ROM and do the UPGRADE manually via Odin? Is that more likely to work than a downgrade.
Regarding the comments about data loss, I am not concerned about that, the phone was new and did not contain any data worth saving, it hadn't been set up yet. In any case, I tried a few factory resets, so any data would have been wiped during that action as well.
I'm getting nervous, I seemed to have really borked up this phone, I sure hope you experts can bail me out. ;o(
Thanks again for the help...
jp071848 said:
Thanks for the quick responses everyone. Apologies, it was very late when I made the OP, and I forgot to mention that I had tried both Kies AND Smartswitch. When I connected the phone while it was bootlooping, and for the brief period while whatever ROM was showing before the reboot, Smartswitch connected with it, but immediately fired back that "USB file transfer is not allowed...". There does seem to be some, or all, of a ROM there, but it is still in the setup stage, which is expected after a full factory reset. I don't have time to go in and enable USB Transfer as it reboots well before I can get into Settings. When I connect while it was in Download mode, SS seems to hang on "Connecting to your device" then fails.
"Your device's model is SM-G920W8, right?
And the only thing you did is flash an firmware via Odin and stuck on sboot.bin?"
SM-G920W8 yes. After the Odin problems, per my original post, I also tried, based on suggestions all over the interweb, a wipe, as well as resorting to a factory reset, through the stock recovery. Nothing worked, the bootloop continues, and the factory reset causes the system to go into setup mode. In the 30 seconds between reboots, I don't have time to get into the ROM to make changes like enabling USB transfer/debugging before it reboots again.
"He tried to downgrade from marshmallow to lollipop that's why it failed"
I assumed, when I first clicked the button and caused the problem, that I was UPGRADING from whatever ROM was properly installed, to Android 7.0/Nougat. This failed and induced the bootloop. I then thought I would try and install Lollipop through Odin, which brings up the sboot.bin fail. From your comment, should I try to find a Nougat 7.0 ROM and do the UPGRADE manually via Odin? Is that more likely to work than a downgrade.
Regarding the comments about data loss, I am not concerned about that, the phone was new and did not contain any data worth saving, it hadn't been set up yet. In any case, I tried a few factory resets, so any data would have been wiped during that action as well.
I'm getting nervous, I seemed to have really borked up this phone, I sure hope you experts can bail me out. ;o(
Thanks again for the help...
Click to expand...
Click to collapse
I think Upgrading to nougat via Odin would be best bet @forumber2 has a good set of steps which are easy to follow .
sofir786 said:
I think Upgrading to nougat via Odin would be best bet @forumber2 has a good set of steps which are easy to follow .
Click to expand...
Click to collapse
I did a search under that name, and came across a reference to a great app called SamFirm (not sure if that's what you meant by a good set of steps ;o). I ran SamFirm using SM-G920W8, and tried both Regions BMC (Bell) and XAC (Canada). Downloaded and unzipped, the XAC file name was SM-G920W8_1_20170428185952_f736z32l4i_fac.zip.enc4, and entered the AP, BL, CP and CSC links in Odin. Failed both times with the same Odin message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
On the phone, on the Downloading screen, the error was "SECURE CHECK FAIL : (PIT)"
Googling these messages, the general consensus seems to be that these errors indicate an attempt to flash an incorrect ROM, but I'm running out of options for finding a "correct" one.
Thanks again...
jp071848 said:
I did a search under that name, and came across a reference to a great app called SamFirm (not sure if that's what you meant by a good set of steps ;o). I ran SamFirm using SM-G920W8, and tried both Regions BMC (Bell) and XAC (Canada). Downloaded and unzipped, the XAC file name was SM-G920W8_1_20170428185952_f736z32l4i_fac.zip.enc4, and entered the AP, BL, CP and CSC links in Odin. Failed both times with the same Odin message:
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
On the phone, on the Downloading screen, the error was "SECURE CHECK FAIL : (PIT)"
Googling these messages, the general consensus seems to be that these errors indicate an attempt to flash an incorrect ROM, but I'm running out of options for finding a "correct" one.
Thanks again...
Click to expand...
Click to collapse
Samfirm is a great tool to download firmwares. The pit file sets your partition sizes, you need to flash the correct pit file for that firmware otherwise the firmware will fail to flash.
sofir786 said:
Samfirm is a great tool to download firmwares. The pit file sets your partition sizes, you need to flash the correct pit file for that firmware otherwise the firmware will fail to flash.
Click to expand...
Click to collapse
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
jp071848 said:
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
Click to expand...
Click to collapse
I think there is a Thread in the general section which has the collection of pit files, you need to make sure the pit file is bmc.
jp071848 said:
Now we're getting somewhere ;o) I stayed away from PIT files as they seem to be controversial/risky, but the error message I'm seeing would seem to confirm what you're saying. Question is, how do I locate the correct PIT file AND GET IT RIGHT THE FIRST TIME, as I understand that making a mistake with the PIT file can be disastrous.
Thanks so much...
Click to expand...
Click to collapse
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
jp071848 said:
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
Click to expand...
Click to collapse
I don't think it could go any worse tbh, try it without the pit file and repartition, you can then try the pit file method if it doesn't work
jp071848 said:
UPDATE: I found what I assume is the correct PIT file for the G920W8. Also, on another forum, I found the question:
"Okay, according to that guide Odin is smart enough to know the Pit file is in the CSC file, when the re-partition box is checked? ",
so I may not need the PIT file after all? I had always read that when using Odin, Re-partition was always to be left UNCHECKED, but this says otherwise. What further damage could I possibly do if I re-run Odin with the same AP, BL, CP and CSC files as before, but CHECK re-partition. I guess I can't brick it worse than it already is? Or can I?
Click to expand...
Click to collapse
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
jp071848 said:
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
Click to expand...
Click to collapse
That's just a warning more than anything else
jp071848 said:
Moving right along.... I decided to live dangerously by flashing the BMC ROM, obtained through SamFirm, with Odin, with Re-partition checked. In theory, this would have let Odin know that the contents of the PIT file are already inside the CSC file. Sadly, same result "Re-partition Operation Failed". Interestingly, when I click the PIT tab in Odin the popup says "Do not use this tab... Your device will be changed with the PIT in the CSC file", which doesn't appear to be the case.
Click to expand...
Click to collapse
Tried ODIN and included the PIT file I downloaded. Tried with "Re-Partition" on and off, both times failed exactly the same way "Re-partition" Operation Failed"
jp071848 said:
Tried ODIN and included the PIT file I downloaded. Tried with "Re-Partition" on and off, both times failed exactly the same way "Re-partition" Operation Failed"
Click to expand...
Click to collapse
where did you get the pit file from?
look in settings>security>reactivation lock
if its checked/enabled then uncheck it/disable it
fyi, stay away from repartition pit in odin, only for experienced users w/correct files if any
sofir786 said:
where did you get the pit file from?
Click to expand...
Click to collapse
From this 22 page thread here on XDA
https://forum.xda-developers.com/galaxy-s6/general/g920f-pit-file-banded-firmwares-t3118459
There is a specific reference to a Canadian W8 PIT file
SM-G920W8 OYA multi CSC ( BMC BWA ESK FMC GLW KDO MTA RWC TLS VMC VTR )
ZEROFLTE_CAN_BMC.pit
That's the one I unzipped and loaded into Odin.