Develop Bugs

[FIX][UPDATE: 19.Jan.2011][110% SAFE] 3-Button Combo FiX for Selected/ALL Firmwares

Changelog:
19.01.2011
-NEW links added
-Heimdall Method is now better explained
02.01.2011
-Added Italian tutorial (written by Z4kW0lf)
18.12.2010
-Added Spanish tutorial (written by Vvaleta, Vinclar and Lorse of HTCmania, thanks guys !)
17.12.2010
-Updated Odin3 solution to use md5 checksum - will NOT hang at boot.bin (Windows, thanks to Lorse and Intronauta of HTCmania)
09.12.2010
-Added the latest bootloaders from Samsung, optimized for Froyo on Galaxy S
-Added the Android dumping method (BML1) for my original FiX
-Files inside RAZ_P-SBL_SGS.tar will be flashed using Heimdall (Windows & UNIX)
-Removed the EXPERIMENTAL x0 FiX (redbend_ua self-flash for x0 Firmwares).
28.10.2010
-Initial Release
Hello FiXed World 3.0 by RazvanG .. in dedication to my beloved grandmother, Camelia Petrescu (05.SEP.1934 – 03.DEC.2010) I will always love you.
(because information should be free for all):
YOU MAY NOT, BY ANY MEANS, USE THIS SOLUTION/CODE OR PART OF IT FOR COMMERCIAL PURPOSES.
DO NOT USE THIS METHOD COMMERCIALLY
YOU ARE NOT ALLOWED TO USE THIS METHOD IN YOUR FREE SOFTWARE WITHOUT PROPER CREDITS ADDED TO IT.
YOU SHOULD ALWAYS MENTION MY NAME AND MY PAYPAL ACCOUNT FOR DONATIONS IN YOUR SOFTWARE IF YOU CHOOSE TO USE THIS SBL FiX
PLEASE give credit (and donations if you can) to RazvanG for finding The Solution, writing this Tutorial and the Automated Script (PayPAL Donation)
For those of you that have donated THANKS!
01. Ghioane Gino Cristian; Romania
02. Jimmie Knutas; Sweden
03. Jose Mendoza; USA
04. Anonymous; Norway
05. Reschi85; Austria
06. Ekin Tekbiyik; Australia
07. Salman Daha; USA
08. Jamie Sidford; UK
09. Stefano Passerini; Italy
10. Fabio Verardo; Italy
11. Radu Marian Enache; Romania
12. Haanstra Sander; Netherlands
13. Rares Alin Benea Nadaban; Romania
14. Alex Curtis; UK
15. James Darley; UK
16. Boris Lulic; Croatia
17. Pietro Rossin; Italy
18. Jonathan Scarfo; Argentina
19. Karl Sever; Austria
20. Markus Kaldenbach; Ireland
21. Wong Ling Choo; Singapore
22.
23.
.. and a bigger THANKS to those who will donate in the future !!
//IF YOU ARE ON FROYO (ANDROID 2.2/2.2.1) OR ON ECLAIR (ANDROID 2.1) WITH A x0 FIRMWARE (OFNI x0) USE HEIMDALL METHOD OR ODIN3 (V1.7) METHOD TO REFLASH YOUR BOOTLOADERS
//UPDATE
//17.DEC.2010
//ALL FIRMWARES
Since Richthofen didn't update his Odin3 solution to use the LATEST bootloaders (03.dec.2010), there you have it.
If Samsung Drivers are properly installed for Download Mode, the flashing process is just as safe to do so with Odin3 as with Heimdall.
When the Galaxy S is connected to the PC in Download Mode, you have to see in Device Manager: USB Composite Device Samsung and Samsung Mobile Modem.
If you see this, is 100% safe to use Odin v1.3 or v1.7 to flash the bootloaders.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Preparations: Make sure you have the drivers installed (i.e Kies is recognizing the phone) and "USB Debugging" is turned on in "Settings -> Applications -> Development" menu. Type *#0228# in the dialer and check Voltage value (without USB plugged in) is atleast 3800(mV).
HEIMDALL METHOD:
01. Unplug the phone from the computer (if connected)
02. Kill all Kies related software (tray agent, etc)
// if you don't have Heimdall's Drivers installed, skip only step 3 for now, and follow the tutorial until you get to step 6, then (with the mobile still connected in Download Mode) run zadig.exe from Heimdall's Driver folder to install proper drivers. After that, continue the tutorial with step 7
03. Start Heimdall Downloader (Heimdall-frontend.exe)
04. Plug in the phone to the computer
05. Download adbDownload.zip
06. Unpack adbDownload.zip and run/double click on Download.bat
07. Download RAZ_P-SBL_SGS.tar
08. Unpack RAZ_P-SBL_SGS.tar
09. Move to Heimdall-Frontend.exe (GUI) and select boot.bin and SBL.bin.
10. Flash the bootloaders
You can get the latest Heimdall, here
Please read the instructions and README files included in the archives.
NOTE: You must have the Microsoft Visual C++ 2010 redistributables installed on your system for Heimdall to work.
ODIN3 METHOD:
1. Unplug the phone from the computer (if connected)
2. Kill all Kies related software (tray agent, etc)
3. Start Odin3 v1.3 or v1.7 Downloader
4. Plug in the phone to the computer
5. Download adbDownload.zip
6. Unpack adbDownload.zip and run/double click on Download.bat
7. Download PSbl_stockJPU.tar.md5
8. Move to Odin3 v1.3 or v1.7 Downloader and select "PSbl_stockJPU.tar.md5" as PDA file. Make sure "Phone Bootloader Update" is ticked and re-partition is unticked. Do not select any other files but "PSbl_stockJPU.tar.md5".
9. Press "Start" button to launch the update process. It will take around three seconds to complete. After the update phone will reboot automatically.
// Romanian Tutorial translated HERE
// Spanish Tutorial translated HERE
// Italian Tutorial translated HERE
//READ BELOW ONLY IF YOU ARE ON ANDROID 2.1 OR USING A CUSTOM RECOVERY MENU TO APPLY THE UPDATE.ZIP
//READ BELOW ONLY IF YOU ARE ON ANDROID 2.1 OR USING A CUSTOM RECOVERY MENU TO APPLY THE UPDATE.ZIP
//READ BELOW ONLY IF YOU ARE ON ANDROID 2.1 OR USING A CUSTOM RECOVERY MENU TO APPLY THE UPDATE.ZIP
Many Orange users and other Branded Galaxy S users bricked or semi-bricked their E-Fused or U3 Phones while applying various 3-Button Combo FiXes.
NOW here is a real PROPER solution ! 110% SAFE ! for Selected Firmwares. NO Odin3 required !
HOW-TO check if your mobile is compatible (Windows):
Step 1: Download the XVI32 Hex Editor
Step 2: Dump your BML1 block (rooted phone needed):
Step 2 Explained:
on ANDROID:
Install "Terminal Emulator" (Market download)
Run "Terminal Emulator" and type:
su (a superuser request will be displayed on the phone screen, accept it).
dd if=/dev/block/bml1 of=/sdcard/bml1.dump
The dump will be copied to the root of the internal SD card.
or WINDOWS:
Open a new command prompt and type:
adb shell
su (a superuser request will be displayed on the phone screen, accept it).
dd if=/dev/block/bml1 of=/sdcard/bml1.dump
The dump will be copied to the root of the internal SD card.
Step 3: Open the bml1.dump file with XVI32.
Step 4: Search (in ASCII Mode) for OFNI.
If the block reads "[email protected]" just follow the tutorial below starting with Step 1.
If it reads "x0" then STOP as this FiX will BRICK your phone if applied !!
HOW-TO check if your mobile is compatible (UNIX):
on UNIX, any hexdump (or od / ghex /etc...) programs will show, for what you call a bad "x0" dump:
Code:
hexdump -C bml1.dump | grep OFNI
000053e0 4f 46 4e 49 1c 02 d7 30 44 02 d7 30 00 48 2d e9 |OFNI...0D..0.H-.|
and for the "safe" dump:
Code:
hexdump -C bml1.safedump | grep OFNI
000053e0 4f 46 4e 49 1c 82 21 40 44 82 21 40 00 48 2d e9 |[email protected][email protected]|
Other output format, with od:
Code:
od -c bml1.dump | grep "O.*F"
0051740 O F N I 034 002 327 0 D 002 327 0 \0 H - 351
od -c bml1.safedump | grep "O.*F"
0051740 O F N I 034 202 ! @ D 202 ! @ \0 H - 351
If it reads "x0" then STOP as this FiX will BRICK your phone if applied !!
Why is this different? How come it is 110% Safe for Selected/ALL Firmwares containing the [email protected] block?
Well .. it uses redbend to self-flash a proper SBL, compatible with the Primitive one found on Selected firmwares
I want to thank my sweet little girlfriend, Georgiana Coman , for making this possible by supporting the geek inside me :* and also for helping me re-pack and upload the needed files.
Also, I want to welcome baby Vlad, into this wonderful world ! (23.nov.2010)
Step 1: Download RAZ-FiX-SGS.zip
Step 1.1: Place the file to the root of the INTERNAL phone's memory and rename it to: Update.zip
Step 1.2: Make sure USB debugging is enabled (Settings->Applications->Development->USB Debugging)
Step 1.3: Connect the Phone to the PC
Step 2: Download adbRecovery.zip
Step 2.1: Unpack adbRecovery.zip
Step 2.2: Run Recovery.bat
//for the next step to work, you need to be on Recovery 2e (Android 2.1). It will NOT work on Froyo (Android 2.2, Recovery 3e)
//to get the proper recovery menu back, follow the guide found HERE (thank you, Reschi85)
Step 3: Select on the phone's menu: apply sdcard; update.zip and press the Home button.
After a few seconds, the phone should restart and the FiX will have been applied.
Now, just use the regular 3-Button Combo to enter Download Mode (Volume Down + H0me + Power) or Recovery !!
Enjoy .
Very special thanks go to..
Georgiana Coman , the girl behind the legend
Special thanks go to..
Richthofen for giving me a place to start in developing this method.
DukeForever for providing the "bad" BML1 Dump (Orange Fr)
Tyxerakias for providind the BML4 (Sbl.bin) Dump
Lorse for writing the automated x0 script and providing the info about proper driver installation.
Intronauta for re-packing the needed files for Odin3 flashing
Vvaleta and Vinclar of HTCmania for translating/writing the tutorial in Spanish
Reschi85 for writing the instructions on how to get Recovery 2e on Froyo
NicDumZ for the UNIX output
Z4kW0lf for translating/writing the tutorial in Italian
.. and a F*ck YOU goes to the Authorized Romanian Orange Care Center Service Team, especially Cristian I.
Please use my PayPal account for donations. Thank You.
Razvan Ghituleasa

