After installing TWRP, following the instructions precisely - at least as far as I can recall - I somehow messed up my PIT (partition information table fwiw). I noticed that I couldn't access my SD-card while in the recovery and upon exiting TWRP I encountered a bootloop. I tried to reflash my phone with a stock ROM but got an error message stating that 'There is no PIT partition'. Lovely. After owning the majority of the Galaxy S series and flashing them to tears, I finally encountered this issue.
I was rooting my S8 to tinker with remapping the Bixby button the hard but right way, without work-arounds. Found a thread on the S8+ forums, here's the link.
Anyway, long story short: I need a new PIT file from someone with an Exynos 64GB model. It's pretty easy to extract but you do need to be rooted.
The required terminal command is:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=580 skip=2176
It can be run on the device and through adb, superuser rights are required.
Would anyone be kind enough to help me out?
EDIT:
Welp, looks like I might be fine after all. There's a PIT file in the CSC-part of a stock ROM. Flashing stuff as we speak, will update. I feel stupid about not googling, I panicked because it's a brand new device and I assumed there wouldn't be any available. Goes to show how tricky assumptions are.`
EDIT 2:
Kill me now. I didn't read the instructions properly and forgot to hold the key-combo to enter recovery immediately after flashing TWRP.
I have the same problem but nothing works for me. I am unable to do anything with the phone at the moment. Please help me!
I can hopefully help..
TarekElsakka said:
I have the same problem but nothing works for me. I am unable to do anything with the phone at the moment. Please help me!
Click to expand...
Click to collapse
I've just overcome this issue with my S8 also however it took me over a day of research. This should hopefully help as for some reason my S8 doesn't like TWRP.
Firstly Download the BL file for AQG5 (google will reveal it).
Next, you should have your regions AP, BL, CSC and CP files to hand.
Open the CSC file with winzip or 7zip and extract just the .PIT file onto your desktop.
Now put your phone into download mode (power, bixby, volume down).
Open ODIN and connect your phone, in 'options' select 'repartition', then click the PIT tab and after the warning select the extracted PIT file that you placed on your desktop.
Also select the AQG5 BL file and ensure that this box is ticked.
Now in ODIN press start and it should repartition your phone. If it doesn't work for some reason (it didn't for me a couple of times) and gives the DEVICEINFO failure, you need to reenter download mode, and keep your fingers over those buttons (power, bixby, volume down). Now click start (it's a multi finger juggle proceedure) and keep hitting 'start' just as you've pressed the 'volume up' to go into download mode. For some reason the PIT will now be flashed and although you'll still have the boot screen you'll at least have the partition to be able to flash the rest of the software.
Finally, reset ODIN and restart, then select your regions Ap, BL, CSC and CP files, ensure that 'repartion isn't selected and click start.
Problem solved.. now try and find an alternative custom recovery because i can't find one.
Good luck.
Barry
holidayaddict1 said:
I've just overcome this issue with my S8 also however it took me over a day of research. This should hopefully help as for some reason my S8 doesn't like TWRP.
Firstly Download the BL file for AQG5 (google will reveal it).
Next, you should have your regions AP, BL, CSC and CP files to hand.
Open the CSC file with winzip or 7zip and extract just the .PIT file onto your desktop.
Now put your phone into download mode (power, bixby, volume down).
Open ODIN and connect your phone, in 'options' select 'repartition', then click the PIT tab and after the warning select the extracted PIT file that you placed on your desktop.
Also select the AQG5 BL file and ensure that this box is ticked.
Now in ODIN press start and it should repartition your phone. If it doesn't work for some reason (it didn't for me a couple of times) and gives the DEVICEINFO failure, you need to reenter download mode, and keep your fingers over those buttons (power, bixby, volume down). Now click start (it's a multi finger juggle proceedure) and keep hitting 'start' just as you've pressed the 'volume up' to go into download mode. For some reason the PIT will now be flashed and although you'll still have the boot screen you'll at least have the partition to be able to flash the rest of the software.
Finally, reset ODIN and restart, then select your regions Ap, BL, CSC and CP files, ensure that 'repartion isn't selected and click start.
Problem solved.. now try and find an alternative custom recovery because i can't find one.
Good luck.
Barry
Click to expand...
Click to collapse
I had the same issue as you, after making a multitude of mods to my phone (S8+) I ended up bricking it pretty good. It would not boot to recovery, like the recovery partition image was not there. I could only get it into download mode. After pissing with different versions of ODIN, I saw that it told me I had no PIT
I stumbled across your post and man o man, the amout of time and the way you have to finagle ODIN and the putting the phone in download mode sucks! You have like milliseconds to put the phone in download mode and start the flash via odin. Took me like 20 tries, but was finally able to flash the PIT file and the other AP, BL, CP, and CSC and finally, FINALLY got my phone back.
I will pay more attention to the mods I make, but at least I know I can recover from it.
Thanks Barry
i have a s8 with the same problem, but the pit way dosent work.
every flash ends in3 sec. with fail.
nighty said:
i have a s8 with the same problem, but the pit way dosent work.
every flash ends in3 sec. with fail.
Click to expand...
Click to collapse
Hi Nighty,
It does work...like I said in my post, you have to be lightening quick with putting the phone in download mode and hitting start in ODIN. Its almost like you have to hit start in ODIN a split second before ODIN shows the device as added. Its nerve racking and frustrating as hell, but it does work. I was using ODIN 3.12 if that helps. Not sure what version you use or what version Barry used.
Good luck and keep trying.
it works .. thx
I emailed TWRP about this issue as it's clearly not just my phone with the problem. They didn't reply.
Has anyone else found an alternative custom recovery for the S8 Exynos?
holidayaddict1 said:
I've just overcome this issue with my S8 also however it took me over a day of research. This should hopefully help as for some reason my S8 doesn't like TWRP.
Firstly Download the BL file for AQG5 (google will reveal it).
Next, you should have your regions AP, BL, CSC and CP files to hand.
Open the CSC file with winzip or 7zip and extract just the .PIT file onto your desktop.
Now put your phone into download mode (power, bixby, volume down).
Open ODIN and connect your phone, in 'options' select 'repartition', then click the PIT tab and after the warning select the extracted PIT file that you placed on your desktop.
Also select the AQG5 BL file and ensure that this box is ticked.
Now in ODIN press start and it should repartition your phone. If it doesn't work for some reason (it didn't for me a couple of times) and gives the DEVICEINFO failure, you need to reenter download mode, and keep your fingers over those buttons (power, bixby, volume down). Now click start (it's a multi finger juggle proceedure) and keep hitting 'start' just as you've pressed the 'volume up' to go into download mode. For some reason the PIT will now be flashed and although you'll still have the boot screen you'll at least have the partition to be able to flash the rest of the software.
Finally, reset ODIN and restart, then select your regions Ap, BL, CSC and CP files, ensure that 'repartion isn't selected and click start.
Problem solved.. now try and find an alternative custom recovery because i can't find one.
Good luck.
Barry
Click to expand...
Click to collapse
THANNK YOU SOOOO MUCH,I i had a recovery seandriod brick,and your method save me!!!
bricked my s8 with an attemt at TWRP flash, this perfect instruction unbricked it. Many kudo's!!! Saved me hundreds of $ can't thank you enough
sorry to resurrect an old thread, but would this method work with nand erase all with S8?
Hi.
Any chance someone can translate this into English?
"Firstly Download the BL file for AQG5 (google will reveal it).
Next, you should have your regions AP, BL, CSC and CP files to hand."
BL = Bootloop?
AQG5 = ???
AP = ??
BL = Bootloop?
CSC = Country Specific Code??
CP = ???
Have just bought a Galaxy SIII Mini GT-I8200 which I am trying to Root and/or install TWRP, with zero luck after 48 hours solid of trying various methods... ADB, ODIN, TWRP.apk etc. etc.
Have been using Linux Mint 20 but am gonna install Windows tomorrow as this is now beyond a joke. All I wanted to do was erase all the Google Nazi stuff.
ADB keeps coming back as unverified signature and ODIN is stuck on 'corrupted PIT file'.
So HOW does one resolve a fecked PIT file? when the instructions above are in a foreign language?
Any help will be greatly appreciated.
Two Tonne Tubbs said:
Hi.
Any chance someone can translate this into English?
"Firstly Download the BL file for AQG5 (google will reveal it).
Next, you should have your regions AP, BL, CSC and CP files to hand."
BL = Bootloop?
AQG5 = ???
AP = ??
BL = Bootloop?
CSC = Country Specific Code??
CP = ???
Have just bought a Galaxy SIII Mini GT-I8200 which I am trying to Root and/or install TWRP, with zero luck after 48 hours solid of trying various methods... ADB, ODIN, TWRP.apk etc. etc.
Have been using Linux Mint 20 but am gonna install Windows tomorrow as this is now beyond a joke. All I wanted to do was erase all the Google Nazi stuff.
ADB keeps coming back as unverified signature and ODIN is stuck on 'corrupted PIT file'.
So HOW does one resolve a fecked PIT file? when the instructions above are in a foreign language?
Any help will be greatly appreciated.
Click to expand...
Click to collapse
BL = Bootloader
AQG5 = Software version
AP = System firmware
CSC =Country specific code
CP= Modem
Flash your latest firmware first, with this pit file
Account Suspended
https://twrp.me/Devices/Samsung/ find the twrp version here and flash through odin.
Nice one.
I actually saw all the abbreviations in the Windoze version of Odin. They don't show in the Linux version.
Thank you
Related
Hey guys, I did a search on the topic but to no avail.
I have a pretty specific probably and am willing to pay a few bucks to anyone who can help me fix this issue.
I work for a mobile repairs place and we have an S4 9505 that a customer bought in, he took it upon himself to flash the latest firmware from sammobile which has resulted in the WiFi not working, you hit the button in the notifications panel and it goes half lit but not connected and never moves past that point. I tried flashing a different firmware and the WiFi fix from the WiFi fix and firmware post and that works initially but after one or two connections to a WiFi, it greys out again.
Thanks in advance.
Anytime there's wifi connect problem I've found that its the kernel.
Well, it is official firmware so there shouldn't be any software bugs. Unless, maybe, he flashed the wrong firmware on the wrong phone model.
check the wi-fi mac addres or make and efs restore, that happend when the files in efs/wifi/ where messed with, and thats a bad thing, flash a custom rom or flash a custom kernel see if it works
@Nationalmaverick
Hello,
You should try to flash the latest stock Lollipop firmware available.
-Download Odin 3.10 here
-Download and install USB drivers (skip this if you already have Kies or drivers installed)
-Download the firmware I9505XXUHOB7 here
Open Odin3.ini (found in extracted Odin package) and edit PhoneBootUpdate from 0k to 1, save and close. Then:
Extract downloaded firmware
Download and extract .pit file from the attached zip
Open Odin 3.10, choose PIT and load the extracted file
Load following files from extracted firmware: BL in BL, AP in AP, CP in CP and CSC in CSC
In Options, tick Repartition & untick Autoreboot
Put the device in download mode: power off->Volume down + power key->confirm with Volume up at Warning screen
Press Start
Once done pull battery out and put it back, then press and keep pressed Volume up + power key (you'll see a blue text, "Recovery booting"). Once in recovery (navigate with Volume up/down & power key to confirm) choose "Wipe data/factory reset" and confirm with "Yes", then choose "Reboot system"
Now your WiFi should work
Behold The Thread to solve your S7 Snapdragon Issue
- I have dealt with Odin errors for the last few days. Name as many as you can I've probably had it. The main issue is when people try to unroot by flashing stock ROM the phone will lock up (Soft Brick). This has happened to me many times in many different scenarios. Whether it presents itself with an eMMC error or any Fused Binary problems etc.
- Heres how to fix it.
- Unfortunately I am not allowed to post links yet but as soon as I can I will add them.
- Dowload your Stock firmware for your device.
- Download the S7 Snapdragon Root .tar for snapdragon
- Download the latest Odin Prince Comsy here
----------------------------------------------------------------------------------------------------
1.) Put your S7 into download mode by holding: Home + Power + Volume Down until you see a warning. Accept it.
2.) Go to the Modified Prince Cosmy Odin and open it up
3.) Grab the s7 Qualcomm .tar file from the root file you downloaded earlier and put it in the AP slot on Odin.
4.) Go to options on Odin and select: Nand Erase All, RE-Partition, Auto Reboot and F. reset time.
5.) Plug your S7 into your computer using a charging cord that is data transfer capable.
6.) After you see a blue or green box in Odin and see your device has been connected hit start
7.) After flashing the .tar root image. Put your phone back into download mode just like before and go back to Odin. (Make sure not to extract the zips inside the extracted USA ROOT zip.)
8.) Hit reset on Odin and go to options and select: Nand erase All, RE-Partition, Auto Reboot and F. reset time.
9.) Fill in BL, AP, CP, and CSC with your phones stock firmware and then select start. If all goes well it should restore your S7 to working condition.
- Make sure to extract all the downloads before you begin -
+ If you have an issue comment below and I or other helpful community members will help you!
+ If your device is not showing up make sure you have the latest Samsung phone drivers!
Hello everyone!
I have a Samsung SM-G935F which after a system update (a patch) is no longer working, it's stuck in boot loop.
When I turn it on I get: Kernel Rev check file Device 1, Binary 0.
I can get into the Download Mode and it will be recognized by ODIN.
But I don't know how to proceed in order to solve the presented scenario. Can you help me out? Thanks!
Regards,
Oliver
Hi, First you need to try to perform a format through recovery,holding power+home+volume up.
If phone did not boot,Then download firmware from sammobile using an app called SamFrim you can find it by simple search on google.
After you downloaded thr firmware,Launch odin and boot your phone into download mode by holding power+home+volume down.
Extract the firmware and it will generate 5 files
AP
BL
CP
CSC
Home_Csc
Add every file to its correct place in odin
AP
CP
BL
Csc( don't use Home_Csc,Because we want to perform a full wipe)
Then hit start, be careful not to unplug the cable,once it's done phone will auto reboot,leave it,It will do everything by its own.
Btw you must use latest odin version because older version doesn't support Oreo roms
Good Luck
Hi, my j500m is bricked because Install the firmware combination to eliminate the frp of the device at the end of the procedure, I proceeded to install the rom stock, in the middle of the installation (partition system) it is hung I left it for a long time and the same, and it happened to me with all the rom stock that download, in the end I searched and decided to install the rom with 4 recovery files and the pit file (BL, AP, CP, CSC and PIT file) when starting odin generated an error in the pit file the phone instead of now restarting in download mode as before I did it, now turn on and go directly into recovery, the computer does not recognize it in any way now and I cannot recover how it would solve this problem
kiomet said:
Hi, my j500m is bricked because Install the firmware combination to eliminate the frp of the device at the end of the procedure, I proceeded to install the rom stock, in the middle of the installation (partition system) it is hung I left it for a long time and the same, and it happened to me with all the rom stock that download, in the end I searched and decided to install the rom with 4 recovery files and the pit file (BL, AP, CP, CSC and PIT file) when starting odin generated an error in the pit file the phone instead of now restarting in download mode as before I did it, now turn on and go directly into recovery, the computer does not recognize it in any way now and I cannot recover how it would solve this problem
Click to expand...
Click to collapse
Doe's your phone go into download mode, if yes try to uninstall Samsung drivers and install them again and try again with another USB cable
Mscreams said:
Doe's your phone go into download mode, if yes try to uninstall Samsung drivers and install them again and try again with another USB cable
Click to expand...
Click to collapse
the drivers is not problem and i use 3 USB
kiomet said:
the drivers is not problem and i use 3 USB
Click to expand...
Click to collapse
Try to use 2 USB
My tablet does not start and shows this message: An error has occurred during device update. Please use the Emergency recovery Function in the Smart Switch PC Software
I tried downloading Smart Switch and opening the Device emergency recovery menu but nothing shows up in the device list.
Then I tried downloading Odin and a firmware, the device was recognized, I imported all the files (including the PIT FILE), checked Nand Erase and Repartition, started the flash but soon after it fails at Complete Write operation Failed.
How can I restore functionality of my tablet?
RobyGuizzo said:
My tablet does not start and shows this message: An error has occurred during device update. Please use the Emergency recovery Function in the Smart Switch PC Software
I tried downloading Smart Switch and opening the Device emergency recovery menu but nothing shows up in the device list.
Then I tried downloading Odin and a firmware, the device was recognized, I imported all the files (including the PIT FILE), checked Nand Erase and Repartition, started the flash but soon after it fails at Complete Write operation Failed.
How can I restore functionality of my tablet?
Click to expand...
Click to collapse
Try flashing with Odin but do not select nand erase or repartition. Also don't select the PIT file it will pull pit from csc if it needs it. Check settings and make sure only reboot and f.reset time are selected. It should go normally, if not may need to look at country change.
tek3195 said:
Try flashing with Odin but do not select nand erase or repartition. Also don't select the PIT file it will pull pit from csc if it needs it. Check settings and make sure only reboot and f.reset time are selected. It should go normally, if not may need to look at country change.
Click to expand...
Click to collapse
It doesn’t work and it gives this error:
RobyGuizzo said:
It doesn’t work and it gives this error:
Click to expand...
Click to collapse
Try flashing BL only. I'm confused by five sections that you're flashing. But just try them one at a time starting with BL then CSC then AP. Un-tick auto reboot for BL and CSC let it auto reboot after AP. You will have to manually reboot download mode after each.
Home_CSC keeps /data and CSC performs factory reset wiping /data. You don't flash both.
If that doesn't work look at this video
You may need to download a different firmware.
tek3195 said:
Try flashing BL only. I'm confused by five sections that you're flashing. But just try them one at a time starting with BL then CSC then AP. Un-tick auto reboot for BL and CSC let it auto reboot after AP. You will have to manually reboot download mode after each.
Home_CSC keeps /data and CSC performs factory reset wiping /data. You don't flash both.
If that doesn't work look at this video
You may need to download a different firmware.
Click to expand...
Click to collapse
I flashed BL, it failed at the end, then I tried to flash CSC and it gives Re Partition operation failed. I tried the others but says that there isn’t any PIT PARTITION. Now it doesn’t go into download mode and the screen flickers.
RobyGuizzo said:
I flashed BL, it failed at the end, then I tried to flash CSC and it gives Re Partition operation failed. I tried the others but says that there isn’t any PIT PARTITION. Now it doesn’t go into download mode and the screen flickers.
Click to expand...
Click to collapse
If not download mode then what does it go into ? What is flickering on screen ? Have you tried a different firmware ?
tek3195 said:
If not download mode then what does it go into ? What is flickering on screen ? Have you tried a different firmware ?
Click to expand...
Click to collapse
Where can I download the right firmware?
It goes into the emergency recovery screen.
RobyGuizzo said:
Where can I download the right firmware?
It goes into the emergency recovery screen.
Click to expand...
Click to collapse
go to easy-firmware and find the one you think to be most suited for your tablet and let me know and I will grab it for you on my account
RobyGuizzo said:
Where can I download the right firmware?
It goes into the emergency recovery screen.
Click to expand...
Click to collapse
I found a UK version on Sammobile. I think the problem is that you are flashing way too much. Try flashing just AP and BL. They are the ones that get messed up.
lewmur said:
I found a UK version on Sammobile. I think the problem is that you are flashing way too much. Try flashing just AP and BL. They are the ones that get messed up.
Click to expand...
Click to collapse
I had mentioned Easy-firmware so he could select from 40 different versions. Have to agree, flashing too much. I had the same error one time years ago and had to flash firmware from a different region to clear it then flashed correct region. I got that solution off youtube but didn't see it when I looked for this now. Know anything about that ?
tek3195 said:
I had mentioned Easy-firmware so he could select from 40 different versions. Have to agree, flashing too much. I had the same error one time years ago and had to flash firmware from a different region to clear it then flashed correct region. I got that solution off youtube but didn't see it when I looked for this now. Know anything about that ?
Click to expand...
Click to collapse
It's been a couple of years since I ugraded my last 2016 to a 2020, but I recall having problems when flashing CSC back then. And there was no USERDATA.
lewmur said:
It's been a couple of years since I ugraded my last 2016 to a 2020, but I recall having problems when flashing CSC back then. And there was no USERDATA.
Click to expand...
Click to collapse
Exactly, BL, AP, CP and CSC or HOME-CSC is it for this tablet as well. There is no USERDATA. @RobyGuizzo flashing anything in the userdata section of odin could be a bad thing.
tek3195 said:
Exactly, BL, AP, CP and CSC or HOME-CSC is it for this tablet as well. There is no USERDATA. @RobyGuizzo flashing anything in the userdata section of odin could be a bad thing.
Click to expand...
Click to collapse
To me the first rule of diognostics is to isolate the elements. We know AP and BL are essential. So which one of the others are the problem?
lewmur said:
To me the first rule of diognostics is to isolate the elements. We know AP and BL are essential. So which one of the others are the problem?
Click to expand...
Click to collapse
I don't know, but that error seems to lock it in some way. I know frp hijacker software is reported to allow flashing with that error. As did different region when I had it before. It's not just a corrupt partition but a lock of some kind.