Develop Bugs

[Q] Did I brick my phone? v2.0

Just tried to root my phone following some instructions I found on youtube:
http://www.youtube.com/user/mypd1991#p/a/u/1/cFwy0LXOw2c
At first I got "file type invalid" for the .md5 files I downloaded in the info panel in youtube. I finally found one that works, and I keep getting
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.lfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried everything I can find from updating my phone drivers to the specific windows 64 bit version, to following the root and recovery/odin stock flashing instructions here http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SPH-D700.
I've downloaded various versions of Odin, as well as several different .md5 files and still it's failed.
I've tried all of this with the SD card in, and with it out.
When I try to boot my phone up, I keep getting what's been called the "soft brick" screen http://i556.photobucket.com/albums/...80 Shots/My Samsung Vibrant/vibrant_brick.jpg
Sometimes, and I don't know what I do different, it will acutally turn on like I held down the 3 buttons to reboot the phone, but when I select that option, or any other, it goes back to the soft brick screen.
Five hours later, I'm still surprised my phone is in once piece. It's a bit frustrating. Anyone have anything else I can try? Thanks in advance!

Some people have success when trying a different and better quality usb cable. The one that comes with the phone isn't that great.
Sent from my SPH-D700 using XDA App

Tried it on the comp at work, using a different cable. Worked like a charm. Thanks!

allheilkingmatt said:
Tried it on the comp at work, using a different cable. Worked like a charm. Thanks!
Click to expand...
Click to collapse
Great news. Glad you got it fixed.
Sent from my SPH-D700 using XDA App

[Guide] Root and CWM recovery new ICS.

To start, you will need
Recovery-cmw-hercules.tar (doesn't have to be the latest, you can update it later). This can be found in other recovery threads, as the process remains the same.
Odin3 v1.85 (or any other compatible version)
root.zip found Here
Steps:
1) Make sure Kies is exited, and you have the drivers installed for Odin. If not, check the other threads as this has been covered many times
2) Just select your CWM recovery for PDA once you are in DL mode (which is achieved by holding down VOL Up and VOL Down when the phone is off as you plug in the cable). Select vol up to confirm dl mode.
3) In Odin, leave the default boxes (Auto reboot and F. Reset time), and then select PDA and choose the .tar file we found earlier. Make sure odin sees your phone properly and start this!
4) once you have CWM recovery installed copy the root.zip to your sd card, and boot into CWM recovery. Do a Nand Backup and then install root.zip and enjoy!
5) Delete that crappy bloat!
For those having connection issues in Odin, try the following.
1) Exit Kies
2) Change to a different USB port
3) Reinstall your USB drivers.
I kept getting an error, and the above fixed that.

Thank you!

Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA

Thanks a lot for posting this for everyone. Hopefully this will quell the 50 billion requests that could be handled by using search or google.

TheTechNiq said:
Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA
Click to expand...
Click to collapse
Its should work the same, my official tmo 4.03 ics
was just rooted doing this

so it's the same process?

Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)

Teo032 said:
so it's the same process?
Click to expand...
Click to collapse
Yes but make sure you download the root.zip file OP posted a link to.
Once you're done with the odin part, having the recovery-cmw-hercules .tar all done.
You should see CWM rom manager in your app, you can click on it but cant really use it. because you don't have superuser permission, That why you need to copy the root.zip file to your sd card. Now get in to CW recovery by turning off the phone.
hold vol. up+down,and hit the power on button, scroll down and install the root zip.
then reboot. now you should have superuser permission and can now uninstall, or freeze all the junk with Titanium backup.

kwilsonjr said:
what do you mean 'leave the default boxes'?!? leave them checked? leave them unchecked? leave them alone? what? I'm assuming you mean leave the boxes alone (default).
Click to expand...
Click to collapse
Don't touch anything but the PDA button, select the .tar file, and click start.
For those worried about using the GB root process with the new ICS ROM, the Kies flashing does not put a new recovery on it. It's the same one that shipped with your phone. Therefor overwriting the the recovery with CWM 5.0.2.6 (via Odin) is the exact same. The root.zip flashed from VWM just installs su, busybox, and the superuser.apk into the OS, this has been done on many ICS roms already.
TL;DR: the process is identical, and confirmed working.

Rooted! T989 with Stock ICS update!
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!

ResidentJack said:
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!
Click to expand...
Click to collapse
Busybox is included in the root.zip in this post?

Worked like a charm thanks!

Damn... Stuck on "Goodbye"
Ok, so I rooted and it worked perfectly, only problem is I'm now getting stuck on "Goodbye" screen when shutting down, or when restarting. I have removed the battery for 2 minutes, wiped cache, wiped dalvik...
Still the same thing...
Anyone have any ideas?
Thanks

kwilsonjr said:
Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OK. Don't know what the heck is going on. Closed and re-opened odin 5 times and tried each time. It finally took on the 5th try. weird.
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/007> Added!!

What did you guys use to remove all the bloatware?

n/m found it.

