Database Users

[Q] How can I SIM unlock my Canadian S4 ?

I have 3 i337m running 4.3 original firmware.One is Bell, 1 Rogers, 1 Telus.
I've tried all the methods I could find that include downgrading, rooting etc. I cannot seem to get access to the UMTS menu.
Is there any method that works ?

Anthony77777 said:
I have 3 i337m running 4.3 original firmware.One is Bell, 1 Rogers, 1 Telus.
I've tried all the methods I could find that include downgrading, rooting etc. I cannot seem to get access to the UMTS menu.
Is there any method that works ?
Click to expand...
Click to collapse
Everything Ihave seen, the service menu is hidden in 4.3... I never was able to get to it after the update... I did unlock my s3 before 4.3 but my s4 never got it done... best you can do now is either buy an unlock code on the net or take it to one of the mall kiosks... lots of the guys that sell cases unlock phones too for around $20

Anthony77777 said:
I have 3 i337m running 4.3 original firmware.One is Bell, 1 Rogers, 1 Telus.
I've tried all the methods I could find that include downgrading, rooting etc. I cannot seem to get access to the UMTS menu.
Is there any method that works ?
Click to expand...
Click to collapse
Did you try specifically flashing a modem from an older version where it had the service menu? (like the old 4.2.2 modem) and did you try flashing an older one and using RegionLock Away?

DeadlySin9 said:
Did you try specifically flashing a modem from an older version where it had the service menu? (like the old 4.2.2 modem) and did you try flashing an older one and using RegionLock Away?
Click to expand...
Click to collapse
+1
Also, the SIM unlock trick does not seem to work on the i337M with the newer MK6 modem. Heck, I even tried it on stock right when I got mine (which was still on MDJ at the time), and it didn't work. But results vary, apparently. Try downgrading to 4.2.2 stock like DeadlySin9 suggested, and see if that will work. If it doesn't, there should be an app out there that can access the hidden Service Menus; I just can't remember the name of it at the moment.

DeadlySin9 said:
Did you try specifically flashing a modem from an older version where it had the service menu? (like the old 4.2.2 modem) and did you try flashing an older one and using RegionLock Away?
Click to expand...
Click to collapse
The device does not allow downgrades to 4.2.2 for any carrier firmware. I tried region lock away on 4.3 with no success.

Anthony77777 said:
The device does not allow downgrades to 4.2.2 for any carrier firmware. I tried region lock away on 4.3 with no success.
Click to expand...
Click to collapse
Your not downgrading the firmware, just the modem. You can flash it in your custom recovery

DeadlySin9 said:
Did you try specifically flashing a modem from an older version where it had the service menu? (like the old 4.2.2 modem) and did you try flashing an older one and using RegionLock Away?
Click to expand...
Click to collapse
jd1639 said:
Your not downgrading the firmware, just the modem. You can flash it in your custom recovery
Click to expand...
Click to collapse
How can I downgrade the modem ?

Anthony77777 said:
How can I downgrade the modem ?
Click to expand...
Click to collapse
Look for the zip file in the development forum and flash that in your recovery.
Here
http://forum.xda-developers.com/showthread.php?p=42589278

jd1639 said:
Look for the zip file in the development forum and flash that in your recovery.
Here
http://forum.xda-developers.com/showthread.php?p=42589278
Click to expand...
Click to collapse
The modem downgrade fails with odin.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> 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)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!

Anthony77777 said:
The modem downgrade fails with odin.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> 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)
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
Do you have a custom recovery or safestrap? I'd flash the zip on there

jd1639 said:
Do you have a custom recovery or safestrap? I'd flash the zip on there
Click to expand...
Click to collapse
I installed the .zip with cwm recovery but when I checked my modem (baseband) it was mk6 modem, so it was unchanged.

Anthony77777 said:
I installed the .zip with cwm recovery but when I checked my modem (baseband) it was mk6 modem, so it was unchanged.
Click to expand...
Click to collapse
I've never been able to get this to work either. Also related, unlocking will remove LTE, permanently.

azuziel said:
I've never been able to get this to work either. Also related, unlocking will remove LTE, permanently.
Click to expand...
Click to collapse
Unlocking shouldn't remove LTE. All you have to do is make sure to correct the APN, as it might change, and flash back to your newer modem afterwards.
Are you sure your ODIN drivers are set up right? Try reinstalling/manually updating the drivers. They never like to work very well. You could also try Mobile ODIN since you have an unlocked bootloader.

[Q] Cant flash custom recovery on i9506 with stock 5.0.1

