Is it possible to take the files out from the update package, then repackage it and sign it with our own certificate? That's unless something's linked to individual devices.
[GUIDE] Bootloader Unlock
- Thread starter jkuczera
- Start date
Well since we're at a loss at the moment, I figured I'd try some random stuff. I repacked the bootloader unlock OTA and signed it with a test certificate. It might be worth trying? Download here.
No, it would check to see who the CA of the cert is. Unless the cert is issued by a trusted CA, wouldn't work. It's like going to the bank and using a home made ID and Credit Card.
Lol.
I was looking into the footer error, for OTAs on other phones, and sometimes even the file name would make a difference. But if it's all the same like it was on @jkuczera 's update (same file location, name) and file CRC32 matches the one he has, it might be that the signature is tied to the device app. For instance the updater-binary is different between two OTAs, i expected the binary to be standard and take queues from updater-script. Problem will be in changing this without braking the crypto chain, all the files are in the SF/MF and if sha1 key don't match, it won't work
I wish I understood more than half of what you guys are saying.
@DrakenFX
can you verify if the zip file on the sdcard is same as the one you downloaded. The on i got has CRC32 f031d661 and MD5 hash bab1e10494a82d6f2c9f172439b3b8b3 size is 61391631.
More i read about this it ends up being a bad file. Nexus forums were littered with OTAs failing with that error. I had this in the past where file woul be corrupted if i transfered it from the PC to Phone
Also give the ADB sideload a try, it should work since this looks like a standard android recovery with Mi logo
Link for reference: http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5
can you verify if the zip file on the sdcard is same as the one you downloaded. The on i got has CRC32 f031d661 and MD5 hash bab1e10494a82d6f2c9f172439b3b8b3 size is 61391631.
More i read about this it ends up being a bad file. Nexus forums were littered with OTAs failing with that error. I had this in the past where file woul be corrupted if i transfered it from the PC to Phone
Also give the ADB sideload a try, it should work since this looks like a standard android recovery with Mi logo
Link for reference: http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5
Man, you posted you've been able to root the axon 7 did you?
Sent from my XT1095 using Tapatalk
Is the same as yours, i don't have my laptop with me so i can try side loading the update, I'll try when i get back home.
Found what throws out that error
https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-13.0/verifier.cpp - start at line 108
My CPP is rusty, but let's see what is used in footer check
https://github.com/CyanogenMod/android_bootable_recovery/blob/cm-13.0/verifier.cpp - start at line 108
My CPP is rusty, but let's see what is used in footer check
Last edited:
I did not. Maybe you're thinking about me posting in another thread in following up with @tenfar (who said he had root for the Chinese variant)?
Last edited:
This is quite a different file. Did you notice that the first file (the zip one) had a system folder with build.prop the display for A2016U, which is Axon Pro. I just noticed that
ro.product.model=ZTE A2017U
ro.build.display.id=A2016UV1.0B18
ro.product.name=P996A01
That file was not in the manifest, which is strange, every file from the zip should be on there otherwise the hash is bad
---------- Post added at 04:48 PM ---------- Previous post was at 04:46 PM ----------
It will not pass the signature check since the certificate is not already stored on the device. Only ZTE and maybe Qualcomm dev keys would work, otherwise Secure Boot would have no purpose
---------- Post added at 04:54 PM ---------- Previous post was at 04:48 PM ----------
Just checked and this file has the proper footer, bytes 3 and 4 from the end should be FF, which they are and that's what the footer error checks
@DrakenFX give it a try please
Thread Cleaned!
The irony of disrespectful adults telling other users to let the adults work, is remarkable!
Follow XDA Rules which include being respectful to other users (even if you disagree with them) and not using vulgarity (even if it is the only way to show that you're an adult).
This will be your ONLY warning.
The irony of disrespectful adults telling other users to let the adults work, is remarkable!
Follow XDA Rules which include being respectful to other users (even if you disagree with them) and not using vulgarity (even if it is the only way to show that you're an adult).
This will be your ONLY warning.
HELLZ YEAH!!! I knew it when i saw the new file footer, I almost PMd you. Where did the first file come from @jkuczera?
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
New posts
-
-
After i changed magisk name the icon disappeared?
- Latest: roberto_1986
-
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone