Related
here is situation:
1. I had rooted 1.4.2 with not blocked OTA and my NT updated to 1.4.3.
2. It is obvious that root and some apps stopped working and some of them even disappeared from the device (like WinAmp for example).
3. I rooted 1.4.3 with SDcard method and it looked like things are fine until I started to get my apps back.
4. I used FIREFOX as a main browser with 1.4.2 update and after registering at Play store on rooted 1.4.3 I read that FIREFOX is incompatible with my device!!! What the hell?
5. Also, my NT registered at Play as NEW device, not the old one as I had - so it seems my serial changed or something has changed in the build.prop or somewhere else in the identification part of device.
6. Besides, after root, i started installing apps and it seems Notification bar has some sort of glitches - it does not clear all the messages and keeps the last downloaded file in the list...
Can anyone point me how to fix incompatibility issue?
---------------
Now, second situation:
7. I reverted back to 1.4.2 with the img file from this post: http://forum.xda-developers.com/showthread.php?t=1663836
8. But the thing is that I want to try 1.4.3 again
9. I downloaded official update from B&N and put it onto the SDCard
10. It boots and progress bar starts to move but at some point (25% of bar) it shows me exclamation icon with '!' and says "Please restart your device and try again..."
What is this issue and how it can be fixed?
Thanks in advance.
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
titanshadow said:
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
Click to expand...
Click to collapse
Can you share the links or files that get your nook back to normal state?
I've been reading and reading a lot the forum but still miss something important. Step-by-step guide would be much appreciated, if possible.
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Nook Color
Eustace2 said:
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Click to expand...
Click to collapse
This was actually a fix for Nook Color... to modify the build.prop. If you copy/pasted the entire build.prop I would think it would work.
One other thing to do is
1.) manage google play
2.) clear data
3.) uninstall updates
4.) manage google market
5.) clear data
6.) manage google services framework
7.) clear data
8.) reboot
This didn't always work and I had to do this a couple time. Not sure if which step made a difference or what order but it eventually worked. And I could see as many apps as my Captivate (Galaxy I).
Anyway, again, this worked for Nook COLOR and not Tablet. Or at least I havent figured Table yet. If you figure it out. Let me know.
My recent attempt was to copy the build.prop from Nexus and I got black screen after start up. Now I had to unbrick my device and I'm back to square one.
Good luck.. Keep me posted!!!!
@rtabasco - Good plan, but it didn't work. Even when I uninstalled the update and just used the Market app. Looks like 1.4.3 may have changed something other than the build.prop file. I'll keep poking around. It would help if the Play Store would provide a little more detail about the compatibility issue.
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
PepeladZ said:
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
Click to expand...
Click to collapse
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
Click to expand...
Click to collapse
I am set at 160 dpi and that didn't help.
old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ?. The market is your friend.
Click to expand...
Click to collapse
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
PepeladZ said:
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
Click to expand...
Click to collapse
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Eustace2 said:
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Click to expand...
Click to collapse
Thanks for explanation. I looked in build.prop from CW7 and DPI there is set to 160. I will try and report if this solved at least firefox problem.
old_fart said:
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
Click to expand...
Click to collapse
Thank you for video, but I was not asking how to edit text document, but rather what this change will give me.
Well, BNs build.prop has separate settings for X and Y dimensions. Following the logic, it does not matter if DPI is set via one command or via two... Anyway, simply changing to 160 DPI and rebooting did not help me with firefox compatibility in play store as well as other apps that were noted to show incompatible.
Any other suggestions and ideas would be very much welcome!
Hi all,
I've sort of bricked my new razr this morining after a reboot...
after reading the thread about trebuchet, I saw that it is adviced to put it in the system folder of the ROM. I then did the same with my current launcher to improve the speed of it (I don't know at all if this is a good solution but I wanted to test anyway).
Problem now is that my launcher force close at phone boot with a basic message saying that the launcher has stopped and a single 'ok' button. when I press 'ok' the same message appear again after a few milli seconds and does not allow me to launch any task.
Then I guess that the only solution for me is to re-upload my ROM (Motorola Razr latest OTA) and that this will suppress my launcher in the system folder but I wanted to share this experience because maybe someone could know a good solution.
Thanks for your help!
Can you go into system settings before boot and just change the launcher? Possible like this
go home, menu, settings, applications, manage applications, running, scroll down to find ADW launcher, open, scroll down and click clear defaults. then when you go home, it should give you a choice to pick your desired launcher. Be sure to check the box on the bottom of the choice box to set your default launcher to your desired choice.
Actually, the launcher started to crash before the system gave me the hand and allowed me to do anything. No way to perform any action with the phone (not any action, nothing was possible under the ROM itself)
Then I finally found some time to get my computer and re-upload the official ICS OTA ROM of the Razr. It had done basically 2 things (and one was the one I was expecting or hoping): lose the root (obviously) and lose the settings of the 2 apps I putted under the phone /system folder.
After that I removed the 2 apps that were installed on /system and changed my default launcher to stay safe :fingers-crossed: (done today, that's why I came back to the thread now)
Everything is ok now.
BTW, I discovered that in the worst case, it is possible to do a full wipe / factory reset under the official / native Razr recovery, and even better, it is possible to install a ROM under this recovery.
Everything is under control at the end.
Thanks for your answer!
I couldn't leave well enough alone. I am in Europe, using a Verizon Motorola Droid, which was working (although at each boot would say 'unknown SIM - press ok, then it worked). I rooted the phone, installed Titanium, backed everything up and then started playing. I froze a load of bloatware - everything fine. I then downloaded Greenify and hibernated apps I didn't use. It was great. I should have stopped. I didn't. I downloaded Xposed framework, and then the Gravitybox module. Whoops. My phone took on a life of its own. First, my 'phone' (dialler) and 'people' (contacts) icons said 'app isn't installed' when they were clicked. I restored my Titanium backup. No change. I unfroze all the Titantium apps. No changed. I then rebooted, and the phone and contacts icons completely disappeared, as well as my wallpapers and ringtone, to something that my phone couldn't identify. I uninstalled Gravitybox and rebooted. Now the phone no longer connects to the cell phone signal either. I'm sunk, and really need some idea of what to do. Please.......Is there any way of just getting this phone back to some kind of workable order?
Try re-flashing the gapps for your android version. I think Android 4.2.2. And always remember: Make backups. Systembackups with Safestrap for example.
Einheit-101 said:
Try re-flashing the gapps for your android version. I think Android 4.2.2. And always remember: Make backups. Systembackups with Safestrap for example.
Click to expand...
Click to collapse
Thanks. I'm on 4.1.2. I have been trying to find instructions and/or a link regarding just reflashing the whole phone to the stock version, but can't find any. Would you know of one? I am a total noob (as evidenced by my thread) - so I am wondering - if I downloaded one of the other systems, like Liquid Smooth or whatever, does that also flash the phone where all the system files are new, or does it build upon the kernel which I appear to have screwed up??
Google should find a flashable Gapps.zip file. If nothing works, look into the firmwares super thread for stock roms or install cyanogenmod.
My mystery is somewhat solved - the upshot being don't leave a rooted phone around a young fella who is just starting to play with computers, as my son has been 'uninstalling' various files on my phone - the effect of which, of course, didn't come into effect until I rebooted, having downloaded Gravity Box. I have been able to find and restore 'People' and 'Phone' through my Titanium back-up. However, my phone is still not seeing my sim - another file that has been uninstalled, I imagine. I would hope that perhaps someone knows the name of the file that allows the phone to see the sim, rather than me having to uninstall all the files. My son says he only uninstalled about 5 files, but does not remember the names. Not a developer in the making!
I also have the problem with the recovery menu, where I cannot boot into it. Would an uninstalled file cause this? I downloaded Clockworkmod recovery, only to be then told that it does not support the Motorola Razr 'Spyder'. Are there any other options? And is the XT912 considered the 'Razr Spyder or is it one of the Droid options?? Thanks for any help you can give.
Hey guys, I've been looking for one ROM that has both the Amazon infrastructure with the ability to have the Google play store without having to reflash. Are there any known ROMs that have basically the stock OS with play store integration?
This is mainly a few step question, if none exist, is there any reason why and what technical limitations are there?
If there is one, what do you recommend?
If one is not yet out, but is in development are there any you'd recommend me to follow?
If there are no good answers to either of the two questions above, are there any close secondary options?
Any other information about this would be helpful too. I'm still learning how ROMs work once the Kindle is rooted.
Additional Info: I have a HDX 7"
Due to a locked bootloader, signed kernel, and the rest there are no "ROM" per se for HDX series. Just mods for the factory ROM.
To create a dual-use setup is actually quite easy:
1) Root
2) Install SuperSU
3) Install Safestrap
4) Backup stock ROM in Safestrap
5) "Restore" the backup you just did into a "ROM slot"
6) Run HDX Utility on it, which will setup everything for you, including Xposed and HDXposed and all the rest
kschang said:
Due to a locked bootloader, signed kernel, and the rest there are no "ROM" per se for HDX series. Just mods for the factory ROM.
To create a dual-use setup is actually quite easy:
1) Root
2) Install SuperSU
3) Install Safestrap
4) Backup stock ROM in Safestrap
5) "Restore" the backup you just did into a "ROM slot"
6) Run HDX Utility on it, which will setup everything for you, including Xposed and HDXposed and all the rest
Click to expand...
Click to collapse
Ok, sool, I actually already had it rooted once with safestrap and SuperSu, but I had to remove and unroot and factory reset due to some issues. I can always re-root it. I had another question, is it possible to only root the device, keep everything stock, and then just install the play store and the framework needed to support it?
But that's exactly what I described: a dual-use setup. You get both Gapps AND Amazon, together. You can even choose to run either the substitute launcher (Launcher 3 by default) or Amazon's Carousel launcher. (or both). (Xposed framework is needed to installed HDXposed, which "patches" Amazon Fire OS to make it cooperate with Gapps)
There's only one catch... You can't access the Kindle books directly from regular launcher. You have to go through the Carousel launcher.
kschang said:
But that's exactly what I described: a dual-use setup. You get both Gapps AND Amazon, together. You can even choose to run either the substitute launcher (Launcher 3 by default) or Amazon's Carousel launcher. (or both). (Xposed framework is needed to installed HDXposed, which "patches" Amazon Fire OS to make it cooperate with Gapps)
There's only one catch... You can't access the Kindle books directly from regular launcher. You have to go through the Carousel launcher.
Click to expand...
Click to collapse
Ah ok thanks. I will be looking into it. I am still figuring out the HDX and what exactly rooting does. I know it gives you increased permissions over the device but I'm not sure what effects it has on the rest. I will be reading more into it. Are there any good comprehensive guides on rooting kindles and info on it? I know how to root, but not sure the details of what is going on behind the scenes. Googling has only been marginally helpful.
Rooting lets you install Safestrap, so if you screw up the setup you won't affect the "original" boot (i.e. stock ROM), but instead, operate on "ROM Slots", which are CLONES of the original ROM, modified whichever way you like.
I have a 4th Gen Kindle HDX which is rooted (Kingroot). I tried install GAPP (minimal) the other day. I overwrote some files (stupid I know) and rebooted the system. Now there is no menubar or launcher. I can't swipe in from the sides or tap to reveal a home/back overlay. I also can't update manual or OTA. When the system boots it boots into the settings window (thankfully), so I'm able to change settings (ADB enabled, wifi) and importantly use the special offers to launch the browser from which I've installed es explorer. I really want to get my Kindle back ideally to the latest Kindle OS WITH functional Google Store. Can anyone help? ideas suggestions.
Thanks
bnbliss said:
I have a 4th Gen Kindle HDX which is rooted (Kingroot). I tried install GAPP (minimal) the other day. I overwrote some files (stupid I know) and rebooted the system. Now there is no menubar or launcher. I can't swipe in from the sides or tap to reveal a home/back overlay. I also can't update manual or OTA. When the system boots it boots into the settings window (thankfully), so I'm able to change settings (ADB enabled, wifi) and importantly use the special offers to launch the browser from which I've installed es explorer. I really want to get my Kindle back ideally to the latest Kindle OS WITH functional Google Store. Can anyone help? ideas suggestions.
Thanks
Click to expand...
Click to collapse
Recovery approach is to adb install an alternative launcher (Apex, Nova) that will allow you to regain some control over your device - hopefully enough to restore the damaged files. The solution is not a panacea; if you touch the 'home' button FireOS will revert to the damaged launcher and you will have to repeat the cycle all over. A present there is no way to reload FireOS on 4th gen device so your options are limited. A factory reset will not restore launcher functionality. If you deleted files recovery will be almost impossible.
If the device remains under warranty contact Amazon for a one-time courtesy exchange.
I was able to install an alternate launcher and as you mentioned there is limited functionality. I wish there were a way to be able to force the device to upgrade to the latest FireOS or to reinstall the default framework as I'm pretty sure that's what got messed up during my attempted GAPP upgrade.
Describe step-by-step your steps. Which files exactly you replaced/changed except gapps.
bnbliss said:
I was able to install an alternate launcher and as you mentioned there is limited functionality. I wish there were a way to be able to force the device to upgrade to the latest FireOS or to reinstall the default framework as I'm pretty sure that's what got messed up during my attempted GAPP upgrade
Click to expand...
Click to collapse
Might consider contacting Amazon to see if they will manually push FireOS v5. Would be risky as an unstable device might not take the OTA well. You would likely 'own' the problem if out of warranty.
At some point a stock image > 4.5.5.1 should become available. You might be able to use that to force a more controlled upgrade. A Safestrap build for 4th gen devices seems unlikely at this point which is the other method used for reinstalling FireOS.
For future reference GApps and FireOS v4 is like Russian roulette. A few can keep the cylinder from rotating but most suffer some type of wound from the experience. Just a matter of time.
The only files changed were GAPP files.
bnbliss said:
The only files changed were GAPP files.
Click to expand...
Click to collapse
The only files changed were GAPP files.
ONYXis said:
Describe step-by-step your steps. Which files exactly you replaced/changed except gapps.
Click to expand...
Click to collapse
Thanks guys. An interesting thing happened when put a launch chooser on the device. Once I chose Nova launcher and then because I had nothing to lose chose Kindle launcher I suddenly had a functional Kindle. I rebooted the Kindle and everything is back to normal with the exception being I still can't update to the latest OS which I'd like to do. Thanks again everyone I appreciate the knowledge shared on these boards.
bnbliss said:
Thanks guys. An interesting thing happened when put a launch chooser on the device. Once I chose Nova launcher and then because I had nothing to lose chose Kindle launcher I suddenly had a functional Kindle. I rebooted the Kindle and everything is back to normal with the exception being I still can't update to the latest OS which I'd like to do. Thanks again everyone I appreciate the knowledge shared on these boards.
Click to expand...
Click to collapse
Great! Nice when the HDX gods are in a good mood
Did you make any effort to block OTA? Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk. If not there or renamed (perhaps with a .bak extension) that is your problem.
Caution: do NOT touch DevicesoftwareOTA Contacts.apk. Alter/rename that file and you'll own a brick
90% there
Davey126 said:
Great! Nice when the HDX gods are in a good mood
Did you make any effort to block OTA? Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk. If not there or renamed (perhaps with a .bak extension) that is your problem.
Caution: do NOT touch DevicesoftwareOTA Contacts.apk. Alter/rename that file and you'll own a brick
Click to expand...
Click to collapse
Thanks Davey for all your help. I had renamed the DeviceSoftwareOTA to prevent OTA updates. I renamed it back, restarted and the 4.5.5.1 download downloads but fails on installation. I've manually downloaded and put it on the Kindle. It's recognized but fails to install also. I then tried devices --> reset to Factory Defaults. The Kindle reboots into Fastboot mode. Strange. I'll dig around and see what I can find. I can't even tell you how happy I am that the HDX Gods have smiled on me, perhaps thanks to your intercession. :laugh:
-bnbliss
bnbliss said:
... I had renamed the DeviceSoftwareOTA to prevent OTA updates. I renamed it back, restarted and the 4.5.5.1 download downloads but fails on installation. I've manually downloaded and put it on the Kindle. It's recognized but fails to install also. I then tried devices --> reset to Factory Defaults. The Kindle reboots into Fastboot mode. Strange. I'll dig around and see what I can find.
Click to expand...
Click to collapse
Thoughts:
- there may be an inconsistency in the system partition that is hampering installation
- typically a factory reset from the native recovery menu (<power>+<vol-up> from cold start) allows balky images to progress
- however, you installed GAaps on FireOS v4 which may be a wildcard
- rebooting to fastboot is weird ...
- verifying you executed the 'Factory Reset' from the native Kindle Recovery menu, correct?
- also assume there was no attempt to install Safestrap or any other 'recovery' tool