I have a i9506 with the official 5.0.1 rom, and due to my device becoming ridicilously slow after flashing the official rom, I want to try an alternative rom. I have tried flashing custom recovery to root my phone, using Odin 3.0.9 and Odin 3.10, I have tried flashing CWM_6.0.4.6_Non-Touch_GT-I9506 and Philz_Touch__CWM_6.3.7_V5.15.0_unofficial_(fixed_preload), but the phone just reboots like nothing happened, and the knox flag is 0x0.
Odin 3.10 says:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
I have enabled USB troubleshooting in developers settings.
Any hints on what I might have done wrong?

Usually you have to root your phone first, then flash the custom recovery.

try this auto root.
http://forum.xda-developers.com/showthread.php?t=2597058&page=190 post number 1897 by dehawk
I have just rooted with this and flashed twrp2850 recovery

GDReaper said:
Usually you have to root your phone first, then flash the custom recovery.
Click to expand...
Click to collapse
adrenalinas said:
try this auto root.
http://forum.xda-developers.com/showthread.php?t=2597058&page=190 post number 1897 by dehawk
I have just rooted with this and flashed twrp2850 recovery
Click to expand...
Click to collapse
Incorrect.
Root has nothing to do with a custom recovery. It are two completely separate things. You never need to be rooted to flash a custom recovery.
You probably just need to uncheck auto-reboot before flashing.

I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..

GDReaper said:
I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..
Click to expand...
Click to collapse
A binary has no relevance on a separate partition
Rooting before flashing a custom recovery is not required

GDReaper said:
I always rooted before flashing a custom recovery.
And in every guide it said that I have to be rooted first. Or it just gave me that impression..
Click to expand...
Click to collapse
Yes, guide makers tend to do that. But it's never needed.

I did a noob mistake, I pressed power, home and volume down. When I pressed power, home and volume up, it worked. Thank you for the feedback!

[Q] How to chage CSC?

Hi
My phone is N910U and it's CSC code is BRI (Thailand)
I was waiting for lollipop update, but it seems that only some countries have received the update.
So I decided to chage CSC to whatever the New Zealand CSC is to get the official update.
My phone isn't rooted and it runs stock rom.
While I was trying to flash recovery.tar via odin, it shows an error:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used correct recovery file, and this happens when I want to flash autoroot too.
USB debugging on, download mode, stock USB cable, reinstalled driver
Does anyone know how to resolve this issue?
Also, can I just download New Zealand firmware and flash it via odin?
Will my phone not brick and be able to use it in the UK?
Any help would be very appreciated
EDIT: FIXED - Disable reactivation lock

Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin

absinthesummer said:
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
Click to expand...
Click to collapse
Thanks for your reply
the reactivation lock was enabled, so I disabled it. But it is still not working.
It shows slightly different error
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I really have no idea what went wrong.
Do you have any clue?

Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.

absinthesummer said:
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried to root it first, and it gave me the same error(new one) as above.
I never had an issue when I was playing around with my SGS3 couple of years ago. Rooting, recovery, custom rom all flashed well via odin.
Any idea?

Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD

cosmostronomer said:
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
Click to expand...
Click to collapse
Very glad to hear it! That reactivation lock is the number one issue when odin fails (on this device anyway)

g900v BootLoop/Wizard loop after factory reset! PLEASE HELP!

Hey guys, so i just tried doing a factory reset on my phone. Now the phone boots into the setup wizard loop stating ''please wait while we prepare your phone''. It never seems to finish preparing so theres definitely something wrong.
The phone was running a pre-rooted g900v stock OE1 with an OD5 bootloader that I had flashed using the flashfire method months ago.
The instruction are in this link http://www.droidviews.com/install-l...sm-g900v-keep-root-and-enable-wifi-tethering/.
I removed sim and sdcard and did factory reset again from recovery with no help.
I attempted to flash both pre-rooted OE1 and OG5 but Odin keeps returning FAIL!
I am still able to get into recovery and download mode luckily but I really don't know how else to get passed this wizard loop.
Please someone help me.

Minikefala said:
Hey guys, so i just tried doing a factory reset on my phone. Now the phone boots into the welcome wizard
The phone was running a pre-rooted g900v stock OE1 with an OD5 bootloader that I had flashed using the flashfire method months ago.
The instruction are in this link http://www.droidviews.com/install-l...sm-g900v-keep-root-and-enable-wifi-tethering/.
I removed sim and sdcard and did factory reset again from recovery with no help.
I attempted to flash both pre-rooted OE1 and OG5 but Odin keeps returning FAIL!
I am still able to get into recovery and download mode luckily but I really don't know how else to get passed this wizard loop.
Please someone help me.
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546 then download the full ncg odin tar one and flash that then re root it (download towelroot busy box safestrap all that) and im not sure what to do for the upgrading part its happening to me too but on the OC4 one it works fine until i flash the oc4 kernal but that will atleast get you a working rooted phone