e-fused ??
i got a bell
I9000UGJG9
will this work for me...
does the lag fix have to be removed?
and how about if it's rooted?

you are my new hero if this works I'v allready bricked my phone twice with the other solution.

tb5... said:
e-fused ??
i got a bell
I9000UGJG9
will this work for me...
does the lag fix have to be removed?
and how about if it's rooted?
Click to expand...
Click to collapse
Here is how to check if the PBL is good or not for SBL update:
Download the XVI32 Hex Editor
Dump your BML1 block (rooted phone needed):
Open a new command prompt and type:
1. adb shell
2. su (a superuser request will be displayed on the phone screen, accept it).
3. dd if=/dev/block/bml1 of=/sdcard/bml1.dump
The dump will be copied to the root of the internal SD card.
Open the bml1.dump file with XVI32.

stinger32 said:
you are my new hero if this works I'v allready bricked my phone twice with the other solution.
Click to expand...
Click to collapse
.. just take a leap of faith and post the results

RazvanG said:
.. just take a leap of faith and post the results
Click to expand...
Click to collapse
Hehe I wonder what the service center will say if I show up for the third time and blame Kies again they must think I'm an complete fool. The service-center didnt manage to fix it the second time, they have sent it back to Samsung so I'm waiting for it right now.

At last, a real good working solution.
THANKS YOU.

