Develop Bugs

unable to write PIT

Dear friends,
I have a problem with my NOTE 2.
I'm unable to write PIT table,
and for this reason I cannot write any ROM on the phone because the PIT table doesn't exists.
I tried multiple cables and multiple pc,
but still have no success.
Odin stuck
Anyone got this fixed?
rgds,
thomas

anyone can help me?

download the pit file in here .. http://d-h.st/Dlv , Re-Partition in odin..

free image hosting
stuck here
tried multiple usb cables and multiple pc

tbudicin said:
free image hosting
stuck here
tried multiple usb cables and multiple pc
Click to expand...
Click to collapse
the pic too small ,I can't see what in it....

deadman12, the screenshot shows the following:
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
<ID:0/011> Get PIT for mapping..
Options checked:
- Auto Reboot
- Re-Partition
- F. Reset Time
PIT file has been selected in the PIT field.
(Just posting this to try to help out the OP, not trying to hijack the thread or anything)
To the OP, I have noticed that in your screenshot you have not selected a ROM in the PDA field to flash to the phone along with the PIT file. Have you tried doing this?

I had this issue where data failed to mount. Used odin to repartition with the pit file. I select the stock rom tar 4.1.1 on the pda tab. Works after that.
Sent from my GT-N7100 using xda premium

hayabusa08 said:
I had this issue where data failed to mount. Used odin to repartition with the pit file. I select the stock rom tar 4.1.1 on the pda tab. Works after that.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Hi your device is n7105 or n7100?

7100. Make sure u flash the correct model pit file.
Sent from my GT-N7100 using xda premium

Thanks guys to post replies in my thread.
@kcnskenn: thank you for posting image info!
My device is 7100.
I tried also to use pit together with PDA but no works either.
I think the problem is not so simple, because when i enter in download mode I don't see model.
maybe bootloader is corrupted.
I found a guide to copy boot from sd to phone opening the phone and bypass a resistor, but the note2 hardware design is different and i cannot find the same resistor. anyone tried this?
thomas

Sorry cant be of more help bro.
Sent from my GT-N7100 using xda premium

tbudicin said:
Thanks guys to post replies in my thread.
@kcnskenn: thank you for posting image info!
My device is 7100.
I tried also to use pit together with PDA but no works either.
I think the problem is not so simple, because when i enter in download mode I don't see model.
maybe bootloader is corrupted.
I found a guide to copy boot from sd to phone opening the phone and bypass a resistor, but the note2 hardware design is different and i cannot find the same resistor. anyone tried this?
thomas
Click to expand...
Click to collapse
your device is infected with SDS syndrome , ( EMMC ic needs to be replaced )

Flashing stop at data.img D710

Flashing stop at data.img in my galaxy s ii sprint
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> Sbl.bin
<ID:0/013> param.lfs
<ID:0/013> zImage
<ID:0/013> factoryfs.img
<ID:0/013> data.img
than stop
I have try with SPH-D710_FI27 and SPH-D710_FL24 and same problem

apas100 said:
Flashing stop at data.img in my galaxy s ii sprint
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Set PIT file..
<ID:0/013> DO NOT TURN OFF TARGET!!
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> Sbl.bin
<ID:0/013> param.lfs
<ID:0/013> zImage
<ID:0/013> factoryfs.img
<ID:0/013> data.img
than stop
I have try with SPH-D710_FI27 and SPH-D710_FL24 and same problem
Click to expand...
Click to collapse
Hi apas100,
So it never fails, it just stops?
My first suggestion - Using PC Odin, I would flash the FL24 low ship tar. You can find this in RWilco's Rom Repo. Use the FL24 Original Tar. (Place in PDA slot in Odin)
Let's see if that works for you.

Hi MoHoGalore
Yes , just stops not fails
I will try with this Rom

I did with this rom but same thine
It's stops at data

Did anything happen before that that caused you to flash a one click?
And what happens if you flash a nodata version?

apas100 said:
I did with this rom but same thine
It's stops at data
Click to expand...
Click to collapse
Can you take a screen shot of the progress?
Also, do you know where to get the pit file and how to add that to that Odin flash? If not, I can link and write the steps but it'll be a few hours.

