Related
Hey! i have a problem....i have a very boring phone...huawei ascend y200. I am bored to see everyday the same icons and that nasty look.I have android 2.3.6. I don't know if my phone support a higher android version.And...i want to change a bit the look of my android...but without launchers and other things.....I saw something nice...it was called jellyBean Revolution.If someone can help me to improve the look of my phone...i will be very pleased! Also i need to root it...and i tryed every method that i ve found without succes..
Thanks a Lot !
Regards,
Alin!
Hi there
The first thing you have to do before even start to look at how you want your mobile to look like is to Root it. By Rooting it you'll open up heaven's gate's in the Android world such as installing custom Roms, top notch apps, control your mobile and not your mobile control you, etc.
You really want to have a look at this link especially at what MoH21 comments and teaches for he is showing you how to Root your mobile. I cannot stress enough for you to read and read and read very well until you're sure of what you're doing.
Here's the link: http://forum.xda-developers.com/showthread.php?t=1727636
After that you can then start looking for proper custom Roms for your mobile and do the next steps like *Bootloader Unlock *CWM Install
...all of them are important and sometimes depending on which method of Root you choose (or have available really) the CWM comes included...
TIP: search in the Forum for a method to see if your Bootloader is locked or unlocked as that's crucial to know.
*for you to Google search.
Don't forget to thank me and MoH21 also for his tutorial
ac3ofS2 said:
Hi there
The first thing you have to do before even start to look at how you want your mobile to look like is to Root it. By Rooting it you'll open up heaven's gate's in the Android world such as installing custom Roms, top notch apps, control your mobile and not your mobile control you, etc.
You really want to have a look at this link especially at what MoH21 comments and teaches for he is showing you how to Root your mobile. I cannot stress enough for you to read and read and read very well until you're sure of what you're doing.
Here's the link: http://forum.xda-developers.com/showthread.php?t=1727636
After that you can then start looking for proper custom Roms for your mobile and do the next steps like *Bootloader Unlock *CWM Install
...all of them are important and sometimes depending on which method of Root you choose (or have available really) the CWM comes included...
TIP: search in the Forum for a method to see if your Bootloader is locked or unlocked as that's crucial to know.
*for you to Google search.
Don't forget to thank me and MoH21 also for his tutorial
Click to expand...
Click to collapse
I tried that .... but...it doesn't work.maybe An other tutorial may help me...
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
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
Here was a Guide. Someone said people don't care about Me or My Work so...
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
nolihowell said:
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
Click to expand...
Click to collapse
Yes, You need to be unlocked, otherwise is there no chance to flash with fastboot. Besides the rooting of the Kernel is everything Stock. Everything works so far even with GSIs
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
nreuge said:
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
Click to expand...
Click to collapse
My Bad, it is the UK one... I'm also still waiting for customized EU which was always My Choice for Xperia Sources and Development. I'm currently working with GSIs on My Xperia 5 but think i will Release some Stock work soon since i prefer Xperia Android actually over AOSP...
Users will be able to use any Base Firmwares (Android 10) for it but i will personally Test on Custom EU :fingers-crossed:
@Miustone will you be releasing a boot.img for the latest security patch?
fcb13 said:
@Miustone will you be releasing a boot.img for the latest security patch?
Click to expand...
Click to collapse
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Miustone said:
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Click to expand...
Click to collapse
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
charlatan01 said:
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
Click to expand...
Click to collapse
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Miustone said:
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Click to expand...
Click to collapse
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
charlatan01 said:
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
Click to expand...
Click to collapse
Prefer a newer Base Firmware over a newer GSI. A Android 9 GSI will run better with Android 10 Kernel as vice versa. Pie will be no Problem if You run Android 10 Vendor and Kernels. Happy flashing! :fingers-crossed:
EDIT: There are also PE Android 10 Builds out there... https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
help me
hi i need a boot.img for my xperia 1 j8170 please help me 10 (55.1.a.3.107)
This method has always been magisk module not friendly. audio compat worked. But once i through more at it it bricked device and had to reflash with new flasher
Hi
Can you please patch this file for me (Device = J9210 Dual | Firmware = 55.1.A.3.149)
boot_X-FLASH-ALL-A2CD.7z
Kind Regards
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
BuyXRPnow! said:
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Miustone said:
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Click to expand...
Click to collapse
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
BuyXRPnow! said:
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
Click to expand...
Click to collapse
First of all. Good choice to get rid of a Samsung Device Like i did with My S9+! Sammy is pushing Android into a Appleish Edge that shouldn't exist...
Just like Huawei. But different Story...
Out of My View with Years of expierence with different Brands is SONY one of the Most supporting OEM in Views of Android Development besides the Fact they Always excluded some functionality of the included Smartphone Hardware. For example:
-Xperia Z1 lost the Complete Camera Function after unlocking (Got fixed with a Update later after Claims from Customers) and lost Display enhancements + Camera Noise reduction
-Xperia Z3 lost the Vibrant Display Colors after unlocking (Aka Bravia Engine) which ended Up in washed Out Colors and was still loosing Noise reduction
-Xperia XZ Premium still loosing enhancements after unlocking plus the loss of Camera Noise reduction
And now the Xperia 5...
Sony used for the First Time Samsung Sensors for the Cameras instead of own ones with High Resolution. So no Noise Reduction needed anymore. Finally OLED, so no washed Out colors without Display Enhancements.
I'm quite Happy with this One since you don't loose Something Essential. Besides that have i Always Managed since the Z3 to fix almost all Problems on Xperias with native Android functionalities that is used on other Devices. Eg. For the Display, Audio, Camera, Mics and so on.
And thats the final Point. While older Devices Had the Chance to Backup and restore the TA Partition or even to use a Recovery on locked Bootloader (I've also worked with this for some Time) which allowed to make Your Device Complete Stock again. We don't really have that Options anymore. So i would say an Unlock is a final Step. But to be honest. I sold many Devices claimed as unlocked and rooted and it hasn't Cut the Price at all. And even if You Don't. I don't think a normal Person will See a difference after unlocking and relocking
Is it worth it? For Me a clear Yes! I never looked back after unlocking any of My "Hundreds" of Devices i used. Magisk and GSIs alone are really worth the Unlock Out of My View actually. You can do so much with Android and it finally doesn't feels Bad anymore on Xperias. My SOM (Magisk based ROM (Systemless-On-Memory) will do a lot of awesome Things with Our Xperias (1 & 5). Another good Reason maybe...
It could be smart to make a Video which explains how to get My Work on Your Xperias. From unlocking to Flashing... Would really like to do that after some preparing for it. Possible that there are a lot of People who don't even know about Bootloader unlocking so it really could be cool. I already did some Videos in the Past; https://www.youtube.com/user/TheMarius517
Think i got a bit lazy since the Software alone takes so much time These days. But i will do My best to get People in Touch and to Show everything step by step.
Lot of Text but Hope i made Your decision to Unlock or not easier... Don't think about the Future of Your Device. Think about what You want from it right now...:good:
Btw. Not Sure but You could try ADB to remove Apps. But idk. If IT IS possible with Google Apps (Locked Bootloader Method)
All the Best,
Miu
Thank you! You are a hero. I will be waiting for your updated guides and possibly a video for noobs. Appreciate your time!
Peace.
Optimized the Thread Structure and Instructions. Optimized Thread Title. Updated Boot Image / Kernel to latest EU .149
I just bought a Motorola Moto E22 and want to install a custom ROM to get rid of google stuff.
It seems Lineage does not support this phone yet, but I found this LineageOS22 guide which I have no idea it is reliable or if it has anything to do with the official Lineage project.
Any clarification or suggestions for alternative privacy respecting ROMs that work on Moto E22 would be much appreciated.
First of all, don't do these before completing 1 year of buying. You will lose warranty for unlocking bootloader.
Second thing is, if any official rom is not supported, you can definitely use unofficial version from xda. Developers try their best to fix issues with unofficial roms. If you don’t know if it’s reliable or not, read the comments to learn about bugs, issues and positive sides.
Don't be afraid of trying roms built for your model. Because by chance if you don’t find the rom good, you can revert back to stock rom using rescue & smart assistant tool (official software from lenovo/moto)
And before getting started, take note of your model number. Also you have to install device info hw app & click on system there. There you have to find what is your device called in developments. The name will be written beside "device" title (not sure). For example, my moto e5 is called nora in development.
N.B. Dont use any unofficial rom from outside of xda!
Tawsif999 said:
First of all, don't do these before completing 1 year of buying. You will lose warranty for unlocking bootloader.
Second thing is, if any official rom is not supported, you can definitely use unofficial version from xda. Developers try their best to fix issues with unofficial roms. If you don’t know if it’s reliable or not, read the comments to learn about bugs, issues and positive sides.
Don't be afraid of trying roms built for your model. Because by chance if you don’t find the rom good, you can revert back to stock rom using rescue & smart assistant tool (official software from lenovo/moto)
And before getting started, take note of your model number. Also you have to install device info hw app & click on system there. There you have to find what is your device called in developments. The name will be written beside "device" title (not sure). For example, my moto e5 is called nora in development.
N.B. Dont use any unofficial rom from outside of xda!
Click to expand...
Click to collapse
Thanks for the quick response.
Privacy is a greater concern than warranty, so much so that I would have got the PinePhone if I could, but the best I can do is try to mitigate the damage made by stock android spyware and Motorola bloatware.
I'm more than willing to test unofficial roms, the problem is that there doesn't seem to be any available for my model here on xda, not even an official thread yet.
The LineageOS20 for Moto E22 link I found does seems a bit suspicious as there is nothing about it here on the forum.