[Q] Modifying Buil.prop for App Install - Nook Touch General

Hello there. I'm not new to the Android rooting scene but am brand new to Nook. My Nook came Wednesday night and it was rooted Thursday night. My main goal of root was to install an app (Moon+ Reader) that would give me reading statistics such as time till end of chapter and till end of book. My wifes Kindle has this feature and I want it now .
So Moon+ Reader has a min-SDK version of 8 (Android 2.2). I decompiled and built it using APKTool 1.5.2 changing the min-SDK version to 7; but the app will not install on my phone or the Nook. My next step is to modify build.prop setting 'ro.build.version.sdk=8.' Now, I've modified other parameters in build.prop, but never the sdk version. Will this have any adverse reactions for the Nook? In my mind it will be fine and if the app installs and doesn't function I can uninstall the app and restore the backup of build.prop. Am I crazy here, is there another app that keeps track of statisticts? I've tried Kindle, but it did not work.
--
Mooney

JMooney5115 said:
... the app will not install on my phone or the Nook.
Click to expand...
Click to collapse
Well, why don't you find out what the problem is?
What does your logcat say?
Changing build.prop doesn't make much sense.

I may have misrepresented myself in my OP. The problem in question here is not the install of the modified APK, rather the modifying of the build.prop and the troubles (if any) associated with changing the min-SDK. Sorry I posted a thread on this because I have moved past getting this app working.

JMooney5115 said:
I may have misrepresented myself in my OP. The problem in question here is not the install of the modified APK, rather the modifying of the build.prop and the troubles (if any) associated with changing the min-SDK. Sorry I posted a thread on this because I have moved past getting this app working.
Click to expand...
Click to collapse
I just tried changing the minsdk in build.prop on my HTC One to try and install an 'incompatible app' and now I'm in a bootloop. Need to wait til I get home from work now to fix it.
Doh!

Android checks for incompatibilities between system version and app minimal required version.
Obviously, to make these congruent you can change either one.
The thing is, this will only have any utility if the app maker overestimated the level of API that they are using.
If an app is using Jellybean introduced API features no amount of lying is going to get that app to work.
So if you still want to play with lying about versions, do yourself a favor and modify the app, not the system.

Related

[Q] Buying apps from Android Marketplace

I've checked as well as I could in KF forum and haven't run across this problem. When I try to download select apps Google Play it tells me they aren't compaible with my device. One was Draw something and I could use an .apk I got from 4shared before they updated it so I know it works. Is there a known solution to this. I've read about changing a file in \system but as far as I can tell that dir doesn't exist. I would think KF would have to have that, I just can't get to it.
Also what exactly does the Replace Framework-res in the KFU do? Does in just replace everything if you screw it up?
I remember when I had my nook color I was able to change some txt file to make the nook appear as a another device allowing more access to apps I didn't have before. I believe Paul O'Briens rom currently does that. Not sure how its being down now but you might find something there.
Sent from my Amazon Kindle Fire using xda premium
Yeah I figured out the whole \system business and feel retarded from that. Ill try editing tomorrow and if that's too much ill just check out that mod. Thanks for the help.

qemu.hw.mainkeys=1 works for everyone EXCEPT ME

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.

SnowMOD: Custom ROM for Black and White Ereaders. [STILL NEED DEVS AND BETA TESTERS]

Alright, this mod is dedicated to mariog, who helped me to not give up on this idea.
Now, on to the MOD...
This mod is a ROM that gives the NST an experience that is as-close-as-possible to legitimate Android. This mod will be flashed using the CWM for NST. There's one problem, I had a release ready, but when I tested it, well that's another story. The point is, I deleted alpha-1 in a fit of rage over it not working, so, I need more devs to help me build this, because A.) I can't dedicate my every waking hour to this. (I'm in school most of the time) B.) Because my first attempt failed even though I looked it over like a Trillion times. Obviously I'm doing something wrong.
In the future, I hope to branch this mod out to other black and white Readers, But at this point, I'm just worried about the NST.
THE MOD WILL INCLUDE:
-The best homescreen possible for the NST (Was using stock 2.1 Eclair launcher, not sure what is best. Launcher 7 looks good)
-Barnes & Noble stock reading apps
-B&N OOBE. (Modified?)
-Android Market/Gapps
-Dropbox included in install
-No bloatware (ie: phone.apk etc)
-Best NST internet browser (opera mini) installed as default browser
-"Chef's freezer" app (look it up)
-Probably more.
-I will also include a minimalistic version. (No: dropbox, browser, freezer, Gapps other than Gmail)
All I need is devs willing to devote just a little bit of their time to this project.
Note: ROM based on android 2.1, I will try to do 2.3 once CM7 support is made for the NST.
Note2: All you readers will be lucky if I get any sort of release anytime soon. Don't rush me. If you want to get this fast, then you can help me! I need beta-testers and devs anyways. No unofficial releases will be made to non beta-testers. If you want them, become a beta-tester!
Origins of SnowMOD
Original Thread: .
First betatester of course.
And I have made progress! Couldn't unzip the stock update file in Mac or Raspbian Linux. (yes I code with a R-PI) Now, I have borrowed my friends windows machine and success! But, it is slow, and not a permanent fix. How do I unzip the update in Linux or OSX? When I try in OSX the .zip file unzips to .tar.gz and THAT unzips to .zip and so on. I am using the regular OSX unarchiver. In Linux, the unarchive just fails. (Any suggestions on that? I'm good with android, but OSX is a mystery to me)
Anyway, I have most of /system/app done, and I am REALLY exited. It looks like this project isn't going to fail, but I NEED MORE DEVS!!!
Mineturtle33 said:
And I have made progress! Couldn't unzip the stock update file in Mac or Raspbian Linux. (yes I code with a R-PI) Now, I have borrowed my friends windows machine and success! But, it is slow, and not a permanent fix. How do I unzip the update in Linux or OSX? When I try in OSX the .zip file unzips to .tar.gz and THAT unzips to .zip and so on. I am using the regular OSX unarchiver. In Linux, the unarchive just fails.
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
It might be because the B&N zips are signed and that causes problems with some unzip programs. Stripping the first 0x1a3 (419) bytes off the start of the file takes the signature off and turns it into a unsigned zip that most unzip programs don't have problems with.
I can become a beta tester
Sensation / Tapatalk
I forgot to say thanks for the dedication
Don't mention it, its only fair.
Sent from my NookColor using xda app-developers app
straygecko said:
It might be because the B&N zips are signed and that causes problems with some unzip programs. Stripping the first 0x1a3 (419) bytes off the start of the file takes the signature off and turns it into a unsigned zip that most unzip programs don't have problems with.
Click to expand...
Click to collapse
Cool, what program can I use to perform this action? BTW winrar is working on windows, but I don't have permanent access to that computer.
Sent from my NookColor using xda app-developers app
Mineturtle33 said:
Cool, what program can I use to perform this action? BTW winrar is working on windows, but I don't have permanent access to that computer.
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
dd if=signed.zip of=unsigned.zip bs=419 skip=1
YES! Thank you. i will try that.
Getting to work now... Using my Raspberry Pi.
Sent from my NookColor using xda app-developers app
If you still need beta testers
Or a designer, i would like to help out!
I've decided to stick with reader only mode for a while after I accidentally triggered a wipe with the NookColor Tools application, but I'll reroot and test as well if needed when the time comes.
Mimefly: yes, I still need testers, and by designer, I'm guessing you mean dev.
Neoman: OK, I'm including NC tools unless you know of a different way to enable 3rd party apps.
Sent from my NookColor using xda app-developers app
Mineturtle33 said:
unless you know of a different way to enable 3rd party apps.
Click to expand...
Click to collapse
Code:
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db
update secure set value=1 where name='install_non_market_apps';
.q
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
Thank you Renate NST.
Now I just want to know, how many people want NookColor Tools in this?
How many people want an alternative?
Sent from my NookColor using xda app-developers app
NCT is quite useful, just also useful to know that certain options within it trigger a no confirmation reset to stock. I wasn't intending to deride it. Haven't rerooted since I realized the only tablet mode features I'd been using with any regularity were replacing the screensaver banner with an "if lost, contact" message and a persistent battery bar, with occasional use of a third party reader to download new books without connecting it to the computer
I was already aware of this issue with factory resets. That is why I am wary of including NCT in the ROM.
PROGRESS:
After getting tons of help from friends, I am pleased to announce that release #1 is coming VERY soon. Lots of help has significantly sped up the development process.
What I did:
-adb pushed my modified /system/app (Everything worked great!)
Release will include:
-Launcher7
-Amazon App Store. (No Android Market YET, sorry)
-ADB Konnect.
-Device Registrator
-Opera Mobile
What I don't have working YET:
-Bloatware still exists in /system/app (ie: Phone.apk, Messaging.apk) I don't yet know if it is safe to simply delete them. Release #2 will include a fix.
-No Chef's Freezer. (I have no excuse, sorry)
-No NookColor Tools. (3rd party apps is enabled)
-I don't think that this will be CWM flashable. It will probably be a dd .IMG file, but I am currently not sure.