garwynn said:
Did anything happen before that that caused you to flash a one click?
And what happens if you flash a nodata version?
Click to expand...
Click to collapse
I got this phone with this message "Firmware upgrade encoutered and issue. Please select recovery mode in Kies & try again."
When I flash a nodata it will flash but the phone dosen't start , It stops with loge samsong
MoHoGalore said:
Can you take a screen shot of the progress?
Also, do you know where to get the pit file and how to add that to that Odin flash? If not, I can link and write the steps but it'll be a few hours.
Click to expand...
Click to collapse
Yes I know , Copy of screen in attach files
.

android+slp? What are you flashing? I'm seriously drawing a blank on me, Garwynn or anyone else packing something named like that..
Link to that please?

MoHoGalore said:
android+slp? What are you flashing? I'm seriously drawing a blank on me, Garwynn or anyone else packing something named like that..
Link to that please?
Click to expand...
Click to collapse
Looks like he might have yanked odin from another package similar to CF autoroot by chainfire.
☆SoA: Son's of Android™☆
I like to break stuff!

-EViL-KoNCEPTz- said:
Looks like he might have yanked odin from another package similar to CF autoroot by chainfire.
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
The black title bar populates from the title when created. Must be old if it's pertaining to our device. I just don't remember seeing it..

Ignore the title. It's plain Odin 1.85 and not the problem here.
Back to this:
I got this phone with this message "Firmware upgrade encoutered and issue. Please select recovery mode in Kies & try again."
Click to expand...
Click to collapse
Who did you get the phone from? Go ask that person what they flashed before that. Then go tear them a new one for not telling you in advance that they triggered the eMMC bug.
The telltale signs are there that it's this. Odin issues, stuck on data (which the phone locks up and freezes, requires a battery pull, right?) It sounds almost like a dead ringer for the eMMC bug. And if you didn't know it when you got the phone (and especially if you paid for it) you got a bad shake on it.
If you have Sprint, get TEP on it ASAP and get it swapped out. If you can't I can get you going again but you're going to lose part of your internal memory. Let me know which way you want to go.

MoHoGalore said:
The black title bar populates from the title when created. Must be old if it's pertaining to our device. I just don't remember seeing it..
Click to expand...
Click to collapse
I never pay attention to it lmao. I don't use Odin much anymore anyways unless it's an emergency like these last 5x I've borked my IMEI/MEID and had to Odin a modem to fix it >_<
☆SoA: Son's of Android™☆
I like to break stuff!

-EViL-KoNCEPTz- said:
I never pay attention to it lmao. I don't use Odin much anymore anyways unless it's an emergency like these last 5x I've borked my IMEI/MEID and had to Odin a modem to fix it >_<
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
You can also make it say whatever you want by putting a Odin3.ini file in the Odin folder and saying
[Option]
Title= I am the best

I did it with Odin3 v3.04 and same thing
Now when I turn it on I get "Firmware upgrade encoutered and issue Please select recovery mode in Kies & try again"
I got it from ebay so I don't know history of it , I just want to make it working

