Related
Guardian Rom by x942Thanks to:
The Guardian Project
Cyanogen Mod
Android Open Source Project
Open-Pdroid Project
Any one else I am missing
Click to expand...
Click to collapse
What is Guardian Rom?
Guardian ROM is a custom android ROM multiple devices. The ROM is completely Open Source and based off of the CM10.1. While this build is stable because it's based on CM10.1 it is a preview so please expect some bugs, & missing features (i.e updater).
What Features does Guardian Rom have?
Kernel is hardened with SecDroid Tweaks.
ROM is patched with and includes OpenPdoird for
permissions management.
Guardian Project apps are pre-installed – These include Orbot (Tor), Gibberbot (Secure IM),
and more.
CSSimple and OStel (https://guardianproject.info/wiki/Ostel) are included as replacements to the
built calling apps. providing encrypted communications.
If encryption is enabled and password is entered wrong 10 times the phone wipes user data.
Click to expand...
Click to collapse
Coming Soon:
Including support for Deniable Encryption (similar to Truecrypt hidden volumes).
Including GRSecurity for exploit mitigation and more secure phone.
Including SQLCipher to ensure all data is encrypted whenever possible
Including a customer “app store” for our repos.
Different lockscreen pin and Pre-Boot authentication password.
Auto-Prompt for encryption setup on first boot.
Click to expand...
Click to collapse
How to use:
Simply flash the flashable zip through your favorite custom recovery. (TWRP is recommended as it supports encrypted devices). Once flashed you should enable Full Disk Encryption by doing the following (may very depending on device):
Code:
Settings --> Security ---> Password [enter a strong 8-16 char password]
Than
Code:
Settings --> Security ---> Encryption --> Enable Encryption
Downloads:Downloads are over here.
Please verify the downloaded file with the attached GPG signature to ensure is is a legit copy.
GAPPS
Google Apps are NOT included and before you flash them you may want to read this article.
UPDATES:
Since this is a preview I have not had a chance to remove or modify the CM Updater. Please do NOT use it as you will be flashing a stock CM10.1 build and not Guardian Rom. This will be fixed shortly.
Reserved.
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
baz77 said:
you could cherrypick some stuff from here
selinuxproject.org/page/SEAndroid
Click to expand...
Click to collapse
I may use SeAndroid. Right now I am focusing on the encryption side of things instead of the exploit mitigation side. That will come later.
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
azrash said:
Been following your work on sec Droid, this looks like a very very good start! May I know which version of CM that you used for this? Or it is based on the latest repo when you built it.
Thanks!
Flowed from my Nexus⁴
Click to expand...
Click to collapse
Awesome! Thanks! It's is based off the latest repo. I simple pulled and than modified the sources. I am currently getting some hosting for our own repo and Tor Hidden service for downloading. Stay tuned much more to come.
TimeAndroid said:
Look'in good, might try.
Click to expand...
Click to collapse
The next build will have an AOSP 4.2.2 base with Mobiflage built in. Also Lock screen PIN and Pre-Boot PINs are now separated. So you can use a simple 4 digit pin on the lock screen and a 32 character pin at boot.
Also for more security you have to passwords one for the "outer volume" which you use as you daily usage and one as "hidden volume" which is your hidden os. You use the second for anything sensitive. That way if an attacker tries to force you to give up your password you just give up the outer volume (decoy) password. There is no way to prove the hidden volume exists.
Encryption also uses AES-256-XTS now instead of AES-128-CBC. Better key length and protection against watermarking attacks.
EDIT: If anyone wants early access please PM. The build is not ready for prime time as there is no GUI for encryption but can be used as a daily driver.
SecUpwN said:
No, I'm sure you're right. But since he explicitly stated that he won't build an ('unofficial') AOKP version, I'm looking for a way to get in the favor of the securiry modifications without gaving to switch to another ROM. It's just that AOKP has so many cool simplifications compared to CyanogenMod, I'd like to avoid a switch backwards. Maybe he could create an unsupported AOKP version every month? Possible?
Click to expand...
Click to collapse
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
DontPushButtons said:
I'm guessing the modifications he has been making go a little further beyond a flashable zip. Otherwise he would've done that instead of making a whole rom around privacy.
Could be wrong..
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes. I custom kernel is needed at the very least. Not to mention removal of Google Apps and tweaked UI for encryption (mobiflage). All of these are OS level tweaks and cannot be made into a ZIP.
droidkevlar said:
Or you could compile your own. Not trying to sound like a d**k but he had already stated numerous times he is only doing Cm base and yet u and others keep saying do this for aokp. There is a reason he is using cm as a base.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. AOKP will NOT be supported. EVER. If anyone wants a different base download the source code from my github and compile it yourself. Build documentation is on there. Furthermore AOKP and CM10.1 are both great roms, however there are too many variables. Both have a ton of unneeded binaries and settings. We cannot guarantee security are these builds. We choose CM10.1 because it's fully open source and has fewer complications then AOKP. On NEXUS devices we are using AOSP modified with our security tweaks. On non-nexus we use CM10.1 for now for simplicity.
I am hoping with the recent Google Edition devices it will be easier to port/compile AOSP onto those devices.
TL;DR:
WE WILL NEVER OFFICIALLY SUPPORT AOKP.
Thanks for understanding.This message is only meant to stop these requests, not to be rude so please don't take it that way.
Cleaning
This thread is in the DEVELOPMENT section. And is for the "Guardian Rom [Secure] [Privacy] [Preview]".
If you need to report an issue or bug then READ THIS POST ABOUT BUG REPORTS
Keep ALL posts aimed at the ROM development.
This thread is NOT A Q&A thread.
So don't ask why the WiFi won't work, post a LOGCAT of the actual event or it did not happen.
I have cleaned this thread.
If you repeatedly make junk posts, then INFRACTIONS will follow.
~JAB
Hey @x942, where is our Android 4.3 version of this funky ROM?
SecUpwN said:
Hey @x942, where is our Android 4.3 version of this funky ROM?
Click to expand...
Click to collapse
We are working toward this. The issue we are having is that while 4.3 is latest 5.0 may be just around the corner. We don't want invest a ton of effort just to have re-port everything to 5.0 if it's released 2-3 months from now. That's not to say 4.3 won't happen. It's just we are focusing on adding more security. For now stable is 4.2.2.:good:
Am I missing where to find the flashable zip?
Sent from my Nexus 4 using xda app-developers app
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
koz said:
Will this ever come to a Samsung Galaxy 3, or are your plans only for Nexus devices?
Click to expand...
Click to collapse
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Request
Hi,
Please add the new moto g xt1032 to your list of planned devices - it would be a great way to get more people secured as it is a very popular handset
Thanks for all your hard work!
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
Has this ever been developed for the Galaxy S3? I haven't been able to find a download anywhere...
@X942 gaurdian rom sounds very interesting to me. would also like the att slll i747 to be added on list for consideration for dev.
am not a dev myself.
thank you for your work/time/energy. :thumbup:
err on the side of kindness
good
Sent from my Nexus 4 using XDA Premium 4 mobile app
x942 said:
S3 is underway. We have support for:
S3, HTC One, Nexus 4, Galaxy Nexus, S4, Nexus 7 and soon Moto X, Note 3 and Nexus 5.
Click to expand...
Click to collapse
I cant find a download for the Note 3 ROM. The only thing I read about it is an update on http://shadowdcatconsulting.com/blog/ saying that support will come soon.
Hello, it appears that ever since I switched to Project Fi from ATT, I'm starting to see some 'bugs'. I noticed that my current build number of LYM48I is older, and a generic firmware image. I'm wondering if I should upgrade to LVY48H, which according to (https://developers.google.com/android/nexus/images) appears to be the latest Project Fi image for the Nexus 6?
Quick details about my setup:
- I am on the Nexus 6 (purchased directly from Google)
- Android version 5.1.1
- Build number LMY48I
- Baseband version MDM9625_104446.01.02.101R
- I don't want to upgrade to 'Marshmallow' as from what I've read, is not officially supported by Fi
- My phone was rooted before switching over to Fi using the following procedure: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 (did not create a custom recovery, etc)
Thanks in advance
gil_happy said:
Hello, it appears that ever since I switched to Project Fi from ATT, I'm starting to see some 'bugs'. I noticed that my current build number of LYM48I is older, and a generic firmware image. I'm wondering if I should upgrade to LVY48H, which according to (https://developers.google.com/android/nexus/images) appears to be the latest Project Fi image for the Nexus 6?
Quick details about my setup:
- I am on the Nexus 6 (purchased directly from Google)
- Android version 5.1.1
- Build number LMY48I
- Baseband version MDM9625_104446.01.02.101R
- I don't want to upgrade to 'Marshmallow' as from what I've read, is not officially supported by Fi
- My phone was rooted before switching over to Fi using the following procedure: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 (did not create a custom recovery, etc)
Thanks in advance
Click to expand...
Click to collapse
lol, not officially supported by fi. you do realize that the n5x and n6p are both fi phones, right? and you do realize that they both come with marshmallow, right? marshmallow is the build that you should be on, as in its the latest. and there isnt a special m build for fi. there's only ine build if marshmallow, and its for fi as well.
..
Great! Thanks so much.... I guess my question is this , which method should I use to upgrade to Marshmallow? Will I lose all of my data? Keep in mind I 'only' rooted my device using the link in my original post.
..
gil_happy said:
Great! Thanks so much.... I guess my question is this , which method should I use to upgrade to Marshmallow? Will I lose all of my data? Keep in mind I 'only' rooted my device using the link in my original post.
Click to expand...
Click to collapse
cam30era said:
You're going to get plenty of advice on that question from other members. Let's just say, read, understand, and pick your poison.
Click to expand...
Click to collapse
fastest and easiest thing to do would be to flash the factory image. right way is via fastboot while youre in the bootloader. but there are ways using a toolkit as well.
..
cam30era said:
While Project Fi team did originally state that they did not recommend flashing MRA58K, that position changed about 10/15, when the OTA started rolling out to Fi users.
Click to expand...
Click to collapse
Source, please? In the official Project Fi support forum, the company line has not changed. See the relevant thread from the forum's most official spokesperson. It has never been superseded.
Thanks for this... do both methods completely 'wipe' the phone of all its data?
..
cam30era said:
The best source is the OTA from LVY48H to MRA58K that is rolling out to Fi users.
Click to expand...
Click to collapse
I know that the OTAs exist and that most of their URLs have been discovered by the community. That's not the point. I was challenging your assertion that the official policy of Project Fi opposing the flashing of factory image MRA58K has been withdrawn. It has not. For that matter, they have never announced an official rollout of the Marshmallow OTAs. With previous OTAs, there has been such an announcement.
..
cam30era said:
Granted. Google is in an untenable position here. Caught between a rock and a hard point when they started pushing OTAs to Fi users on the one hand...
So, what's your advice to the OP?
Click to expand...
Click to collapse
Depends on his risk tolerance. As a purely technical matter, nothing prevents him from flashing any build he wants. If he prefers an officially sanctioned OTA path, he should probably sit tight and wait for Marshmallow to be pushed out to him.
His concern that he is on the "wrong" build within 5.1.1 is misplaced. Project Fi officially supports three different Lollipop forks: the Fi-specific builds, the T-Mobile builds, and the generic Nexus builds. There will be an OTA path from each fork to the new unified Marshmallow. (But one messy detail is that the most recent round of security updates also spawned a fourth AT&T fork build LMY48W, which so far has no OTA path to 6.0. Some Fi users report that they have been OTAed to LMY48W .)
Personally, I use a daily driver on FI that runs the T-Mobile fork, and I want to keep it stock. I am in no hurry to flash the Marshmallow build because of multiple reports that doing so would probably break my existing Band 12 data service, which I want to keep as long as possible. So I am awaiting the OTA to be pushed out officially, and hoping that the Band 12 issue gets resolved soon somehow, even if that is a subsequent build.
I would assume the reason for the 3 forks is that there must be specific fixes or enhancements to each firmware load, otherwise what is the point of having 3 forks? Meaning, since I'm on Project Fi, it would make sense to be on the specific Project Fi load and not the T-Mobile or generic Nexus build.
gil_happy said:
I would assume the reason for the 3 forks is that there must be specific fixes or enhancements to each firmware load, otherwise what is the point of having 3 forks? Meaning, since I'm on Project Fi, it would make sense to be on the specific Project Fi load and not the T-Mobile or generic Nexus build.
Click to expand...
Click to collapse
We really don't know what was different about the Fi-specific build. Google claimed the difference was not very significant, but never disclosed what it was. The T-Mobile fork was created to support TMO's proprietary WiFi calling. And of course the generic Nexus fork was mainstream Android. It might be that Project Fi management just kept all three as officially supported because they wanted to test performance with three different radios. Remember, it is all beta (or beta-like), and we are all lab rats.
People speculated about the relative merits of the Fi build for months, with no rigorous testing that really proved anything beyond anecdotal placebo effects. But all this specualtion is about to become ancient history with the unification in Marshmallow. This is supposed to happen OTA any day now, and already has happened for some. So I can't see any great value in flashing the old Fi build at this point because it isn't worth the hassle. But it would do no harm.
boomerbubba said:
We really don't know what was different about the Fi-specific build. Google claimed the difference was not very significant, but never disclosed what it was. The T-Mobile fork was created to support TMO's proprietary WiFi calling. And of course the generic Nexus fork was mainstream Android. It might be that Project Fi management just kept all three as officially supported because they wanted to test performance with three different radios. Remember, it is all beta (or beta-like), and we are all lab rats.
People speculated about the relative merits of the Fi build for months, with no rigorous testing that really proved anything beyond anecdotal placebo effects. But all this specualtion is about to become ancient history with the unification in Marshmallow. This is supposed to happen OTA any day now, and already has happened for some. So I can't see any great value in flashing the old Fi build at this point because it isn't worth the hassle. But it would do no harm.
Click to expand...
Click to collapse
Thanks again.... I will attempt to upgrade to Marshmallow in the next day or so after a little more reading about 'how' to do this. As mentioned, I am rooted (no recovery) and will need to find out which of the 2 upgrade methods erase the phone.
I'm on a custom Marshmallow ROM (PureNexus) and easily activated Fi on it. Here's what I did, using a custom recovery (TWRP):
- downloaded M bootloader and M radio, PureNexus ROM and Gapps, and FiFix for dialer
- rebooted into TWRP
- removed my old carrier's SIM and left the SIM slot empty
- flashed M bootloader and M radio
- wiped everything except internal storage
- flashed PureNexus and its Gapps, and Fi Fix for dialer.
- booted and setup wizarded the new ROM on wifi, and updated ALL apps (most importantly Fi, Hangouts and Messenger, though I don't use the latter two) in Play. Had to enable Fi in Settings/Apps/Fi for it to updated by Play. Also allowed all permissions for Fi.
- put the Fi SIM into phone
- finally, ran the Fi app...
DONE.
Hope this is helpful to someone!
Sent from my Nexus 6 using Tapatalk
gil_happy said:
Thanks again.... I will attempt to upgrade to Marshmallow in the next day or so after a little more reading about 'how' to do this. As mentioned, I am rooted (no recovery) and will need to find out which of the 2 upgrade methods erase the phone.
Click to expand...
Click to collapse
I'm on Fi and upgraded to MM using the recovery flashable mages found in this thread. Make sure to read the entire op and also flash the bootloader and radio zips. Fi activated on my first boot and has functioned properly since.
A follow up to this... now today, my phone indicates I have a 'System upload downloaded' notification. When I try to install it, it fails. I believe this is because I have read something in the past that indicated it fails because my phone is rooted (and would need to be manually installed). If I'm going to attempt to manually install, is there any way to figure out via shell, ES File Explorer, etc what the name of this firmware is so that I can attempt to find it online somewhere and download?
Thanks in advance
Hello everyone. Those days I feel some to root my phone (ALE-L21 6.0 Dual SIM) to install custom ROMs like LineageOS with Android Nougat and use apps like WPS WPA Tester but other some I feel not because I'm still in warranty time (it ends after 1 year + the warranty isn't in my country) and I never rooted any device or even used Android (my lase phone was Nokia 110) so today I wanna to know why root is useful and why not and what can I use it for and what's the root dangerous? I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs? Like Radio FM doesn't work, screen recorder doesn't work or even has a bug?
AmirGTX said:
I need all informations about root. :laugh:
Edit: Is all custom ROMs has bugs?
Click to expand...
Click to collapse
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
keikari said:
I think main reasons for rooting and unlocking bootloader.
1. Devices with small memory you can install apps in to SD-card.
2. If you realy hate ads you can use Adblocking.
3. Install custom ROM or kernel to get better battery life/performance (with some devices these are only stuff that isn't perfectly stable but sill stable enoughfor daily use).
4. Uninstall unessesary system apps.
5. More customizing possibilities like change screen dpi(dots per inch --> smaller value gives smaller icons and text so you can fit more stuff in screen at the same time).
6. There is more things to do but this was of the top of my head.
Click to expand...
Click to collapse
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
fosco_ said:
IMO root yes, of course, many reasons pick the ones you like most: uninstall bloatware, tweak kernel parameters, activate hidden options, xposed, greenify...
Click to expand...
Click to collapse
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
AmirGTX said:
1. I use my device currently and needn't more space.
2. I already have Adguard, it's enough for me.
3. Yes, I've bored from the stock Android theme and want to change it.
4. I needn't to remove system apps because I don't even use them.
5. IDK what's this obviously. :laugh:
6. What else?
Click to expand...
Click to collapse
Well I forgot to tell most important reason, because you can : D
Nowdays that's prety much all the stuf that matters for regular user.
Maybe bagroundplayback for youtube if it isn't already possible with regular app.
And it's kind of a plus that you can back backup your full system in TWRP, thought main reson for backups is that you are testing something unstable or new stuff which you can only do with unlocked bootloader.
PS. Your logic in 4 is kind of weird XDD
And dpi is kind of like resolution of screen but still very different but you can think of it as a weird resolution setting
Azzureux said:
Root was a good thing on earlier versions of Android. Now I don't think it's a necessity.
Custom ROM's seems a good idea, but if you don't have official version from the developers I myself don't recommend it.
You can try deoxed, modified or trimmed versions of stock ROM, to get more features.
If you have a branded phone I recommend to unbrand it to obtain ROM updates easily.
I recommend to keep stock for now because we get security patches from time to time.
Click to expand...
Click to collapse
Can you explain more? I didn't got it :cyclops:
AmirGTX said:
What's IMO? What's bloatware? What's tweak kernel? What's all this? :silly:
Click to expand...
Click to collapse
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
AmirGTX said:
Can you explain more? I didn't got it :cyclops:
Click to expand...
Click to collapse
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
fosco_ said:
Are you kidding?
IMO = In My Opinion
bloatware = preinstalled apps you don't want but can't remove
tweak kernel = change kernel parameters such as min/max speed, governor, i/o scheduler, gpu speed and so
Click to expand...
Click to collapse
Oh alright +1, why I need root else? (I'm just collecting info b4 rooting my device)
Azzureux said:
I'll try to be brief.
First I rooted my Samsung Galaxy S plus, android version was 2.3.6. Was a good thing? Yes, I had good devs who not only made Rom's up to Lollipop (I use now KitKat on it) but also repartitioned the space available through Twrp giving me more space for apps.
My next one was Galaxy S3 mini, android version was 4.1. I rooted it. Was a good thing? Yes and No.
Yes was good because I could use apps for backup, to remove bloatware, and posible to try custom ROMs.
No... Because I didn't had good developers, every custom ROMs had issues. That made me feel cautious and only installed stock ROM's that gave me more personalization and stable use of the phone (that doesn't mean I don't have problems with it, but it's mostly caused by apps who are not 100% compatible with KK ROM's).
Now let's talk about P8 Lite.
1. Can I squeeze more time of use from battery? Yes, we got the option <Ultra battery>.
2. Can I disable bloatware? I can't remove apps but I can disable them (MM has an option for it).
3. Can I backup apps and data? Yes. We got an option for it.
4. Can I get security updates for my ROM? Yes, for now we get security updates from Huawei.
5. Can I customize my ROM? To a point... Yes, you can customize the interface through themes, and the theme itself using other apps.
6. Can I get Nougat (version 7 of Android).
No, and you can start blaming Google for the requirements asked for it.
Yes, if you buy the 2017 version of the phone.
Sorry I was not brief. :good:
Click to expand...
Click to collapse
Awesome, that's why I want to root it but I'm still waiting until LineageOS be available and stable without bugs for me. I bought my phone last year and updated it to MM 6.0 at 7 month of last year, now I have UPDATE.APP (got it from here) it has no bugs and too stable for me. So I saw tutorials here for rooting my device but it were too much big and I need to use my computer. NP if I used my computer but can't I root it using apps suck as KingRoot and then install the ROM? Also I want to know all thing about bootloader and unlocking it and all thing in this operation. I want to know to be deep for such as problems. Thanks for info
AmirGTX said:
Also I want to know all thing about bootloader and unlocking it and all thing in this operation.
Click to expand...
Click to collapse
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Azzureux said:
Few years ago, when we could not imagine that phones can get ROM updates, no one bothered about bootloaders. But after few years they were shocked to see old clients use same depleted phones with new ROM's.
If you look back, when Google started to release Android 3 and up, we can see that the manufactures didn't try to much to improve "the smartphones", the selling ideology was the same as before, manufactures imagined just few improvements for the new models.
But then iPhone appeared, Samsung Galaxy smartphone line appeared and rules changed. Everyone tried to sell smarter phones on the market, Apple had a closed system so everyone looked at Google and android delivered.
So after the "Wild West" period, manufactures wanted more control over their devices, don't forget that devices had hardware in many configurations, so to prevent bricked phones, to try to stop clients from destroying their devices and after ask for guaranty, bootloaders were invented. It's a compromising way for users to obtain root access and avoid warranty claims.
Now, we see that Google stepped a bit, with Android 7, by limiting the compatibility asking for minimum hardware from manufactures. It's a way to make clients buy new devices. Same thing we saw at Microsoft when it released Vista and up. It's a good way for manufactures to stop companies like CM to make unwanted ROM's updates. At the beggining CM ROM's where 100% bug free, but now we can't say the same. Manufactures don't release drivers for hardware so developers to implement new versions of Android on old devices.
For me the only viable option for ROM updates is stock modifications that try to remove restrictions in the software available thru all the world.
But why is Huawei giving a legal way to unlock the bootloader? It's a very easy way to see who still got guaranty and who is out of guaranty. And also it's a way to keep clients close by getting ROM updates faster, it's basically a removal of the middle man (manufactures can't live without firms that do installment sales) a way to increase the overall sales.
Imagine a person who needs a smartphone but can't afford it. Carriers can give devices for less, manufactures get the full price, and carriers get the whole price with interest over a limited period. And now manufactures have a problem, they need to keep clients of carriers happy, and need to push updates on the devices. Carriers see this as a loss of control, but can't make the manufacturer to keep the system closed. So for legal requirements bootloaders were invented.
You can ask for root, but manufactures and Google is giving secure control over the devices, that basically do same thing as apps that required root.
My final advice: if you don't plan to learn about android ROM development, if you don't plan to be a developer, then don't root. Wait until you get a new device, maybe with the new iteration of ROM. If you see something you like, then you can start learning and start developing.
:silly: can't believe i wrote so much. Happy reading and good luck.
Click to expand...
Click to collapse
Extremely awesome and thanks a lot. I want to start to learn about root but IDK from where can I start! There are no way to root any Android emulator and learn from it or executing on main device would be more stable?
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
ItalianWolf said:
IMO, root device it's a personal choice, the important question is:
There's something that you want to do and you can't because you need root?
To install custom rom you don't need root, you have to unlock bootloader, install a custom recovery (TWRP) and finally you can flash you custom rom (generally already rooted!)
Click to expand...
Click to collapse
Ciao amico mio ? (some Italian from school ?) can you give me a tutorial for this? I need to try. Also why there are a lot of stuffs to root ALE-L21? What if I used apps such as KingRoot?
Ciao!
Kingroot, if it's working again, isn't a good root solution; i've tried (we were with lollipop) but messed up a lot of things so i had to re-flash stock firmware.
https://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Yes for :
Tweak kernel, install AdAway and remove preinstalled apps.
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
panchovix said:
personally for me is a must, i just do much things with root, anyways you could say i'm an advanced user of android so i need root, if you are good with your phone as it is, or a newer user of android, you don't need to root
Click to expand...
Click to collapse
I don't like normal things, I need to be special that's why I think to root my device. I'm neither pro nor newer. So I need to know if I rooted my device what will I do else custom ROMs and block ads and remove system apps?
Hi, i have this, i need check this information.
Here the screenshots.
Are you signed up to the Motorola Feedback Network? If so, that looks like the soak test for the G5S (as reported here as well: https://forum.xda-developers.com/moto-g5s/how-to/android-oreo-soak-test-brazil-t3803812 )
EDIT - hmm, looking at that email posted in the other link, it says the soak test is for G5 devices, yet the opening poster has a G5S from what I can see. The build matches up with your post, so unless Motorola is pushing the same build to G5 and G5S devices, I think this build is for G5S?
At least they're moving the G5S to Android 8.1 from the looks of things.
If you are on the soak test/signed up to the MFN, as per the soak test agreement, please report any bugs to Motorola, and be aware of any device breaking bugs that may occur. Have fun, but please be responsible too.
echo92 said:
Are you signed up to the Motorola Feedback Network? If so, that looks like the soak test for the G5S (as reported here as well: https://forum.xda-developers.com/moto-g5s/how-to/android-oreo-soak-test-brazil-t3803812 )
EDIT - hmm, looking at that email posted in the other link, it says the soak test is for G5 devices, yet the opening poster has a G5S from what I can see. The build matches up with your post, so unless Motorola is pushing the same build to G5 and G5S devices, I think this build is for G5S?
At least they're moving the G5S to Android 8.1 from the looks of things.
If you are on the soak test/signed up to the MFN, as per the soak test agreement, please report any bugs to Motorola, and be aware of any device breaking bugs that may occur. Have fun, but please be responsible too.
Click to expand...
Click to collapse
I faild to register in Soak Test :/
EmiAndroid said:
I faild to register in Soak Test :/
Click to expand...
Click to collapse
Unfortunate - I guess they've got plenty of soak testers for these soak updates. I imagine there may be a leak of the Oreo soak test at some point, though be careful with flashing said leak. Any bugs or issues you won't have Motorola support (as you're not on the soak test) and downgrading back to Nougat is a potentially risky procedure. It won't be the downgrade back to Nougat that is problematic, but using Nougat OTA updates on a device updated to Oreo may hard brick your device.
Seems that they're soak testing the G5S Plus as well from the screenshots: https://www.techdroider.com/2018/06/moto-g5s-plus-android-8-1-oreo-beta-screenshots.html (looks like it's OPS28.49-2?)
If it is the soak test, then all being well, the update should be rolling out in the next 1-2 months.
. Gdfhjjh
jesemalave1 said:
I got mine 2 days ago I love it
Click to expand...
Click to collapse
Nice, could you download DevCheck by flar2 https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en_GB and in the app, under the System tab, post a screenshot of the architecture please? The app is free and should work without root.
I'm a mtf tester but it's confidential as parbagreementbwishbibcouldnshare more
jesemalave1 said:
I'm a mtf tester but it's confidential as parbagreementbwishbibcouldnshare more
Click to expand...
Click to collapse
Not a problem - good to see you're respecting the NDA Hoping there aren't too many bugs to report.
It looks like the Oreo update is a 32 bit update anyhoo: https://forum.xda-developers.com/showpost.php?p=76813739&postcount=121 That's not surprising given the migration to 64 bit might require a wipe and the drivers re-written for the 64 bit architecture.
Moto g5s plus Oreo 8.1 Soak test
Watch this video for features
can someone share a photo of the 8.1 lockscreen? i wanna know if the ugly font changed..
also does it uses the G6 bootanimation or keeps the 7.1 one?
Keeps the same boot animation, no changes to fonts
Beneduzi said:
Keeps the same boot animation, no changes to fonts
Click to expand...
Click to collapse
thank you
I don't like that font but since oreo makes the clock a bit smaller maybe it looks better in comparison to 7.1
echo92 said:
Not a problem - good to see you're respecting the NDA Hoping there aren't too many bugs to report.
It looks like the Oreo update is a 32 bit update anyhoo: https://forum.xda-developers.com/showpost.php?p=76813739&postcount=121 That's not surprising given the migration to 64 bit might require a wipe and the drivers re-written for the 64 bit architecture.
Click to expand...
Click to collapse
Then there is nothing to look after, only our xda dev can use the default camera in custom rom otherwise this 32 bit Oreo is nothing less than a ****.(tati)
Extremely disappointed with moto will never buy in future
jesemalave1 said:
I'm a mtf tester but it's confidential as parbagreementbwishbibcouldnshare more
Click to expand...
Click to collapse
Breaking - there are serious bugs in the oreo 8.1 keyboard handler.
---------- Post added at 09:56 AM ---------- Previous post was at 09:50 AM ----------
Rush94 said:
Then there is nothing to look after, only our xda dev can use the default camera in custom rom otherwise this 32 bit Oreo is nothing less than a ****.(tati)
Extremely disappointed with moto will never buy in future
Click to expand...
Click to collapse
A tati?
He means fecal matter
Rush94 said:
Then there is nothing to look after, only our xda dev can use the default camera in custom rom otherwise this 32 bit Oreo is nothing less than a ****.(tati)
Extremely disappointed with moto will never buy in future
Click to expand...
Click to collapse
On a counterpoint, the camera drivers and blobs would be updated to Oreo, so may be easier for the developers to work with. If you really want a Moto device that's 64 bit, I think the X4 and the G6 Plus are 64 bit, else I wish you luck finding a 64 bit device that you like and can afford.
echo92 said:
On a counterpoint, the camera drivers and blobs would be updated to Oreo, so may be easier for the developers to work with. If you really want a Moto device that's 64 bit, I think the X4 and the G6 Plus are 64 bit, else I wish you luck finding a 64 bit device that you like and can afford.
Click to expand...
Click to collapse
Mi A1 is a 64bit device cheapest than g5s plus
ATENTION! OTA OREO IS CAPTURED
https://drive.google.com/uc?id=14nWazUMHTyk-od6SF3KJOXVTOWZoC_Do&export=download
Here is the OTA captured from Android Oreo, they must install it from the stock recovery.
Rush94 said:
Mi A1 is a 64bit device cheapest than g5s plus
Click to expand...
Click to collapse
Man, you really have some deep knowledge abt all this.
I wonder, are you also aware of Mi A1's SAR value.
Important announcement:
If you have used the Persist G4 to recover the IMEI this update will eliminate the same, they must be in android stock, without TWRP, without root, and with the Persist of the corresponding G5s Plus, otherwise, they will have errors.
Does anyone know if there is any custom ROM out yet for Oneplus 10 pro?
batterylifesucks said:
Does anyone know if there is any custom ROM out yet for Oneplus 10 pro?
Click to expand...
Click to collapse
if they don't, buy another phone.
Kosta26 said:
if they don't, buy another phone.
Click to expand...
Click to collapse
HAHHAH, ok thanks
There's potentially a few in development, but it's moving along slowly.
The clear answer is "no" and I don't see any signs of that changing any time soon (if at all). Someone started working on it, but it looks like they lack the expertise to see it through, so don't count on any custom ROMs.
However, this seems to be an issue that is more widespread, not just OnePlus phones are affected. I would actually be interested if there are any new Android phones that have custom ROMs readily available. All the official Lineage OS devices seem to be older.
Too much thing is missing guys.released kernel source has missing scripts and header files.any custom rom group don't have linaro waipo built in sources.Just relax and give time to developers.
metrixx02 said:
Too much thing is missing guys.released kernel source has missing scripts and header files.any custom rom group don't have linaro waipo built in sources.Just relax and give time to developers.
Click to expand...
Click to collapse
hows that coming along?
eviling said:
hows that coming along?
Click to expand...
Click to collapse
Issue is that developers don't have a free and secure way of recovering their devices if it bricks. The MSM tool requires authentication with OnePlus which have deemed the tool as internal use only.
We're stuck until either someone cracks it or OnePlus makes the MSM tool public.