Related
So... I'm about to get a new S6 for Verizon. There's pretty limited info in this thread, but a lot of it seems like a new S6(as of 10/01/2015) isn't rootable/ROMable because of the most recent OTA that I would assume would be on a phone bought now. Is that correct? If not can someone point me to threads that show how to root and get a custom recovery on?
Thanks,
Craig
Correct. You will not be able to root the new s6 unfortunately. You can likely buy one on swappa that hasn't been updated and is running fireflash or whatever.
Sent from my SM-G925V using XDA Free mobile app
.....unless you get lucky and get a phone with OC3 or OE2. Verizon just sent me a replacement S6 (was having major BT issues) and I got lucky enough to get one on OC3. S6 + OE2 + root + greenify = me happy :laugh:
Software out-of-the-box
csh8428 said:
So... I'm about to get a new S6 for Verizon. There's pretty limited info in this thread, but a lot of it seems like a new S6(as of 10/01/2015) isn't rootable/ROMable because of the most recent OTA that I would assume would be on a phone bought now. Is that correct? If not can someone point me to threads that show how to root and get a custom recovery on?
Thanks,
Craig
Click to expand...
Click to collapse
Were you able to get a new S6 from Verizon with either OC3 or OE2, if so which one? I am interested in getting it too, but it's a no go if root is not possible.
NSRacer said:
.....unless you get lucky and get a phone with OC3 or OE2. Verizon just sent me a replacement S6 (was having major BT issues) and I got lucky enough to get one on OC3. S6 + OE2 + root + greenify = me happy :laugh:
Click to expand...
Click to collapse
I'm worried that if I get a new S6 from verizon it will auto-update to 5.1.1 OG5 during the initial setup wizard/process. Can you explain how you stopped yours from updating to OE2 and OG5? Thanks in advance
The device won't auto-update itself without consent from the user. My replacement came with OC3, so I pulled down OE2 (from the web) and pushed that to the phone using ODIN. Once that was done, I applied root which prevents the phone from receiving OTA updates.
NSRacer said:
The device won't auto-update itself without consent from the user. My replacement came with OC3, so I pulled down OE2 (from the web) and pushed that to the phone using ODIN. Once that was done, I applied root which prevents the phone from receiving OTA updates.
Click to expand...
Click to collapse
Thanks for the info! I went in to a verizon the other day and their answers were all over the place; it's amazing how they know so little about the devices they spend all day selling, servicing. They tried to tell me that a mandatory update came out Friday "for all verizon android phones" and the play store wouldn't work if it wasn't updated to it (though they told me also that the user has no choice to reject updates - lol)
NSRacer said:
The device won't auto-update itself without consent from the user. My replacement came with OC3, so I pulled down OE2 (from the web) and pushed that to the phone using ODIN. Once that was done, I applied root which prevents the phone from receiving OTA updates.
Click to expand...
Click to collapse
I got my s6 from someone on swappa and for some reason, once I first booted and was doing initial setup, the phone automatically rebooted into update mode. As soon as it was back up and running, the build version was too new to root and the bootloader version had been updated too. I don't know why it did this for me, I was really tempted to hard reboot while it was in update mode to prevent it because I really wanted to root, but I was even more worried about bricking the phone. I figure maybe the guy who sold it to me had already downloaded the update but did not run it, and after doing a factory reset maybe the phone was somehow set to auto-execute the update...
I recently bought a verizon Pixel and have already unlocked the bootloader and flashed a stock image NDE63V that comes directly from google. I'm using it on T-Mobile. If I relock the bootloader at this point will everything be ok? I've read something about people saying it would brick the phone if you relock after flashing unsigned code, but the official stock images from google are signed. Will I get official updates for the unlocked google store version of the Pixel?
-edit- I decided to live dangerously, re-locked the bootloader, and now I have a completely stock google store pixel
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
brainymd said:
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't think anyone knows. Right now I flashed stock google ROM through fastboot which replaced bootloader image, I am using it with T-Mobile, and I relocked bootloader. I'm going to assume it would get stock google updates.
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
I also have a Verizon version. Is there an advantage to flashing the Google version of updates as opposed to Verizon? For the moment I have an unlocked bootloader with TWRP and SuperSU installed. I tried installing an OTA update and it failed.
If I want to install one of the image updates posted (such as NDE63X from Verizon available right now) do I need to run the "flash-all" script? Could I just flash system or something else? Or should I expect it to overwrite my custom recovery and I'll have to restore that?
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
mruno said:
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
Click to expand...
Click to collapse
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
ohioDroid said:
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
Click to expand...
Click to collapse
If the gestures were not in that update, they should be soon in an upcoming OTA according to reports. I am currently using the double-tap gesture with the ElementalX kernel (enabled within its app).
Edit: I think this app can enable lift to wake. I bookmarked it after finding a post about it here until I read Google will be adding this feature soon.
fink.nottle said:
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
Click to expand...
Click to collapse
I am not sure as I haven't had a nexus device since the Samsung Galaxy Nexus on Verizon .
On a lot of their devices Verizon likes to update bootloaders to only accept new updates. It's likely that if they patch out the ability to use dePixel8 in a future update, they will prevent people from flashing older builds. C'Est la Vie I guess
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
aholeinthewor1d said:
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Click to expand...
Click to collapse
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
tobalaz said:
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
Click to expand...
Click to collapse
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
jmartin72 said:
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
Click to expand...
Click to collapse
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I bought my Verizon Pixel yesterday. Unlocked in 20 seconds and within a few minutes TWRP 3.0.2-0 for sailfish is installed and SuperSU 2.78-SR5 has been flashed. Works perfect.
aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I feel your pain! I'm also coming from the S5 for 2.5 years. Had everything (almost) perfect with systemless root, twrp, xposed, adaway, etc. (but no Android Pay) . Now with this Pixel and Verizon-depixel8 unlocked bootloader, I'm trying to piece together the best plan for having the most stuff working.
So far, bootloader unlocked, and I flashed the full 7.1.1 images from Google. Then I tried using the setup wizard and it brought over my account info and wifi passwords and such from my S5 by directly connecting the phones, and it downloaded my apps from google play, but I need app-data.
So, now I'm thinking this would be the process if you want to have a rooted pixel, and be able to reboot into a "clean" boot for Android Pay?:
1) boot TWRP alpha2 (since RC1 having problem rooting?)
2) install TWRP alpha2 zip
3) install stock-safetynet kernal to boot_a
4) boot into boot_a
5) setup Android pay, add credit cards, etc.
6) boot into TWRP and install root with SR5 to boot_b
7) boot into boot_b and restore other app backups with Titanium Backup, install Adaway/hosts
8) no Xprivacy /Xposed available yet, right?
9) restore backed up apps from old phone with Titanium Backup (from cloud, etc.)
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
bobhinkle said:
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you can still use it on Verizon. Advanced Calling is a feature i am not too familiar with. Is that HD Calling? If so then yes that will work as well works on my phone without issue.
So from here I can flash Google's bootloader and Google image and then when updates come out just use the Google ones
Sent from my Pixel using XDA-Developers mobile app
Question for those with a Play store version of the Pixel: what is your bootloader version on the 7.1.1 software?
For reference my Verizon store Pixel has BL version 8996-12001-1610061102.
Thanks in advance!
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Benno81 said:
im sorry if this is in the wrong section but ,ok so i bought an open box galaxy s6 from becetech online and it would not let me update the firmware past 5.1.1 which made me a bit suss, downloaded root checker app and it came too me rooted. apart from not being able to update the firmware past 5.1.1 as far as im aware the phone has no issues and works perfectly fine. i downloaded the *samsung* phone info app, in general under manufacturer it says Samsung/verizon so im assuming that is part of the reason they rooted the phone as it needed to be unlocked from verizon to be refurbished? so what i want to know is how do i find out exactly what becetech have done to the phone and is there an easy way for me to update the firmware to nougat or at least marshmallow without stuffing the phone, like i said the phones running fine its just really bugging me not being to update. obviously im not able to work it out myself but i can follow instructions so any help from someone would be greatly appreciated so thank you in advance.
Click to expand...
Click to collapse
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Benno81 said:
Could someone with a bit more knowledge please tell me if the reason I can't update the firmware is because the firmware csc is TGY when I'm in Australia or just because it's rooted or what? I'm getting no answers from the company who I bought it off
Click to expand...
Click to collapse
Are you trying to update via the phone update feature? If so this won't work as rooting disabled the ability Update using ota
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Benno81 said:
First I tried OTA then downloaded samsung smart switch and gave that a go both no good. What I want to know is, if they had to root the phone to refurbish it will it brick it if I try to update? Won't it reset all the company I bought it off has done to it to refurbish it? Which I'm guessing is quite a process as when I look at the open source licenses there's a long list of files that have been changed. It just sucks that it's locked to a three year old version of the firmware that I'm worried apps will start to stop supporting in the near future? Apart from that I can not fault the phone there's been no problems, maybe I'm asking a bit much for a $400 phone?
Click to expand...
Click to collapse
From what I can tell you have a g920v variant if the phone Shows Verizon but the sure fire way to know what variant you have is turn the phone off once off hold home-power-volume down, this will take you to download mode but should tell you your variant. You don't need to root a phone to refurbish It, you can flash Stock firmwares via Odin. I really don't know why they would have Rooted It tbh, you'd need to contact them, but I know for sure you can manually download the latest Verizon firmware and the phone should work. Maybe they Rooted it as part of making it network unlocked, o really can't say
Ok I tried that and a bright blue screen came up warning about custom OS then press up volume for download and down volume for reset? I just pressed down as there was no other info on the screen but it does say it's a sm-g920v in the settings as well as the root checker app. Another thing was I did ring samsung support gave them the serial number and IMEI and they said an authorized modification had been done on the phone but could offer no other support as it wasn't an Australian phone. I'll keep trying to get some info out of the company I bought it off and try to sort it out thanks for your help :good:
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
LodeUnknown said:
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
Click to expand...
Click to collapse
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
*Detection* said:
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
Click to expand...
Click to collapse
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
LodeUnknown said:
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
Click to expand...
Click to collapse
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
*Detection* said:
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
Click to expand...
Click to collapse
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
LodeUnknown said:
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
Click to expand...
Click to collapse
If your phone is a US model S7 (snapdragon) you cannot flash custom ROMs
My instructions are for ODIN (version 3.12.7 for Nougat)
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
LodeUnknown said:
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
Click to expand...
Click to collapse
You cannot flash a custom ROM to a snapdragon phone using any method, it has a locked bootloader
ODIN is for stock ROMs only (and TWRP recovery which you cannot use on snapdragon either)
You can use ODIN on any S7 for stock ROMs
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
LodeUnknown said:
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
Click to expand...
Click to collapse
Yes, only Exynos has an unlocked bootloader (See the snapdragon vs exynos custom ROM dev forums)
Yes you could still use a US carrier as long as the phone is SIM unlocked (carphone warehouse phones are all unlocked), I have no idea of the limitations / implications, but some people here already do that, and the G930W8 (Canada) is Exynos
No idea about warranty, but if you bought it from say the UK and had it shipped, you'd have to discuss with Samsung if they would accept it into a US service centre or if you'd have to ship it back to the UK, no idea about that, no doubt there are places in the US that you could buy a Exynos from
Hit Samsung up on twitter and ask them
Hey All,
Like many unfortunate souls out there I updated my device to Oreo via T-Mobile OTA and instantly my device slowed down with odd behavior. Given I have G930T model which cannot be rooted (be very honest I am confused between the models and why G930T can't be rooted), I am desperate to make this posting hoping someone can help me a bit.
My simple goals:
- Get stock Android on my device and have it running faster, all features working and extend my battery life.
- Keep my phone/app settings
- Not have T-Mobile bloatware.
My concerns:
- Will I lose features such as camera not working in a text message app, WiFi calling, etc.
- Is it better to go back to Nougat or install Oreo? (this is once I figure out all the jargon and many guides)
I refuse to upgrade to a newer device because of stupid software updates and I love this phone too much. This phone is causing me issues professionally such as speaker turning off in the middle of the call, call volume is too low, outgoing text messages failing, sluggish performance, freezing, and horrible battery life. Beside for battery issue, everything else started to happen after software updates.
My Device/Setup:
- Samsung Galaxy S7 - T-Mobile - G903T
- Current stock version R16NW.G930TUVU4CRF1
- macOS with Samsung USB cable
Before there is an outcry on why I didn't search for and find a previous thread that can easily explain, I did and found this amazing write up (it took me a while to even find this):
https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-t3846694
However, there are a few things that I use daily such as visual voicemail and WiFi calling in an office where I had a bad signal. I really hope this post gets me some specific pointers and not get removed from the site for posting this. I am a beginner so please be gentle.
Thanks!
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues https://www.reddit.com/r/Android/comments/5xzbo3/qualcomm_s7_engineering_boot_images_leaked_root/
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Beanvee7 said:
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues ...
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide ...
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Click to expand...
Click to collapse
Thanks for such a detail accurate answer I was looking for. Sorry for the late reply as work has been crazy. I will go through to install Samsung stock firmware and see if it improves performance and battery life. Will try to get G930U and see if I can go without WiFi calling. First, I am trying to do a backup using SmartSwitch (will dig around for more backup option if this one doesn't work). Will update here once I am finished and any lesson learned to help someone else in the future.