{CLOSED} [TUT] 1/11/2014 HDX8.9 Working Play Store, GAPPS & PARTIAL Amz Services...

{CLOSED} [TUT] 1/11/2014 HDX8.9 Working Play Store, GAPPS & PARTIAL Amz Services...
I am no longer updating this thread. Currently, you best bet for everything working is SafeStrap, rom slot, Hashcode's Stock Fire Rom, Xposed module & the flashable gapps from Cpasjuste. I currently have a work load that precludes me from investigating anything further. Not too mention it seems other have the time & a better grasp on everything than I do. I will continue to help those stuck in bootloops or with issues as time permits. I recommend starting anew with your device, restoring the factory firmware, & then using safestrap & the other items mentioned above to get Play Store & Amazon working together.
Edited on 1/11/2014 - Added a fixed version of wget to the hdx.7z file to correct the gapps download rename issue.
READ ME FIRST OR YOUR DEVICE WILL EXPLODE, SCORCHING YOUR EYEBALLS!
If you have never modified an Android Device, if you have no idea what ADB is, how it is used & nearly every command memorized because you have been participating at xda for years or lurking for half a decade, if you do not know what the SDK, ANT, IDE or Ubuntu is, if you cannot afford to possibly throw away $300 to $600, then do yourself a favor & leave your Kindle alone. This is not a simple process, nor does it seem to work the same for everyone. I am NOT a developer. I also have a family & a career, which is very time consuming. I lost over a week in vacation days this past year because I rarely have time for myself, so that should tell you about how much time I am going to have for you if you break something. Sure, I will try to help WHEN I HAVE TIME, but if you are messing with things & then sending me a one line PM saying "I brick it" without any specifics about EVERYTHING you have done, well, I am not even going to respond. So, now you know, if you still want to mess around & possibly break some stuff, go right ahead.
EDIT: It seems if some Amazon services do fail to work for most people. books work fine for me, but not most others & the Amazon App store is not working 100% either. I am working on a fix.
Okay, firstly, I have to thank @Ptiwee who was the first to really bring all of the scattered data & info together, discovering the location in the Java/Smali, where the issue in getting Play Store to function correctly resided.
You will also find a lost pf tips & fixes in post #2. I will add to it as developments arise.
This is a step by step guide for the newer member that wants to learn. I have tried to be as precise as possible & list out every step, along with a few tips on getting your Android adventure started successfully. There are no dumb questions, except for those you should have asked. So ask away & we'll try to get you an answer you'll understand.
Now, we must thank @CrashThump who took Ptiwee's solution & instead of relying on the notoriously unreliable apktool & dependecies, he took the time to recompile a fixed binary in the form of new services.odex. This is exactly what I had been looking to do, but I have been having some troubles with aapt & apktool & he just probably knows a lot more than I do. Either way, it's here now & it works.
Be sure to hit thanks to those guys, for without there help, you would still be bootlooping & cursing Amazon under your breath.
This is NOT an easy or clean way to install GAPPS package, but it works perfectly & I for one have NOT lost a single Amazon service. It is relatively low risk if you follow directions & test that things are working before jumping in head first.
Here is what you need to do to install the Play Store & GAPPS (for now), until I or another member has the time to properly compile everything into an easy to use utility. The root & signature verification parts of this tool work well. The install GAPPS script can fail occasionally, but it will not hurt anything.
This guide is for use on windows, though I will later also present a terminal command version for Linux & possibly Mac. It will be a manual version for now & I will not get to it until later. Feel free to take the data here & compile it into whatever tool or utility you want. I don't think anyone would have an issue with that, just be sure to thank everyone mentioned in this post. you can also easily open the script & just manually do everything in the script for linux. Just make sure you also grabbed the tools like SED from Ptiwee's original script tool.
For this to work, you must be rooted & have busybox installed, along with completing the steps & requirements listed below. The script from CrashDump in the HDX.7z file can root your device, as well as install gapps, fix for signature checking & the wallpaper issue. I recommend downloading everything ahead of time, including the attached busybox installer. If you are already rooted, you can skip some steps, otherwise follow the directions closely.
1. Download the Windows batch file & the necessary scripts & binary from CrashDump named hdx.7z. It can be found below in the attachments.
EDIT (1/11/2014) - Added a different version of wget to fix the download rename issue..
Download & install a BusyBox installer on your device.
2. Ensure you have the latest Java SDK installed. The JDK can be found here: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
Make certain you install the version for your operating System, i.e. 32-bit or 64-bit.
For 32-bit (x86), the JDK you want is titled: jdk-7u45-windows-i586.exe
For 64-bit (x64), the JDK you want is titled: jdk-7u45-windows-x64.exe
I recommend installing it to the default directory.
Once you have this installed, make sure to add it to you PATH in Environmental Variables.
To do this, hit the Windows button (like you are going to open an app), or launch the file explorer & RIGHT CLICK on "Computer" & select "Properties".
.Go to "Advanced System Settings" & select the "Advanced" tab.
Select the "Environmental Variables" button towards the bottom right side of the window.
In the second window, "System Variables", scroll to "Path" & select edit.
Add your systems path to the recently installed version of the Java SDK (JDK) to "Variable Value:", it should look something like this:
C:\Program Files\Java\jdk1.6.0_33\bin; (make sure yours reflects your correct version & path to the JDK Bin directory. DO NOT JUST COPY/PASTE MINE). Also take care to have a semi-colon ( both before & after your path & DO NOT ALTER ANY OF THE OTHER VALUES.
I also recommend you add these file types to the entry below, called (PATHEXT):
.BAT;.CMD;.JS;.JSE;.SH
These two steps allow you to use these tools from any directory, telling tools & applications where to find the resources they need.
After installing the Java SDK (JDK), make sure you also have a "System Variable" entry called "JAVA_HOME" with a value that is the same as your environmental variable, pointing to your Java SDK Bin directory. Mine is "C:\Program Files\Java\jdk1.6.0_33\bin" (again, you need to have YOUR installed location, not mine, so do not copy/paste from here).
3. Ensure you have installed the Android SDK. You do NOT need Eclipse, just the SDK. It can be found here: http://dl.google.com/android/installer_r22.3-windows.exe
Install the SDK somewhere simple & avoid spaces in directory names. My SDK (when I bother to use Windows anymore, is C:/Android/
I use Eclipse, so for me, my directury tree is "C:/Android/sdk & C:/Android/eclipse" this is where all the important Android tools live, like ADP & AAPT & Fastboot, in /sdk/tools & /sdk/platform-tools.
4. The script & utilities used by CrashDump need several Linux based tools, like SED & a few others. Fortunately, the GnuWin32 package exists & can be downloaded here: http://sourceforge.net/projects/getgnuwin32/files/
This is a set of packages designed to work with Windows, It will download an executable & you will open it, paying attention to where it is downloading & extracting the packages. Once it is finished, you will go to what ever directory you selected for the "GetGnuWin32" folder & you will click on a script batch file named "download.bat. This will download all the GnuWin32 packages. Follow the instructions & let it download the updates as it goes.
Once this is complete, you will then go back into your "GetGnuWin32" folder. Now you will double click (execute/run) the script batch file named "install.bat".
This process takes about 15 to 30 minutes depending on your machine & your download speed.
5. Connect your device to the USB port & give it time to install the proper drivers. Next, open a cmd window & enter: adb devices
If successful, you should see your device serial number listed, similar to this:
C:\Users\gleon>adb devices
List of devices attached
B0xxxxxxxxxSH device
If your device was recognized & you see something similar to the above, congratulations, you have installed the SDK successfully & are now ready for some action. If not, you may need to install the HDX adb drivers. If you are here, you have most likely already done most of the steps above anyways.
7. Extract the file HDX.7z to somewhere simple like C:/ or in your Android SDK directory.
Double click on the "HDX.bat" script & a terminal window will open with the following data:
Only for Kindle Fire HDX 8.9
WARNING ! All the manipulations here are dangerous.
Your tablet may become unstable or unusable.
Nobody except you will be considered as responsible.
What do you wanna do ?
1. Root my Kindle Fire HDX 8.9
2. Remove Amazon ads on lockscreen and some Amazon applications
3. Remove signature check (Requisite for Google Apps)
4. Install Google Apps
5. Fix wallpaper
6. Quit
Choice :
Select option #1 if you are NOT yet rooted. Once you root, open up the Superuser app & give it a minute. Make sure it is working & then install the attached busybox installer on your device & make sure to open it & install busybox & the applets. I suggest using the "Smart Install" feature. It will take a minute or two for it to load & install busybox, but please wait & ensure it installs successfully.
To install busybox, you can transfer it to your device & use a file explorer to navigate to the apk, OR you can use your newly installed SDK & open a cmd prompt in the folder you downloaded or extracted the bb installer & issue the following command (just the part in quotes, WITHOUT the quotes of course): c:\Android> "adb install busybox.apk"
It will say "successful" once busybox is installed. Open the app & let it setup. Then click on the "install" button & let it do its thing.
Once you are rooted, have busybox & Superuser installed, or If you are already rooted with both installed, you can move to the script tool's option # 3, "Remove signature check <Requisite for Google Apps>
This is going to replace the services.odex file from your devices /system/framework directory. It will restart the SystemUI, which means it will look like it has reboot, but do not panic, it will not boot loop your device, it will resume normally in a moment.
Once it is has restarted the SystemUI & the screen comes back on, you can now use option #4 "Install Google Apps".
Congratulations, you now have an Amazon HDX 8.9 with fully functioning GAPPS, including Play Store & you have all Amazon Services working.
Take wht you have learned & pass it along. This is a forum about sharing ideas & knowledge. Pay it forward.
I know this is written fairly simply, but I do this so that nobody will misunderstand. i know many of you know what you are doing, but there are new users & members here every day. I will do whatever I can to help you if you have issues & as you have seen, I have already been able to fix 2 types of soft bricks, so your risk is much more limited than even a few weeks ago.
Fixes, Tips & Tricks
Tips & Fixes:
1. For all of your Google Play installed app to show up in the app drawer, please delete versions in the "Cloud" tab of the App Drawer. (This only applies to the Stock Amazon launcher/app drawer).
2. Currently, all apps & Amazon Service work EXCEPT Amazon App store. A work around is listed below.
3. There is a work around for the Amazon App Store crash. It will work if you remove the existing app, delete the dalvik cache & then install the generic Amazon App Store for Android from here: http://www.amazon.com/gp/mas/get/android/ref=mas_rw_ldg
You will need an app like Titanium Backup Pro, which can remove unnecessary Dalvik files. This work around functions, however, the Amz App will crash occasionally. Also be sure you are uninstalling the App Store, not the IntentProxy, which also show as Apps in TB.
4. I have not thoroughly tested this, however from short testing, it appears that Kindle Free Time does indeed work. It will launch, allow password to be set & rules & times to be selected.
5. If you have any issues & want to return to 100% stock, I will be uploading a fixed build.prop, along with a script to download & ready the latest update. This will erase all changes in the device System partition, without removing installed apps in the user land, aka /data/app.
I'm looking forward to trying this when I get home! Thank you all for you hard work!!
Does this require root?
cbtk18 said:
Does this require root?
Click to expand...
Click to collapse
Yes. Steps 1-6 is PC preparation to run step #7, for Kindle modification. You need 'option #1 - root' for any other option to work.
---------- Post added at 05:37 PM ---------- Previous post was at 05:28 PM ----------
GSLEON3 said:
Tips & Fixes:
2. Currently, all apps & Amazon Service work EXCEPT Amazon App store.
Click to expand...
Click to collapse
With Amazon App store not working, does this also include functionality of downloading of content locally in Freetime, Kindle, MP3, Video?
I've tried all known methods (except ptiwee/crashdump/yours) and I still haven't gotten a working App Store + content sync... All content requests show 'queued' indefinitely...
Thanks,
Alex
I can play, download & watch movies, music & books without issue. Only the Amazon app store has issues for me. Being one of the worst curated Android Markets around, I could care less, though I do plan on comparing it to the HD 8.9 DL manager, which functions 100% for everything.
My household all have tablets & my youngest is a teen, so no idea on Free time, but I'll check for you when I get everything back in place. I'm bricked again (on purpose & not from this, so don't worry) I'm trying to find a fix for another user with issues.
Sent from my Nexus 5 using XDA Premium HD app
Can we use the wallpaper fix? There was another thread saying wallpaper fix bricked their device (8.9). Is it ok to do here?
Amazon Appstore
will you find a way to get the amazon appstore to work
Now if only this could be ported to 7 ...great job
Sent from my KFTHWI using XDA Premium 4 mobile app
So I went ahead and applied the wallpaper fix built in this tool. It was fine. Although I did have a black screen for awhile, basically seemed dead for a couple minutes, which concerned me. Next step... how to get live wallpapers? I love this. Makes the 8.9 better than the 7" now. Functionally that is, minus the live wallpaper that is working with thor-gapps rom for the 7".
Yes no Amazon apps work at all on 7 but 1 person claims all is working on his but I don't see how with Thor gapps rom
Sent from my KFTHWI using XDA Premium 4 mobile app
davekaz said:
Now if only this could be ported to 7 ...great job
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nobody said step 7,options 2+ won't work on 7, it just hasn't been tested..... I would go back to ptiwee's original script to test, and as it modifies files from the device and doesn't rely on potentially device specific modified binaries...
Sent from my AT100 using Tapatalk 4
Thanks for a very good jobb, which give us all users of HDX 8.9 get a fantastic tablet. I do not understan what you mean with this lines, "For all of your Google Play installed app to show up in the app drawer, please delete versions in the "Cloud" tab of the App Drawer."? Where do I find "Cloud Tab?"
I use Nova launcher so mabe it´s not for me?
Thanks
lasset said:
Thanks for a very good jobb, which give us all users of HDX 8.9 get a fantastic tablet. I do not understan what you mean with this lines, "For all of your Google Play installed app to show up in the app drawer, please delete versions in the "Cloud" tab of the App Drawer."? Where do I find "Cloud Tab?"
I use Nova launcher so mabe it´s not for me?
Thanks
Click to expand...
Click to collapse
If you're using Nova Launcher, then you're right, you likely won't care.
GSLEON3 is pointing out for those who choose to use the stock launcher app carousel and you're wondering why play store apps aren't showing up, it's due to a conflict between the existence of the app in Amazon App Cloud and the Google Play store. To resolve this, he's recommending you remove this from Amazon App Cloud...
Ok, thanks I understand and I stay in Nova.
Thanks and A Happy New Year from Sweden!
---------- Post added at 12:31 PM ---------- Previous post was at 12:30 PM ----------
davekaz said:
Yes no Amazon apps work at all on 7 but 1 person claims all is working on his but I don't see how with Thor gapps rom
Sent from my KFTHWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Has anyone tried using the Amazon store app from the Google play store?
improvius said:
Has anyone tried using the Amazon store app from the Google play store?
Click to expand...
Click to collapse
Great Idea. This may work. I'll have a try after morning coffee.
Has anyone tested this on the 7 inch HDX?
Is there any reason why this would/should not work on this model?
Thanks!
Guys, I am about 99% sure that you do not need the GnuWin32 packages for this to work. Duh... I forgot we are using a binary, not an on the fly rebuild like Ptiwee.
I'll test & modify instructions accordingly.
Sent from my KFAPWI using XDA Premium HD app
GSLEON3 said:
Guys, I am about 99% sure that you do not need the GnuWin32 packages for this to work. Duh... I forgot we are using a binary, not an on the fly rebuild like Ptiwee.
I'll test & modify instructions accordingly.
Sent from my KFAPWI using XDA Premium HD app
Click to expand...
Click to collapse
thanks again for the all the hard work and persistence..
xda is about sharing and learning and "a man only owns what he knows"..
thanks again..great job!!
question though.. can i go ahead and try this on my kindle fire hdx 8.9 LTE 64GB?

Found way to disable undisable-able bloatware non root lolipop

First off I am running lolipop and have been working to find a way to disable bloatware that you don't want. I can't root as I'm on a att s5 lolipop...
finally found out how to get those apps that can't be disabled disabled.
Instructions:
1. Find the app that your wanting to dissable... let's say for example My Magazine.
by default in lolipop this app can't be disabled without root... frown face.. bad day...
2.Search for an apk file online for that app you want to disable.
And install it.
3. Here's what happens now... since you just updated the system app yourself, you now have permissions over it.
So to disable the app go to app manager and look under downloaded. You will notice that now the app that previously could not be disabled... now can be. You also have the option to Uninstaller the update... update only unfortunately but oh well.
Now you have just succusfully disabled My Magazine or what ever other system app that can't be disabled.
If you need any help just ask.
adam_ky said:
First off I am running lolipop and have been working to find a way to disable bloatware that you don't want. I can't root as I'm on a att s5 lolipop...
finally found out how to get those apps that can't be disabled disabled.
Instructions:
1. Find the app that your wanting to dissable... let's say for example My Magazine.
by default in lolipop this app can't be disabled without root... frown face.. bad day...
2.Search for an apk file online for that app you want to disable.
And install it.
3. Here's what happens now... since you just updated the system app yourself, you now have permissions over it.
So to disable the app go to app manager and look under downloaded. You will notice that now the app that previously could not be disabled... now can be. You also have the option to Uninstaller the update... update only unfortunately but oh well.
Now you have just succusfully disabled My Magazine or what ever other system app that can't be disabled.
If you need any help just ask.
Click to expand...
Click to collapse
Nice idea, but sometimes it may not work. Now i have no idea as to why My Magazine worked but when installing other system apps it is bound to meet a signature conflict if the apps are the same version and completely untouched by any third party. If a signature conflict appears it will be impossible to install that system app manually.
I have only seen this phenomenon on S2 and therefore i have no idea if the same principles are embedded in the S5 but just a tip if a signature conflict ever appears while trying this method.
Anyways, good find :good:
Thank u sir.
Yes oddly enough my magazine was my first attempt and didn't even check version and had success.. noW that I see this method is possible... I'll just have to find other versions of the apps I want to dissable. I haven't had any luck finding newer versions of the apk files tho
Any thing u think might work. Modifying the apk perhaps so it may possibly install as an update?
I'm just happy to have mymagazine no longer starting up and running in the background
adam_ky said:
Thank u sir.
Yes oddly enough my magazine was my first attempt and didn't even check version and had success.. noW that I see this method is possible... I'll just have to find other versions of the apps I want to dissable. I haven't had any luck finding newer versions of the apk files tho
Any thing u think might work. Modifying the apk perhaps so it may possibly install as an update?
I'm just happy to have mymagazine no longer starting up and running in the background
Click to expand...
Click to collapse
If you modify an apk file you will need to create your own signature when recompiling, android won't like two of the same apps (same package names) but with two different signatures and the modified apk file wont be installed.
So try your method as long as it goes. who knows, maybe you wont encounter a signature conflict.
As long as the app is disabled a signature conflict shouldn't matter tho right? Because the app is disabled and all?
I'll keep a look out. The version my magazine I'm showing now is 3.0.0
In app manager I have orion to uninstal the update so if something does happen I'll remove it
You seem to know a good bit maybe you can help me with something.
Is there a way I could take
expample.apk version 1.0 and edit it somehow and trick it and or android into thinking it's say version 1.1
This would allow me to install the same version over what I have now.. then perhaps be able to disable it..
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app

Categories

Resources