Related
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Just my 2 cents... There is not eLocity (Stream TV Network) problem
Google denied Market at some tablets. G considered that their OS version 2.X is not compatible with tablets.
These tablets do not have Market "out-of-box":
Viewsonic G Tablet
Malata ZPad
Advent Vega
Archos (all versions)
etc...
Idk why Galaxy Tab has market "out-of-box". May be Samsung proved Google that it's big phone)))
StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up
Click to expand...
Click to collapse
Try nameing the file Update. Do not add the.dot zip, holding down the power button until the third line of text is seen then release will get you into program mode.. selling a tegra tablet to get anything other than another tegra is like going backwards...
StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Click to expand...
Click to collapse
Where are you located? I'm. Sure if there is a member here local to you, they'd be willing to help you out.
I'm enjoying my A7 but, I do have to give a certain amount of blame to Stream for the lack of user friendliness the device presents. There are all sorts of documentation out there for companies to reference when designing an Android device, giving them an outline of what will work. The choice to implement a code structure or hardware features that do not work or require a work-around is directly the fault of Stream, as testing should have revealed the issues.
Take a look at how long Dexter has been working on the mod many of us are using, the feedback people give after putting it through the "real world" challenge and then the subsequent updates from Dexter...if Stream did the testing and verifications on this product from concept to creation to now...someone needs to be fired or doesn't care. Without detracting from Dexter's efforts or anyone else contributing on this board but, if the customer base can put so many fixes in place:Why can't the OEM? Why are they so slow in comparison on responses? Why don't their updates fix the most common issues? How did they allow themselves to release a tablet without a proper OS and fail to do better funtionality testing?
I'm glad their are folks like Dexter out here and forums like XDA otherwise decent hardware like this would allow companies to seperate us from our dollars on inflated claims of fuctionality and force us to jump through hoops to get a remedy.
problem with A7
StarBriteK said:
After spending much of the past 24 hours trying to install both eLocity's latest firmware update (from 2/24/11) and DexMod 1.3 (so I can utilize Android Marketplace) I am probably going to give up and return my A7 to the retailer before my 30 days are up. Thank you to Dexter and everyone else who posted such informative and useful instructions on the A7 forum. I am perplexed as to why I was not successful in accomplishing the update and modification. I really do like the A7 and hate to return it, but whats the sense of owning a Android device if you can't utilize the Marketplace. Duh! I would even be willing to pay a nominal fee to a honest, tech-savvy individual to modify/update my A7 for me. Thanks again everyone, looks like I'll be shopping for a tablet thats a little more user-friendly.
Click to expand...
Click to collapse
\
email me at [email protected] and I will do what I can to help.
A7 Towel
Here are some quick things to know/try that work for me -
1. SD card must be formatted as FAT format, FAT32 is fine
2. Mod file is named update.zip in sd card, do not put it in any folder in the SD card
3. When you are powered down, if you hold the power button in for about 15 seconds and then release and then hold in again for a few seconds you will see, hold in for another 5 seconds to go to boot menu, immediately hold in for another 5 seconds and then release, you should see a android character, tap on home icon on right and it should go into a boot menu
4. Use the buttons on the tablet (home, etc on the right) to page down and up the list of selections. Top 2 buttons on the right are up and down. Second to bottom icon is select.
5. Scroll to "apply sdcard:update.zip"
6. Select that option (second to bottom icon on right of screen)
it should now apply the update.zip on your sd card. It could take a while.
If there are any errors then the update.zip file may be corrupted. All updates are over 90MB in size except for the patch that Dexter sent recently which is around 3MB.
Let us know if this works.
Thanks for the responses
I have done several times the instructions some of you have responded back with and watched several posts on YouTube also. Yes my card is formatted to Fat32 and yes I used a capital U on Update.zip. I have followed the instructions to a "t" for installing DexMod and Elocity's own instructions on their website in regards to the 2/24/11 update. My A7 simply would not recognize and open the SD card file and would then abort the program. I'm simply at a point where how much more of my time do I want to spend spinning my wheels on the A7 tablet in order to have access to the Android Marketplace. Thanks again everyone.
Please see my response at bottom.
A7 issue
sorry to hear that. I suspect your update.zip file is probably not being recognized as a zip file. mine is named update.zip, no uppercase anything. Sometimes there can be a hidden extension of another .zip so the system sees it as update.zip.zip
I downloaded the mod and renamed mine on my pc and then copied it directly to the microsd card. Sorry to hear about the time its taken you so far. As I said earlier I would be happy to work with you if you wish.
just to clarify, you can't really install the latest feb 24 update from elocity AND dexters elocitymod rom. Unless, that is, you take the mods that dexter has done and apply them to the latest elocity update and regression test it, debug it, etc... elocity did a fair job of putting out a cheap android tablet. they made some sacrifices on the hardware side - no multitouch and no hi res screen, but for the price, it's hard to beat. and dexter's mod makes the a7 infinitely more useful. have you tried other microsd cards? you can get cheap 2gb and 4gb ones at target or bestbuy. if those don't work, you can just return them. lots of people have been using dexter's elocitymod successfully. without it, i probably would have returned the a7 also. if you're looking for something a bit more polished, get ready to spend a bit more. samsung galaxy tab goes for about $600-$800 motorola xoom about the same price as well.
Did you check your sd card for bad sectors or tried a different sd card? Just curious.
Same problem adding Dexter Mod
I've just got the A7 and I'm following the threads about the Dexter Mod. I'm a little confused about 1- what to name the file...some say with a capital U and some not...2- with or without .zip...again same thing 3- can you use the 1.2 Mod after Elocity's latest firware update...the reason I ask this is because the link for 1.3 is down and I do have 1.2 on my pc for some reason.
On my sdcard it doesn't have a directory "ROOT" do i just copy it to the open card. So may questions...sorry about that, been at it for 3 hours and no success. Have to laugh tho....
BTW I have a file named LOST.DIR on the sdcard
file name
The file when you download it is already in zip form. All you need to do is rename it to ( update ).
Dexter Mod 1.3
Thank you. Just installed on 1 of my A7's but the 1.3 Mod...Was able to download it this morning, the site is back up again.
Now to do the bluetooth fix...life is all go...lol
Ok, lets clear this up once and for all...
For everyone that is getting confused about update.zip, Update.zip, Update.zip.zip, and whatever other additional permutations of combinations that people have been able to come up with.
The answer: although some people have reported success with a lower case "u", the best way is to simply follow the directions layed out for you and name it "Update.zip"
Here's the simple truth of the matter, the file you download is <Dexter's_webspace>/ElocityModv13.zip ... or if you are going after eLocity's updates it would be
<elocity's_webspace>/update.zip
Notice that both files have ".zip" at the end. No question about it, no chance that this is not true, no chance that as I actually saw someone post on here "elocity never named it .zip".
Now, here's where people have the opportunity to get confused and do something wrong...
PC Users:
A default out of the box Windows installation is set to HIDE file extensions of known file types (zip files included). So, when you look at your download it will appear to be just "ElocityModv13" or just "Update" even though the file extension (.zip) is actually there. So when you try to rename it to "Update.zip" you are changing only the information BEFORE the file extension, thereby making it "Update.zip.zip"... This is no one else's fault. Please don't blame eLocity, please don't blame Dexter, please don't blame the Android OS itself.
The Solution!:
Open Windows Explorer, go to the "Tools" drop down menu, go to "Folder Options", click on the "View" tab on the window that just popped up, uncheck the "Hide extensions for known file types" checkbox, click "OK", profit.
MAC Users:
I am guessing that this applies to most of the "What do I do with all these folders from the zip file" type of posts. The most probable issue here is that Mac's have a rather annoying habit of unzipping zip files as soon as it finishes downloading them, leaving you with just a folder (in this case either named "ElocityModv13" or "update" with no file extension (its a folder).
Mac Solution:
To keep Safari from automatically unzipping your files, the fix is easy.
Open Safari, open Safari's preferences, Click on the "General" tab, uncheck the "open safe files" box, close preferences. Now download either the mod or the stock update again, and you'll have the actual zip file instead of just a folder with the contents of the original file.
Hopefully this helps a lot of people figure this out.
Now...
My Disclaimer:
I already am prepared for the inevitable "stop being rude", "somebody call me a wahmublance", "I'm new to this" type of response that I seem to get more often then not on here. So, before any of that happens let me explain my standpoint.
Anyone trying to go down this route and put a custom rom on their device is attempting to modify it. This SHOULD require at very least a working knowledge of the device or software you are trying to modify. I am not saying everyone here should be on Dexter's level, but at least a little computer know how would be very beneficial. Next, before just diving in to changing things on this little chunk of technology that you just spent a few hundred on, read. Simple as that, educate yourself on the toy you just bough. Creating many many duplicates of threads asking the same extremely basic questions does not help anyone. It clutters up the forums, makes the people that actually have the answers so sick of saying the same thing over and over that they just don't answer any more, makes it harder to navigate the actual different topics, and makes it harder for everyone else to find the answers they are looking for. There should be no "which one of the 15 bluetooth not working threads was that post in?"
I apologize for my complete lack of patience with people that can not search for information and need to be spoon fed. But 99% of the time the question has already been asked and answered. And lets be serious here, the A7 forum only has FOUR SECTIONS, really not a lot of reading. And in the other cases where it is a user error like not knowing how to rename a file or yesterday's hilarious "My SD card doesn't have a folder called ROOT", you really need to ask yourself if this is really something you are up to. If you lack the basic knowledge to perform the easy steps of the process, is it really worth it to risk creating a $300 paperweight to say "look at the cool thing I did" to your friends?
If something I said here seems like it was taken from your post/story, don't take it personal, it was only listed as an example.
I'm sorry I opened such a can of worms on this subject for some "TECHNOLOGICALLY-ADVANCED" individuals who seem to have nothing better to do but respond with condescending remarks on this forum. FYI: I recently purchased a new Samsung Galaxy tablet on eBay for $360.00, hence my A7 has been shipped back to the retailer for a refund. I still think the A7 is a great device, I simply do not have the time to repeatedly attempt to update it so I can have access to the Android Marketplace, nor the patience to tolerate the attitude of certain posters to this forum. I thought the purpose for this forum was to help each other out on issues, not to repeatedly "Beat Dead Horses" which some individuals tend to be doing. Thanks again everyone and GOOD LUCK!
StarBriteK said:
I'm sorry I opened such a can of worms on this subject for some "TECHNOLOGICALLY-ADVANCED" individuals who seem to have nothing better to do but respond with condescending remarks on this forum. FYI: I recently purchased a new Samsung Galaxy tablet on eBay for $360.00, hence my A7 has been shipped back to the retailer for a refund. I still think the A7 is a great device, I simply do not have the time to repeatedly attempt to update it so I can have access to the Android Marketplace, nor the patience to tolerate the attitude of certain posters to this forum. I thought the purpose for this forum was to help each other out on issues, not to repeatedly "Beat Dead Horses" which some individuals tend to be doing. Thanks again everyone and GOOD LUCK!
Click to expand...
Click to collapse
You didn't open a can of worms, it was just a coincidence that the misinforming post that sent the fingers of fury flying happened to be on your thread. and trust me, I have plenty of better things to do, this is just filler.
Seems like you got a hell of a good deal on the G Tab, Congrats.
And yes, the point of a forum is to help other people, which I do. By correcting bad advice, and trying to get people to ask for and give help in a more collaborative way instead of the same questions being asked over and over again. I'm sorry if you find my presence on the internet grating, just be glad that you haven't had to endure my vocabulary in person (apparently it is pretty similar to that of a drunken sailor with tourette's syndrome with the same measure of sarcasm that I treat the net to)
Back at you on the good luck. Expecting a review on the g tab, pro's and con's vs the A7 hopefully
LOL
LOL, you guys are just hilarious
...wouldn't this be an option (people more in the know, please correct me if I am wrong):
- Use one of the utilities to revert your system back down to ICS (4.0.4)
- Unlock the bootloader / root / do whatever you want to do that you can't when on the latest software...
- Re-take all of the updates to get you back up to 4.1.2 (or use the utility to get back to 4.1.2)
Easy-peasy, pending the updates that block the unlock exploit are reverted as well when the software is reverted.
I do understand that one would lose all their precious info (contacts, pics, vids, apps, etc.), but making a hard copy list of that stuff (or a backup of some sort - Backup Assistant Plus, DropBox, and Titanium Backup to Cloud storage come to mind) may be worth it to get the bootloader unlocked. To save pics, vids, etc. one could also just drop all of that stuff on to their computer before reverting as well.
Just thinking of a way to help those that cannot unlock but want to... maybe it'll help rid the forum of the "new unlock method needed please" threads as well
From what i've gathered, downgrading the phone from current firmware will not undo their patch that blocks unlocking/rooting.
LifeAsADroid said:
...wouldn't this be an option (people more in the know, please correct me if I am wrong):
- Use one of the utilities to revert your system back down to ICS (4.0.4)
- Unlock the bootloader / root / do whatever you want to do that you can't when on the latest software...
- Re-take all of the updates to get you back up to 4.1.2 (or use the utility to get back to 4.1.2)
Easy-peasy, pending the updates that block the unlock exploit are reverted as well when the software is reverted.
I do understand that one would lose all their precious info (contacts, pics, vids, apps, etc.), but making a hard copy list of that stuff (or a backup of some sort - Backup Assistant Plus, DropBox, and Titanium Backup to Cloud storage come to mind) may be worth it to get the bootloader unlocked. To save pics, vids, etc. one could also just drop all of that stuff on to their computer before reverting as well.
Just thinking of a way to help those that cannot unlock but want to... maybe it'll help rid the forum of the "new unlock method needed please" threads as well
Click to expand...
Click to collapse
along with the many "new unlock method needed please" post, there are many post just like yours, to which in every case we "in the know" state "cant be done/will not work"
as previously stated, the files that need to be modified to unlock can not be reverted.
Yeah, like Bwen said, it's not going to happen. The ability to downgrade was locked up on the update that also patched the unlock. Many have tried, many have failed, and a few have bricked.
1) I apologize if it came off as offensive about the stopping all the "new unlock method needed please" posts. It wasn't meant to be. Was simply thinking that new posts like that wouldn't develop, and the older ones would naturally die off, thus letting us all happily and jointly move on to newer topics or issues and solve them when they arrive. I have seen lotsa posts from people needing a new method to unlock, I haven't seen any along the thought process of trying the method I (apparently unoriginally) suggested.
2) Of course I did not expect this to be a new idea, but hadn't seen it posted so I thought I'd give it a whirl and perhaps help others out if it hadn't been thought of... A shot in the dark of an idea.
3) To receiving the knowledge that it cannot be done this way - ah nuts. Oh well, tried to help.
4) I'm glad I went and did the unlock when I did, prior to the corrective action taken by Motorola.
5) Anyone know what caused Motorola to make the fix? Since the XT925 is able to be unlocked, I'm thinking they don't personally care whether people unlock or not... I'm guessing that VeeZeeDub may have forced their hand to make the correction since VeeZeeDub doesn't want the phones unlocked? (disclaimer: I apologize up front if this is not a new topic)
I would blame it on VZW, more than anything else. Moto is somewhat trying to push towards being more dev friendly, but VZW is far from it.
I agree that it must be Verizon. Sorry for the duplicated thanks in the post above.
Sent from my RAZR Maxx HD
Jhall8 said:
I agree that it must be Verizon. Sorry for the duplicated thanks in the post above.
Sent from my RAZR Maxx HD
Click to expand...
Click to collapse
No worries man. I know I can be abrasive and it only gets amplified through the internet, and I apologize if my post came off that way.
LifeAsADroid said:
1) I apologize if it came off as offensive about the stopping all the "new unlock method needed please" posts. It wasn't meant to be. Was simply thinking that new posts like that wouldn't develop, and the older ones would naturally die off, thus letting us all happily and jointly move on to newer topics or issues and solve them when they arrive. I have seen lotsa posts from people needing a new method to unlock, I haven't seen any along the thought process of trying the method I (apparently unoriginally) suggested.
2) Of course I did not expect this to be a new idea, but hadn't seen it posted so I thought I'd give it a whirl and perhaps help others out if it hadn't been thought of... A shot in the dark of an idea.
3) To receiving the knowledge that it cannot be done this way - ah nuts. Oh well, tried to help.
4) I'm glad I went and did the unlock when I did, prior to the corrective action taken by Motorola.
5) Anyone know what caused Motorola to make the fix? Since the XT925 is able to be unlocked, I'm thinking they don't personally care whether people unlock or not... I'm guessing that VeeZeeDub may have forced their hand to make the correction since VeeZeeDub doesn't want the phones unlocked? (disclaimer: I apologize up front if this is not a new topic)
Click to expand...
Click to collapse
it really doesn't matter that this was posted again, you could post it 10 more times and i guarantee within a couple days someone will ask again.
the problem is, there is an ever increasing group of people who want answers spoon fed to them because they are too lazy to read for 5 minutes to find it them self. that may sound harsh, but if you have been around the forums for at least a few years helping people its easy to see it progressing.
i have provided help on various forums through the past few years and the majority of the time when i dont have an answer, i throw some key words into a search engine and come up with the answer within minutes.
its not that im much more knowledgeable than most, its that i would rather read a few minutes and learn how to do something rather than have someone feed it to me. thats why you very rarely see me ask any questions or ask for help. 99% of the answers are out there some where, all you have to do is look...
:semi rant concluded: just my opinion, take it as you will...
I know that we can't load prior software as it won't over write the exploit fix but, here's what I don't understand. When a phone gets sent back for repair, I would think there's a way that they wipe the phone out completely removing any trace of it's previous owner. Including the traces of a new update, boot loader...etc. Then install a completely fresh copy.
Why can't that technique been done to reinstall the previous software that allows boot loader unlocking? Wouldn't a cell phone repair shop have this capability? If you put a new board in the phone, can it be flashed with any software?
Or even in the refurbish process, not everything gets wiped?
bear263 said:
I know that we can't load prior software as it won't over write the exploit fix but, here's what I don't understand. When a phone gets sent back for repair, I would think there's a way that they wipe the phone out completely removing any trace of it's previous owner. Including the traces of a new update, boot loader...etc. Then install a completely fresh copy.
Why can't that technique been done to reinstall the previous software that allows boot loader unlocking? Wouldn't a cell phone repair shop have this capability? If you put a new board in the phone, can it be flashed with any software?
Or even in the refurbish process, not everything gets wiped?
Click to expand...
Click to collapse
I'm sure moto or verizon can do it, but they have access to the software that contains the encrypted key that is necessary.
But, in any event, they probably would just update it to the latest software if that hasn't happened already.
I got lucky. When I had to replace my RAZR MAXX, they "upgraded" me (for free) to a RAZR MAXX HD. I was lucky enough to have it come in with the 9.16 version, which meant I was able to unlock it, which I did immediately.
The main thing to understand is, if you don't unlock at the 9.14/9.16 version BEFORE applying any other updates, there is NO way to unlock the bootloader. It was an exploit that wasn't meant to be there. Said exploit has now been patched, and if you didn't take advantage of it when it was there, then you have no one to blame, not even Verizon or Moto since it was a security issue that they didn't know existed.
I've rooted all my devices since the days of the OG Droid. Up until a year or two ago, root and custom roms were a must have for a lot of useful features, but the dependency on root features has definitely gone down as stock android has advanced.
With the Moto X being mostly stock, and a little harder to root (especially with every OTA) I've been thinking about just going stock and keeping it unrooted when it arrives today.
As of now I use root mainly for just backing up and syncing app data between my phone and tablet (since a lot of apps don't implement google's cloud sync). It appears that Helium works with the Moto X, though that's definitely not as seamless or quick of a process. I also use Greenify but apparently that doesn't need root anymore.
Has anyone else gone down this path? I feel like I might end up missing a lot of things I can't even think of right now.
I just got my MotoMaker yesterday, and I was basically in the same boat. I was initially going to just unlock the bootloader, install TWRP, and install SuperUser, but the Moto site was rejecting my device key. I usually will immediately root a device and install Titanium Backup to install my standard set of apps. I gave up waiting for Moto to update their db and started installing apps without unlocking. Most apps I use don't really store much beyond some basic settings locally, so I just re-downloaded everything I wanted from the Play Store and logged into everything again. The few apps that had locally saved data that I wanted to transfer (games, mostly) I ended up using adb on my computer to backup individually, then used adb to push the apps to the new phone. This worked for most things... some apps don't let you back them up. My biggest concern was Google Authenticator, which I use for a number of websites. For that, I had to cheat. Since my existing phone was already rooted, I used adb to pull the stored secrets database off the phone (which you can't do without root). I found this awesome tool which lets you generate QR codes directly from a Google Authenticator db file, and used that to add the secrets to a freshly installed copy of Authenticator.
In the end, the Moto site finally let me get an unlock code, though I think I've decided to skip that, at least for the time being. Unlocking the device wipes it, and I've got things installed and configured the way I want. I don't see myself wanting to push any non-stock roms to this (I really like the Moto additions). I still want root (mostly for backups, though it does make tweaking the device a bit easier), but I can live without it for now.
detonation said:
I've rooted all my devices since the days of the OG Droid. Up until a year or two ago, root and custom roms were a must have for a lot of useful features, but the dependency on root features has definitely gone down as stock android has advanced.
With the Moto X being mostly stock, and a little harder to root (especially with every OTA) I've been thinking about just going stock and keeping it unrooted when it arrives today.
As of now I use root mainly for just backing up and syncing app data between my phone and tablet (since a lot of apps don't implement google's cloud sync). It appears that Helium works with the Moto X, though that's definitely not as seamless or quick of a process. I also use Greenify but apparently that doesn't need root anymore.
Has anyone else gone down this path? I feel like I might end up missing a lot of things I can't even think of right now.
Click to expand...
Click to collapse
I am the same as you. Traditionally, I always rooted but for the X I've just felt no need. (I was worried about receiving future updates, mostly).
I wrote a guide on backing up and restoring app data to the Moto X without root.
Helium works well for backing up your old devices, but it seems to have trouble for many on restoring the data. That's where my guide comes in, helping lay out the adb commands to finish up.
I will add, though, that after the Lenovo/Moto X announcement, it seems likely that I will root this in the future in case Lenovo drops the ball with delivering future OS updates.
Thanks, forgot about using adb for backup/restore
First Andoid I haven't felt the need to root, it's just so stable and smooth. The only reason I can imagine rooting it would be to install Adaway. Didn't realize how many ads there are until now :laugh:
I have rooted all my previous phones up until the X. I'm still able to enjoy it without the root access.
Usually rooting was necessary to debloat the phone and tune it to a stock like Android experience. Haven't really needed it with the X obviously.
The only thing that bothers me I guess is I didn't realize some of the apps I use had ads....lol
I just want adblocking again.
I was in the same boat before. Flash flash flash... That's all I ever did. Of course it was due to HTC and Samsung. Then with my n4 I went custom kernel and a few mods. The only thing I truly miss root for is ad block but that I can live with out
Sent from my XT1053 using Tapatalk
This is my fifth android phone and the first I didn't root. Finally saw no need to as like you say android has come along way, especially with being able to disable and hide apps you don't want. I have used Helium for backup, it needs to be connected to a PC for the first use and then every time the phone is rebooted, a little bit of a hassle. I also have used mybackup pro since 2010 and it never needed root but doesn't have the option to back up to box or dropbox only their own cloud storage.
Same thing for me. Decided first phone not needing root. Tethering even works out of the box! (XT 1053 on AT&T).
The only catch I had with helium was that I wasn't able to restore google authenticator data. So I manually used an SQL lite tool to extract the keys and just re-enter in a new install of google authenticator.
I refuse to limit myself so I got a developers edition. Being one if the first in America with 4.4.2 and being able to fix the exchange email issues beforehand etc are reasons I made sure I had root as an option. However this and my Nexus5 are the first phones that don't have Cyanogen Mod and so far I don't see a need or have a desire to run a different OS.
MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
You're a better man than I if you can pull it off
Galaxy S4 was my first bootloader-locked phone, and I couldn't stand it. I'm on Moto X Dev version now.
I got my Moto X (at&t version) a couple weeks ago and like you I've always rooted. This time the experience was great out of the box, I just reinstalled everything fresh. I hate seeing tons of folders on my "sdcard" so now I feel like its clean and there is no legacy garbage brought over from my old phone. The only thing I am missing over my old phone (HTC One X) is being able to tether for free.
Also, the Motorola Migrate app is actually pretty good at bring your pics, texts and call logs over to your Moto X.
compulov said:
found this awesome tool which lets you generate QR codes directly from a Google Authenticator db file, and used that to add the secrets to a freshly installed copy of Authenticator.
Click to expand...
Click to collapse
Can you share a link to this? I need this also!
msk said:
I got my Moto X (at&t version) a couple weeks ago and like you I've always rooted. This time the experience was great out of the box, I just reinstalled everything fresh. I hate seeing tons of folders on my "sdcard" so now I feel like its clean and there is no legacy garbage brought over from my old phone. The only thing I am missing over my old phone (HTC One X) is being able to tether for free.
Also, the Motorola Migrate app is actually pretty good at bring your pics, texts and call logs over to your Moto X.
Click to expand...
Click to collapse
That's exactly how I felt... I wanted to start clean. I have all my photos uploaded to Google+ via auto backup and I occasionally import them all into Lightroom on my laptop, so that was a non-issue. As for SMS, I've been using SMS Backup+ for a few years now to automatically backup my SMS and call history to my Gmail account. It also makes it easy to search my SMS history if I'm looking for an old message.
Can you share a link to this? I need this also!
Click to expand...
Click to collapse
The tool I used can be found here: https://github.com/ikonst/authenticator-import
It's basically an html page and some javascripts that you run locally in your browser (no web server needed). I actually want to run this again and save the QR codes either into Lastpasss or an encrypted file or something, just so I have easy access to them in the future.
I can do lots of things without needing root now thanks to third party apps. There are still essential reasons I need root. Ads blocking and apps permission management mainly and have more to do with security and anti-malware, I purchase my apps so it's not about depriving devs. App Ops will no longer work with Android 4.4.2 without root, I think it's a major mistake by Google. Also Cerberus needs root to exist through factory reset.
But so far I haven't root my Moto X due to warranty, but will eventually. I think the Moto X is very usable without needing root and KitKat with ART performance really help with that.
Just a question about the bootloader on the MotoX. If I unlock it, can I relock it and unlock it later without needing to use the unlock code or run into any trouble?
sent via tapatalk
I was in the same boat for about a day. I couldn't help myself and had to get the Xposed Framework up and running. I need Gravity Box and Xprivacy.
Sent from my XT1053 using xda app-developers app
overthatscreen said:
I was in the same boat for about a day. I couldn't help myself and had to get the Xposed Framework up and running. I need Gravity Box and Xprivacy.
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
+1
I am probably going to root but only because I often use tethering. I used to do all the custom roms and such, but those are more of a PITA than they're worth the majority of the time.
deanrobbins said:
I am probably going to root but only because I often use tethering. I used to do all the custom roms and such, but those are more of a PITA than they're worth the majority of the time.
Click to expand...
Click to collapse
I rooted because I needed to get that stupid at&t logo off the top of the screen and gravity box was + and greenify.
MOTO X Slapped
Greetings fine folks of the S3 Mini forum!
I first broached this idea in the OmniROM 5.1.1 thread - I just got back from Cuba having met some folks out there who are pretty keen to get their hands on the latest Android goodness, but are completely unable to as:
there is essentially no residential internet in Cuba
there is no cellular internet
the WiFi you can find in tourist hotels/town telecoms offices cuts in and out preventing downloads of any size
Many Google services don't work due to the embargo
Currently apks are shared phone-to-phone using Zapya over Bluetooth and WiFi hotspotting. To give these guys something to play with, I am planning on sending an SD card over - an Android 'care package' - including:
Everything needed to flash custom ROMs (USB drivers, ODIN, minimal fastboot/adb)
A couple of custom ROMs (CM12.1 and OmniROM?)
Comprehensive flashing instructions (using Odin and not) for the S3 Mini (translated into Spanish ideally)
GApps (5.1.x) - 'Mini' if the phone can take it
Useful .apks/binaries e.g. Camera, Cardboard (I took one over, it was a big hit!), SuperSU...
Anything else useful to get them started playing with Lollipop
I'm currently working in a Google Doc collecting where these things can be downloaded and starting to find flashing instructions - which is where you guys come in. Although I found the S3 Mini to be relatively popular in Cuba, I don't own one so I can't test this stuff myself. If anyone would like to contribute to this project, I'd really appreciate it. It won't require too much work - but some sanity checking would be appreciated. You can find the Google Doc here. If you do make any changes, please use 'Suggesting' mode or coloured text
If you have any suggestions for things I should be including other than what's above and in the document, please add it or let me know. I'll update this thread once I've got some instructions done to be checked.
Thanks!
Regarding the flashing instructions, I don't know if this can help you, though it's in English.
http://forum.xda-developers.com/showthread.php?t=3102258
Sent from my GT-I8190 using XDA Free mobile app
Since the the guide mentioned above is mine, i would like to know if it is the final choice.
Why not set up a mesh network? If you could get enough devices running it, You could in concept make your own internet.
I'm not from Cuba, (live in south Florida) but I can probably help out.
Disclaimer: I know this should go in the correct subforum for my device, but I'm having trouble navigating this site, altogether. I only see subforums for a handful of devices. So if there is a better place for this thread, I apologize
Oh, where to begin. My wonderful girlfriend got me this tablet back in october, since i said it'd be nice to have a linux based tablet so i wouldn't have apple telling me what i can and cannot do with my device (she saw that as a hint, even though it was more social commentary, but I'll take it). Anyway, I found the 16GB limitation problematic, so I decided to root it so i could use some sort of sshfs app to create a slow multi-terabyte harddrive space to steam small files (like music) from. Seeing as i had the thing for only a week and it's kind of expensive, even for a nurse, to buy for me, i chickened out and made due with a small 8GB microSD card which i just happened to have laying around.
Fast forward to a few days ago, I ordered from Amazon a 128GB microSD card (also from samsung), and decided to try to make due with that. Only to find out (and, if you're able to help me you've probably met the following issues yourselves) that the seemingly largest apps refuse to let you move them to external storage. Even better, there's some apps like Star Wars KOTOR (2.5GB) that say they let you move them, but in reality they stay on internal storage and create empty folders on the external medium. And then many apps cannot write and read to and from SD cards (like DOSbox Turbo), for reasons that completely stump me (which leads to me having to move dos games back and forth when i want to play one that saves). I then read about this wonderful feature called "Adoptable Storage," and promptly go through all sorts of things to try to enable it, only to find out that, since I have Android Version 6.0.1 from Samsung, that feature was disabled by them. After using the email support to berate them (they don't have a suggestion box), decided to try to come here and figure out how to properly root this device and figure out how to solve my space issue (I have 128GB of space that I need to use, but have no idea how to use it for what i need to use it for). By the way, a small shoutout to Samsung support, despite my very terse response, there clearly was a human being at the other end and this human was very, very civil and said that they'll pass it on as feedback (I got the impression that the employee either had the same issue or at least wanted me to know that there have been alot of complaints about this issue).
Anyway, now that that wall of text is over, this is how far i've gotten.
I know that XDA is reliable, they've had problems in the past with malware, but it was unintentional and the ship has been cleaned. I don't know about anywhere else, so the rooting instructions i find elsewhere i assume are probably correct, but i don't know where to get files for the process that i can trust, outside of XDA (and i'm having trouble finding the files i need, here).
I have a nice little article from techbeasts.com ( techbeasts.com/install-twrp-and-root-samsung-galaxy-tab-e/ ), but I don't know where their downloads came from and how many people checked them out for windows and android trojans and such.
So...
1. Is that article accurate for android 6.0.1?
2. Are those files safe (free from corruption and viruses)?
3. If they're not safe, where can I get safe files?
4. I like to develop programs, and I want to be able to develop apps for android as well. Once rooted, how does one test how their app would work on an unrooted device to ensure the app follows the "proper procedures?"
5. How do I deal with apps that are root sensitive? The point of all this is so that I can keep using my apps, so if they all break because i'm rooted that defeats the purpose.
6. Other than having to be careful with what i do (I've used Linux for years, and I occasionally like to code in assembly), that it voids my warranty, and that screwing up can make for a really bad day, is there anything else that I should know? This is, indeed, my first touch screen device outside of Nintendo products, because my V3xi is fine for me as a phone.
EDIT:
7. Forgot the most important question: How would I go about getting adoptable storage working on this device once it is rooted?
Forward: Given the nature of my question, the URL is absolutely necessary. After I've gotten my "10 useful posts" I'll fix the URL for future viewers.
EDIT2: Decided to take a chance. Ran into some issues finding the "stock firmware" which I ended up having to do. For those that have problem getting TWRP to stick, you gotta flash the stock firmware of the version you have currently installed. I tried to flash the original that it came with, which, for some reason, it didn't like at all.
Oh, and don't turn off OEM mode after everything's done. I assumed that after everything was installed it wouldn't second guess it and i could safely turn it off for added security if any app went rogue or something. Nope, must keep it on, so do regular backups. Turn off auto-updating, etc. I hear there's some sort of app that lets you "update safely." Not sure what it is, but unless you *NEED* it, don't do it.
And as a bonus note (so it shows up in the archives), some apps didn't install right (either google or the app developer's fault, but these apps weren't tied to this process [pokemon go and just about all the final fantasy games]). The kicker about this is is that you will not notice this UNTIL you uninstall the app, and reinstall it. Deleting the data before uninstalling the app will make it unstable. To find the data, i used
Code:
du / | grep "pokemon" > pokesearch.log
, since i knew that there should not have been a pokemon related directory on my droid at the time, since i needed to reinstall pokemon go because it was acting really fruity. Deleting the folders (actually, the last entry contains the rest, so it's easier just to delete the last one) allowed me to avoid the -504 issue (not to be confused with 504).
Code:
[email protected]:/data/data/com.termux/files/home # cat pokesearch.log
4 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/cache
1192 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/code_cache
12 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/shared_prefs
4 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo/files
1220 /mnt/expand/07aa2c40-4a8f-428c-afb9-7495df69eb26/user/0/com.nianticlabs.pokemongo
Message me if have the same tablet on a system root
Sent from my SM-S907VL using Tapatalk
denakor said:
Message me if have the same tablet on a system root
Sent from my SM-S907VL using Tapatalk
Click to expand...
Click to collapse
We can talk here for the benefit of the community. Any problems you might have should be documented for the sake of the community. But, yes, the -504 error i mentioned above can only be solved through root, so, yes, i was successful.
Kohlrak said:
We can talk here for the benefit of the community. Any problems you might have should be documented for the sake of the community. But, yes, the -504 error i mentioned above can only be solved through root, so, yes, i was successful.
Click to expand...
Click to collapse
I have the same tablet
---------- Post added at 09:32 PM ---------- Previous post was at 09:28 PM ----------
keith thibodeau said:
I have the same tablet
Click to expand...
Click to collapse
Tablet just updated itself after I tried to root it .. MM 7.0.1 but I didnt ask it to
I disabled automatic updates (from settings and google play, 'cause it's in both places) to prevent this problem. There might be a new firmware for the tablet, but i'm sticking to this version. I'm not sure you can downgrade after you upgrade, though. You can take a shot, though, if you're not afraid of loosing data. I doubt this process will brick as long as you can get the official firm ware on backup incase something goes wrong.
Kohlrak said:
We can talk here for the benefit of the community. Any problems you might have should be documented for the sake of the community. But, yes, the -504 error i mentioned above can only be solved through root, so, yes, i was successful.
Click to expand...
Click to collapse
Now it seems impossible to root without pc