Database Users

[Q] G900F dead, help me fix it please!

First: Yes i've tried Odin flashing stock rom, recovery and all the other things!
So from the beginning:
My phone unlocked itself in my pocket and some weird things happend (i don't know what).
When I took it out it said that my sd-card could be safely removed
Then it said it was coruppted (I checked it on my laptop and it wasn't)
Then it started to reboot, and suddenly got stuck in bootloop!
When I pulled out the battery and put that in again. it booted black screen with text in the left uppercorner with some things about not being able to boot because there's no XXXX partition and some other things I cant remember.
So I thought, let's try and flash stock rom on it, and did that. Flash failed with error (size) or something.
Then I thought, let's reboot into recovery (How dumb that I haven't thought of that before) When I tried it it just bootlooped trying to get into recovery everytime.
Flashed new recovery, Still the same problem.
Flashed stock rom of another country, It worked but after odin finished and rebooted my phone it tries to boot itself into recovery (bootloop)
So nothing worked...
Download mode says this:
Current binary: Samsung official
system status: custom
Reactivation lock(kk): off
knox warranty void 0x1 (4)
qualcomm secureboot: ENABLE (CSB)
rp swrev: s1, t1, r1, a1, p1
udc start
I really don't know what to do, can you guys please help me?
Thanks in advance.
Donovan Nice

PMed you my Skype. Contact me if needed

Try to repartition your S5 with a pit file in Odin, maybe the filesystem is corrupt.
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Download the pit fole for a G900F, load it as PIT in Odin, tick "Re-Partition", and start.

v3rtex said:
Try to repartition your S5 with a pit file in Odin, maybe the filesystem is corrupt.
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Download the pit fole for a G900F, load it as PIT in Odin, tick "Re-Partition", and start.
Click to expand...
Click to collapse
Must it be pit only? I tried pit file together with stock ROM but that didn't work

I would try it step by step, so pit only first.
Is there any error message in odin?

Flashed pit file, succesfull. No errors. Phone still stuck in bootloop

Try to flash pit file with your pda stock firmware, check repartition, and uncheck Auto reboot.
Start, wait until it says pass, unplug your phone, remove your battery, wait a minute or so, put it back in, and try to boot into recovery with vol up/home/power.
Important is, try to wipe your cache and do a factory reset then.

v3rtex said:
Try to flash pit file with your pda stock firmware, check repartition, and uncheck Auto reboot.
Start, wait until it says pass, unplug your phone, remove your battery, wait a minute or so, put it back in, and try to boot into recovery with vol up/home/power.
Important is, try to wipe your cache and do a factory reset then.
Click to expand...
Click to collapse
This time I got a fail.. @hidden.img.ext4 "FAIL (size)"
F. Reset Time was checked but that shouldn't do anything right

donoboy97 said:
This time I got a fail.. @hidden.img.ext4 "FAIL (size)"
F. Reset Time was checked but that shouldn't do anything right
Click to expand...
Click to collapse
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...

v3rtex said:
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...
Click to expand...
Click to collapse
Recovery + pit works, pulled out the battery, waited a minute or so. Booted in recovery, get's the blue message.. and then bootloops again...

Gonna try nand erase, as you said I have nothing to lose. Wish me luck I guess?

long shot but check md5's on your downloads.. my first guess was the pit file but u said that didnt work

elliwigy said:
long shot but check md5's on your downloads.. my first guess was the pit file but u said that didnt work
Click to expand...
Click to collapse
md5's match!

v3rtex said:
Have you tried the same with your recovery file?
If that fails again, the only idea i have at least is to check "nand erase all" checkbox in odin while flashing stock fw or recovery, try with and without pit and "re-partition", and without "autoreboot"
In some situations this fixed bootloops and steck bootloader issues.
At least you have nothing to loose...
Click to expand...
Click to collapse
NAND-erase / Flashed stock rom: Did not work. NAND-erase /Flashed recovery: Did work, booted up in recovery... Bootloop. My phone is broken hard

donoboy97 said:
NAND-erase / Flashed stock rom: Did not work. NAND-erase /Flashed recovery: Did work, booted up in recovery... Bootloop. My phone is broken hard
Click to expand...
Click to collapse
when u say boots to recovery and bootloops, what do you mean exactly? like goes to recovery and immediately reboots?
can you screenshot exact error of odin when you use the pit and stock tar? also, i assume you have usb drivers and the right odin installed? try different usb ports/cables?
---------- Post added at 05:25 PM ---------- Previous post was at 05:25 PM ----------
if it boots at all then its not a hard brick so there is still hope

elliwigy said:
when u say boots to recovery and bootloops, what do you mean exactly? like goes to recovery and immediately reboots?
can you screenshot exact error of odin when you use the pit and stock tar? also, i assume you have usb drivers and the right odin installed? try different usb ports/cables?
---------- Post added at 05:25 PM ---------- Previous post was at 05:25 PM ----------
if it boots at all then its not a hard brick so there is still hope
Click to expand...
Click to collapse
it goes to recovery for 5 secs and then reboots, exact error is when it's flashing "hidden.img.ext4" and then it says "FAIL! (size)" Yes I have USB drivers and I'm using Odin v3.10 but I just checked on some threads, and they all say v3.09 soo.. could that be the problem?
I also tried different ports and cables but i'm mainly using the official cable!

donoboy97 said:
it goes to recovery for 5 secs and then reboots, exact error is when it's flashing "hidden.img.ext4" and then it says "FAIL! (size)" Yes I have USB drivers and I'm using Odin v3.10 but I just checked on some threads, and they all say v3.09 soo.. could that be the problem?
I also tried different ports and cables but i'm mainly using the official cable!
Click to expand...
Click to collapse
try odin 3.09 and report back.. i know its wonky sometimes with certain odin versions.. normally there is a hidden.img.ext4 in the tar file.. have you tried other odin tars? different or older odin tars? it almost seems like something wrong with the tar file or odin version

it's taking a while, please hold

elliwigy said:
try odin 3.09 and report back.. i know its wonky sometimes with certain odin versions.. normally there is a hidden.img.ext4 in the tar file.. have you tried other odin tars? different or older odin tars? it almost seems like something wrong with the tar file or odin version
Click to expand...
Click to collapse
Nope v3.09 did not work, tried redownloaded stock rom, stock rom from another country, and all of them with pit file..

did u dl tar from sammobile or elsewhere?

S7 Edge G935F // Faulty ODIN flash // Stuck in Bootloader [SOLVED]

Hi Guys,
today I wanted to flash the latest Stock ROM for my device via ODIN. I've done this many times before and (thought) I knew what I was doing. It is my third Phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly I wasn't aware that this particular device was locked.
After downloading the international firmware I tried to install it and ODIN got stuck while writing the system.img. After that my phone did not boot up (of course). After that I downloaded and tried to isntall the firmware of the carrier, but I had the exact same issue. When I turn my device on I get to an error screen which tells me to execute an "emergency recovery" via the Samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
FRP hinders me to install a custom recovery and the stock one does not allow any isntallations via ADB or SD card.
My qustion is: Does anyone know how I can install a rom from here?
I know that I had to have made some changes prior to the flashing, but as I said I was not aware and an Idiot for not double checking.
Since it is not bricked yet I suppose there must be an answer but I can't find anything.
Thanks in advance
Edit:
After only installing the stock bootloader, I am autmaticly entering it when I boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"

Fix
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.

fabivons said:
hi guys,
today i wanted to flash the latest stock rom for my device via odin. I've done this many times before and (thought) i knew what i was doing. It is my third phone frome the same carrier and none of them were branded/ locked devices before. Unfortunatly i wasn't aware that this particular device was locked.
After downloading the international firmware i tried to install it and odin got stuck while writing the system.img. After that my phone did not boot up (of course). After that i downloaded and tried to isntall the firmware of the carrier, but i had the exact same issue. When i turn my device on i get to an error screen which tells me to execute an "emergency recovery" via the samsung smart switch software. But it too gets stuck on some point and only gets me to an error screen.
Frp hinders me to install a custom recovery and the stock one does not allow any isntallations via adb or sd card.
My qustion is: Does anyone know how i can install a rom from here?
I know that i had to have made some changes prior to the flashing, but as i said i was not aware and an idiot for not double checking.
Since it is not bricked yet i suppose there must be an answer but i can't find anything.
Thanks in advance
edit:
After only installing the stock bootloader, i am autmaticly entering it when i boot my devive. On the bottom of the screen is an error message: "dm-verity verification failed...
E:failed to mount /system (invalid argument)"
Click to expand...
Click to collapse
have u solved your problem ? This problem i am facing on the s7edge nougat ? Plz help ?

Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might be worth a try!
Good luck!

Fabivons said:
Hey,
look at the second post I made in this thread. There is described how I got my S7 up and running again. I'm not sure if it is a valid solution since it felt like trial and error to me, but I'm writing this text from my S7 so it might me worth a try!
Good luck!
Click to expand...
Click to collapse
y i have done that and the device boots up but some applications force close and when i insert the memory card , the phone gets restarted everytime

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Tell us in detail now.

SjDU said:
Tell us in detail now.
Click to expand...
Click to collapse
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.

Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?

suhaibahmad said:
the time when u were fixing your device , you were on marshmallow or nougat ? beacuse i am on nougat and whenever i flash twrp , it stucks there and not booting into it even i have ticked the oem unlock and usb debugging in developer mode ?
Click to expand...
Click to collapse
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.

Fabivons said:
Does the TWRP flash complete? Can you boot up the OS after you flashed TWRP? (And did you download the correct version of TWRP for your device?)
As a last resort, you could try and flash marshmallow on your device and see if it works there.
Click to expand...
Click to collapse
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally

suhaibahmad said:
if i flash marshmallow it doesnt even boot up and in the odin mode showing binary and everything as custom , if i flash nougat and then flash twrp and try to manually boot into twrp it stucks on the s7edge screen which comes before recovery , and if i boot the mobile normally without the button combination then it stucks on the second logo SAMSUNG . if i flash again the stock recovery then boots normally
Click to expand...
Click to collapse
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.

Fabivons said:
Have you tried to perform a regular factory reset via the OS on nougat? Sometimes that does the job, too.
But as I said. I can only give you my best guess here - my phone worked after my procedure, so I didn't investigate further.
And don't forget: Google is your friend.
Click to expand...
Click to collapse
thats your kindness , yes i have performed the factory reset several times from recovery , but when i trying to reset it from settings , it goes after restart to recovery with dm-verity error , then i wipe and factory reset from there

Fabivons said:
For anyone in the same situation: I fixed it.
In the end all you have to do is flash the firmware with the fitting PIT file. If you firmware consists of multiple files and there is a "HOME"-file, flash it with this one first on the AP slot in ODIN. After that the same again just use the AP file this time.
My phone is up and running again now.
Click to expand...
Click to collapse
Fabivons said:
"please"
I described everything I did in the posts before.
As soon as you can enter the system again all you need to do is deactivate the locks I was talking about in my first post and perform a full wipe.
After that you can install any ROM you want via ODIN just like you are used to.
If that doesn't work for you, I don't have any answers either.
But again:
Prep work:
1. Download most recent ODIN
2. Download the correct firmware for your carrier (from www.sammobile.com)
3. Download the correct PIT file for your device
4. Put your device in download mode
Process:
1. Extract your firmware if it is a zip
2. Start up ODIN
3. Connect your device and check if it's detected by ODIN
3. Put the PIT file in ODIN
4. Put the "HOME" file of your firmware in the PDA slot of ODIN
5. Press start
6. When finished unplug your device and restart phone and ODIN
7. Reconnect your phone and check if it's detected by ODIN
8. Put all the other files of your firmware + the PIT in the correct slot in ODIN
9. Press start
After that my device booted up but still was, as you described too, a little buggy. So I deactivated FRP, activated USB debugging in the dev options, installed TWRP, performed a full wipe and installed another firmware of my choosing via ODIN (without a PIT file this time).
I am running 7.0 on my device now and it works flawlessly.
Click to expand...
Click to collapse
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model

SjDU said:
Well I had the same issue but Odin method didn't work for me on Nougat. And also FRP lock was On. every time I flashed the files it give me FRP on error. so I had to use Smartswitch. Even though I used original csc and ap files with latest Odin. BTW I have SM-G935FD model
Click to expand...
Click to collapse
Well FRP has to be turned off (the button in the menu is called "OEM unlock, the button has to be set to on which deactivates FRP). You don't mention using a PIT file - did you use one?

Corrupted PIT

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

T280 - Can not flash back to stock, secure check fail (boot)

Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
To install TWRP:
1. Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
2. Load the respective file below into the AP slot and hit start.
3. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
TWRP_3.0.2-1_SM-T280_261016
Click to expand...
Click to collapse
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request

ngvhoang96 said:
Summary: My tablet is soft-brick now. Can only access to Download (ODIN) mode. I have tried 2,3 different firmwares, tried 3 versions of ODIN. But it doesn't work.
Here is the story:
I bought this tablet from bestbuy (USA)
I only wanted to root my tab A 7.0 SM-T280.
I enabled the OEN unlock from the developer mode.
Then I tried to flash the TWRP by the tutorial from this topic by @ashyx :
After flashing, on the download mode it showed: "SECURE CHECK FAIL: (RECOVERY)", then I reboot into recovery mode to access the TWRP but it said: "RECOVERY IS NOT SEANDROID FORCEFUL (although in ashyx topic said the SECURE FAIL is fine).
I still was able to reboot into the system this time.
And then I thought I should try another way. And then I came up with the TINKER ROM.
I tried to flash the Rom (v5) but somehow ODIN said FAIL.
I COULD NOT access the system since then.
Bu @zenful 's advices, I tried some different stock firmwares and different versions of ODIN just to get back to normal, but it never works.
Every time I flash, it always has the same problem:
- First try, ODIN fails at:
sboot.img
sboot2.img
complete (write) failed... (I don't remember though)
And in the download mode screen (from the phone) said:
SECURE CHECK FAIL (SBOOT)
SECURE CHECK FAIL (SBOOT2)
- Second try, ODIN fails at:
boot.img
system.img
Complete (write) fail...
And in the screen said:
SECURE CHECK FAIL (BOOT)
SECURE CHECK FAIL (RECOVERY)
I also tried emergency recovery mode in smart switch but it didn't solved the problem. One good thing (after I entered the tablet model and serial number) is that it showed "PHONE: QA4 CSC: PH3 (XAR)"
______________
I'm pretty sure that the problem doesn't come from fw nor from ODIN since I downloaded the fws from sammobile and updato and downloaded ODIN from xda (the latest version from samsungodin.com)
I'm seriously need a help right now. I just wanna have a rooted tablet so I can play game with my ps4 controller.
I have experienced with these flashing business. I rooted my galaxy s2, HTC desire c, HTC evo, etc. and so on, but have never done rooting in the last 1 year. I can attach some snapshots if you guys request
Click to expand...
Click to collapse
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.

Stixas said:
Try this: download your desire firmware via samfirm (BL+AP+CP+CSC when extracted) plus you need a pit file for your model with the same region as firmware and then flash (with 4 firmware files incl pit) via odin autoreboot+repartition+nand erase+f.reset time. At least you will get working stock tablet. It worked on my note 4 soft bricked.
Click to expand...
Click to collapse
Last time I tried download fw by using samfirm was last week and it didnt work. Can you test yours again?
And whre can I found the pit file? I dont think there is one in the internet right now.

Bricked J500M Any solution PC no recognize

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