Related
Okay so I've bought a samsung galaxy chat B5330 device back in feb'2013. Don't ask me why cause I conciously bought it. So I realised after searching for 6 months that there is no interest of developers in this device. so I have taken up the initiative to 1) Build CM 10, 2) Port CWM, 3) Root the device myself. However I don't have much idea about building android. I've rooted and flashed Custom recovery n ROMs to my dad's phone before and I'm a geek so I learn things quickly about computers n phones. So I'm nor a complete newbie neither a Master developer. Therefore I need help of those devlopers who will be kind enough not to discourage me. Anyone can root a device which is more popular because it gets vulnarable too quickly so there is no point in telling me that "you should have bought a device which has developer support". I am interested to be a developer myself n that challenge is really so tempting to me. So here are my questions which I don't have exact idea about.
1) I have a computer of the config -> AMD fx 6100 hexacore buldozer 3.3 GHz/4 GB RAM/500 GB HDD/Windows7(32) & Ubnuntu 13.04(64). Can I do the job of building roms from the source with this config in the first place?
2) Does galaxy chat B5330 support 'fastboot'? if yes then How can I boot into fastboot mode? I've tried with adb 'reboot-bootloader' but the device just restarted normally. So I don't know How can I get into the fastboot mode?
3) CM developers are really kind enough that they have put alot effort into making the wiki. I've got precious informations about building android from source and all. But I have a confusion. There was mentioned fastboot is necessery for building CM. So if my phone does not have fastboot should it mean that I can't build CM for my device at all?
4) How much data do I have to download? Do I need to be connected to the internet always while editing local file? n If I use 'repo sync' to update the code always won't my editings get overwritten by stock code again?
so these are few basic questions I have for now. I know I might not get any response at all. But there's no harm in trying. thanks
Update1
ranchoabc said:
Okay so I've bought a samsung galaxy chat B5330 device back in feb'2013. Don't ask me why cause I conciously bought it. So I realised after searching for 6 months that there is no interest of developers in this device. so I have taken up the initiative to 1) Build CM 10, 2) Port CWM, 3) Root the device myself. However I don't have much idea about building android. I've rooted and flashed Custom recovery n ROMs to my dad's phone before and I'm a geek so I learn things quickly about computers n phones. So I'm nor a complete newbie neither a Master developer. Therefore I need help of those devlopers who will be kind enough not to discourage me. Anyone can root a device which is more popular because it gets vulnarable too quickly so there is no point in telling me that "you should have bought a device which has developer support". I am interested to be a developer myself n that challenge is really so tempting to me. So here are my questions which I don't have exact idea about.
1) I have a computer of the config -> AMD fx 6100 hexacore buldozer 3.3 GHz/4 GB RAM/500 GB HDD/Windows7(32) & Ubnuntu 13.04(64). Can I do the job of building roms from the source with this config in the first place?
2) Does galaxy chat B5330 support 'fastboot'? if yes then How can I boot into fastboot mode? I've tried with adb 'reboot-bootloader' but the device just restarted normally. So I don't know How can I get into the fastboot mode?
3) CM developers are really kind enough that they have put alot effort into making the wiki. I've got precious informations about building android from source and all. But I have a confusion. There was mentioned fastboot is necessery for building CM. So if my phone does not have fastboot should it mean that I can't build CM for my device at all?
4) How much data do I have to download? Do I need to be connected to the internet always while editing local file? n If I use 'repo sync' to update the code always won't my editings get overwritten by stock code again?
so these are few basic questions I have for now. I know I might not get any response at all. But there's no harm in trying. thanks
Click to expand...
Click to collapse
I have acquired the source code for my device from samsung. Now I just need to port the board configs to the CM10 source.
ranchoabc said:
I have acquired the source code for my device from samsung. Now I just need to port the board configs to the CM10 source.
Click to expand...
Click to collapse
nce going man
"Devs Not Interested...."
I don't know whether some people are still talking about this device.
I thought everybody started throwing it and getting his newer one.
Niral.DMello said:
How did you manage to do that? You wrote to them and they gave it? If thats the case you must have some special powers. I'm impressed.
Click to expand...
Click to collapse
If I were not wrong, you could get the source from ://opensource.s*msung.com (*can't post yet )
My Bad English....
excellent
: Bueno:: Bueno: wouldnt see anything wrong in my galaxy cm10 ch @ t gt-B5330 : Bueno:: Bueno:
I've got a working CWM. Looking forward to porting a newer version.
I've got my hands on a working cwm (somehow it did) for b5330. Now looking forward to porting CWM 6 from cm source. I just have too slow bandwidth for cm source syncing. So let's see how it goes.
ranchoabc said:
I've got my hands on a working cwm (somehow it did) for b5330. Now looking forward to porting CWM 6 from cm source. I just have too slow bandwidth for cm source syncing. So let's see how it goes.
Click to expand...
Click to collapse
I really hope you succeed and make it working! Good luck mate!
TheUnknownThing said:
I really hope you succeed and make it working! Good luck mate!
Click to expand...
Click to collapse
Can you give me some directions? I'm trying my best to learn it.
Sent from my GT-B5330 using xda app-developers app
ranchoabc said:
Can you give me some directions? I'm trying my best to learn it.
Sent from my GT-B5330 using xda app-developers app
Click to expand...
Click to collapse
The best way to start is to use another Rom as base (get permission first) then start tweaking it with scripts, apps and build.prop tweaks. Once you start to get familiar with the basics, start experimenting with different tweaks. Since you are going to create a Cyanogenmod 10 Rom from scratch, I give you best of luck and hope many people will use it!
FINALLY!
ported
I always support you sir!
Sent from my GT-B5330 using xda app-developers app
REALLY for GT B5330
patraanjan23 said:
ported
Click to expand...
Click to collapse
REALLY ??
when date to release this ROM ?
sorry my bad english language..
[email protected] said:
REALLY ??
when date to release this ROM ?
sorry my bad english language..
Click to expand...
Click to collapse
I'm currently working on it. It still does not support audio/bluetooth/wifi/phone/usb nothing. It just supports full touch n can run games. You can't use it for calls/internet! I just sideloaded few apk files via adb. So it ran them smoothly. N don't call me sir please. I hate formalities.. just chill
Sent from my GT-B5330 using XDA Premium 4 mobile app
patraanjan23 said:
I'm currently working on it. It still does not support audio/bluetooth/wifi/phone/usb nothing. It just supports full touch n can run games. You can't use it for calls/internet! I just sideloaded few apk files via adb. So it ran them smoothly. N don't call me sir please. I hate formalities.. just chill
Sent from my GT-B5330 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how did you port cm to your device
i also have Samsung star pro and have made a manufacturer based stock rom
my device is samsung star pro
gamersam16 said:
how did you port cm to your device
i also have Samsung star pro and have made a manufacturer based stock rom
my device is samsung star pro
Click to expand...
Click to collapse
I am building from source. it's teadious job. but you sure can try
device tree
by source do you mean the android source(10gb +)
i am also trying the same thing but my source is now syncing
could you help me with making my device tree.
and what else do i need apart from the the device tree
gamersam16 said:
by source do you mean the android source(10gb +)
i am also trying the same thing but my source is now syncing
could you help me with making my device tree.
and what else do i need apart from the the device tree
Click to expand...
Click to collapse
Sure ask whatever you need. But I suggest you do thorough research n a lot of forum searching before you ask anything. I've been digging for 1 year collecting info n learning things.
Sent from my GT-B5330 using XDA Premium 4 mobile app
Cyanogenmod for B5330
HERE COMES CYANOZANE
GO for it n test it yourself!
help
patraanjan23 said:
HERE COMES CYANOZANE
GO for it n test it yourself!
Click to expand...
Click to collapse
could you guide me in this process as i have to build the device tree from scratch and am having difficulties in finding the correct info.
how did you start to look for info in the boot.img
help needed
if possible could you provide a basic guide minimum stuff to help
thanks
gamersam16 said:
could you guide me in this process as i have to build the device tree from scratch and am having difficulties in finding the correct info.
how did you start to look for info in the boot.img
help needed
if possible could you provide a basic guide minimum stuff to help
thanks
Click to expand...
Click to collapse
read this thotoughly.
Hello All,
I am trying to re-vive the Ubuntu Touch port for Galaxy S3. In which of the many areas of XDA this would be placed?
- Its no official or unofficial Android ROM
- its rather like Sailfish OS
How to name the thread correctly according to [ROM] etc flags?
BR Florian
Flohack said:
Hello All,
I am trying to re-vive the Ubuntu Touch port for Galaxy S3. In which of the many areas of XDA this would be placed?
- Its no official or unofficial Android ROM
- its rather like Sailfish OS
How to name the thread correctly according to [ROM] etc flags?
BR Florian
Click to expand...
Click to collapse
Well, that should be the least of your problems!
Option58 said:
Well, that should be the least of your problems!
Click to expand...
Click to collapse
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Flohack said:
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Click to expand...
Click to collapse
I don't own your device. But if that's the case...good luck :good: :fingers-crossed:
Flohack said:
The other problems I manage locally - but I want to start a discussion thread soon, since I am convinced to be able to push out a test build soon. I want to involve more people into this, thereby generating more possible solutions for problems.
In case you are interested, the phone boots already correctly, kernel is fine without errors, Android container starts also without errors. Ubuntu´s init/upstart is mounting all necessary partitions, and brings up most of the basic services. Currently stuck with GUI since mir/libhybris/unity8 cannot paint on framebuffer or hw composer
BR Florian
Click to expand...
Click to collapse
Bro.. I own a s3 at&t.. And would love to help out on testing ROMs. This task of yours seems promising.
Meanwhile, I installed a Linux OS in my system of which am still trying to wrap my head around (If its of any help). So just call out anytime u need me.
holysaint1 said:
Bro.. I own a s3 at&t.. And would love to help out on testing ROMs. This task of yours seems promising.
Meanwhile, I installed a Linux OS in my system of which am still trying to wrap my head around (If its of any help). So just call out anytime u need me.
Click to expand...
Click to collapse
Hi,
good to know. We just need to make sure AT&T version does not have too much difference from the international one. Can you dedicate it for testing? It does not need data to be wiped normally, since Ubuntu runs off a container in the data partition but you never know...
I am currently stuck with the GUI and tbh I have no idea when and how this will be resolved. Samsung has done a great job with their GPU and Exynos, but our libhybris part does not want to play with it nicely.
Keep you updated!
BR
Actually I use it as my DD but wouldn't mind testing a few ROMs for the gd of the comm.
Aiite then. Patiently waiting for the update.
I have the international version of S3 GT-i9300. It is currently without a working rom, so I need to find time to see if it will boot with an official rom flashed with odin, it currently has an old clockwork mod recovery installed and a lineage os rom that wont boot..
If I get it working again, then I could dedicate it to testing... I would love to have a phone that was pure linux with phone capabilities... then I would no longer need to use google's linux abomination known as android
Hi,
sorry to say but I stopped now every porting activity, since Canonical dropped Ubuntu Touch and we are struggling on all other frontlines to get the community together for continuing the OS.
There will be no new hardware ports in the near future, which I think will be up to 1 year or 2. By that time, also S-III etc are end of life, since its hard to support multiple generations of smartphones with different kernels properly. Im afraid we are too late...
Anyway, contact me if you want to help in other areas of Ubuntu Touch going UBports community
BR
Anyone can post link for ubuntu touch note 2 n7100 please?all links are dead
laharl_22 said:
Anyone can post link for ubuntu touch note 2 n7100 please?all links are dead
Click to expand...
Click to collapse
same here ! I am also trying to find from so long, tried a lot but no luck !!
Please somebody post it
Hi there,
Florian from UBports. The active devices that we support can be found here: https://devices.ubports.com/#/ - that being said, you wont find the Note 2 there as an active device. What happened in the past I can´t say, but currently we have no ETA to work on new devices.
BR Florian
Hello XDA members and friends ! I want to please you for something. Ok so I have Acer Liquid Z630 and i have 1year old security patch So i wanted to if someone can make me rom based on android 6.0 or better I'll be very glad for that because i still running Android 5.1.1 and i want new android and new things So if u want to you can send me PM
With regards BotoBalboa
BotoBalboa said:
Hello XDA members and friends ! I want to please you for something. Ok so I have Acer Liquid Z630 and i have 1year old security patch So i wanted to if someone can make me rom based on android 6.0 or better I'll be very glad for that because i still running Android 5.1.1 and i want new android and new things [emoji14] So if u want to you can send me PM
With regards BotoBalboa
Click to expand...
Click to collapse
ROM requests are not allowed. Also, if you want someone to build a ROM for you then you'll have to PM some developers here and ask them if they would be willing but you'll have to be willing buy another device like yours and donate that device to the developer. If you can't donate a device then you are wasting your time asking for a ROM.
If you can't or won't donate a device then you'll have to learn how to build ROMs for yourself. There are many guides for building your own ROM all over the Internet and there are many members here that have made their own recoveries and ROMs because their device was not supported by any developers.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
ROM requests are not allowed. Also, if you want someone to build a ROM for you then you'll have to PM some developers here and ask them if they would be willing but you'll have to be willing buy another device like yours and donate that device to the developer. If you can't donate a device then you are wasting your time asking for a ROM.
If you can't or won't donate a device then you'll have to learn how to build ROMs for yourself. There are many guides for building your own ROM all over the Internet and there are many members here that have made their own recoveries and ROMs because their device was not supported by any developers.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
As I'm in the same position with this phone I'm considering creating my own basic ROM for it. Although I'm good at IT in general I'm not a programmer or developer or Android expert so I'll need to ask one or two of my friends to help me with the compiling and makefile aspects of the task (according to a Youtube video).
My question is how much time my friends would need to put aside for this (as long as I do the downloading and use my PC to do all the compiling work).
I don't even want to ask them if it will take hours of their time.
dude it is not problem for me
Spitsborstel said:
As I'm in the same position with this phone I'm considering creating my own basic ROM for it. Although I'm good at IT in general I'm not a programmer or developer or Android expert so I'll need to ask one or two of my friends to help me with the compiling and makefile aspects of the task (according to a Youtube video).
My question is how much time my friends would need to put aside for this (as long as I do the downloading and use my PC to do all the compiling work).
I don't even want to ask them if it will take hours of their time.
Click to expand...
Click to collapse
Hours would be an understatement, more like days weeks or even months to iron out all the kinks.
Sent from my LGL84VL using Tapatalk
SM-G389F Marshmallow Port for SM-G388F
Hello Everyone,
So we all know that the SM-G389F has Marshmallow as it's OS,
But when we look on the side of the SM-G388F, we still have Lollipop as it's OS, So I decided to port the OS version of the SM-G389F to the SM-G388F while configuring it to be compatible with it's hardware! :laugh:
I might need some help....
But we can start by Converting the Firmware Download to a Zip for the Custom Recovery to flash it
(Link to Download)
Thanks for Tuning in,
I will keep you all Updated soon! :fingers-crossed:
Hello Everyone,
I've wasted plenty of time trying to extract the SM-G389F Marshmallow Firmware but it was all for nothing. So now I am asking you all who own this device to flash the ROM link above using odin (https://www.sammobile.com/firmwares/galaxy-xcover3/SM-G389F/BTU/download/G389FXXS1APK1/114774/) and then creating a backup via TWRP including the system.img and the boot.img and sending it to me via Dropbox, Google Drive...
Anyway I would like to forgive myself for failing to do this operation without owning the phone because of the md5 protection, but now I will be leaving this part in your hands
Thanks in Advice,
Diamond26
For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.
Matt07211 said:
For all intents and purposes consider the two devices as completely separate/different. First of all the got completely different SoC's (not revisions but completely different brands of SoC's). I started try to compile LineageOS (my sources are up on github), but I was facing completely obscure or unheard of errors that where difficult to fix and the amount of free time I have has changed so I more or less have stopped doing that for the time being.
I will be writing up all the info I know off the device but that task has gotten away from me at the moment due to computer problems.
Click to expand...
Click to collapse
Thanks for including yourself in this thread!
But may I ask which device do you own please?
Diamond26 said:
Thanks for including yourself in this thread!
But may I ask which device do you own please?
Click to expand...
Click to collapse
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F
Matt07211 said:
Well in currently typing it from my Samsung xCover3, with the Marvell SoC, so it's the SM-G388F
Click to expand...
Click to collapse
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!
Diamond26 said:
Oh ok!
I was just eager to see if someone with a SM-G389F has come, maybe he could back up his 6.0 Stock ROM and maybe I could modify it.
That's why!
Click to expand...
Click to collapse
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)
Matt07211 said:
Please re-read my initial post in this thread, it's not possible. Your dealing with two different types of SoC's, so what your proposing is not possible, compiling from stock Android sources is (if you can fix every compile error)
Click to expand...
Click to collapse
I just want to mess around with the ROM, maybe I could modify something!
PixelBoot said:
I just want to mess around with the ROM, maybe I could modify something!
Click to expand...
Click to collapse
Do what ever you want, you can still mess around a lot, you just can't transplant files from the value edition to the Normal edition.
There is some cool mods you can do if you modify system apks.
https://forum.xda-developers.com/showthread.php?t=2799050
Is this thread still up?
Rrrrrrx404 said:
Is this thread still up?
Click to expand...
Click to collapse
Thinking about it...
I was thinking the same thing… I have an old Xcover, so i just wanted to try…
Did you succeed?
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Alando123 said:
I know the first comments on this post will be the pessimistic "if you are asking all these questions, then you will not be able to do this" type.. however, if that is the case, how did all the developers learn to build custom ROMs for their devices? They must have learnt from somewhere or by their own trial and error.. therefore they can share their knowledge if willing to do so.
My question is about the building of a custom ROM e.g. LineageOS for an unsupported device which has no device tree or anything of the sort, such as a BLU Studio X Plus.
I know the basic commands.. But I'm not sure of the full process for creating the necessary blobs for my device(s).
I am aspiring to be a developer myself, but need someone to teach me. If any of you are willing to assist me in my endeavour, comment down below, or you can even privately message me.
Any assistance will be greatly appreciated!
Click to expand...
Click to collapse
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with an assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
First of all, it depends on whether the stock source code is available for your device, if there is no stock source code available to the public(no, I'm not talking about the stock firmware file), then you will not be able to build a custom ROM from source for your device, which means that you won't be able to build anything like LineageOS because setting up the device tree requires the stock source code. No source code=no device tree, no device tree=no LineageOS or AOSP ROMs. Devices that do not have a source code available can only get ROMs if someone chooses to port a ROM from a similar device with similar hardware, that is the only way to get a ROM without stock source code. The stock firmware would be required in order to port a ROM from a similar device, if the stock firmware is not available, you can't port a ROM.
Sent from my LGL84VL using Tapatalk
Droidriven said:
They started by starting with smaller, less complicated developments/modifications to get some basic understanding. Then they started spending more time doing more diligent research, reading, reading again then reading again than they did spending time asking questions.
As for the "sharing their knowledge" for others to learn.... Well, that is exactly why there are hundreds or even thousands of guides and threads on the various types of android custom development on many different websites and forums. The issue you are having is based in the fact that all of the guides are written with assumption that the reader already has some form of intermediate programming knowledge, they are not written for the proverbial "noob". Another factor is that none of the guides are an "all-in-one, everything you need to know from start to finish" type of guide, this is because there are too many differences in the various android versions, hardware architectures, SDK versions, APIs and etc. to make a guide complete enough for general usage on every type of device, there are specific things involved that make that an impossible task. So don't get your hopes up about some kind of miracle answer that takes the pain and hard work out of your journey.
Study the guides, start small, get good at what you start with, then work your way up, starting with trying to build something like a ROM with no previous programming experience, is not a good idea for a starting point.
There is no shortage of people coming to XDA wanting to be developers and asking for someone to help teach them, it just doesn't work that way, you gotta be willing to put the time into learning and figuring out at least 95% of it on your own, that is how they learned, why should it be any different for you. The cold reality is, those that truly desire it, seek it diligently without reaching out for a hand to do the "real" work for them, the ones that succeed and excel are the ones that climb the ladder themselves with very little help from the outside because they reach inside of themselves and apply themselves to their goal without quitting or losing heart or saying "this is too hard, help me".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Alando123 said:
Thanks for the advice.. I was hoping for something along the lines of a "I found a formula, you can use it to solve your problem" kind of answer.. But I understand your point of view. I was by no means asking for anyone to do the "real" work for me, just for a helping hand to point me in the correct direction. Most of the guides I see are just to create some basic files using the boot.img of my device.
Click to expand...
Click to collapse
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery such as TWRP(which you'd probably have to build for yourself, which is yet another task to learn in development along with learning to build a ROM, not to mention learning how to get the kernel right) in order to flash a LineageOS custom ROM or any other ROM that is not based on stock, TWRP is easier to learn how to build than a ROM, but still a task in itself. Modified stock ROMs can be customized and flashed without root or custom recovery but they aren't "true" custom ROMs, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Droidriven said:
I added to my post above, it might give you an idea of what is possible and what isn't.
Go to the LineageOS website and read the basic guide for setting up an android build environment, then read some guides for building ROMs for other similar Blu Studio devices.
Also, another important factor in whether or not a custom ROM is possible for your device is thst your bootloader must be unlocked or at least "can" be unlocked.
You also need a custom recovery in order to flash a LineageOS custom ROM or any other ROM that is not based on stock. Modified stock ROMs can be customized and flashed, but they aren't custom, they are still fully stock underneath with some tweaks "on the surface".
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Alando123 said:
Yes.. I have made a TWRP for my device.. I also created a modified (rooted, debloated, updated) stock ROM.. But want to reach a stage where I'm able to make an actual custom ROM. I am currently flying through many guides to get an idea of what is needed.
I've set up build environments and built ROMs for Samsung Galaxy Grand Prime (grandprimeve3g) but that device already had proprietary blobs made for it.
Click to expand...
Click to collapse
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ok, so you have a decently basic understanding, that is in your favor. As for the blobs, is the stock source available for your specific device? That would help increase your chances of success. Are their any other models of Blu Studio or other device with similar hardware that have custom ROMs already available? If so, you may can put something together using some blobs from those devices and then filling in the blanks.
@Alando123
Can you get a ROM dump or system dump from your device?
I'm going to assume that you've read this and experimented with it?
https://wiki.lineageos.org/proprietary_blobs.html
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools. I also just stumbled upon the link to the LineageOS page about blobs right before you replied ?
Alando123 said:
No, BLU rarely releases source for any of their devices, however I made a system dump using MTK Droid Tools
Click to expand...
Click to collapse
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Droidriven said:
You should be able to use the system dump to generate vendor blobs by extracting them from the system dump or from a system dump pulled from a similar BLU studio or MTK device running a current LineageOS ROM as described in the first portion of the guide in the link that I gave you.
Also, there is a Lineage forum and a place to comment/ask questions on their github page.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Alando123 said:
Hey, I currently ported several ROMs for my device.. the only problem I have with all of the ROMs are auto-focus and front camera (though camera is an issue for almost all ROMs, developed or ported at first). Most of the devices are similar, so, I'll do some digging and see what I can do about this. Or if I can develop a ROM, with some kanged blobs and some of my own, that will work, then fix camera piece by piece.
Click to expand...
Click to collapse
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yes, stock camera is always an issue when building ROMs because stock camera is proprietary, this means the camera is a closed source software instead of open source software.
Generally, the "quick fix" is to use a 3rd party camera app from PlayStore such as Google Camera or A Better Camera(ABC camera). Try some 3rd party camera apps and see if any work.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Alando123 said:
Yeah.. replacing libcameracustom.so results in the same issue with front camera, also even Footej closed when trying to use the front camera.
Click to expand...
Click to collapse
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try more than just a few camera apps, try many, try several, try them all, one of them might work. It's aggravating and time consuming, but with patience, it might work out for you.
You might need to try an app and then if it doesn't work, uninstall the app then boot into recovery and wipe cache and dalvik cache then reboot and try another camera app, you might also need to try a factory reset along with wiping cache from recovery before trying another camera app because some things might be left behind from the non working app that you tried and it might interfere with the next app that you try. Factory resetting and wiping cache before trying the next app might increase the chances that it will work. If you try an app and it doesn't work, just uninstalling it before trying the next app might not be "enough" if it leaves something behind that prevents the next app from working.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
I don't think that any camera app would have helped.. I replaced libcameracustom.so from a different device, and front camera works, but no both cameras have a blue hue on them
I am having problems with building lineageOS for my "Unsupported" Device I have made themed ROMS, Themes for cyanogenmod, Themes for substratum, basic apps for my ROM, and customized recovery and ported ROMS to my device but I need a small headstart to actually "Build" lineageOS for my device. Thats It
Regards
Manav Harsana