Hello Everyone!
This OP is meant to be a reference for anyone who may attempt to "unlock" their Verizon S4 so that they can use another carrier's SIM in their Verizon S4 (SCH-I545)
A few weeks ago, I naively followed a guide to unlock my S4 so that it could be used with other carrier's SIM cards. Example Guide (There are many of these throughout the web): http://forum.xda-developers.com/showthread.php?t=2282683 - These guides are NOT meant to used on Verizon branded S4's.
For the record, I followed this guide in an attempt to change some of my network settings in order to get SMS working on a ROM, and did not realize the gravity of changing settings in the Service Mode Menu. To make a long story short, I changed the PERSO SHA256 status in the Service Mode menu (This menu is available on TW ROM's) and also attempted to restore the "Golden Backup" to the NV (Non-volatile memory - I believe). This inadvertently resulted in disabling calling and SMS on my phone. I later learned, and members like @k1mu have talked of this before:
Verizon S4's DO NOT NEED TO BE UNLOCKED
(and already have the PERSO SHA256 status set to "OFF" anyways.)
Our S4's are already capable of connecting to GSM, LTE, CDMA, and other some other network types for different carriers. If you decide to change your carrier to AT&T or Straight Talk, you can do so by changing out the SIM, changing your Network Mode, and setting up new APN's (all of which should be possible on a stock ROM). Although, I understand there are still certain limitations on our S4 with specific bands and network types that may not result in the most ideal performance on another carrier's network. There are also guides and threads throughout the forum that discuss different advanced settings and modifications to achieve certain capabilities on other carriers networks with our phones.
--------------------------------------------------------------------------------
The following information is in reference to MDK users. However, if you are on a different bootloader, Please read the end of this fix for a possible solution.
For those (MDK users) who have attempted to "unlock" their Verizon S4's and are having issues with SMS, Data, or Calling:
There is no way, that I determined, to reset the setting in the Service Mode menu to restore SMS and calling. I was able to change a lot of settings like network bands and data settings, but nothing to remedy SMS and calling. I even went to a Verizon retailer and got a new SIM card (which somehow restored SMS - depending on different Service Mode settings, ROM, and modem). I think Service Mode settings have an affect on both the phone's internal settings, as well as on the SIM card.
It took me many days, a lot of research, a lot of experimentation with Service Mode settings, and getting a new Verizon SIM to stumble on a solution to my issues. My solution arose form this post by @colton22 http://forum.xda-developers.com/showthread.php?t=2650296.
This is how I solved the issues:
- ODIN back to the stock MDK ROM (excellent guide here: http://forum.xda-developers.com/showthread.php?t=2301259 )
- Factory Reset the device via the settings menu Settings > Accounts > Back Up and Reset > Factory Data Reset > Reset Device.
- And Victory! Just follow the above guide to also re-root the device and re-install your custom recovery
Click to expand...
Click to collapse
I know it may seem obvious to ODIN back to stock, but that is not what fixed the issue. I tried that multiple times, tried many different modems, and tried many different network settings. However, the key to this is the Factory Reset via the touchwiz menu. I wiped my phone dozens of times, but it required the stock Verizon ROM factory reset option in order to regain full functionality.
This leads me to a possible fix for non-MDK users:
- It may be possible to restore full functionality by just doing a Factory Reset (via the settings menu) in any TW ROM
- I am unfamiliar with Safe Strap and how the whole system works, so it would be interesting to see if someone not on MDK could remedy this issue if it arose.
Click to expand...
Click to collapse
Thanks for your time! If you have any comments, or if you believe I need to make any corrections to the OP, please let me know.
Thank you!
Glad my post helped. Reading that old thread again gave me goosebumps As I thought I really messed up my phone. I, as well as many others, appreciate people like you who take the time to make sure no one is left behind. Thank you!
My S4 received the crack of doom so I am now typing this off my Edge!
Thanks again!
I'm on KK 4.4.2 with VRUFNC5 Built. Which following built should restore to get service menu for sim unlock?
For VRUAMDK Build (Look for this) - Link
For VRUAME7 Build (Look for this) - Link
For VRUDMI1 Build (Look for this) - Link
Tekone said:
I'm on KK 4.4.2 with VRUFNC5 Built. Which following built should restore to get service menu for sim unlock?
For VRUAMDK Build (Look for this) - Link
For VRUAME7 Build (Look for this) - Link
For VRUDMI1 Build (Look for this) - Link
Click to expand...
Click to collapse
If you are asking about how to recover your phone's SMS and calling capabilities because you tried to unlock your phone via the service menu, then here is my advice:
I have not had anyone test this method that did not have MDK yet. However, I imagine flashing one of Surge's Odin Tar's for your specific bootloader version would be your best option. For NC5, I would recommend using the VRUFNC5 Full-Wipe zip found on this thread: http://forum.xda-developers.com/showthread.php?t=2735172
You can try wiping you phone with the above zip via Odin, then going into the settings menu and doing a Factory reset (as mentioned in the OP).
Let me know if you get any positive results!
However...
If you are trying to gain access to the service menu, you will need to find a guide somewhere else. Verizon S4's do not require a SIM unlock, and therefore I do not recommend you trying to do so.
FYI, I have used this phone for quite some time in Indonesia, maybe almost a year, and I don't get any problem using different carrier. No need to unlocked it anyway, just put my GSM SIM Card (Telkomsel) from the first time I bought it and then it works very well. The only thing that might need to be done is adding a new access point, which is only "internet" for both username and password, if you flash a new ROM.
Related
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Megneto said:
Error: “Not Registered on Network”
SGS III have JB 4.1.1 (I9300XXDLI8) ROM/baseband, rooted with CF-Root/TWRP.
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
I downloaded and flashed Omega 32.1, thinking that I can always go back if something doesn’t work out. Anyway, long and the short of it, when I restored my S3 through TWRP restore, I found out that it isn’t connecting with my mobile network i.e. Warid Tel with the error “Not Registered on Network”.
By the way I also happen to have the factory unlock code for this SGS3, but unfortunately all the USSD codes I've tried to enter it, doesn't work.
Although, I guess I can take it back and get it re-unlocked again, but that isn’t going to allow me to install custom roms.
Can anyone guide me how to fix this situation, any tips, help, will be highly appreciated.
Regards
Babur
Click to expand...
Click to collapse
Check your IMEI number.
Has it changed?
eggman89 said:
Check your IMEI number.
Has it changed?
Click to expand...
Click to collapse
No it hasn't changed.
The problem was the original "soft unlock"
Megneto said:
...
I was running the above ROM with some sort of (probably) Soft unlocking done by a local mobile repair shop. Anyway, recently I decided to try out one of the custom ROM i.e. Omega 32.1 (JB 4.1.1) and before proceeding any further I made a full backup on SD card with TWRP.
...
Click to expand...
Click to collapse
The problem was the original "soft unlock" - some of those (I believe even some early that were made by NSPro) are rather poor and are based on flashing a special modem binary. You will be able to fix it if you search around for the fix posted by Ariza (even if I believe something happened to the original post).
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Hmm ...
Megneto said:
I am trying to find the fix by Ariza, but so far nothing has turned up. Also, if I search for the user "Ariza" it doesn't help either. Do you remember exact member alias?
Also, does that fix result in permanent resolution of the issue?
Or, is it better to get rid of this SGS3, and get factor unlocked version?
Thanks for your help and patience.
Edit:
I forgot to mention in OP that it correctly identifies the network when I check Status of the device.
Edit 2:
I was able to get hold of the guy who actually did the 'soft' unlocking in the first place, and he confirmed that it was done using NSPro (through Dongle) and is willing to do it again.
But the issue is, it will restrict me to JB 4.1.1 and I can't install any custom ROM.
Click to expand...
Click to collapse
The thread was this:
http://forum.xda-developers.com/showthread.php?t=1918601
(in a post towards end I have some of the stuff from the forum where you had to register in order to get the files, and you might still recover some of those links - apparently those are patched versions of the corresponding stock modems which no longer check some of the information from nv_data.bin; you will need to add that modem after each major ROM change).
If you only plan to use 4.1.1 and not upgrade then NsPro should be OK, otherwise you either need a "subscription" to the services of that guy
Thank you for the help. I will go through that thread soon.
I've have also looked at this thread http://forum.xda-developers.com/showthread.php?t=1705650 by UpInTheAir. I have installed android SDK for Winx64 and successfully extracted modem.bin (as a test). I think I'll get the phone back to that guy, so he can patch the modem with NSPro again, once that is done, I'll extract the modem, repackage it so I can install it with CWM and test whether that can eventually help me in experimenting with other ROMs.
I will keep you posted on my progress.
Again thank you for your valued help.
Kind regards.
Babur
Having tried the method mentioned in my previous post, I finally gave up and took the phone for repair.
What transpired from thereon is interesting and confusing. As according to Mr. Repair 'serial number and IMEI' were repaired, nothing more. In fact I extracted the modem and compared it with the one I have, they are exactly same no patch applied.
However, both IMEI and serial number were showing correctly prior to the repair, and even after repair they are same (I double checked those with the original invoice/phone box etc.). So I am not sure how they were damaged when they were showing correctly.
Update:
I've sold the unit question, as I felt not to take any more risks with it, and bought an factory unlocked SGS3. Hopefully I will not face any problems with playing around with custom ROMs from hereon in.
Thank you and kind regards to all.
Babur
When I found the Darth Stalker multi-carrier ROM for the Galaxy S4, I was very happy. It works very well, and has allowed me to take my Verizon Galaxy S4 (i545 version) -- that wouldn't work on a US GSM carrier -- and put it on a $60 AT&T "GoPhone" BYOD plan. This saved me about $80 a month since I have 2 phones on the account.
Unfortunately, soon after flashing this ROM, I found out that my WiFi could not be turned on. After some research, I found that there were some modules not included in the ROM that are needed on the i545 variant for WiFi to work properly. I was able to install these easily.
Unfortunately, this ROM will **NOT** work alongside the stock ROM through SafeStrap; it will flash in a ROM slot just fine, but it won't boot at all. This is thanks to the antics of Verizon developers in Verizon's constant attempt to lock their phones to their service. But all is not lost! This just means that you must flash this ROM over the stock ROM.
I have put together the following guide, based on my own experience, that will allow you to properly backup your stock rooted phone completely, properly flash the Darth Stalker ROM over the stock ROM, and make your WiFi work properly. I am using this device & this ROM as my "daily driver", and it works flawlessly.
If, for some reason, things go wrong and you manage to soft-brick your phone, you can re-flash the original MI1 ROM by following the procedures in this thread --> [ http://forum.xda-developers.com/showthread.php?t=2301259 ], which also lists download links for the Odin image file and all tools mentioned. Once your phone is recovered, simply re-root it and install SafeStrap in order to completely restore it to pre-flash condition (right down to the wallpaper) using the nandroid backup i will show you how to create.
INSTRUCTIONS TO PROPERLY FLASH DARTH STALKER v9 ON THE i545 VERIZON/ GALAXY S4:
1. This guide assumes that you have brought your Galaxy S4 up to the I545VRUDMI1 baseband version. If you have upgraded past that, there is no way to do this at the present time.
2. Follow the procedute outlined in the this Forum thread --> [ http://forum.xda-developers.com/showthread.php?t=2487142 ] to "ROOT" your Galaxy S4.
3. Once you have successfully rooted your Galaxy S4, you can now begin to convert your phone over to one of these GSM carriers, and use a much less expensive GoPhone or StraightTalk SIM card.
4. Go here --> [ http://forum.xda-developers.com/devdb/project/dl/?id=991 ] to download SafeStrap custom recovery, version 3.62. Once you have downloaded it, copy it to your phone's SD card.
5. Go here --> [ http://forum.xda-developers.com/showthread.php?t=2292054 ] to download the Darth Stalker ROM that supports multi-carrier operation very well. Once you have downloaded it, copy it to your phone's SD card.
6. Go here --> [ http://forum.xda-developers.com/devdb/project/dl/?id=1342 ] to download the modules that must be added to make WiFi work on the I545 version of the Galaxy S4; the developer did not add them into version 9 of Darth Stalker, but it is easy to do. Once you have downloaded it, copy it to your phone's SD card.
7. On your phone, tap your way to "Settings -> Security -> Unknown Sources", and make sure that it is checked/ enabled.
8. Now that you have all of these ZIP files on your phone's SD card, you have allowed it to install from the SD card, and your phone has been successfully rooted, bring up your phone's file manager.
9. Navigate to your external SD card, and tap on the green shield icon to install SafeStrap. Once it finishes installing, tap "Open", then tap "Install Recovery". Once it is finished, tap the new button for "Reboot Into Recovery" and let your phone reboot into SafeStrap Recovery.
10. Once you are in SafeStrap, tap on "Backup"; make sure that "Data", "Cache" and "System" are all checked, and that the storage location is set for your external SD card (DO NOT PUT THIS BACKUP ON YOUR INTERNAL STORAGE!!!). Then swipe to start the backup. This is referred to as a "nandroid backup" and you can recover your entire phone as it exists at that point from it. Let it work -- it should take around 10-15 minutes.
11. Once you have your backup done, tap "Back" to return to the main menu. You will see, in red at the top of the window, that you are working with the Stock Rom slot -- DO NOT CHANGE IT -- that is what we intend to do.
12. From the main menu, tap "Install", then select your external SD card in the Storage field; then scroll down to "DARTHSTALKER_S4_V9.zip" and tap on it. Swipe the button to begin flashing this ROM.
13. In a few seconds, the Aroma Installer will start up which will allow you to specify what features you want in your ROM. Make sure you follow these "bullet points" from the developer, jovy23 [ http://forum.xda-developers.com/member.php?u=4454815 ] -- it matters!
* Choose The "Full Wipe" Method.
* Choose Any Of The Apps You Want.
* Now Install The Rom Until Its Finished.
* The Aroma Installer Will Then Reboot Your Device.
* Once Rebooted And In The Setup Wizard, DO NOT Touch For 5 Minutes!
* After 5 Minutes, Reboot The Phone... ALMOST DONE!
14. Once you have finished installation, and your phone is working (all except WiFi), you will need to re-install SafeStrap from your SD card. This is a quirk of the stock MI1 bootloader, but can be worked around. Simply re-install SafeStrap when it disappears. Once you have SafeStrap Recovery installed again, reboot your phone into recovery directly from SafeStrap -- DO NOT USE THE PHONE REBOOT MENU TO REBOOT INTO RECOVERY.
15. You will repeat the process you used in originally flashing the ROM, but instead, this time you will flash the file jfltevzw-MI1-modules.zip that is on your external SD card.
16. When flashing is done, tap on the "Wipe Cache/Dalvik" button to clean up and make the kernel recognize the new modules when it loads.
17. Reboot your phone.
18. Once your phone comes up, you will now have WiFi. Enjoy!
Warning: I cannot be held responsible for anything you do to your phone. Anything you do to your phone is your responsibility. I am simply giving your the benefit of my experience in this guide, and I cannot help it if you don't follow it exactly.
Mms and everything works fine?
Sent From The Future
killajoe said:
Mms and everything works fine?
Sent From The Future
Click to expand...
Click to collapse
Yep -- everything works great...
budding_developer said:
Yep -- everything works great...
Click to expand...
Click to collapse
My stock TW VZW Galaxy S4 works wonderfully on T-mobile and AT&T out of the box with a few APN settings added.
joderme said:
My stock TW VZW Galaxy S4 works wonderfully on T-mobile and AT&T out of the box with a few APN settings added.
Click to expand...
Click to collapse
That's curious -- mine would show the APN's with an activated SIM, but no signal whatsoever. This is what I had to do to use anything other than Verizon's CDMA here in the US. I was told that Verizon locks out the US GSM frequencies in their kernel so that you can use GSM outside of the country only.
budding_developer said:
That's curious -- mine would show the APN's with an activated SIM, but no signal whatsoever. This is what I had to do to use anything other than Verizon's CDMA here in the US. I was told that Verizon locks out the US GSM frequencies in their kernel so that you can use GSM outside of the country only.
Click to expand...
Click to collapse
I wonder if something changed in the later updates. As of MDK/ME7 it was working. I was able to get AT&T HSDPA after putting in the APN data. Voice worked without any of that.
As a part of their 700 Mhz spectrum agreement they had to be sim unlocked. My wife is using a VZW iPhone with an AT&T sim without problem. Did you see any sort of signal when you had the sim in (no data indicators, just signal bars)?
Anyone try stock MDK ROM and MJ7 Modem on ATT or Prepaid ATT with LTE active? Is this possible? In service mode I see both Band 17 and Band 20 as new selectables when updated to the MJ7 Modem
My 2 cents
unlocked out of the box
the sch-i545 is unlocked out of the box. no mod required. the only issue i have with AT&T is caller ID formatting has a + in front. Otherwise once with APN added, it works fine and able to get HSPA+
joderme said:
I wonder if something changed in the later updates. As of MDK/ME7 it was working. I was able to get AT&T HSDPA after putting in the APN data. Voice worked without any of that.
As a part of their 700 Mhz spectrum agreement they had to be sim unlocked. My wife is using a VZW iPhone with an AT&T sim without problem. Did you see any sort of signal when you had the sim in (no data indicators, just signal bars)?
Click to expand...
Click to collapse
No -- no bars at all -- just an empty triangle. I would get the occasional flashing small triangle just above the signal indicator (searching for data, I believe), but the bars would never show. About half the time, I would get a red "NO" circle over the indicator, too.
As soon as I flashed Darth Stalker, though, it glommed onto signal & data lickety-split. I'm happy with it now -- in fact, I did a second one and sent it to my girlfriend in New York.
equake said:
Anyone try stock MDK ROM and MJ7 Modem on ATT or Prepaid ATT with LTE active? Is this possible? In service mode I see both Band 17 and Band 20 as new selectables when updated to the MJ7 Modem
My 2 cents
Click to expand...
Click to collapse
Before I left Verizon, while it was still on MI1, I flashed the MJ7 radios -- it virtually killed my transfer speeds. Went from almost 20 mbps to less than 10.
I've been through allot of this trial and error as I've always used GSM services in the past and before my S4 used a Verizon Note 2 with Straight Talk "AT&T". I got lucky and got an MDK and I've helped a friend with an ME7 on same service.. so I've worked with them both. What I found right away was that the Verizon CyanogenMod builds do not work properly with GSM phone service properly.. then I got a tip and made a custom VZW loki'd ATT recovery and started flashing the i337 CM ROMs and everything worked perfect from that point on.. I still have to do some work swapping files around when I want to run custom kernels.. not sure why most of the devs decide to pre-patch the kernel images instead of loki patching them during the recovery flash process as this would make a universal VZW/ATT kernel.. but it works non-the-less. As for the ME7 i545, the stock rom worked as long as you selected global mode but you'd still get the non-verizon sim error. Used SS with the GE 4.2.2 ROM and it works perfect with his GSM service.
budding_developer said:
Before I left Verizon, while it was still on MI1, I flashed the MJ7 radios -- it virtually killed my transfer speeds. Went from almost 20 mbps to less than 10.
Click to expand...
Click to collapse
Is this on LTE or did it drop back down to HSPA+?
equake said:
Is this on LTE or did it drop back down to HSPA+?
Click to expand...
Click to collapse
The radio flashing happened while it was still a CDMA/ Verizon phone, before I flashed Darth Stalker. It really cut my LTE speed. Flashed the original MI1 radios, and I got the speed back.
Now, with Darth Stalker, I am on HSPAP:15 or HSPA:11 but the indicator says 4g -- I get comparable throughput as I did on Verizon.
Anyone getting LTE on ATT or prepaid ATT like goPhone, StraightTalk, AIO with the MJ7 radio?
Guys I actually have un-used AT&T go phone sim card I need it for someone to simply remove activation on iPhone. I put it in my S4 VZW and it showed AT&T as service provide so you don't need to mess with custom roms.
patt2k said:
Guys I actually have un-used AT&T go phone sim card I need it for someone to simply remove activation on iPhone. I put it in my S4 VZW and it showed AT&T as service provide so you don't need to mess with custom roms.
Click to expand...
Click to collapse
Are you getting LTE with the goPhone SIM?
equake said:
Are you getting LTE with the goPhone SIM?
Click to expand...
Click to collapse
Don't know never activated it it was only used for few seconds with iPhone.
If it's a micro sim chances are it's not lte enabled.
Sent from my SCH-I545 using Tapatalk
CDMA SIM card
I have a CDMA SIM for 1x and EVDO here in India, we have been using GSM after the unlocking without any extra APN settings. Since the author has mentioned other networks, will this procedure help in using other CDMA SIMs in Verizon S4?
dr.faramroze said:
I have a CDMA SIM for 1x and EVDO here in India, we have been using GSM after the unlocking without any extra APN settings. Since the author has mentioned other networks, will this procedure help in using other CDMA SIMs in Verizon S4?
Click to expand...
Click to collapse
No, I think you misunderstood the nature of my original post. It was meant to illustrate how to get away from the high phone bills with Verizon here in the US -- since Verizon locks out all GSM US carriers in the RIL, you MUST replace the Verizon stock ROM in order to be able to use the Verizon phone on any US carrier which uses GSM technology.
You can still use foreign GSM carriers with the stock Verizon firmware, but there is no known method to "open up" the Verizon stock ROM for the use of the phone on US carriers on GSM -- many have tried, and everyone has failed. The only viable option is to completely replace the stock ROM and kernel -- which was the purpose of my "tutorial" here.
If you are in India, and you have a Verizon CDMA S4, you simply need to pop a SIM from a foreign GSM carrier into it in order to use GSM there -- you will NOT be able to use GSM here in the US, though, because of Verizon's lock-out logic contained in the RIL (Radio Interface Layer). I am not sure about the use of the Verizon US CDMA phone on foreign CDMA carriers, though.
Good evening all.
I flashed my S4 to Hyperrive 20 this week. ever since I have had no 4G access. 3G and 1X are no problem. I tried to modify APN but can't seem to add new APN's or modify existing. Even after enabling Dev Mode. So two questions.
First. Is there a fix for this? and if not, will flashing back to stock fix it?
Thanks in advance.
See the following link:
http://forum.xda-developers.com/showthread.php?t=2487298
Use Safestrap to flash the appropriate modem.
If that does not work flash the following file if you came from NC5:
https://www.androidfilehost.com/?fid=23486521113837640
or this file if you came from NK1:
https://www.androidfilehost.com/?fid=95832962473396366
When all else fails flash gogolies-wififix-VZW-retail-NC5-w-modules-SS.zip
https://www.androidfilehost.com/?fid=23487008491963692
rbird2 said:
See the following link:
http://forum.xda-developers.com/showthread.php?t=2487298
Use Safestrap to flash the appropriate modem.
If that does not work flash the following file if you came from NC5:
https://www.androidfilehost.com/?fid=23486521113837640
or this file if you came from NK1:
https://www.androidfilehost.com/?fid=95832962473396366
When all else fails flash gogolies-wififix-VZW-retail-NC5-w-modules-SS.zip
https://www.androidfilehost.com/?fid=23487008491963692
Click to expand...
Click to collapse
I guess talk to me like I'm 5 I am not a complete noob but I stopped rooting more than a year ago on my S3. No time for it anymore. This S4 was running CM 11 and was having the same problem. That's when I inherited from a friend that upgraded to the S5. I flashed Hyperdrive to try and fix wth no luck. I actually wouldn't mind going back to CM if I could 4g fixed. Right now the modem I545VRUAMDK. How do i find out what I came from? Or do i just start running through the list until it works?
Edit. I am on ClockworkMod Recovery 6.0.3.2
OK, perhaps you should try to restore it back to Factory new. If I run into a problem I can not fix, restoring a factory image will fix it.
You will need to download and unzip Odin 3.09:
https://www.androidfilehost.com/?fid=23321874045862094
Then take a look at the following XDA links:
http://forum.xda-developers.com/showthread.php?t=2776189
http://forum.xda-developers.com/showthread.php?t=2289325
Below is a link to an excellant video that explains how to use ODIN:
https://www.youtube.com/watch?v=GL8XwuRYoWU
Watch the video and follow the instructions.
rbird2 said:
OK, perhaps you should try to restore it back to Factory new. If I run into a problem I can not fix, restoring a factory image will fix it.
You will need to download and unzip Odin 3.09:
https://www.androidfilehost.com/?fid=23321874045862094
Then take a look at the following XDA links:
http://forum.xda-developers.com/showthread.php?t=2776189
http://forum.xda-developers.com/showthread.php?t=2289325
Below is a link to an excellant video that explains how to use ODIN:
https://www.youtube.com/watch?v=GL8XwuRYoWU
Watch the video and follow the instructions.
Click to expand...
Click to collapse
Thanks for your time.
I used Odin to get back to factory MDK. Still no 4g. OTA updates also will not install. They will download but install.
Well at this point I would remove the sim card and reinstall. If still no 4g, stop by a Verizon store and try a replacement sim card. You may have a bad one.
I have heard that if you try to dial *228 (Blocked with OEM Samsung Touchwiz ROM) you can destroy the sim card. If this was done, your sim card is defiantly bad.
rbird2 said:
Well at this point I would remove the sim card and reinstall. If still no 4g, stop by a Verizon store and try a replacement sim card. You may have a bad one.
I have heard that if you try to dial *228 (Blocked with OEM Samsung Touchwiz ROM) you can destroy the sim card. If this was done, your sim card is defiantly bad.
Click to expand...
Click to collapse
I ruled out the sim card. I put it in my wife's S4 and it got 4G. I took her card and put it in my S4 and no 4G. Definitely something in the OS I am thinking. I dd notice the APN settings don't match though. But I am unable to modify them on my stock S4.
Any other ideas? Now that I am back to stock is it worth contacting VZW? I am not sure they will be any real help.
I did a search of XDA and found the following:
From:
http://forum.xda-developers.com/showthread.php?t=2578569&page=2
Look at #18
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.http://forum.xda-developers.com/showthread.php?t=2487298
Looks like LTE bands are not supported until MJ7. My guess is that you will need to update the Modem.
http://forum.xda-developers.com/showthread.php?t=2487298
rbird2 said:
I did a search of XDA and found the following:
From:
http://forum.xda-developers.com/showthread.php?t=2578569&page=2
Look at #18
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.http://forum.xda-developers.com/showthread.php?t=2487298
Looks like LTE bands are not supported until MJ7. My guess is that you will need to update the Modem.
http://forum.xda-developers.com/showthread.php?t=2487298
Click to expand...
Click to collapse
I am back on CM11. Flashed several different modems from the link you provided. No luck.
I've been asked by lots of folks on how to convert the HTC 10 unlocked US version into a full-featured Verizon version so I figured i'd write an all encompassing guide on how to complete the process.
After following this guide, your phone will effectively be a fully-functioning Verizon variant. IMS, advanced calling, wifi calling and all other Verizon features will work flawlessly!
Note: I am purely compiling this information. I had no part in discovering this process, I simply followed multiple guides and other random posts on XDA to accomplish this! Credits go to @jcase, @beaups, @dottat, and any others that were involved with testing this process. Please make sure to thank these guys for the work they've done.
Step 1: Unlock bootloader and acquire s-off
In order to modify the CID/MID and change the radio, we must first acquire s-off. The easiest way to do this is to follow jcase's well-written guide.
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Move on to step 2 after finishing the above guide to completion.
Step 2: Change CID and MID
2a) Download this link, and extract into your directory of choice
https://www.androidfilehost.com/?fid=24545065934258327
2b) Boot your phone into download mode via the button combo (down + power) or by using adb reboot-bootloader with USB debugging turned on and then selecting download mode
2c) Issue the following command while in download mode:
Code:
htc_fastboot oem writecid VZW__001
2d) Issue the following command while in download mode:
Code:
htc_fastboot oem writemid 2PS650000
2e) Reboot phone back into download mode and verify the CID and MID have changed and are correct.
Step 3: Flash Verizon RUU to phone
Now that we have s-off, unlocked bootloader and the proper CID/MID on our device, now we just need the Verizon stock ROM and radio on our device. The Verizon RUU will handle both of these for us in a relatively hassle-free manner.
3a) Download the following .exe file to your local machine (big thanks to @dottat!)
Verizon Stock RUU exe (dottat)
3b) Boot phone into download mode (or Android OS w/ USB debugging enabled) and run the executable file
3c) Follow onscreen instructions and wait for process to finish
3d) Reboot phone (it may take a while to boot so BE PATIENT! mine took about 4-5 minutes if I recall)
After your phone boots, it will be a fully functioning Verizon phone. At this point, you can go activate your phone and it will work. You will be able to take Verizon official OTAs and it will behave identically to the true Verizon variant due to the RUU re-flashing stock recovery and an unmodified system.
OPTIONAL -- Step 4: Re-root phone
The RUU that you deployed on your phone was an unrooted system image with stock recovery. In order to get root back, you will need to re-do steps 1-10 in jcases's Root/s-off guide from step 1.
Here's the link again in case you're too lazy to scroll back up
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Reminder: your phone already has s-off so you ONLY NEED TO DO STEPS 1-10! Running Sunshine again will likely just report that your phone already has s-off so no worries if you accidentally do the entire guide again.
Step 5: Activate your phone
This step can be very straightforward or a moderate pain the ass depending on what you have available to you.
There are two ways to activate the HTC 10 now that it's running stock Verizon firmware/software:
1) Pop an existing, activated nano-SIM with your current phone number on it in the device and reboot. Voila!
2) Take your device to a Verizon store and convince the employee that your phone is in fact, a true Verizon phone.
I would highly suggest using an already active nano-SIM if you have that available. I, unfortunately, did not as I was coming from the Verizon LG G4. I had to go three different Verizon stores to convince them to finally activate the device. Your IMEI on your unlocked 10 will not show up in Verizon's IMEI database. The store clerk actually had to pull an IMEI from a display model HTC 10 so that she could get the nano-SIM activated for my 10.
noahjk said:
Good post! I think you're looking for this link: http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
Click to expand...
Click to collapse
Good catch, thanks. I updated the links.
Tried this twice, both times my phone gets stuck on 'Preparing your phone...' after flashing and rebooting on the setup wizard.
edit: worked fine after removing SIM. Run through the setup without SIM for anybody having issues. I know this isn't explicitly stated in OP but if you're having issues, make sure you try this.
If anyone is having connection issues after putting in your SIM, you have to change your Preferred Network mode from Global to LTE/CDMA.
Other than that, everything's working great! Even comes with free VZW bloatware
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
codelinx said:
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
Click to expand...
Click to collapse
Haven't seen that before. What did you do to setup your Hotspot?
DoctorB0NG said:
Haven't seen that before. What did you do to setup your Hotspot?
Click to expand...
Click to collapse
That error would be the ota downloader.. what anything frozen I would ask the person who posted
Sent from my HTC6545LVW using Tapatalk
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Zooks97 said:
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Click to expand...
Click to collapse
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Looks like all the stock information, RUUs, roms, and recoveries are here.
Has the MID/CID for stock there as well. Hope this makes it into the OP.
When I have access to a desktop/laptop I'll update the guide. Thanks for the suggestions.
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
hunteditor said:
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
Click to expand...
Click to collapse
Yep that's the fix. The vzw ruu does not wipe.
Sent from my HTC6545LVW using Tapatalk
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Did you pick up a 10 yet?
aer0zer0 said:
Did you pick up a 10 yet?
Click to expand...
Click to collapse
I did.
It's prepared to be sent to Mr. @beaups when they are back doing devices again on May 22nd.
(In my signature below, in green are the devices I currently own, and the ones striked out are previous devices I had but are sold).
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Light1984 said:
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Click to expand...
Click to collapse
Did you activate those features on your account using the menu on the phone?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Did you activate those features on your account using the menu on the phone?
Click to expand...
Click to collapse
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Light1984 said:
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Click to expand...
Click to collapse
Take some screen shots.
Sent from my HTC6545LVW using Tapatalk
Here is my advanced calling menu with Wi-Fi calling now showing up. Haven't tested, but it seemed to let me set it up. I have Wi-Fi tether enabled via default.xml edits. The one feature I'd really like is LTE on call. Had this without problem on my M7 but I think thats because it had multiple radios and didn't have to share a radio while on call. My noob guess anyways.
Maybe it's a setting in the hidden dialer menu *#*#4636#*#*? However, when I enter that into the dialer, nothing happens, the entered numbers just disappear and nothing happens. Thoughts?
Hello,
Backstory:
So here's the deal. My provider (Virgin Mobile Data Done Right) changed my phone number, and asked me to update PRL to make it work again.
I don't have a working stockrom backup - neither does anyone else. Neither does Kies, I've spent over two weeks researching this and working with various intermediate developers so don't even go there. I just want to work on making a custom rom do the PRL update.
It seems the easiest way to do this is simply to inject all needed files into the custom rom, but so far I've not had any success in finding the working files.
Things that are not solutions:
1) Flashing System via Odin or Hiemdall, multiple people including myself can confirm that Virgin has somehow blocked this method.
2) Flashing stockrom or Touchwiz KitKat via TWRP (anything below 5.1 lolipop fails to boot, gets caught in hard loop).
(On top of that, you loose baseband because no one on planet earth has a Virgin Mobile Data Done Right tri-band phone. It's a rare OH1 modem. I was fortunate enough to make a backup of modem.bin, before running flash attempts overtop of my custom rom. No thanks to the many fools who told me otherwise)
3) Paying developers to fix the issue. I gave one a brand new phone and another a few bucks, neither of them know how to fix it.
4) Giving up.
Developer Info Needed:
So what I'm looking for is people experienced with HiddenMenu.apk that can give me some tips to get it working on d2refreshspr (Triband) OctOS-L. OctOS-MM does NOT work, never did. OctOS is very aware of the issue but they are probably just as clueless at this point and aren't interested in putting proprietary blobs in their rom. People like @digiblur who have all but decompiled the thing would probably know how it works.
To my knowledge, I need to find the following files:
OmaDmclient.apk
UpdateSettings.apk
HiddenMenu.apk
These files have to be able to run on Lolipop, and they have to be branded for Sprint, preferably for the Galaxy S3 triband, but I'm not sure it exists so well have to make do. I tried injecting the packages from some older KitKat roms and they crash.
Once again, the only rom that ever worked properly on this phone is custom rom OctOS-L, so others are not an option.
Alright devs, let me know some tricks! No noobs.
I have located the stock Sprint KitKat version of HiddenMenu for the S3 tri-band. Unfortunately, I have been unable to execute it on the custom rom as of yet. It does not appear in any of the activity launchers, and the dial-code is not working. I've manually put this into /system/app/HiddenMenu/HiddenMenu.apk
APK for reference:
http://www.fileconvoy.com/dfl.php?id=g8fd96be733233c149998319870a8759deb41050a7
SHA512: dc9a5e06200637da2b1e5c71d16af239a80fa44f7067ab83efa45ac59b9df0016de2b99d97e0cfc023a3ac4be91d4dd6f945303c2184d5232476f0c445440d55 HiddenMenu.apk.zip
- Pulled from:
L710TVPU0AOH1_L710TSPT0AOH1_L710TVPU0AOH1_HOME.tar.gz --> system.img.ext4
(Note that this LT710T Odin dump foolishly contains the NF4 modem, NOT the OH1 as it's name implies)
Without anyone's help, I will continue to google this endless endeavor. :good:
Ran apktool on this thing. Inside the apk of the HiddenMenu it mentions the NF4 variant. Not sure if this is why it's not working or not.
Also tried recompiling it by changing AndroidManifest.xml to add android.intent.category.LAUNCHER as an option so that it appears.
No love. I can't get HiddenMenu to come up.
Ideas?
For anyone encountering this issue. I never got HiddenMenu to work. Not even on a TouchWiz rom, but I found another way.
Look here: http://forum.xda-developers.com/showpost.php?p=67026377&postcount=6
This was way more complex than it should be. Proprietary APK makers should be ashamed.