Develop Bugs

[Q] Failed attempted update to 4.0.4 - stuck (FIXED)

See my reply to this thread on page 2 for the resolution.
---
So I unlocked and rooted my VZW LTE galaxy nexus a couple months ago, no problems with the process.
I looked into updating from 4.0.2 to 4.0.4 and found this walkthrough for YAKJU IMM76D:
androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2/
Page 1 goes through checking USB debugging, what to back up first, etc. USB debugging was enabled already.
Page 2 (link above) provides the instructions on what to download, how to run it, etc. I followed the steps there. It went through:
---
<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> bootloader.img
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> userdata.img
<ID:0/008> radio.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---
As it stands, if I put the battery in the phone, the screen will turn on and display an icon of a mobile device, two dots, a warning ! triangle, two dots, and a PC monitor.
Pressing the power button "reboots" back to this screen - it just turns off, then turns back on.
Vol up and power does the same thing - does not go into recovery
vol down and power does the same thing
vol up, vol down, and power does the same thing
pulling/replacing the battery does the same thing
I am able to re-run Odin3 v1.85 with the PDA download option checked, specifying that same .tar. It will still go through 95% of the process and end the same way, with "FAIL!" shown in Odin and an almost-complete blue progress bar on the phone below that other error image described above.
So, I *think* this should be salvageable, but I don't know how or what/where to find the file(s) that I should be using to fix this.
THANK YOU for reading and any advice you have, and let me know if anything needs clarification. Screenshot of Odin results attached (seems to not be working... imgbucket link alternative: imgbucket.info/photo/ggnkdlyyu/Odin3_v1_failed.jpg)

Youre phone has nothing to boot from. That's what that means... (Check my signature) use that, reflash stock 4.0.2, try again... And do a backup, first!!
If you're very unlucky, you buggered up the whole memory unit. That means, loss of EVERYTHING...
Oh, and: Stop being a whimp Be a man. Stand above it. Think: "I can do it!!"...
It may sound harsh, at first. But, if you would know, how many times, that has happend, with a Samsung Phone, to me... And if I would have given up, I wouldn't have gotten me a developers phone
So, be strong, (Use my root helper) And tell that phone, who's boss!

Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.

trevordyck said:
Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.
Click to expand...
Click to collapse
I like your way, of thinking
Like a man!

The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app

El Daddy said:
The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
OH, well that explains everything! Thanks for that clarification... now back to trying to un-bork my handiwork.

Time to try to get into Odin mode.
Sent from my Galaxy Nexus

Time to "stay" in Odin mode... playing with Odin (ignorantly, a bit) is what got me here...
axne1 said:
Time to try to get into Odin mode.
Click to expand...
Click to collapse

Well I haven't made any progress on the phone, but I've done a few things to try familyguy's stuff. I think I have the latest version of that, and the 4.0.2 downloaded via the program, but I get this error message every time I try to flash a stock LTE ROM with it. Do I need to do this with Odin, this program, or something else?

I think you should read this
http://forum.xda-developers.com/showthread.php?t=1600203
Sent from my Galaxy Nexus

