HipKat
Recognized Contributor
That is precisely the reason, well, and billing that I switched to T-Mobile. And the better cell signal
Question Sweet merciful Jesus is the Verizon bootloader still permalocked?
- Thread starter jdkzombie
- Start date
wr3cckl3ss1
Senior Member
The two java applets that control this are...
oem_lock
persistent.data.block
Typing "cmd -l" in shell...and you can see that both services are running....starting with oem_lock....sending a few service calls...you'll come to see that it points to persistent.data.block......and sending a few more service calls....you'll see that it points to GMS...Play Services...because that's the only package that has any OEM reading and/or managing capabilities....the only problem is...finding a hole...big enough to... overwrite (like what DirtyPipe did) a read only system file....or somehow repacking an OTA with a patched init_boot.img and see where it can go...and if all fails....I'm going to say DirtyCred (pending PoC release)...should be good enough to pop a root shell...but only if....u don't continue to keep updating your firmware....the older...the better....but as i don't follow the source code or patches that Google releases...it's very hard to tell when they would patch Dirty Cred....or if it's already patched fully on their new baby...the Pixel 7 Pro. But I'm hopeful to keep hammering it out. It's just right now with work and the holidays...my time is super limited and right now...I'm split with both this phone and the S22 Ultra S908U. The S22 Ultra is where I'm advancing pretty good and day by day....it's coming closer to another way in or another level of privilege. But best believe once I'm in the s22....it should be pretty easy...pulling the packages for oem_block and persistent.data.block (s22 falls under same umbrella) and learning how it works and what makes it stay in place.
***Anyone know any Magisk devs...no not John Wu? Got a couple logs...maybe someone can interpret and help me out to figure what I'm reading and what's missing***
wr3cckl3ss1
Senior Member
It's only as simple as those who have the money and shell out hundreds and hundred of dollars...but I do agree with you on some parts. Me....i had the option for either buying outright....thru any carrier...or even Google. But I like a challenge and i do like everything I'm learning and building a good database of knowledge doesn't hurt one bit. But I'll definitely be quick to say...this is absolutely not easy especially coming from simple adb commands and following a guide to hands on reading and reading lines and lines of source code and cross referencing what you can find available.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
3VZW variants have been locked since the OG Pixel days aside from that small window before taking an OTA you could unlock if it was on a certain version. Sadly I don't see this changing anytime soon and if you want to unlock BL and root get the unlocked version from the Google Store. There's really little incentive buying Pixels from Verizon now. With Pixel Pass and Google Store financing those are good options if you can't drop all the money up front.1
I doubt it is a simple or easy as it being simply a "software thing", and I completely believe it could/would never be done...but @wr3cckl3ss1 is on the case!
you can see a bit of how he's progressing HERE and HERE and HERE11My question is why is Verizon so "gung-ho" about it? More than any other carrier (other carriers eventually allow to unlock the bootloader)? I could understand when they used to repair their own devices (so they didn't want the liability and the headaches of when customers messed with the devices); but that's the not the case anymore. Outside of their greedy archaic grasp on tethering and to load unremovable bloatware, I don't know what they have to fear of unlocked bootloaders & root access.
