Database Info

Bootloader unlockable in all versions?

Hey all, I'm thinking of getting a G2 and wanted to make sure that the newer versions of the bootloader can all be unlocked or downgraded. I found this thread but wasn't sure if it was up to date. I plan to buy on eBay so I have no clue what I'll actually end up with until I have it in my hands.
I didn't do my homework before buying my Galaxy S4 and have been stuck dealing with Samsung's halfassed inefficient and locked down software because of their un-unlockable bootloader for the last year or so. I really want to make sure my phone is actually mine this time.

Verizon Phones will get os updates the same day as google unlocked pixels

FYI
http://www.droid-life.com/2016/10/12/verizon-pixel-xl-updates-google-same-time/
http://www.theverge.com/circuitbreaker/2016/10/12/13258286/verizon-google-pixel-fast-android-updates
Google also confirmed this.
From Ars
Update 2: Google agrees! The company told Ars "OS updates and monthly security patches will be updated on all Pixel devices (Verizon and non-Verizon versions) simultaneously."
Bootloader still won't be unlockable, but this is a step in the right direction.

Frankly, if software is updated quickly along with Google it makes an unlockable bootloader less important to a lot of people.
Verizon has a mixed past with this and Google. They screwed up the Galaxy Nexus but did OK with the Nexus 6.
I'm still happy to buy from Google since I see the ability to unlock the bootloader as insurance against Verizon changing it's mind a year down the road when everyone is paying attention to something new.

atlp99 said:
Frankly, if software is updated quickly along with Google it makes an unlockable bootloader less important to a lot of people.
Verizon has a mixed past with this and Google. They screwed up the Galaxy Nexus but did OK with the Nexus 6.
I'm still happy to buy from Google since I see the ability to unlock the bootloader as insurance against Verizon changing it's mind a year down the road when everyone is paying attention to something new.
Click to expand...
Click to collapse
So, with a locked bootloader, there's absolutely no way to flash the Google stock image over it, correct?
Let's say down the road someone figures out a way to root the device and unlock the one sold by VZW. Theoretically, couldn't we then flash the factory stock Google firmware, effectively turning it into the same model as the Google Store one? Then we wouldn't have to worry about VZW pushing updates that would relock it if we flashed those? Of course I know one wouldn't take an OTA on a rooted, unlocked phone, but if you had to return to stock...you could go straight to Google's firmware.
If the VZW phones are going to get updates pushed straight from Google, then those images would have to be different from all the other Google updates, right? They would have to include the VZW bootloaders...would there be a way to inject the Google Unlockable bootloader into that OTA and then flash that?

Jank4AU said:
So, with a locked bootloader, there's absolutely no way to flash the Google stock image over it, correct?
Let's say down the road someone figures out a way to root the device and unlock the one sold by VZW. Theoretically, couldn't we then flash the factory stock Google firmware, effectively turning it into the same model as the Google Store one? Then we wouldn't have to worry about VZW pushing updates that would relock it if we flashed those? Of course I know one wouldn't take an OTA on a rooted, unlocked phone, but if you had to return to stock...you could go straight to Google's firmware.
If the VZW phones are going to get updates pushed straight from Google, then those images would have to be different from all the other Google updates, right? They would have to include the VZW bootloaders...would there be a way to inject the Google Unlockable bootloader into that OTA and then flash that?
Click to expand...
Click to collapse
Assuming that we only have one US version (which I think has been confirmed), and the fact that verizon bloat gets installed on first boot with sim card activation, I want to say that the phones are the same. Maybe the only difference between the google phone and the verizon phone is the "oem unlock" toggle will not work on the verizon phones. Or maybe they will have different bootloaders. Then there would be multiple firmware images, one for verizon, one unlocked. If you could get root, then you could possibly get an ota for an unlocked phone and install it, thus replacing the verizon bootloader (if it is in fact different). I am growing more and more skeptical that there is any difference at all between the verizon and google phones. I wonder if this is all going to fizzle out in a week when everyone gets their phones.
I have 1 on preorder from google and an upgrade preorder from Verizon right now. I'm torn on which one to go with because I will save a good bit of money by going through Verizon. All I really want to do is root, so I "might" be worried for no reason. Time will tell.

