Updating Verizon Pixel unlocked bootloader with depixel8

LoliSmith

Senior Member
Mar 17, 2017
266
29
0
There is nothing jcase is unaware of when it comes to Android.
That's definitely an overstatement. There are unknown bugs in every piece of firmware and if someone doesn't take the time to try to find them, they remain unknown. AFAIK, jcase found the bugs in 7.1 bootloader and now has no interest in investigating any later versions of the firmware so he isn't looking for them any more. Or at least that is what he has stated publicly.

The 2 phones at issue here are on 7.1.1.
 

npjohnson

Senior Member
May 3, 2014
1,451
2,037
148
St. Augustine, FL
I don't think you are correct. If you leave the bootloader on 7.1, you should be able to unlock it again using depixel8.

Where has anyone done what I am proposing to do - upgrade everything but the bootloader to 7.1.1 and leave the bootloader on 7.1? No one has done it. So no one knows.
You're wrong. I've done some reversing on dePixel8. The exploit that allows you to unlock relies on the 7.1 aboot (what you are calling the bootloader), 7.1 system (which means vendor as well), and boot image.

Here is a note. You can fully upgrade with the factory image, and still remain unlocked, but, should you ever re-lock on 7.1.1, you would permanently lose the ability to re-unlock (short of another exploit surfacing), a potential workaround would be downgrading from 7.1.1 to 7.1 should you ever want to re-lock (which is possible), then remain on 7.1 until you decide to re-unlock (though there is little to no point in this method).
 
  • Like
Reactions: LoliSmith

LoliSmith

Senior Member
Mar 17, 2017
266
29
0
I've done some reversing on dePixel8. The exploit that allows you to unlock relies on the 7.1 aboot (what you are calling the bootloader), 7.1 system (which means vendor as well), and boot image.
Thanks for the info. So does the vendor.img contain any carrier data or is it just hardware drivers?

Boot image = boot.img = kernel, yes?

system = system.img + system_other.img + vendor.img?

Here is a note. You can fully upgrade with the factory image, and still remain unlocked, but, should you ever re-lock on 7.1.1, you would permanently lose the ability to re-unlock (short of another exploit surfacing)
So then the problem is upgrading to 7.1.1 system and kernel and relocking on 7.1.1 system and kernel?
 

5.1

Senior Member
Mar 18, 2012
1,316
546
143
haguenau
Thanks for the info. So does the vendor.img contain any carrier data or is it just hardware drivers?

Boot image = boot.img = kernel, yes?

system = system.img + system_other.img + vendor.img?

So then the problem is upgrading to 7.1.1 system and kernel and relocking on 7.1.1 system and kernel?


Hello... I'm not going to contribute in your research with my knowledge. I'm not a computer or security expert.

I found some little infos for you. The author sells a PDF for a few bucks if you are interested in learning about Android security:

http://newandroidbook.com

There is an outdated version available for free. Take a look, maybe it may help you understand the partitions structure. The one sold seems to cover Android until 7.1 version.

On XDA portal, I've seen some people propose online Android security course really cheap.

Maybe the above could be a good investment for you since you seem really determined to find another exploit. Unless you learn the basics, i doubt people who learned the hard way will give you the answer. :good:


Good luck...
 
Last edited:

npjohnson

Senior Member
May 3, 2014
1,451
2,037
148
St. Augustine, FL
Thanks for the info. So does the vendor.img contain any carrier data or is it just hardware drivers?

Boot image = boot.img = kernel, yes?

system = system.img + system_other.img + vendor.img?

So then the problem is upgrading to 7.1.1 system and kernel and relocking on 7.1.1 system and kernel?
Vendor = proprietary hardware drivers and other configs (must match system version though or you'll get weirdness).

The rest you said is mostly correct, except that vendor is it's own partition.

Yes. But you'd need to downgrade fully to 7.1 (bootloader, vendor, system, boot) to be able to use DePixel8 again.
 
  • Like
Reactions: LoliSmith

awakenedwithin

Senior Member
Mar 25, 2016
59
19
0
Here is a note. You can fully upgrade with the factory image, and still remain unlocked, but, should you ever re-lock on 7.1.1, you would permanently lose the ability to re-unlock (short of another exploit surfacing), a potential workaround would be downgrading from 7.1.1 to 7.1 should you ever want to re-lock (which is possible), then remain on 7.1 until you decide to re-unlock (though there is little to no point in this method).
This only applies to unlocked Marlin and not the locked ones from Verizon that came with 7.1.1, right?
 

bobby janow

Senior Member
Jun 15, 2010
5,653
1,849
253
No... he is right.


Yes.
Substantiate please.

---------- Post added at 06:03 PM ---------- Previous post was at 05:57 PM ----------

This only applies to unlocked Marlin and not the locked ones from Verizon that came with 7.1.1, right?
A Verizon model that came with 7.1.1 cannot be unlocked. What part of this is unclear? If you have a Google device you can do whatever you want. If you want to unlock and relock a Verizon device you need to have your head examined. How is this even a discussion at this point? If you want to unlock, relock, unlock, relock then .. well need I say more? What is going on here?
 

awakenedwithin

Senior Member
Mar 25, 2016
59
19
0
Substantiate please.

---------- Post added at 06:03 PM ---------- Previous post was at 05:57 PM ----------


A Verizon model that came with 7.1.1 cannot be unlocked. What part of this is unclear? If you have a Google device you can do whatever you want. If you want to unlock and relock a Verizon device you need to have your head examined. How is this even a discussion at this point? If you want to unlock, relock, unlock, relock then .. well need I say more? What is going on here?
?
What did I do besides ask a question for you to try and insult me?