Rooting/Transforming my SM-G900V for Australian Telstra Use - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Hello all!
Got a few questions I'd like some help from everybody to figure out please! Here's a basic summary of my problem:
Recently moved down to Queensland, Australia, and had a friend from the US ship me a Verizon Samsung Galaxy S5 (SM-G900V), on account of phones being super expensive down here. Received the phone, put in my Telstra SIM card, and altered the APN Settings, and got the phone working properly, no problems with it really.
However, I'd love to root the phone in order to hopefully upgrade the Android OS from 5.0 to something newer. There's a couple little features I'd also like to get rid of, which I imagine would be possible upon successfully rooting the phone:
- On the Notifications Panel, there is a permanent Notification that reads: "SIM card is not from Verizon Wireless." (I would love to remove this).
- All of the Verizon Apps from my Apps Menu.
If I were to root it, is there anyway I could install the Telstra based OS, or a network unrestricted OS, that wouldn't have all of the unwanted apps in the Application Menu?
In a nutshell, what I'm requesting help for, is in order to root my phone and get an updated OS (hopefully), without having to use a Custom ROM? Although I'm not completely against using a Custom ROM.
Thanks in advance.

Bump....Somebody please help me...I'm having trouble even installing the recovery. ODIN will start the process of installing the custom recovery to the phone, then will fail within 5 seconds...

Related

AT&T Now Bricks Modded Galaxy Tabs

What used to be a simple patch to permit AT&T Galaxy Tabs to download apps from sites other than the Google Market is no more. We recently got our Tab back from the Samsung repair facility and it was wiped clean and loaded with a new Android version that now puts your Tab in an endless boot loop if you attempt to patch the config setup to permit downloads from outside Google Market.
Simple solution: DON'T BUY AT&T-BRANDED GALAXY TABS.
If there were some sort of unlimited data plan, this kind of behavior might be warranted but since AT&T charges by the amount of data you consume, there's really no excuse for crippling these devices... other than just being assholes!
Not entirely sure what you're referring to here. I have an AT&T SGT and it works just fine with sideloaded apps.
Did you run SuperOneClick root and then enable non-market apps?
Either way, nuke that horrid stock ROM with one of the Euro roms and you'll never have to worry about AT&T's crippled version again.
Yeah, but...
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
What version of firmware did your Tab come back with?
What method did you attempt to enable side loading?
I find this very hard to believe because every single ATT Android device to date has been able to side load after a simple 1 bit edit of the device settings db.
I believe that you had problems with the SuperOneClick app but there is a much cleaner / safer way to do it.
Sent from my SGH-I987 using Tapatalk
NerdUno said:
There still are a number of ways to root the phone, but the new checksummed firmware will make it extremely difficult to load custom roms with any hope of restoring an earlier firmware version. And, once you update your current version of Android, using the standard method of allowing non-market apps by changing the non-market apps entry in /dbdata/databases/com.android.providers.settings/settings.db will put the device into an endless boot loop when you restart it.
So, while it used to be simple, those days are over. No need to shoot the messenger.
Click to expand...
Click to collapse
I don't believe my ATT SGT came with a protected bootloader, and if I'm not mistaken, AT&T hasn't released any firmware updates via KIES or OTA. So while there's always the possibility of Samsung "screwing" us all with that mess, it's only been seen on the leaked firmwares. Not that I don't put it past the big blue DeathStar to opt to use something like that to prevent people from avoiding their preloaded garbage....
I'm happy I liberated my device from the clutches of the Evil Empire, and will gladly look to XDA for my future upgrade paths.
Could just be a bad software flash from factory. A number of t-mobile vibrants couldn't get to restore via volume up/down power because of a buggy flash file they put on a certain build date
Sent from my Galaxy Tab

[Q] LG Quantum still has not received mango

Still have not received the mango update. I've been searching and researching this issue for more than 4 months with no luck.
When connecting to zune, it says my phone is up to date with current software version: 7.0 (7392)
i have tried the "walshed" phone fix but that was not the issue.
also, the phone doesnt seem to have full functionality with WPDM and whenever i try and install a .xap file, the application wont launch after being installed on my phone.
the reason i am this desperate is because i want to back up all of my text messages on this phone. my mother passed away recently and it would means a great deal to me that i keep those conversations. if i am able to do this without installing mango, then that is fine by me.
my logic in installing mango is that all of the latest apps such as smsbackup require an unlocked mango device.
i have tried installing WP7 Root Tools so that smsbackup is able to operate on this lg device.
any input would be greatly appreciated, thank you in advance
mmoustafa111 said:
Still have not received the mango update. I've been searching and researching this issue for more than 4 months with no luck.
When connecting to zune, it says my phone is up to date with current software version: 7.0 (7392)
i have tried the "walshed" phone fix but that was not the issue.
also, the phone doesnt seem to have full functionality with WPDM and whenever i try and install a .xap file, the application wont launch after being installed on my phone.
the reason i am this desperate is because i want to back up all of my text messages on this phone. my mother passed away recently and it would means a great deal to me that i keep those conversations. if i am able to do this without installing mango, then that is fine by me.
my logic in installing mango is that all of the latest apps such as smsbackup require an unlocked mango device.
i have tried installing WP7 Root Tools so that smsbackup is able to operate on this lg device.
any input would be greatly appreciated, thank you in advance
Click to expand...
Click to collapse
To backup all SMS and all messages in Messages tile, use SMSBackup. Then try to flash your phone with Telstra ROM, here is the guide.
Note #1: Your phone must be network unlocked first before flashing because you might not be able to enter unlock code once you flashed it to Telstra ROM. The only solution is re-flash to its original ROM then enter unlock code then flash it to Telstra ROM again. You can buy unlock in Ebay.com and price is as cheap as chip.
Note #2: The reason that I suggested Telstra ROM is because it is the only network that give the latest Mango update for LG Quantum, but no sign of Tango.

