Database Users

Devs Need volunteers that are using 1.5

This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.

e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5

NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.

Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip

FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.

Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.

Ah. My bad.

We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working

Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?

Scratch that. I don't think AVDs will get OTAs.

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"

zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)

nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0

Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.

FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0

bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.

nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0

bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.

Im still on 1.5 PM me and ill help if needed

Do you guys still need this?

[GUIDE] Galaxy Tab Network Unlock

**UPDATE**
This method causes your serial number to change to 00000000 (which isn't a problem as such as this isn't currently used for anything) but there is a new method which involves directly hex editing the nv_data.bin file, which may be faster and does not change your serial number. You can find the details here: http://forum.xda-developers.com/showthread.php?t=843323.
**UPDATE**
First up I'll say that I'm not incredibly familiar with Galaxy S firmware changes/modding, and this mostly builds on work done in these areas, so not all these steps may be necessary but they worked for me. If someone can suggest a faster way to do this/unnecessary steps then please go ahead and reply with them!
This unlocked my Network Locked Australian Galaxy Tab and so I assume should work for others.
You should back up your /efs/ folder before you proceed as you may need this to undo if something goes wrong.
*I take no responsibility if something goes wrong!*
Requirements:
Root access
repair_nv_data.zip (from http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94)
Java
Busybox
The Android SDK for ADB, Root Explorer or some similar file system explorer/editor
(If you have US firmware with no Phone software, you may need to flash European firmware as described here: http://forum.xda-developers.com/showthread.php?t=838250 ).
Firstly, on your phone dial *#7465625# and check if the Network Lock is set to [ON], if so then your phone is locked (duh), so continue.
1. Use Superoneclick (http://forum.xda-developers.com/showthread.php?t=812367) to root your phone (the other z4root method may work as well, but this isn't what I used).
2. Either use ADB or some other method to rename or delete (backup first):
/efs/nv_data.bin.md5
/efs/.nv_data.bak
/efs/.nv_data.bak.md5
(I just used Root Explorer to rename them to something else).
3. Restart your phone and then go into the /efs/ directory and see if the 'nv_data.bin.md5' file has been re-created by your phone, as long as it has been created then you can proceed.
4. Go to http://forum.xda-developers.com/showpost.php?p=8942669&postcount=94 and download the repair_nv_data.zip file (the credit for all of this mostly goes to that thread and helroz).
5. Install 'busybox' from the Market. Once you install it, you actually have to run it and properly install it (the Market app is basically an installer) - the files in the above zip have a dependency on this.
6. Extract the above zip to your PC, plug in your Tab in USB debugging mode. Run the Step 2.bat from the extracted file. You may need to allow the script super user access several times. This should copy the /efs/ and a bunch of files into a directory with a french name.
7. Run the Reparation_nv_data.jar file. (You will need Java for this step.) It will prompt you to enter two numbers, which are your pseudo-unlock codes. I entered '11111111' and '11111111' (eight 1's) both times. This rewrites the nv_data.bin file to be simunlocked with these details.
8. Run the Step 4.bat. Your superuser app (the one installed when you rooted using SuperOneClick) will need you to allow each command to have root access so keep an eye on your Tab. You may need to press y/n a few times if you encounter errors. This is uploading the edited nv_data.bin onto your Tab.
This batch file will stop several times and need you to hit a key when it pauses. My Tab rebooted halfway through this batch file - when it did this I waited for it to fully reboot back to the lock screen before pressing a key to make the script continued while the Tab was actually able to respond to its commands.
9. Towards the end of its execution it rebooted a second time. It paused during loading up and had some yellow writing on the screen saying it was updating media (I assume it was rebuilding the nv_data.bin). Leave it for a minute and it will prompt you to reboot/some other options. Just press whatever it wants (home I think) to reboot the phone - you don't want any of the other recovery options.
10. Go into your dialer and put in *#7465625# again and (hopefully) voila! Your phone should no longer be network locked. Try a SIM from a different provider to make sure.
Enjoy!
Edit: I had to go out and actually buy a prepaid SIM to confirm that all was working with a different provider. Attached are screen caps of my Tab on two different networks, as well as the network status screen, making/receiving calls etc. all works on both.

Awesome man, thanks.
This is much better than the 2 month wait we had for Galaxy S unlocking.

Hello, I'm french and i use your post to unlock my Galaxy TAB SFR ''réunion island'' and she is unlock thanks for your AMAZING post for unlock TAB
Ps: For unlock my TAB by SFR REUNION, he tell me 150 Euros.... Vive smithdc & helroz

Works well! I had little trouble running java on windows7. But changing compatibility mode to windowsxp sp3 and check run this program as an administrator solved the problem.
Thanks for easy guide!

tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).

Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?

smithdc said:
tacoda, you mean for running the .jar file? or for installing Java itself? (I assume the former).
Click to expand...
Click to collapse
Running the jar file. I didnt know how to run it.
Sent from my SGH-T959 using XDA App

Does the sim card and/or sd card should or should not be plugged in during the unlocking progress?

It shouldn't make a difference Zeron.Wong.

jay_jay_n said:
Sweeet thx , curious if unlocking the AT&T version has hardware only set to AT&Ts 3G frequencies, so 3g wont work on tmobile or is it capable of running 3g on tmobile with a unlocked AT&T tab?
Click to expand...
Click to collapse
Traditionally, AT&T and T-Mobile hardware used different radios, it was more than just firmware. That's also true on the little brother Galaxy S series, the Vibrant has a different radio than the Captivate (though the Vibrant radio DOES have 1900 band in the hardware, for some reason).

Kudos to smithdc for this awesome guide! I saved a lot of money thanks to him. Congrats again.

Bump, is there any way to sticky/pin this for people?

So your saying if I use this method and install my tmous unlimited sim I can get calls and 3g or do I need a prepaid sim

I'm not sure on how T-Mobile are blocking, but if it IS my IMEI then you would have to use a SIM from a different network.
If they are blocking your IMEI on their network, then you would have to use a SIM from a different network (as a different network, wouldn't be blocking this IMEI number). Changing it to a different SIM on the same network won't help as your IMEI is for the device itself.

I just want to clarify something..
I have a T Mobile Tab and want to use a SIM I have for ATT.
Will I have to flash my device with the EU firmware first in order to get the phone software on it..then do the rest of the unlocking steps?
Assuming thats correct..after unlocking it I then can put my ATT sim card in and it should work for calls and data (Edge only) with not having to tweak any setting at all? Or do I have to set up my wap.cingular connections for the data like on a WM phone on ATT?
And if I want to get back to original out-of-the-box firmware from T Mobile (like if I had to send it in for repair) I just have to flash stock T Mobile firmware and its back completely to original?
Thanks..and wow am I loving this TAB !!!

You'll need to set up your APN data for AT&T, yes.

Thanks for the fast reply. As for the flashing of the EU rom..is that the only/best way so far in order for me T Mobile Tab to get the radio software on it. I was thinking I saw an APK for the radio software someplace but did not know what way was better.
I just want to be 100% sure bfr I take the jump to unlocking and playing with the phone part
thanks

I got a quick couple of questions:
1. If I restore original firmware (Canadian), does it relock my phone?
2. Where can I get the Canadian firmware release? I see EURO and US, but no Canadian.

I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?

clubtech said:
I read on one of the other threads that sim unlock method also changes your imei number. Is this really case?
Click to expand...
Click to collapse
Yes, it will set your IMEI to a bogus one that will get your T-Mobile internet access disabled after 1/2 hour.

Dummy's Guide to update your I9000 from the stock software to the Official Froyo

After successfully;
researching, upgrading to the official build of my choosing, getting it to work and typing this tutorial out (for those that like me weren't knowledged in this),
I stumbled across this thread. I thought I should also share it here aswell.
Here's a N00b's (Dummy's) Guide to how to update your device from the stock software to the Official Samsung Froyo ROM (software/operating system) OF YOUR CHOICE!!
Why do this?
You get Froyo. So you get the latest version of Android to support more Apps.
It comes with some UI-tweeks, JIT-compiler, and FLASH 10.1 PLAYER!!!
Also you get a newer (better) kernel on your phone with some of Samsung's fixes for the lag and for the GPS.
You can get features/Apps not available in your native rom build and/or remove the bloatware.
This method (not incl E) can also be used to install custom ROMs (I personally can't wait for the Official English MIUI ROM).
** Denotes steps which I skipped, or was unable/unwilling to follow, or didn't quite understand
Here's the comprehensive, step-by-step, easy-to-follow breakdown/walkthrough (Section E only works on Windows Computers):
A) Remove your microSD card (this will prevent some weid issues later on)
A2) Make sure you have Kies downloaded and installed on your computer
A3) Make sure you have an extractor installed (for Windows 7, winRAR is a great free solution)
B) We need to root your device, for this goto "One Click Root/Unroot" by TGA_Gunnman at http://forum.xda-developers.com/showthread.php?t=742403
B1) Download (2.5MB) the software (depending on your computer, mine is Win7 Home Premium 64-bit) into your computer not phone
B2) Make a folder somewhere in your computer labelled "OneClickRoot" (or anything) and drag the .rar file (the one you just downloaded) into it
B3) Extract the contents of the files by Right-Click then "Extract Here" (If you don't have this option install WinRAR)
B4) Set your phone to USB Debug mode (on your phone goto MENU > Settings > Applications > Developement > USB debugging = Checked) and then connect the phone to the computer via USB cable.
B5) Open the "Galaxy S I9000 One-Click Root" application. (This step didn't work for me, so I instead opened "rootme" batchfile which started the command prompt).
B6) Your phone will shut itself off, and then turn on in a "recovery mode". DO NOT REMOVE THE CABLE. Use the Volume Up and Volume Down buttons to get to "install from " and then hit the Home button.
B7) Now your device should be restarting again but this time it will actually go to your lockscreen.
B8) Now, you have ROOT, Congratulations.
B9) Not sure? We can test to see if you have root. Goto Market on your phone and download two Apps (Superuser and Titanium Backup, use the search to find them fast).
B10) Install both and launch Titanium Backup. As soon as you turn it on it will come up with a pop up and say something like "Your device is not rooted" or "Root is not accessible" ... if you didn't get Root.
B11) If you have root it will say something like "Titanium Backup needs to gain permission from Superuser" here click Apply. If you get to the App, well done you have indeed Rooted your phone
C) Now if you want to Backup your device before the update (recommended) you can follow steps C, otherwise skip straight to Step D.
C1) On Titanium Backup if a pop up notification comes with something like "Download an updated BusyBox" allow it to do so.
C2) Now first thing you will want to backup your Apps (all paid and free and the levels/hiscores) make sure you don't have any emulator ROMs on there (they consume too much space) and delete all those unwanted Apps
C3) On Titanium Backup, hit the Menu button > More > Create "update.zip" ...
C4) On this screen select "User application" and "TitaniumBackup-3.6.2.zip" and UN-TICK the "Sign the ZIP file (with ZipSigner)"
C5) Hit the Create "update.zip"... on the bottom and Please wait
C6) Once it finishes it, exit Titanium Backup, go back to settings and disable USB debugging (as posted on B4).
C7) Connect your phone to your computer (through Kies or PC link) and then browse your My Computer until you find Galaxy S I9000.
C8) Open that folder and then open phone. Find "TitaniumBackup-3.6.2.zip" and copy that to somewhere on your computer.
C9) Now that we have backed up your applications, lets backup your ROM.
C10) According to TGA_Gunnman you can use Clockwork MOD Recovery to do this, but this is for a different (Galaxy S) device ie "Samsung Vibrant"
**C11) Follow the steps on http://forum.xda-developers.com/showthread.php?t=734164 to do so, personally I skipped doing so out of fear of bricking the device (there may be subtle differences between the devices that can make your phone a paperweight/brick)
C12) Now if you did follow the Clockwork MOD, be sure to copy the "update.zip" file somewhere into your computer (better be safe than sorry)
D1) Now we need to apply the 3-Button-Combo Fix (this is the only reason for steps A-C because it is highly recommended to have this before flashing ANY rom)
D2) I recommend the Fix by RazvanG http://forum.xda-developers.com/showthread.php?t=821698 because it seems to be the *safest*
**D3) Firstly check if your device is compatible. I wasn't successful to dump my BML1 block, so I couldn't test if the block reads "[email protected]"
**D3) RazvanG has provided some instructions on this method see his post for more information http://forum.xda-developers.com/showthread.php?p=9595936#post9595936
D4) So I took a leap of faith and continued anyways with the risk of bricking my device. I have it on contract/plan so if it fails I would just return it and say Kies was updating and it failed
D5) I followed the steps on the thread but I'll reitterate it here for your convnieance
D6) Download both files (RAZ-FiX-SGS and adbRecovery) from the thread.
D7) Make a new folder (adbRecovery) on your computer and extract the adb .zip file into there
D8) Connect your phone to the computer and copy the RAZ-FiX-SGS.zip into your phone's memory
D9) Delete the old Update.zip file AND rename the RAZ-FiX-SGS.zip to Update.zip
D10) Again, turn on USB debugging (you know how) and open "Recovery" batch file from your computer
D11) This will initiate a command prompt (on Win7) and restart your phone
D12) Your phone will go into recovery mode (like we've seen before)
D13) You need to navigate (Volume buttons) to "apply sdcard; update.zip" and hit the Home button
D14) Your phone will turn off and restart and should get to your lockscreen
D15) So you're at the lockscreen? SUCCESS! (mine didn't brick *pheww*)
D16) Now let's test to see if the 3-Button-Fix worked
D17) *IMPORTANT* Firstly browse into your phone's internal memory and delete update.zip (the one we put there from RazvanG)
D18) Now that you have done so, you can safely just turn off the device
D19) Hold the Volume Down + Home button ... then hold the power button, as soon as the device begins to turn on release the power button (keep holding Volume Down + Home)
D20) If you get a Yellow triangle with the Android robot and "Do not turn off Target", well done, you have the 3BF so you have a means to ensure that you can always recover your phone if you do brick, well done!
D21) You can *safely* remove the battery and restart your phone ONLY if you don't have a Update.zip in the root of your phone
D22) If you don't want to take a leap of faith try this method (safest method but doesn't work for some people): http://forum.xda-developers.com/showthread.php?t=860773
E1) Now is the fun part (we've just past the difficult parts)
E2) You need to hunt down the version of (official Samsung)software you wish to install ... just go through member's reviews and recommendations
E3) You need to find the product code of that build, you can do this navigating through this thread http://forum.xda-developers.com/showthread.php?t=846913
OR by asking members (they can find out with http://forum.xda-developers.com/showthread.php?t=787163)
E4) For me this was the Virgin mobile Australia build (XSA - an unbadged, no-bloatware, unlocked Froyo build with a free copy of Navigon Navigation)
E5) Make sure you update your Kies to "ver 1.5.3.10103_102" (latest as of the time I'm writing)
E6) Go visit this thread http://forum.xda-developers.com/showthread.php?t=835628 for information (the software may have been upgraded)
E7) Download (300KBs) the Kies Registry patcher 1.6.0.0 (latest as of writing) <<This only works on Windows computers, sorry Mac'ners>>
E8) Launch the Kies Registry Patcher WHEN KIES IS OPENED
E9) Click on File > Backup (and save this somewhere in your computer - this is your original product code - better safe than sorry)
E10) Make Enable Spoof to True
E11) Now where it says "Spoof Product Code as" type in the product code of your desire (mine is XSA)
E12) Hit Write Registry and it should say "Registry pathed successfully"
E13) Connect your phone via USB cable to the computer
E14) On your phone select "Samsung Kies" when the pop up comes ... it should be at the "Connected" screen (DO NOT HIT HOME BUTTON)
E15) On Kies it should find your phone, and a pop up on the corner will say "There is a firmware update available for your phone" hit that pop up
E16) Now you will see another pop up and it's asking if you want to "Back up contacts before upgrading firmware" ... seems like a good idea, tick the box and hit Upgrade
E17) If the screen on the phone shuts (ie standby) don't be alerted. Hit the power button to wake it up. DO NOT HIT THE HOME BUTTON!
E18) Another pop up will come to name the contacts file - I just hit save so its the original filename in original (Samsung)folder
E19) Another Pop up will come to say "Save to PC completed" - hit OK, its just letting you know the contacts saved properly
E20) Now you get another Pop up to start the Firmware Upgrade - This is an important area, note down the: Model Name, Current Version and Latest Version (if something goes wrong this info maybe valuable for developers)
E21) Mine is (model)GT-I9000, (current)PDA:JG4 / Phone:JG3 / CSC:JG2 and (latest) PDA:JP5 / Phone:JP3 / CSC:JP4 ......... notice they are diffirent, this is what I was looking for
E22) Hit Upgrade! (Allow Kies to function when Windows 7 or Windows Vista prompts you)
E23) Tick the "All information has been verified" and Click Next
**E24) Let Samsung record your phone number in their database? I don't care (I'm on insurance/contract/plan) and I hit "Allow saving" ad Clicked Next
E25) Wait patiently, its downloading the rom from the server, DO NOT UNPLUG THE DEVICE
E26) A progress bar will appear, your USB will get disconnected, reconnected several times, the phone will be stuck on the yellow triangle screen - these are normal
E27) The progress bar will slowly be filled from grey to blue and a progress bar will appear on your phone - almost there!
E28) The progress bar on the computer will finish and the pop up will read "GT-I9000 Upgrade completed" - Click Close
E29) Your phone will restart and will enter "recovery mode" some yellow texts will appear and scroll forward
E30) The phone will reboot again and you will see the boot image with the Galaxy S logo
E31) The phone will be stuck on that logo for awhile - be patient
E32) The phone will now get to your lockscreen, unlock it
E33) You will have to go through your initial setup firstly its the Swype tutorial, then data settings, and finally the account settings emerges
E34) If the Kies connection screen comes up: hit the home button
E35) Now you should have come to your Homescreen go and test everything (all your passwords, all your bookmarks, all your contacts, all your images/music/videos and all your apps (except bloatware) should be there but the order of all the widgets/apps in TouchWizz will be reset to abc-order)
E36) Goto Settings > About Phone Does it say Android 2.2?
E37) Well done you have passed Android Hacking 101, you are officially smarter than 50% of iPhone and Blackberry users
E38) Donate me a beer, nah just kidding, enjoy everything for free but feel free to donate to the developers that help make this possible

