- Sep 5, 2017
The recovery partitions only haves 6mb so ye small for latest twrp builds...
I actually did it, but you need to edit your "stock" scatter file
Increase recovery partitions by editing the scatters's partition size, you take space from the next partition into /recovery
I made two scatters, one with 11mb another with 24mb
The only problem is , for releasing this , people would messed up things... Haha
Some people can't work with spflashtools, and this involves more work...
Flash an full "modified stock rom" with an modified scatter ( increased recovery part.)
Then let that ROM boot
Back to recovery and erase all
Flash new ROM (Los etc)
Tons of work for the "regular user"...
So if I manage to edit the scatter file (Do I need to edit EBR1 and MBR files too?) successfully, in theory I would need to update the partition defines on the kernel source too? Also, "disabling" (Removing all the dummy_lens, device imgsensors, flashlight, audio...) the drivers doesn't let me compile, it errors out about something related to audio and the flashlight, so I'm out of options in regards to that I think.
I used a tool named MTK Partition Editor for editing the scatter and the EBR1/MBR files, all looks good, I format the nand entirely except the bootloader (Using SP Flash Tools) and then, I use Download Only to flash the new files. Rom itself works and I can flash the regular lower-than 6MB recoveries, but when I flash a larger one it doesn't want to boot (Checked that it's working on the kitkat partition scheme, but not on the repartitioned jb one), anything I could be missing?
@DragonPT I think I've found why it does not boot, I've recompiled the kernel, formated the phone (Again...) using Jellybean stock rom+lk+preloader etc using SP Flash Tools, changed a working recovery kernel (PhilZ) and pushed it to the device, the result? It takes like 30 seconds to get to recovery mode, only to be presented with a partition mount error, can't mount cache, system... etc To my surprise (And by navigating through your commit history) I've seen a commit where you fix partition defines, applied that to my kernel (Using values for my device obviously) but it hasn't changed, still throws those errors. Also, vol+ and vol- don't seem to be working (Rest of the buttons including touch ones seem to work just fine if I use PhilZ key test function to check which keys are pressed) but the rest (Including lcd and touchscreen) seem to be working. I think my kernel doesn't boot android because it cannot actually find any partitions and thus, it gets stuck in kernel mode and doesn't bootstrap itself to android (If that makes any sense...).
Where could I look into in order to fix this?
Thanks for your precious time reading and answering!
For some strange reason, the recovery/kernel is able to detect and browse my external sd, which is very strange, anything you could think of knowing this?
Managed to get a kmsg of the kernel, hope it helps
Cloned your asus kernel, added my LCM and Touchpanel and magically, all partitions work! But kernel lasts only for 5-10 seconds before it reboots itself... What could it be? (Also, where could I try diffing on my kernel source to fix mounting of partitions?)
Finally fixed it! Sorry for the long reply, problem was easier than I thought, it all was due to partition_defines.h being misconfigured... Re-checked with the scatter, fixed the addresses and now it gets to recovery mode (Without rebooting) and using bq's original source!
Quick ported CM11 (The one that still used 3.4.5 kernel) just to test the kernel, no bootanimation shows but it logcats a bunch of stuff. It gets to SetupWizard (Shows up and instantly disappears) so I think kernel-side, it's working. But if I try to make it work on my stock jelly bean, it doesn't boot (Disabled SELinux completely and still the same), it's getting on my nerves because it doesn't make any sense... -> Attaching logcat: