[Please help] Coolpad Mega 3 (3503I) - I need to unlock bootloader, flash custom recovery and root.
[Please help] Coolpad Mega 3 (3503I) - I need to unlock bootloader, flash custom recovery and root.
(16-05-2020, 06:55 PM)X3non zip and upload this recovery.img of yours then drop the link here
(16-05-2020, 09:14 PM)Detective_Khalifah Already did, @https://www.hovatek.com/forum/thread-33808-post-192875.html#pid192875
Direct link: https://www.4shared.com/zip/MBX4epDEiq/C..._TWRP.html
(18-05-2020, 01:50 AM)X3non it seems you didn't follow the instructions properly. i noticed you've posted different sizes
if you remove the extra data from original zimage, you'll get a modified zimage that'll decompress without an error having a "Size":16 680 552, "Packed size":7 110 754 bytes
if you decompress this modified zimage using 7zip to get zimage-content and then recompress the content using gzip you'll get the same file size as above
following the guide, you're to
* remove extra data from zimage to get modified-zimage file (store the extra data as you'll need it later and take note of the size of this modified-zimage)
* modify zimage-content using hxd hex editor and replace the right hex value
* recompress this newly modified zimage-content using gzip then check and confirm that the size matches the modified-zimage file
* if it doesn't then add a single byte (00) to the end of the modified zimage-content, recompress and confirm the size
* once the size matches, then copy back the extra data to the end of the newly compressed file
* repack twrp image using the final output zimage
(18-05-2020, 01:05 PM)Detective_Khalifah(18-05-2020, 01:50 AM)X3non it seems you didn't follow the instructions properly. i noticed you've posted different sizes
if you remove the extra data from original zimage, you'll get a modified zimage that'll decompress without an error having a "Size":16 680 552, "Packed size":7 110 754 bytes
if you decompress this modified zimage using 7zip to get zimage-content and then recompress the content using gzip you'll get the same file size as above
following the guide, you're to
* remove extra data from zimage to get modified-zimage file (store the extra data as you'll need it later and take note of the size of this modified-zimage)
* modify zimage-content using hxd hex editor and replace the right hex value
* recompress this newly modified zimage-content using gzip then check and confirm that the size matches the modified-zimage file
* if it doesn't then add a single byte (00) to the end of the modified zimage-content, recompress and confirm the size
* once the size matches, then copy back the extra data to the end of the newly compressed file
* repack twrp image using the final output zimage
Dunno what went wrong. Will redo it.
(18-05-2020, 01:50 AM)X3non it seems you didn't follow the instructions properly. i noticed you've posted different sizesI also noticed after calling your attention to a screenshot last week. Although, I'm getting 7 110 755 bytes from 7-zip (on image with extra data removed).
if you remove the extra data from original zimage, you'll get a modified zimage that'll decompress without an error having a "Size":16 680 552, "Packed size":7 110 754 bytes
(18-05-2020, 05:09 PM)X3non ok, because i already tried extracting & re-compressing and it matches the original sizeI used your CP zImage.7z while working and it turns out I extracted correctly; I compared with the wrong file - patched & gzipped file versus unmodified recovery.img-zImage instead of image with payload data extracted.
files @ https://mega.nz/file/N2xhAa5D#rMlR9_Fe9z...57CJ4f_zeA
(18-05-2020, 01:05 PM)Detective_Khalifah Dunno what went wrong. Will redo it.All right. So, I retried a quadruple. I patched it, and the recovery booted, without touch. Here's what I did: at 20 05 10 37 A1 40 00 D0, I modified 05 to 00 according to instructions for 65-bit-based kernel, while keeping a copy of the original recovery file I extracted from recovery.img-zImage. I had to add 00 once to make packed size 7 110 755.
(18-05-2020, 11:14 PM)Detective_Khalifah All right. So, I retried a quadruple. I patched it, and the recovery booted, without touch. Here's what I did: at 20 05 10 37 A1 40 00 D0, I modified 05 to 00 according to instructions for 65-bit-based kernel, while keeping a copy of the original recovery file I extracted from recovery.img-zImage. I had to add 00 once to make packed size 7 110 755.
When it didn't work, I modified 20 to 00 while leaving the rest of that line untouched (including 05); that also booted without touch, again.
I then modified 20 05 part to 00 00 and the result was the same.
I finally attempted re-modifying 05 to 00 while checking if adding another set of 00s would make it remain 7 110 755 or go up 7 110 756 0 - I had this idea I might be missing the target by half a byte (nibble == 4 bits) or something; but the packed size went up higher than 755 after compressing. Null positive progress whatsoever at that.I flashed both image-new.img & unsigned-image.img, to see if I was going to get something there. All files flashed successfully, booted into TWRP-recovery without touch functionality.
Ah, Computer Architecture & Organization! I'm totally clueless how assembly language works. I'd say programming is easier, but it would be a bad guess to consider this less important.
(19-05-2020, 09:16 AM)X3non well, we're hoping that tpd_probe is what should be used in place of tpd_i2c_probe. don't forget that it maybe a wrong assumptionHere 'tis:
meanwhile can you upload a screenshot similar to step 37 @ https://www.hovatek.com/forum/thread-27132.html
you attached something similar before but without the hex view @ https://www.hovatek.com/forum/attachment.php?aid=7778