this is a guide for I9000 international
I9000M owners please be advised that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem

AllGamer said:
this is a guide for I9000 international
I9000M owners please be advized that the I9000 might cause you to lose the 850 band, and might also trigger the internal SD problem
Click to expand...
Click to collapse
You made it into a thread, thanks!
Hopefully this might help fellow xdanians

Aww Mate this is awesome, I have the same Carrier and I had OPTUS crap on my Phone from custom roms, Now I'm back to Stock Froyo!!!!
A great tool to Start from afresh.....
But
At Instruction E11 - Select your product code from the drop down Box and it will populate the next field for you.

Gonna put into my favorites

Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram

DamianGto said:
Wow.
I don't think anybody that don't now much would read that.
I know allot and i would never use it either.
You should stick a warning sign on this tread.
I did read about half of it and then i just stop and shake my head.
I hope this tread is a joke.....
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
Click to expand...
Click to collapse
Can you elaborate?
Joke? No it's no joke but I should disclose (as always) this is a tried-and-true way of getting you to update your software but in no way can I be held responsible for damages.
Things may vary slightly in between different phones which is why the links for each source/thread is up there.
I found myself knowing what to do, but always guessing how to do it.
This is a step-by-step process of how and what I did to upgrade my phone to any ROM I want.
If this was posted up before I attempted my upgrade, I would've been so happy that someone really simplified it for me