Would it be possible to adapt this method to all Phones ?
Even non e-fused phones had some bricks while flashing bootloader with Odin.
I made the mistake to flash Kies update without checking first if it was "e-fused" or not and that's what might led me into trouble (tried to flash with Kies, regedit method, no way to tell now about "efused", it's not booting at all, power button not working, Download mode combo not working.)

great tool, worked flawless on my SGS, thank you RazvanG, the other methods seemed to complicated or risky for me so i decided to wait until something safe appears and here it is the safest method.
Great work, greatly appreciated!

aureusz said:
Would it be possible to adapt this method to all Phones ?
Even non e-fused phones had some bricks while flashing bootloader with Odin.
I made the mistake to flash Kies update without checking first if it was "e-fused" or not and that's what might led me into trouble (tried to flash with Kies, regedit method, no way to tell now about "efused", it's not booting at all, power button not working, Download mode combo not working.)
Click to expand...
Click to collapse
It *should* work on any firmware (even non e-fused).. if you want to take a leap of faith, be my guest and post the results.

Thank you man!
And do you know if there is a technical operation to unbrick those who bricked their "orange" phones using various 3-Button Combo FiXes?

Worked like a charm for me. Thanks a lot RazvanG
@aureusz
Try the method with 301K resistor (you can find it here: http://forum.xda-developers.com/showthread.php?t=819551 ).
It works, if you have working boot loader, but blocked 3 button combos (i've tested it).

cyberdamienb said:
Thank you man!
And do you know if there is a technical operation to unbrick those who bricked their "orange" phones using various 3-Button Combo FiXes?
Click to expand...
Click to collapse
You can force the firmware update into the phone using the JTAG port (on the PCB) or you can make a JIG Tool using a modified USB Cable (see this thread) and force the phone to enter Download Mode and then reflash using Kies or Odin3

So, what makes this safer than the original one?
It uses the same SBL as I did with the Redbend release.
The SBL is incompatible with some old PBL versions, so to make it safe it is required to update the PBL too.
This is the reason I use Odin to flash PBL & SBL.
So this is identical with my GT-I9000_SBL_RCVDL_FIX_REDBEND.7z (released 9/19/2010).
I do not recommend using either of these versions as the PBL-SBL updater (Odin method) has proven to be alot safer.

Richthofen said:
I do not recommend using either of these versions as the PBL-SBL updater (Odin method) has proven to be alot safer.
Click to expand...
Click to collapse
Yea right...

Richthofen said:
So, what makes this safer than the original one?
It uses the same SBL as I did with the Redbend release.
The SBL is incompatible with some old PBL versions, so to make it safe it is required to update the PBL too.
This is the reason I use Odin to flash PBL & SBL.
So this is identical with my GT-I9000_SBL_RCVDL_FIX_REDBEND.7z (released 9/19/2010).
I do not recommend using either of these versions as the PBL-SBL updater (Odin method) has proven to be alot safer.
Click to expand...
Click to collapse
This method is 110% safe for the eFuesed terminals (tested on many phones from Orange Romania before releasing).
The Odin3 method that you provide, updates both the PBL and the SBL, and sometimes fails resulting a brick.
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You say that: If Odin gives a error it is a driver issue or you did not follow the instructions.. but a brick is a brick and the phone needs JTAG to recover or a home-made JIG (soldering skills)
I know many guys who bricked their phones using your latest (so called safer) method and had to send the phone back to Samsung for flashing. I only provided a fix for those who don't want to take that risk.
Thank you for providing at some point a SBL. It helped a lot

manosv said:
Yea right...
Click to expand...
Click to collapse
Can you elaborate a bit?

RazvanG said:
This method is 110% safe for the eFuesed terminals (tested on many phones from Orange Romania before releasing).
The Odin3 method that updates both the PBL and the SBL, sometimes fails and bricks the phone.
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You say that: If Odin gives a error it is a driver issue or you did not follow the instructions.. but a brick is a brick and the phone needs JTAG to recover or a home-made JIG (soldering skills)
I know many guys who bricked their phones using your latest method and had to send the phone back to Samsung. I only provided a fix for those who don't want to take that risk.
Thank you for providing a SBL in the first place. It helped a lot
Click to expand...
Click to collapse
True, but this version of the SBL has also been producing bricks with phones with E-Fused PBL´s. I don´t know why would it be different this time.

RazvanG said:
This method is 110% safe for the eFuesed terminals (tested on many phones from Orange Romania before releasing).
The Odin3 method that you provide, updates both the PBL and the SBL, and sometimes fails resulting a brick.
<ID:0/003> Please wait..
<ID:0/003> Checking MD5 finished Sucessfully..
<ID:0/003> Leave CS..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You say that: If Odin gives a error it is a driver issue or you did not follow the instructions.. but a brick is a brick and the phone needs JTAG to recover or a home-made JIG (soldering skills)
I know many guys who bricked their phones using your latest (so called safer) method and had to send the phone back to Samsung for flashing. I only provided a fix for those who don't want to take that risk.
Thank you for providing at some point a SBL. It helped a lot
Click to expand...
Click to collapse
I am one of them

Richthofen said:
True, but this version of the SBL has also been producing bricks with phones with E-Fused PBL´s. I don´t know why would it be different this time.
Click to expand...
Click to collapse
I'll reconsider this FiX after someone using an eFused phone gets a brick following my tutorial, but for now .. 110% success rate
Thank you once again

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

[Q] Lot of questions about the GT-B5510 (Y Galaxy Pro).

I bought this phone a week ago. My phone has Android 2.3.5, and I know that Samsung has released Android 2.3.6, but I cannot update through "software update" and even by Kies. Always says that I have the latest version.
My questions:
1) Samfirmware has the 2.3.6 for my model (GT-B5510B). Is a tar.md5 file. But I read that this phone didn't accept update via Odin. Is this correct? I tried via Odin. I selected the tard.md5 in PDA but I always received:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
[tar.md5 file] is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl.bin
NAND Write Start!!
BcmCP.img
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I'm doing something wrong?
2) I can install CWM in this phone? There's some tutorial?
2.1) If I can install CMW in this phone, can I applied the tar.md5 file through CWM? Or tar.md5 is only accepted on Odin? If tar.md5 cannot be applied through CMW, can I convert tar.md5 file to a format accepted by CWM?