Let's assume the emmc bug is triggered.
You need to do a few things:
1. Get a MicroSD card if you don't have one already.
2. Put on the MicroSD card:
HG42's Find Brick (Beginning to End) CWM App.zip
HG42's Find Brick (End to Beginning) CWM App.zip
Source: hg42's Partition Scanner Thread
(A big shout out to Hg42 for his efforts here and here on this project!)
3. Download and flash via Odin:
FL24 Kernel with Agat's tRec 0.2.2 (v0.4.0, FL24 based)
4. Reboot to recovery by holding vol. up and power until you see Agat's recovery.
You now have to verify where the emmc bug trigger starts and stops to work around it.
So keep the battery cover off for the next few steps.
5. In recovery run the find_brick_start zip.
Wait until it freezes - if it's the eMMC bug it should.
hg42 said:
If it freezes, the block shown last with "..." at end of line is the first bricked block in that direction.
The line before with "-> ok" is the first usable block before/after the brick.
Click to expand...
Click to collapse
You'll know because you'll see it moving at a pretty steady clip and then just stop dead in its tracks.
If it somehow goes through the entire script and doesn't hang, stop here and let us know.
6. Assuming you were hung up on Step 5, note where it bricked. (the ... block)
Now pull the battery, put it back in, boot to recovery and do the other zip.
Wait until it hangs and note it.
You know know where it bricks. This is important because that part of memory is now unusable.
Step 7
Now go to the OP of this thread and download pits-Epic4GT.zip.
Unzip it, look inside the pits-patched folder.
Inside you're only going to care about the files with DATAFS in the name. Ignore the rest.
Now, look for the pit file that patches between your start (Step 5) and end (Step 6)
It should always start at 00922 and normally ends 2 GB later. (ex. 3070MB)
Your start and stop must be within the range of the pit fix or it will lock up again later.
Hold on to this pit file. You will need it for every Odin flash you do.
Step 8
Using Odin, flash any full restore (rooted/unrooted), include the pit and check "repartition".
This will repartition and format your phone to "work around" the black hole that is the eMMC bug.
This is a lengthy process but should get you in the game.
I caution against flashing custom ROMs though because if anything touches that bad area it will lock up your phone and require a battery pull.
Lastly - if you are on Sprint, still consider taking it to a store, requesting TEP and then asking them to look at and/or replace it. This is just a workaround and the wear leveling could slip back in and start trying to use that block eventually.
Can you PM me the details when you can including the ebay item #? (link okay) If they didn't add this to the description you should file a dispute immediately on it and honestly try to recover some/all of what you paid for the phone IMHO - especially if in the past 30 days.

I have nothing else to add to this thread other than a standing ovation for your help. Well done!
Hope the OP gets this resolved!
Sent from my SPH-D710 using XDA

Photos will talk , to know what is happen exactly
Photos in ATTACH FILES

apas100 said:
Photos will talk , to know what is happen exactly
Photos in ATTACH FILES
Click to expand...
Click to collapse
In first one you didn't add the pit file and check re-partition. What was the result of that one?
If it I rebooted on its own we can immediately rule out the eMMC bug. Good news but still need to fix your partitions.
Sent from my SPH-L900 using Tapatalk 2

garwynn said:
In first one you didn't add the pit file and check re-partition. What was the result of that one?
If it I rebooted on its own we can immediately rule out the eMMC bug. Good news but still need to fix your partitions.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Do u mean I have to check re-partition and add the pit file , Ok I will do that but which file there many files in pits-patched

apas100 said:
Do u mean I have to check re-partition and add the pit file , Ok I will do that but which file there many files in pits-patched
Click to expand...
Click to collapse
Try just the regular pit file.
Sent from my SPH-L900 using Tapatalk 2

Galaxy S3 Can't Mount

I have a Galaxy S3 T-Mobile. It is running cyanogenmod 11. Suddenly it randomly rebooted and bootlooped. I went into recovery to reflash the rom,
but I got
E:can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E: cant mount /cache/recovery/last_log
E: can't open cache/recovery/last_log
E: can't mount /sdcard
I am not able to install any rom or anything. I have tons of photos and important data on my internal sd card. Is there a way I can save my phone and save all my data?

Boot custom recovery and use the built in file manager to copy items to your external sdcard. If thst doesnt work try using adb to pull what you need.

DocHoliday77 said:
Boot custom recovery and use the built in file manager to copy items to your external sdcard. If thst doesnt work try using adb to pull what you need.
Click to expand...
Click to collapse
Thanks. After that do I just odin back to stock touchwiz?

DocHoliday77 said:
Boot custom recovery and use the built in file manager to copy items to your external sdcard. If thst doesnt work try using adb to pull what you need.
Click to expand...
Click to collapse
adb recognizes my device but pulling isn't working

DocHoliday77 said:
Boot custom recovery and use the built in file manager to copy items to your external sdcard. If thst doesnt work try using adb to pull what you need.
Click to expand...
Click to collapse
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.

Sorry, been gone all day. Look in the .tar.md5 archive and see what is inside. It shouldn't be saying single download unless theres only one item inside. Where did you download it from? You can get it from my firmware thread if you want an alternative source. Its linked in my thread, stickied in development.
Did adb give you any errors?

