Related
I am trying to build a TWRP version for the SM-J530F following this guide by Dees_Troy.
This is my first time trying to build a recovery, so I could use some help.
It would be great if someone could tell me or help me writing the Boardconfig.mk as I am not sure if I got everythingright and everythinh what is needed.
The recovery.fstab should be correct , although I am not sure for the usb partition. The files I am using for building are in the attachments.
Last and most important thing for me to start to build would be if someone can reach me out a proper firmware or whatever i need to put in the /device directory of my build environment.
I have tried sammobile.com/SM-J530F and some other site I can't find anymore but I could not get the .img unzipped by 7zip out of the md5 files to mount(tried on Win and Linux) . Any hint on that?
I am building on a Virtual Box on a Win10 machine running Linux Mint.
Thanks in advance!
Adlbert said:
I am trying to build a TWRP version for the SM-J530F following this guide by Dees_Troy.
This is my first time trying to build a recovery, so I could use some help.
It would be great if someone could tell me or help me writing the Boardconfig.mk as I am not sure if I got everythingright and everythinh what is needed.
The recovery.fstab should be correct , although I am not sure for the usb partition. The files I am using for building are in the attachments.
Last and most important thing for me to start to build would be if someone can reach me out a proper firmware or whatever i need to put in the /device directory of my build environment.
I have tried sammobile.com/SM-J530F and some other site I can't find anymore but I could not get the .img unzipped by 7zip out of the md5 files to mount(tried on Win and Linux) . Any hint on that?
I am building on a Virtual Box on a Win10 machine running Linux Mint.
Thanks in advance!
Click to expand...
Click to collapse
try updato.com or samfirm app also you need to convert the img.ext4 to actual EXT4 first, Recovery & Boot images can be unpacked easily with Image Kitchen
Amy News
Hey fellas, I will be trying to get TWRP for this device as i own it at the moment. I was hoping if there are users left who would like to test it with me. so if anyone is aware of an official J530F section please let me know. thanks.
ananjaser1211 said:
Hey fellas, I will be trying to get TWRP for this device as i own it at the moment. I was hoping if there are users left who would like to test it with me. so if anyone is aware of an official J530F section please let me know. thanks.
Click to expand...
Click to collapse
i have a j530fd ,can i test it too?
ananjaser1211 said:
Hey fellas, I will be trying to get TWRP for this device as i own it at the moment. I was hoping if there are users left who would like to test it with me. so if anyone is aware of an official J530F section please let me know. thanks.
Click to expand...
Click to collapse
I can test it i have J530F
Unofficial release -TWRP recovery for the Galaxy SM-J530F
https://forum.xda-developers.com/galaxy-j5/development/twrp-twrp-recovery-j5-pro-2017-t3668266
This unrooted my phone?
Thanks to this thread we can download the P20 Lite firmware and extract the boot image (called ramdisk in these new huawei devices). Because of my bad connection (about 3hours of download and I can't wait), can someone extract the boot image file and attach it here, please ?
If you still need: https://mega.nz/#!kDpTiYbb!9GxIphHYIMPMW9Re-KwYWmy2Mt39FH7UpwdcxCWR-QA
ante0 said:
If you still need: https://mega.nz/#!kDpTiYbb!9GxIphHYIMPMW9Re-KwYWmy2Mt39FH7UpwdcxCWR-QA
Click to expand...
Click to collapse
U have for ANE-LX2J?
Chrisu_Kun said:
U have for ANE-LX2J?
Click to expand...
Click to collapse
Download service ROM for your model and regional variant, then extract ramdisk.img from UPDATE.APP using Huawei update extractor.
[ Advanced users (using DualbootPatcher) Only ]
As dualbootpatcher doesn't officially support for installing oreo , Pie roms in data slot .
But Everyone wants to install in data slot for keeping stock rom in primary slot.
So for fixing the issue i googled & found some thread about this but that aren't adaptable for our devices ( msm8916 which use QCDT image ).
To resolve this problem there is needed to fix the dtb file. So I've compiled it for fixing.
Please follow the procedure carefully.
1. Unpack an Oreo or Pie rom.
2. Unpack the boot.img using carliv-kitchen. ( Attached bellow )
3. Replace the boot.img-dt from unpacked boot.img. { Attached bellow ( Rename the given boot.img-dt___.img to boot.img-dt ) }
4. Repack boot.img.
5. Use output boot.img in the unpacked rom.
6. Delete assart line from updater-script from META-INF folder.
7. Patched the rom zip file with dualbootpatcher.
8. Then install.
Click to expand...
Click to collapse
DualbootPatcher Details Guide for J5 : https://forum.xda-developers.com/ga...reo-pie-j5-t3874301/post78310831#post78310831
Reserved 1
The pie ROM is installed only in the primary slot, i tried this solution but no boot.
abdogeni said:
The pie ROM is installed only in the primary slot, i tried this solution but no boot.
Click to expand...
Click to collapse
What's wrong say details.
Carliv Kitchen For Windows
Carliv Kitchen By bluefirebird.
Original Thread :
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
Hey I don't know how to do the third point... can you help me? I extracted all with cariv image kitchen, i've found boot.img-dt but I don't know with what I have to replace that file
HWDEV said:
What's wrong say details.
Click to expand...
Click to collapse
It worked now, i have not deleted the assert command, so now it boot perfectly.
Jhacker05 said:
Hey I don't know how to do the third point... can you help me? I extracted all with cariv image kitchen, i've found boot.img-dt but I don't know with what I have to replace that file
Click to expand...
Click to collapse
are there any updates on this please?
Sorry ! Unfortunately the boot.img-dt removed while thread updating. I'll add it very soon.
HWDEV said:
Sorry ! Unfortunately the boot.img-dt removed while thread updating. I'll add it very soon.
Click to expand...
Click to collapse
Ok tank you bro
Jhacker05 said:
Ok tank you bro
Click to expand...
Click to collapse
File Added.
About internal storage size
HWDEV said:
File Added.
Click to expand...
Click to collapse
I used the new file uploaded and i am facing a new problem that the storage size is 32 GB instead of 16 GB, is it the cause or the problem in the ROM, i use Pixel Experience ROM for SM-J510FN.
The boot.img you gave can't be added to another samsung device like an S8 I supposed ?
Envoyé de mon SM-G955F en utilisant Tapatalk
Benjamin2557 said:
The boot.img you gave can't be added to another samsung device like an S8 I supposed ?
Envoyé de mon SM-G955F en utilisant Tapatalk
Click to expand...
Click to collapse
No. The boot.img only compiled for J5 2016.
work with magisk?
Does is also work when i have magisk installed?
Phitschhd said:
Does is also work when i have magisk installed?
Click to expand...
Click to collapse
Dead project. Move on and do what i told you in the other thread.
THE FOLLOWING GUIDE IS FOR OREO IMAGES.
TO UNPACK AMLOGIC 9.0 PIE IMAGES, WATCH THIS TUTORIAL VIDEO: https://youtu.be/exDD6YOC4HU
Hey Everyone! Many people requested me on forumXperience to make a repacking/unpacking guide for Amlogic Oreo/Pie Images. So yesterday, when I had time I started to create my own windows tool for you guys to unpack and repack Amlogic Oreo/Pie Images.
You can now easily extract files in a few clicks and edit them to flash on your devices!
Very simple to use and it works great and is also faster than stock Amlogic Customization Tool which unfortunately doesn't support Oreo images.
There may be a few bugs that I am unaware of, so please let me know if you run into any problem. Later, I may add recovery and kernel unpacking option in the tools.
Thanks to Ricky for his Customisation Tools, I used his binaries for this project
The tool is pretty much open for everyone to edit and modify, it has batch scripts so you can easily edit with Notepad and learn the process of Amlogic Unpacking/Repacking manually [emoji23]
Here you can download the tool:
[Amlogic Unpacker by Nayam.zip]
3.26 MB
it works fine. thanks.....
i was going to buy the other tool but this did the work without any money
techygaga said:
it works fine. thanks.....
i was going to buy the other tool but this did the work without any money
Click to expand...
Click to collapse
Good to hear. This has been flying under the radar and people really didn't care about this tool. Glad to see atleast there's someone using this.
Yes it does unpack/repack oreo images but it doesn't (yet) unpack recovery and kernel which I thought were not really important for the time being. Unpacking vendor and system will do all the work if you want to mod ROMs. Kernel and Recovery modifications are really not required and can be avoided by using alternative ways.
Sent from my F3116 using Tapatalk
Cool. Thank you
thanks
link doesn't work
do you have support uppack/repack Android 9??
xmannv said:
do you have support uppack/repack Android 9??
Click to expand...
Click to collapse
Yes ofcourse
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Yes ofcourse
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
But Image Pack Failed (Android 9 Pie)
Level 1 repack doesnt work with A95X Max.
Copy Level 1 folder into Ricky Customisation tool "tmp" folder and repack with that.
like your tool..
Tonian1878 said:
Level 1 repack doesnt work with A95X Max.
Copy Level 1 folder into Ricky Customisation tool "tmp" folder and repack with that.
Click to expand...
Click to collapse
Hey, i have the same problem with a gt king pie .img..
I unpack LVL 1 & LVL 2 with nayams tool (works great :good: ). make changes (example: delete one app, paste another) ... and then?
Unfortunately I can not just unpack lvl2 with nayams tool. To unpack lvl2 I have to unpack lvl1 ..
and with rickys tool I can only pack lvl1 when i try to repack lvl2 it dosent work .. can you please explain to me briefly how I have to do it?
Thanks
Sim
5im said:
Hey, i have the same problem with a gt king pie .img..
I unpack LVL 1 & LVL 2 with nayams tool (works great :good: ). make changes (example: delete one app, paste another) ... and then?
Unfortunately I can not just unpack lvl2 with nayams tool. To unpack lvl2 I have to unpack lvl1 ..
and with rickys tool I can only pack lvl1 when i try to repack lvl2 it dosent work .. can you please explain to me briefly how I have to do it?
Thanks
Sim
Click to expand...
Click to collapse
get rickys customisation tool, in the folder of ricky customisation tool, create a folder called "tmp".
Now unpack your firmware with nayams tool (both level 1 and 2) and copy the level 1 and 2 folders from the "unpacked" folder and paste them into you newly created "tmp" folder.
start rickys customisation tool, edit and repack your rom from there.
hope that make sense
5im said:
Hey, i have the same problem with a gt king pie .img..
I unpack LVL 1 & LVL 2 with nayams tool (works great :good: ). make changes (example: delete one app, paste another) ... and then?
Unfortunately I can not just unpack lvl2 with nayams tool. To unpack lvl2 I have to unpack lvl1 ..
and with rickys tool I can only pack lvl1 when i try to repack lvl2 it dosent work .. can you please explain to me briefly how I have to do it?
Thanks
Sim
Click to expand...
Click to collapse
I'm sorry for not explaining everything correctly.
Level 2 is unpacked after unpacking level 1.
You cannot unpack level 2 without unpacking level 1 first.
Similarly, the repack script I wrote first repacks level 2 and then repacks level 1. If you want these separated, I can provide that too.
So you need to run the scripts in order.
Run script number 1, then 2. Then make changes in level 2 folder and then run repacking script.
Sent from my F3116 using Tapatalk
Tonian1878 said:
Level 1 repack doesnt work with A95X Max.
Copy Level 1 folder into Ricky Customisation tool "tmp" folder and repack with that.
Click to expand...
Click to collapse
Thanks for confirming, I'll fix the repacking script If it's causing problems.
Sent from my F3116 using Tapatalk
If Pie images aren't working, please wait for a fix. I'll try some pie images out and will update the commands
Sent from my F3116 using Tapatalk
N'ayam Amarsh'e said:
Thanks for confirming, I'll fix the repacking script If it's causing problems.
Sent from my F3116 using Tapatalk
Click to expand...
Click to collapse
Thanks.
it does repack the firmware but after flashing the a95x max, it just hangs on the boot logo and doesnt get to the boot animation.
as said before, if i take the unpacked level 1 contents from your tool and repack with rickys tool, A95X max flashes and boots perfectly.
level 2 to level 1 repack doesnt seem to be an issue, purely level 1 to img repack.
@Tonian1878: Thx for the explanation!
N'ayam Amarsh'e said:
If Pie images aren't working, please wait for a fix. I'll try some pie images out and will update the commands
Click to expand...
Click to collapse
That would be great! If you need a Pie image for testing: bee-link.com/forum.php/forum.php?mod=viewthread&tid=50649&extra=page%3D1
Download link is down.. pls re-up.
Tonian1878 said:
get rickys customisation tool, in the folder of ricky customisation tool, create a folder called "tmp".
Now unpack your firmware with nayams tool (both level 1 and 2) and copy the level 1 and 2 folders from the "unpacked" folder and paste them into you newly created "tmp" folder.
start rickys customisation tool, edit and repack your rom from there.
hope that make sense
Click to expand...
Click to collapse
I tried it that way. Unfortunately, there is always an error message "Failed to repack system, default will be used"..
The image will be packed correctly, but my changes will be overwritten again.
Do you use AMLogicTools_V6.0.0?
Where are the programmers?...
The programmers are programming
ShaDisNX255 said:
The programmers are programming
Click to expand...
Click to collapse
why is nobody interested in the A10?
rockeirodohs said:
why is nobody interested in the A10?
Click to expand...
Click to collapse
bcuz its a cheap low budget device?
elliwigy said:
bcuz its a cheap low budget device?
Click to expand...
Click to collapse
yea
but it is still a great cell phone
rockeirodohs said:
yea
but it is still a great cell phone
Click to expand...
Click to collapse
if u say so.. its great for its price i guess
Sent from my SM-G977P using Tapatalk
rockeirodohs said:
yea
but it is still a great cell phone
Click to expand...
Click to collapse
Why don't you try learning? That's pretty much how all developers start, wanting to make their phone better.
rockeirodohs said:
Where are the programmers?...
Click to expand...
Click to collapse
Has the 64bit vendor been made yet?
ShaDisNX255 said:
Why don't you try learning? That's pretty much how all developers start, wanting to make their phone better.
Click to expand...
Click to collapse
How can I do it? I am willing to do, or at least start. If you could help me.
mmacedoc7 said:
How can I do it? I am willing to do, or at least start. If you could help me.
Click to expand...
Click to collapse
There are lots of tutorials on XDA, I suggest you start using google + XDA to learn.
Trust me, it's better to ask
"Hey, I'm following this guide and I'm stuck on this step" instead of
"Hey, can you teach me? Can you give me a guide?"
I tried adding the lib64 folder from the galaxy a20's android 9 vendor to my android 10 galaxy a10 vendor and editing all the .prop files in /vendor to support arm64-v8a, but it didn't boot arm64 gsis (black screen after a10 logo for a while, then reboot). Is this because the library files are made for android 9 or do i have to edit the device tree and kernel too? or is there something else in the vendor I'd have to edit?
Pankiefield said:
I tried adding the lib64 folder from the galaxy a20's android 9 vendor to my android 10 galaxy a10 vendor and editing all the .prop files in /vendor to support arm64-v8a, but it didn't boot arm64 gsis (black screen after a10 logo for a while, then reboot). Is this because the library files are made for android 9 or do i have to edit the device tree and kernel too? or is there something else in the vendor I'd have to edit?
Click to expand...
Click to collapse
I think there was also something you needed to do in ramdisk, but I'm not sure.
The only person I've seen who's been successful in porting arm64 libs to another device is @Astrako I don't know if you want to ask him and maybe he can help you out.
ShaDisNX255 said:
I think there was also something you needed to do in ramdisk, but I'm not sure.
The only person I've seen who's been successful in porting arm64 libs to another device is @Astrako I don't know if you want to ask him and maybe he can help you out.
Click to expand...
Click to collapse
i tried to take a deeper look into the exynos 7870 64bit vendor and seems like app_process64 support needs to be added to init.rc (which is in ramdisk).
i tried looking up how to edit the init.rc but only found older tutorials and the tools ive tried wont extract the ramdisk from the boot.img (saying that its missing or smth). so thats going to be the hardest thing...
Pankiefield said:
i tried to take a deeper look into the exynos 7870 64bit vendor and seems like app_process64 support needs to be added to init.rc (which is in ramdisk).
i tried looking up how to edit the init.rc but only found older tutorials and the tools ive tried wont extract the ramdisk from the boot.img (saying that its missing or smth). so thats going to be the hardest thing...
Click to expand...
Click to collapse
Have you tried using ClassyKitchen? https://forum.xda-developers.com/chef-central/android/tool-classykitchen-android-roms-t3862584
Pankiefield said:
i tried to take a deeper look into the exynos 7870 64bit vendor and seems like app_process64 support needs to be added to init.rc (which is in ramdisk).
i tried looking up how to edit the init.rc but only found older tutorials and the tools ive tried wont extract the ramdisk from the boot.img (saying that its missing or smth). so thats going to be the hardest thing...
Click to expand...
Click to collapse
I think ramdisk may already be in the system (system-as-root device).
Check inside system to see if you have something like init.rc and stuff
ShaDisNX255 said:
I think ramdisk may already be in the system (system-as-root device).
Check inside system to see if you have something like init.rc and stuff
Click to expand...
Click to collapse
but when installing a gsi, system partition would be overwritten, it wouldnt make sense to edit it then.
or do you mean system_root?
Pankiefield said:
but when installing a gsi, system partition would be overwritten, it wouldnt make sense to edit it then.
or do you mean system_root?
Click to expand...
Click to collapse
Yes, I mean system_root
ShaDisNX255 said:
Yes, I mean system_root
Click to expand...
Click to collapse
almost finished my vendor, but cant test it, because the vendor partition is too small.
i searched for a way to resize it but no luck
also, i think theres no zygote stuff that needs to be edited, besides zygote type in default.prop, due to the device being a lot newer than the exy 7870 devices