GT-B5510
Hi, I also have the phone and i'm very pleased with it, but is quiet a low profille device, there isnt any custom roms or whatever, we can only hope that some developer undertake that task.
about your problem, talk with Doky, he helped me a lot with some serious issues.
keep in touch

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

tutabeier said:
I bought this phone a week ago. My phone has Android 2.3.5, and I know that Samsung has released Android 2.3.6, but I cannot update through "software update" and even by Kies. Always says that I have the latest version.
My questions:
1) Samfirmware has the 2.3.6 for my model (GT-B5510B). Is a tar.md5 file. But I read that this phone didn't accept update via Odin. Is this correct? I tried via Odin. I selected the tard.md5 in PDA but I always received:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
[tar.md5 file] is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl.bin
NAND Write Start!!
BcmCP.img
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I'm doing something wrong?
2) I can install CWM in this phone? There's some tutorial?
2.1) If I can install CMW in this phone, can I applied the tar.md5 file through CWM? Or tar.md5 is only accepted on Odin? If tar.md5 cannot be applied through CMW, can I convert tar.md5 file to a format accepted by CWM?
Click to expand...
Click to collapse
I have the exact same problem. Try with different computers, different cables, different firmware, tried on win7 & winxp.... still get the same problem... fail every time. Anyone managed to flash the flash their B5510?
Matt

