Hopefully it's the same for that everybody's getting. I had mixed it up with another file I was trying for the update software.Is this file modified from ones that people received as OTAs, or is it the same file that everyone is getting?
@DrakenFX, did you try unlocking the bootloader then? Just flashing the update wouldn't necessarily do that part as well.
OP link updated!There was something odd about the OP file. It had a file which was not in the manifest and the footer on the zip was invalid. This one is proper (full sig file). This would not be possible to replicate without the private signing key. There might be a tweak in the fastboot code for device specific check, but everything has been so vanilla so far, I am positive it will work
Ok, that's what I thought. It will be interesting to see how deep they integrated the IMEI checking.There was something odd about the OP file. It had a file which was not in the manifest and the footer on the zip was invalid. This one is proper (full sig file). This would not be possible to replicate without the private signing key. There might be a tweak in the fastboot code for device specific check, but everything has been so vanilla so far, I am positive it will work
Yup, so we have to sideload B20 in case new one comes out. We already have a copy of it, just no one has tried the process from B18 like that AFAIK. Plus ZTE would have to build new B21_boot anyways for people who want to unlock after B21Won't this stop working if you're on a build beyond B20?
Won't sideloading B20 fail though? It's going to be checking that is updating against B18, not B20_boot or B20+ version. We would need a full backup of clean B20, or the fabulous unavailable-as-of-yet system images.Yup, so we have to sideload B20 in case new one comes out. We already have a copy of it, just no one has tried the process from B18 like that AFAIK. Plus ZTE would have to build new B21_boot anyways for people who want to unlock after B21
Is this file modified from ones that people received as OTAs, or is it the same file that everyone is getting?
@DrakenFX, did you try unlocking the bootloader then? Just flashing the update wouldn't necessarily do that part as well.
There was something odd about the OP file. It had a file which was not in the manifest and the footer on the zip was invalid. This one is proper (full sig file). This would not be possible to replicate without the private signing key. There might be a tweak in the fastboot code for device specific check, but everything has been so vanilla so far, I am positive it will work
It would be great to get a second file so we can compare and make sure, but this is all standard code from android source tree, just using logo background. The use of old oem unlock command is also interesting, but it might be a legacy support that Google removed since OP3 unlock is the exact same way.Hopefully it's the same for that everybody's getting. I had mixed it up with another file I was trying for the update software.
Was this your update file? If so, it doesn't mean it's generic yet.you mean this, Unlocking the Bootloader? so yeah i already unlocked![]()
, i didn't wanna do it but hell of it ...now reinstalling everything LoL
(yeah "fastboot oem unlock " will wipe device )
P.S. DON'T GO OVER ZTE Community telling about our finding here, i'm not sure if they are all over checking this stuff but lets keep this just XDA wise
:victory:you mean this, Unlocking the Bootloader? so yeah i already unlocked![]()
, i didn't wanna do it but hell of it ...now reinstalling everything LoL
(yeah "fastboot oem unlock " will wipe device )
P.S. DON'T GO OVER ZTE Community telling about our finding here, i'm not sure if they are all over checking this stuff but lets keep this just XDA wise
nop, update file is from @jkuczera (modified by him)Was this your update file? If so, it doesn't mean it's generic yet.
I think he modified the first one, the second one is the same he DL'dnop, update file is from @jkuczera (modified by him)
http://forum.xda-developers.com/showpost.php?p=68162778&postcount=51
mmmm the 2nd one is the one i flash to get access to Unlock Bootloaderdelete
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
I think he modified the first one, the second one is the same he DL'd
I feel like they voluntarily made this easy somehow, could also be that they were way too busy to work on the bootloader and just threw something together as fast as possible. Nonetheless lets hope they are too busy to check XDA. Now I just need my phone can't wait for next week anymore.P.S. DON'T GO OVER ZTE Community telling about our finding here, i'm not sure if they are all over checking this stuff but lets keep this just XDA wise
You could officially void your warranty so we can get the second file for comparison :angel:So when I get my A7 next week, is there anything I can do to help out?
Or just sideload B20 (which no one has done, yet?) and then flash the file in the OP?
Can't we just update to the B20 from the update screen instead of sideloading?So when I get my A7 next week, is there anything I can do to help out?
Or just sideload B20 (which no one has done, yet?) and then flash the file in the OP?
They just used the standard way of doing it that is already provided in the base code, it's all vanillaI feel like they voluntarily made this easy somehow, could also be that they were way too busy to work on the bootloader and just threw something together as fast as possible. Nonetheless lets hope they are too busy to check XDA. Now I just need my phone can't wait for next week anymore.
It might get pulled and replaced with something that does fix this loopholeCan't we just update to the B20 from the update screen instead of sideloading?