[Q] Advice req'd

OK so I recently got my hands on an S4 (GT-I9505). This is an upgrade from my previous phone that was stolen; I had an S3 with CM11 installed. So as I have enjoyed CM11 previously I would like to use it on my new S4. I have a few questions:
Is the default boot-loader locked? What alternatives exist for this device?
If I root and install a custom boot-loader, would I be able to replace it later if I wanted to?
Broad question, but what security features does Cyanogenmod come with?
Is there a stock CM phone location service built in to the OS, i.e. like a tracker?
Can I encrypt the device storage with CM11 without installing apps to do this?
Can I encrypt the removable storage without installing apps to do this?
How do I restrict USB mounting of the media folders on the phone/removable media to a specific machine?
Can I restrict access to the ADB via USB to a specific machine only?
The stock recovery menu states CTC code applied "BTU" (I'm in the UK). Does the bootloader apply this setting so the phone knows which region to operate in and if so does the CWM boot-loader also apply this code too (I don't want to run into problems after where the phone won't associate to a network due to some issue with CTC, or maybe I've misunderstood this concept...) ?
I know, dumb questions eh.
You have more than a few questions there. :lol:
The only S4 devices that have locked bootloaders are ones purchased from the United States cellular carriers AT&T and Verizon. Current bootloader code includes Knox security software, which is not found on the SIII.
You don't install a custom bootloader. Custom kernels and recoveries can be easily restored to stock using Odin.
Your questions regarding CyanogenMod I can't answer, as I don't use CyanogenMod.
Encrypting the removable storage may be possible, but it varies from ROM to ROM. You'll have to read up on the ROM you choose to use.
AFAIK, you can't restrict mounting of media folders.
You cannot restrict access to ADB to one specific machine.
The bootloader has nothing to do with the CSC code. Where you're planning on installing a custom ROM it won't matter anyway.
The only stupid questions are the ones that aren't asked. But, most of this information applies to the SIII as well. Surely you had to have been aware of some of it, as the two devices really aren't that different when you get right down to it.
Thanks for your feedback.

Question about 6.0.1 Update for Verizon S5 that is on Straight Talk

Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?

OK2 Carrier Unlock & ROM Questions

I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
natenkiki2004 said:
I've got a S4 AT&T running OK2 with root and it ran my AirVoice Wireless SIM perfectly fine for a month while I researched and got a new phone. I'd now like to use it as a backup phone with a FreedomPOP SIM but it's giving me grief about "SIM network unlock PIN". This is the carrier lock correct? I found a tutorial that has you go into the Service Mode and turn off NETWORK LOCK. This tutorial doesn't seem to work (missing the options) in OK2. Do I have to downflash to 4.2.2 in order to get these options? If so, how do I go about doing that? I put OK2 with root on this phone but that process took 2 days and with all the mixed info out there and different versions, it's confusing to say the least.
My other question is, I tried flashing TWRP (jflteatt) and I believe I ended up with the "software not authorized by AT&T" error. Doing some reading, it looks like this may be due to not using a loki'd TWRP?
Any pointers/tips would be much appreciated. All this Samsung stuff is way over my head despite having rooted, recoveried and rom'd maybe a dozen Android devices. I much prefer LG and Moto
Click to expand...
Click to collapse
Yeah you're carrier locked. I think you can only downgrade to NB1 from OK2, not sure you can carrier unlock on NB1 or not. As for installing TWRP you can't due to the locked bootloader. You can only use safe strap recovery and boot only custom touch wiz roms. Loki only works on the MDB and MDL bootloaders, once you've upgraded the bootloader past MDL, you can't go back.
If the AT&T phone is like the i337m and m919, you may be able to flash down to 4.4.2, flash a 4.2.2 modem, root, run regionlockaway, upgrade modem back to 4.4.2.
Thanks for the replies. I grabbed NB1 from here: https://forum.xda-developers.com/showthread.php?t=2616221
and flashed it via Odin. All went well but when it came time to follow various instructions I found online, they either yielded no unlock or the options weren't in the menu. I don't think the free unlock trick via the service menu works on 4.4.2/NB1.
I researched a bit more and feel very stupid with one of the results that came up... AT&T offers online unlocking of their devices and you don't even have to be one of their customers! I figured I could go to one of their retail stores but also figured they would deny me since I'm not a customer. I'll be jiggered though, here it is: https://www.att.com/deviceunlock/
Slapped my IEMI in with my e-mail and in less than an hour or so, I got my unlock code for free. AT&T said they would e-mail it but I checked back on the status page and found the code there. Hopefully this helps other people.
So, moving forward now, is OK2 the best I can do with a locked bootloader? I ran it for a while but I found that I burned through my data real quick because when I would leave my WiFi coverage and come back, it would reconnect but for some reason wouldn't actually use WiFi (data was still on, had the 4G icon) until I restarted the phone. Basically, every time I left and came back home, I had to restart my phone. Is this a known issue, did I botch something in the install process? I may make another thread for this.
*EDIT*
Running OK2 for a while, I no longer have the WiFi issues I had before. Doing some thinking, I can only attribute the issue to either incorrectly followed steps the first time around flashing OK2 or the use of the debloater script found in the OK2 downloads thread. I've been using Link2SD to remove system apps and so far haven't removed anything that has affected WiFi.

Categories

Resources