b5510
i have exactly the same problem here..plzzzzz let we know about the solution

Finally found a flashable firmware for my B5510. Most website claim that it is possible to flash with only 1 file but I didn't get it to work. You guys may wanna try this firmware. It is also 2.3.6, have all the modem/PDA/bootloader/csc files. I got it from here... http://forum.gsmhosting.com/vbb/f200/samsung-b5510-hang-up-done-odin-1465719/ (thanks to author) and link to download here... http://www.4shared.com/zip/WKBL3GY7/B5510DXKK1_OLBKK1.html or here ...http://www.mediafire.com/?g8xjuzo9l3xzcim
I flash this firmware over my china bought B5510....
Hope this helps....

need stock rom 2.3.5 for galaxy gt-b5510
can sombody help me with restoring the 2.3.5 or 2.3.4 for the gt-b5510
I need the files and manual for installing the image

If you want to flash the available fimware you need to split it up in a MODEM/CSC/PDA file. This is done with Splitfus2.
I have split several firmwares and uploaded them to Rapidshare. Note that when you flash the 'splitfus2' firmware you DO NOT use luisa_0623.pit and DO NOT check repartition and only use the MODEM/CSC/PDA file with Odin3 v1.85.
The Philippines firmware (December 2011) is no 'splitfus2' firmware. It contains all the files (including a boot and luisa_0623.pit file). If you want, you can use this firmware to do a 'clean' install and then install a 'splitfus2' firmware of your choice/country. But you can install the other firmwares on top of your current firmware if you please.
Firmware:
December 2012 Luxembourg B5510CELK2_B5510LUXLK1_B5510XXLK1_HOME.tar.md5 --> Split-up flashable firmware
Ocotber 2012 Germany B5510XXLH3_B5510OXALH4_B5510XXLH3_HOME.tar.md5 --> Split-up flashable firmware
September 2012 United Arab Emirates B5510JPLI1_B5510OJPLF1_B5510XXLH3_HOME.tar.md5 --> Split-up flashable firmware
August 2012 Spain (Orange) B5510BVLF1_B5510AMNLF1_B5510BVLF1_HOME.tar.md5 --> Split-up flashable firmware
July 2012 Philippines (Smart) B5510DXLF1_B5510OLBLF1_B5510DXLE1_HOME.tar.md5 --> Split-up flashable firmware
May 2012 Italy B5510XXLE3_B5510ITVLB1_B5510XILE1_HOME.tar.md5 --> Split-up flashable firmware
May 2012 Phlilippines (Smart) B5510DXLE2_B5510OLBLD1_B5510DXLE1_HOME.tar.md5 --> Split-up flashable firmware
April 2012 Spain (Orange) B5510BVLD1_B5510AMNKJ2_B5510BVLD1_HOME.tar.md5 --> Split-up flashable firmware
March 2012 South Africa (Vodafone) B5510XXKL3_B5510XFVKK1_B5510XXKL1_HOME.tar.md5 --> Split-up flashable firmware
January 2012 Greece (Cosmote) B5510XXKK3_B5510OXAKK2_B5510XXKK2_HOME.tar.md5 --> Split-up flashable firmware
December 2011 Philippines (Full firmware package rev03) --> Full package
December 2011 Netherlands B5510CEKK1_B5510KPPKI2_B5510XXKK2_HOME.tar.md5 --> Split-up flashable firmware
October 2011 Romania (Cosmote) B5510XXKJ2_B5510OXAKJ2_B5510XXKJ2_HOME.tar.md5 --> Split-up flashable firmware
October 2011 Serbia B5510XXKJ2_B5510OXFKJ1_B5510XXKJ2_HOME.tar.md5 --> Split-up flashable firmware
B5510B Firmware Brazil
B5510B May 2012 Brazil (VIVO) B5510BVILE1_B5510BZVVLE1_B5510BVILE1_HOME.tar --> Split-up flashable firmware
B5510B February 2012 Brazil B5510BVILB1_B5510BZTOLB1_B5510BVILB1_HOME.tar.md5 --> Split-up flashable firmware
B5510L Firmware Peru
B5510L October 2010 Peru (SAM) B5510LVSKI5_B5510TFGKI5_B5510LVSKI5_HOME.tar.md5 --> Split-up flashable firmware
I personally flashed April 2012 Spain (Spain firmware gives an altered layout of keyboard) December 2011 Netherlands, Italy May and July 2012 and they work fine, and as always: USE AT YOUR OWN RISK!
(Hit the thanks button if this post was helpful, thank you)

