This post was a question, but now I've edited it to help some users. Marshmallow ota was released in India, but if you want to flash it manually you can. Using this amazing tool: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
You can download the stock MM firmware for the a8. Just set the region code to INS and put your model number. Make sure 'decrypt' box is checked. After downloading the firmware, you will see the file extension is '.zip.enc4'. Remove the .enc4 extension and unzip it. There you will find the .tar.md5 file which you can flash with Odin, just put it in the Ap/pda section.
Hope this helped you guys
Arathergreendroid said:
This post was a question, but now I've edited it to help some users. Marshmallow ota was released in India, but if you want to flash it manually you can. Using this amazing tool: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
You can download the stock MM firmware for the a8. Just set the region code to INS and put your model number. Make sure 'decrypt' box is checked. After downloading the firmware, you will see the file extension is '.zip.enc4'. Remove the .enc4 extension and unzip it. There you will find the .tar.md5 file which you can flash with Odin, just put it in the Ap/pda section.
Hope this helped you guys
Click to expand...
Click to collapse
XDA Assist is not the place for this.
Thread closed.
Related
I have a Samsung Galaxy Tab Plus Wi-Fi only GT-P6210 that I want to flash back to stock ROM using ODIN. I have found two packages at this thread. (I can't post to the following thread because I'm a noob)
http://forum.xda-developers.com/showthread.php?t=1367478
One package has only one file that I know is the PDA file. The other package has 3 files:
GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5
P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5
P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5
The CODE file is the PDA file, correct?
The CSC file is the CSC file, duh.
What is the APBOOT file?
Can you also explain what the different files are? What is a CSC file? What is a PIT file? Why does the other package only contain the PDA file?
I've never ODIN'd before so I want to make sure I know what I'm doing and flash the correct package.
bdarc said:
I have a Samsung Galaxy Tab Plus Wi-Fi only GT-P6210 that I want to flash back to stock ROM using ODIN. I have found two packages at this thread. (I can't post to the following thread because I'm a noob)
http://forum.xda-developers.com/showthread.php?t=1367478
One package has only one file that I know is the PDA file. The other package has 3 files:
GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5
P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5
P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5
The CODE file is the PDA file, correct?
The CSC file is the CSC file, duh.
What is the APBOOT file?
Can you also explain what the different files are? What is a CSC file? What is a PIT file? Why does the other package only contain the PDA file?
I've never ODIN'd before so I want to make sure I know what I'm doing and flash the correct package.
Click to expand...
Click to collapse
I have the same question my self but didnt know where to look... Hopefully you get an answer soon cause id like to know to, my tab got screwed up and i dont know how to get the original firmware back and no clue how to properly flash the odin with out screwing it up more, so hopefully this works
Deleted
Can you tell me, what is the function of PIT file? sorry i'm noob
freshtanto said:
Can you tell me, what is the function of PIT file? sorry i'm noob
Click to expand...
Click to collapse
These 2 XDA threads offer information on PIT files:
http://forum.xda-developers.com/showthread.php?t=816449
http://forum.xda-developers.com/showthread.php?t=999097
Basically, I'd only ever use a PIT file if Odin threw up an error relating to it, 99% of the time these are not needed when using Odin unless you've screwed up your devices partitions.
It's handy to have this file saved as a backup though just in case that ever happened
okey i got it now, thanks it's really hepful :good::good::good:
invalid pit for t310
This file is also necessary to build packages for Heimdall. FYI
This file is also necessary to build packages for Heimdall. FYI
Your pit-file kill my tablet..............
MNKF said:
Your pit-file kill my tablet..............
Click to expand...
Click to collapse
How, a little more information would be nice?
What model did you use it on; T310, T311 or T315?
What options did you tick in ODIN?
I compared the same PIT file to one extracted with heimdall on my T310, all entries/contents were the same, it came from a T311 firmware package but T310 firmware packages also have the same file. T315 uses a different named PIT file hence why I was uncertain.
Just now I've even compared it to another PIT file off the SamMobile forums that a Moderator posted for the T310, everything is the same, ODIN will reject it if it isn't signed as well.
https://www.diffchecker.com/cta675hS
I didn't force you to use the file, nor was this a guide in anyway, your device must have been in a bad way for you to consider using it.
In any case I've now removed the file.
Hello all!
This is my first tutorial here, hope to be useful as it was for me. After several attempts and extense research mainly here in XDA I finally achieved to downgrade my SM-G920I from 7.0 to 6.0.1 even with secure boot enabled.
The basics: Using a chilean stock 6.0.1 ROM:
- I've extracted all files from the stock rom and repacked it as 4 files without sboot.bin Instructions here: forum DOT gsmhosting DOT com/vbb/f777/tutorial-create-samsung-4-file-multi-firmware-your-own-100-a-1860706/- I've used a PIT default file for my model and region from here: sammobile dot com/forum/threads/30173-galaxy-S6-G920-pit-files
The instructions are the usual, Using Odin 3.12, flash the files into their respective slots and select the PIT file into PIT tab also. In options disable auto reboot and check re partition.
Download link in progress, but you can DIY with the instructions before.
downgrade issue can you give me the PIT file for sm-g920f please
also i have issue to back to nougat an error occured hidden.img durinf flashing
Mehar Zain said:
also i have issue to back to nougat an error occured hidden.img durinf flashing
Click to expand...
Click to collapse
Have you downloaded a 6.0.1 stock rom for your model and then followed my instructions?
PD: The FRP for your device in on the second link mentioned before.
There is easier way ,after extracting delete all .bin (aboot cache hidden and something else cant remember)then repack using 7zip to the originat format u will notice that the new archive is bigger it's about 3.6 gb inside there is data,system and some other files flash the new archive with odin and thats all ,worked fine t mobile g920t downgrading from nougat to mm
amin44 said:
There is easier way ,after extracting delete all .bin (aboot cache hidden and something else cant remember)then repack using 7zip to the originat format u will notice that the new archive is bigger it's about 3.6 gb inside there is data,system and some other files flash the new archive with odin and thats all ,worked fine t mobile g920t downgrading from nougat to mm
Click to expand...
Click to collapse
Yes, you are right. Using 7zip is a lot easier.
Will work on Att version G920A with locked bootloader on 7.0? I've been researching 2 days to see about downgrading it 6.0.1 while taking least chances as possible. If answer is yes, when repackaging should I remove md5 extension on all 4 files?
Thanks
amin44 said:
There is easier way ,after extracting delete all .bin (aboot cache hidden and something else cant remember)then repack using 7zip to the originat format u will notice that the new archive is bigger it's about 3.6 gb inside there is data,system and some other files flash the new archive with odin and thats all ,worked fine t mobile g920t downgrading from nougat to mm
Click to expand...
Click to collapse
how you repack to original format with 7zip?
i always get error cheksum when put the file in odin
zhadow88 said:
how you repack to original format with 7zip?
i always get error cheksum when put the file in odin
Click to expand...
Click to collapse
Just select the file and compress them using normal compression in options ,maybe the problem is with your version of odin
https://forum.xda-developers.com/showpost.php?p=81418691&postcount=29
Hope this might help someone here.
I rooted my s8+ and basically got stuck with a soft-bricked phone, telling me I could only use official firmware etc etc. I was able to get the phone into download mode (eventually) but I wasn't able to flash anything including the stock Pie rom. I spent all night trying to find a solution to no avail and then found this, which I've edited a bit. And it worked. I've now got my s8+ back with Android 9 on it without any bloatware and it's actually better than ever. Thanks to Krolik301 for your help. I'm just hoping this may help someone.
1. Download the stock ROM and extract it.
2. Make a copy of the CSC file and rename one from the file type .md5 to .rar
3. Extract the PIT file from the CSC .rar file.
4. In Odin v3.13, make sure you add all four files from the extracted ROM (BL, AP, CP and CSC).
5. Click the PIT tab and add the PIT file that you just extracted from the CSC.rar file.
6. I the Options tab of Odin, make sure that Re-Partition, Auto Reboot and F.Reset Time are all ticked.
7. Click Start and hopefully you'll be back to your stock ROM
And please don't hold me responsible for any loss of data or a phone that still won't boot.
Hope this helps someone. Happy Easter
Muddyfunk said:
Hope this might help someone here.
I rooted my s8+ and basically got stuck with a soft-bricked phone, telling me I could only use official firmware etc etc. I was able to get the phone into download mode (eventually) but I wasn't able to flash anything including the stock Pie rom. I spent all night trying to find a solution to no avail and then found this, which I've edited a bit. And it worked. I've now got my s8+ back with Android 9 on it without any bloatware and it's actually better than ever. Thanks to Krolik301 for your help. I'm just hoping this may help someone.
1. Download the stock ROM and extract it.
2. Make a copy of the CSC file and rename one from the file type .md5 to .rar
3. Extract the PIT file from the CSC .rar file.
4. In Odin v3.13, make sure you add all four files from the extracted ROM (BL, AP, CP and CSC).
5. Click the PIT tab and add the PIT file that you just extracted from the CSC.rar file.
6. I the Options tab of Odin, make sure that Re-Partition, Auto Reboot and F.Reset Time are all ticked.
7. Click Start and hopefully you'll be back to your stock ROM
And please don't hold me responsible for any loss of data or a phone that still won't boot.
Hope this helps someone. Happy Easter
Click to expand...
Click to collapse
Hello. I'm helping someone on discord with this exact issue (the error code is "can't open the specified file (line 665)". I extracted the PIT file from CSC and placed it into the PIT file. I also put all of the firmware files in their proper place (except for HOME_CSC, as he wants to keep his files). Do I absolutely have to put the CSC file in place of the HOME_CSC file?
I live in pakistan, i need international Ftf file link. Please provide download link
please provide and also tell me what i need to select in flash tool during flash.
thanks
Still no reply..
S8232 or g8231???
Im confuse here... S8231 OR G8231? SOV35 AND G8231 its the same phone right?
xperifirm & effort
It's quite simple, you have to edit the firmware.xml file from the download folder in your flasher before packing the .ftf . I don't know what .ftf you need but if you have flashtool with xperifirm plugin you should be able to select your customization of the oem rom of your choice. Edit the file (firmware.xml) while you have xperifirm open in your rom downloads folder, change the tagged info where the model written is 8321 to SOV35. Then close xperifirm and the .ftf will bundle as SOV35 instead of 8321. When you flash the phone the system firmware itself will write/update the phone to 8321. You might get an error or two, flashing it again right after should get rid of those. Make sure you know how to create the partition folder with the right contents for XZ and later models. A bit late, let me know if you still have it and are successful.