Yeah, I canceled my order through the Google Play store to get it through VZW on my company account once I learned Big Red wasn't holding up the updates. Ultimately, I may be okay with the locked bootloader as I'm getting older and have 3 kids. I don't have to time to mess with android like I used to. :crying:
---------- Post added at 01:19 PM ---------- Previous post was at 12:42 PM ----------
dbrohrer said:
Assuming that we only have one US version (which I think has been confirmed), and the fact that verizon bloat gets installed on first boot with sim card activation, I want to say that the phones are the same. Maybe the only difference between the google phone and the verizon phone is the "oem unlock" toggle will not work on the verizon phones. Or maybe they will have different bootloaders. Then there would be multiple firmware images, one for verizon, one unlocked. If you could get root, then you could possibly get an ota for an unlocked phone and install it, thus replacing the verizon bootloader (if it is in fact different). I am growing more and more skeptical that there is any difference at all between the verizon and google phones. I wonder if this is all going to fizzle out in a week when everyone gets their phones.
I have 1 on preorder from google and an upgrade preorder from Verizon right now. I'm torn on which one to go with because I will save a good bit of money by going through Verizon. All I really want to do is root, so I "might" be worried for no reason. Time will tell.
Click to expand...
Click to collapse
If this phone is truly carrier unlocked, if you paid for it outright at Best Buy or where ever you decided to get it and took it to another carrier, how would future updates work? Maybe the Google store phones IMEI's are all stored as the unlocked bootloader batch and get updates from set A, while all other IMEI's get updates from set B to maintain the unlockable bootloader. If I'm on AT&T, with a phone purchased from any store other than Google, what's to keep that phone from getting the same Google update as the ones bought from the Play Store? I'm sure hoping there will be a way to flash the stock Google image over the top of the VZW phones, that would be ideal.

Jank4AU said:
If this phone is truly carrier unlocked, if you paid for it outright at Best Buy or where ever you decided to get it and took it to another carrier, how would future updates work? Maybe the Google store phones IMEI's are all stored as the unlocked bootloader batch and get updates from set A, while all other IMEI's get updates from set B to maintain the unlockable bootloader. If I'm on AT&T, with a phone purchased from any store other than Google, what's to keep that phone from getting the same Google update as the ones bought from the Play Store? I'm sure hoping there will be a way to flash the stock Google image over the top of the VZW phones, that would be ideal.
Click to expand...
Click to collapse
Good point. If 2 separate firmware images are in circulation, Google has to give you the ability to get updates after you leave Verizon (I hope...). The more I think about it, the more I believe that there isn't going to be any difference. Fingers crossed that evleaks and every android blog site blew this way out of proportion.
Nexus 6 was sold by Verizon and was identical to the google play store phone. Bootloader could be unlocked and any factory image could be flashed on it.

The Nexus 6 was basically this way. Verizon kept their hands off it except for the branding on the back of the phone body. If they treat the pixels the same as the Nexus 6, there is little to no reason to buy straight from Google if you want to buy from Verizon.
The only difference for me is that i would have been able to spread out payment on my bill if I went through Verizon. Buying through Google meant that I had to pay for it up front.
For me, avoiding the possibility of an non unlockable bootloader was worth paying up front for.

VZW apps on my phone?

This may be a silly question but I hope someone can answer for me.
I am currently living in Thailand and picked up a Pixel 2 not too long ago. I got the OTA up to January while my phone was still stock/unrooted with my Thai Sim card. I then unlocked the bootloader rooted Magisk etc... At one point I flashed the stock image from google (not the UK or verizon variants) as I wanted to go back to stock.
I then updated to the February update by flashing the factory image without the -w to prevent wiping. Currently on OPM1.171019.019
Just earlier today I was snooping around and found the following installed but disabled:
My Module: com.vzw.apnlib
Retail Demo Mode: com.customermobile.preload.vzw
Vzw OMA Trigger: com.android.vzwomatrigger
vzw_msdc_api: qualcomm.com.vzw_msdc_api
VZW_Multicast_MW: com.qualcomm.ltebc_vzw
My question is, are these Verizon services baked into the stock image files? A Verizon had never been in the phone, as far as I know.
Thank you kindly

