Related
[STICKY] [FAQ] Official Atrix "Ask A Dev" & FAQ Thread (Last Update: 05/31/2011)
Official Atrix "Ask A Dev" & FAQ Thread
So, there's a ton of misinformation and confusion going around about the Atrix. I'm gonna go through this section best I can and pick out questions that I think should be in here. If you have one you'd like added or have a question to ask, post here and I'll answer and update the first post with the results. I will do my best to provide links, explain as best I can, and keep things UP TO DATE (which is the most important thing). I hope that users will see this thread and use it to their advantage. There's a lot of info out there, and I know it can be confusing, so I want to give everyone a place they can come ask questions or read information they know will be up to date. Feel free to ask anything you wish to know and I'll do my best to answer
PLEASE try to keep the thread clean. Post questions, keep discussion at a minimum (if there's a relevant discussion thread, I will link it here), and be polite.
Without further ado, let's get started with the basics.Frequently Asked Question - Updated 05/31/2011
Q: "What is"/"How do I" root?
A: If you don't know what root is, chances are you don't need it. This is the basic of the basics of Android modification. Go ahead and do a little research first if you don't know what it is. You can root almost all Atrix devices using the method in this thread, just identify what device you have an follow the appropriate tutorial: http://forum.xda-developers.com/showthread.php?t=1016060
If your device isn't supported by GladRoot, you can follow this guide by jug6ernaut: http://forum.xda-developers.com/showthread.php?t=1046626
Q: What is a ROM/P-ROM?
A: This is one of the more tricky questions when it comes to the Atrix. Designgears set the standard by calling Adeo a ROM. This is loosely based in truth. When we refer to an Atrix ROM, what we are doing is basic Android customization. It could be themes, a few added features (reboot/recovery in power menu, sideloading, adding a tethering APN for certain carriers, etc), or just an automated install for a deodexed system. They are not true ROMs, but we'll take what we can get.
As of GladiAtrix3 beta, I changed the name of these mods to Pseudo-ROM, or P-ROM for short (yes, pronounced 'prom').
Q: What is an SBF? How do I flash it?
A: An SBF file is the Motorola base firmware. There are only a few SBF files available, and instructions (Thanks to seven2099) to use them can be found here: http://forum.xda-developers.com/showpost.php?p=13604217&postcount=2. The guide was written with the Bell Atrix in mind, but this process will work with any version provided you have the correct SBF for your device. This guide by kennethpenn contains links to a few of the SBFs for AT&T devices: http://forum.xda-developers.com/showthread.php?t=991072
It should also be noted that these files are NOT community provided. They are leaked from Motorola, are are technically for internal Motorola use only. Do NOT ask where we get them, how we get them, or if we can make you a custom one. We cannot.
Q: What does "deodex" mean?
A: This guide has a pretty good explanation of what the difference between odexed and deodexed is: http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
Q: What is sideloading?
A: Sideloading lets you install any applications, regardless of carrier or market restrictions. This is also sometimes called "Unknown sources." It can be enabled several different ways. Both the GladiAtrix (for 4.1.26, 4.1.52,, 4.1.57, and 4.1.83) and GingerBlur ROMs contain it. You can also enable it using the GladiAtrix Enabler.
Q: <app> in the market doesn't work! Help!
A: There are several applications still that have not been updated to support the Atrix. It uses a lot of new hardware, and does things a little differently. Before jumping on and making a thread saying Motorola sucks for your app not working, contact the developer first and ask them to update.
User Submitted Questions - Updated 04/27/2011
Q: Is there a way to install an apk without finding it and tapping on it? Maybe through terminal emulator and if so what would the command lines be? (submitted by drock212)
A: Yes! You can install applications through ADB on your PC with the command 'adb install <app>.apk' where <app> is the filename of the app you want to install. You can also use a file manager, or as [email protected] mentioned, the Android Market website. Finally, there is a command line that you can use to install: pm install <app>.apk
Q: I have a Bell Atrix (unlocked to work with Rogers). Are there any precautions I need to keep in mind when flashing ROMs, installing the new 1.5.7 update and rooting it all using the At&t files in the Dev forum? (submitted by TareX)
A: Absolutely. As far as I know, you cannot flash any of the AT&T firmwares on a Bell Atrix. This will cause a brick and you will be unable to recover since there isn't a Bell firmware SBF available right now. If anyone has been brave enough to try and flash a Bell Atrix with AT&T firmware and has SUCCEEDED, please let me know.
Q: The atrix has 1GB of ram. Is all of that memory used on the phone or is it like what was rumored and some of it is reserved for the webtop? (submitted by RacecarBMW)
A: The webtop shares memory with the phone side. There is about 800mb free for use by both, with roughly 200mb reserved for system processes.
Q: Are more ROMs in the works? (submitted by danboard)
A: I've been working hard at getting GladiAtrix 2 to a point where I feel comfortable releasing it in CWM format. Unfortunately, I can't speak for other developers. The tools available for the Atrix are relatively limited, and we don't have a very strong base of talented people like other Motorola phones do. I'm pretty proud of what we've managed to accomplish even with such a small userbase.
Q: Can I use my phone on a carrier other than AT&T or Bell? (submitted via PM by [email protected])
A: You can, but you need to make sure that the carrier you want to use the phone on supports the same frequencies as AT&T/Bell. There are a few different ways you can get the phone unlocked. The easiest, and honestly best, way to do it is to call the carrier and ask them for an unlock code. If you're persistent and polite enough, make your case as to why you need the phone unlocked, there's a good chance they'll accommodate. Getting mad and upset rarely works. You can also get an unlock code through several different online sites. This thread talks about sites with unlock codes, and gives you a good idea which to trust. General consensus seems to be that cellunlock.net worked for most users and has a 20$ rebate coupon code: android50
Q: Can I use the Webtop without a dock? (submitted via PM by [email protected])
A: You sure can. It requires modifications to the system files, so if you don't fee comfortable making permanent changes to your phone's OS, you shouldn't be doing this. This thread has a very detailed explanation on how to get it working on your phone, but make sure you match up the proper firmware version or can potentially brick your phone.[/B]
Q: Is there a way to install a full version of linux on the Webtop? (submitted via PM by [email protected])
A: There is a project running to unlock the Webtop OS and allow you full access to install anything you wish. You can read about the progress here: http://forum.xda-developers.com/showthread.php?t=1000316
Q: I don't use the webtop. Is there any way to remove it completely to regain the space on the phone? (submitted by Girgizzlemuf)
A: Unfortunately, you cannot. The Webtop is directly integrated into the Android OS, so removing it would render your phone inoperable. I'm unsure if an unlocked bootloader will allow it to be removed either, as the entire build of Android running on the Atrix was built around the Webtop.
Q: Do I need to unlock before rooting, or are the two completely independent from eachother? (submitted by dropshipinc)
A: Unlocking and rooting are not tied together. You can root without unlock, and you an unlock without root. Unlocking is, in most cases, referring to the ability to use the phone on any carrier. This is called SIM unlocking. Rooting gives you root access to your device. On the Atrix, you cannot unlock your phone by having root. Some devices this is the case, but the Atrix is not one of them.
Q: Will installing a rom prevent OTA updates? If so, can they be easily removed so that we can install OTA updates? (submitted by ratkid2271)
A: Installing any of the currently available ROMs will prevent the phone from applying an OTA update. You should still be able to download them, but the installation will fail. As for uninstalling, you should be making a nandroid backup of your phone with CWM before installing any of them. A simple restore of that backup will prep you for an OTA update.
Special Thanks
Thanks to: drock212, TareX, RacecarBMW, danboard, [email protected], Girgizzlemuf, ratkid2271, and dropshipinc for their submissions.
Is there a way to install an apk without finding it and tapping on it? Maybe through terminal emulator and if so what would the command lines be?
Sent from my MB860 using XDA Premium App
It is possible through site of Android Market. Just log-in and you can search and install any app on your phone
That's the problem market doesn't work. I have the apk on an sd card but phone I need to install apk on does not have a file explorer.
Sent from my MB860 using XDA Premium App
So propably you need to enable sideloading and apply root then instal this .pak or just use the adb tool (search for "instal apk adb")
drock212,
The Atrix has a default file manager in the app menu called "Files". Once opened, just navigate to "SD card" and click the .apk.
-Opish
Yeah lol the issue isn't with my Atrix its for another phone that im trying to port stuff from my Atrix to it but the other phone is all messed up and the market wont connect and it has no file explorer lol
Sent from my MB860 using XDA Premium App
I have a Bell Atrix (unlocked to work with Rogers). Are there any precautions I need to keep in mind when flashing ROMs, installing the new 1.5.7 update and rooting it all using the At&t files in the Dev forum?
I bought it off ebay so if I brick it, it's over.
The atrix has 1GB of ram. Is all of that memory used on the phone or is it like what was rumored and some of it is reserved for the webtop?
drock212 said:
That's the problem market doesn't work. I have the apk on an sd card but phone I need to install apk on does not have a file explorer.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
there is a file explorer on the phone, it's called "Files"
Please take the discussion to a new thread. I understand you're trying to help, but send a PM. This is Q&A only. Thanks. Updating first post with answers to the questions shortly.
Are more ROMs in the work? Correct me if I m wrong (as I don't know all that much about what the bootloader limits) but since we now have a CWM of sorts, we're able to pretty much change most parts of the android OS excluding the kernel and radio.
In this post:
http://forum.xda-developers.com/showpost.php?p=12710040&postcount=6
Kenneth stated that the Milestone had more tools and devs than the atrix to get custom roms like miui to work; the dev part I can understand but which tools exactly was he referring to? A few of the things I could think of were the script mods that were available in the open recovery for the milestone but I believe the Atrix already have these features (just not in the CWM).
So I m just wondering is the Atrix at a point where devs are able to mod it as much as the milestone? or is there still quite a ways to go?
Updated first post! Check it for your answers.
So I understand the awesomeness that is the webtop. However, I have no use for it other than to say 'HAY i got a netbook in my phone wanna see??'
Having said that... is there a way to *remove* the webtop entirely, or is this something we are going to have to wait for in the form of a custom rom / unlocked bootloader?
Girgizzlemuf said:
So I understand the awesomeness that is the webtop. However, I have no use for it other than to say 'HAY i got a netbook in my phone wanna see??'
Having said that... is there a way to *remove* the webtop entirely, or is this something we are going to have to wait for in the form of a custom rom / unlocked bootloader?
Click to expand...
Click to collapse
Unfortunately, you cannot. The Webtop is directly integrated into the Android OS, so removing it would render your phone inoperable. I'm unsure if an unlocked bootloader will allow it to be removed either, as the entire build of Android running on the Atrix was built around the Webtop.
I've accidentally partitioned my internal SD storage rendering my phone useless. Had to flash and tried all three AT&T SBF files to no avail. Bottom inch of my touch screen is horrendously off.
Anyway to get this back to the OEM settings? Flashing is no help and I'm getting daemon errors in ADB when I try manually formatting and partitioning it. Any way I could commission you to write a script? Talking to a couple others with this problem too. You'd be a hero!
Nice OP Ririal Thanks for being oh so helpful and contributing to the Atrix! Keep up the good work! I wish I can play with your ROMs Hoping that the Bell's SBF will be leaked one of these days (yes I know...wistful thinking...)
bongd said:
I've accidentally partitioned my internal SD storage rendering my phone useless. Had to flash and tried all three AT&T SBF files to no avail. Bottom inch of my touch screen is horrendously off.
Anyway to get this back to the OEM settings? Flashing is no help and I'm getting daemon errors in ADB when I try manually formatting and partitioning it. Any way I could commission you to write a script? Talking to a couple others with this problem too. You'd be a hero!
Click to expand...
Click to collapse
Unfortunately, I'm not sure what you all changed, but this is something that should not have been messed with. Especially with a locked bootloader, you should NOT be repartitioning your device. I would assume that flashing the SBF would fix this, but again, as I'm not sure what you all did I don't really know for sure.
Ririal said:
Unfortunately, I'm not sure what you all changed, but this is something that should not have been messed with. Especially with a locked bootloader, you should NOT be repartitioning your device. I would assume that flashing the SBF would fix this, but again, as I'm not sure what you all did I don't really know for sure.
Click to expand...
Click to collapse
Thanks. I know it was erroneous but it was late at night and my contacts were all gunky. I clicked on the wrong thing and the way I was holding my device I had already gotten too far into the menu by clicking too fast
Internal SD was partitioned. Flashing didn't help. Was hoping you may know but that's okay... I'll keep trying.
bongd said:
Thanks. I know it was erroneous but it was late at night and my contacts were all gunky. I clicked on the wrong thing and the way I was holding my device I had already gotten too far into the menu by clicking too fast
Internal SD was partitioned. Flashing didn't help. Was hoping you may know but that's okay... I'll keep trying.
Click to expand...
Click to collapse
Yeah, I wish I could be of more help If you do find out a way to fix it, be sure to let me know or post here, I'll add it up to the FAQ just in case anyone else makes the same mistake. Hope you get it sorted out!
MOD EDIT @gregbradley WARNING. King root sends your IMEI number to an IP address in China. Only use this method if you are OK with this. You have been warned
Pls remove this thread.
I removed Kingroot and flash supersu instead because that is the most important trick in this tutorial but ppl seems to believe what they choose to believe…
Reserved
Enough said.
Remove remove
There are reports that king root sends IMEI /your personal information to some chinese servers..
It is not safe i think...Please check xda before trying this . Now that you have tried use the app for few days and monitor it ..and please report back if there is any suspicious activity by the app.
Video ?!!!
Video Guidance incomplete
Were you asked to remove your much easier way to root, or did you take it down just out of spite?
Am I to expect nothing more from you in the way of efforts to help people like me root, who simply don't understand WTF anybody else here is even talking about?
I simply need to know, that's all. I'm frustrated because obtaining root seems so close and yet completely out of reach.
AddictedToGlass said:
Were you asked to remove your much easier way to root, or did you take it down just out of spite?
Am I to expect nothing more from you in the way of efforts to help people like me root, who simply don't understand WTF anybody else here is even talking about?
I simply need to know, that's all. I'm frustrated because obtaining root seems so close and yet completely out of reach.
Click to expand...
Click to collapse
He was not asked to remove it. XDA allows the mention of this root method as long as the warning about information being sent to an IP address in china is mentioned as well.
XDA Rule 17
17. Apps that collect identifying details
We don't routinely remove Apps that collect identifying numbers or other personal and device identifiers.
However, should an App, developed by you, be identified as one that maliciously performs this activity (e.g. by not disclosing it to the user), it will be removed from the site and possible sanctions applied;
Click to expand...
Click to collapse
Just google king root and use it. The info here was just about which buttons to press.
1) use king root
2) install recovery
3) Flash SuperSU.zip and remove kingroot.
Done
WARNING. King root sends your IMEI number to an IP address in China. Only use this method if you are OK with this. You have been warned
Thread closed at OP request
Hi all, when I bought the Lenovo A916 phone from www.lightinthebox.com it came with spyware included in the Stock Rom(which had been modified by 3rd party), impossible to get rid of unless you root the phone, because its located in system files.
Beware, if you do a factory reset the spyware will be back! Also, do NOT use your phone for banking or anything else with passwords, before you have removed the spyware since it contains a keylogger!
You can flash it with new Rom(also known as Firmware) or a clean Stock(original) Rom - that will remove the spyware. You have to be rooted for this to work.
Right now my phone has A916_S1205_141013 rom - below there is a link to this Rom - its multilingual - I have not yet had the time to try it myself and don't know if its clean.
http://firmwarefile.com/lenovo-a916
I have removed all the spyware, after I rooted my phone, and its working as it should - But as I said earlier, the spyware will return if I do factory reset.
If you bought this phone on the net like most of us, then I suggest that you install the following and scan for spyware. Take note, that the spyware is not from Lenovo!
Avast, Avira, ESET, 360 security, Malwarebytes - use all of them, since there are always something one don't find but the other one will.
Be aware that something can go wrong, and I'm not responsible for you trying this out.
The best way to root is Kingo root. But first, attach your phone to your PC/laptop(make its connected to the internet) and on the phone choose MTP, now the phone will install drivere for its first use - this is important!
Then you click the icon in the notification area in windows, to dissconnect usb devices and dissconnect your phone. Wait a few min, - then re-connect and this time (on he phone) choose the last option which say something like "Virtual CD". If autorun is enabled on your pc, you will then get an option to browse this virtual CD - do so!
Copy the content of the virtual CD to a new folder on your pc, then run and install LenovoUsbDriver_autorun_1.0.12.exe - this is important. Don't bother with the other things there since its in chinese.
Then get Kingo root from here:
http://www.kingoapp.com/android-root.htm
Click to download it from CNET, be aware that it might get caught by your antivirus - not that it contains virus, but because its used to root phones. If it got to you pc safely, then run it and it will download the real rooting software - make sure to say NO/Decline/uncheck to any offer that comes up(like install Yahoo). Stupid and annoying way CNET try to impose their stuff onto people.
Now, the real software has been downloaded(android_root.exe) - run it and follow the guide. There are also a guide on Kingo root's webpage.
After you have rooted your phone, run the antivirus Apps again, this time you will be able to remove some but not all of the spyware. Make a list of those you can't remove - then go to the superuser app you can remove the software that contains spyware and cannot be cleaned otherwise. Be careful what you remove.
I found spyware in these and removed with the supeuser app
Trojan.Agent.mq in /system/app/CallerID.apk
PUP.Adware.ShinyMob.a in /mnt/sdcard/funweather.apk
Backdoor.Ginmaster in /system/app/Weatherservice_K517_u002_20140910.apk
Trojan.Fadeb.a in /system/app/Twitter_qd_3025.apk
Do NOT remove the ThemeCenter app!! Its used its used by the system to set wallpaper. If it has spyware then you can remove it and replace it with the one in this post:
http://forum.xda-developers.com/showpost.php?p=63651753&postcount=42
Good luck!
JBJ
Moderator, please don't remove any of this - Its super important!
If someone has suggestion or tips to this thread then please PM me an I can insert it with credit in the 1st post!
I don't have any direct experience with this device, being in the USA, but this seems like it might work http://www.needrom.com/download/lenovo-a916-multilang-root-gapps/ .
I don't have any direct experience with this device, being in the USA, but this seems like it might work http://www.needrom.com/download/leno...ng-root-gapps/ .
Click to expand...
Click to collapse
Hi and thank you for the answer, I have looked at these already, but the authors seem not to want to answer questions on if this is clean.
EDIT: this is obsolete now - please read at 1st post!
EDIT: this is obsolete now - please read at 1st post!
Moderator: Is there a way to delete ones own post?
insomniacno1 said:
EDIT: this is obsolete now - please read at 1st post!
Moderator: Is there a way to delete ones own post?
Click to expand...
Click to collapse
Hello I have a Lenovo A916 and im planing on rooting it and installing a vanilla version of android on it to get rid of the bloatware it contains
I was thinking of using the rom you just shared but after seeing your comment about "this is obsolete now" I have now to ask you what do you mean by obsolete? the rom link didnt turn out to be safe or something?
LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?
dvdram said:
LOS 17.1 is now available and developers say that LOS's own recovery is going to be the preferred recovery.
Last year Google announced that adb is very likely to be removed soon.
Those two statements brings up an important question: how can users create a full backup of their devices **without** having to root them in order to make backup apps work?
I am not talking about backing up pictures, media, calendars or address books, there are plenty of ways to do this without root access. I am talking about a full backup, including the whole system partition and user data. TWRP was an excellent tool for this job: a backup could be created any time, any where, completely independent whether a PC was near or not. You could even write the backup directly onto a USB storage, and the phone could always be restored as well any where and any time.
That is a feature that I miss very much in LOS's own recovery and to my opinion this is an issue that needs to be solved.
Will this feature be added to LOS recovery in the (near) future? Or are there any other solutions to do a full backup without the need for root access?
Click to expand...
Click to collapse
Making a complete system backup requires root and/or custom recovery, period.
That is he way it is, you can't change that. There are no alternatives.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Making a complete system backup requires root and/or custom recovery, period.
Click to expand...
Click to collapse
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.
dvdram said:
Pardon me, but that is a very harsh answer to a seriously asked question of common interest.
"We take security very seriously"...
Do you know where these words are written?
Maybe you'd like to try looking at this issue this way:
Many users who install LOS, are doing this because of security reasons. Imagine some of these users having bad luck and their phones get compromised by some bogus apps. And then they read an answer like this, telling them nothing different than: sorry, we can't and we won't help you!
And know imagine this:
Users can create snapshots or images of their running systems, with all of their apps included, as well as all necessary accounts, logins and passwords. When the "impossible thing" happens to a device running LOS, they have the option to restore the complete system without having to do a factory reset and without having to reinstall each and every app and the corresponding accounts.
What do you think, which one would please the users of your product more: an answer with an attitude like that one above, or the second possibility?
Furthermore: I was not bagging you to include this possibility. I was asking how this kind of back up could be made in the future, when TWRP won't work with Android 10, and when Google will remove adb. And frankly, I don't see why a recovery made by LOS should not be able to do a task that a third party recovery is capable of. If TWRP developers can put together such a piece of code, I am sure LOS developers should be able to do so as well.
Another possibility would be to reverse Google's decision and to keep adb.
So, from my perspective, there are at least two possible ways of dealing with this. But I am a user, not a developer, and I don't know if or why any one of these possibilities is a bad idea, or if there are really serious arguments against it, or whatever pro or con there might be. I simply don't know about these things and that's why I was asking about it. I am a user who doesn't like having to do a complete re-installation after a crash. And I am pretty sure that I am not the only user with this kind of antipathy.
A polite answer to the question would have included at least a glimpse of explanation why this and why not that.. And an open minded developer would have even cared to discuss about this.
Click to expand...
Click to collapse
Your reaction is a very butt-hurt reaction for a question that has been asked AND has been answered many times on this website and could have easily been found by you if you had searched.
Unless, of course, you did search and you did read where it has been answered before and, for whatever reason, you mistakenly thought that you would get a different answer just because you needed it to.
My point was, there is no way to access system partition or data partition without root. This forum is full of posts from other users asking the same thing, they all got the same answer, it can't be done without root or TWRP. Android just does not work that way, it has a linux kernel, which means, everything requires specific permissions and it is not in the best interests of OEM/carriers to allow access to /system and /data that easily and there is no way to give you "limited" access that only allows you to backup the /system and /data. There is only full permissions or none and they will not allow full permissions to the user.
That is entirely the whole point of people like us that find ways of rooting devices and installing custom recovery in the first place, because it is the ONLY way we can access /system and /data to make backups or modifications.
As for your thoughts of whether there will be a "new" way of making backups if adb and TWRP are no longer viable options....
Who knows? None of us will know until that time comes. We will all just have to wait and see if any takes the time to develop a new method.
Sent from my SM-S767VL using Tapatalk
dvdram said:
...
Last year Google announced that adb is very likely to be removed soon.
...
Click to expand...
Click to collapse
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.
jwoegerbauer said:
Android Debug Bridge (ADB) is a Server - Client pair software
ADB Server runs in the Android device
ADB Client runs in Windows / Linux / Mac iOS
ADB completely is open source. Hence everyone can grab the source code and compile it matching the target Android OS / computer OS. Manufacturers like Samsung & ZTE actually already provide their build of ADB Client suitable to their Android devices: they don't recommend to make use of universal ADB Client that floats around the WEB.
AFAIK Google announced to remove backup / restore feature from ADB Client, not ADB at whole.
Click to expand...
Click to collapse
Yeah, I can't see Google completely removing adb, it is too valuable of a tool for development even for the stuff the carriers and their developers do on their end. Removing it would be like building cars and engines but completely disallowing the production or use of tools to assemble/disassemble the cars or engines.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
My point was, there is no way to access system partition or data partition without root.
Click to expand...
Click to collapse
I know that and I understand that. I've been using Linux on my private and on my working machines for at least 30 years now, and I know about permissions. And I also understand that there are good reasons for not rooting an Android device.
But that is not the point here.
I am and I always was talking about the recovery here, not the running LOS system, that you run every day to make any use of your phone at all. From my point of view, as a Linux user, booting into recovery is like taking a secondary boot device, eg a USB memory, and starting another Linux system that is completely independent of the one that my PC is running in normal cases. Using this secondary Linux I can do anything to the system and the hard drive that I want, regardless of permissions. I can re-install the boot manager, I can copy or delete files, I can repair the file system, and, most important: I can create images and snapshots of the system that will serve as an lifeline, a certain point in time that I can return to if it should become necessary.
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
Again: I am not talking (and I never was) about making root available in LOS.
@dvdram
...
My question was and still is, why a custom recovery like TWRP can include this function, but the recovery made by LOS can or will not do so, or if there is a chance that the LOS recovery will include this function in the future.
....
Click to expand...
Click to collapse
Wondering why you don't ask this question to the developers of LineageOS?
jwoegerbauer said:
@dvdram
Wondering why you don't ask this question to the developers of LineageOS?
Click to expand...
Click to collapse
Silly me! I actually believed there would be developers reading this forum. How could I mistaken this statement on the starting page:
"XDA Developers was founded by developers, for developers."
I guess the word "developers" must have another meaning than I have always believed. Thank you for showing me my wrong!
I have never used a Pixel phone, but I am strongly considering a Pixel 6 now. I want to root the phone using Magisk **and** I want to successfully hide root. Furthermore, I want to be able to install some modules in an Xposed-like framework such as LSPosed, and I want the existence of that XPosed-like framework also to be hidden. Ever since Android 11, it's been complicated and confusing to figure out how to accomplish all of this in a reliable manner, given the latest changing versions of Magisk and given the various root-hiding mechanisms that are now offered, and which are also now still in development.
There is a huge amount of information about this general topic in the following threads ...
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/page-2689#post-87696219
https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
https://forum.xda-developers.com/t/...r-unofficial-third-party-magisk-fork.4460555/
https://forum.xda-developers.com/t/lsposed-xposed-framework-8-1-13-0-simple-magisk-module.4228973/
... however, there are collectively more than 50,000 messages in this group of threads, and for me, this fits into the category of "Too Much Information", especialy given that much of this info is contradictory, with different people reporting success and others reporting failure, and different people reporting slightly different versions of the same procedures.
The reason I'm posting here is that I'm wondering of anyone has successfully accomplished what I'm trying to do with a Pixel 6 under Android 11 or Android 12, and if so, whether that person (or people) might be willing to share a straightforward, step-by-step, cookbook-like set of instructions about how to accomplish all of this from beginning to end.
By "beginning to end", I mean to start with a brand new locked Pixel 6 and to install all of the software and features that I described above, with the end result being a reliably rooted Pixel 6 (with root reliably hidden) running some sort of XPosed-like framework under Android 11 or Android 12, and which can be consistently rebooted with no boot loops.
If that is considered off-topic here, I'm glad to take this into private chat.
Thank you very much in advance for any help that you might be able to offer.
What he said, but instead of android 11 or 12, give me one for 13 please.
Oh! I somehow overlooked the following thread when I first came here:
https://forum.xda-developers.com/t/...nlock-bootloader-pass-safetynet-more.4388733/
It covers a lot of the information I'm looking for.
I will soon dig into that thread in more detail, and if it indeed ends up explaining everything that I want to learn, then I will abandon this current thread.
But for the moment, I'll keep this thread alive.
I can confirm my rooted Pixel 6 running 13 passes SafetyNet check and is certified in the Play app following those instructions. However, Google is not using SafetyNet to check for an unlocked bootloader in their apps anymore. GPay complains about device security and there are some apps that I can't download. Netflix, Hulu. Other than GApp and having to sideload Netflix, I don't have any issues.
Here's a thread about the new security check.
https://forum.xda-developers.com/t/discussion-play-integrity-api.4479337/
anyone having issues with some apps detecting root even after magiskhide should try the shamiko module. helped me
few stupid questions regarding rooting my pixel 6 .....
1) its new unlocked phone, should i have the new SIM in phone when rooting, does it matter ?
ok to put it when its done ?
same question for being signed into Google account when rooting, does it even matter, either way ?
2) is there a way to get the pixel phone transfer to show back up, or a way to access it ?
Its very easy for me to transfer all backed up data from my current Pixel 3 that way...
3) can I still run my banking & crypto apps once rooted ? I have read conflicting reports on this... elsewhere that is.
Thank y'all for the awesome information ya provide on here, and Thank You in advance if you have any input for me rooting...
Its amazing how far along we've come along since my bag phone
kengel1969 said:
few stupid questions regarding rooting my pixel 6 .....
1) its new unlocked phone, should i have the new SIM in phone when rooting, does it matter ?
ok to put it when its done ?
same question for being signed into Google account when rooting, does it even matter, either way ?
2) is there a way to get the pixel phone transfer to show back up, or a way to access it ?
Its very easy for me to transfer all backed up data from my current Pixel 3 that way...
3) can I still run my banking & crypto apps once rooted ? I have read conflicting reports on this... elsewhere that is.
Thank y'all for the awesome information ya provide on here, and Thank You in advance if you have any input for me rooting...
Its amazing how far along we've come along since my bag phone
Click to expand...
Click to collapse
1. No, yes, no
2. Yes, kind of
3. Yes with safetynet module and magisk deny list, and sometimes magisk props.
Read @Volatyle's and @Homeboy76's guides. Great info in both.
It would be better if you explained what your end result is. Hiding root can be very difficult; depending on the app requirements, simply having an unlocked bootloader can be enough, because an unlocked device will always fail hardware backed attestation.
If you're simply trying to get apps like Google Pay to work, you should need to do nothing more than install Displax's modded USNF module, and enforce DenyList on the Play Store and Play Protect service.
If on the other hand you're trying to use apps that specifically detect the presence of Magisk, then you may need to hide the Magisk app. As far as hiding the presence of root itself, I am unsure as to whether any app without root privileges can detect whether an SU binary is installed. Someone like @pndwal would know better than I would.