Still confused with flashing
Hello, Im having a hard time flashing my Samsung Galaxy Y Pro Philippines firmware because I don't know how to use the splitfus2 program. Please help

The Phillipines firmware is a complete package that you can flash with Odin. You don't have to use Splitfus on that package. (Or any other package I link to for that matter. They are all ready to flash with Odin.) Odin should be present in the package.
How to use Odin:
- Make sure your battery is full
- Start Odin
- Put your phone in download mode (volume down + Home key (house button) + power. This can be tricky sometimes your phone wil boot normally. You should release the power just around when the phone starts to bootup. You will get a message 'are you sure, press volume up')
- When the phone is in download-mode connect USB. Odin will give a COM# connected message.
- Check 'Re-partition' and place the correct files in the selectionboxes:
PIT : Luisa_0623.pit
BOOTLOADER : Boot_B5510xxxxx...
PDA : PDA_B5510xxxxx_.....
PHONE : MODEM_B5510xxxxx_....
CSC : GT-B5510-MULTI-CSCxxx....
- Press Start and wait
If you flash a split-up firmware (Just stock split up in a PDA/PHONE/CSC file) you do as described above, but you leave the PIT-selectionbox an Bootloader-selectionbox empty. You don't check 'Re-partition'
(press the thanksbutton if you think this post was helpful, thank you)
EDIT
Maybe I understood your question wrong and you are trying to split-up the latest Philipines firmware. I am downloading it now and I will process it for you. I will post a dowloadlink later.