This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there

nagrom78 said:
This is a noobs guide??!!! Simplified??!! I think that everyone will appreciate the time you have spent typing this up and trying to help, but I'm with DamianGto, dude this guide is scary and just explains how YOU got YOUR particular phone running froyo and lets face it, you certainly didn't go about it the easy way!
Once again I think the time you have spent and the willingness to help is admirable, but there are much simpler and noob friendly guides out there
Click to expand...
Click to collapse
Well you need root + busybox to get the 3 button fix.
If anything a n00b did, they can recover with 3 button trick otherwise they will have a brick.
This is why this guide is long, to ensure things are a-ok.
If you found a friendlier guide can you post the link, much apprecated ;D

How do I exit downloading mode if I forgot to erase update.zip ?

What is it ? Kies
A2) Make sure you have Kies downloaded and installed on your computer
Thanks

Well I think this is an excellent guide that has great potential!
However, a couple of crucial mistakes, which if fixed could help make the guides less confusing...
At beginning of (D) you talk about (A-C) being solely so you could fix your 3 button download (which I don't think is actually true!)
.... But, you should mention 3 button download at the very start of the guide anyway!!
Also, you should include a quick test at the very start to check for 3 button download, because mine is already fine, so a newbie might run all those extra steps when they already had working 3 button download anyway! (The more sections that can be skipped the better!). You can then steer people to the sections they uniquely will need.
However, titanium backup isn't needed for 3 button download fix, but is a wise step before running a rom update. And this works best with root anyway. Hence I don't think your opener for (D) is very accurate. You didn't just complete those steps JUST to get download mode. The backup was important anyway!
Do others think there should be a stage added for backing up contacts etc?
A stage for backing up efi?
Anything else wise that should be in here?

[Q] 7004>nodo>mango dev unlock...is there an easier way?

Hi Everyone,
I just received a brand new ATT Focus from US ( with the SIM unlocking code also ).
The phone is rev 1.3 and running 7392 atm.
Searched and searched on XDA, Google also...couldn't find a definitive answer at all...
What is the easiest/fastest way to get to dev unlocked Mango ?
So far, from what I've read is to revert to 7004-chevron unlock-update NoDo- keep the unlock-update mango ( of course some registry tweaks during the way).
Thanks,

htc9420 said:
So far, from what I've read is to revert to 7004-chevron unlock-update NoDo- keep the unlock-update mango ( of course some registry tweaks during the way).
Click to expand...
Click to collapse
That is the only way except ofc, paying the developer unlock.

OMFG...I'm stuck @ 7008 version. Zune tells me it's the latest update...LOL
this is driving me nuts...can do Silverlight but can't update the freaking phone

htc9420 said:
OMFG...I'm stuck @ 7008 version. Zune tells me it's the latest update...LOL
this is driving me nuts...can do Silverlight but can't update the freaking phone
Click to expand...
Click to collapse
Try on another computer. That solved it for many.

Job done
haha, I wasn't seeing the trees because of the forest.
For anyone that might get interested in this, here are the steps that worked great for me ( didn't put any SIM, nor had the time adjusted):
All info I had maily came from this :
http://forum.xda-developers.com/showthread.php?t=1143999
1. Install/flash 7004. Unlock via chevron. Use any registry editor to erase the values from HKEY_LOCAL_MACHINE > Software > Microsoft > DeviceReg/PortalUrlInt, remove its value data and save it. Do the same with PortalUrlProd
2.Zune upgrade to 7008.
3.Zune upgrade to NODO.
STOP THE UPDATING WHEN DONE otherwise ZUNE will automatically proceed to the last two updates that leads to Mango.
4. Deploy http://forum.xda-developers.com/attachment.php?attachmentid=722646&d=1316284246
5. Deploy http://www.edisk.cz/en/download/38910/New_SMS_unlock.xap_41.01KB.html
6. Make root /provxml. Copy unlock.xml to it.
7. Let Zune do the rest.
In my case, everything worked flawless and updated to the last samsung update: fm 2103.11.8.1; radio: 2103.11.8.1 BL: 5.8.0.2

you forgot to mention that after updating to mango 7720, you need to run the diagnostics app to load the "unlocked" profile. Heres a link to the thread, but this thread i find is unclear;
http://forum.xda-developers.com/showthread.php?p=16809179
What i did was the following AFTER the update to MANGO!
1. Enter the diagnostics terminal by entering "##634#" as a phone number
2. Typed "*#9908#" in the diag. mode, which brought me to the GPRS settings
3. Scrolled through the list of profiles, selected "unlock", clicked "save"
4. now your focus is ready for sideloaded apps!

htc9420 said:
haha, I wasn't seeing the trees because of the forest.
For anyone that might get interested in this, here are the steps that worked great for me ( didn't put any SIM, nor had the time adjusted):
All info I had maily came from this :
http://forum.xda-developers.com/showthread.php?t=1143999
1. Install/flash 7004. Unlock via chevron. Use any registry editor to erase the values from HKEY_LOCAL_MACHINE > Software > Microsoft > DeviceReg/PortalUrlInt, remove its value data and save it. Do the same with PortalUrlProd
2.Zune upgrade to 7008.
3.Zune upgrade to NODO.
STOP THE UPDATING WHEN DONE otherwise ZUNE will automatically proceed to the last two updates that leads to Mango.
4. Deploy http://forum.xda-developers.com/attachment.php?attachmentid=722646&d=1316284246
5. Deploy http://www.edisk.cz/en/download/38910/New_SMS_unlock.xap_41.01KB.html
6. Make root /provxml. Copy unlock.xml to it.
7. Let Zune do the rest.
In my case, everything worked flawless and updated to the last samsung update: fm 2103.11.8.1; radio: 2103.11.8.1 BL: 5.8.0.2
Click to expand...
Click to collapse
Consider me new; can you connect steps 4 and 5 with step 6? 4/5 are each XAP files, what purpose does each serve?
Also (and maybe related), unlock.xml seems to be within one of the linked XAPs if you change it's extension to ZIP. How do I copy it to /provxml? This isn't self evident to me, but maybe it is once in Root Tools? I haven't been in Root Tools yet, but is there somewhere to do step 6 within this and if so, can you summarize where?
Sorry for the many questions, there's a lot of info that's hard to digest on the matter - this is pretty close to being the best (most understandable) step-by-step once the questions I posed are answered. Thanks.

xaeryan said:
Consider me new; can you connect steps 4 and 5 with step 6? 4/5 are each XAP files, what purpose does each serve?
Also (and maybe related), unlock.xml seems to be within one of the linked XAPs if you change it's extension to ZIP. How do I copy it to /provxml? This isn't self evident to me, but maybe it is once in Root Tools? I haven't been in Root Tools yet, but is there somewhere to do step 6 within this and if so, can you summarize where?
Sorry for the many questions, there's a lot of info that's hard to digest on the matter - this is pretty close to being the best (most understandable) step-by-step once the questions I posed are answered. Thanks.
Click to expand...
Click to collapse
When you get to NoDo-cancel search for updates as it will surely get you to Mango without unlock.
Install ''WP7 Root Tools" from the link-yes it is a xap.
Install " New SMS" xap from the link.
Open WP& root tools on phone. Make a provxml folder in root. Navigate to Applications/Install/D19A80F2-..../Install and copy unlock.xml.
Paste unlock.xml inside the previously created PROVXML folder.
Exit.
Go to home screen open Phone.
Go to dialer- dial ##634#. A new program should open.
Type *#9908# and a new dialog comes out.
Choose unlock from the list. Press save. Exit.
Done. Fertig. Listo. Finito.
Hope it's clearer this time. Good luck.

This steps should be posted in a new thread and stickied.. IMO, its really hard to find good collected guide about the focus...

3G not working after Unlock
Hey guys, have you noticed that 3G data doesnt work anymore after loading the unlock.xml profile under Mango? I tried reloading the other presets that were available in the GPRS diag. shell, but my 3G is still knocked out. Any thoughts? I am with Rogers in Canada

htc9420 said:
When you get to NoDo-cancel search for updates as it will surely get you to Mango without unlock.
Install ''WP7 Root Tools" from the link-yes it is a xap.
Install " New SMS" xap from the link.
Open WP& root tools on phone. Make a provxml folder in root. Navigate to Applications/Install/D19A80F2-..../Install and copy unlock.xml.
Paste unlock.xml inside the previously created PROVXML folder.
Exit.
Go to home screen open Phone.
Go to dialer- dial ##634#. A new program should open.
Type *#9908# and a new dialog comes out.
Choose unlock from the list. Press save. Exit.
Done. Fertig. Listo. Finito.
Hope it's clearer this time. Good luck.
Click to expand...
Click to collapse
Yup, it's not much different from your previous steps, but the few bits you added helped make the rest more evident. Danke!
pachuau86 said:
This steps should be posted in a new thread and stickied.. IMO, its really hard to find good collected guide about the focus...
Click to expand...
Click to collapse
Agreed!
---------- Post added at 08:36 PM ---------- Previous post was at 08:29 PM ----------
ssingh819 said:
Hey guys, have you noticed that 3G data doesnt work anymore after loading the unlock.xml profile under Mango? I tried reloading the other presets that were available in the GPRS diag. shell, but my 3G is still knocked out. Any thoughts? I am with Rogers in Canada
Click to expand...
Click to collapse
Look around in the WP7 hacking forum for mango update threads - I remember reading something specific to this very issue - "how to fix 3G after provxml unlock" or similar...

ssingh819 said:
you forgot to mention that after updating to mango 7720, you need to run the diagnostics app to load the "unlocked" profile. Heres a link to the thread, but this thread i find is unclear;
http://forum.xda-developers.com/showthread.php?p=16809179
What i did was the following AFTER the update to MANGO!
1. Enter the diagnostics terminal by entering "##634#" as a phone number
2. Typed "*#9908#" in the diag. mode, which brought me to the GPRS settings
3. Scrolled through the list of profiles, selected "unlock", clicked "save"
4. now your focus is ready for sideloaded apps!
Click to expand...
Click to collapse
Just to confirm, you went through 7392, 7403, and 7720 all BEFORE selecting the unlock profile, right? LOL, I rolled back to Nodo to do this a few days ago, and Zune isn't giving me the option to update anymore, so when (if?) it finally does, I want to make sure I don't screw up and have to roll back again.
Not sure why it continues to tell me no updates are available when I have already gone through the update (using the official process) before, so I know it has been released to me. Perhaps it was only "available" to me briefly before they moved on to a different set of users?

do i have to use the unlock using dialpad BEFORE or AFTER mango update... im in 7392 (i think thats NoDo???) right now, and im confused

Get Update from different carrier using SmartSwitch [Canadian]

IF YOU USED THIS METHOD BEFORE AND WANT THE NEW ROGERS/FIDO UPDATE THEN LOOK AT POST
http://forum.xda-developers.com/showpost.php?p=68314268&postcount=72
This guide is for Canadian S6 edge owners who are with Rogers or Fido since the been waiting for Marshmallow update forever. However, This should work for for others as long as the TWO CARRIERS share the exact phone model, which is the case for all s6 in canadian market.
DO it on your own responsibility
Doing this will not delete your data or trigger knox ... However, its wise to backup with SmartSwitch before attempting so.
1- I assume that you running windows and have latest version of samsung smart switch installed (I tried it on Windows 10)
2- install Fiddler (Its used to capture HTTP traffic and we will use it to be man-in-the-middle between Smartswitch and Samsung servers)
https://www.telerik.com/download/fiddler
3- Install FiddlerScript Editor (we will use to write and edit script rules)
http://www.telerik.com/download/fiddler/fiddlerscript-editor
4- Open Fiddler go to Rules --> customize rules
delete everything and past whats in the txt file in the attachment
5 - In this we are interested in only two functionsin that script
the contact from SMARTSwitch to the Sever: Here instead my phone identify itself as Fido phone "FMC" to the server it pretend its Kodoo phone "KDO"
Code:
static function OnBeforeRequest(oSession: Session) {
if (oSession.uriContains("NF_DownloadBinaryInform")){
oSession.utilReplaceInRequest("FMC", "KDO");
}
}
the contact from the server to SMARTSwitch: Here i get replay from the server for Kodoo phone "KDO" but i pass it to SmartSwitch as Fido phone "FMC"
Code:
static function OnBeforeResponse(oSession: Session) {
if (oSession.uriContains("NF_Download")){
oSession.utilReplaceInResponse("KDO","FMC");
}
}
6- Now safe and restart Fiddler
- Also when you open Fiddler go to File -> Capture traffic
make sure its checked
- Also make sure that fiddler can access HTTPS traffic by going to Tools--> Fiddler options --> HTTPS tab
make sure that 'capture HTTPS connect" and "decrypt https traffic" are both checked
7- Another thing worth mentioning, in Smart Switch > More > Preferences > Software update you have to deactivate Latest software Pre-Download
if you keep that option checked, the download will start in background before you click the update button, and procedure will end in error too;
8- Start SmartSwitch and plug your phone.
9- Click on the Update button
10- after Smart switch is offering the update download, accept the terms of update, then immediately when download start preperation, fidller must be closed. it is very crucial that Fiddler be turned off at just the right time otherwise you will get an error ;
Note: those are the codes for Canadian Carriers:
- Fido: FMC
- Koodo : KDO
-Rogers: RWC
-Bell: BMC
- Wind: GLW
-Telus: TLS
- Virgin: VMC
-Sasktel: BWA
-EastLink: ESK
- Vidéotron: VTR
This page will show you which carrier has the latest update
http://www.sammobile.com/firmwares/database/SM-G925W8/
For now Kodoo has the latest update which support wifi calling

thank you; greatly appreciated;
just installed the Telus version of 6.0.1, July 1 security patch; it worked very fine.
only one mention you may add maybe:
after Smart switch is offering the update download, accept the terms of update, then immediately after the download start, fidller must be closed;
else the download will end with error at about 70%
the rest is flawless, absolutely no problem with the update, first boot will take little more time, even more if lot of apps are installed, because all apps are optimized at first boot.

850RPM said:
thank you; greatly appreciated;
just installed the Telus version of 6.0.1, July 1 security patch; it worked very fine.
only one mention you may add maybe:
after Smart switch is offering the update download, accept the terms of update, then immediately after the download start, fidller must be closed;
else the download will end with error at about 70%
the rest is flawless, absolutely no problem with the update, first boot will take little more time, even more if lot of apps are installed, because all apps are optimized at first boot.
Click to expand...
Click to collapse
Happy it helped, just updated the post.
Heads up Kodoo has the latest update which support wifi calling and for some reason I see big improvement on my battery especially is wifi calling enabled and you you are in wifi coverage

Do I just copy/paste that code as is if I'm with Rogers or do I need to change it to RWC?

Yes after u copy and past whats in the attachment, you need to change both FMC to RWC since you are with rogers

aboganas said:
Yes after u copy and past whats in the attachment, you need to change both FMC to RWC since you are with rogers
Click to expand...
Click to collapse
It's not working for me, gives me the button to update it but when I do it it says preparing the software update components but then I get a pop-up that says "ErrorCode=5,ErrorMessage=The operation completed successfully." and that's it

Hello,
Will this work for someone who bought a locked Rogers Samsung Galaxy S6 Edge and is using it unlocked now on Bell network? What would I change the scripts to? It's not showing any update in Smartswitch for me, currently on 5.1.1.

jcrann said:
Hello,
Will this work for someone who bought a locked Rogers Samsung Galaxy S6 Edge and is using it unlocked now on Bell network? What would I change the scripts to? It's not showing any update in Smartswitch for me, currently on 5.1.1.
Click to expand...
Click to collapse
Yes it will work. Just change both FMC to RWC

daandman said:
It's not working for me, gives me the button to update it but when I do it it says preparing the software update components but then I get a pop-up that says "ErrorCode=5,ErrorMessage=The operation completed successfully." and that's it
Click to expand...
Click to collapse
As I said in the post when start preparing the update and before start downloading you need to close Fiddler otherwise you will get the error

aboganas said:
Yes it will work. Just change both FMC to RWC
Click to expand...
Click to collapse
I have everything set up correctly and I can see the Update button, I hit it, goes to preparing and I close Fiddler it then says The most current update is already installed on connected device. I'm on SM-G925W8, Android 5.1.1.
Should I try changing the RWC to BMC as Im currently on Bell network even though it was a locked Rogers phone?
EDIT: Nevermind sorry, it looks like I didn't wait long enough before closing Fiddler, downloading now.

Will this work for Galaxy S6 (not Edge) as well?

4walls said:
Will this work for Galaxy S6 (not Edge) as well?
Click to expand...
Click to collapse
I didn't try it on normal S6, but I don't see any reason why it won't work since the only thing we change is the carrier code and nothing else. So it should work

aboganas said:
As I said in the post when start preparing the update and before start downloading you need to close Fiddler otherwise you will get the error
Click to expand...
Click to collapse
Okay that worked, just needed to wait for the windows installation prompt then close Fiddler right away before the download starts. Thanks!

Finally got it to work on the Galaxy S6 (not Edge) Rogers
aboganas said:
I didn't try it on normal S6, but I don't see any reason why it won't work since the only thing we change is the carrier code and nothing else. So it should work
Click to expand...
Click to collapse
Ok, I think I got it to work finally. I tried KDO, but ended up using TLS in the end. I tried several times and got the previously mentioned errors. I also kept getting "this device is up to date" but I kept trying and it seems that it is very crucial that Fiddler be turned off at just the right time. I finally got it to work by turning off Fiddler right after the two notices from Smart Switch and immediately following that, the update download started.
It is downloading now and I will update this post when the upgrade is successful.
Thanks for the tip!
:highfive:

4walls said:
Ok, I think I got it to work finally. I tried KDO, but ended up using TLS in the end. I tried several times and got the previously mentioned errors. I also kept getting "this device is up to date" but I kept trying and it seems that it is very crucial that Fiddler be turned off at just the right time. I finally got it to work by turning off Fiddler right after the two notices from Smart Switch and immediately following that, the update download started.
It is downloading now and I will update this post when the upgrade is successful.
Thanks for the tip!
:highfive:
Click to expand...
Click to collapse
Looking forward to hear your feedback, so maybe I can post the thread in S6 Forum because I know everyone sick waiting for rogers and fido to release the update. I have been using this method since last year to get update as soon as any carrier push it. In theory it should work for all Samsung phones as long as the phone model is the same between the two carrier.

Android is upgrading...
---------- Post added at 11:36 AM ---------- Previous post was at 11:20 AM ----------
aboganas said:
Looking forward to hear your feedback, so maybe I can post the thread in S6 Forum because I know everyone sick waiting for rogers and fido to release the update. I have been using this method since last year to get update as soon as any carrier push it. In theory it should work for all Samsung phones as long as the phone model is the same between the two carrier.
Click to expand...
Click to collapse
It is working just fine. The upgrade was successful and everything works as far as I can tell so far.

Confirmed this worked great on my Rogers phone unlocked to Bell network. Thank you very much!

Guys another thing worth mentioning, in Smart Switch > More > Preferences > Software update you have to deactivate Latest software Pre-Download
if you keep that option checked, the download will start in background before you click the update button, and procedure will end in error too;
the download has to start at your click on update button, to be able to close Fiddler at that point

850RPM said:
Guys another thing worth mentioning, in Smart Switch > More > Preferences > Software update you have to deactivate Latest software Pre-Download
if you keep that option checked, the download will start in background before you click the update button, and procedure will end in error too;
the download has to start at your click on update button, to be able to close Fiddler at that point
Click to expand...
Click to collapse
Thanks for this, thats true. if you don't mind I'll add your post to the thread

So I am trying this out on my s6 tethered to fido
I can't get past the copy and pasting the code part in fiddler. I deleted everything and then copied and pasted as instructed but Fiddler is giving me an error once I try to save it. I can't copy and paste it but Ill type it out here for you....
Fiddler Script error
------------------------------Source---------------------------
{start-of-file}
Error LINE --> static function onbeforerequest(o Session:Session) {
if
(oSession.uricontains("NF_DownloadBinaryInform")){
--------------------------------------------------------------
Only Valid inside a class definition"
Here is the what the text looks like once I paste it in....
static function OnBeforeRequest(oSession: Session) {
if (oSession.uriContains("NF_DownloadBinaryInform")){
oSession.utilReplaceInRequest("FMC", "KDO");
}
}
static function OnBeforeResponse(oSession: Session) {
if (oSession.uriContains("NF_Download")){
oSession.utilReplaceInResponse("KDO","FMC");
}
}
am I doing something wrong?