-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Walton Primo RX5 (Primo_RX5) #84
Comments
hi, some newer devices have a signed GPT (partition table). on such devices, altering the GPT hard-bricks the device. this is the reason i mostly stopped development of REPIT. make sure you read this. you can try running the to recover from a hard brick you would need an image of your eMMC and the ability to program the eMMC with a JTAG probe. if you do not know what JTAG is, then assume you have no way to recover your device. please decide whether you want to risk testing a REPIT port on your device. thanks! |
hi, sorry for the long delay. are you still interested in this? thanks! |
Actually, I'm sorry. And my device does not have any bootloader image or partition available. |
after looking at your partition table:
i'm assuming your last stage bootloader is the to pull the partition to your PC, you can boot TWRP, make sure you can connect to it using adb, and issue this command on your PC:
you can then run otherwise you may want to blindly try REPIT and take the risk. your MTK device is old, it might not have a signed GPT, but there is always a risk. |
From earlier, I didn't thought that But, as you said, I backed up lk.img and got the strings extracted. |
i didn't find references to GPT signatures in those strings, but that is not a conclusive test. let's try directly finding a signature instead. try this command on TWRP to dump the first 0.5MB of your eMMC, which has the GPT and possibly its signature:
then adb pull the gpt.bin file and post it here (you might need to zip it or change the extension). |
I pulled it out using terminal emulator without going to TWRP. I hope that It's okay. |
i see the protective MBR, the GPT partition header, and 23 GPT partitions. no trace of any signatures. i believe this devices is not protected with GPT signatures. REPIT should work on this device. |
you can debloat your OS, shrink /system to whatever you can and shrink /cache to 32MB to gain space in /data. however you seem to have a stock OS. stock OSes are typically protected by dm-verity, which means that any change to the /system partition will make the phone not boot. you need a kernel without dm-verity to modify the system partition. once /system is modified, OEM updates will not apply (but on old phones there are no updates). for this reason, the /cache partition is not needed anymore. if your OS has dm-verity enabled, you cannot use REPIT. a system-less version of REPIT could be made for your device that ignores system and allows you to move space from /cache to /data. i don't think it is worth the trouble though. |
I do use Custom ROMs of Android Nougat a lot, but still prefer the old Modified Stock Android MM ROM (that I'm still using) very much. And yes, my OEM stopped giving OTA in the late 2017 😩 P.S: |
Device: Walton Primo RX5 (Running on mt6735)
Codename: Primo_RX5
Recovery: TWRP 3.2.1 (Unofficial, Ported from Coolpad Note 3 Lite device.)
Recovery Source > http://zerodevelopers.blogspot.com/2018/01/twrp-321-coolpad-note-3-lite.html
Kernel: 3.18.19 (Stock)
ROM: Amigo OS 3.2 (Android 6.0, Arm64)
Partition Layout: Stock Factory Layout
Dump Log: repit-dump.log
I want to shrink /system (partition no. 20) a little bit and add that bit to /data (partition no. 22)
But /cache (partition no. 21) size will be same as previous
Please help.
The text was updated successfully, but these errors were encountered: