I bought a rooted Samsung Replenish last week off Ebay. I had trouble activating it, so I had to call in to Sprint to get it activated. After doing a factory reset on the phone, it finally activated. But now there is an update available and I have found conflicting info as to whether or not updating it to GB would brick it. Does anyone here have any firm answers on whether or not attempting to update it would brick it?
Additional info:
I think it has a custom ROM on it, as the About Phone specs are:
Android Version 2.2.2
Baseband Version S:M580.06x.ED23
Kernel Version 2.6.32.9
Build LeafRom 0.2-Beta
When the screen comes up, it displays 4 penguins and has "ShabbyMod" at the top.
Any assistance is appreciated.
not sure how to update for you, but LeafRom is a custom rom, google that and look into it, maybe there is an update?
nissandave said:
I bought a rooted Samsung Replenish last week off Ebay. I had trouble activating it, so I had to call in to Sprint to get it activated. After doing a factory reset on the phone, it finally activated. But now there is an update available and I have found conflicting info as to whether or not updating it to GB would brick it. Does anyone here have any firm answers on whether or not attempting to update it would brick it?
Additional info:
I think it has a custom ROM on it, as the About Phone specs are:
Android Version 2.2.2
Baseband Version S:M580.06x.ED23
Kernel Version 2.6.32.9
Build LeafRom 0.2-Beta
When the screen comes up, it displays 4 penguins and has "ShabbyMod" at the top.
Any assistance is appreciated.
Click to expand...
Click to collapse
Any updates?
did you try the OTA update? did it work?
LeafROM is a custom ROM possibly still Beta, I think at this point it was released almost a year ago and since the current Replenishes are shipping with GingerBread 2.3 it may be a tad behind.
I found mention of it HERE
also try ACS they have been doing some work on the replenish, looks like there may even be a CWM for it..
Hi there i recently bought a Samsung galaxy Nexus unlocked, build ITL41F.I9250XEKK9 its an att docomo phone that i bought off amazon.
Anyway when i go to search for updates it says the phone is up to date and there are no new updates and i'm currently running android 4.0.1.
I did seach google, but i really no nothing about roms and flashing devices so i didn't really understand much.
By the way the first time i connected the phone to wifi it updates the phone but it only did this once. The current version is ITL41F don't no what it was before the update.
Can someone help me or give me a guide to how to update my galaxy nexus ITL41F to a new version of ICS. By flashing the device and using an official ICS rom.
Any help greatly appreciated.
any help anyone?
Same problem here
I've got the same problem here. It installs a "system update" periodically but I'm still suck on 4.0.1. My build # and purchase location are the same. Did yours come bootloader unlocked, i.e., do you see the padlock icon when you first turn on the device? Unfortunately I didn't figure out what the padlock icon meant until it was too late to return it to Amazon.
I'm starting to get worried that someone sold me a hacked firmware that is sniffing my passwords...has that ever happened?
Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
hgpt said:
Hello!
I have a Verizon HTC ONE M8 that no matter what it won't download the new update. I've bought 3 of them (identical) 1 month ago from Ebay. One of them was able to receive the update. On the other two i keep receiving the following message: "We were not able to download this update. To retry, go to Settings > Software update. "
My device is S-off (after a lot of effort). I've tried to get rid of all the bloatware and many more by flashing a new ROM. I have tried flashing ViperROM, ARHD, Clean ROM using TWRP Recovery, without any success. All of my attempts got stuck at the booting screen for more than 30 minutes without any success of booting into the OS. Clean ROM even refused to flash properly. Keep in mind that all the ROMs that I've flashed were based on 4.4.2 firmware, the one that my phone came with, not 4.4.3. I've searched on this forum for a flashable 4.4.3 OTA update, but no success either. What's to be done !?!? All my attempts of installing a new OS failed. Please HELP!
P.S: I'm a newbie when it comes to all of this stuff. First time doing S-off/ installing custom ROMs.
Click to expand...
Click to collapse
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
dynofrk666 said:
You probably won't be able to take the OTA with a custom recovery, it has to be stock. Best bet is to flash the 4.4.3 firmware from the development section since you're s-off, then flash an already rooted stock 4.4.3 rom. It's been a while since I've done this stuff so if I mentioned some incorrect info, my apologies.
Click to expand...
Click to collapse
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
hgpt said:
I flashed back again the stock ROM and i keep receiving the same message over and over again. No TWRP recovery this time, just the red triangle. I guess my best bet is to try and flash the CleanROM ODEX 4.4.3 as mentinoned here: @branmuffin17
I'll come back with the results.
Click to expand...
Click to collapse
If you are on the old firmware you need to update firmware separately.
And btw, if you freeze just one system app that can cause a Vzw ota to fail.
Question.....Is the phone active on your account? I also had one in the drawer and got the same error till I switched it to the active device on my account.
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
runandhide05 said:
It honestly sounds like there is something preventing the ota to even download, if that's the case use dottat's ruu to return to a clean slate, if it still won't download the OTA then I would be willing to bet money that they are defective or not genuine Verizon M8s And if I were to guess it's more of the latter that would be the only valid reason every Rom you've tried fails no matter what.
sent from space
Click to expand...
Click to collapse
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
hgpt said:
Based on what you said i went on some websites to check the IMEI/ESN of the device it seems to be OK. After that i went to the Verizon Wireless website to try an activate my phone and when it comes to "Enter your Device ID to check eligibility", I type in the IMEI and the following message apears: "The phone associated with the Device ID you entered is not compatible with the Verizon Wireless network." To me is strange because on the back of the phone it says Verizon 4G LTE. When it comes to the identity of the phone it is a HTC6525LVW. The phone is GSM Unlocked (I use my phone in Europe so i needed it to be GSM unlocked). More strange it is to me that i don't receive the same message when i type in the IMEI of the others Verizon GSM unlocked HTC's ONE M8 that i bought along with this one.
I guess my only chance is to flash the new firmware @here[and after that flash the Deoxed 4.4.3 Stock Clean ROM @here. If it's not going to work i really don't know what's else it's to be done.
Click to expand...
Click to collapse
The message from the vzw site tells me something is not right.
Google goophone or knock off gs4, the goophone also has an m8 now too... Even with all the branding and everything. And I've seen some gs4s that run what appears to be TouchWiz cloned to a T.
I'd try calling vzw and talk to a rep and it's possible that they could give you more info other than just what the site said.
sent from space
So I did what I've said:
1. Installed firmware provided here @Tigerstown
2. Installed the Odex Stock Rooted ROM proivede here: @scrosler
I am pleased to announce you that everything is fully functional now
Phone is showing:
Android Version: 4.4.3
Software number: CleanROM 2.0.0 (after flashing it from @here)
Baseband version: 1.09.20.0702
Bulid number: 2.21.605.2 CL362279 release-keys
After managing to flash the 4.4.3 version of Android all went up without any problem. Tried to ARHD but it's still not booting. After that installed ViperROM which went up all, but to me it is not the pure HTC Sense 6 experience i was looking about and all that customization is to much for me, so i flashed CleanROM 2.0.0 and here I am. Everything is as it should be: no bloatware, pure HTC Sense 6, optimized performance... and above all the mobile hotspot is now fully functional, not to mention the EXT SAVER.
As a conclusion, to all that guys that are not able to update to the 4.4.3 version via the OTA updates provided by Verizon do what I did above (steps 1 and 2).
ATTENTION: Your device needs to be S-Off and bootloader unlocked + custom recovery!!!
Another thing worth to be mentioned: it would be great if the admins could flag this thread, cause I've seen so many users on different forums that are not able to update via the OTAs.
In the end i would like to thank to all the devs out there for their work and to the users for their support. Cheers!:highfive:
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!
Solved
Used patched version of odin to flash the samsung unlocked firmware (G955U1) from the firmware servers. No more Verizon Splashscreen and spay/bixby work fine
I've been using android devices all my life and have rooted every single device I've owned in the past (probably 4-5 devices). I know the risks and I know how to flash my device and such but I got my S8+ from verizon about 3 months ago before the international unlocked version was released. I only bought it from verizon because their phones are carrier unlocked by default. I use google's project fi.
Verizon is somewhat good with bloatware I can disable or uninstall all of their applications and I haven't found my device to be slowed or burdened by their addons so I never felt the need to root my device which was nice but I got the Bixby update today and I cannot use it unless I update my system software. Tried to update it and it attempts to connect via verizon and ultimately fails saying it cannot connect to the update server. I expected this -- I think it's due to me not using verizon and not having the phone registered with their service.
Want to use Bixby and also would like to flash a stock updated (latest stock version) ROM as I don't care for any new features or custom ROMs because this phone is perfect as it is so far.
Phone software/model specs:
model is SAMSUNG-SM-G955U
kernel version 4.4.16 march 11th, 2017
sev 8.1
android 7.0
aspv march 1st, 2017
knox 2.8
If I follow my usual rooting route properly is it safe to root my phone? Asking because S8+ root is relatively new. I won't ever sell the phone so I don't care if the warranty goes void or something like that.
Essentially looking to turn my Verizon version into a completely US unlocked phone with a stock clean ROM. Is there any possible way I can perform this and still be able to use Samsung Pay? Not a necessity but I do enjoy it.
No root is out
joshclouds said:
No root is out
Click to expand...
Click to collapse
Alright, If I flash the newest version of the samsung firmware onto my device (force update it) will SPay and Bixby still work? And my Knox will be fine?
Both should be intact and working as far as my knowledge goes Bixby for sure spay shouldn't be affected. Let me get this straight you have a Verizon s8+ flashing the unlocked firmware correct?
joshclouds said:
Both should be intact and working as far as my knowledge goes Bixby for sure spay shouldn't be affected. Let me get this straight you have a Verizon s8+ flashing the unlocked firmware correct?
Click to expand...
Click to collapse
I have the S8+ G955U. It's verzion and has the ****ty verzion startup screen and sound it's just annoying. I really want to use Bixby voice as I just got the update from samsung but it says I have to have the newest samsung firmware to use it. I cannot update my phone normally because I don't use verizon I use google fi. So I want to try to flash the standard US carrier unlocked firmware onto my phone from sammobile (not the verizon variant). Is this safe?
the firmware list I'm choosing from: (spaces added so because account is not old enough to post links)
www . sammobile . com/firmwares/galaxy-s8/SM-G955U/
Which one on that list should I use? Obviously I'd choose the first one which is the Verizon firmware but I really would like to just have pure Samsung unlocked stock firmware so I don't have verizon apps & the verizon startup screen.
That's a tough decision I too have a Verizon s8 and it was plagued with the bloat and the splash screen when booting but I used a package disabler to get rid of many if the unwanted and unnecessary packages I didn't like as for using Bixby and getting rid of the splash screen.... It is safe to flash unlocked firmware many people have done this and there is a thread here on xda somewhere all about carrier switching the s8+ to the unlocked firm I could find it if you'd like?
joshclouds said:
That's a tough decision I too have a Verizon s8 and it was plagued with the bloat and the splash screen when booting but I used a package disabler to get rid of many if the unwanted and unnecessary packages I didn't like as for using Bixby and getting rid of the splash screen.... It is safe to flash unlocked firmware many people have done this and there is a thread here on xda somewhere all about carrier switching the s8+ to the unlocked firm I could find it if you'd like?
Click to expand...
Click to collapse
If you could get that thread for me that'd be perfect. Thanks for the help. Really wishing I waited the extra 3 weeks and bought the unlocked version instead.
Updating because I was able to solve it myself. I used a patched version of Odin to bypass the model mismatch error and flashed a new system image and csc (G955U1 model image) that wasn't for my G955U Verizon model.
Bixby works, KNOX is fine, SPay is solid. Verizon splash screen is gone and the phone (from the settings point of view) has no carrier and is fully unlocked and void of bloatware.