I know that this post is a few months old, but I was just searching for the same answer to this question regarding my phone. I am currently seeing these on my T-Mobile branded Snapdragon Note 8. If anyone out there might be able to help answer?

I think this thread and this thread are related.
For some reason there's a cross over between what the VZW and Google should be. It must have something to do with the partnership between them.
I just had the issue of VZW potentially (NOT confirmed) locking my boot loader...

Also on my Sprint G965U

same thing with me on a us cellular s8 that i bought brand new in store. I found a verizon service agreement in my network config. i called and questioned them about it, i asked what their affiliation with vzw was , they said they had none unless it was above their paygrade. they ended up telling me the phones are programmed for multi carriers from the manufact then the acutual carrier will optimize them which leaves pretty much dead files that cant be rewmoved. use activity launcher you dont need root and you can access almost every file in a readable state and also control tons of **** that is in your phone but cant access. i cant believe all the settings that you would never know about. anyway getting off track. back to vzw, i first thought vzw files on a new us cellular device meant maybe it was rerfurbished and they lied, i wish , bye bye contract lol. i think this could be made into a big deal, possible void a contract , going to go to the store and see what they think, i know they wont have a clue. thats what im hoping because ill easily take an s10+ and not pursue it any further haha

taldavid2 said:
This may be a silly question but I hope someone can answer for me.
I am currently living in Thailand and picked up a Pixel 2 not too long ago. I got the OTA up to January while my phone was still stock/unrooted with my Thai Sim card. I then unlocked the bootloader rooted Magisk etc... At one point I flashed the stock image from google (not the UK or verizon variants) as I wanted to go back to stock.
I then updated to the February update by flashing the factory image without the -w to prevent wiping. Currently on OPM1.171019.019
Just earlier today I was snooping around and found the following installed but disabled:
My Module: com.vzw.apnlib
Retail Demo Mode: com.customermobile.preload.vzw
Vzw OMA Trigger: com.android.vzwomatrigger
vzw_msdc_api: qualcomm.com.vzw_msdc_api
VZW_Multicast_MW: com.qualcomm.ltebc_vzw
My question is, are these Verizon services baked into the stock image files? A Verizon had never been in the phone, as far as I know.
Thank you kindly
Click to expand...
Click to collapse
it all comes down to business. those apps are preinstalled, yes, baked in? yes and no. they have read only permissions but are not an integral part of the system and can be removed. some users report having trouble using verizon apps with their verizon service after uninstalling com.vzw.apnlib i'm sorry you didn't get an answer sooner, but these things happen.

Samsung J7 (2018) J737V

Hello all! I am an owner of a Samsung Galaxy J7. It is the newer generation, model J737.
I did not see any threads on this type of phone and so I wanted to get things going.
Anybody know of roots being developed for this? Or is this model compatible with the same root software as its predecessors? What shall we do!? I am no phone programmer but I am willing help out with what I can! Share what you know.
Thanks.

J737
I'm still looking for all the firmware. I have the Verizon model. Firmware is listed as: J737VVRU2ARI4.

MOD EDIT: PAY-PER-CLICK LINK REMOVED
https://androidfilehost.com/?fid=1322778262904010272 - J737VPPVRU1ARG1 / Prepaid / July 2018 security patch (1)

I just recently purchased this phone as well and am looking to root, install twrp, play with rooms etc. Injave found very little info on this model. Its surprising to me that with all the great mid range phones available now still so much attention is directed toward company flagship models. I started rooting phones way back with my S3, then two LG G2s, S4, and S5. Since I have mostly purchased midrange phones because the pre-paid plans are significantly cheaper then contract phones and just as good as they use all the same networks. I guess the main draw back is the majority of devices associated with the pre-paid networks have locked boooaders that cannot be in blocked until after a year of service. The exception is the verizon pre-paid devices which only require only the first month of service to be purchased before becoming eligible to be unlocked. They will then happily provide you with an unlock code. I'll just go ahead see what I can accomplish with my j737 by using files for other j7 devices and see what I can accomplish. Some might find this foolish but I love this stuff and patience may be a virtue but i e never been good at waiting. If I have any success I'll post back....
.if I don't post back it's because I'm using my j7 as a paperweight.

