Related
For instance I'm trying to flash stock from sammobile
G920FXXU1AOE3_G920FXEU1AODQ_XEU.tar
which contains
boot.img
cache.img
cm.bin
hidden.img
modem.bin
recovery.img
sboot.bin
system.img
odin fails as soon as it gets to a bin file
That's ok I can just remove the bin files and it installs fine.
my understanding is that it's failing because the partitions are not all the same size. So what? If the pit was there it wouldn't matter, it could repartition and everything would be hunky dory?
Why is the pit not there, and where do I get the correct one? 32Gb
ZEROFLTE_EUR_OPEN-sb256-128.zip
ZEROFLTE_EUR_OPEN-sb200.zip
ZEROFLTE_EUR_OPEN-sb.zip
ZEROFLTE_EUR_OPEN-HIDDEN100M.pit
also I can't grab/backup my current pit with
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
because there is no mmcblk0
The TAR file is basically an archive. Just open it with WinRAR and delete cache.img and hidden.img from the archive.
You will be able to flash any firmware without the PIT file.
neflictus said:
The TAR file is basically an archive. Just open it with WinRAR and delete cache.img and hidden.img from the archive.
You will be able to flash any firmware without the PIT file.
Click to expand...
Click to collapse
'
How do remove these files? This doesn't seem possible? Regards
Hello guys! Today I bring the extracted PIT for Galaxy Ace 3 GT-S7275R, but it should work on S7275B and S7275T due to they have same mounts points.
If you want to recover your phone from bootloop, soft brick, unroot or remove custom recovery, you should flash Stock ROM via Odin. If everything goes correctly, Odin flashing process should finish without any problem. However, in some cases the process finish before flashing and an error message appears at Odin. Some of those errors are "Invalid Ext4 Image" and "Get PIT for mapping".
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
Android uses the EXT4 storage structure, which defines the free available storage location for system partitions. PIT file (Partition Information Table) is a Samsung internal element that contains the location of different system partitions, I mean, it allocates phone partitions.
When you're installing a firmware, Odin starts to review partitions information. If it detect PIT file, everything will finish correctly, but if PIT file is not detected or is damaged, you'll get "Get PIT for mapping" issue.
To fix this problem, you must provide PIT file for Odin to flash firmware without problem.
Besides, this file is useful if your partitions are damaged or you want to restore their values due to some partition you've made or whatever.
You must put in "PIT" section of Odin, and be sure that "Auto-reboot", "Re-partition" and "F. Reset Time" boxes are ticked.
Download: CLICK HERE
That's all! Sorry for my bad english :silly:
dude my galaxy gt-7275R device is hard bricked! i must get the data back from internal storage,is there anyway to do that? or can u give me the debrick.img file for this device.. help me it's my favorite phone
It stays on the booting screen flashing. "Samsung galaxy s6 live demo unit". I can't get it to boot hence can't set the usb debugging on to flash another firmware. What is there to do ?
EDIT: Managed to enter recovery mode and clear cache + do a factory reset. That not only did not solve anything but now i can't get into recovery or download mode at all. That "Samsung galaxy s6" thing flashes only when the phone is charging !
Alright, it has to be charging in order to get into recovery/download mode. Now, what shall i do ? What ROM should i flash since this is a SM-G920X ? Please help me, i couldn't find any useful information on google. Even if there was a suitable firmware to flash, the device is not recognized in odin. What shall i do ?
I had some problems with my account and i had to post from that other one. I downloaded samsung drivers and the phone is now recognized in odin but i cant flash the sm-g920 firmware, it fails just on start. Please help me out of this.
EDIT : FOUND THIS http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738 . I think it will be a great help.
Alright, i tried flashing that verified ready-to-flash ROM that was provided there and it failed at around 40%. Now i cant flash it again, it stay locked at
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
I dont know what to do next.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Second time it fails.. I dont know why.
---------- Post added at 09:05 PM ---------- Previous post was at 08:42 PM ----------
I flashed that ready-to-go ROM successfully and now it boots further to that "welcome" screen but i encounter a big yellow triangle with an black exclamation mark in middle and a 'dead' android bot behind it. What should i do next ?
IMPORTANT NOTE : The phone won't show any kind of life unless it's CHARGING.
Can anyone really help me a little, what's up with this device ? Should i hope or try any further cause i really dont know what to do
Everything you guys need to know to get off the mess you created is here in this thread.
http://forum.xda-developers.com/galaxy-s6/general/g920x-master-thread-guides-firmwares-t3267738
Read and make sure you know what you're dealing with first, then start flashing ROMs!
I noticed the link was already found and posted by the OP in a later edit. Thanks.
One more thing i wanted to add is you can only flash a ROM that matches with your bootloaders. Since the LDU bootloader is Android 5.1.1 at the latest, you cannot flash Android 6. I suggest, if you manage to update bootloaders from 5.0.1 to 5.1.1, getting the latest 5.1.1 from sammobile, removing the *.bin files, and flash in ODIN.
Sent from my SM-G920F using XDA-Developers mobile app
Thanks god someone is willing to help me out of this ! I read the entire thread multiple times and i really really want to get out of this mess.
I took that ready-to-go ROM he provided there cause of the fact alone i have no clue what a unix machine is hence i can't remove these .bin files listed there. Also, i have no clue what bootloader this phone has or what that means in the first place, but i flashed a 5.1.1 one ( I guess) that i found on that thread successfully.
I would be extremely grateful if you could help me remove these files on my own or provided a 5.1.1 rom with these files removed.
Pure curiosity. Why does the phone 'play' dead when i'm trying to power it while not being charged ?
---------- Post added at 11:18 PM ---------- Previous post was at 10:20 PM ----------
Meh.. i seem to cant flash any ROM anymore. It would just fail mid-process saying "Removed".
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Im extremely grateful for your help, i will try to flash this one and if it won't work i'll check nand erase. I guess i can't screw it more than it already is.
EDIT : No success flashing either way.
---------- Post added at 06:05 AM ---------- Previous post was at 05:50 AM ----------
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Erase...
<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> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<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> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
That's a log, 3 flash attempts in a row, different messages though.
In that g920x master thread it is said so " The only preparation required is the removal of the modem, bootloader, PIT, and related partitions.". I couldn't help but realize that while the flash was going on it still went through modem.bin, is that alright ? I have no idea myself, just trying to figure out why i can't this damned thing to work.
Ah I see the modem file in there. Sorry about that, although it seems that it flashed just fine. I would think the modem file will be there but not get used. But at any rate, I've redone the whole process from the original factory file, and i'm uploading now, no bin files this time! ETA 35 minutes ...
https://drive.google.com/open?id=0B31Omryqpl4nd2NLTG5nY3JxUk0
It still won't flash. I don't know what to do next.
Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Help me figure out the exact commands i have to type in cygwin for a filename. What do i have to do to let that terminal know where my file is located, cause i guess you have to mention the location.
Just write the exact command i have to write with the "Filename.tar" in cygwin while filename is located on desktop.
By the way, im requesting them cause i tried the commands you provided and i can't figure out how to use them.
"[email protected] ~
$ tar --delete --file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
[email protected] ~
$ tar --delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship] hidden.img
tar: unrecognized option '--delete--file[AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship]'
Try 'tar --help' or 'tar --usage' for more information.
"
I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app
Commodore 64 said:
I typed the exact commands for you already. I put each command under the line that starts with a dash - which tells you what that following command is doing.
Did the file flash and go through on Odin? You probably know you need to reboot the phone freshly back to download mode every time it is connected to Odin or else you'll get a flash error. So open Odin put phone in DL mode and connect USB. If you disconnect USB, you shouldn't just plug it back in, you'll need to reboot the phone into DL mode again!
I think what it is about Cygwin that you're struggling with is that, cygwin isn't given permission to go out of its own folder environment and edit files in other places, such as your desktop. That is a good thing and we wanna keep it that way for security reasons so you don't accidentally damage the OS or delete other files/folders.
So what you'll do is copy the file you want to manipulate by cygwin to home directory of cygwin, and then it will see it and be able to edit it. Something like c:\cygwin\home\[Windows Username] depending on where you installed Cygwin. And yes you can change its home directory to somewhere else on your PC, but that is really not with in the scope of this thread.
Sent from my SM-G920F using XDA-Developers mobile app
Click to expand...
Click to collapse
I am a total noob. I cant figure it out really, it may be your way of explaining too but i cant. Just do that, write the exact command you write to remove hidden.bin from the "Filename.tar" which is located in cygwin local director.
---------- Post added at 06:05 PM ---------- Previous post was at 05:54 PM ----------
Commodore 64 said:
Well if you're a windows user you can install Cygwin and use the commands, if you're a MAC user just open up terminal and use:
- to rename the md5 file to tar for unpacking:
mv filename.tar.md5 filename.tar
- to untar (extract) the tar file:
tar -xf filename.tar
- delete the .bin files:
rm *.bin
- repack the .img files into a tar:
tar -cf newfilename.tar *.img
- create md5:
md5sum -t newfilename.tar >> newfilename.tar
- add the md5 file extension so ODIN will recognize it:
mv newfilename. tar newfilename.tar.md5
now you have your "newfilename.tar.md5" to load into the "AP" of your ODIN and flash it.
I've zipped the one I just made while I typed up the commands in cygwin for you to make sure they worked. Uploading, but it's going to take a while. I will check back in ~hour to see if it timed out or not.
Ok download it, unzip it, and load the "G920FXXU3COI9_G920FXEU3COJ2_G920FXXU3COI9.tar.md5" in the AP segment of Odin. Try it first and if it didn't work again, since you've done multiple flashes, it won't be a bad idea to check "nand erase all" one time in ODIN options.
Link removed. Please use link in my next post.
Click to expand...
Click to collapse
Wow, im unbelievably dumb. I just figured out ! You wrote the commands i have to use, one by one. Im so ashamed of myself now. I thought there are some commands i could use not at all they are meant to be used in that order, im so sorry for wasting your time.
I'm afraid i'll still have to bother you one more time
$ tar -xf AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar
tar: AP_G920XZCU1BOI2_LLK_CL5369277_QB6240453_REV02_user_low_ship.tar: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Steps i went through : 1. moved the ROM to C:\cygwin64\filename.tar (renamed it manually, not via command)
2. Wrote tar -xf filename.tar and i got that error you can see there.
---------- Post added at 06:10 PM ---------- Previous post was at 06:05 PM ----------
I GOT IT RIGHT, GOD. I am really sorry to waste your time. Finally, i understood, i read it all once again and i understood. I had to copy the tar file to cygwin64/home/User/. I am extremely grateful and i hope i will get my device to work.
I'm really sorry you had to dealt with such a noob though. I thank you again for your help.
Hello XDA
model-G920I rom-NEMESIS NOUGAT STABLE S7E PORT V3.1
I flashed bootsplash custom image MOD zip file which i think was corrupted it flashed correctly on twrp 3.0.2.0 without any error but after reboot phone is not booting.no charging(though i think its charging somehow) animation LED is not working while plugged in to charging nor i am able to go to system,recovery The only thing thats working is DOWNLOAD MODE obviously no bootsplash either
Therefore i flashed stock 6.0 MM firmware by ODIN(tried multiple times) but still having same issue please tell me how to fix this ??
ODIN MODE
PRODUCT NAME: SM-G920I
CURRENT BINARY: Custom
SYSTEM STATUS: cUSTOM
REACTIVATION LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x030c)
ODIN V3.10 LOG:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU3EPC7_G920IODD3EPC1_G920IDVU3EPC3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
please help me !! :/
can you post log of odin?
shiko2007 said:
can you post log of odin?
Click to expand...
Click to collapse
thanks for replying,
i have updated the thread with odin logs plz refer it thanks :good:
when turn on device? is it stuck on samsung boot image powered by android or only black screen, you can try bro to flashed latest bootloader of your device instead of "3ep7“
shiko2007 said:
when turn on device? is it stuck on samsung boot image powered by android or only black screen, you can try bro to flashed latest bootloader of your device instead of "3ep7“
Click to expand...
Click to collapse
only black screen
n i flashed firmware but didnt work where is the splash screen files stored in the bootloader?? and will any version of bootloader work??
i am not able to find latest bootloaer of G920I
try find your firmware in sammobile or use samfirm to find your firmware, you can download by samfirm the 4 files firmware and after that flash 4 files (search the way in Google) in odin and the device will should work after flashing 4 file, notice it will wipe everything on your device and return your device like out of bax state
---------- Post added at 12:04 PM ---------- Previous post was at 11:51 AM ----------
black screen bro without Samsung boot image mean there is damage happen in the boot file
shiko2007 said:
try find your firmware in sammobile or use samfirm to find your firmware, you can download by samfirm the 4 files firmware and after that flash 4 files (search the way in Google) in odin and the device will should work after flashing 4 file, notice it will wipe everything on your device and return your device like out of bax state
---------- Post added at 12:04 PM ---------- Previous post was at 11:51 AM ----------
black screen bro without Samsung boot image mean there is damage happen in the boot file
Click to expand...
Click to collapse
and how am i supposed to fix that ???
[email protected] said:
and how am i supposed to fix that ???
Click to expand...
Click to collapse
bro your do that by try flash full stock firmware of your device , if you have same situation after flash try to flash by another version of odin , i recommend you version Odin3-v3.11.1 that run perfect with me but if it didn't work also so you have two way :
first- flash 4 file firmware of your device and you can get this type of firmware by using samfirm pregame that will search your latest firmware of your device
second- extract boot.img from 1 file firmware of your device and convert to boot.tar to do that make this step :
a - Download and install 7-zip
b - Extract boot.img from your firmware by open firmware by 7-zip and you will notice there are file boot.img choose it and click on extract you will now have boot.img
c- Right click on the file > 7-zip > Add to archive...
d - In this screen you can ((( most important))) in "Archive format" choose "tar" now you should have boot.tar
e - Open ODIN and flash the new file as always by choose "AP"
shiko2007 said:
bro your do that by try flash full stock firmware of your device , if you have same situation after flash try to flash by another version of odin , i recommend you version Odin3-v3.11.1 that run perfect with me but if it didn't work also so you have two way :
first- flash 4 file firmware of your device and you can get this type of firmware by using samfirm pregame that will search your latest firmware of your device
second- extract boot.img from 1 file firmware of your device and convert to boot.tar to do that make this step :
a - Download and install 7-zip
b - Extract boot.img from your firmware by open firmware by 7-zip and you will notice there are file boot.img choose it and click on extract you will now have boot.img
c- Right click on the file > 7-zip > Add to archive...
d - In this screen you can ((( most important))) in "Archive format" choose "tar" now you should have boot.tar
e - Open ODIN and flash the new file as always by choose "AP"
Click to expand...
Click to collapse
i tried latest firm. on various odin versions but didnt work now i will try with 4 diff. files
btw i think that boot files are damaged so do u think nand erase all then flashing the one file firm work??
DO NOT USE THAT TICK BOX. you will have a very pretty paperweight . bro just flash 4 file firmware and everything will be great ,it should fix your boot file and every thing else.
NAND Erase mean dude , IT WILL ""ERASE ALL""" of the “Storage (eMMC) unit inside the Device.
---------- Post added at 06:00 AM ---------- Previous post was at 05:31 AM ----------
bro ,if every thing failed with you , the last thing you can do it using ((nand erase all )with proper pit file for your device with tick repartion on odin+with proper flash 4 files ) . but this the last thing you should do bro , i didn't like using "nand erase all " because that function can be quite unpredictable .
So,Finally I Recovered My Phone So,Lemme Tell How
Flashing Firmware Using ODIN Was Useless For me As It Didn't Wipe Internal Storage Therefore the issue persisted even after flashing numerous firmwares
so,i tried updating SAMSUNG SMART SWITCH And It Worked Like Charm
Click to expand...
Click to collapse
& the problem was that i flashed the bootsplash image with higher resolution that bugged up my boot
Thanks anyway guys
Hello! Yesterday I went to install TWRP on my Galaxy S8 to install a custom rom. In the tutorial, he said he should do Wipe on some things. I have and since then my phone is dead! I tried installing three different roms and none works.
When I flash the rom I have the following message:
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> modem_debug.bin
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 4042 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm using Odin v3.13. The most recent I found.
I've already looked all over the internet and saw a video where you should click Start on the odin and then click on the three buttons to restart the device etc. That did not solve!
Please, can anyone help me? I am getting crazy!
Solution
1-. First at all run ODIN as an administrator.
2-.Boot on download mode.
3-.Dont flash (BL) for the moment select only AP and HOME_CSC to make a fast flash.
4-.When you boot successfully on your system go to developer options and then select "Oem Unlock".
5-. Download a zip called (no-verity-opt-encrypt.zip) for the S950F . Move the zip to your phone you will need that later to make work the TWRP.
6-.Boot on download mode again.
7-.Flash the Custom recovery.
8-.Boot on Custom recovery wipe all data.
9-.Reboot on recovery again
10-.Now flash no-verity-opt-encrypt.zip and restart normally
11-.Done!
MrMeeeMdick said:
1-. First at all run ODIN as an administrator.
2-.Boot on download mode.
3-.Dont flash (BL) for the moment select only AP and HOME_CSC to make a fast flash.
4-.When you boot successfully on your system go to developer options and then select "Oem Unlock".
5-. Download a zip called (no-verity-opt-encrypt.zip) for the S950F . Move the zip to your phone you will need that later to make work the TWRP.
6-.Boot on download mode again.
7-.Flash the Custom recovery.
8-.Boot on Custom recovery wipe all data.
9-.Reboot on recovery again
10-.Now flash no-verity-opt-encrypt.zip and restart normally
11-.Done!
Click to expand...
Click to collapse
Thanks for the answer! I selected the AP and the SCS, but when I click to start the same thing happens!
Check the print
prntscr.com/kd0c3j
I got to TWRP. Is there anything I can do?:crying:
Rubson Goldner said:
Thanks for the answer! I selected the AP and the SCS, but when I click to start the same thing happens!
Check the print
prntscr.com/kd0c3j
I got to TWRP. Is there anything I can do?:crying:
Click to expand...
Click to collapse
...
Rubson Goldner said:
...
Click to expand...
Click to collapse
1.-Boot on TWRP If you can. Select the option (Advanced Wipe Cache and Data)
2.-Select only (AP) MAKE SURE IS CORRECT FIRMWARE, you have the correct samsung drivers and you are running odin as an ADMINISTRATOR
3.-If that doest work flash only the bootloader (BL). if you successfully flash the (BL), then flash (AP).
MrMeeeMdick said:
1.-Boot on TWRP If you can. Select the option (Advanced Wipe Cache and Data)
2.-Select only (AP) MAKE SURE IS CORRECT FIRMWARE, you have the correct samsung drivers and you are running odin as an ADMINISTRATOR
3.-If that doest work flash only the bootloader (BL). if you successfully flash the (BL), then flash (AP).
Click to expand...
Click to collapse
Hi!. I was able to install an alternative ROM, not original by TWRP, but I happen to be without a signal, then I would go back to the original rom, but I get the same error every time!
Rubson Goldner said:
Hi!. I was able to install an alternative ROM, not original by TWRP, but I happen to be without a signal, then I would go back to the original rom, but I get the same error every time!
Click to expand...
Click to collapse
Downgrade the Bootloader (BL). But you can install Z3 and repair the signal
***You can also flash the original modem.bin and you are go to go with the signal***