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.
I hope this is the right thread.
Hello bois, I got a QiKU 360 N4 which is a pretty sick phone for the money I paid it.
It came out recently on the chinese market and its bootloader is locked.
I googled a bit and found some tutorials tho unlock the bootloader and install TWRP, because somebody compiled that already! Awesome, right?
Too bad are in chinese, yeah.
Google translate doesn't help that much, it is incomprehensible, and even if it did help: I am required to sign up to the chinese forum to read the whole tutorial (which requires me to understand how to sign up) and from what I understand the procedure makes use of a software running on windows to enter the bootloader and such software is in chinese only!
So I am looking for some kind soul who could translate the procedure and, if possible, reupload the necessary files somewhere so people like me wouldn't have to sign up to the linked chinese forum to get them.
In exchange I can offer some tips on health and fitness for I have a master in sports sciences. Or, I could offer you a beer?
P.S. sadly xda does not allow me to post links, can link in private... I guess.
Robert Hall said:
I hope this is the right thread.
Hello bois, I got a QiKU 360 N4 which is a pretty sick phone for the money I paid it.
It came out recently on the chinese market and its bootloader is locked.
I googled a bit and found some tutorials tho unlock the bootloader and install TWRP, because somebody compiled that already! Awesome, right?
Too bad are in chinese, yeah.
Google translate doesn't help that much, it is incomprehensible, and even if it did help: I am required to sign up to the chinese forum to read the whole tutorial (which requires me to understand how to sign up) and from what I understand the procedure makes use of a software running on windows to enter the bootloader and such software is in chinese only!
So I am looking for some kind soul who could translate the procedure and, if possible, reupload the necessary files somewhere so people like me wouldn't have to sign up to the linked chinese forum to get them.
In exchange I can offer some tips on health and fitness for I have a master in sports sciences. Or, I could offer you a beer?
P.S. sadly xda does not allow me to post links, can link in private... I guess.
Click to expand...
Click to collapse
Please PM me the link to the website . I don't know Chinese but I remember a root tool that was in Chinese and I will try my best to "mimic" how I got my way around that.
RAZERZDAHACKER said:
Please PM me the link to the website . I don't know Chinese but I remember a root tool that was in Chinese and I will try my best to "mimic" how I got my way around that.
Click to expand...
Click to collapse
I've sent you a message however I don't think you'll manage without knowing chinese
The tool they use is to unlock the bootloader and it's a proprietary tool.
Robert Hall said:
I've sent you a message however I don't think you'll manage without knowing chinese
The tool they use is to unlock the bootloader and it's a proprietary tool.
Click to expand...
Click to collapse
Yea I saw it, I'll see what I can do...
I'm sorry but I did not have time yesterday. I don't have access to a proper computer so I am using my raspberry pi to do all this. Since it does not have a photo editor I am working on a google slide document that will be accessible by link. I'll post it here as fast as I am done
---------- Post added at 10:36 PM ---------- Previous post was at 10:20 PM ----------
Here is how far I have come. I assume you have to download a bunch but at least the company gives you information. I've heard numerous people who buy Chinese phones and are stuck with whatever software they offer.
Yeah there is no chance to write a custom rom because the kernel source is never being given by Mediatek.
However having the ability to backup and play around with the stock firmware is great.
Robert Hall said:
Yeah there is no chance to write a custom rom because the kernel source is never being given by Mediatek.
However having the ability to backup and play around with the stock firmware is great.
Click to expand...
Click to collapse
True, I like how it has become a meme that "I'll die before mtk releases their sources".
Any more news on this? Loving my N4 so far, but would like to install TWRP and gapps, but not quite sure how. Have read somewhere that Kingroot has worked on other Qiku/360 phones but haven't got that far myself. Any chance you could send me that link to me too, your googling skills are clearly far superior to my own!
Hi.
I wiped my data from the stock recovery and now i am stuck at boot logo.I don't know how that happened.but i think i have to flash stock firmware which i cant find anywhere.
Qiku forum is unresponsive and there is no other place with info of this rare phone.
Help me out here please
help me please! I.want to unlock my QIKU N4S, but i can not download from chinese forum. thank you a lot！
Bootloader unlock - HERE
Found some ROM's also .... Althought, You'll Need TAMPERMONKEY and Baidu Download Script for Tampermoney
ROM'S - HERE and other Tools + rom's HERE
There is a whole Qiku N4 forum but it's in chinese .... didnt have time to bother with it,
since it requires to be registered ...
And, as bonus ...
I found Russian modified ROM's ....
HERE for HW version A01
and
HERE for HW version M02
TWRP Recovery - HERE
Check HW version of your phone, if you want to flash roms and BEFORE screwing it up.
Hope that's enough for now ....
p.s. Be carefull what are you doing and flashing into phone. Links I posted are from third party sources,
people reported they are working, but all you do - you do on your own responsibility.
b.r.
Alex
mobilexpert said:
Bootloader unlock - HERE
Found some ROM's also .... Althought, You'll Need TAMPERMONKEY and Baidu Download Script for Tampermoney
ROM'S - HERE and other Tools + rom's HERE
There is a whole Qiku N4 forum but it's in chinese .... didnt have time to bother with it,
since it requires to be registered ...
And, as bonus ...
I found Russian modified ROM's ....
HERE for HW version A01
and
HERE for HW version M02
TWRP Recovery - HERE
Check HW version of your phone, if you want to flash roms and BEFORE screwing it up.
Hope that's enough for now ....
p.s. Be carefull what are you doing and flashing into phone. Links I posted are from third party sources,
people reported they are working, but all you do - you do on your own responsibility.
b.r.
Alex
Click to expand...
Click to collapse
if you want root your phone,you must use ROM V019
mobilexpert said:
ROM'S - HERE and other Tools + rom's HERE
Click to expand...
Click to collapse
Hello Alex,
Those links are sadly down.
Do you know any other link to a stock N4 image and scatter file that I could use to factory-reset a pattern-locked N4 ? I got my hands on a discarded one, but the factory reset option in recovery mode requires that cloud account be first deleted, which I can't to because of the pattern lock.
Thanks !
EDIT :
Sorry, I spoke too fast. I gave another try and the links are up, though in chinese. I'll try to get what I can. Thank you !
I am Chinese
Robert Hall said:
I hope this is the right thread.
Hello bois, I got a QiKU 360 N4 which is a pretty sick phone for the money I paid it.
It came out recently on the chinese market and its bootloader is locked.
I googled a bit and found some tutorials tho unlock the bootloader and install TWRP, because somebody compiled that already! Awesome, right?
Too bad are in chinese, yeah.
Google translate doesn't help that much, it is incomprehensible, and even if it did help: I am required to sign up to the chinese forum to read the whole tutorial (which requires me to understand how to sign up) and from what I understand the procedure makes use of a software running on windows to enter the bootloader and such software is in chinese only!
So I am looking for some kind soul who could translate the procedure and, if possible, reupload the necessary files somewhere so people like me wouldn't have to sign up to the linked chinese forum to get them.
In exchange I can offer some tips on health and fitness for I have a master in sports sciences. Or, I could offer you a beer?
P.S. sadly xda does not allow me to post links, can link in private... I guess.
Click to expand...
Click to collapse
Hello Is the 360n4 on your hand still there? I can help you with the problem!
1915007283 said:
Hello Is the 360n4 on your hand still there? I can help you with the problem!
Click to expand...
Click to collapse
Hi !
I'm not the original poster, but am in the same situation, and have a N360 at hand. Are you willing to help me ?
Hello
breversa said:
Hi !
I'm not the original poster, but am in the same situation, and have a N360 at hand. Are you willing to help me ?
Click to expand...
Click to collapse
Is the cell phone on your hand 360n4? This cell phone has two versions of 360n4 and 360n4s
Yes, it a 360N4, not a 360N4S.
What I'm trying to do is follow that howto : http://www.cnroms.com/360-n4-061-unlock-bootloader-install-twrp-recovery.html to downgrade it, then factory reset it and install TWRP.
However, I can't read chinese (can't even tell whether it's cantonese or mandarin). Google Translate helps, but most link seem to be broken, and when they're not, the download speed is abysmally slow (several days…).
Is there any way you could help me ? Maybe get the needed files and reupload them somewhere faster ?
I see
breversa said:
Yes, it a 360N4, not a 360N4S.
What I'm trying to do is follow that howto : http://www.cnroms.com/360-n4-061-unlock-bootloader-install-twrp-recovery.html to downgrade it, then factory reset it and install TWRP.
However, I can't read chinese (can't even tell whether it's cantonese or mandarin). Google Translate helps, but most link seem to be broken, and when they're not, the download speed is abysmally slow (several days…).
Is there any way you could help me ? Maybe get the needed files and reupload them somewhere faster ?
Click to expand...
Click to collapse
We have a lot of links, and if you have QQ, I think I can give you faster links
Because I don't know what tools you use to chat
1915007283 said:
We have a lot of links, and if you have QQ, I think I can give you faster links
Because I don't know what tools you use to chat
Click to expand...
Click to collapse
QQ ? What's that ?
In case your links are private, why not using private messages on this here forum ?
I'm sorry
breversa said:
QQ ? What's that ?
In case your links are private, why not using private messages on this here forum ?
Click to expand...
Click to collapse
I just came to this forum, I still don't know how to send messages
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
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?
Hi,
Today I am here with new post.
As you know I am now posting new posts daily.
Many of you have a phone that is less popular and there is no active developer for that device but did you know that there is a way that you can be a developer of your own.
There is team Hovatek that they made up a tool to make TWRP maker tool which you can use to make your own TWRP recovery for your phone and be an engineer of your phone but note that your phone must have common chipset on it like Mediatek, Spreadtrum, etc and your android version must be Android 5,6,7,8,8.1,9 otherwise you need to port it your self.
I am making this post for people like me to help them get a test of Custom recovery.
Thanks, Folk.
I will continue it on Part 2
Roktim iH said:
Hi,
Today i am here with new post.
As you know i am now posting new post daily.
Many of you have phone that is less popular and there is no active developer for that device but did you know that there is a way that you can be a developer of your own.
There is team Hovatek that they made up a tool to make TWRP maker tool which you can use to make your own TWRP recovery for your phone and be a engineer of your phone but note that your phone must have popular chipset on itself like Mediatek,Spreadtrum etc and your android version must be Android 5,6,7,8,8.1,9 otherwise you need to port it your self.
I am making this post for people like me to help them get a test of Custom recovery.
Thanks Folk.
I will continue it on Part 2
Click to expand...
Click to collapse
Did you just say Mediatek and Spreadtrum are "popular" chipsets?
Lol, no, I don't think so.
Most real developers avoid devices with those processors.
Sent from my SM-S767VL using Tapatalk
well I'm so glad to heard about it, mm and maybe I'm so happy about it . well absolutely I can't wait for this one. I'll see you at the next part
so where is the next part?
Sorry
MarvinMod said:
so where is the next part?
Click to expand...
Click to collapse
Sorry for replying late. But I will make it soon.