Veid71 said:
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546 then download the full ncg odin tar one and flash that then re root it (download towelroot busy box safestrap all that) and im not sure what to do for the upgrading part its happening to me too but on the OC4 one it works fine until i flash the oc4 kernal but that will atleast get you a working rooted phone
Click to expand...
Click to collapse
Thank you for responding so quickly!!
Thank you for responding so quickly.
Unfortunately, the links for the OC4 rooted link in the thread you shared me does not work. I attempted to flash the ncg_full_odin and the g900v_downgrade_to_ncg and both returned fail in ODIN.
If you have any other sources for the file or any other ideas it would be greatly appreciated. I hope this is fixable......

Minikefala said:
Thank you for responding so quickly!!
Thank you for responding so quickly.
Unfortunately, the links for the OC4 rooted link in the thread you shared me does not work. I attempted to flash the ncg_full_odin and the g900v_downgrade_to_ncg and both returned fail in ODIN.
If you have any other sources for the file or any other ideas it would be greatly appreciated. I hope this is fixable......
Click to expand...
Click to collapse
no problem and you downloaded this one and flashed it with odin in download mode? G900VVRU1ANCG_Full_Odin.tar

Veid71 said:
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546 then download the full ncg odin tar one and flash that then re root it (download towelroot busy box safestrap all that) and im not sure what to do for the upgrading part its happening to me too but on the OC4 one it works fine until i flash the oc4 kernal but that will atleast get you a working rooted phone
Click to expand...
Click to collapse
Veid71 said:
no problem and you downloaded this one and flashed it with odin in download mode? G900VVRU1ANCG_Full_Odin.tar
Click to expand...
Click to collapse
Yes, that file!
ODIN fails after ''NAND write start!'' step.
It is a .rar file so tried both converting to .tar with 7z application and just manually renaming to .tar. neither worked though.

Minikefala said:
Yes, that file!
ODIN fails after ''NAND write start!'' step.
It is a .rar file so tried both converting to .tar with 7z application and just manually renaming to .tar. neither worked though.
Click to expand...
Click to collapse
hmmm thats really weird maybe you have something wrong with your nandroid try redownloading it and flashing it again might have been a bad download
it should read something like this
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4

Veid71 said:
hmmm thats really weird maybe you have something wrong with your nandroid try redownloading it and flashing it again might have been a bad download
it should read something like this
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
Click to expand...
Click to collapse
Mine is reading
-file analysis
-setupconnection..
-initializing..
-Get pit Mapping..
-Firmware update start..
-singledownload
-g900vvru1ancg_full_odin.rar
-NAND Write start!!
-FAIL
-
-Complete(write) operation failed
is there any way to do this in recovery?
will try to re-download

Minikefala said:
Mine is reading
-file analysis
-setupconnection..
-initializing..
-Get pit Mapping..
-Firmware update start..
-singledownload
-g900vvru1ancg_full_odin.rar
-NAND Write start!!
-FAIL
-
-Complete(write) operation failed
is there any way to do this in recovery?
Click to expand...
Click to collapse
hmmm i cant really help much with this one maybe message a mod and see what they say about it or someone more experienced

Veid71 said:
hmmm i cant really help much with this one maybe message a mod and see what they say about it or someone more experienced
Click to expand...
Click to collapse
I managed to revive my phone by bringing to all the way back down to NCG using this thread, http://forum.xda-developers.com/showthread.php?t=2784880.
Thank you for the help!

Minikefala said:
I managed to revive my phone by bringing to all the way back down to NCG using this thread, http://forum.xda-developers.com/showthread.php?t=2784880.
Thank you for the help!
Click to expand...
Click to collapse
No problend don't forget if you upgrade to lollipop you gotta flash oa8 or oa6

Problem trying to install Stock Firmware

Whlist trying to put stock firmware back on my Note 3 SM-N9005 the USB became disconnected and I am now stuck with this issue, I can still get Odin to recognise phone and boot into download mode but cannot flash the stock firmware as I think I have corrupted something, not sure how to proceed, below is my current read outs from Odin.
<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> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Kies Recovery ??

JJEgan said:
Kies Recovery ??
Click to expand...
Click to collapse
Kies recognises the phone but gets stuck in an endless connecting message or quits after a few minutes saying coudln't connect to phone.

Are you flashing the latest stock ROM from sammobile.com?
Tried using different USB cables or USB ports?

audit13 said:
Are you flashing the latest stock ROM from sammobile.com?
Tried using different USB cables or USB ports?
Click to expand...
Click to collapse
Hi,
Yes, I am using the latest stock ROM from sammobile, and I have tried all USB ports and 3 wires, it's always failing at the NAND write start stage in Odin on all ports and wires. Thanks for the advice so far.

Try another firmware .
Search Nand Write fail .

The aboot.mbn file is the bootloader.
You confirmed the phone model# in download mode?
Aboot.mbn can fail to flash because the bootloader is not for the phone, the bootloader in the phone is newer than the bootloader being flashed, and/or you need to use the original Samsung usb cable.