This statement is not debatable. It is straight up fact.There is nothing jcase is unaware of when it comes to Android.
This statement is not debatable. It is straight up fact.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.There is nothing jcase is unaware of when it comes to Android.
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.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.
Thanks for the info. So does the vendor.img contain any carrier data or is it just hardware drivers?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.
So then the problem is upgrading to 7.1.1 system and kernel and relocking on 7.1.1 system and kernel?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)
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).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?
This only applies to unlocked Marlin and not the locked ones from Verizon that came with 7.1.1, right?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).
Other way around.This only applies to unlocked Marlin and not the locked ones from Verizon that came with 7.1.1, right?
No... he is right.
Yes.This only applies to unlocked Marlin and not the locked ones from Verizon that came with 7.1.1, right?
Not gonna substantiate that with anything?
Substantiate please.No... he is right.
Yes.
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?This only applies to unlocked Marlin and not the locked ones from Verizon that came with 7.1.1, right?
?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?
Oops.. not directed at you. Sorry. This discussion is just so old at this point. I'm weary.?
What did I do besides ask a question for you to try and insult me?
Understandable, thank you for answering when you said the opposite. I appreciate it.Oops.. not directed at you. Sorry. This discussion is just so old at this point. I'm weary.