Ever since getting my Razr Maxx HD (XT926) three months ago I've been trying to get rid of the Navigation Bar on the bottom of the screen. I use Button Savior so I'm fine with having the NavBar controls disappear.
Among the most reliable remedies seemed to be upgrading to 4.1.2, at which point many people said that you could simply add the line "qemu.hw.mainkeys=1" to the end of your build.prop file in /system, reboot, and *poof* the NavBar would be gone. My phone, which I bought used, was running a leaked 4.1.1 so, once root for OTA 4.1.2 was discovered, I downgraded to 4.0.4, did the updates to that, then took the OTA upgrade to 4.1.1 (no problem), then took the OTA upgrade to 4.1.2 (no problem). So now I had the latest JB version offered for Verizon XT926 in the US. I know that I'd wiped data at least once along the way. The SafeStrap installation that I used to have was gone, as I expected. I assumed that my phone was as stock as it could be and thus ready for the build.prop edit.
I used the new procedure to root my XT926. At that point all I did was to download and install Root Explorer (needed to do the build.prop edit) and Button Savior (needed for navigation once NavBar was gone). In Root Explorer I navigated to /system, made it R/W, opened build.prop in the stock text editor, added qemu.hw.mainkeys=1 at the end, saved (which backed up the older version as expected), and rebooted.
The first thing I get when my phone boots up is the "SystemUI has crashed" error message. My NavBar is gone but so is my System Bar (a/k/a Notification Bar), which I need and want to be visible. I've read a TON about this and I'm pretty sure I've followed the instructions. Why is this not working for me?
I am just not smart enough to decompile and edit my framework-res.apk file (or whatever the name is) so I'm stuck trying to make the build.prop edit work. What could I be doing wrong?
(also, if I use one of the apps like FullScreen or BottomBar they produce the EXACT SAME result -- SystemUI crashes, NavBar disappears but so does System Bar).
cant help
it works for me as experted
Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX
deeje00 said:
Are you positive you entered it correctly?
Sent from my JokerMATRIX HD MAXX
Click to expand...
Click to collapse
He also tried an app which writes the line to the build.prop and got same results.
AFAIK I had crashes on ICS but since I'm on JB 4.1.2 I never had any issues...
Sent from my XT925 using xda app-developers app
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
I have had the exact same issue and done the same troubleshooting...sucks!
did you happen to check file properties after you saved, i remember back in the early days of Android if you edited a file, you had to change the properties back to the defaults, not sure if that is still the case, but worth a look.
It can't be done on any stock via build.prop only, and framework edits require a deodexed rom.
I recommend you install CM10 or 10.1. If you prefer safestrap over CWM, then you can use CM10, but without a camera. Fullscreen toggle works perfectly, and I'm able to use PDroid : )
I suppose I should be glad that at least *one* other person is having this problem. Means it's slightly less likely that I'm just incompetent.
As for changing file properties, I didn't change any properties to do the edit other than making /system "RW" in order to be able to edit the file. Could someone tell me what the default values are for build.prop? The most recent edit I've made always shows up correctly when I go back into build.prop, by the way, so I know I'm actually changing the file.
If a rooted stock 4.1.2 can't hide the NavBar with a build.prop edit then this is the first I've read about it, and I've read just about everything that I can find on this subject (including translations of non-English discussions, just in case I could get a new lead from them). Not saying that's not true, just not consistent with what I've read so far.
I'd love to install a CM ROM on my XT926. I've admired Cyanogenmod since I first started fiddling with my Nook Color some years ago. Their crew does some spectacular work. But -- no camera? No Bluetooth? Sometimes wifi or phone call problems? That's too much lost functionality for me. If those remaining few obstacles are someday overcome I'll be all over it though.
ONE LAST QUESTION -- I assumed that, if I "scrubbed" my phone down to the lowest level possible (wipe cache, wipe dalvic, wipe data) I would eliminate whatever weird impediment I have to getting the build.prop edit to work. Is there something else I can do to wipe the phone even MORE thoroughly?
The permissions are RW-R-R, I have had the issue with stock and custom roms (running Foot Through the Floor right now). I wasn't surprised when it didn't work with stock (silly Moto) and I was a little surprised when it didn't work with and of the custom roms I tried, I have no doubt it would work in CM.
I tried it out, it works but you need to reboot after edit, I hot booted and nothing changed, full reboot and it works. hope it helps you.
Just in case this makes the difference, can you tell me what distinguishes a "hot boot" from a "full reboot"?
Having issues myself. Have 4.1.2 rooted, RAZR HD. Added the line above to build . prop with "=0" first shutdown, started back up. Then changed to "=1" saved, shutdown and started back up. System UI FC's.
Wonder if it matters what launcher is being used. I am on GO Launcher. I say this since on home screen I see the GO Launcher menu show up just below bottom of my wallpaper but behind it. I can swipe up to bring up full menu but it is weird how it comes up in background on its own.
Anyone get it to work with GO Launcher?
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 10:56 AM ---------- Previous post was at 10:54 AM ----------
Oh and does it matter where in build.prop the line goes? I just added to bottom. Thx.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 11:29 AM ---------- Previous post was at 10:56 AM ----------
lesdense said:
Yes, the edit is entered correctly. I've checked that more times than you can imagine. And I've tried nearly every variation that's been suggested anywhere: with spaces before and after the "=", adding the line ending with "0" first then rebooting then changing the end to "1" then rebooting, putting an empty line at the end of build.prop before adding the edit. No change. Is there any history of an app interfering with this edit? I don't have anything exotic installed I don't think but I use a third party launcher (Go Launcher EX) and then a variety of apps, mostly audio/video, social media and a few basic games. I believe that changes to build.prop take place "below" that kind of activity, though, right? And besides, I made the edit before I installed any of that stuff. I may try a hard reset or something like that but if this works for everyone else then I must just be missing something.
Click to expand...
Click to collapse
I just noticed this (missed it first scan through) that you use Go Launcher as well. I do also and am having same issue. I am going to try switching to Apex, Nova or other to see if that is the culprit. If so, I can most likely get used to another custom launcher to gain the extra space.
BUT if anyone doesn't have issues AND is using Go Launcher, please let us know so we can rule that out.
Thanks
I use nova pro and have the issues.
Sent from a non-apple device.
coolloser said:
I use nova pro and have the issues.
Sent from a non-apple device.
Click to expand...
Click to collapse
I just tried Apex Launcher and had same FC issue. So guess it isn't specific to any of the launchers (was a long shot anyway). This is just really weird. Some folks swear they have it running on stock 4.1.2 (OTA update) rooted, but many of us have the same and can't get it to work.
I saw one thread where someone mentioned you needed to make sure everything is stock, meaning using TB to unfreeze anything you had frozen, and then give it a go. Problem is I'll want to refreeze much of that bloatware from VZW so not sure if that helps or not.
So frustrating......
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
lesdense said:
At this stage in the trail and error I wonder what other variables could be the key. It's not the version (4.1.2). It's not launcher (problems with Go, Apex and Nova plus the stock launcher). Making everything stock didn't help me -- I flashed a brand new version of 4.1.2, installed ONLY Button Savior (for navigation) and Root Explorer (to edit build.prop). Same problems as usual. I assume it's not the rooting utility as I believe only one exists.
OK, how about some weirder ideas. Has everyone done the build.prop edit with Root Explorer? Maybe there's a flaw in that tool. I just tried editing the build.prop to put IN the qemu.hw.mainkeys=1 line, then temporarily suspended root with VooDoo, then rebooted to see if it would behave if it thought it wasn't rooted. Same result. Maybe the guy saying you can't make this work on rooted stock ROMs was right Still, I'll keep looking, and sharing.
Click to expand...
Click to collapse
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
PantsDownJedi said:
Root Explorer is what I used.
For the other guy having trouble, it hasn't been mentioned yet; did you set the owner and group for the file to root? If the file was ever stored on the sdcard or pushed there then moved, those permissions might make a difference as well. Its a good security measure in the case that it isn't relevant in any case... don't want a wild website writing to your build.prop file, for example.
Click to expand...
Click to collapse
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.
surfmly said:
I used ES File Explorer (and then you have to use Root Explorer menu option to set r/w prior to opening build.prop).
Regarding the rest of the post above. Not sure what the question is. I never did anything to the build.prop file other than set ES File Explorer to r/w on everything, then edited the build.prop file, saved, checked to ensure it was edited right, then rebooted. So the 'file' has never been anywhere other than in /system. When I check the properties on the build.prop file I see rw- r-- r-- (this the same whether or not /system is set to RW or just RO). I believe these are correct (default) settings, but let me know if that is not correct.
Anyone out there that has this working on Stock 4.1.2 it would be nice to know more (i.e. is 4.1.2 the OTA or leaked version, did they use motochopper root method (only one I thought), persmissions on file, where did they place the qemu line in the file, etc, etc).
---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------
BTW... anyone look into testing the framework-res.apk option? Sounds in-depth and much more work (not to mention chance of screwing things up). It would be new to me to decompile, etc, etc, but am not scared to try, just thought I would ask if anyone else already has. Also, not sure if that option is for the 4.1.2 OTA version (verizon in my case).
Thanks.
Click to expand...
Click to collapse
I was kind of just pulling at straws, and trying to answer two posts at the same time, sorry for the confusion. My habit, especially before unlocking the bootloader, is to push things to the sdcard then moving them and setting the right permissions and assingining the correct group and user.
As you've explained things, I don't know why it shouldn't work. Mine is a 4.1.2 OTA. It was originally rooted before upgrading and using Voodoo root keeper but between that and Supersu paid version I was able to reinsert root again after a factory reset, which was a stroke of luck as others lost it. I don't think it would matter which root method is used but I could be wrong; esentially its just allowing us to access the build.prop file to edit at all. I don't remember if I had modified the build.prop before or after the reset. I know that it was working both before and after I unlocked the bootloader though. As for the placement of the line, I put it at the end. I also, out of habit, hit enter for a new line for this type of thing. Afterwards, though, there is now new things that Pimp My Rom has inserted (Some of the tweaks in that package are old and I'd advise people to stick with close to stock as possible when using it unless they know what those lines mean; and there's some build.prop myths still floating around XDA that are not good ones, one of which I know Pimp My Rom uses and looks pretty apealing to select). So, now I have some stuff after it. If there were other things added to your build.prop, then perhaps moving the line to the end of where the default configuration ended... grabbing at straws again with this last sentance but in the lack of information I'm just trying to be helpful
Perhaps if people also with this problem, in addition to answering your question about the root method they used, also posted which carrier branding they had it might reveal something, or rule it out. <-Put that in bold for you
I am VZW with Nova Pro, and I get the systemUI FC as well. After much research, I haven't heard of too many people with PHONES that have been successful in this hack, so I tried it on my GTab 2, and same thing.
After spending entirely too much time looking into this, I purchased Full!Screen+, set the apps that I wanted full screen, and I'm set (oddly enough, this didn't work on my GTab, so I also purchased Hide Bar for that device. I prefer FullScreen+ because the truth is, there's only certain apps that I care about being full screen (Netflix, games, youtube...).
The biggest problem with FS+ is that it hides the notifications. Honestly, I don't really care about that either when I'm doing one of these other activities. After all, we have a notification light.
Related
Just curious if anyone is willing to tackle this little gagdet. It needs some fine tuning and possibly a voodoo sound app would be awesome. It lacks the loudness like most android phones.
It looks interesting, but I would not personally buy it. It does not have enough features for me to use it over my phone.
Sent from my XT862 using XDA App
Well I purchased one and with the help of the other thread about the apk i was able to sync to my epic with all features including the calls/missed calls and acuweather. This was with the corded headset. I have no real reason to get the wireless. The only real problem that i have right now is the sound level of the player. Its very frustrating to have to use a program to up the db level in every song i put on it. It running some kind of android platform so someone has to have some ideas.
Well, it looks like someone has listened... I didn't see a thread anywhere else, so I'll post it here, some one has rooted the motoactv. the story, along with a link to a how to is available, just google it. I was gonna post a link, but I can't.
The Motoactv runs gingerbread. CWM has gained root on it and installed Google apps. It has a decent chip and ram for a small device. The bootloader isn't locked. More and more smart watches and wearable computers will be coming out. I'd like to see a custom launcher for this size screen as QCIF+ ain't exactly great for a lot of launchers. A custom rom that remapped the hardware buttons would be nice as well.
Cheers,
-M
XDA member since 2007
Hi People
I just rooted the MotoACTV with the tutorial provided by Wade, the guy that rooted the watch. But I am having problems installing the ggole apps on it. The guide does not explain very well how to install the gogle apps. I managed to install several apk via adb commands and they work ok. But I am missing the market and every default google ape. Can someone explain how to do this? I already downloaded google apps zip file from cynogen web page.
rdavidowski said:
Hi People
I just rooted the MotoACTV with the tutorial provided by Wade, the guy that rooted the watch. But I am having problems installing the ggole apps on it. The guide does not explain very well how to install the gogle apps. I managed to install several apk via adb commands and they work ok. But I am missing the market and every default google ape. Can someone explain how to do this? I already downloaded google apps zip file from cynogen web page.
Click to expand...
Click to collapse
There are libraries in the unzipped file that need to be installed with the adb push command to get maps to work. The market needs a bunch of crap to work. You should push all the apk (except car home if you don't want it) once you have those over, restart and you download the rest of the apps from market.
Cheers,
-M
XDA member since 2007
This sounds intriguing can you run RunKeeper on the rooted device. I have the motoactv and love it for running but RunKeeper in my opinion is the best running app. Im anxious to hear more about this.
Thanks Dragon, but one more question before I keep trying this market stuff. Do I do the adb push command to the same exact directories as the zip has. Like for example: the zip file that I downloaded was for CM7 and it includes a lot more directories than simply the app directory. Do I have to push every single directory the zip has and create the ones that are missing within the watch. Can you please explain more in detail if possible. Thanks again for the help as this is the only thing I am missing from this "the market".
rdavidowski said:
Do I have to push every single directory the zip has and create the ones that are missing within the watch. Can you please explain more in detail if possible. Thanks again for the help as this is the only thing I am missing from this "the market".
Click to expand...
Click to collapse
So, once unzipped you will see "META-INF" and "system" folders.
Inside "system" you will see:
app
etc
framework
lib
inside "app" you will see:
*CarHomeGoogle.apk
*FOTAKill.apk
GenieWidget.apk
Google Maps 5.12.0.apk
GoogleBackupTransport.apk
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
GoogleFeedback.apk
GooglePartnerSetup.apk
GoogleQuickSearchBox.apk
GoogleServicesFramework.apk
*LatinImeTutorial.apk
MarketUpdater.apk
MediaUploader.apk
NetworkLocation.apk
OneTimeInitializer.apk
*Talk.apk
Vending.apk
(*not really needed on MotoACTV but won't hurt to install)
I am doing this from a Mac using terminal, it has been a richard year since I have used CLI with windows but for Linux the commands will be the same ("dragon$" is just my terminal prompt).
dragon$ adb push ~/Desktop/gapps/system/app/Vending.apk /system/app
dragon$ adb push ~/Desktop/gapps/system/etc/permissions/features.xml /system/etc/permissions/
So, you see I have pushed the files to the corresponding directories that the files are found in the unzipped folders.
I cannot remember if adb push defaults to parent owner and permissions but if not you will have to change them to root/root and RW-R--R--
I followed CMW's guide to root mine, too.
dragon_76 said:
I'd like to see a custom launcher for this size screen as QCIF+ ain't exactly great for a lot of launchers. A custom rom that remapped the hardware buttons would be nice as well.
Click to expand...
Click to collapse
A full custom would be great (but not needed for remapping hardware keys); Motorola's UI is really quite nice for the screen size, but won't show custom apps. Instead of the fake Honeycomb one, I prefer to use Zeam (with the launcher and grid set to 3x3 icons) -- I just think it works much better, without overlapping icons and so on.
To get a shortcut to the wifi access point settings in zeam, press and hold in a blank area, and go to "add", then "shortcuts", then "settings", then "settings" again. This "settings" is the hidden wifi one.
I also remapped "Start" to menu fairly easily by modifying they G2-keypad.kl file under keylayout; nosit1 was able to do the same with music to home. The people in #motoactv on freenode.net are very helpful, including CMW.
More information on that:
/system/usr/keylayout/G2-keypad.kl
Change this line:
key 220 FITNESS WAKE_DROPPED
to this:
key 220 MENU WAKE_DROPPED
On a separate note, you'll want to backup your userdata partition, too. Otherwise, it can get corrupted and make the file loop at the motorola logo:
dd if=/dev/block/userdata of=/sdcard/userdata.img bs=1024
adb pull /sdcard/userdata.img userdata.img
Even when restoring that, there are a ton of force closes from com.motorola.gault.activity; you have to get past them to a custom launcher to factory reset.
@dragon_76
Does anything need to be done with the META_INF folder? I'm attempting to get Market working on my Motoactv but I'm still getting a Google Services Framework force close. I pushed over the gapps from CM6 (the ones under HDPI). Not sure if those were the right ones.
I think I need to factory reset and start over from the beginning. :/
MinionOfEckerd said:
@dragon_76
Does anything need to be done with the META_INF folder? I'm attempting to get Market working on my Motoactv but I'm still getting a Google Services Framework force close. I pushed over the gapps from CM6 (the ones under HDPI). Not sure if those were the right ones.
I think I need to factory reset and start over from the beginning. :/
Click to expand...
Click to collapse
No, that folder is for recovery mode installers.
Amazon app store works perfectly if you can't get Market to work. It takes a fair amount of trial and error with apps to find ones that are functional.
I can't recommend enough installing grafitti pro. I have it from Amazon FAOTD.
I have superuser.apk installed and I had to push my preferences from /data/data/ on my phone to my watch so as to autorespond "yes" to root requests and no notifications because the UI is a fixed size window.
After doing that I installed button saviour and my purchased key for the pro features to have only home and menu onscreen. (Button saviour needs root permission).
I use golauncher ex with 3x3 home screen and the notification bar hidden. I wish I could remove the dock but oh well.
Android is going into more types of devices, I wish Google would push scalable graphics. I am however very impressed with the amount of apps that work usably on a QCIF+ screen (Netflix!)
I also like the main launcher and if I could access an app like AltDrawer from it I would not have another home replacement installed. I will tear apart Launcher2.apk soon and see if there is a way to customize it.
Sent from my MB860 using xda premium
Okay so last night I attempted to root my motoactv but my adb for some reason say it cannot load the root.img, I had the same problem where it's couldn't load the recovery.img for my photon when attempting to apply CWM or twerp recovery. Fastboot devices definitely sees both my devices (no I didn't do them are same time, and the files needed are in the same file location as instructed) and I can even Fastboot reboot and have that work. Any ideas or suggestions?? Any help would be appreciated.
moonzbabysh said:
Okay so last night I attempted to root my motoactv but my adb for some reason say it cannot load the root.img, I had the same problem where it's couldn't load the recovery.img for my photon when attempting to apply CWM or twerp recovery. Fastboot devices definitely sees both my devices (no I didn't do them are same time, and the files needed are in the same file location as instructed) and I can even Fastboot reboot and have that work. Any ideas or suggestions?? Any help would be appreciated.
Click to expand...
Click to collapse
Try downloading a new root image. Also try switching USB ports.
Sent from my MB860 using xda premium
dragon_76 said:
No, that folder is for recovery mode installers.
I have superuser.apk installed and I had to push my preferences from /data/data/ on my phone to my watch so as to autorespond "yes" to root requests and no notifications because the UI is a fixed size window.
After doing that I installed button saviour and my purchased key for the pro features to have only home and menu onscreen. (Button saviour needs root permission).
I use golauncher ex with 3x3 home screen and the notification bar hidden. I wish I could remove the dock but oh well.
I also like the main launcher and if I could access an app like AltDrawer from it I would not have another home replacement installed. I will tear apart Launcher2.apk soon and see if there is a way to customize it.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks, wasn't sure about the META-INF folder. Going to try installing button saviour. How did you "push" preferences from your phone to the watch? I have root/su on my Xperia Play so I should have the files there to push?
Did you personally get the Google Apps working?
EDIT: Everything is forceclosing on me. :/ Installed the Stock Browser from my XP but that's forceclosing as well. Attempted to change the permissions of the applications but either it didn't work or it didn't help.
I couldn't figure out how to push preferences, but I was able to tell Superuser to allow all apps after remapping Start to Menu, then just doing Superuser > Menu > preferences. You could always do this to get Superuser working, get Button Savior working, and then revert it back.
(I made a step by step on Pastebin, but if you use Oneroot, it might do all this for you: http://pastebin.com/AZRemesV )
ldrn said:
I couldn't figure out how to push preferences, but I was able to tell Superuser to allow all apps after remapping Start to Menu, then just doing Superuser > Menu > preferences. You could always do this to get Superuser working, get Button Savior working, and then revert it back.
(I made a step by step on Pastebin, but if you use Oneroot, it might do all this for you: http://pastebin.com/AZRemesV )
Click to expand...
Click to collapse
Thanks a lot. Just did a factory reset, figure I'll start from scratch. Did you get the Google Apps working after Superuser was configured? What Browser are you using? (Dolphin was forceclosing for me every time I went to type.)
EDIT: Got Superuser working, did the keyboard hack to make Start=Menu. Anybody know what button Music is mapped to in the configuration?
Going to fiddle around some more w/ Google Apps. Anybody have a walkthrough of installing the apps? IE Which ones you must do, don't have to do and what to do to get it working.
EDIT: It was WAKEkey 378. It was set to "MEDIA" so I changed it to "HOME". Works perfectly!
Hanging at the Red Moto Logo
Followed the instructions and had it working rooted, etc. Was going to change out the launcher. And obviously did something wrong. Now it just just hangs at the Red Moto logo. Can get it to power off and can still get it to the fastboot mode. Have tried reflashing the system and userdata, wiping the user data, etc. Any suggestion on what to try next?
ts937km said:
Followed the instructions and had it working rooted, etc. Was going to change out the launcher. And obviously did something wrong. Now it just just hangs at the Red Moto logo. Can get it to power off and can still get it to the fastboot mode. Have tried reflashing the system and userdata, wiping the user data, etc. Any suggestion on what to try next?
Click to expand...
Click to collapse
Join our IRC at irc.freenode.com #motoactv
We have been working on this for a while. We are planning on working on a thread for this.
Currently I have Spotify and Sportstrack Pro running well. I'll start to compile a list of working applications.
If you're stuck in a boot loop, you'll need the userdata partition image. I'll edit my post with it once I'm on my computer.
Sent from my Galaxy Nexus using Tapatalk
I searched and could easily find stock build.props but I'm pretty sure than CM's is tweaked. Whilst messing with Android Tuner (just got the app, am more familiar with ROM Toolbox) and tapped one click optimization without thinking. Well, I've tried again and again (yes after a reboot too) to reset everything, but the build.prop just won't reset. I'm guessing for some reason it never backed up properly. Perhaps it was a mistake to kill the app when it was acting up and stuck on modifying the build.prop. Device boots fine, and works fine, but I wish to undo whatever was done. I like it the way it was with CyanogenMod originally anyhow. i don't want any unexpected surprises tweaking the build.prop. I have tweaked build.props before and actually do it with a zip to enable LTE, but no other tweaks. Like hiding notifications. So I am simply requesting an unmodified Cyanogenmod build.prop I can download and apply to my Nexus 4 to undo any unwanted changes. Preferably one from the 6/14/13 CM 10.1 Nightly (the latest one). Thanks!
MikeRL100 said:
I searched and could easily find stock build.props but I'm pretty sure than CM's is tweaked. Whilst messing with Android Tuner (just got the app, am more familiar with ROM Toolbox) and tapped one click optimization without thinking. Well, I've tried again and again (yes after a reboot too) to reset everything, but the build.prop just won't reset. I'm guessing for some reason it never backed up properly. Perhaps it was a mistake to kill the app when it was acting up and stuck on modifying the build.prop. Device boots fine, and works fine, but I wish to undo whatever was done. I like it the way it was with CyanogenMod originally anyhow. i don't want any unexpected surprises tweaking the build.prop. I have tweaked build.props before and actually do it with a zip to enable LTE, but no other tweaks. Like hiding notifications. So I am simply requesting an unmodified Cyanogenmod build.prop I can download and apply to my Nexus 4 to undo any unwanted changes. Preferably one from the 6/14/13 CM 10.1 Nightly (the latest one). Thanks!
Click to expand...
Click to collapse
Why not just download the CM zip that you would flash via recovery, unzip it, and look at the build.prop there?
kbeezie said:
Why not just download the CM zip that you would flash via recovery, unzip it, and look at the build.prop there?
Click to expand...
Click to collapse
I can do that too. Thanks. I will however upload it to Dropbox and share it here in case anyone runs into a similar issue I did. That way nobody has to download the entire thing for a single thing and add more stress to CyanogenMod's servers.
Build.prop for 6/14/13 CM 10.1 Nightly
Here. This is for future reference in case anyone else runs into the same issue.
Discovered this totally by accident, but thought I'd post it in case some one found it useful.
First I followed the method out lined by cdub50 here
This was on 7in. HDX software version 13.3.1.0.
I've copied the steps here for ease of use:
1) You need to first mount /system as RW in ES file explorer go to tools > Root Explorer and turn it on then click on Root Explorer to bing up the options menu. Select Mount R/W and mount / and /system as RW.
2) open /system/app
3) look for dtcp_apk-release-signed_62320010.apk trailing number might be different for you
4) you can either rename the file by changing .apk to .old or modify permissions and remove all permissions.
5) reboot and you will no longer get any offers on the lock screen.
6) You can change / and /system back to Read Only once you are done if you want.
After completing these steps my lockscreen no longer had ads , but no wallpapers showed either, just a blank screen with the screen lock on top. Now some users were using 3rd party unlockers ,but many of them would then need to be unlocked twice(3rd party unlocker and stock). I didn't want to go through that so I was willing to live with the black lockscreen. However, after having trouble with an app not leaving app drawer after deletion, I factory reset. After I still had root but no more blank lockscreen , now it cycles through the stock amazon wallpapers(the ones that appear the few times you unlock with out seeing an ad). I've counted 10 or 11 of them.
So my additional step is:
7)Settings>Device> Reset to Default
EDIT: WARNING! It should go with out saying but factory reset will wipe all user installed apps, settings, etc. You still have root , but will need to reinstall superSu if you don't want to automatically give su to any app that requests it. So be prepared to reinstall everything unless you have a working back up app like titanium.
I can't promise that this will work for you just that it did for me. I have no idea why it worked , I'm just reporting my results.
Removal of ads
Great I can confirmed it worked for me. No more ads Even the offers tab got removed
Thanks for find.
I totally bricked my device by reseting to factory defaults I somehow thought that choosing this in the menu should be safe...
This works, but if you do it make sure it's right after you root. If you have anything that you've downloaded on your HDX it will go along with all of your personal settings, etc. it cleans house but does allow Amazon's still wallpapers. They are definitely better than the black screen. Thanks for the share.
johnnydowngrief said:
I totally bricked my device by reseting to factory defaults I somehow thought that choosing this in the menu should be safe...
Click to expand...
Click to collapse
I'm going to go on a limb and say factory resetting didn't brick your device. Have you been trying to get Google play to work? If factory reset bricked the device Amazon is in for a lot of returns. I'd guess something was already wrong and factory resetting triggered it perhaps?
As a previous poster pointed out factory reset will reset all settings and delete all user installed apps. I'll update OP to make this clear. It wasn't a big deal for me bc , I got my HDX at 9 last night was rooted by 930. So when I factory reset I only had to reinstall superSU, es file, and maybe 1 or 2 other things. I can definitely see this not being worth it for those who have had their kindle's for a while and have many apps. Although I don't see why titanium backup wouldn't be an option. Can any one confirm it works on HDX?
mysongranhills said:
I'm going to go on a limb and say factory resetting didn't brick your device. Have you been trying to get Google play to work? If factory reset bricked the device Amazon is in for a lot of returns. I'd guess something was already wrong and factory resetting triggered it perhaps?
As a previous poster pointed out factory reset will reset all settings and delete all user installed apps. I'll update OP to make this clear. It wasn't a big deal for me bc , I got my HDX at 9 last night was rooted by 930. So when I factory reset I only had to reinstall superSU, es file, and maybe 1 or 2 other things. I can definitely see this not being worth it for those who have had their kindle's for a while and have many apps. Although I don't see why titanium backup wouldn't be an option. Can any one confirm it works on HDX?
Click to expand...
Click to collapse
Yes. I don't blame you for anything. Just saying it can happen. Yes I tried to install google play. I unistalled everything (google play services, framework etc) and only had root and used custom launcher. I live in the Czech republic. Is there any way to contact amazon without having to send the device back to the US? Does anyone know? Thanks.
---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------
Edit : I probably know why it happened. I rememeber renaming the file that usually handles ota updates to keep my root. So factory reset probably just deleted everything but did not have anything to back up from. Just a thought. Sorry for spamming. But if this is true, we can use it as a cautionary tale of sort.
Honestly? I don't know. In my experience Amazon customer service is amazing. They tend to bend over backward for you. I once got a 60' plasma that was 1600 new from amazon warehouse for 1250 it arrived with plastic still covering screen(so much for used and was missing the remote. One 5 min phone call and I was credited 50$. For a 20$ Remote. Contact them and see what they can do for you. Hope it works out for you.
I will also add my 2cents that when I was working on getting google play , I deleted all the apps required but even though I deleted Vending,apk from system/app and data/app the icon changed in app drawer to a "?" and could not be run ,but I could not get rid of the left over icon (thus the factory reset I mentioned in OP)
I'm never more then 10ft from my S4, so I'll just deal with my google stuff on there for now. Until we have unlocked bootloader and method for recovery I'm not gonna risk fooling with google services.
Edit : I probably know why it happened. I remember renaming the file that usually handles ota updates to keep my root. So factory reset probably just deleted everything but did not have anything to back up from. Just a thought. Sorry for spamming. But if this is true, we can use it as a cautionary tale of sort.
Click to expand...
Click to collapse
I don't think that is it b/c I did the exact same thing. But good luck.
mysongranhills said:
Discovered this totally by accident, but thought I'd post it in case some one found it useful.
First I followed the method out lined by cdub50 here
I've copied the steps here for ease of use:
1) You need to first mount /system as RW in ES file explorer go to tools > Root Explorer and turn it on then click on Root Explorer to bing up the options menu. Select Mount R/W and mount / and /system as RW.
2) open /system/app
3) look for dtcp_apk-release-signed_62320010.apk trailing number might be different for you
4) you can either rename the file by changing .apk to .old or modify permissions and remove all permissions.
5) reboot and you will no longer get any offers on the lock screen.
6) You can change / and /system back to Read Only once you are done if you want.
After completing these steps my lockscreen no longer had ads , but no wallpapers showed either, just a blank screen with the screen lock on top. Now some users were using 3rd party unlockers ,but many of them would then need to be unlocked twice(3rd party unlocker and stock). I didn't want to go through that so I was willing to live with the black lockscreen. However, after having trouble with an app not leaving app drawer after deletion, I factory reset. After I still had root but no more blank lockscreen , now it cycles through the stock amazon wallpapers(the ones that appear the few times you unlock with out seeing an ad). I've counted 10 or 11 of them.
So my additional step is:
7)Settings>Device> Reset to Default
EDIT: WARNING! It should go with out saying but factory reset will wipe all user installed apps, settings, etc. You still have root , but will need to reinstall superSu if you don't want to automatically give su to any app that requests it. So be prepared to reinstall everything unless you have a working back up app like titanium.
I can't promise that this will work for you just that it did for me. I have no idea why it worked , I'm just reporting my results.
Click to expand...
Click to collapse
What device do you have? We share 2 diff devices in this forum. Please tell the version with such posts. It makes things much clearer. johnnydowngrief I hope Amazon works it out with you.
Faznx92 said:
What device do you have? We share 2 diff devices in this forum. Please tell the version with such posts. It makes things much clearer. johnnydowngrief I hope Amazon works it out with you.
Click to expand...
Click to collapse
I have the 7in. Your absolutely right slipped my mind. I'll update OP to note that. If anyone gets it to work on 8.9 please post. I'll also note software version as well. I know most everyone is on 13.3.1.0 but I'm sure that will change with future updates.
I wrote amazon an email. So wish me luck. I may just have to wait until we have unlocked bootloader and a method to unbrick with fastboot cable. I paid too much for postage and VAT (stupid EU ) to satisfy with a refund. The best option for me would be a replacement with the postage covered by Amazon, but I am not that optimistic.
Edit : I just talked to amazon support. They are going to send me a replacement to the Czech republic and even cover the postage. Way to go.
johnnydowngrief said:
Edit : I just talked to amazon support. They are going to send me a replacement to the Czech republic and even cover the postage. Way to go.
Click to expand...
Click to collapse
Awesome. Glad to hear Amazon customer service is as good as ever.
I changed the file name also before doing the factory reset. However, I had not attempted to install Google Play. I have the new kindle. I just had to re-install all my apps.
Sent from my KFTT using Tapatalk 2
Sorry for OT. Now they are telling me they can't cover the postage, which means 100 dollars just for the postage and another 50 dollars for the possibility of paying another VAT. I guess i will have to wait for an un-brick method..As of now i can get to the stock recovery, but ADB is not recognized.
it must have some other way to do it , your way is too risky, may brick my hdx.
Just wondering, but if wallpapers appeared on the lock screen after the restart, I shouldn't need to do a factory reset, right? I'm just wondering if a reset would be optimal, or if I'm fine.
StAlfonzo said:
Just wondering, but if wallpapers appeared on the lock screen after the restart, I shouldn't need to do a factory reset, right? I'm just wondering if a reset would be optimal, or if I'm fine.
Click to expand...
Click to collapse
When I first rooted it, I saw a regular wallpaper one time. After that, it was a black screen without fail. I know that you probably don't want to factory reset, but trust me when I tell you that it works seamlessly once it's reset. Yeah, it's a pain installing everything again. But it's worth it to have saved $15.
Take that, Amazon!
Just chat with the customer support, ask him to remove the "special offer" if you are in the country(such as China) where you can NOT use this "special offer".
Heliotrope65 said:
When I first rooted it, I saw a regular wallpaper one time. After that, it was a black screen without fail. I know that you probably don't want to factory reset, but trust me when I tell you that it works seamlessly once it's reset. Yeah, it's a pain installing everything again. But it's worth it to have saved $15.
Take that, Amazon!
Click to expand...
Click to collapse
Yeah, you're right. It went black after the first one. Luckily I only received my kindle last night, so there wasn't much to reinstall after the reset.
my new note 4 N910H lags too much
I only rooted the phone. then to make sure I flashed the latest official rom. but it's lagging.
for example in browsing or facebook when I scroll it pauses for a moment then scrolls. it's like a temporary freezing
is there a way to fix it?
found a solution: @quantumtraveler
Open root explorer file manager and navigate to /system. Set it to read/write. Open a file called build.prop with text editor. Find (at the bottom usually) a line that reads: ro.securestorage.support=true. Change "true" to "false" (without quote marks.
Save build.prop and reboot your device
If you use xposed, go to the xposed installer and install the framework again. reboot.
Sounds like your internet is to blame. It's not loading the page fast enough. It's done it on all of my phones.
omid_freesky said:
my new note 4 N910H lags too much
I only rooted the phone. then to make sure I flashed the latest official rom. but it's lagging.
for example in browsing or facebook when I scroll it pauses for a moment then scrolls. it's like a temporary freezing
is there a way to fix it?
found a solution: @quantumtraveler
Open root explorer file manager and navigate to /system. Set it to read/write. Open a file called build.prop with text editor. Find (at the bottom usually) a line that reads: ro.securestorage.support=true. Change "true" to "false" (without quote marks.
Save build.prop and reboot your device
If you use xposed, go to the xposed installer and install the framework again. reboot.
Click to expand...
Click to collapse
How long have you had your device? Mine was lagging the first couple of days, I was pissed off but too lazy to do anything, just thought I'd fix it later when I installed a custom ROM
After a few days the lag just stopped by itself... No idea what happened but I'm happy.
equlizer said:
Sounds like your internet is to blame. It's not loading the page fast enough. It's done it on all of my phones.
Click to expand...
Click to collapse
it wasn't the internet load problem, and fyi I have a very fast internet.
as I explained I found the solution and the lag is gone.
I also cleared data of S health as suggested
any ways my phone is as smooth as it can be.
the phone was lagging the first day I bought it.
After you installed xposed, which you forgot to mention. Glad it's working out for ya.
Sent from my SM-N910P
Yea I'm not rooted but mine was laggy at first and I restored it and it's much better
As ive learned on many previous Samsung phones, always factory reset the phone after you've done initial setup, preferably flash stock rom in odin and then factory reset
Hello to everyone,
as promised in my old thread, here is a first version of the automatic script to replace the launcher.
For now, firelauncher will be replaced with cyanogenmod's trebuchet.
If you want to use a different launcher, just replace the apk in the folder. (Remember to rename your new file to trebuchet.apk.)
No root is required for this to work.
This will not work with regular updates to 5.1.1!
Only for those who kept the old bootloader.
I will update the script to work with 5.1.1 later today
Remember to enable usb-debugging before running the script and make sure your PC is authorized.
There are automatic delays in the script, but check the necessary points when asked to do so, because boot-time can be really long sometimes.
As no one complained about the original script, I do believe that the basic steps are working properly.
However: I'm not responsible if anything goes wrong, please keep that in mind.
Credits go to @csolanol for finding root, @Awesomeslayerg for summing up the manual steps (If you don't like scripts, just take a look at his thread, it's good too), and to all those other people that were involved in working on boot.img and root.
Trebuchet is a cyanogenmod app, please refer to their website and xda-posts for further information.
Changelog:
V1.1:
Added some automatic delays and reduced the "pause"-commands, runs with a little less user-interaction.
Let's sum it up as more one.click.
V1.0:
Initial release
Planned features:
Allow the user to choose between trebuchet and any other launcher he copies into a special folder.
Make it easier, more documentation, clean up
Thanks for the package could come in handy for me with my daughters fire I did mine the longer way
Sent from my HTC One_M8 using Tapatalk
Okay good, should work for you as you already know the steps
If anything goes wrong booting the boot-firelauncher.img again and copying firelauncher.apk back in place will fix it.
But that should only be needed if connection is lost or any other unusual thing happens.
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
cryophil said:
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
Click to expand...
Click to collapse
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Vlasp said:
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
cryophil said:
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
Click to expand...
Click to collapse
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Vlasp said:
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
No problem, and good luck!
Sent from my KFFOWI using Tapatalk
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
Just to clarify, for the launcher replacement, the boot.img is used just to make the system partition r/w so that the changes can be made to replace the launcher. So the r/w mounting of the system partition will only last for that one boot, but the replacement of the launcher will be "permanent," in that it will persist after reboot. The rooting procedure uses the same method to copy the necessary su binaries to the device and set permissions.
So if you follow this procedure for replacing the launcher, it will be permanent with no need to then also root the device in order to make it permanent. Of course, you can also then root the device if you want, but you don't need to in order to replace the launcher.
Will the home button work after running this? I had read in some other threads about replacing the home screen messing up the home button.
Yes, the home button will work after using this.
Even widgets should work.
Maybe I'm missing something, but I don't see the script anywhere.
Was due to updating, you can find the new version 1.1 in the first post.
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Enviado desde mi KFFOWI mediante Tapatalk
Darkside1984 said:
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Click to expand...
Click to collapse
So you want to replace the trebuchet.apk with google now launcher and use that as your default?
If you rename your apk file to trebuchet.apk that will work.
But google now launcher is reported to be rather unstable as default one somewhere else in this forum, so it might be a better idea to install trebuchet using the script and then google now launcher from play store.
That should allow you to choose between the two and set now launcher as default one, but with a fallback to trebuchet.
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
below seems to be "USER ERROR"
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
a1yet said:
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
Click to expand...
Click to collapse
I can confirm the first issue, but it also exists if you replace the launcher manually (as I did), will look at were it comes from tomorrow.
The second one appears like you ran pm hide on the default video player and should not be related to the script.
ChrBeck said:
you ran pm hide on the default video player
Click to expand...
Click to collapse
thank you
i installed VLC after hide should it not use it as my default video player ?
or do i have to unhide the default one ?