No longer a needed tread and has been locked.
This thread is for discussing early development for the Omate TrueSmart. The current and most pressing is if Omate does not receive Google's OK for Gapps and play store. How to get this installed on a device using something your grandmother could figure out. Lets assume that Omate will commit installing CWM on all devices. So the set up would then be
Unrooted
CWM recovery
What's needed know- Can your script a device to reboot into CWM and flash a file then reboot normally without root?
How it implement- Have an app dl a "fixme.zip" and run the flash script with minimal interaction from the user.
(I know this is a mess but it's 5am and I have slept yet)
Recovery first
First question to answer:
TWRP or CWM as custom recovery?
We want Omate to ship the device unrooted, but with a custom recovery. The recovery can then be used to easily do the following tasks:
Install official updates from Omate (OTA)
Install unofficial updates from the community
Root the device
Install Google apps (in case there is no official support when the devices are shipping)
The recovery should allow instaling updates AUTOMATICALLY, that means SCRIPTED.
TWRP support OpenRecoveryScripting. Does CWM support scripting?
How much work is it to compile TWRP and CWM? Anybody experience with that?
---------- Post added at 02:23 PM ---------- Previous post was at 02:14 PM ----------
Here's a link about OpenRecoveryScripting:
http://www.teamw.in/OpenRecoveryScript
---------- Post added at 02:30 PM ---------- Previous post was at 02:23 PM ----------
Just one more idea:
What about a pre-installed app for installing "official" and "unofficial" apps?
The app could, e.g. look at a list of servers and retrieve potential updates. Similar to the updater of CM.
In the settings, we could specify what servers to use, so the watch as shipped would only look on Omate server. But you could tick an option like "Community updates" and the app would also check goo.im (or similar). That way, we could provide an "unofficial" update to install Google Apps.
If the user decides to install the update, the update should work completely automatically, if possible. So, just one click, then download, reboot to recovery, install and reboot again.
Anybody experience with the CM updater? Source code is open source, I guess?
Seeing that cwm is already built going with twrp should be a last resort. We would most likely need access to Omate's files to compile twpr and have anything we could even submit to them for testing.
From this link http://www.teamw.in/OpenRecoveryScript I got the impression that CWM also supports at least a subpart of OpenRecoveryScripting.
Did anyone see this? http://www.xda-developers.com/android/effortlessly-download-gapps-packages-with-easygapps/ ??
Can it be given to Omate to INCLUDE in the standard pre-installed apps?
WIll it work?
chrisvor said:
Did anyone see this? http://www.xda-developers.com/android/effortlessly-download-gapps-packages-with-easygapps/ ??
Can it be given to Omate to INCLUDE in the standard pre-installed apps?
WIll it work?
Click to expand...
Click to collapse
Very nice one. But Omate probably cannot include that into the pre-installed apps.
But the Updater app we are talking about could work very, very similar. Maybe we can get the dev involved in this project?
Lokifish Marz said:
We would most likely need access to Omate's files to compile twpr and have anything we could even submit to them for testing.
Click to expand...
Click to collapse
The porting "kit" would most probably come from mediaTek and be covered by an NDA. That is assuming Omate did the port themselves and didn't just receive the whole kernel ported and compiled from MediaTek. In both cases, given that MediaTek doesn't publish much info on their site its most probably covered by a NDA.
Neuer_User said:
Very nice one. But Omate probably cannot include that into the pre-installed apps.
But the Updater app we are talking about could work very, very similar. Maybe we can get the dev involved in this project?
Click to expand...
Click to collapse
I'm going to look into itanyways. Think, dl this apk, put on device and open it up in the file browser. This would trigger package manager and install it. Simply mention it and giving a link to the thread / apk would go a long ways. Hopefully root is not needed or regular folks will be boned.
Omate still needs to remove the play store included statement until they get an official answer from google or it will continue to cause problems.
iraqigeek said:
The porting "kit" would most probably come from mediaTek and be covered by an NDA. That is assuming Omate did the port themselves and didn't just receive the whole kernel ported and compiled from MediaTek. In both cases, given that MediaTek doesn't publish much info on their site its most probably covered by a NDA.
Click to expand...
Click to collapse
"
Solution. Pick some firmware devs and make them "subcontractors". I'm already under an NDA with Omate as it stands. It would just need to be amended.
Lokifish Marz said:
Solution. Pick some firmware devs and make them "subcontractors". I'm already under an NDA with Omate as it stands. It would just need to be amended.
Click to expand...
Click to collapse
If the work was commissioned by Omate. If not, wouldn't that also count as a breach of NDA?
My understanding is that the dev edition already comes with CWM, I recall reading a comment by Omate that they were already using it internally. If so, its simply a matter of extending CWM installation to all production units instead of dev only.
Updater code
Here is the code of the old CM updater app:
http://code.google.com/p/cyanogen-updater/
Lots of code, but maybe, if the original dev would be interested in the Omate, too, he might go and adapt his code?
iraqigeek said:
If the work was commissioned by Omate. If not, wouldn't that also count as a breach of NDA?
My understanding is that the dev edition already comes with CWM, I recall reading a comment by Omate that they were already using it internally. If so, its simply a matter of extending CWM installation to all production units instead of dev only.
Click to expand...
Click to collapse
There's a couple different ways it can be approached. I don't know what Omate's agreement is with MediaTek or Umeox regarding the firmware.
Even if CWM came preinstalled on all versions, flashing a gapps.zip is still not noob friendly. That's what I want to resolve. Something as simple as "visit this page and install this app" at the least and a preinstalled "one click" solution at best.
The other side of getting hands on the firmware ahead of time. Think of all those edits and tweaks being factory vs having to flash a custom rom. Oppo does this and has gained a a ton of attention as a result.
Even if CWM came preinstalled on all versions, flashing a gapps.zip is still not noob friendly. That's what I want to resolve. Something as simple as "visit this page and install this app" at the least and a preinstalled "one click" solution at best.
Click to expand...
Click to collapse
That's why I thought about the CM updater app.
The point is: In order to get CWM to do a scripted install the scripts need to be saved to /cache/recovery/openrecoveryscript
I'm pretty sure you can do that only with root rights. So, it would be best, if the updater would be bundled with the firmware. If you need to side-load the app, you would need to assign root rights etc. Not that easy for the average user.
A pre-bundeled Updater app could be the easiest way. Omate claims to have OTA updates. So the mechanism is already there. We only need to have a UI for the user to choose to install an "unofficial" Gapps update from a community server (goo.im) instead of only the official updates from Omate.
We really need an Omate guy here you understands this and the way they currently plan OTA updates!!
Neuer_User said:
That's why I thought about the CM updater app.
The point is: In order to get CWM to do a scripted install the scripts need to be saved to /cache/recovery/openrecoveryscript
I'm pretty sure you can do that only with root rights. So, it would be best, if the updater would be bundled with the firmware. If you need to side-load the app, you would need to assign root rights etc. Not that easy for the average user.
A pre-bundeled Updater app could be the easiest way. Omate claims to have OTA updates. So the mechanism is already there. We only need to have a UI for the user to choose to install an "unofficial" Gapps update from a community server (goo.im) instead of only the official updates from Omate.
We really need an Omate guy here you understands this and the way they currently plan OTA updates!!
Click to expand...
Click to collapse
Unless something has dramatically changed in the past week or so, you do not need root to side load most apps. I side load diagnostics apps all the time on tons of phones. If the gapps installer that was linked a couple of posts back does not need root to run then the "visit this page and install this app" is resolved.
Lokifish Marz said:
Unless something has dramatically changed in the past week or so, you do not need root to side load most apps. I side load diagnostics apps all the time on tons of phones. If the gapps installer that was linked a couple of posts back does not need root to run then the "visit this page and install this app" is resolved.
Click to expand...
Click to collapse
You misunderstood me.
Sure, you don't need root to side-load apps.
But I believe you need root to script CWM. The script must be put into /cache/recovery/openrecoveryscript and that is, I think, only accessible as root.
If you want to install Gapps, then this needs to fgo through CWM. If it goes through CWM, you don't want the user to manually go though CWM, but to do the installation automatically. And therefore you need a script telling CWM what to do ("install /sdcard/updates/Gapps.zip", "reboot"). And to save this script you need root. Also, to automatically reboot into recovery, you would need to have root.
So the app downloading the update would need to have root. And that is best, if it is already pre-installed.
I'm goign to try some thing and get back to you. It may take me a little bit as I don't have a singled unrooted device in my house.
Well, anyway. I want a definite commitment from omate to support any development we do. Otherwise, I won't invest time into this.
Let's hope some omate firmware guy will join this discussion here soon.
Neuer_User said:
Well, anyway. I want a definite commitment from omate to support any development we do. Otherwise, I won't invest time into this.
Let's hope some omate firmware guy will join this discussion here soon.
Click to expand...
Click to collapse
At least publicly, they're pretending that business is as usual and nothing happened. Instead of posting an update explaining what is what, they posted about the Clockface contest.
Speaking of Clockfaces, shouldn't those too be something devs can make through their SDK? Seems those too will be restricted to a few predefined ones :\
iraqigeek said:
At least publicly, they're pretending that business is as usual and nothing happened. Instead of posting an update explaining what is what, they posted about the Clockface contest.
Speaking of Clockfaces, shouldn't those too be something devs can make through their SDK? Seems those too will be restricted to a few predefined ones :\
Click to expand...
Click to collapse
Their failure to edit the kickstart page is a really bad idea. I will not go into details on this.
They should but we don't even know what the app is even capable of at this point. I posted my concept InfoCenter Clock just in case the clockface app has those functions. If it doesn't, it won't stay on my Omate for long.
Lokifish Marz said:
Their failure to edit the kickstart page is a really bad idea. I will not go into details on this.
Click to expand...
Click to collapse
That's what is also worrying me. The Kickstarter FAQ doesn't say anything about removing promised features, let alone doing so a few days before the campaign ends. I'm worried Omate will try to resolve this with Google until the last moment, then abruptly change the project to remove the play feature and jeopardize the whole campaign.
Ok. here's where I'm at with this. There was a workaround app "Google Installer" but it no longer works. What it did was install Play Store and services as regular apps from a remote server. I found an updated replacement that is in Chinese ONLY but it requires root and it's permissions are suspect. Also, forget any scripting while booted normally without root. It's a no go.
I need to take a break from this as I've been digging through poorly translated Chinese and Russian forums and the regular sources for hours trying to see if I missed something. My head and eyes are killing me.
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!
Is there any site or source on the web that provides downloads of old versions of Android Market apps? This would be for apps that are now updated or no longer available on the Market? I am looking for a site similar to "OldVersion.com" which has some old/classic PC software (but this would be something for android apps instead)?
Thanks if anyone knows of a source or sites.
CustomShortcut gone?
The app that I am looking for in the above post was a free one called CustomShortcut APK. I now have it on one of my two phones (the other phone had it but was lost and replaced). I have tried looking for a developer page for this app but no luck as everything seems to point back to android market as the source link for download.
Does anyone know of a way or source for me to get this APK back on my other phone? Is there a way to copy it from one phone to the other? I am assuming that it was removed from the market because it may not be compatible with ICS but I am not running ICS. The application was made by appli.club.
Are you rooted? If so use root explorer to look for the .apk in the /system/app folder and copy or email it to the other phone and install it.
85gallon said:
Are you rooted? If so use root explorer to look for the .apk in the /system/app folder and copy or email it to the other phone and install it.
Click to expand...
Click to collapse
No sadly I am not rooted. Is that how this could be done? I have an HTC phone (Sensation) and I like my "sense" gui. Don't want to wipe it out by rooting (that is what would happen, right?) If access to the apk is possible with rooting, then I guess my question would be, does anyone else here have CustomCut on their rooted phone? (Or possibly know of any website that would have those apk's available for download). I would be willing to pay if someone would take the time to send me a replacement copy.
just google for any app you want like this:
"title" "versionnumber" "apk" "download"
for example:
android market 2.9 apk download
mojosingle said:
No sadly I am not rooted. Is that how this could be done? I have an HTC phone (Sensation) and I like my "sense" gui. Don't want to wipe it out by rooting (that is what would happen, right?) If access to the apk is possible with rooting, then I guess my question would be, does anyone else here have CustomCut on their rooted phone? (Or possibly know of any website that would have those apk's available for download). I would be willing to pay if someone would take the time to send me a replacement copy.
Click to expand...
Click to collapse
Rooting will not wipe out your phone or change it other than giving you super user privileges. That way you will have access to get to the system apps folder.
I notice apktop keeps old versions around. But part of the reason I like Titanium backup is because I have a fail safe if a new update to an app is bad, as I can just restore from the last backup the older version.
85gallon said:
Rooting will not wipe out your phone or change it other than giving you super user privileges. That way you will have access to get to the system apps folder.
Click to expand...
Click to collapse
Well I am not really too concerned about it wiping out my phone, but I thought I had read many posts here talking about once you root your phone the native skin from the manufacturer is eliminated (for HTC that would be the "Sense" user interface). Can you please confirm? Is this not true? HTC Sense will remain exactly the same after rooting my phone?
The other thing that has made me cautious is that my phone runs perfectly now and I see so many threads on the xda boards here and over at various android forums that start off with "My ____ app is not working right since I rooted...." Just a little daunting for a newbie like myself.
spunker88 said:
I notice apktop keeps old versions around. But part of the reason I like Titanium backup is because I have a fail safe if a new update to an app is bad, as I can just restore from the last backup the older version.
Click to expand...
Click to collapse
Thanks very much for the site suggestion. I have been trying to search for the CustomShortcut APK over there but no luck ...so far (the site search is not that easy to use). I have even tried to seach the site externally using google but, unfortunately, still no luck.
Wait for someone else to confirm on the htc, but nothing changed on my droidx. I just had superuser privs. All of the "this app quit working" is when people flash custom roms. You don't do that when you just root. But you have to be rooted in order to do things like that. Lol.
Rooting gives you the power to do that if you want to.
When I rooted my droidx, I did it just so I could have the power to do other things if I wanted. I am still on factory rom. But I am able to get to parts of the phone that are off limits if I wasnt rooted. I made it where I could tether, later I got rid of bloatware, etc.
85gallon said:
Wait for someone else to confirm on the htc, but nothing changed on my droidx. I just had superuser privs. All of the "this app quit working" is when people flash custom roms. You don't do that when you just root. But you have to be rooted in order to do things like that. Lol.
Rooting gives you the power to do that if you want to.
When I rooted my droidx, I did it just so I could have the power to do other things if I wanted. I am still on factory rom. But I am able to get to parts of the phone that are off limits if I wasnt rooted. I made it where I could tether, later I got rid of bloatware, etc.
Click to expand...
Click to collapse
Thanks once again for the reply. Now that you mention it, I remember reading the terminology "flashed" rom and thought they were similar or the same thing as rooting. One other question, once a phone is in a rooted state, if I was to go in and copy the APK for my replacement phone and put it on there could I then "unroot" lol ...sorry if this is not a word... so that my phone was no longer open? I had read somewhere (perhaps I heard it on a TWIT or Android podcast) that when your phone is in root state that anyone (ie: potentially bad software) has easier access to your phone's vunerable areas.
mojosingle said:
Thanks once again for the reply. Now that you mention it, I remember reading the terminology "flashed" rom and thought they were similar or the same thing as rooting. One other question, once a phone is in a rooted state, if I was to go in and copy the APK for my replacement phone and put it on there could I then "unroot" lol ...sorry if this is not a word... so that my phone was no longer open? I had read somewhere (perhaps I heard it on a TWIT or Android podcast) that when your phone is in root state that anyone (ie: potentially bad software) has easier access to your phone's vunerable areas.
Click to expand...
Click to collapse
yes you can unroot. As for easy access after you are rooted to vulnerable areas, they can only get access if you let them. If an app wants super user privileges, you will get a pop up from su(the super user apk) telling you that some app is wanting privileges. You can grant or deny access. The only things on my phone that have ever given me a pop up are things that i downloaded and know need su access. Wifi tether, root explorer, adfree, etc.
I have found a site that keeps older version of an android app. It's called Android Drawer.
Hope it helps
Is there currently a way to have both the Amazon App store and the Google Play store working together? On the newest update?
Does rooting have any adverse affects from Amazon? Like will anything stop working?
I plan on buying a used tablet, how can I check to make sure the tablet is deactivated so that I can use my own Amazon stuff on it and it doesn't get marked as stolen?
I may think of other questions I need help with in the meantime, but thanks for any help.
everwhere
Hobox10 said:
Is there currently a way to have both the Amazon App store and the Google Play store working together? On the newest update?
Does rooting have any adverse affects from Amazon? Like will anything stop working?
I plan on buying a used tablet, how can I check to make sure the tablet is deactivated so that I can use my own Amazon stuff on it and it doesn't get marked as stolen?
I may think of other questions I need help with in the meantime, but thanks for any help.
Click to expand...
Click to collapse
Check out the general section, you will find the anwser you seek. if you have any other questions there is also a search abilility..there are only about a half a dozen threads titled with the same or basically the same as yours...thanks for visiting and I hope you find all the information you need. Previous owner must unregister. the tablet from their account before u received it.and I would attempt to register it and setup your account before cash exchanges hands or contact amazon with id to verify that it has not been blackliisted already, it can either be unregistered by owner from tab then reset . Or done through ther online account..
A lot of the threads I have read seem to have people contradicting or trying to figure out what actually works or not, or is simply outdated.
Yeah, I'm with OP. I have a new Fire HDX and am trying to figure out the 'best' way to root it, and after reading through everything I'm more confused than before.
I haven't taken my Fire out of the box yet. There seems to be discussion that if I haven't downloaded an OTA yet, I can root in a way others can't because the new updates block it?
Is there a known "best" ROM someone can point us to?
Why do I keep seeing everyone say 'don't ever turn on wifi!'? I assume that is just to not get the OTA update at the beginning. But once rooted, obv we can use wifi right?
Is every root method dependant on creating a separate partition for the new ROM, and whenever we use the Kindle we have to choose to use the stock amazon rom or the new ROM we've flashed?
Thanks!
well
lordtigger said:
Yeah, I'm with OP. I have a new Fire HDX and am trying to figure out the 'best' way to root it, and after reading through everything I'm more confused than before.
I haven't taken my Fire out of the box yet. There seems to be discussion that if I haven't downloaded an OTA yet, I can root in a way others can't because the new updates block it?
Is there a known "best" ROM someone can point us to?
Why do I keep seeing everyone say 'don't ever turn on wifi!'? I assume that is just to not get the OTA update at the beginning. But once rooted, obv we can use wifi right?
Is every root method dependant on creating a separate partition for the new ROM, and whenever we use the Kindle we have to choose to use the stock amazon rom or the new ROM we've flashed?
Thanks!
Click to expand...
Click to collapse
Well "root"has nothing to do with seperate partitions n such. root is all permission control over system.
The only way to flash anything currently is being on older os rooting,then installing safestrap which will set up alternate system and data boot path allowing you to flash a ROM separately from your factory os ,as to not disturb it. Because currently we do not have stable working fastboot for this device. As for BEST rom. In any situation is totally in one own experience and opinions. Currently there isn't any selection if u look in development section the only two that function only work on old firmware ...you can roll back to that firmware ..but also bootloader is locked tight thus the need for a "safe" type of recovery as of moment only works on older firmware also. Just.within the last couple of days have reveiled a couple of rooting options for lastest firmware so ...this tab per Amazon gives no warning nor asks permission to upgrade of firmware which unrooted a ton of people last few months...soooo no root no development....now we have root again we will get going again..Have fun and most of all be PATIENT and do not ask for ETA remember all the developers here are doing that on there FreeTime and free of pay most the time. AS FAR as rooting and adding gapps to newest firmware I heard that it has been achieved with HDXPOSED found in development and permission module . Then sideload gapps... As far as adverse effects... Like I said you will have to be patient if you want somebody else to find out bugs for you.. still to new .....due to new root releases..like last three days.
I'm perfectly fine with the stock rom honestly, as long as I can get Google Play store working alongside the Amazon app store. Now, assuming I can root when I receive the tablet, I will install safestrap. Is there any bugs or anything with safestrap but just using the stock rom? I saw some people mention getting permission errors and such but I think that was just for custom roms in another slot. I only want safestrap to make a backup.
Basically, is there any actual danger to modifying the stock rom at all, even something simply like play store? Or should it all be done on a custom rom slot? I would assume having the backup would mean if something got messed up I can just restore it.
Secondly, there is a SEPARATE play store mod you can do where they don't both work together right? I believe I saw something about it where you just have to install a custom launcher, and with the custom launcher the google play apps work but under the amazon launcher, amazon stuff works? If that's correct, does that work without root? Because I can live with that temporarily until root is secured.
Thanks.
nope
Hobox10 said:
I'm perfectly fine with the stock rom honestly, as long as I can get Google Play store working alongside the Amazon app store. Now, assuming I can root when I receive the tablet, I will install safestrap. Is there any bugs or anything with safestrap but just using the stock rom? I saw some people mention getting permission errors and such but I think that was just for custom roms in another slot. I only want safestrap to make a backup.
Basically, is there any actual danger to modifying the stock rom at all, even something simply like play store? Or should it all be done on a custom rom slot? I would assume having the backup would mean if something got messed up I can just restore it.
Secondly, there is a SEPARATE play store mod you can do where they don't both work together right? I believe I saw something about it where you just have to install a custom launcher, and with the custom launcher the google play apps work but under the amazon launcher, amazon stuff works? If that's correct, does that work without root? Because I can live with that temporarily until root is secured.
Thanks.
Click to expand...
Click to collapse
As far as I know gapps aside from gmail will not work without root and HDXposed..(fixes permissions)and as far as doing any mods to stock slot it is not advised because of very difficult if even possible recovery due to no fastboot capabilities. Check for bugs for any mods in associated threads. As far as flashing anything ,again I am not sure safestrap is functioning on latest firmware .. And there hasn't been enough time for any development because of the recent rooting capabilities.
Alright, so it sounds like this is what I should do then:
Get tablet
Root it (If I can't, then I stop here)
Install safestrap
Backup
Install the backup on romslot 1??
Make the modifications I want to romslot 1
Is that right?
Also let's assume I can't root it, I can still sideload most apps I want like Gmail, Youtube, etc? (Those aren't on the amazon app store correct?)
yeap
Hobox10 said:
Alright, so it sounds like this is what I should do then:
Get tablet
Root it (If I can't, then I stop here)
Install safestrap
Backup
Install the backup on romslot 1??
Make the modifications I want to romslot 1
Is that right?
Also let's assume I can't root it, I can still sideload most apps I want like Gmail, Youtube, etc? (Those aren't on the amazon app store correct?)
Click to expand...
Click to collapse
Yeah I would say you just about got the idea .... If it is a brand-new unit you have a possibility that it will be on the old firmware still ... That is why they need to bypass activation skip set up . And check firmware before you hook it to any active Wi-Fi service .. And even if it does or is already updated there is now root available for the latest firmware ... It's just a question whether or not we can get anything else to work along with the latest firmware ... I would be advised if you attempt to run the OTA blocker which comes in the HDX utility you may have Wi-Fi glitches and reboots .... But like I said those bugs need to be checked for and follow through and repaired in their associated threads ... Not a new thread that only plugs up our forums but puts the helpful threads on the next page where cannot find them ... Remember there are multiple pages each forum section and some of the helpful threads have been buried on the next page due to people starting new threads with the same questions or problem... That have been resolved already... Remember reading is more informative than typing . And remember if anybody here is giving you their personal time to answer your questions and respond to your post it is courtesy here to hit the thanks button in the left lower corner of the post.End rant. thx
<~~~~~~~~~~ ; )
Ok, So i got the new updates from Google Wallet to the new Google Wallet and Android Pay.
When I attempted to setup Android Pay, I received the error that my device couldn't be "verified as being compatible."
A little browsing turned up some information that Android Pay doesn't like rooted devices, and even gave a couple of solutions.
1. Disable Superuser access if your Superuser app has the capability.
2. If option one isn't possible, then go back to stock, activate, and re-root.
This fix will NOT work for everyone, but since it is a simple setting change, it can't hurt to try this before looking into more 'drastic' measures. This will most likely only work on rooted stock ROMS.
I know that I use Chainfire's SuperSU app, and it has the ability to be disabled so the operator does not has superuser access until it is re-enabled. Simply go to your SuperSU app, go into the "Settings," and uncheck the "Enable Superuser." Different versions and other apps may be a little different, but principle should remain the same if it is an option.
After disabling SuperSU, open Android Pay and complete your initial setup. Once completed, return to the SuperSU app and re-enable Superuser access. The Android Pay app has continued working since then for me.
Based on information given by 'rbeavers,'
https://koz.io/inside-safetynet/
Guess I'm screwed
Click to expand...
Click to collapse
it appears rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on rbeavers' link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that probably won't matter if anyone is curious about that. (Could be different for other people though.)
Original Posting:
Just got the new Android Pay. I received an error that my device couldn't be verified as being compatible. Found some where else that it doesn't like rooted devices . Fix with SuperSU is easy. Go to SuperSU, touch Settings, and uncheck Enable superuser. Setup Android Pay, then re enable it, and so far, it's working for me.
Click to expand...
Click to collapse
Tried it didn't work for me "turned off " SU. My bank isn't on the "list". So that might be it?
Maybe? I didn't think Android Pay used the bank account, only Wallet does. Pay requires you to link your debit or credit card. Both apps automatically pulled my information, so I didn't have to dig into that very much.
Another thing my ROM is otherwise stock.
I've also read that Android Pay just doesn't like some ROMs, so users on custom or ported ROMs and a few devices in general are probably going to be left out in the cold... unfortunately.
Hopefully someone with more knowledge of the Android system can help us out here soon.
https://koz.io/inside-safetynet/
Guess I'm screwed?
Interesting read. Thanks for sharing
So, rooted stock ROMs will probably work if you disable superuser (no guarantee though). Custom and ported ROMs most likely will never work unless the devs figure out a workaround. I would also imagine a otherwise stock ROM running a custom kernel wouldn't work either based on your link.
Another note, I've integrated updated system apps and certain other apps into the system partition, so that shouldn't matter if anyone is curious about that.
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!