Blackleopord187 said:
What did you guys use to remove all the bloatware?
Click to expand...
Click to collapse
I freeze it with titanium backup.

I can confirm the reboot hang issue.

ian577416 said:
I can confirm the reboot hang issue.
Click to expand...
Click to collapse
maybe its an isolated incident on some devices? (I used the OP's root method) I just tried restarting and turning off my phone and i get no hangs on the goodbye screen or anything.

No hang issues here. Root method works great.
Bloat removed,,,,,ALL OF IT!!!!!

[Q] Possible Soft Brick. I'm a noob. Sorry. ANY HEEELPPP PLZZZZ.

galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.

XXM3G4XX said:
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
Click to expand...
Click to collapse
Make sure you have usb debugging checked in developer options. I had thew same problem as you but once I selected usb debugging it worked..

Phone doesn't turn on
colint3 said:
Make sure you have usb debugging checked in developer options. I had thew same problem as you but once I selected usb debugging it worked..
Click to expand...
Click to collapse
Hi Colint3 thank you for the first person to reply. Much appreciated.
How can I select USB debugging if the phone doesn't come on for me to access the option.
Although if I remember correctly, I already had it on before this incident occurred.
Update 05/02/2014
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMK9_2138564_REV04_user_low_ship.tar.md5 is valid.
<OSM> AP_N7100XXUEMK9_2138564_REV04_user_low_ship.tar.md5 is valid.
<OSM> CP_N7100XXUEMJ9_REV08_CL1423182.tar.md5 is valid.
<OSM> CSC_OXX_N7100OXXEMK4_2174777_REV04_user_low_ship.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
still nothing. Any further ideas guys?? thanks again.

XXM3G4XX said:
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
Click to expand...
Click to collapse
i guess you have tick marked repartition..you should not do that..

all these roms all request pit files
iprabhsingh said:
i guess you have tick marked repartition..you should not do that..
Click to expand...
Click to collapse
i have followed so many guides its unbelievable. some say to tick, some says dont.
any roms i try to put on always gets stuck around the partition section.
im looking for a good n7100 pit file thats pretty new and is known to work please. would be really helpful. thanks.

XXM3G4XX said:
i have followed so many guides its unbelievable. some say to tick, some says dont.
any roms i try to put on always gets stuck around the partition section.
im looking for a good n7100 pit file thats pretty new and is known to work please. would be really helpful. thanks.
Click to expand...
Click to collapse
just tell me what you really want to do..do you want to install custom rom..or stock rom..was your device rooted before..??

iprabhsingh said:
just tell me what you really want to do..do you want to install custom rom..or stock rom..was your device rooted before..??
Click to expand...
Click to collapse
My device was rooted. I want to get it to work. Doesn't matter with the roms. Any rom that makes it come on is good enough for me.
When I attempt to get it into recovery, all I get is a blank grey screen with white horizontal lines. Download menu doesn't show the device name and all other details are there.
I have tried everything that I've gathered from different threads as well. Keep on getting stuck on pit section.
I've spoken to samsung and sending it for repairs.
I've looked at other threads and from, that I've gathered its half sds and it's a hardware problem which according to the forums will be replaced as the technicians themselves cannot put roms on so they'll change the faulty parts, install a stock rom and send it back.
I could be wrong, so if there are anything else I could try, please advise. Many thanks.

XXM3G4XX said:
My device was rooted. I want to get it to work. Doesn't matter with the roms. Any rom that makes it come on is good enough for me.
When I attempt to get it into recovery, all I get is a blank grey screen with white horizontal lines. Download menu doesn't show the device name and all other details are there.
I have tried everything that I've gathered from different threads as well. Keep on getting stuck on pit section.
I've spoken to samsung and sending it for repairs.
I've looked at other threads and from, that I've gathered its half sds and it's a hardware problem which according to the forums will be replaced as the technicians themselves cannot put roms on so they'll change the faulty parts, install a stock rom and send it back.
I could be wrong, so if there are anything else I could try, please advise. Many thanks.
Click to expand...
Click to collapse
In my opinion if you are not able to find anything from xda or any other site..i think you should go to samsung service center..
or i guess you have bad recovery..just try to flash a new recovery like cwm or philz recovery through odin..May be this might help you.

Update to the issue NOW lol
Hi guys, hope all is well with everyone. I sent the phone to the service centre and got it back unresolved but better than originally. I have new issues which is explained in a new thread. Please advise and help if possible. Many thanks again guys. much respect.
http://forum.xda-developers.com/showthread.php?t=2658220

[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.

s4 mini won't boot

I have a Samsung S4 Mini on the Verizon network (SCH-i435). I restarted my phone this morning and it took a much longer than usual to boot. My screen showed the Verizon logo for about 5-10 minutes and when the phone finally booted I was greeted with the utility to set up the phone (pick language, setup email, etc. etc.). I was confused because I had done this already a few months ago when I bought the phone. I skipped the steps and I was greeted with the stock home screen (all my custom shortcuts and widgets were gone). All my marketplace apps were still installed, but some of them had been reset (had to reconfigure waze, winamp, etc). My best guess is that there was an OTA update or some security patch that reset everything. Finally I got things running again the way I liked them. I was using my phone and suddenly it went dead. I tried to restart it but nothing showed on the screen. Oddly enough the phone just vibrates over and over again, but the screen remains black. No matter what I do I can't boot it. The only way I could stop it from vibrating was to pull out the battery. Is there any hope to recover this phone? Thanks.

Did you try to enter recovery mode?

Yes, I followed the instructions on the manufacturer site. I held down the home button, up volume, and powered the device on. A small bit of text appeared for a split second, it was so fast I couldn't read it. It disappeared and the screen went black and the same vibrate pattern started up again.

I got a video camera and managed to capture the text that was being displayed. Here is a screenshot...
It looks like...
MMC: mmc_read fail
Movinaand Checksum Confirmation Fail
Any hope of fixing this?

I asked for recovery cause it was easier to reset to factory the phone. If that's not working, i don't know if there's hope for it to enter download mode, for manual flashing with odin.

I'm able to get into download mode. Is there a ROM I can flash with? This S4 Mini is the Verizon phone so it is the SCH-i435, I didn't think there were any custom roms I could use with this phone.

Stock rom.
Try http://www.sammobile.com/firmware and see if your firmware is there.

Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.

RoyaLKurTx3 said:
Download this for KitKat: http://www.sammobile.com/firmwares/download/31291/I435VRUBNE1_I435VZWBNE1_VZW.zip/
Download this for Jelly Bean (If you had KitKat DO NOT flash the Jelly Bean) :
http://www.sammobile.com/firmwares/download/27312/I435VRUAMK5_I435VZWAMK5_VZW.zip/
If you don't know what you had, flash the KitKat one.
Download Odin, Extrect the downloaded file, Press PDA in Odin and insert the extracted tar.md5 file. Make sure your phone is read with the "COM:**" and start. For detailed info, search on google. Good Luck.
Click to expand...
Click to collapse
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?

droid2501 said:
Thanks for the links. I got the files you said and googled for tutorials. I found quite few and followed the instructions., but I keep getting the error message.... There is no PIT partition. Here is the Odin readout...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I435VRUBNE1_I435VZWBNE1_I435VRUBNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas? I googled around for a bit but didn't find anything. Is there a PIT file specific for the SCH-i435?
Click to expand...
Click to collapse
I am not sure since this is the first time for me with experience with that phone...
In Odin, make sure Auto Reboot and F. Reset Time check boxes are only two that are selected. DO NOT SELECT ANY OTHER OPTION! Click the AP/PDA button and select that file you downloaded earlier with extension I435VRUBNE1_I435VZWBNE1_VZW.tar.md5 Click the CSC button and select file with CSC in its name. Ignore if there is no such file. Click the PIT button and select the .pit file. Ignore if there is no such file. (You should have this file, do it if you are having that error) Now, once you are ready, hit the START button to begin the flashing process.
If you have any other problems please ask.

RoyaLKurTx3 said:
(You should have this file, do it if you are having that error)
Click to expand...
Click to collapse
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.

droid2501 said:
Where do I get this file from? I looked at many Odin tutorials but none of them seem to say where I can get it. My phone is dead so if it's something that I need to extract/transfer from my phone then I'm out-of-luck.
I think I'll just contact Verizon and see if my phone is under warranty and if they can send me a new one. It may be easier than combing the web for a tutorial that more fully explains what this PIT file is and why I need it.
In the future should I disable Verizon OTA updates? I suspect a error during the update is what caused this problem in the first place.
Click to expand...
Click to collapse
The file should be one of the extracted files in the file you have downloaded from my links. If the file is not there, then most probably Verizon modded the phone to not be able to flash via Odin Mode.
The error during the update may have happened because of low battery, making your phone shut down during the update, which is serious.
You can check yourself if your phone is under warranty (excluding the warranty period)
-Just go to download mode and you will see: KNOX WARRANTY VOID: [if it is 0x0, than it you are still under warranty, but if it says 0x1, you are not.]
Yeah, you should go to the place you have bought the phone from, if none of the above steps worked for you.
Good Luck.

I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?

droid2501 said:
I looked at the links you sent me and I searched the samsung site but I could not find that PIT file. I bought it back into my local Verizon store and they gave me a new S4 Mini. The tech didn't say much about why it broke, he only said that it was still under warranty so I was covered. To avoid something like this happening again I wanted to disable updates on my new S4 Mini. I rooted my new phone, purchased Titanium Backup, and Froze SDM. Is there anything else I have to do?
Click to expand...
Click to collapse
You got the same version of your previous phone?

Yes, that's all they would do for free. They did offer me a Droid Turbo for and extra $100.00 but I really don't like the large phones they're coming out with these days so I declined.

Then you shouldn't get OTA Updates. I don't think that it was needed since the problem you got earlier was because of a faulty firmware from Verizon, which is unlikely or your phone had no battery while your phone was updating.