I'm not allowed to post more outside links while I don't have 10 posts yet so the first link (Philippines May 2012) is your splitup firmware ready to flash with Odin.
Look at post #8

gt-b5510
Hi,
i can only use the Odin3.185, any higher like 4.42 or 4.34 does not recognize the phone. i am looking for an dutch firmware (rooted or stock) with android 2.3.5 or 2.3.4.
can someone help me please....
the single file Odin does not work and when i try to download the splitfus i get access denied.
regards
**** toha

****.toha said:
Hi,
i can only use the Odin3.185, any higher like 4.42 or 4.34 does not recognize the phone. i am looking for an dutch firmware (rooted or stock) with android 2.3.5 or 2.3.4.
can someone help me please....
the single file Odin does not work and when i try to download the splitfus i get access denied.
regards
**** toha
Click to expand...
Click to collapse
Please read post #8.
I've packaged Dutch firmware that is flashable including Odin (for B5510). I've tested the hotlink, it redirects you to the download link on Rapidshare.
Could you be more elaborate on what the problem is. How do you mean 'access denied'? Is this a message from Odin? Is this a message from your webbrowser?
---------- Post added at 03:45 PM ---------- Previous post was at 03:00 PM ----------
@****.toha
Maybe you are using Odin wrong. The correct manner to update your B5510:
- Download the desired firmware from post #8. (The firmware has to be split up, so the RAR will end with "....by Splitfus2")
- Extract the files from the RAR in a folder on your computer
- Open Odin (don't connect your phone with the USB cable)
Putting your phone in 'Download' mode.
- Power off your phone
- Press at the same time: volume down + home (button whith 'house' logo) + power on. (This part is a bit tricky because sometimes the phone just boots normally. When the phone powers on you have to release the power. A warning will appear with 'are you sure, press volume up'. Once you press volume up you are in download mode.)
- Get into download mode
- (Now) Connect the phone with the USB-cable. Odin will give a yellow bar with COM# connected.
- Place the extracted PDA/MODEM/CSC file in the designated selection box.
(do not use a .PIT or BOOT file and don't check Re-partition. Just the three files from the package.)
- Hit 'start' --> because your phone is in 'download'-mode Odin can connect to your phone and wil flash the new firmware.
- Wait until your phone is rebooted.
Hopefully this will help you allong.
(if you find this post helpful, please hit the thanks button, thank you)

GT-B5510
Hi borrelbar,
still linked to hotfile.com in trhead #8

****.toha said:
Hi borrelbar,
still linked to hotfile.com in trhead #8
Click to expand...
Click to collapse
I am sorry, I don't understand what you mean.
The links in post #8 are for Rapidshare downloads not hotfile.

gt-b5510
Hi Borrelbar,
sorery for that i had the wrong thread, downloading now, many thanks

No problem, good luck.

???
@borrelbar
Thank you for your help, I've been able to flash my galaxy y pro.But here is another problem, when i went to settings/about phone, I saw that the Kernel version of my phone is still rooted having kernel version 2.6.35.7 [email protected]#1.
How do I remove this? I want my phone to be super clean

richsmart24 said:
@borrelbar
Thank you for your help, I've been able to flash my galaxy y pro.But here is another problem, when i went to settings/about phone, I saw that the Kernel version of my phone is still rooted having kernel version 2.6.35.7 [email protected]#1.
How do I remove this? I want my phone to be super clean
Click to expand...
Click to collapse
I do not know what the code beneath the kernel version means exactely, but form what I have seen is that stock (updated) firmwares have something in the line of [email protected] I think it's some kind of identification of the employees workstation who worked on the rom. The Rom itself is completely stock with no tampering at all.
Your phone is not rooted at this time if that is what you mean. Your firmware is stock and full of bloatware (apps you don't use but take up memory and space). It is possible to root your phone --> install titanium backup (app) --> remove system apps you don't want and thereby clearing memory and space.
You can clean up your system and make it 'super clean' whith this method.
I can't post you the link (because I don't have 10 posts yet) but if you google 'root b5510' you should find a tutorial with downloadlink for the superuser app (update.zip).
I hope this answers your question (a bit).

Hi guys,
i've installed the B5510 XXLE3 from italia, but i do need the french keybord (physical). Any idea where i can find the french csc?
Thx

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