DocHoliday77 said:
Sorry, been gone all day. Look in the .tar.md5 archive and see what is inside. It shouldn't be saying single download unless theres only one item inside. Where did you download it from? You can get it from my firmware thread if you want an alternative source. Its linked in my thread, stickied in development.
Did adb give you any errors?
Click to expand...
Click to collapse
got it from your thread. http://forum.xda-developers.com/showthread.php?t=1949687
I don't think it can be extracted.
When I tried to pull files it said 0 files out of 0 pulled. adb worked though. recognized my device etc.

Kyle Chen said:
got it from your thread. http://forum.xda-developers.com/showthread.php?t=1949687
I don't think it can be extracted.
When I tried to pull files it said 0 files out of 0 pulled. adb worked though. recognized my device etc.
Click to expand...
Click to collapse
I am thinking of using this: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/

Kyle Chen said:
got it from your thread. http://forum.xda-developers.com/showthread.php?t=1949687
I don't think it can be extracted.
When I tried to pull files it said 0 files out of 0 pulled. adb worked though. recognized my device etc.
Click to expand...
Click to collapse
Did you try using the built-in file manager in TWRP? Pretty sure cwm has it too. Im guessing you have an insecure kernel so im not sure why adb isnt working.
You can also factory reset from TWRP/CWM. It won't wipe internal sdcard. Might get it booting again too, or allow you to flash.
And you can extract the firmware. There should be multiple files inside. Use 7zip or winrar. Did you check the md5sum on the download page? Sounds like it may have been a bad download.
Kyle Chen said:
I am thinking of using this: http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Click to expand...
Click to collapse
Thats mostly for hard bricks where you cant even boot download mode or recovery. If nothing here can get it working, you can try that, but it may be a hardware failure that cant really be fixed.

DocHoliday77 said:
Did you try using the built-in file manager in TWRP? Pretty sure cwm has it too. Im guessing you have an insecure kernel so im not sure why adb isnt working.
You can also factory reset from TWRP/CWM. It won't wipe internal sdcard. Might get it booting again too, or allow you to flash.
And you can extract the firmware. There should be multiple files inside. Use 7zip or winrar. Did you check the md5sum on the download page? Sounds like it may have been a bad download.
Thats mostly for hard bricks where you cant even boot download mode or recovery. If nothing here can get it working, you can try that, but it may be a hardware failure that cant really be fixed.
Click to expand...
Click to collapse
I can boot into recovery, download, otherwise it loops at cm logo. I can adb into my phone, and adb recognizes my device.
I just am not able to pull files. I get 0 files pulled 0 files skipped. Not able to flash the stock touchwiz with odin. I tried factory reset. doesn't work.

Sounding more and more like hardware. Did you try the file manager in recovery? You can try to copy files from internal to external sdcard.

SM-T211 wifi + bluetooth not working after root and bloatware removal

Hi all, new guy to the forums. After rooting my T211 (4.1.2) via Odin and with TWRP and SuperSU, I started to remove some of the bloatware that Samsung sticks on the tabs. everything was working great until I rebooted one day and then the wifi and bluetooth stopped working. I've flashed the 4.4.2 in preperation to flash a custom rom, but it seems no matter what I do, the wifi and bluetooth issue remain. Can anyone help me with a zip to reinstall the wifi and bluetooth? or an instruction on how to do it? I have the 4.1.2 rom as well as the kitkat rom from italy and a few custom roms. If I knew how to make a flashable zip and which apks and such to use I would be happy to do it myself. Any help would be greatly appreciated. Thanks in Advance, James.

Bump
Bump

Tried just re flashing stock nonrooted bloated os back on?
---------- Post added at 03:41 AM ---------- Previous post was at 03:41 AM ----------
With odin of course and use the pit file for a full reformat wipe

Flashing stock rom
Trying it now. I'm a bit of a idiot, when I was trying to flash the stock rom, I forgot to unzip and wondered why I was getting an error...haha. I wanted to try a dirty flash just in case it worked but no kewpie doll. Trying it with the pit file now. fingers crossed.

Ugh...no luck. here's the read out from Odin. Not sure whats going wrong yet. Maybe not the right pit file.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T211XXAML1_T211OXXAML2_T211XXAML2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Yea double check the pit file is for your model tablet

LT02.pit, this is the one that keeps getting reccomended in all the posts I've read. Says its for the T210 but it is supposed to be the same?

This is very frustrating thought I had it fixed. Wifi button turned on...bluetooth button turned on...just kept scanning. then both shut off and wont stay on

