I am completely new to Android Engineering and want to learn it. Till now, I have tried building aosp oreo from repo. It is built successfully but I don't know about the use of all the folders that are downloaded by the repo. What is the use or importance of each folder in repo? Where can I learn more about this?
I have also modified my stock firmware (only removed some bloatware apps) and rebuilt the firmware. I haven't installed it yet. I used android kitchen which helped me with signing the zip but I am afraid the signature might be for testing and not the official vendor signature. I have phone with unlcoked bootloader but it's still on stock recovery. According to my knowledge, unlocking bootloader helps us to flash unofficial files but people at XDA say that we should also have custom recovery to flash custom ROMs. Should I flash the modified ROM built by me in device with stock ROM and unlocked bootloader?
My device doesn't have official TWRP support. How can I port recovery or build it from scratch for my phone?
Also, I have only modified stock ROM and need to learn porting ROMs like porting MIUI for my device. How can we port ROMs?
Sorry for asking all these at once but I tried getting answer one after another which confused me a lot. I am a noob in this field.
I read XDA thread of TWRP developer which included a guide on how to build TWRP for any device. But as the author said, that post wasn't for noobs. Maybe I need to learn a lot before I reach that level of understanding. But I don't know what to learn and from where. Please help..
And one last thing - What is a device tree? Or vendor tree? I saw these words many times when I was trying to understand the above things. But I still don't know what these are and Google doesn't help. Thank you everyone..
Hi
there is this section here https://forum.xda-developers.com/android/software
you`ll find some sticky threads of the top with plenty of info , have a look !
you may also use search and type XDA University , it will reveal also some useful links
Good luck !
Related
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Ain't nobody is going to help you ^^ I am looking for that kind of knowledge too. I would like to start building roms from source and make some modifications to CM10's kernel
check out Legion modz team thread
it has a little info on it
http://forum.xda-developers.com/showthread.php?t=2314836
and make google your best friend
so much way to take...
theabnormalguy said:
Hello there forum users! This thread was created with the sole purpose of helping me (and others) find out how to build ROMs for unsupported devices.
Basically, I've built AOKP from source, but the device I was building for was already supported. What I'm trying to do now if build Dirty Unicorns 4.2.2 for my device, which is not supported by the ROM. From what I've read, I've already forked the "vendor_du", "
android_device_samsung_vibrantmtd", "vendor_samsung", "proprietary_vendor_samsung", "android_hardware_samsung", "android_packages_apps_SamsungServiceMode", and "android_build".
My github account is MaxusPrimus
How do I build the ROM for the Samsung Vibrant T959, when it is not supported. If someone has miraculously found a post that I have missed, I would appreciate it very much. Additionally, a list of commands and explanations would greatly assist me. I'm pretty new to the whole Android building thing so I thank you all for help!
Click to expand...
Click to collapse
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
---------- Post added at 08:51 PM ---------- Previous post was at 08:09 PM ----------
flipinfin said:
Im starting to learn to build from source. Theres many tutorials on how to get started. Ill post links when I get to my pc later. First I would get the source code for kernel on samsung. If not available get stock rom to dump required files aswell as other files needed. I dont know if this will guide you in the right direction. Just keep in mind and always remember the kernel hardware devices is different then the operating system. You juz need to learn google how to merge the to.
Click to expand...
Click to collapse
Heres some starting links that im using starting to build from source. the samsung open source page look for your model number http://opensource.samsung.com. Obviously. you can build your own kernel.
how to unpack repack img http://forum.xda-developers.com/showthread.php?t=1081239
http://www.kandroid.org/online-pdk/guide/index.html very useful link aswell as this one http://source.android.com/source/initializing.html.
heres a link to identify partition tables http://forum.xda-developers.com/showthread.php?t=1959445. . Heres another link that you prolly can pull files from if needed http://www.teamandroid.com/2013/04/...kp-build-6-android-422-jelly-bean-custom-rom/
Dont take this the wrong way but i think your getting confused how roms kernels etc r built its all open source. That rom is based off of jelly bean and alls they did was change the name. Though its open source so i would assume you can repo the rom at https://github.com/. In addition if i was you i would download the rom "which you prolly already have and do some investigating.. heres another useful link http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code. Never forget google is your best friend. Fogot to mention if you aint on linux i would switch os real soon. I think this link will be ver ver very helpful https://bitbucket.org/bigwillyg/buttered_toast_shooter
Is that Vibrant T-Mobile ? cuz if it is http://aokp.co/devices/vibrantmtd theres your starting point
I am really confused! I went through a lot of threads and forums. Unfortunately i can't get some of the concepts....
Can someone give me a roadmap on how to get started with compiling android roms(not custom roms)
How do OEMs like Samsung, HTC compile their ROMs??? I mean where do they learn that the particular process should be done this way regarding Android firmware???
In Repo Sync, is it possible to pause and resume that huge download? If i want to reinstall linux, is it possible to backup that 30-40GB download???
I have Asus Fonepad 7 and has kernel sources here: http://www.asus.com/support/Download/28/7/0/7/K0zj5cW6VJEzTjQR/32/ My question is am i able to create stock Android ROMs like those in Nexus devices and fastboot images for flashing on to this device??? Also do x86 devices have a different way of compiling ROM???
I want to do things the original official way... Please help me, I am very eager to learn!!!
I would be more than happy if someone could help!!!
Redmi note 3 ROM Uploaders please read!
I have been flashing stock roms for a few years now and I have noticed with this device that many of the uploaders are not providing all the details just some of the following:
Detailed description
Is bootloader to be unlocked first
Is a custom recovery needed
Full instructions on how to install
Screenshots
bug list
Which Gapps package to use
Please provide all (the above) the neccessary information so we can make the decision is this ROM good for us to flash on our phones.
There needs to be a template for ROM postings so it can be easy for the end users. (Forum moderators will know the formula so I ask ye guys to sticky a template)
Thank you (ordered mine 3 days ago come on gearbest I wants my precioussss)
rslatara said:
Redmi note 3 ROM Uploaders please read!
I have been flashing stock roms for a few years now and I have noticed with this device that many of the uploaders are not providing all the details just some of the following:
Detailed description
Is bootloader to be unlocked first
Is a custom recovery needed
Full instructions on how to install
Screenshots
bug list
Which Gapps package to use
Please provide all (the above) the neccessary information so we can make the decision is this ROM good for us to flash on our phones.
There needs to be a template for ROM postings so it can be easy for the end users. (Forum moderators will know the formula so I ask ye guys to sticky a template)
Thank you (ordered mine 3 days ago come on gearbest I wants my precioussss)
Click to expand...
Click to collapse
First thing, its not stock rom, its custom rom.
Second, the developers are not being paid, and thus whatever thay are doing, just accept it and ask for help, not post post like this to command them to list things that are obviously common sense.
1. CM13 Nightly, this 2 words give enough description, what more do you need. In this time, if you don't know what cm13 is then don't buy an android. Nightly means that there are still bugs, both minor and major, and sometimes it means that there are some things broken too. The devs also list whats working or whats not. They can't list every single thing.
2. You are flashing custom rom, thus you must have custom recovery like twrp, in order to install it you must first unlock your bootloader. If you have custom recovery, then it doesn't matter whether your bootloader is unlocked or not.
3. Did you really just asked if custom recovery is needed, are you a fool or what. Let me make this clear, if you want to flash a rom, how are you supports to so without a custom recovery. Stock recovery can't flash rom, neither it can make backup, restore backup and lots of things. The most basic thing to do even before rooting is to flash a custom recovery. Without custom recovery you can't even properly root. Well you can root with some apps, but custom recovery makes it easier, just download supersu and flash it with recovery.
4. Whats there to know. If you have custom recovery, then first create a backup. Almost every thread that i have ever read on xda, it is stated every where to always make a backup before doing anything, even rooting. Then, wipe data cache dalvik system, and then flash the zip file. After that if you wish flash the gapps.
5. What do you need screenshot for. Haven't you ever saw CM13 or ressurection remix. Just google it. they are not obliged to post it here for your convenience.
6. They do provide bugs, whats working or what not. And its not like they know a bug and haven't told other about it. They, in most cases don't know how many bugs there are, the other users tell them the bugs and they fix it.
7. Why would they tell you which gapps package to use. Do they work for google. Anyway, just google gapps, your rom version, ie cm12 or cm13, you mob architecture, arm64 or arm32 or whatever, and just download it. There is no geek stuff behind it that you can't do it yourself.
And finally, you are not paying them do anything, they are doing this because they like doing this. They are not even getting paid by this. So you ordering them to these things which you can do yourself after some googling and using your brain a bit, is just unjust. Just accept what they are doing, thank them, enjoy the rom, and report the bugs, etc etc, and have fun.
archit.bajpai.ab said:
First thing, its not stock rom, its custom rom.
Second, the developers are not being paid, and thus whatever thay are doing, just accept it and ask for help, not post post like this to command them to list things that are obviously common sense.
1. CM13 Nightly, this 2 words give enough description, what more do you need. In this time, if you don't know what cm13 is then don't buy an android. Nightly means that there are still bugs, both minor and major, and sometimes it means that there are some things broken too. The devs also list whats working or whats not. They can't list every single thing.
2. You are flashing custom rom, thus you must have custom recovery like twrp, in order to install it you must first unlock your bootloader. If you have custom recovery, then it doesn't matter whether your bootloader is unlocked or not.
3. Did you really just asked if custom recovery is needed, are you a fool or what. Let me make this clear, if you want to flash a rom, how are you supports to so without a custom recovery. Stock recovery can't flash rom, neither it can make backup, restore backup and lots of things. The most basic thing to do even before rooting is to flash a custom recovery. Without custom recovery you can't even properly root. Well you can root with some apps, but custom recovery makes it easier, just download supersu and flash it with recovery.
4. Whats there to know. If you have custom recovery, then first create a backup. Almost every thread that i have ever read on xda, it is stated every where to always make a backup before doing anything, even rooting. Then, wipe data cache dalvik system, and then flash the zip file. After that if you wish flash the gapps.
5. What do you need screenshot for. Haven't you ever saw CM13 or ressurection remix. Just google it. they are not obliged to post it here for your convenience.
6. They do provide bugs, whats working or what not. And its not like they know a bug and haven't told other about it. They, in most cases don't know how many bugs there are, the other users tell them the bugs and they fix it.
7. Why would they tell you which gapps package to use. Do they work for google. Anyway, just google gapps, your rom version, ie cm12 or cm13, you mob architecture, arm64 or arm32 or whatever, and just download it. There is no geek stuff behind it that you can't do it yourself.
And finally, you are not paying them do anything, they are doing this because they like doing this. They are not even getting paid by this. So you ordering them to these things which you can do yourself after some googling and using your brain a bit, is just unjust. Just accept what they are doing, thank them, enjoy the rom, and report the bugs, etc etc, and have fun.
Click to expand...
Click to collapse
1. I know what CM is this is about description not quick copy and pastes from another website.
2. Some modified roms can be ran from the stock recovery.
3. You are a fool this is information for the end user I will slap you with a fresh wet fish!
4. Information is key.
5. Screenshots show people what they are flashing very helpful to the end user
6. They don't always bub!
7. Again inofrmation helps to clarify lot's of things.
Not all the guys that post are the actual devs THAT DO IT RIGHT, some are just bad copy paste jobs coz they wanna be cool n **** and don't Fu(&ing tell me not use andorid you little pretend dev snot! :victory:
rslatara said:
1. I know what CM is this is about description not quick copy and pastes from another website.
2. Some modified roms can be ran from the stock recovery.
3. You are a fool this is information for the end user I will slap you with a fresh wet fish!
4. Information is key.
5. Screenshots show people what they are flashing very helpful to the end user
6. They don't always bub!
7. Again inofrmation helps to clarify lot's of things.
Not all the guys that post are the actual devs THAT DO IT RIGHT, some are just bad copy paste jobs coz they wanna be cool n **** and don't Fu(&ing tell me not use andorid you little pretend dev snot! :victory:
Click to expand...
Click to collapse
If you are using a 32bit windows, then do you ask others which application to install, 32bit or 64bit. Man you are a joke, it's not information, its common sense. information is which partition is used for what purpose. How to restore imei. How to unlock lte band, not which gapps to flash. And there is no stock recovery out ther which flash custom roms. The only roms you can flash with stock recovery are ota.
archit.bajpai.ab said:
If you are using a 32bit windows, then do you ask others which application to install, 32bit or 64bit. Man you are a joke, it's not information, its common sense. information is which partition is used for what purpose. How to restore imei. How to unlock lte band, not which gapps to flash. And there is no stock recovery out ther which flash custom roms. The only roms you can flash with stock recovery are ota.
Click to expand...
Click to collapse
Hey I am just a certified IT Technician working for the IT department of a mutlinational company what would I know and I spit on x86 always have..even my windows vista was x64 boi!!!!
rslatara said:
Hey I am just a certified IT Technician working for the IT department of a mutlinational company what would I know and I spit on x86 always have..even my windows vista was x64 boi!!!!
Click to expand...
Click to collapse
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
archit.bajpai.ab said:
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
Click to expand...
Click to collapse
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little and it's kinda lazy on the posters part.
That is all. I ain't a programmer (although i touched on some c++) but I ain't a noob just like details and not everyone is well informed and there a newbies to flashing roms it's to help them too not brick a device.
archit.bajpai.ab said:
So if you are not a noob then why are u asking for such things that are common sense. Nobody ask these things now. I just passed class 12 and i know most of the procedure for tweaking an android. I can even write partition table. You just have to search. Not post like this and expect the dev to post them too. Do a little bit more work to achieve something.
Click to expand...
Click to collapse
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little info and it's kinda lazy on the posters part.
I ain't a programmer (although i touched on some c++) but I ain't a noob, I just like details and not everyone is well informed and there a newbies to flashing roms it's to help them to not brick a device.
From what I see it's mostly non devs just copy paste guys who are doing it.
Does it hurt to have a small guide or at least the fundemntals of requrements for the installation of each rom?
Waiting on my redmi still order prcessing, hurry gearbest hurry I am back on my g510 as my asus went for a swim in my tiolet!
rslatara said:
Coming from a Huawei g510 where i got my roms on Modaco, and The zenfone 2 here at xda the posts were well put togther with all the info needed , I have found quiet a few here with very little and it's kinda lazy on the posters part.
That is all. I ain't a programmer (although i touched on some c++) but I ain't a noob just like details and not everyone is well informed and there a newbies to flashing roms it's to help them too not brick a device.
Click to expand...
Click to collapse
Nice idea, looks like there's no room for a newbie on XDA anumore (in remembrance of XDA 2012).
Sent from my Redmi Note 3 using XDA Labs
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
---------- Post added at 07:43 PM ---------- Previous post was at 07:42 PM ----------
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
tdssmarty16 said:
guys rn3 is an amazing device and it has got amazing developement going on which makes me wanna try the range of amazing custom roms available for this device
however there are so many damn complications like different methods of unlocking bootloaders,different twrps,boot patching files etc.
although there are some good guides available they are still not noob friendly in my opinion and the fact that there are so many threads made by people who brick there redmi note 3 is a proof of that
i am new to the rn3 developement forums and terms like fastboot rom developer rom edl are all confusing to me at this point developement has reached to a level that i believe it is really difficult for someone who is a noob to even try flashing cm
all i want is a really really noob friendly guide which covers in complete detail all the instructions related to these topics
1. bootloader unlock , which method to choose and why
2.twrp version best recommended for flashing both miui and custom roms
3.need for patching boot file and in which
cases
4.any other stuff you might think is necessary
Click to expand...
Click to collapse
Bootloader: Go with the official way. The tool can be used again and again as long as you got the permission. There are many cases of bootloop and bricked phones when using unofficial method. Just goto miui unlock page and login with you id, you will get unlock permission within a week.
Download miunlock tool and follow the onscreen instructions.
Twrp: use the official version or if you want f2fs (which is not that big of a deal) thestrixs twrp. I prefer the official one. Reasons: no idea. The cofface version is for those who want twrp to remain unchanged even when they are using miui rom. If you plan to port to cm or anyother rom no need for cofface. The alka version lets you backup every single partition and allow you restore them seperately. No need to use this as you can always use miflash to flasb miui rom again. The only backup you will ever need is efs which can be done with any version.
I prefer a partition dump instead of twrp backup. If you want to know how to create a fool proof backup of efs see my guide. Just search it under discussions and you will find it.
Boot image:
There is no need. The custom cooked boot image is only eequired if you use miui and want to keep stock recovery from replacing twrp. Again why do all this when you can flash twrp again.
Any other stuff:
You can check out guides for installing rom, xposed, i dont know.
thanx a lot helping out mahn
will go with the official unlock
and official twrp
i have been waiting a lot to try cm 13
So i've been looking on the internet for some ways to port any CM to my device J100FN, i found quite a few but some of them are outdated or badly explained etc etc...
I'm gonna put it plain and simple.
I have linux, i have my stock rom J100FNXXU0AOD1, and i can surely get any CM somewhere in the internet (note that i have CM12 for Samsung S3 neo already so tell me if that's gonna do it)
Here are the tutorials that i found so far:
https://www.youtube.com/watch?v=GAyxypK7_K8 (says that i need a CM already built for my phone, which is no available)
https://forum.xda-developers.com/showthread.php?t=2545618 (same with this one)
https://forum.xda-developers.com/showthread.php?t=2245786 (and this one is kinda poorly explained at the begining)
Note that i have a rooted device and TWRP recovery up and running on it, also i read about this "Cyanogenmod compiler" thingy thing, but i couldn't manage to download it, i think the repos are down now or idk. (https://forum.xda-developers.com/showthread.php?t=1415661) (https://korben.info/cyanogenmod-compiler.html)
IDK MAN I REALLY NEED CYANOGENMOD ON MY GALAXY J1 LTE, i'm kind of a rookie when it comes to complicated roms maneuvering but i still do have basic knowledge (flashing, rooting, few terminal cmd's etc etc...)
Please help, and thank.
Putshi said:
So i've been looking on the internet for some ways to port any CM to my device J100FN, i found quite a few but some of them are outdated or badly explained etc etc...
I'm gonna put it plain and simple.
I have linux, i have my stock rom J100FNXXU0AOD1, and i can surely get any CM somewhere in the internet (note that i have CM12 for Samsung S3 neo already so tell me if that's gonna do it)
Here are the tutorials that i found so far:
https://www.youtube.com/watch?v=GAyxypK7_K8 (says that i need a CM already built for my phone, which is no available)
https://forum.xda-developers.com/showthread.php?t=2545618 (same with this one)
https://forum.xda-developers.com/showthread.php?t=2245786 (and this one is kinda poorly explained at the begining)
Note that i have a rooted device and TWRP recovery up and running on it, also i read about this "Cyanogenmod compiler" thingy thing, but i couldn't manage to download it, i think the repos are down now or idk. (https://forum.xda-developers.com/showthread.php?t=1415661) (https://korben.info/cyanogenmod-compiler.html)
IDK MAN I REALLY NEED CYANOGENMOD ON MY GALAXY J1 LTE, i'm kind of a rookie when it comes to complicated roms maneuvering but i still do have basic knowledge (flashing, rooting, few terminal cmd's etc etc...)
Please help, and thank.
Click to expand...
Click to collapse
Don't let this thread die please :/
Like come on 34 views but no replies...
How did you get the TWRP for your phone? Is there one for the J100? I haven't managed to root my J727 One thing you could do is use the google android tree with all its garbage and then copy and paste the CM tree into it. But quite frankly I hesitate to suggest this because it's a huge pain in the ass, and like I said, I haven't managed to get TWRP working for my phone doing this. I can get it compiled but... I have no idea what makes it specific to the phone. I thought it was enough just to have the kernel for the specific phone...
peterius said:
How did you get the TWRP for your phone? Is there one for the J100? I haven't managed to root my J727 One thing you could do is use the google android tree with all its garbage and then copy and paste the CM tree into it. But quite frankly I hesitate to suggest this because it's a huge pain in the ass, and like I said, I haven't managed to get TWRP working for my phone doing this. I can get it compiled but... I have no idea what makes it specific to the phone. I thought it was enough just to have the kernel for the specific phone...
Click to expand...
Click to collapse
Idk man, I just looked up a tutorial on how to root it, I had to look quite deeply but I found it and it's working just fine, it requiers you to flash the boot.img too and then root it with Kingoroot, this is the tutorial I followed www .halabtech. com/root-for-j100fn/ (I know it looks shady but it worked, also I can't post links because my account is new...)
Also I asked a dev and he asked me about the source code of the cpu or some stuff, tbh I have no idea why you would need that to make a rom out of a stock rom...
As I've been informed by twrp, the recovery image typically has it's own kernel which means its specific to the device. I'm not totally sure of the reasons for this. I ended up returning the galaxy j727u which has a locked bootloader for a xiaomi, I'll see how it goes.
I see, but that doesn't really advance in my case
Is any devs out there willing to help out a stupid newbie :^)
Come on now don't let this thread die