Aha! Thank you much for that. Following a few links I think I can fix it just by specifying a suitable firmware, because Odin does actually run the "PDA" flash until the end (progress bar still shows up on my "soft bricked" display and Odin indicates it's copying stuff). So, when I land later tonight I'll download and give this a try:
dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
I guess I'm not really asking any useful question here so much as tracking my attempts... hope I get this sorted before work in the AM!

Awesome!!!
Keep us updated!
Sent from my Galaxy Nexus

No luck yet. I can still run the GSM "Phone" flash in Odin until 95% complete when it fails, but all of my attempts at using Google's archived 4.0.2 for CDMA are stopping at about 15%, and I have to R&R battery to restart it. This is as far as I can get:
<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> boot.img
<ID:0/008> NAND Write Start!! (*sits here indefinitely)
Any pointers on what is required for the various fields to flash a stock setup to this thing using Odin?

It sounds like it's looking for some type of backup like a nandroid
Sent from my Galaxy Nexus

There is a tool on amazon.com that should help it's called a jig or something like that.
Sent from my Galaxy Nexus

AHHHH! FIXED!
Things I learned:
- Odin is a Samsung product and needs special samsung-y .tar files to flash the phone. Regular ROM stuff doesn't work. (pardon the ignorance in terminology)
- "mysid" specifies a VzW compatible build for the GNEX
- If you accidentally flash a GSM tar to your VzW phone using Odin, Odin is the only thing that will get you out of your sitch (of the things I could figure out how to try. I didn't try any command line stuff. That's last ditch for me - takes more time for me to learn, and a busy Monday morning at work wasn't helping me)
- I found the resolution here: http://forum.xda-developers.com/showthread.php?t=1426207&page=5 - a factory Odin pair of files for CDMA/VzW, one for PHONE and one for PDA. Saved. My. Bacon.
- The $10 wifi on Alaska Airlines is slow as junk.
- Starting this whilst abroad is a bad idea. (HAHA!)
Regarding the walkthrough I followed that got me in this mess - nowhere that I saw did the author (or readers) specify that the flash I was about to try was GSM only. Maybe I missed that detail, but if not it would make sense to me that someone reading a tutorial on how to flash their phone probably would have NO IDEA that yukjiwhatever is GSM and mysid was for CDMA. That would have been good to read, like, in the first paragraph of the article. Anyways...
I have a working phone and somewhere unicorns are grazing in a field. I hope this helps some other equally poor sap recover his phone.

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 )

[Q] How to flash baseband modem with Odin without rooting

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

[Q] SM-P607T (T-Mobile) -- Can it make calls?

That's my big question. I use my phone so rarely for calls, and my phone plan has a way better data plan than anything I can get with this tablet. If I can use my SIM from my phone on the tablet and be able to make/receive calls, I think I would be set in a way I've only dreamt of.
So, does anyone know if this is possible? There doesn't appear to be an app on the stock device for calling. The site http://pdadb.net/index.php?m=specs&id=6176&view=1&c=samsung_sm-p607t_galaxy_note_10.1_2014_lte-a shows this:
Phone Controller: Qualcomm MSM8974A
That just refers to the Snapdragon!
Any thoughts on this?

Am not sure exactly the spec of SM-P607T , but look like its has sim to use data-net only , but not making callsas
p600 is wifi only
p601 is wifi and 3g can be used as phone
p605 is wifi and 4g can be used as phone
p607 is wifi and 4g can't be used as phone

dsp4774 said:
That's my big question. I use my phone so rarely for calls, and my phone plan has a way better data plan than anything I can get with this tablet. If I can use my SIM from my phone on the tablet and be able to make/receive calls, I think I would be set in a way I've only dreamt of.
So, does anyone know if this is possible? There doesn't appear to be an app on the stock device for calling. The site http://pdadb.net/index.php?m=specs&id=6176&view=1&c=samsung_sm-p607t_galaxy_note_10.1_2014_lte-a shows this:
Phone Controller: Qualcomm MSM8974A
That just refers to the Snapdragon!
Any thoughts on this?
Click to expand...
Click to collapse
Only way for you to find out would be to flash a 605 rom and see with a voice sim card. You can always odin back to stock if you want to. I have yet to flash a 605 rom because I finally got the stock rom where I want it.

Prod1702 said:
Only way for you to find out would be to flash a 605 rom and see with a voice sim card. You can always odin back to stock if you want to. I have yet to flash a 605 rom because I finally got the stock rom where I want it.
Click to expand...
Click to collapse
This seems like it could work. I'll do a backup first and try it out--there would be 0% surprise here if tmo just didn't want people replacing phones with tablets.
As I go through TB, I see a com.sec.phone.fake 4.4.2-P607TUVUANE2. I tried to google up the first part of that only to be met with a lot of information about how to enjoy becoming a phone sex operator. I'm wondering if someone with a P605 can look through with TB (or whatever) to see what might be in place when it comes to the phone.

I've been on international 3G G-Tabs with phone features for three years. In that time, no U.S. carrier's Samsung tablet has ever supported phone features. Also in that time, I've never seen anyone successfully add phone features to a U.S. tablet through modding or use an international ROM on a U.S. tablet that didn't bork the radio. So I'd make sure you T-Mobile folks have tested back-ups before you flash a P-605 ROM. The P-605M does support U.S. LTE bands and I'll probably get one the next time I'm in Latin America to use on AT&T. If you're going to try and flash a ROM on your P-607 you're probably better off using the P-605M's ( http://samsung-updates.com/device/?id=SM-P605M ) since some of the bands your h/w supports are there. The SM-P605 radio you're about to flash doesn't support the 700MHz LTE band.
P-605
P-605M

P607T should be able to make calls... no?
I believe the hardware is identical to the P605M which can make phone calls.
I think the phone calling feature is just "missing" at the software level (but that's just my noob hunch.)
Anyway, my technical abilities are not at a level where I can create custom roms so I need some help:
I'd like to flash the COO 4.4.2 P605M firmware to my P607T.
naturally, I'd also need a way firmware to get back to the stock 4.4.2 P607T if things don't work.
I'm willing to try it on my device if someone can create the TAR.MD5 files needed
Thoughts?
Or... if someone wouldn't mind sending me a step-by-step on how to create the above? I have both stock firmwares now as well as ODIN and everything ready to go.
*I've tried researching TAR BALLS and creating files... but there no simple step by step instruction anywhere.
Cheers

TG2008 said:
I believe the hardware is identical to the P605M which can make phone calls.
I think the phone calling feature is just "missing" at the software level (but that's just my noob hunch.)
Anyway, my technical abilities are not at a level where I can create custom roms so I need some help:
I'd like to flash the COO 4.4.2 P605M firmware to my P607T.
naturally, I'd also need a way firmware to get back to the stock 4.4.2 P607T if things don't work.
I'm willing to try it on my device if someone can create the TAR.MD5 files needed
Thoughts?
Or... if someone wouldn't mind sending me a step-by-step on how to create the above? I have both stock firmwares now as well as ODIN and everything ready to go.
*I've tried researching TAR BALLS and creating files... but there no simple step by step instruction anywhere.
Cheers
Click to expand...
Click to collapse
It's very easy. Use 'Total Commander' for windows by Christian Ghisler (Google it).....Ghisler. com. Download the software. On the website check FAQ+ support then on ' tutorials' for beginners check animated (step by step) tutorials for unpacking and packing files.
Sent from my SM-N9005 using xda app-developers app

shayind4 said:
It's very easy. Use 'Total Commander' for windows by Christian Ghisler (Google it).....Ghisler. com. Download the software. On the website check FAQ+ support then on ' tutorials' for beginners check animated (step by step) tutorials for unpacking and packing files.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Excellent. Thank you.
I successfully tested using this by doing the following:
1. Renamed extension on stock E2 P607T firmware from 'TAR.MD5' to '.TAR' (so it can be opened by Total Commander)
2. Viewed, then deleted the 'aboot.mbn' file from the firmware.
3. Flashed the .TAR file (with missing .mbn) to my device.
4. Succeeded.
Now, when I get home today after work (very soon.) I plan on doing the same thing with the COO E2 P605M firmware... would you see a problem with this? Anything I should know before I go ahead and do it
Cheers~
Thanks again.

TG2008 said:
I plan on doing the same thing with the COO E2 P605M firmware. Would you see a problem with this? Anything I should know before I go ahead and do it?
Click to expand...
Click to collapse
My only question is why that particular FW (i.e., is that the latest or most compatible)? I may also do this as well, but I need to make sure I don't lose the US LTE bands (namely 2, 4 and 7).
ETA: I'd also strip out the "Modem.bin" file, too, at least at first.

kcrudup said:
My only question is why that particular FW (i.e., is that the latest or most compatible)? I may also do this as well, but I need to make sure I don't lose the US LTE bands (namely 2, 4 and 7).
ETA: I'd also strip out the "Modem.bin" file, too, at least at first.
Click to expand...
Click to collapse
P605MUBUCNE3_P605MUUBCNE3_P605MUBUCNE2_HOME.tar.md5
and
P607TUVUANE2_P607TTMBANE2_P607TUVUANE2_HOME.tar.md5
are the two files I am playing with.
The closest I got was I removed the SYSTEM.INI file from the 605 and put it inside the 607, replacing it... when I booted I got the 605 system and my device was seen as a P605M.
I was able to dial, but nothing happened. I could successfully send text messages however
Anytime I tried to flash the 605 to the 607 directly something would always fail. I remove the culprit file, then it would fail again on the next files... and so on.

OK, so I went ahead and flashed the "Nordic Countries" SM-P605 FW "P605XXUCNE2/P605XXUCNE2" 4.4.2 ROM . Here's a screenshot of my "About" screen.
I had to remove all the "*.bin" and "*.mbn" files (I suspect it won't overwrite the ones already on the P607T unless you check "Phone Bootloader Update", but I wanted to try first changing the "*.img" files first).
I'd done a full TiBu as well as a TWRP backup of everything first (I was prepared to have had to wipe completely) but it upgraded just fine and everything was OK.
Here's a thread that's got FAR faster downloads than SamMobile (that was a waste of EUR5 ) of the official full stock ROM if you want that as a reference (use the Google Drive link, I was getting 160MBit/sec downloads).
Here's a Google Drive link to my Odin-flashable .tar file that's got all the bootloader/modem files removed.
I don't know what this will do to your Knox (I'd rooted via flashing the TWRP recovery and therefore tripped my Knox 20mins after I'd gotten the tablet) but I suspect that since this is all Samsung-signed code you should be OK.
I see there's a "Phone" app now, but every time I tried to dial any number (even *611) it on either of my data-only SIMs (ATT/T-Mo) it immediately hung up. Normally even on data-only SIMs (like on my OG Note 10.1) you'll be able to complete a call and dial into an error recording, so I suspect that's 'cause we didn't update the "modem.bin" file, so the voice capability isn't in the phone modem anyway. If I feel adventurous, I'll try swapping that out but for now I'll see how this ROM performs first.
BUT- and this might be helpful- we have different options for Mobile Networks->Network mode: "LTE/WCDMA/GSM (auto connect)"/"WCDMA/GSM (auto connect)"/"WCDMA only"/"GSM only". There's another thread wondering if the T-Mo version gets access to 3G/2G networks and/or if T-Mo US has removed those, so it'll be interesting to see what effect this would have when on the road (I wonder if the network status icons change too).

Nice. I too have come to the conclusion that a modem.bin from the P605M is definitely required if we want to have any success... unfortunately I don't know how to make a compatible ZIP install file:
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
If someone can link one, or again point me to how to create one I will give it a shot

TG2008 said:
Nice. I too have come to the conclusion that a modem.bin from the P605M is definitely required if we want to have any success
Click to expand...
Click to collapse
Apparently so. I'm going to do some research here on XDA and see if it's possible to interchange modem files at will.
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
...
<ID:0/003> Receive Response from boot-loader
<ID:0/003>
Click to expand...
Click to collapse
Was this with "Phone Bootloader Update" checked?
If someone can link one, or again point me to how to create one I will give it a shot
Click to expand...
Click to collapse
I'm 99% sure there's a way to do it with "dd" in adb shell, so let me look into that.

kcrudup said:
Was this with "Phone Bootloader Update" checked?
Click to expand...
Click to collapse
I had extracted the modem.bin file from the 605.tar file, then attempted to flash it via ODIN 'Phone' option.
"Phone Bootloader Update" was not checked
The 'Phone Bootloader Update' cannot be checked unless the file being used has the .MD5 extension... when I use a .TAR only the option is greyed out (and cannot be "checked.")
-------
Trying now with the 607-.tar.md5 firmware and the 605-modem.bin. I've ticked-off the "Phone Bootloader Update" option.
The result:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P607TUVUANE2_P607TTMBANE2_P607TUVUANE2_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> modem.bin
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Receive Response from boot-loader
<OSM> All threads completed. (succeed 0 / failed 1)
SECURE CHECK FAIL : modem

I'm pretty sure that still has to be done in the "PDA" box (but don't quote me on that).

ADB goodness
Well, I spent the morning and part of the afternoon re-familiarizing myself ADB SHELL, SU, etc.
looking forward to any modem-changing methods that might pop up this weekend

Bear with me; I haven't had the chance to verify if I can flash (via Odin or "dd") different modems without causing any trouble.

... so apparently without some sort of bootloader hack, this isn't going to happen.
I've spent a couple of hours on this, and the Knox-enabled bootloader in 4.3+ ROMs (that the T-Mobile P607T apparently got from day-one; my manufacturing date is May 30th(? I believe)) is protecting the "modem.bin" and "NON-HLOS.bin" flash partitions (at a minimum) and no matter what method I try and use (Odin, which fails as above), neither "dd" nor "flash_image" (with a custom recovery .ZIP I'd made) can write the flash. Although I can read back the flash immediately after flashing and have the MD5 check out (due to backing store of the device from the Linux block cache, most likely), it never actually gets written to the device.
Until we get a workaround for unlocking the flash device (it's kind of like an HTC "S-ON" condition) we won't be able to flash any modems.

Thanks
Thanks for confirming.
I realize the device is new (released early June'14)... do you think this is something we could put a bounty on ?
I am regretting my purchase currently... I should have ebay'd the P605-International (sigh)
Hopefully in time.
Thanks again.

I know it is not the same thing as regular calling but groove ip lite does a pretty good job of voice over ip and its free and it even receives calls to.

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.