So after reflash they still do it?

yeah, they still do it. puzzling that it turns on but only scans and has no connection.

Using a file manager with root access, delete the following 2 directories:
/data/misc/bluedroid
/data/misc/wifi
Then, reboot.
Can't promise it will work, but it may.

Cool, gonna give it a try in a bit.

Any luck?

well, yes and no... after loading up root browser, I navigated to /data/misc. I don't have a bluedroid directory. I have a bluetooth and a bluetoothd and I have a wifi and a wireless directory. I deleted the first three and rebooted. I then was able to turn on the wifi and it recognized my router and connected...for about 10 seconds then shut off again and wouldn't turn on again. So, I think we're on the right track but not quite there yet. The fact that it did work even if temporarily was encouraging.

If it were me, I would go to sammobile.com and download the full firmware package for your region and flash it with Odin. That will ensure that you have a matching set of firmware (boot, radio, system, etc.) It will not wipe your data. If it works correctly after that, then you can reinstall your custom recovery and whatever rom you want.
Sent from my SM-G920V using Tapatalk

well, that didn't work either. Still has the same problem. I went into twrp and wiped everything except the external sd card. then with Odin, flashed 4.1.2 rom for UK and wifi will not turn on. Scratching my head now

Any other ideas?

Try using Heimdall with a full firmware package. You'll have to extract the firmware package (change the filename ending with ".tar.md5" to ".tar" and use 7-zip to extract it.
Then open up Heimdall, go to "Utilities -> Download PIT -> Destination File" and pick a location and name for the pit file.
Following this step, go to "Flash -> Options -> PIT" and browse to the pit file.
You will then have to go through the process of adding each partition that you want to flash, browsing to the location of the firmware package, and then flashing it.
I've done this several times, although I have not tried with "Repartition".
You will probably want to flash "SYSTEM", "MODEM", "KERNEL", and "RECOVERY" at a minimum. That said, it would be a *good* idea to use all the files inside the firmware package.
I'd upload packages I've made for my own convenience, but I'm unclear about their legal situation. I think I can get away with PMing links around though. Maybe.
EDIT1: Please post the output from the "Status" box if it fails.

Apologies for not responding sooner. Been busy with work, will try this soon and post results. Thanks

Can't get Heimdall to work. All I get is its not a valid win32 application. I refuse to give up on this, I know it's a software issue so there has to be a way to fix it. ...pulling my hair out though.

Custom Binary Blocked by FRP Lock - How I Fixed It Without Data Loss

YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.

"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.

koop1955 said:
"1. Download QB1 from koop1955's thread"
Yeah, that koop1955 character is one heck of a guy...or so I hear.
Glad this worked out for you.
Click to expand...
Click to collapse
He's crazy if you ask me
Sent from my SM-G920P using Tapatalk

I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it

fentezi said:
I have the same problem with my samsung galaxy sm-j120f and I can't seem to fix it
Click to expand...
Click to collapse
First off, you should probably post in the correct forum.
Secondly, did you try flashing the firmware for your phone: https://www.sammobile.com/firmwares/galaxy-j1/SM-J120F/

I fixed it
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it:laugh:

My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.

THANK YOU
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!

killroot said:
I just wanted to say thanks. This post helped me out a lot. I spend about 4 hours trying to fix this issue then found your post and had it done in a matter of minuets. I used to do this a lot back in days and I'm getting back into this. I got a lot of reading to do. Thanks for the post again!
Click to expand...
Click to collapse
Hey! Glad it helped. I was really active back in the HTC Hero days and around 2013 I slowed down. I like to keep my phones rooted but i getting more and more worried about manufacturer warranty being denied over being rooted... Fortunately I was able to iron this whole thing out with some meticulous research and some help from awesome people here, and it's still satisfying knowing I've helped at least one person who appreciated it enough to say thanks!
Sent from my SM-N920P using Tapatalk

finalc said:
My SAMSUNG G928P was flashed a 3rd firmware. l have a same issue which cause the device can't boot the system. And now still the same way appears red on the left conner 'custom binary blocked by frp lock'. I tried officiall firmware as you did, it can flashed successfully, just stuck in the SAMSUNG logo. HELP ME PLEASE, Dont want to lose the data.
Click to expand...
Click to collapse
Sorry, not sure what the g928p is and unfortunately I can't help with your issue. I just wrote what I did to fix this issue and if you're still having problems I recommend doing some very in depth research to make sure you didn't miss some tiny but crucial step.
Sent from my SM-N920P using Tapatalk

fentezi said:
All i had to do is change the firmware extension to .tar instead of .tar.md5 and flash it[emoji23]
Click to expand...
Click to collapse
That's what the instructions said to do [emoji6]
Glad it worked.
Sent from my SM-N920P using Tapatalk

Same issue on my Samsung A%
The file is not there anymore bro. Where do i get the file for my device please(Samsung A5) ? i found a way to solve this using kies 3 and wiping the phone. But u did it without data loss? amazing ! glad if you can help. thanks!
jerry43812 said:
YMMV.
Proceed to read at your own risk. This is intended for informational purposes only. I am not responsible for anything here.
So my wife's Sprint S6 displayed the error of "Custom binary blocked by FRP Lock". This was caused by Developer Options being turned off, then the device was rebooted.
In order to fix it, I tried so many things, including making an attempt to install 6 different versions of the ROM for this phone. I tried 4 different USB cords, tried all of the USB ports on my computer, and even went and grabbed the newest Odin, 3.12.3. None of the flashes worked, because they all failed, as shown below:
Code:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I did loads of research and found out that you (obviously) can't install a version lower than the currently installed version, and I couldn't remember what the current version was on her phone. However, I found many success stories telling how the currently installed version was successfully Odin flashed onto a device exhibiting the same issue as mine, but it never worked for me.
I spent a few more hours this morning researching this issue because I did not want to lose the data that was on my wife's phone, because I care about keeping her happy Amazingly, I tried something I read on a whim, expecting it to not work.
Using Odin 3.12.3, I downloaded QB1 from koop1955's thread. I verified the MD5 before doing anything else with the file. Then, I unzipped that download to produce a file ending in .tar.md5. I then deleted the extension .md5 from that filename, and put it into the AP slot in Odin. Odin didn't give any output (because it didn't do the md5 check that it would normally do). I then clicked Start. The flash worked!! The phone successfully flashed, and no data was lost at all. I am so damn happy!
tl;dr
0. Put phone into download mode. From an off state, press and hold Volume Down, Home, and Power til you get the blue screen, then press Volume Up to enter download mode. Plug it into your computer using a good USB cable.
1. Download QB1 from koop1955's thread
2. Unzip that download once.
3. Put the unzipped file into the folder in which Odin exists.
4. Delete .md5 from the filename. It should end in .tar now.
* If you don't see .md5 on the end of the filename:
* If you do not see file extensions, on W10, go to Control Panel\Appearance and Personalization. click File Explorer Options. Click the View tab. Place a check mark by the line labeled "hide extensions for known filetypes". Boom.
5. Click the AP button in Odin, then select that file you just renamed.
6. Click start in Odin. Let it flash. It should work.
Click to expand...
Click to collapse

i just had the same problem on my mothers phone and your method worked perfectly thank you so much i didnt want to do a stock flash and have her loose everything so thanks for your knowledgeable and easy to follow post

Hello @jerry43812 and @koop1955 that file has been deleted from android file host, would any of you please care to upload it again? Thanks very much. I have a Samsung Galaxy Note 5 btw, I think it works right?

I dont even remember making this thread, I definitely dont have the file you're looking for. Maybe koop can help.Sorry!

@koop1955 I don't have knowledge about any of the android OS. But I have an issue and it still is an issue from 2016 to 2022. I have an android phone launched in 2016. I rooted it using SuperSU binary. By turning ON all the necessary features required for making custom recovery (TWRP) installed and installing SuperSU binary as well.
Therefore my developer options were turned ON and OEM unlocking was ON aswell. My phone name was Samsung J2 2016 (SM-J210F). I by mistake disabled OEM unlocking switch. And restarted the phone and it never
rebooted after that.
I need the data it is very precious to me. I don't need root privileges back or anything like that.
I just need the data and state of operating system the way it was before restarting.
Please help me @koop1955.
I will be very thankful to you.

I have no idea. Good luck.