Hi Guys,
I am new to Android (a noob) - Started with flashing some custom ROMs on my devices and i am bothered by the security of my device, although android is open source, is it possible that a custom ROM is bugged to steal your personal or financial information? I don't have any experience with android development and i don't have time to jump into Android development so even if the ROM is open source i wont be going through the code to check for leaks or potential built-in hacks.
Basically my question is, is it safe to install Unofficial ROMs such as CM unofficial? I understand, the majority of apps store sensitive data on device in encrypted way but still, i don't think it will be hard to just modify the ROM to develop a built-in key-logger OR read username/password from a username/password fields while user is typing using an on-screen keyboard, save it as LOG file and when connected to the internet, send it to the 'unknown' source. I can see so many possibilities, the user wont even have a clue that they are sharing data. it is like Microsoft making windows Open Source and people making their own versions of Windows and users installing them on thier PCs.
Please help me understand - How safe are our devices when running on custom ROMs from developers we don't even know (no disrespect to any dev, all this amazing work is appriciated, I just want to understand the security of android - Please help me understand as after flashing custom ROMs on my devices i am avoiding installation of sensitive apps or even using chrome to type my passwords) - am i paranoid ?
Cheers
It's entirely possible that a malicious custom ROM could steal your data (or worse), and there's really no technical way to mitigate it. You're implicitly trusting the developer of a ROM by flashing it. All you can really do is make sure that whatever ROM you choose is from a well-known, trusted developer.
aliusman999 said:
Hi Guys,
I am new to Android (a noob) - Started with flashing some custom ROMs on my devices and i am bothered by the security of my device, although android is open source, is it possible that a custom ROM is bugged to steal your personal or financial information? I don't have any experience with android development and i don't have time to jump into Android development so even if the ROM is open source i wont be going through the code to check for leaks or potential built-in hacks.
Basically my question is, is it safe to install Unofficial ROMs such as CM unofficial? I understand, the majority of apps store sensitive data on device in encrypted way but still, i don't think it will be hard to just modify the ROM to develop a built-in key-logger OR read username/password from a username/password fields while user is typing using an on-screen keyboard, save it as LOG file and when connected to the internet, send it to the 'unknown' source. I can see so many possibilities, the user wont even have a clue that they are sharing data. it is like Microsoft making windows Open Source and people making their own versions of Windows and users installing them on thier PCs.
Please help me understand - How safe are our devices when running on custom ROMs from developers we don't even know (no disrespect to any dev, all this amazing work is appriciated, I just want to understand the security of android - Please help me understand as after flashing custom ROMs on my devices i am avoiding installation of sensitive apps or even using chrome to type my passwords) - am i paranoid ?
Cheers
Click to expand...
Click to collapse
You are paranoid but that's good!
Yes we are trusting the devs (or Samsung et al with stock) AND hopefully smart coders who regularly check the code (but I suspect checking doesn't happen a lot!). You can use a firewall/packet sniffer to check what servers your phone is connecting to and see (some) of the data being sent to reduce your risk and put your mind at ease. But still it's no guarantee, as I understand it (I'm no expert!).
---
trainsuit said:
If you get a stock android you are also trusting the developer. Just look at these lenovo laptops which had malware served on their stock windows versions. Best is to always start clean when buying any form of product.
Click to expand...
Click to collapse
That's true, but how do you define ”clean”? In theory, you could build AOSP for your device yourself so you're only trusting Google, but that's completely impractical for most people. If you just switch from stock to someone else's custom ROM, you're just changing who you're trusting.
---
Perhaps it's a silly question but I do it: do you think that a XDA Senior Member with one or two thousand of thanks is reliable?
Bach_J said:
Perhaps it's a silly question but I do it: do you think that a XDA Senior Member with one or two thousand of thanks is reliable?
Click to expand...
Click to collapse
Another question for you: if a ROM has malicious code that send personal information to unknown servers, is using a firewall like AFWall+ twhich blocks all system apps sufficient to prevent this malicious ROM to stole data?
Thanks
Bach_J said:
Perhaps it's a silly question but I do it: do you think that a XDA Senior Member with one or two thousand of thanks is reliable?
Click to expand...
Click to collapse
Probably.
Bach_J said:
Another question for you: if a ROM has malicious code that send personal information to unknown servers, is using a firewall like AFWall+ twhich blocks all system apps sufficient to prevent this malicious ROM to stole data?
Thanks
Click to expand...
Click to collapse
No, a custom ROM could make data look like it's coming from any app it wants, or just bypass the firewall completely.
josephcsible said:
No, a custom ROM could make data look like it's coming from any app it wants, or just bypass the firewall completely.
Click to expand...
Click to collapse
Alternatively if the device is on your own network you could wireshark it using a computer and monitor IP addresses that the device attempts to connect to.
LyricalMagical said:
Alternatively if the device is on your own network you could wireshark it using a computer and monitor IP addresses that the device attempts to connect to.
Click to expand...
Click to collapse
This is helpful but not perfect. There's a bunch of ways to stealthily exfiltrate data over a monitored network, and don't forget a malicious ROM might only do its dirty work over cell and not Wi-Fi for this very reason.
josephcsible said:
This is helpful but not perfect. There's a bunch of ways to stealthily exfiltrate data over a monitored network, and don't forget a malicious ROM might only do its dirty work over cell and not Wi-Fi for this very reason.
Click to expand...
Click to collapse
I agree with you it's not a perfect solution; this question is sort of like asking if you can trust someone who has a root account to your computer when you cannot see what they are doing, it's an incredibly disadvantaged situation from the start.
LyricalMagical said:
I agree with you it's not a perfect solution; this question is sort of like asking if you can trust someone who has a root account to your computer when you cannot see what they are doing, it's an incredibly disadvantaged situation from the start.
Click to expand...
Click to collapse
I don't want to flash custom ROMs anymore! :crying:
It can be very dangerous! Or am I paranoid and I can trust xda developers?
Bach_J said:
I don't want to flash custom ROMs anymore! :crying:
It can be very dangerous! Or am I paranoid and I can trust xda developers?
Click to expand...
Click to collapse
Remember, everything I've been saying is reasons not to flash a ROM unless you trust the dev. None of it is saying that devs aren't trustworthy. I don't know of a single instance when a well-respected XDA member's ROM turned out to be malicious.
josephcsible said:
Remember, everything I've been saying is reasons not to flash a ROM unless you trust the dev. None of it is saying that devs aren't trustworthy. I don't know of a single instance when a well-respected XDA member's ROM turned out to be malicious.
Click to expand...
Click to collapse
Thank you for clarifying that but the question comes once more: how to recognize a well-respected XDA member? With the number of thanks? It is obvious that if the smartphone you are interested in is not so famous, there will be few comments on custom ROMs, too. So, how to evaluate the reliability of a xda dev who is developing ROM for not-well-known devices?
Are ROMs in Original development Section trustworthy?
Bach_J said:
Thank you for clarifying that but the question comes once more: how to recognize a well-respected XDA member? With the number of thanks? It is obvious that if the smartphone you are interested in is not so famous, there will be few comments on custom ROMs, too. So, how to evaluate the reliability of a xda dev who is developing ROM for not-well-known devices?
Are ROMs in Original development Section trustworthy?
Click to expand...
Click to collapse
Number of thanks can hardly tell that a dev is reliable or not(in some cases it can), rather it's the quality of their work and their expertise on the related topics that could clarify their position a bit. the recognized contributors, recognized developers, recognized themers you should look at cause
these are given to a member after being checked and passed by moderaters here on XDA. So they are pretty much reliable guys. in cases where there are no recognized developers and hardly any comments. you will have to check and find out yourself
1. ask the dev if he has tested the ROM himself?
2. how did he compiled the ROM? is it a port or just a modified copy of another ROM or a build from source.
3. check the link of the download, if it's to some survey site or ask for a password, stay away from it.
4. if you trust the download link, then download scan with antivirus and unzip the file.
5. generally I look inside app if there are apps which I don't trust and I remove them, then check build.prop, init.d folders. basic things to look for is any references of some other website/ports in between codes. if you're more paranoid you can check bin folder as well and every other you want.
6.don't install the ROM simply Root and debloat.
billysam said:
Number of thanks can hardly tell that a dev is reliable or not(in some cases it can), rather it's the quality of their work and their expertise on the related topics that could clarify their position a bit. the recognized contributors, recognized developers, recognized themers you should look at cause
these are given to a member after being checked and passed by moderaters here on XDA. So they are pretty much reliable guys. in cases where there are no recognized developers and hardly any comments. you will have to check and find out yourself
1. ask the dev if he has tested the ROM himself?
2. how did he compiled the ROM? is it a port or just a modified copy of another ROM or a build from source.
3. check the link of the download, if it's to some survey site or ask for a password, stay away from it.
4. if you trust the download link, then download scan with antivirus and unzip the file.
5. generally I look inside app if there are apps which I don't trust and I remove them, then check build.prop, init.d folders. basic things to look for is any references of some other website/ports in between codes. if you're more paranoid you can check bin folder as well and every other you want.
6.don't install the ROM simply Root and debloat.
Click to expand...
Click to collapse
Thanks for the complete explanation!
billysam said:
Number of thanks can hardly tell that a dev is reliable or not(in some cases it can), rather it's the quality of their work and their expertise on the related topics that could clarify their position a bit. the recognized contributors, recognized developers, recognized themers you should look at cause
these are given to a member after being checked and passed by moderaters here on XDA. So they are pretty much reliable guys. in cases where there are no recognized developers and hardly any comments. you will have to check and find out yourself
1. ask the dev if he has tested the ROM himself?
2. how did he compiled the ROM? is it a port or just a modified copy of another ROM or a build from source.
3. check the link of the download, if it's to some survey site or ask for a password, stay away from it.
4. if you trust the download link, then download scan with antivirus and unzip the file.
5. generally I look inside app if there are apps which I don't trust and I remove them, then check build.prop, init.d folders. basic things to look for is any references of some other website/ports in between codes. if you're more paranoid you can check bin folder as well and every other you want.
6.don't install the ROM simply Root and debloat.
Click to expand...
Click to collapse
I've just unzipped ROM but I can't find what you said. I've only found build.prop and nothing else!
Here a screenshot:
Bach_J said:
I've just unzipped ROM but I can't find what you said. I've only found build.prop and nothing else!
Here a screenshot:
Click to expand...
Click to collapse
That's because lollipop and marshmallow ROM files are further zipped into system.new.dat files which needs another method to extract, https:\\forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Just a small correction. When going to aosp you I ly are trusting yourself as you can inspect everything you add and remove what you don't.
Now to add to your paranoia. A custom rom could be made that allows all apps root permission without the users knowing. Add in a Key logger and have e it all headed without you ever knowing. This is common is xiaomi and other china based devices.
Heck there are a few key parts in the playstore with built in Key loggers.
Heck most of the go apps send all their data to China. Things like their Keylogger files, screen recording and device usage. But mind you it is all legal
Related
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/showthread.php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
noobworld said:
Hi,
I thought this was not yet possible to port Cyanogenmod on Dual Sim devices, at least not properly, but then I saw this post:
http://forum.xda-developers.com/show....php?t=2246874
It gave me a real hope for the generic MT6589 device I am currently using.
I am new to all of this, so I hope I don't bother everyone.
Also, my device uses obviously different hardware, but uses the same processor, so I managed to install the above ROM and got it working but without any screen display.
In other words, it was working, and I could see everything as far as the installation wizzard was concerned, so I thought I was fine, but then when I was done and it rebooted, I could not see anything on the display anymore, but the phone was still working working.
So I am assuming some obvious hardware drivers differences, and that the old drivers were still working till I restarted?
Is there a way to modify the rom to make it work?
What files would I need to pull from my device to add/replace in the posted ROM to make it worlk, if that is possible?
Or does cynanogenmod have to compile with the files of my device to work, even though the processor bit had already been done?
If so, I have no problem in trying to compile cyanogenmod from scratch, but I will still get the dual SIM problem, and I thought this has been fixed in this ROM.
So what modifications would need to be done to incorporate the DUAL SIM issue, and make it work, or has this already been resolved upstream?
Is there a github or such of the modifications and alterations that were done to Cyanogenmod for this posted ROM in order to get it working?
I am willing to use those files and port it to my device, but without these modifications, I will not be able to do anything, even though the kernel sources for MT6589 are openly available now.
Sorry for asking this question here, but I tried to reply to the original post and it did not let me.
Is it okay to ask this here?
If not, please excuse me, and if you can forward me to the right place.
Thanks and regards
Click to expand...
Click to collapse
link is dead.
who is the dev.
prantoroy said:
link is dead.
who is the dev.
Click to expand...
Click to collapse
Thanks for the headsup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
noobworld said:
Thanks for the headup.
I placed in an incomplete link, here is the complete link:
http://forum.xda-developers.com/showthread.php?t=2246874
I also updated the post.
The developper seems to be:
bgcngm
Thanks
Click to expand...
Click to collapse
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
prantoroy said:
give sme time.will try
Click to expand...
Click to collapse
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
prantoroy said:
give sme time.will try
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
just as I thought.the kernel.
its not fr u. ask dev to create a kernel fr u!
Click to expand...
Click to collapse
noobworld said:
Thank you for your fast reply.
Where do I ask?
Also, I was hoping to learn how to do it, and have the sources if possible, or at least how to modify the sources, because I have about three of these chinese devices, all using the same processor, but with different hardware.
Thanks
Click to expand...
Click to collapse
Ask The dev
And Its not that easy
prantoroy said:
Ask The dev
And Its not that easy
Click to expand...
Click to collapse
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
And Its not that easy
Click to expand...
Click to collapse
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
noobworld said:
Well, I tried posting on the original thread, but couldn't.
Then tried to send a private message, but couldn't.
So I started this thread.
You said:
Did you mean it is not easy to contact the dev, or not easy to compile the sources for my devices?
Just wanted to be sure.
Thanks again
Click to expand...
Click to collapse
no you cant post until u have 10 posts
and its not easy to develop rom
prantoroy said:
no you cant post until u have 10 posts
and its not easy to develop rom
Click to expand...
Click to collapse
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
noobworld said:
I can see that, but I think with some patience I can do it.
Also, I have been using Linux for years now, and it seems I just need to figure out how things are laid out in Android.
And once I get used to that, then things become easier.
I am assuming that the linux kernel needs to be compiled with the specific drivers related to my hardware, right?
However, that would still not take into account:
- The changes made in Android/Cyanogenmod that take into account Dual SIM functionality
- How Cyanogenmod is actually laid-out, such as are changes done directly to stock android, or applied as patches?
I was thinking of the following:
1) Checking for the difference between stock Android and Cyanogenmod, and save aside the diff changes to make a patch file.
2) Then hope to find the sources of the stock android that has already been modified to work with MT6589, since these devices obviously use Android on them with some modifications
3) Then apply the patch made in (1) on these sources
Thus, I also need one important question answered:
If I were to download the sources for Cyanogenmod (which I already did), are the patches to the stock Android already applied, or are they placed in a separate folder, and applied on compilation?
I have this feeling that the above patches will probably not work out, because there will probably be extra functions, code that the patch will not be able to take into account, and will have some type of non-working or broken system, until I figure out what is missing.
I might get it to boot to a certain point (most probably shell like), and it would stop there.
Well, in either case, after writing all this down, I started to visualize more the hard part you are talking about, and this would require good knowledge of Android Code and structure.
Thus, if anyone can give me the required Cyanogenmod sources that have already been modified to work on an MT6589, or the diff patches between the normal and modified Cynogenmod, then that would be amazing.
Then I will have to only figure out at that point the propriety files I need to pull from the device, and specific vendor modifications.
Of course, I am just speculating, as this depends on how Android/Cyanogenmod is structured, and I could be completely off the mark, and have no idea what I am talking about.
Thanks
Click to expand...
Click to collapse
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
prantoroy said:
ok I will help u.
go here
http://forum.xda-developers.com/forumdisplay.php?f=613
Click to expand...
Click to collapse
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
noobworld said:
Wow... Even though I searched for so long, I did not find this.
I guess I did not know what to search for.
I thank you a lot.
I will probably take a while to learn how to use this, so I will disappear until I figure it out.
If I managed to do anything, then will come back and post my status.
Thanks again
Click to expand...
Click to collapse
glad I could help.
and don't bother .its my job to help new.
and pm me if u need smthing.
and please close thread.
hi i use custom roms on my s4 i9505, i told my friend and he said i was stupid because people can attach harmful code to any rom or program.
that can give a crook access to your pc or phone. he played me a couple of videos showing this because he has been hit on his self using third party apps, and antivirus programs do not see this code..
Can anyone elaborate on this and prove this is not true about custom roms.
Many thanks
fezz64 said:
hi i use custom roms on my s4 i9505, i told my friend and he said i was stupid because people can attach harmful code to any rom or program.
that can give a crook access to your pc or phone. he played me a couple of videos showing this because he has been hit on his self using third party apps, and antivirus programs do not see this code..
Can anyone elaborate on this and prove this is not true about custom roms.
Many thanks
Click to expand...
Click to collapse
custom roms on this site are required to be open source. that means the developer must post the source code to his work or it can not be posted here. for this reason it is highly unlikely you will find any nefarious code in any of the roms posted here. as for roms posted on other sites, i cant speak for their policies.
apps are always subject to malware, thats why you should only download them from a trusted source like the play store or this site.
bweN diorD said:
custom roms on this site are required to be open source. that means the developer must post the source code to his work or it can not be posted here. for this reason it is highly unlikely you will find any nefarious code in any of the roms posted here. as for roms posted on other sites, i cant speak for their policies.
apps are always subject to malware, thats why you should only download them from a trusted source like the play store or this site.
Click to expand...
Click to collapse
hi thanks for your help i will continue useing echoe rom as i cannot fault it...
.........THANKS TO ALL..........
stick to one developr
stick to one developer and follow the custom rom threads carefully so that u can understand who is a very good developer
I have an old phone that uses Android 2.x, I think froyo or gingerbread. I want to download AFWall+ which is a firewall application that's the successor to DroidWall. The problem is the most recent version no longer supports the Android version used by my old phone. The app's details are here (I can't make it a hyperlink because I don't have 10 posts):
Code:
https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall&hl=en
The relevant part says:
- Supports 4.x ,5.x and 6.x (for 2.x support use 1.3.4.1 version)
Click to expand...
Click to collapse
But the problem is I don't know how to get the 1.3.4.1 version and verify it is the legitimate version. There are a lot of websites that offer downloads for older versions of apks but they could inject anything they want in them couldn't they?
I would ask the developer in his thread what is the proper way to go about this but as I mentioned I don't meet the post requirements at the moment.
Thanks for any help you can offer.
agenda21 said:
I have an old phone that uses Android 2.x, I think froyo or gingerbread. I want to download AFWall+ which is a firewall application that's the successor to DroidWall. The problem is the most recent version no longer supports the Android version used by my old phone. The app's details are here (I can't make it a hyperlink because I don't have 10 posts):
Code:
https://play.google.com/store/apps/details?id=dev.ukanth.ufirewall&hl=en
The relevant part says:
But the problem is I don't know how to get the 1.3.4.1 version and verify it is the legitimate version. There are a lot of websites that offer downloads for older versions of apks but they could inject anything they want in them couldn't they?
I would ask the developer in his thread what is the proper way to go about this but as I mentioned I don't meet the post requirements at the moment.
Thanks for any help you can offer.
Click to expand...
Click to collapse
use this google search to find it.
i saw it on several sites, but cant post the links because they contain warez.
edit,
ha, im an idiot, i didnt read your whole post. yea, im not sure how you would verify.
maybe mention the dev here and he may come. @devsnamehere <-- thats how to mention someone.
bweN diorD said:
yea, im not sure how you would verify.
maybe mention the dev here and he may come. @devsnamehere <-- thats how to mention someone.
Click to expand...
Click to collapse
Thanks.
@ukanth can you tell me how to obtain and verify version 1.3.4.1?
agenda21 said:
Thanks.
@ukanth can you tell me how to obtain and verify version 1.3.4.1?
Click to expand...
Click to collapse
I thought f-droid builds still pointing to 1.3.4.1. I will upload in OP of my thread. Thanks !
ukanth said:
I thought f-droid builds still pointing to 1.3.4.1. I will upload in OP of my thread. Thanks !
Click to expand...
Click to collapse
@ukanth Sorry to bother you again but I can't find version 1.3.4.1 in your thread. Did you ever get a chance to post it somewhere? I can get it from a 3rd party website but I just need you to give me the hashes of the packages so I don't install something that's trojaned. I'm a computer programmer but I don't know much about phones, so please keep that in mind if you have special instructions. Thanks
agenda21 said:
@ukanth Sorry to bother you again but I can't find version 1.3.4.1 in your thread. Did you ever get a chance to post it somewhere? I can get it from a 3rd party website but I just need you to give me the hashes of the packages so I don't install something that's trojaned. I'm a computer programmer but I don't know much about phones, so please keep that in mind if you have special instructions. Thanks
Click to expand...
Click to collapse
@agenda21, Can you try this and let me know, this I found in my backup's. If it doesn't work, then I will build one using the old source and update it.
https://www.dropbox.com/s/c3g4lqzbltbuxfq/dev.ukanth.ufirewall-171.apk?dl=0
I raised a request in f-droid to restore the old version https://gitlab.com/fdroid/fdroiddata/issues/362 . Lets see.
Introduction:
My name as you may be able to tell is Francesco, and I am a long time user of the Samsung Galaxy S Series Devices. My current device is the SM-G935W8. I have just requested Developer Access on Android File Host so I can give access to everyone for the Stock Firmware for the SM-G935W8 of which I grabbed from Samsung SmartSwitch on Windows. I am an experienced programmer in the Languages C# and Java. I have made a few personal apps that aren't even worth mentioning.
Goal:
My Goal is to contribute and dedicate myself to the Canadian Users because I have noticed the lack of support towards them. I am currently working on a ROM based on the stock firmware of which I am trying to release. I am going to need help on it as I am rather new to this area of Android but nonetheless does not mean I am terrible. I have done my research and have gotten some of the tools that are needed and have already successfully built a ROM just not able to boot it but I believe it is because I missed a step with the boot.img. The main tool I am using is the one that Superr has created called SuperRs_Kitchen. I am currently using v1.0.5.6 as the newest version I was having issues with.
If anyone has any questions, please feel free to ask me and I will try and answer them to the best of my ability.
I will provide an upload link once and if I get approved for requesting developer access. If I don't I will then use a different mirror to host it.
Please be patient, and I do not have an ETA on when the link will be up.
Welcome Francesco! Nice to see some W8 support here! Really looking forward to see development from you
Sent from my SM-G935W8 using Tapatalk
FrancescoM01 said:
Introduction:
My name as you may be able to tell is Francesco, and I am a long time user of the Samsung Galaxy S Series Devices. My current device is the SM-G935W8. I have just requested Developer Access on Android File Host so I can give access to everyone for the Stock Firmware for the SM-G935W8 of which I grabbed from Samsung SmartSwitch on Windows. I am an experienced programmer in the Languages C# and Java. I have made a few personal apps that aren't even worth mentioning.
Goal:
My Goal is to contribute and dedicate myself to the Canadian Users because I have noticed the lack of support towards them. I am currently working on a ROM based on the stock firmware of which I am trying to release. I am going to need help on it as I am rather new to this area of Android but nonetheless does not mean I am terrible. I have done my research and have gotten some of the tools that are needed and have already successfully built a ROM just not able to boot it but I believe it is because I missed a step with the boot.img. The main tool I am using is the one that Superr has created called SuperRs_Kitchen. I am currently using v1.0.5.6 as the newest version I was having issues with.
If anyone has any questions, please feel free to ask me and I will try and answer them to the best of my ability.
I will provide an upload link once and if I get approved for requesting developer access. If I don't I will then use a different mirror to host it.
Please be patient, and I do not have an ETA on when the link will be up.
Click to expand...
Click to collapse
im from sprints s7 edge i have a question. where is the downloaded file found in smart switch. ive looked every where.
what folder does windows put it in
thanks
Robalboa said:
im from sprints s7 edge i have a question. where is the downloaded file found in smart switch. ive looked every where.
what folder does windows put it in
thanks
Click to expand...
Click to collapse
When SmartSwitch says it's downloading your firmware:
If you open up the run dialogue, type in %APPDATA% you will be brought to the Roaming folder. Click in the address bar to actually go to the APPDATA Folder, click Local, then go into the Temp folder.
Sort the results by last modified.
You will see one that has a random generated name and is a .tmp file. Keep your eye on this file and the size. Keep pressing refresh. Once that file is done another file will be created above it with the exact same name but it will be a zip file. Keep an eye on the file size as for this one as well. Keep refreshing until it the file size stops changing. In my experience it's still the exact same size as the tmp file, but just wait about 5 seconds after it stop changing, then copy it to somewhere like your desktop.
jark99 said:
Welcome Francesco! Nice to see some W8 support here! Really looking forward to see development from you
Sent from my SM-G935W8 using Tapatalk
Click to expand...
Click to collapse
Thank you. I know there isn't much support for this device, but the ROM I believe the one that is called Renovated Edge does work on the W8 version, but it will change your CSC to XAC and it was a real pain trying to get it back to RWC. Actually took me a couple days to figure out how to do it.
FrancescoM01 said:
Thank you. I know there isn't much support for this device, but the ROM I believe the one that is called Renovated Edge does work on the W8 version, but it will change your CSC to XAC and it was a real pain trying to get it back to RWC. Actually took me a couple days to figure out how to do it.
Click to expand...
Click to collapse
I am happy with echoerom for my G935W8
Sent from my Pebble Time
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