Related
Can anyone tell me if it's possible to flash/change/update just the baseband modem in my AT&T Samsung Galaxy S3 SGH-I747 without rooting the phone? After installing the latest update via the Samsung KIES software my phone reception has dropped a good bit. I no longer have service where I used to. My phone calls are also very choppy in the fringe reception areas, where before they were significantly better. I live in an area where 4G/3G coverage is fairly spotty, so EDGE is my primary network.
I wish I could remember which baseband version it had before the update so I could roll back to it, but I don't, so it may take a few tries before I can find the correct baseband version. Before the update I know I had ICS v4.0.4......not sure on Baseband version. Now I have Jelly Bean v4.1.1 (which I would like to keep) with Baseband I747UCDLK3.
I've tried using Odin v3.07 and the "AT&T Models Only! (I747U)" files via the link below and inserting the correct file path into the "Phone" section without any luck. Odin detects my phone, starts the process, but fails. http://forum.xda-developers.com/showthread.php?t=1831898
I've read to only use the "PDA" section in Odin to flash, but the files via the link below dont seem to have the proper file to use with the "PDA" seciton in Odin......am I missing something critical here maybe?
I then came across the following link where other people have used Odin to flash the baseband modem and seem to have been successful. http://forum.xda-developers.com/showthread.php?t=927568
Thanks for any help because I've spent hours searching the forum and Internet trying to find an answer!
I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.
I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!
SideWinder4x4 said:
I've tried downloading three different stock ROM files and when I open or extract the files using 7zip, I'm unable to find any file or folder named modem or modem.bin. What am I missing or doing wrong here?
One of the extracted files contains files named, aboot.mbn, boot.img, recovery.img, HON-HLOS.bin, system.img.ext4, and some other misc files.
Another of the extracted files contains three folders, data, META-INF, system, and a file named boot.img. Within the system folder I see 19 other folders....app, bin, cameradata, csc, etc.........folders, but nothing named modem.
Thanks!
Click to expand...
Click to collapse
i believe HON-HLOS.bin is your modem
SideWinder4x4 said:
and when I open or extract the files using 7zip,
Click to expand...
Click to collapse
Do not actually extract the files or else you will ruin the MD5 checksum and the flashing process will fail. Simply replace the modem file with the one you want to use by taking a "peek" in the actual TAR file.
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
I've tried this method using Ubuntu Terminal to create a new modem.tar.md5 file, but everytime I try to flash with Odin, it fails. What am I doing wrong. Thanks for any further advice, this is driving me crazy!
My steps are as follows:
1.) I'm unzipping the correct modem files (modem_CWM_I747_UCLH9.zip) from this link - http://forum.xda-developers.com/showthread.php?t=1831898
2.) I'm taking the "modem.bin" file and copying it to Ubuntu desktop folder
3.) I'm opening Terminal
4.) I change to the Desktop directory
5.) First command...without the quotes is "tar -H ustar -c modem.bin > modem.tar"
6.) Second command...without the quotes is "md5sum -t modem.tar >> modem.tar"
7.) Third command...without the quotes is "mv modem.tar modem.tar.md5"
8.) I copy that "modem.tar.md5" file back to my Windows 7 based computer
9.) I rename "modem.tar.md5" to "modem.tar"
10.) I press and hold the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted press the "Volume Up" key
11.) On the screen I see the following: ODIN MODE, PRODUCT NAME: SGH-I747, CUSTOM BINARY DOWNLOAD: No, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, QUALCOMM SECUREBOOT: ENABLE
12.) I then open Odin v3.07 using defaults
13.) Odin recognizes my phone on COM8 with a blue teal colored box
14.) I press the "Phone" button and select the "modem.tar" file
15.) I press the "Start" button and it shows "modem.bin" in the first box in white, but about 5 seconds later it turns red and says FAIL!
The Odin message box indicates the following:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> modem.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Well, try naming it NON-HLOS.bin instead of modem.bin. Also, don't rename it after you make the tar.md5 file.
Solution Found
I finally got this figured out. Thanks for all of the help and ideas along the way!
The key tip was found in this thread - http://forum.xda-developers.com/showthread.php?t=1658809
Just to simplify things for others in the future, the steps I performed were as follows:
1.) Installed Cygwin from http://www.cygwin.com/
2.) Started Cygwin Terminal
3.) Put the SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 firmware file into the following folder I created "c:\baseband"
4.) In Cygwin, typed the following command without the quotes "cd /cygdrive/c/baseband"
5.) In Cygwin, typed the following command without the quotes "tar -xvf SGH-I747_ATT_I747UCDLK3_I747ATTDLK3_Original.tar.md5 NON-HLOS.bin"
6.) In Cygwin, typed the following command without the quotes "tar -H ustar -c NON-HLOS.bin > baseband.tar"
7.) Pressed and held the "Home" + "Power" + "Volume Down" keys on my phone, then when prompted pressed the "Volume Up" key to enter "Download Mode"
8.) I then opened Odin v3.07 using defaults
9.) Connected my phone to my computer using the proper USB cable
10.) Odin recognizes my phone on COM8
11.) I pressed the "Phone" button and selected the "baseband.tar" file I created in step #6
12.) I pressed the "Start" button and about 30 seconds later it finishes and the box turns green and the phone rebooted.
Thanks Sidewinder. Its very informative.. I am facing a strange issue on my Galaxy R ever since I upgraded to ICS and JB (stock/ custom ROMs).
Very often I get my calls disconnected while speaking. This was not the case with Ginger bread..
Today followed your procedure to extract the modem.bin from stock GB rom and flashed to my JB custom ROM (Carbon).. Looks good so far..tried
with test calls - seems to be OK.. Will observe for some more time.
You're Welcome asbalaji. I'm glad what I posted helped you out. My phone reception issues improved a lot after downgrading to an older modem.
Anonymously_Unknown said:
I think using 7zip is your solution. Open the 4.1.1 TAR file with 7zip and replace the new modem with the older ICS one.
You would then flash this with ODIN. I haven't tested this myself, but I was advised that this works.
Click to expand...
Click to collapse
I am in desperate need of a baseband to flash via ODIN for a boostmobile galaxy S3
---------- Post added at 07:00 AM ---------- Previous post was at 06:24 AM ----------
mrhaley30705 said:
Non-hlos.bin is the modem. But, chances are just replacing the modem in the tar. Md5 will cause a check sum failure. To do what you want, you need to make a new tar.md5 with just the modem in it. Then load that into the phone slot in Odin.
Click to expand...
Click to collapse
Basebadn boostmobile s3
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Zen Arcade said:
1 - Install the USB drivers for the i317m (from samsung web site)
2 - Download the latest Heimdall package from here - http://www.glassechidna.com.au/products/heimdall/
3 - Extract Heimdall to a folder on your PC and open a command window there
4 - Connect the phone in download mode to your PC. From windows go to the drivers folder and run zadig. Consult the readme or search XDA on instructions on how to configure the heimdall driver. The device you are looking for might be shown as "Gadget Serial" for the i317.
5 - Now go back the the command window you opened and enter the following commands:
5a - heimdall detect [this will tell you whether the interface is working]
5b - heimdall download-pit --output i317m.pit --no-reboot
6 - check your heimdall folder, you should have a file called i317m.pit if everything worked
7 - If this allows you to successfully repartition your phone, upload the resulting pit here for others to use
Click to expand...
Click to collapse
hellocng said:
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Click to expand...
Click to collapse
Did you ever find a good download? I am trying to pull a pit file from a newly upgraded i317m Stock 4.3 but it is failing during the pit download... I have another i317m that is in the same boat as yours so any help/info you have would be helpful
Cheers
full flash?
Any progress in acquiring a full flash for this phone?
hellocng said:
In my attempt to play around with the new JSS15J.I317UCUBMJ4 leak to get Wifi working on the I317M, I dont know which part corrupted my PIT so now I cannot access my internal media. I'm not sure if it is the bootloader, PIT or combination of the files I was using but I need a full I317M firmware to unbrick the device (preferably 4.1.2 / RWC).
This was my first time using Heimdall and despite reading through the ReadMe a few times, there were countless problems along the way including driver issues and file formats.
I hope to get a full firmware for the I317M as all the ones on Sammobile do not contain param, sboot, tz, and pit. The most important file for me at the moment is the pit file as I think that would restore access to the internal media, which would make flashing other things much easier for me. I havent tried sideload in TWRP yet but I doubt any solutions to my immediate problem could be solved in recovery.
Anyone who has a I317M, please download a copy of your pit file with the instructions as provided by Zen Arcade below:
Click to expand...
Click to collapse
emutter said:
Any progress in acquiring a full flash for this phone?
Click to expand...
Click to collapse
The pit file is here - http://forum.xda-developers.com/showthread.php?t=2609871
The 4.1.2 and 4.3 stock firmwares are available from sammobile.com and do contain bootloader and tz (and most everything else except param and tombstones).
I've not seen a param file for the i317m... if someone wants to extract them from stock rooted 4.1.2 and 4.3 and share them I will resize and post them.
To do so run these commands from terminal emulator on phone:
Code:
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/param.bin
PM me and let me know what firmware you were running and what specific phone - i.e. i317-rogers or bell or ...
Hi all,
just having some problems flashing my tab 10.1 3 p5220.
Kies is refusing to do it as I suspect it is because the rom in it is
currently a german one.
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
I seem to remember being able to do this on the htc and assume
we can do the same with the samsung. This way I hope I can I
reflash it via odin.
Many thanks in advance,
Andrew
Just download a firmware from sammobile and flash through odin
BennyCat said:
Now, how do I intercept the rom file after kies has downloaded it but
before it attempts to install it and fails?
Click to expand...
Click to collapse
Not sure if you've managed it now?
Anyway here is how you do it, also may be useful for others too, I've done this in the past, although I was doing an emergency recovery instead of an upgrade, this works either way.
I take absolutely no credit for this:
Here is a guide to save the firmware during your kies update,so u can save that firmware for future use .i just copy paste this from some where else
1. On your pc, windows explorer, check the option "Show hidden files, folders, and drivers".
2. Now connect your phone to pc via kies to begin the firmware upgrade.
3. Kies will begin to download the firmware files...
a. The files will be saved under a tmp file called "tmp****.tmp"
(NB: **** can be any letters or numbers, e.g. In my two times of upgrade via kies,
first timethe tmp files was "tmpA4CE.tmp", and on the second it was "tmpD900.tmp"
b. In Windows 7, this tmp file is located at, C:\Users\*\AppData\Local\Temp
(NB: * is the pc user session name, e.g. C:\Users\Spacks\AppData\Local\Temp)
4. When download is complete, kies decompresses this tmp file into a folder called
"tmp****.tmp.zipfolder" and begins the firmware upgrading process.
a. The folder has same name as the tmp file but now with an extention of .zipfolder.
(So scroll through the folders in the same directory to locate it).
b. When kies begins the upgrade process starting from 1% until it reaches 100%,
quickly copy the "tmp****.tmp.zipfolder" to your desktop.
You have about 2 to 3 minutes to do this. Kies will delete the folder once upgrade is 100% (completed).
5. The "tmp****.tmp.zipfolder" contains all the firmware files kies has used to upgrade your phone.
Now you have a backup of official firmware from kies. This is also useful in case kies fails to complete the upgrade process.
Click to expand...
Click to collapse
:good: Credit to & quoted guide by blackperl @ androidforums.com :good:
WHAT IS THE USE OF .pit FILE?
.pit FILE IS USED TO DIRECT THE PARTITION OF THE WHOLE ANDROID SYSTEM..JUST LIKE WE ARE DOING GRUB IN PC...HERE ALSO WE NEED TO PARTITION THE SYSTEM FOR FLASHING THE FIRMWARE PROPERLY.. AND HERE THE .PIT IS USED
1. Get your phone into download mode..
2. connect to computer. Make sure that usb drivers installed and you have the firmware.tar file.
3. Now open odin 3.10
4. click on PIT and select ZEROLTE_USA_TMO.pit
5. Make sure that partition is tick
6. click on PDA and select firmware.tar file
7. Now start button and wait...You are done
link:
https://drive.google.com/folderview...tmV3YxMTB4WGpSZU5ReEI1WjZtUXM&usp=sharing_eid
Mhhh could be useful great job Op
The link doesn't work for me, could you reupload it? Also does this contain data about your /data partition? If so this might be specific to your model (16/32/64 GB)
update the file
update the file
SHATTAH said:
update the file
Click to expand...
Click to collapse
Just requested permission for the file.
SHATTAH said:
WHAT IS THE USE OF .pit FILE?
.pit FILE IS USED TO DIRECT THE PARTITION OF THE WHOLE ANDROID SYSTEM..JUST LIKE WE ARE DOING GRUB IN PC...HERE ALSO WE NEED TO PARTITION THE SYSTEM FOR FLASHING THE FIRMWARE PROPERLY.. AND HERE THE .PIT IS USED
1. Get your phone into download mode..
2. connect to computer. Make sure that usb drivers installed and you have the firmware.tar file.
3. Now open odin 3.10
4. click on PIT and select ZEROLTE_USA_TMO.pit
5. Make sure that partition is tick
6. click on PDA and select firmware.tar file
7. Now start button and wait...You are done
link:
https://drive.google.com/folderview...tmV3YxMTB4WGpSZU5ReEI1WjZtUXM&usp=sharing_eid
Click to expand...
Click to collapse
Can you please explain how you got the pit file? from what I understand you cannot simply dump the pit anymore unless I missed something.
requested access to this as well-- can you post somewhere other than Google Drive as people cant get to this file?!
can you please grant my request to download the file? I have a soft bricked phone and I really need the Pit file. thanks so much
looking a pit file for latest firmware 5.1.1 G925TUVU2COF6 does anyone have?
onlineunlocks said:
looking a pit file for latest firmware 5.1.1 G925TUVU2COF6 does anyone have?
Click to expand...
Click to collapse
According to: http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
Requirement: To be able to use any of the methods described below [to extract the PIT file], you must have root privilege on your Galaxy device. Both the methods have been tested on the Samsung Galaxy S5.
Click to expand...
Click to collapse
This means that, unless someone gets it directly from Samsung somehow (leak, release, or otherwise), you'll need to wait for root on the 5.1.1 stock ROM.
I don't know a whole lot about the PIT file, and why someone would ever need it (apart from screwing around so much that you overwrite your partition information on the device... which would be hard for the average user to accidentally do).
Have you tried Samsung Smart-Switch? I don't know if it's capable, but it might download the PIT info from the internet before restoring stock firmware on a 100% borked device.
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
onlineunlocks said:
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
Click to expand...
Click to collapse
Let us know if this worked. I need to restore back to 5.0.2 also from 5.1.1. Thanks
will not work to restore to 5.0.2 from what I know and might also damage it,so do not recommend to try that
onlineunlocks said:
Thank you for the reply; by adb I know does not work without root as I looked over those methods. But there is also Heimdall that should be able to extract the pit while in download mode and has the option to save it,but seems not supporting this device. Also odin performs this tasks " Get PIT for mapping.." ,but does it automatically and there is no option to save from a working device with same details to use on other. I need it for a g925t that is stuck on samsung logo after odin restore and showing in download mode SW rev. check fail. device:2 binari 1 , and I think by flashing with a pit might fix it
Click to expand...
Click to collapse
I'm in the same situation.
Have you found a solution?
Aou said:
According to: http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
This means that, unless someone gets it directly from Samsung somehow (leak, release, or otherwise), you'll need to wait for root on the 5.1.1 stock ROM.
I don't know a whole lot about the PIT file, and why someone would ever need it (apart from screwing around so much that you overwrite your partition information on the device... which would be hard for the average user to accidentally do).
Have you tried Samsung Smart-Switch? I don't know if it's capable, but it might download the PIT info from the internet before restoring stock firmware on a 100% borked device.
Click to expand...
Click to collapse
is this gonna fix my phone if efs is not mounted??? me and my buddy have no idea how he broke his phone.
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.