If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I really don't get this tool.
I have no problems unpacking roms with it, but I can never repack them again. Not even if I make any changes to it.
It crashes when it tries to pack "recovery" every time. Does anyone have any idea on how to solve this problem?
I have tried this on windows 7, windows 8 and windows 10, same problem on every computer.
It says it crashes because of this dll-file: MSVCR100.dll. Which I also have re-installed via the distributables.
Would really appreciate a solution to this. Been pulling my hair for two days.
I've been seeing crashes too, though they were on Linux using Wine. Are you trying to repack an Android 7 image ?
Ah, I see. Yeah I've been trying to repack an Android 7 image. It's the stock-rom for the H96 pro plus that I'm trying to do some work on.
It's a shame if all android 7+ experience these issues with this tool. I just don't get why it fails with the packing, when the unpacking works without any issues at all.
Any will do fine, you can go for the classic (X)Ubuntu or Debian. You can use my toolkit to unpack and repack images if you want, just search for linux-amlogic-toolkit
I would recommend BBQ Linux.
it is based on Arch Linux and Setup for Android ROM Developer.
Also look above in the Scrolle there we are featuring an Linux Tool for unpacking repack AML ROMs.
Any will do fine, you can go for the classic (X)Ubuntu or Debian. You can use my toolkit to unpack and repack images if you want, just search for linux-amlogic-toolkit
An wonderful Tool you have done!
One question i have about it.
Can it unpack the boot.partion?
I did it by hand once to see how it worked, but I didn't bother including it in the toolkit. I figured that those who needed it knew how to do it without the toolkit, because you know that's some advanced stuff.
But if you need it or if you feel like others would need it, just tell me and I'll add it to the toolkit !
Unpacking the initrd and repacking it without touching anything produces a file of a different size (a few kb of difference), and it's enough to break the boot image ("updated is too big for the boot image"). The solution is to edit the bootimg.cfg file, but it has to be done by hand. As a result, I put it in a separate script, to avoid breaking everything for people who don't care about initrd.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment