Related
After a few headaches and some claps on the forehead i finished a very alpha build of CM9 for the IDEOS X5. It was ported from the Galaxy W port of arco68 with the files of Aurora ICS and this guide.
I don't know the bugs, so please PM me if you find a bug.
NOTE: I think i am only too stupid to sign a zip, so you have to sign it by yourselves or toggle verification in the recovery.
Download
Mediafire
Thanks to fjsferreira for re-packung the boot.umg
Thanks to dzo for Aurora ICS
Thanks to arco68 for the Galaxy W ICS port
Thanks ti freeeyourandroid.com for the porting guide
alex1301 said:
After a few headaches and some claps on the forehead i finished a very alpha build of CM9 for the IDEOS X5. It was ported from the Galaxy W port of arco68 with the files of Aurora ICS and this guide.
I don't know the bugs, so please PM me if you find a bug.
NOTE: I think i am only too stupid to sign a zip, so you have to sign it by yourselves or toggle verification in the recovery.
Download
Mediafire
Thanks to fjsferreira for re-packung the boot.umg
Thanks to dzo for Aurora ICS
Thanks to arco68 for the Galaxy W ICS port
Thanks ti freeeyourandroid.com for the porting guide
Click to expand...
Click to collapse
Can't flash it, starts but then getting error and no message as the phone reboots. First time ever it has done something like this and my heart skipped...
cirnocirno said:
Can't flash it, starts but then getting error and no message as the phone reboots. First time ever it has done something like this and my heart skipped...
Click to expand...
Click to collapse
Did you toggle signature verification first?
Is there any chance for u8800pro?
Sent from my u8800pro using XDA
... finished a very alpha build of CM9 .....
Click to expand...
Click to collapse
Please go to advance edition and put a big ALPHA warning in the title thread.
why? is it that bad?
have you tyed? whats working and not?
thanks for ypu effort alex1301
r1c4rd0 said:
why? is it that bad?
have you tyed? whats working and not?
thanks for ypu effort alex1301
Click to expand...
Click to collapse
Alpha is not bad nor good, just a phase of software development. Please confirm the rom is working, otherwise I will move it to general section.
poyensa said:
Alpha is not bad nor good, just a phase of software development. Please confirm the rom is working, otherwise I will move it to general section.
Click to expand...
Click to collapse
i´m downloading it right now, and will test it in one hour and i will say someting here...
It doesn't install, always Error status 6 in CWM. I replaced the METAINF folder in the zip with aurora, and changed the name of the zip itself, then it installs, but doesn't boot...
Next, I replaced the boot.img inside with the 3.0.8_v2 from DZO, then it boots but never goes further than boot animation
It is not rom development if you just switch some of the files, compress the file into a .zip and post it here.
Can anyone have a look at it and help me? I think the problen is the updater script, because i've only copied the one from aurora.
Sent from my SGH-T989 using xda premium
I will do a port from desire z
Sent from my SGH-T989 using xda premium
will test it soon btw yeah port from desire z would be better.
i have only one problem. the guide says the Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
but when i take the boot.img-kernel from the unpacked aurora boot.img, it has 2,6 mb, but when i rename the packed boot.img from aurora to boot.img-kernel it has 3.0 mb. which one should i take?
alex1301 said:
i have only one problem. the guide says the Easiest way to replace the kernel is to take a kernel update zip for your device, un-zip it and rename the zImage file to "boot.img-kernel" and copy and replace the file of the same name in your directory.
but when i take the boot.img-kernel from the unpacked aurora boot.img, it has 2,6 mb, but when i rename the packed boot.img from aurora to boot.img-kernel it has 3.0 mb. which one should i take?
Click to expand...
Click to collapse
Boot.img is ramdisk and kernel, compiled into one. You need kernel.
Unpack both boot images, replace kernel with auroras and change init.rc scripts to mount the correct partitions.
On mobile now so can't give a tutorial.
Sent from my U8800 using Tapatalk 2 Beta-5
the guide i follow says, that i only have to rename the init.devicename.rc to init.huawei.rc. should i also change the init.rc to the one of aurora?
does anyone have the mkbootimg for the X5?
alex1301 said:
does anyone have the mkbootimg for the X5?
Click to expand...
Click to collapse
We don't need to have any device specific mkbootimg, any mkbootimg will do it just fine
Sent from my U8800 using Tapatalk 2 Beta-5
i've uploaded a new version. it's ported from the desire z, but i think it's too big for the x5. i can't upload it to mediafire, because it doesn't load my files correct. so i only can upload it to dropbox, but there is also a limitation of downloads. http://db.tt/u8PrGM5m
alex1301 said:
i've uploaded a new version. it's ported from the desire z, but i think it's too big for the x5. i can't upload it to mediafire, because it doesn't load my files correct. so i only can upload it to dropbox, but there is also a limitation of downloads. http://db.tt/u8PrGM5m
Click to expand...
Click to collapse
Can you confirm this one boots?
Sent from my U8800
Easiest and best way to port CM7,CM9,CM10 Based ROMs to HTC Aria/Intruder/Gratia
Code:
I do not guarantee any successful porting.
I am not responsible for [B]bricked devices, dead SD cards, or a broken device[/B].
[B]YOU[/B] are choosing to make these modifications,
and if you point the finger at me for messing up your device,
I will laugh at you.
->Copied from some xda thread.
*****
But a rom, no matter how bad should *not* do any physical non recoverable harm to your device,flashing a rom or restoring a nandroid backup via cwm *should* immediately fix any problems what so ever.
And I will try to help in any ways I can.
I am NOT a developer, I can not code,compile,etc, I am only an android enthusiast with half a brain able to follow specific instructions.
This guide is actually somewhat a good combination of various "how to port roms"
guides found here on xda suited and very slightly modified for our beloved Aria.
Thanks to all of those threads and their writers.
Click to expand...
Click to collapse
Actual Tutorial starts here:
I will try to make this guide as straight forward as possible.
PORT ROM:
First you need to figure out what rom you are going to be porting.
For our Aria, The rom you want to port should belong to a device that has:
HTC brand (optional but recommended)
A ArmV6 CPU (VVVV important)
A HVGA Resolution (optional, any mdpi should do,if not just open the system apk files using 7zip and resize all the BIG images.)
The Rom needs to be:
CM7 BASED OR CM10 BASED OR CM9 BASED.
The full zip size less than 150MB(Recommended).
What Does Port Mean:
This simply refers to the rom you will be trying to port.
Recommended device to port from is the HTC Wildfire S a.k.a Marvel.
But any other device
BASE ROM:
What Does Based Mean:
It means that the rom should have similar sources and stuff,
Meaning you can only attempt to port a android 2.3 rom if you already have a 2.3 rom on the device.(In our case cm7).
So,
For porting 2.3 roms, chose cyanogenmod 7.2 as BASE.
For porting 4.0 roms, chose cyanogenmod 9 as BASE.
For porting 4.1 roms, chose cyanogenmod 10 as BASE.
ETC... I hope you get the point.
:fingers-crossed:
Thing you will need:
A good Zip extractor and compressor. (I use 7zip, its free. If you have winrar or something else,it will also do.)
Notepad++ (This thingy is awesome! And you need it for some stuff)
Android SDK(Not the whole thing, just adb zip from our sticky thread will do.)
Some Basic Android Knowledge, Root knowledge.
Mostly Common Sense.
Click to expand...
Click to collapse
Step 1:
Extract our device rom zip and name the folder AriaRom,
Extract our Port rom zip and name the folder PortRom.
Step 2:
Delete the following folders on the AriaRom/system folder:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
Step 3:
Go to
Code:
PortRom folder/system
and copy:
App(You can keep some non conflicting indepent apps if you want)
Framework
Fonts
Media
and then paste them to AriaRom/system.
Step 4:
You need to open these two folders side by side(on windows, open both folders then right click on the task bar and click "Tile windows vertically").
The two Folders are:
Code:
[LIST]
[*]AriaRom/system/etc
[*]PortRom/system/etc
[/LIST]
In
Code:
etc/permission
folder copy all the permissions files in PortRom to your AriaROM folder except
Code:
platform
handheld_hardware
Then open init.d Folder in AriaRom and Delete Everything except
Code:
banner
and then copy all the files inside init.d folder of PortRom to init.d folder of AriaRom.
Step 5:
Now
Code:
AriaRom/system/buid.prop
and
PortRom/system/buid.prop
files using Notepad++
On AriaRom Build.prop make changes as you wish.
Code:
[LIST]
[*]ro.build.id=
[*]ro.build.display.id=
[*]ro.build.date=
[*]ro.modversion=
[/LIST]
Copy and replace these values from PortRom buildprop to Aria rom buildprop.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
Also Copy anything you Find Extra and important-ish in ADDITIONAL BUILD PROPERTIES using common sense.(Not much major stuff, but if bootlooped, copy whole thingy.)
IMPORTANT Step of commons sense:
Open up both
Code:
META-INF/com/google/android/updater-script
using Notepad++.
Compare AriaRom AND PortRom line by line(on two tabs in notepad++ easily done).
Copy extra/additional lines from PortRom which are not present in AriaRom to aria roms updater script.
Step 6:
If You find any extra file or folder in system folder of PORTrom than copy them to your Ariarom system folder.
Finally, zip the
Code:
META-INF
system
boot.img
data(if exists).
folders/files togather and use "normal" compression if asked.
Name the zip to whatever you want, and walla you have successfully ported the rom!
:fingers-crossed:
Doing the above steps should land you a pretty solid rom, as solid as the base rom.
Still,Incase of problems:
If the ported rom does not boot:
Stuck at boot screen
Bootlooping
Then copy system/lib/
Code:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
files from PortRom to AriaRom system/lib.
It should boot, if it still doesnt, check the above steps and find out what you did wrong.
Common reasons could be:
Build.prop mess up
Updater Script mess up
Forgot to delete or copy file
After it boots,
Everything that worked on Base rom, should work on Ported.
Every problem on Base Rom will exist on Ported.
In case of root related problems(settings not being saved,system app FCs,etc), install a root app like titanium backup or something and check if it works,if it doesnt its surely root issue,just download and flash latest superuser zip.
If some FC,Port rom funciton not working,etc issues appear, you need to decompile framework-res.apk using apktool and change device specific xml files to ours.This is a part where I have the most trouble and suck at.
Just search xda for
How to Logcat,
Click to expand...
Click to collapse
this will help you to find the problems and search xda to solve them. Ask me if you want on this thread, & I will try to help, but I dont think I will be able to help much as I have very limited knowledge on compile De-compile stuff.
If someone is good at framework-res and framework decompile & recompile stuff, please help us.
Click to expand...
Click to collapse
Thanks for reading this,I hope you port over some awesome roms to our device.
:highfive:
I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...
dansou901 said:
I just tried to port the PACman ROM from Samsung Galaxy Ace to the Aria, but I am stuck at boot screen after following your tut, which is awesome by the way. Could you post a working build.prop and updater-script for this ROM? Maybe this will help me get it booting...
Click to expand...
Click to collapse
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Why are SMARTphones soo... Freaking Dumb?
sifat3d said:
That's an Armv7 device.
Still I'm gonna download it & try.
In the meantime take a look at bootclass path.
Click to expand...
Click to collapse
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.
hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )
rami.ejle said:
hey man thnx for the tut but i tried porting the paranoid rom like you but i keep getting this error while flashing ( set_perm: some changes failed) i think it have something to do with the updater-script, could u upload the build.prop and the updater-script for me ? and btw why do we need the sdk ??
---------- Post added at 02:43 AM ---------- Previous post was at 02:03 AM ----------
actually now i tried not to change the updater-script and the rom flashed but stock at boot pleaaase help me i really want to try the paranoid rom (ive been trying to port the "pa_marvel-2.54-beta1-08NOV2012-164651" )
Click to expand...
Click to collapse
Here you go,
http://pastebin.com/62hbaQwL
on THAT ROM,
IF you follow the guide & use my posted script,
100% assurance rom will boot and work. except cm
The sdk is for getting the logcat when a problem occurs.
Why are SMARTphones soo... Freaking Dumb?
Nice tut very well done
XDA Moderator
dansou901 said:
I don't think so... the Samsung Galaxy Ace with device number S5830 should be Armv6, but in the Galaxy Ace Forums there is also a place for the Galaxy Ace II, which is Armv7. Maybe that's a bit confusing. But nims11 PAC-Man Rom is definitely for the Armv6 device.
Click to expand...
Click to collapse
In that case you'll need to unpack both boot.img aka the kernel , fix bootclass path in init.RC by replacing it with the value from port roms init.rc.
Ill try to port that rom soon and upload a fixed boot.img (if I can get it to boot),if you don't beat me to it. it looks cool.
Why are SMARTphones soo... Freaking Dumb?
Bootclasspath is the same on both roms. So there must be a mistake in updater-script and / or build.prop. I've just messed up my updater-script, I guess, so I'll make a new one and post it later together with the build.prop.
I got this pac rom booting & everything operational except per app dpi(exists in port rom).
This rom works with the guide.
http://forum.xda-developers.com/showthread.php?t=2118567
Why are SMARTphones soo... Freaking Dumb?
I'll try this and let you know if it worked.
Hi guys,
If you only want per app dpi,persistent apps,etc
Try this on winsuk bros cm10
http://forum.xda-developers.com/showthread.php?t=1574401
Its quite good.
...Devided by zero
dansou901 said:
I'll try this and let you know if it worked.
Click to expand...
Click to collapse
btw,
did it work?
...Devided by zero
Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.
dansou901 said:
Sadly, I didn't get any time to try so far. But on Sunday I lost my Gratia, so I won't continue this project; I've upgraded to the HTC Desire X.
Click to expand...
Click to collapse
That's a shame. Similar thing happened to me. I lost my Aria right before i had a chance to try this, and upgraded to the Nexus 4.
will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??
Could work, just try... I would do it if I still had the phone...
dansou901 said:
Could work, just try... I would do it if I still had the phone...
Click to expand...
Click to collapse
rami.ejle said:
will this method work on cm10.1 and this http://forum.xda-developers.com/showthread.php?t=2297580 ??
Click to expand...
Click to collapse
It should pretty much work,
If it doesnt, just send me the
Updater script
Build.prop
files of BOTH roms, And I'll have a look.
I wouldve tried myself but my aria has no network and has random reboot issues due to falling hard.
I can see this version has been made available to some other devices, like the N7, but I can't find any version for the N4, anyone know if it's available yet?
You can get it here from the CWM builder:
http://jenkins.cyanogenmod.com/job/recovery/32462/artifact/archive/recovery.img
Ok, I'd like to know how Jenkins works (appreciated you sent me a link though). How do I find the recovery for a specific device, all I see is what appears to be md5 sums
http://builder.clockworkmod.com/
Click on existing device, choose mako and touch recovery and it builds CWM for the mako uing the latest code. If there is already one built it gives the link (like above)
EddyOS said:
http://builder.clockworkmod.com/
Click on existing device, choose mako and touch recovery and it builds CWM for the mako uing the latest code. If there is already one built it gives the link (like above)
Click to expand...
Click to collapse
Much appreciated! :good:
Sorry, this thread is now closed.
I would suggest you to move this thread to the General Disucssion section
Moved.
well I think I found a bug so twrp thinks there is no os installed and the browser doesnt work and when you try to flash gapps for 7.1 it doesnt work how do we fix this
williambright80 said:
well I think I found a bug so twrp thinks there is no os installed and the browser doesnt work and when you try to flash gapps for 7.1 it doesnt work how do we fix this
Click to expand...
Click to collapse
For which ROM u talking about?? Aosp espressos'
Kunal Gautam said:
For which ROM u talking about?? Aosp espressos'
Click to expand...
Click to collapse
yes
TWRP :-OK it isn't that severe to be called a bug
GApps:- I know its a problem with the ROM that it doesn't deal with opengapps but still you can try PA GApps they are working fine with the ROM.
Thanks
Kunal Gautam said:
TWRP :-OK it isn't that severe to be called a bug
GApps:- I know its a problem with the ROM that it doesn't deal with opengapps but still you can try PA GApps they are working fine with the ROM.
Thanks
Click to expand...
Click to collapse
which gapps
link me to 7.1 ROM you promised, ty.
Boscep said:
link me to 7.1 ROM you promised, ty.
Click to expand...
Click to collapse
here is the link to 7.1 https://builds.unlegacy-android.org/aosp-7.1/espresso/ua_espresso-7.1.1-20170227.zip
Is this for pad 2 gt-p5100
JPSimon said:
Is this for pad 2 gt-p5100
Click to expand...
Click to collapse
Yes but to avoid confusion please call it by galaxy tab 2 10.1
hello @CCD
how are you?
comeback pls
tab 2 needs more dev, ty.
UPDATE 2.0
Builds are almost ready CM 14.1 once my exams are completed will start to test them.... Dont know why but still camera bug carry on almost no lags..... + CyanogenMod Features....
JPSimon said:
Is this for pad 2 gt-p5100
Click to expand...
Click to collapse
It could be but right now i haven't updated my device tree
For P3100's right now but i will do it soon but it could be faster if you could help me updating
williambright80 said:
which gapps
Click to expand...
Click to collapse
Sorry my mistake PA Gapps are now discontinued instead of them you could download dynamic gapps
Link-https://forum.xda-developers.com/android/software/gapps-dynamic-gapps-t3487192
Kunal Gautam said:
Introduction
At the end of 2016 I started to seek nougats for Tab 2, found AOSP by Ziyan and Android - Andi
flashed it, examined it, Discontinued it......
Here we gonna discuss it.
What is the need?
Tab 2 was released in 2012 and in mid 2014 was discontinued by Samsung thus resulted to get this to be called OLD but in my eyes its still new with great potential and great reliability so I just want to keep this device alive till 2019. So that's the reason....
CURRENT STATE
Nougat development is doing well and with the help of you I can or all devs can make it better.....
So just because of this learned porting and started porting, successfully ported 4 out 5 ROMs will upload them all......
DEVELOPING CIRCLE
Roms that are being supported by me are :-
AOSP
Lineage OS
AICP
Resurrection Remix
Thanks To @[email protected]
SlimKat Roms
CyanogenMod
LineageOS
You
Me of course
Click to expand...
Click to collapse
So hey, i'm nee to this forum and rooting in general but i will glad if some of you could help me out of this, here's the deal: i saw that AOSP roms are the best for performance (right?) and i also want the lastet version of android so that rom fit perfectly my needs, where i can download it? And is compatibile with my tab 2 10.1 WiFi only? Also where the hell is the guide to root that Device, i saw it once and i never found it back... (yeah i'm probably stupid)
LordReaperIV said:
So hey, i'm nee to this forum and rooting in general but i will glad if some of you could help me out of this, here's the deal: i saw that AOSP roms are the best for performance (right?) and i also want the lastet version of android so that rom fit perfectly my needs, where i can download it? And is compatibile with my tab 2 10.1 WiFi only? Also where the hell is the guide to root that Device, i saw it once and i never found it back... (yeah i'm probably stupid)
Click to expand...
Click to collapse
No need for guide
Steps
1. Download KingRoot.
2. Install it.
3. Root your device with it.
4. Enjoy
TO INSTALL CUSTOM RECOVERY TO INSTALL CUSTOM ROMS
1. Download official TWRP app from the Play Store.
2. Install recovery using the information on the screen.
INSTALL THE MODDED RECOVERY PLZ IF YOU DONT WANT TO GET YOU DEVICE BRICKED
1. Go to google search andi github
2. Open it
3. Go to the recovery section and then in TWRP download the common recovery and install the downloaded recovery using the current TWRP recovery
And AOSP are good but actually for Tab 2 it is really unstable right now. But if you really want to install it
Just go in the Tab 2 Development section
The AOSP must on top there will be links to the website
Just go to directory when you visit downloading website
AOSP 7.1/espresso/Download the latest one
And just copy to you device
Then go to the recovery (Power + Volume Up)
Then go into wipe/anvanced
Select
1. DALVIK
2. CACHE
3. SYSTEM
4. DATA
Then wipe
Then install the Rom
TADA Done than just reboot.
Kunal Gautam said:
No need for guide
Steps
1. Download KingRoot.
2. Install it.
3. Root your device with it.
4. Enjoy
TO INSTALL CUSTOM RECOVERY TO INSTALL CUSTOM ROMS
1. Download official TWRP app from the Play Store.
2. Install recovery using the information on the screen.
INSTALL THE MODDED RECOVERY PLZ IF YOU DONT WANT TO GET YOU DEVICE BRICKED
1. Go to google search andi github
2. Open it
3. Go to the recovery section and then in TWRP download the common recovery and install the downloaded recovery using the current TWRP recovery
And AOSP are good but actually for Tab 2 it is really unstable right now. But if you really want to install it
Just go in the Tab 2 Development section
The AOSP must on top there will be links to the website
Just go to directory when you visit downloading website
AOSP 7.1/espresso/Download the latest one
And just copy to you device
Then go to the recovery (Power + Volume Up)
Then go into wipe/anvanced
Select
1. DALVIK
2. CACHE
3. SYSTEM
4. DATA
Then wipe
Then install the Rom
TADA Done than just reboot.
Click to expand...
Click to collapse
Awesome dude, thanks for the tips, i'll wait that my tabet charge will be over 80% (just for safety) and the i'll root it. I downloaded both ".tar.md5" and ".zip" file but when i go to choose the file with TWRP in the directory that i put them, the app explorer don't see them... -> update, the TWRP app let me see only the 2..8.5.0 version of recovery, while the site on github start from 3.x.x.x. also i tried to flash the img files extracted from the 3.x.x.x. recoveries and it told me "flash failed".
Also my Galaxy Tab 2 just crashed while rooting with Kingroot (it was trying the could method) -> EDIT: i reset it and when i open the kingroot app it start from where it left , it was a "crash" because the stock rom have not the reboot function?
BTW i thought, you said that galaxy tab 2 is unstable, but i remember that the first stock rom was very well optimized with no lag, then i updated it via samsung and then it come to lag and IT IS VERY SLOW. so you mean that installing a custom rom will not solve the problem?
[b]"need alpha testers for cm 14.1"[/b]
Alpha testers wanted for CM 14.1
1st Build releasing today.. Stay Tuned!!!
We currently don't have a custom ROM for the A20,
but it would be the next logical step.
If someone could develop a custom ROM it would raise our status in the xda community.
Useful links.
1. Android ROM development from source to end.
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
2. Building AOSP.
https://source.android.com/setup/build/requirements
3. Easy guide?
https://forum.xda-developers.com/showthread.php?t=2195858
4. Custom Rom Builder
https://forum.xda-developers.com/chef-central/android/tool-custom-rom-builder-t3947779
5. Android Kitchen.
https://forum.xda-developers.com/showthread.php?t=633246
6. SuperR's Kitchen.
https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Post 3
physwizz said:
We currently don't have a custom ROM for the A20,
but it would be the next logical step.
If someone could develop a custom ROM it would raise our status in the xda community.
Click to expand...
Click to collapse
Without the support from USA device owners and them being left out from rooting played a huge factor.
The Motog7power just got Lineage OS 16.
Twrp was done weeks ago. Buy a Motorola.
jhjhjhjhjhjh said:
Without the support from USA device owners and them being left out from rooting played a huge factor.
The Motog7power just got Lineage OS 16.
Twrp was done weeks ago. Buy a Motorola.
Click to expand...
Click to collapse
Yes. It has left us at a great disadvantage without you guys.
I tried Android Kitchen.
https://forum.xda-developers.com/showthread.php?t=633246
Made a ROM zip from my system.img and boot.img
Got updater error when installing.
physwizz said:
I tried Android Kitchen.
https://forum.xda-developers.com/showthread.php?t=633246
Made a ROM zip from my system.img and boot.img
Got updater error when installing.
Click to expand...
Click to collapse
Last update seems to be from 2013, i don't think that is compatible with Android Pie.
I recommend you to use SuperR's Kitchen (free version is only available for Linux, to use it on Windows you need to buy the full version).
TBM 13 said:
Last update seems to be from 2013, i don't think that is compatible with Android Pie.
I recommend you to use SuperR's Kitchen (free version is only available for Linux, to use it on Windows you need to buy the full version).
Click to expand...
Click to collapse
Should work on my Mac
TBM 13 said:
Last update seems to be from 2013, i don't think that is compatible with Android Pie.
I recommend you to use SuperR's Kitchen (free version is only available for Linux, to use it on Windows you need to buy the full version).
Click to expand...
Click to collapse
Couldn't execute binary on the Mac, but I got it running on a Linux virtual box.
physwizz said:
Couldn't execute binary on the Mac, but I got it running on a Linux virtual box.
Click to expand...
Click to collapse
Cool ... please keep us posted on any progress you make I will also take a look into a possible build for our phone.
Peace
....The box said to install under Windows 2000 or better ... so I installed it on Linux
Thibor69 said:
Cool ... please keep us posted on any progress you make I will also take a look into a possible build for our phone.
Peace
....The box said to install under Windows 2000 or better ... so I installed it on Linux
Click to expand...
Click to collapse
I just flashed a zip I cooked that was made from the patched boot and the stock system.img
No luck there.
Back to the drawing board.
physwizz said:
I just flashed a zip I cooked that was made from the patched boot and the stock system.img
No luck there.
Back to the drawing board.
Click to expand...
Click to collapse
Stuck at boot animation?
Any logs?
TBM 13 said:
Stuck at boot animation?
Any logs?
Click to expand...
Click to collapse
I'm going to try a non-stock system.img
physwizz said:
I'm going to try a non-stock system.img
Click to expand...
Click to collapse
How is it going for you, i try modding a GSI System.img but it also bootloops, i also try creating a EXT4 Img but it gives me system partition sizes error.
LietRell said:
How is it going for you, i try modding a GSI System.img but it also bootloops, i also try creating a EXT4 Img but it gives me system partition sizes error.
Click to expand...
Click to collapse
still working on it.
No luck yet
physwizz said:
still working on it.
No luck yet
Click to expand...
Click to collapse
Were all hoping to get a working custom rom for this device, Keep up bro. Thanks for trying
Seems like all the GSI ROMs break some hardware functionality at this stage so the best option for now is to root and debloat stock and load your own preferred apps in place of the Samsung / Google ones. Not quite a "Custom" ROM but makes for a pleasant enough phone that you can tolerate much more than the horror of stock.
Now a custom kernel to clock our severely crippled SoC back to its full glory would be a thing to smile about
LietRell said:
How is it going for you, i try modding a GSI System.img but it also bootloops, i also try creating a EXT4 Img but it gives me system partition sizes error.
Click to expand...
Click to collapse
My GSI based ROM gives me an error:7 during installation
physwizz said:
My GSI based ROM gives me an error:7 during installation
Click to expand...
Click to collapse
I think that's because you have to add the device in 8)Room tools, 4)Asserts menu, 1)Add/remove device, then try adding the device, in my case i added "a20,a205g", i don't really know what device name TWRP reads
LietRell said:
I think that's because you have to add the device in 8)Room tools, 4)Asserts menu, 1)Add/remove device, then try adding the device, in my case i added "a20,a205g", i don't really know what device name TWRP reads
Click to expand...
Click to collapse
When I flashed as A20, it told me the device was a20.
I added just a20. It flashed but froze on the Samsung screen.
Progress.
It's all a learning experience.
I also found this on GitHub.
https://github.com/alwayslivid/android_kernel_samsung_a202f
https://github.com/alwayslivid/android_platform_samsung_a202f
From Open Source Samsung.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=A20