J737v
Cf auto root keeps failing. Phone says "security check fail. (Recovery)" can someone help.

need root
also had fail with recovery message

timba123 said:
Hello everyone. I have the straight talk version. It's a 737 variant. They just changed the model number basically...sm-s767vl.
Are you on the j737v able to allow OEM unlocking in developer options?
Click to expand...
Click to collapse
Did anyone have luck at changing this j737v to another carrier or unlocked firmware

i got combination file for binary 5 ....... still need root !
trying to install u firmware
will update with more info when accomplished

Question New SM-S908E-D/S, and planning on rooting - Got a few quick questions

Hi, guys - I've been a OnePlus fan since they first started selling phones, but stopped at the OP7P. IN the past, I rooted my phones as soon as they came out of the box.
I decided to switch back to Samsung after all these years. I live in the US, and purchased a new global SM-S908E-D/S so that I could continue having a rooted phone.
I was going to try out my global S22 Ultra for a week or so before rooting to make sure that I have good coverage for my connection to AT&T. I saw that the global S22 Ultra has many of the AT&T 4G/5G bands that the US version supports, but there are differences. If I don't have good coverage due to the channel differences, I will look into returning the phone.
So, I have a few quick questions:
I know that I will lose all my data once I unlock the bootloader, but can I configure my phone normally and take all Samsung updates before unlocking the bootloader and rooting the phone? On my previous Samsung devices, bootloader unlocking/rooting was patched/blocked by Samsung, so there was a limited opportunity to unlock the bootloader/root.
If I unlock the bootloader, is there a way to relock the bootloader so that it isn't visible that the phone was previously unlocked? I know the Samsung Knox aimed to always fail a security check if the bootloader was ever unlocked.
Is there a way to configure my global S22 Ultra to support all the US AT&T 4G/5G bands instead of a partial list?
Thanks!
¿GJ?

I know the feeling of coming back to a Samsung after experimenting with the open world,
1. Question isn't really clear - As I understood; Yes - You can use the phone, get OTA and configure until you decide to unlock it. Unlocking the bootloader will wipe all data.
2. You can relock the bootloader - but traces will always remain as Knox is a one way ticket. Once broken, Knox can never be sent back to 0x0. Even after relocking, Samsung Apps such as Health and Pay will not work.
3. So far, No confirmed method.

Thanks, @JazonX - That's what I was looking for.
The question for #1 was revolving around how in the earlier days of rooting, it was a cat & mouse chase to stay ahead of the manufacturers with rooting. Some devices I have owned (Amazon FireTV sticks, and my Samsung S4 Tablet, for example) would be rootable for a short period of time, where if you didn't unlock the bootloader and root immediately, you would get an update from Samsung that patched the hole and it was never rootable afterwards.
I was asking if the SM-S908E-D/S would always be rootable (maybe because of the EU?), so that I could use the phone as a normal device, accept all the Samsung updates, and not be concerned that a Samsung update would come along that permanently blocked the bootloader and rooting.
I could decide in a few weeks that the phone was good on AT&T, and then be able to root it at that point.

Unlocking the bootloader doesn't trip Knox. Rooting does.
There are a few "patched" Knox apps that you can use, shealth, private share and secure folder. These are included with beyondrom and Dr ketans rom.

@MRDOCA - Thanks, that's good to know.
I unlocked my bootloader, and I am attempting my first manual Firmware update (not rooting at this time).
I downloaded and ran Frija, which asks for my CSC. Looking into my phone's Software settings, I see that my CSC is CHO/CHO,CHO/CHO/CHO - Which appears to be in Chile. Even though I am in the US on the AT&T network, I'm assuming that I just use the CHO CSC in Frija and my phone will re-adapt to the AT&T network after my update?