Related
Hey guys, I downloaded some apk's and transferred them to my sd/NC.
I went into file manager located the apks and click to install and I get the following error "installation of download apks is not supported"
This may have something to do with permissions, but you also may want to give ADB a shot. I know it's a bit of a pain to set up, but someone in the dev. forums posted some simpler drivers. I always install with ADB and it works like a charm.
Check to make sure you have "Unknown Sources" checked under Applications in Settings.
Can also try installing with a different file manager, I use Astro and that works.
Tenburn said:
Check to make sure you have "Unknown Sources" checked under Applications in Settings.
Click to expand...
Click to collapse
^^^^^^^^^
What he said.
RoboRay said:
^^^^^^^^^
What he said.
Click to expand...
Click to collapse
i had the same issue with mine checked already, uncheck then re-check it fixed me up and for putting the apk's to nook may want to try dropbox makes things a hell of a lot simpler and here is a shameless plug to get me (and you some free space lol) use my referral link for extra 250mb of space http://db.tt/Zw55leX ;P
b00sted said:
i had the same issue with mine checked already, uncheck then re-check it fixed me up and for putting the apk's to nook may want to try dropbox
Click to expand...
Click to collapse
Good point, you may need to uncheck and recheck it if it's automatically set to "checked" by default when flashing.
I keep a "new ROM setup" folder on my SD card containing DropBox, RootExplorer,Titanium Backup, adbWireless and Terminal Emulator APKs to make setting up a new system easy.
I download the apk, email it to myself, use the gmail app, open the file, tap install, done. Haven't had any issues with 24+ install. I got tired of ADB to push it.
can a file manager be use to install .apk's that are missing from the market place? currently im missing google maps. ive heard about market manager to trick the market and get the full listings, however should this not work, like some have stated, can i download the .apk from my computer and install it using a file manager?
also for the life of me i do not understand nor can i get adb to work. i know its probably real simple. but im done messing with it, so that option is out.
Same Problem
I've got the same problem. "Install blocked. Installation of download apks not supported."
I've tried all the above suggestions: gmailed it, used various filemanagers, Dropboxed it and no success. I could not figure out how to change permissions....how does one doe that?
I haven't tried ADB - waiting to try everything else before I did that.
Im a medical student and I really would love to be able to use the newly available Android Medscape app (free from the market) on my phone.
Unfortunately, it says in description of the app that it may have problems with "rooted" phones. Im assuming it means our HD2's running android on NAND as well, because after installing the App on my phone, I am unable to update/download the Clinical reference data required for the app to work offline.
It gives the error "Internet connectivity was interrupted..Please try again"
Any help from the developers or anyone else would be very greatly appreciated
dude0014 said:
Im a medical student and I really would love to be able to use the newly available Android Medscape app (free from the market) on my phone.
Unfortunately, it says in description of the app that it may have problems with "rooted" phones. Im assuming it means our HD2's running android on NAND as well, because after installing the App on my phone, I am unable to update/download the Clinical reference data required for the app to work offline.
It gives the error "Internet connectivity was interrupted..Please try again"
Any help from the developers or anyone else would be very greatly appreciated
Click to expand...
Click to collapse
Looking at the description and the error you gave, have you tried disabling any ad-blocking software? It may be something cooked into the ROM - if so, try asking the dev how to disable it. DLing now - i'll post back what I find.
.............................
EDIT:
Ok, having found this question asked on the thread for the ROM I use, you can remove medscape from the adblock 'hosts' list. (find it in \system\etc).
Original Post URL: http://forum.xda-developers.com/showthread.php?p=11521445&highlight=block#post11521445
I had to copy the file to PC before editing and copied back again using droidexplorer.
kinsago said:
Looking at the description and the error you gave, have you tried disabling any ad-blocking software? It may be something cooked into the ROM - if so, try asking the dev how to disable it. DLing now - i'll post back what I find.
Click to expand...
Click to collapse
Thanks for the reply. I forgot to mention the ROM im using. Its Core Droid DHD 1.5, and it seems you may be right. It says in the description of the ROM that the "Adds are Blocked (Host files modified)". Is there any way to reverse this host file change?
Fixed it with the help of the developer of the Core Droid ROM. Just opened the app "Add free" and hit "revert". Restored the original host file. Medscape works now.
im having the same issue and clicking the "revert" bottom on AdFree did not fix it
I have uninstalled AdFree and have the same problem all the time. Anybody fixed this?
i had the same problem!
After i revert the hosts file in ad-free, medscape did not update the reference!
So what i did:
I did not unistall ad-free, but:
- i revert the host file 3 times in a row;
- i stopped the access of AD Free from SuperUser (root access);
- and i restart medscape (i killed the process with automatic task killer) and start it again;
- and voila, my htc g1 is updating the reference while i text.
(i don't know what are the steps that make medscape update, but i guess, is the revert host file and restart the app, to it starts didn't knowing that can't access that host to update)
I hope this help you!
Good luck
It works for me, reverted host files, stopped Adfree acces to Superuser and voila!! Medscape is updating again. Thanx
how to correct medscape installation please?thx\
SOLVED!
Just got an OTA update for my flyer and software got updated to version 2.27.1540.32
The android version is 2.2.4 while sense is 1.0
Just for the record, AdFree only works on ROOTED devices. i mentioned in another thread on xda that adfree does not work for me. with this OTA update, my Medscape is finally installing as i type this - - -
Just kill the AdFree app and immediately run Medscape app,it'll definitely take the update.I did the same and it worked
i try looking for file in \system\etc
in use editor to open file host.. thera are a lot of files,
and it make me confuse, where the file "medscape from the adblock 'hosts' list" is ???
wisnu19 said:
i try looking for file in \system\etc
in use editor to open file host.. thera are a lot of files,
and it make me confuse, where the file "medscape from the adblock 'hosts' list" is ???
Click to expand...
Click to collapse
i had found problem solve
copy host file from \system\etc (in yr device) to PC
[*]and open using worldpad in pc
[*]use search from worldpad..type medscape
[*]and delete all file which has name medscape
[*]save !!
[*]move and replace host file which edit from pc to \system\etc in yr device (use es file explorer)
[*]install again medscape
[*]and the update reference should work again..done !!
not solved for me!
Hi everyone!
Well, I've experienced the same "connectivity error" as everyone with a root cellphone, after reinstalling medscape app at my cell. I never had AdFree, and even though I'm able to found the hosts file and take a look of it with my pc it says absolutely nothing about medscape (only 127.0.0.1 localhost and emptyness after), so I guess I must be getting the wrong file or not accesing to it correctly?
I've tried everything you said, but is still not working.
I'm pretty new with android, and I would really aprecciate you help, given the fact that this is one of my favorities app!
lalauri089 said:
Hi everyone!
Well, I've experienced the same "connectivity error" as everyone with a root cellphone, after reinstalling medscape app at my cell. I never had AdFree, and even though I'm able to found the hosts file and take a look of it with my pc it says absolutely nothing about medscape (only 127.0.0.1 localhost and emptyness after), so I guess I must be getting the wrong file or not accesing to it correctly?
I've tried everything you said, but is still not working.
I'm pretty new with android, and I would really aprecciate you help, given the fact that this is one of my favorities app!
Click to expand...
Click to collapse
i just rename file host in /system/etc via root explorer..then it works like a charm
note: ypu can rename it by any programs that's can mount and write root folder and explore (es file explore,x-plore,etc)
Rename?
ivaneris said:
i just rename file host in /system/etc via root explorer..then it works like a charm
note: ypu can rename it by any programs that's can mount and write root folder and explore (es file explore,x-plore,etc)
Click to expand...
Click to collapse
i have got a file in /system/etc called "hosts" , so what should i rename it after? im using root explorer.
Thanks
Thanks Ivaneris
Iam on CM 7.2 LG p500.I had same probs and ur method really worked like a charm.I thought I almost lost it but thanks to you.BTW I renamed hosts file as explorer
Okay, if you have received the 1.3 update or you want to get it, this has worked for a few people now (thanks to billingdl for figuring our walking this path first!). This has only been tested for going from rooted 1.2 to 1.3. No idea on how it will fare with other changes.
You will need a bootable CWM card for this procedure. Look here for that. Then put these files on it:
manualnooter-4-5-18.zip
manualnooter-4-6-16a.zip
Note: Rom Manager is included as part of MN.
You'll notice that MN has an 'a' on it. I added two things there: the final fix for build.prop that was never updated and I also added a script to update the database to block OTA updates (this has worked for me) as found here.
Okay, so here we go...
1. Get the 1.3 update. YOU WILL LOSE ROOT! But don't fret - you shouldn't lose anything else.
2. Shut down your nook and boot with the bootable card.
3. Install manualnooter-4-5-18.zip and then reboot.
4. You have root now, so go launch the market and sign in.
5. Shut down your nook again and boot with the bootable card.
6. This time install manualnooter-4-6-16a.zip.
6a. If you want to, you can also install Dalingrin's OC kernel while you're here, which he recently updated with the 1.3 source. Your choice, but the file is here.
7. Reboot again.
8. Put your regular "data" SD card in for this step - Go into Rom Manager and run the 'Fix Permissions' option.
9. Go into Nook Color Tools and note the check box at the top. After 1.3 for most (if not all) people, the label is missing now. Uncheck and check the box anyway and close NCT.
10. Reboot
and Voila! All should be working!
root seems to be back after step four, but I wasn't unable to open the market until loading up 16a. Looks good so far though!
Your instructions didn't work for me
I purchased a Nook Color in July. It came with Froyo 1.2. I rooted it using Manual Nooter 4.6.16 shortly afterwards and was loving it!
Then last night, the Nook OTA auto-updated me to the Nook 1.3 firmware.
This morning when I picked up my Nook, I noticed that my Android Market, Google Email and Calendar apps icons had changed. When I tried to start them, I got a "App not found" error message. Then after some exploration, I discovered that I had I had lost Root access.
I followed your instructions. After installing Manual Nooter 4.5.18 and rebooting my Nook, I had root access again. However, when I tried to run the Android Market app I got a prompt saying "loading...", then the app closed.
I tried a couple of times with the same outcome. I then ran Rom Manager, was prompted for super user access and allowed it. I then selected the fix permissions option and rebooted the Nook, but the Android Market app still had the same issue as above.
I then figured I move ahead and install Manual Nooter 4.6.16a in hopes it would fix the problem. After applying it and rebooting my Nook, I again tried to start the Android Market app. This time, on the first attempt to run it, I was prompted to set up a Google account. I selected the existing account option and provided my account name and password. I received a confirmation that my android device was now associated with my Google account.
When I attempted to run the Google Market app again, I experienced the same issue as above. I got a prompt saying "loading...", then the app closed.
I again used Rom Manager and selected the Fix Permissions option and rebooted my Nook again. After rebooting I still have the same problem with Android Market app - starts to load then closes.
Now I'm stuck...
Anyone else experiencing the same behavior? Anyone have suggestions for how I might fix the issue?
For those of you who have been lucky enough to dodge the Nook OTA 1.3 firmware auto-update, I'd highly recommend you disable your wireless until you are able to turn off the auto-upgrade to avoid this unpleasant experience.
I'd be very happy to return to Nook 1.2 firmware with Manual Nooter 4.6.16. It was working perfectly for me and allowed me to access, load and run Android Market apps without any problem.
...Steve
ManualNooter was never about blocking updates, it's about keeping the device as fully functional as possible INCLUDING updates while adding more to the device such as a proper Android Market. Unrooting was always going to be a side effect of the update, which should of easily been fixed by by just reapplying 4.6.16. As for the build.prop "final fix", what exactly is that?
Also any indication on WHY this works would be more helpful than you repackaging 4.6.16 with stuff it wasn't designed to have.
GabrialDestruir said:
ManualNooter was never about blocking updates, it's about keeping the device as fully functional as possible INCLUDING updates while adding more to the device such as a proper Android Market. Unrooting was always going to be a side effect of the update, which should of easily been fixed by by just reapplying 4.6.16. As for the build.prop "final fix", what exactly is that?
Also any indication on WHY this works would be more helpful than you repackaging 4.6.16 with stuff it wasn't designed to have.
Click to expand...
Click to collapse
Wish I could say why it works. Like I said, the only thing I did with it was put the build.prop fix in and add the ota change. But others had it work using the last published MN of 4.6.16. I'd love to be able to say it was something I did, but it's not. I was just trying to pull everything together for folks...
sbrack01 said:
I purchased a Nook Color in July. It came with Froyo 1.2. I rooted it using Manual Nooter 4.6.16 shortly afterwards and was loving it!
Then last night, the Nook OTA auto-updated me to the Nook 1.3 firmware.
This morning when I picked up my Nook, I noticed that my Android Market, Google Email and Calendar apps icons had changed. When I tried to start them, I got a "App not found" error message. Then after some exploration, I discovered that I had I had lost Root access.
I followed your instructions. After installing Manual Nooter 4.5.18 and rebooting my Nook, I had root access again. However, when I tried to run the Android Market app I got a prompt saying "loading...", then the app closed.
I tried a couple of times with the same outcome. I then ran Rom Manager, was prompted for super user access and allowed it. I then selected the fix permissions option and rebooted the Nook, but the Android Market app still had the same issue as above.
I then figured I move ahead and install Manual Nooter 4.6.16a in hopes it would fix the problem. After applying it and rebooting my Nook, I again tried to start the Android Market app. This time, on the first attempt to run it, I was prompted to set up a Google account. I selected the existing account option and provided my account name and password. I received a confirmation that my android device was now associated with my Google account.
When I attempted to run the Google Market app again, I experienced the same issue as above. I got a prompt saying "loading...", then the app closed.
I again used Rom Manager and selected the Fix Permissions option and rebooted my Nook again. After rebooting I still have the same problem with Android Market app - starts to load then closes.
Now I'm stuck...
Anyone else experiencing the same behavior? Anyone have suggestions for how I might fix the issue?
For those of you who have been lucky enough to dodge the Nook OTA 1.3 firmware auto-update, I'd highly recommend you disable your wireless until you are able to turn off the auto-upgrade to avoid this unpleasant experience.
I'd be very happy to return to Nook 1.2 firmware with Manual Nooter 4.6.16. It was working perfectly for me and allowed me to access, load and run Android Market apps without any problem.
...Steve
Click to expand...
Click to collapse
I decided to go back and give it a try again from the top. (I had nothing to lose).
The second time I applied MN 4.5.18 and rebooted, the Android Market started working. I was able to connect and I tested installing an app just to make sure it was fully functional.
Great - Then I figured I try to move forward and re-apply MN 4.6.16a. After doing so and rebooting, the issue with Android Market app NOT working returned, ("loading..." message followed by a shutdown of the app). I then realized that wifi wasn't working properly after applying MN 4.6.16a. Checking the settings panel revealed that wifi was off. Every attempt to turning on wifi resulted in a wifi error. Tried applying ROM Manager 'Fix Permissions' again just in case - but wifi problem persisted.
So, I decided to go back and reapply MN 4.5.18 once more. Voila - the wifi and the Android Market started working again.
So I'm now running with MN 4.5.18 and Nook firmware 1.3
I should note that I did apply the optional over-clocking update that you included in your instructions above after applying MN 4.6.16a. Don't know if that is related to the wifi problems I experienced.
Anyway - I've got my Nook Rooted again and running Android Market so I'm happy.
Hope the above info is useful to others who might have the same experience I did.
...Steve
FYI... Did some more follow-up. Tried another version of MN 4.6.16...
Seems that MN 4.6.16 with Nook firmware 1.3 breaks wifi. After applying it, checking the settings panel shows "error" under wifi and wifi is off. Attempts to enable it result in a wifi error. Checking the Nook device info shows an empty MAC address.
So on my Nook there's definitely something incompatible between MN 4.6.16 and Nook firmware 1.3. On doing some googling, wifi improvements are mentioned as one of the optimizations included with firmware 1.3. So maybe that's where the issue lies.
Anyway it's easy to re-apply MN 4.5.18 and once that's done things seem to work fine with firmware 1.3.
...Steve
Try removing the Kernel from 6.16 and see if that works.
sbrack01 said:
FYI... Did some more follow-up. Tried another version of MN 4.6.16...
Seems that MN 4.6.16 with Nook firmware 1.3 breaks wifi. After applying it, checking the settings panel shows "error" under wifi and wifi is off. Attempts to enable it result in a wifi error. Checking the Nook device info shows an empty MAC address.
So on my Nook there's definitely something incompatible between MN 4.6.16 and Nook firmware 1.3. On doing some googling, wifi improvements are mentioned as one of the optimizations included with firmware 1.3. So maybe that's where the issue lies.
Anyway it's easy to re-apply MN 4.5.18 and once that's done things seem to work fine with firmware 1.3.
...Steve
Click to expand...
Click to collapse
There are many variables in getting BN1.3 to be rooted and functional:
1. the method to get to BN1.2: upgrading to BN1.2 via wifi or restoring to BN1.2 via Nemith's zip file.
2. whether CWM is installed on emmc or not.
3. green dot NC or not?
Thanks to OP, i have my NC 1.3 rooted and functional. By the, Flash 10.3 is part of NC 1.3. This is how I got there:
- restore to stock BN1.2 via Nemith's zip file with no CWM on emmc.
-apply MN4.5.18
- get NC working with gmail, apks', etc... still on BN1.2 but rooted
- side load BN1.3 update
- apply MN 4.5.18 - but be sure to wait until it's done 10-15 minutes
- apply MN 4.6.16a
- fix permissions
- install Dalingren's updated OC kernel
Everything works like a champ.
Thanks don caruana! I followed your instructions exactly and they worked perfectly! Like another poster, I didn't have the market back until after I uploaded MN 4-6-16a but everything is back to normal now. Yay!
If I am running cm7 off emmc, i should not even get prompted for this update, correct?
I am not dual booting, just straight cm7!
I'm having a problem.
I was on 1.2 w/MN 4.6.16 and get the OTA to 1.3.
I just flashed MN 4.5.18 and rebooted.
When I launch market, I get a message saying "you must add an account to the device to continue. Do you want to add one now"? If I select either yes or no, it takes me back to my home screen.
What do I do now?
lexluthor said:
I'm having a problem.
I was on 1.2 w/MN 4.6.16 and get the OTA to 1.3.
I just flashed MN 4.5.18 and rebooted.
When I launch market, I get a message saying "you must add an account to the device to continue. Do you want to add one now"? If I select either yes or no, it takes me back to my home screen.
What do I do now?
Click to expand...
Click to collapse
Try going in to gmail and setting up your account there, then go back to the market. You could also clear data for the market and see if that helps.
doncaruana said:
Try going in to gmail and setting up your account there, then go back to the market. You could also clear data for the market and see if that helps.
Click to expand...
Click to collapse
Gmail and Talk both automatically close immediately, clearing data for market doesn't change anything. I got into youtube, chose my channel and it took me to an add account option and when I click that it says "there was a problem authenticating."
Now what?
lexluthor said:
Gmail automatically closes immediately, clearing data for market doesn't change anything. I got into youtube, chose my channel and it took me to an add account option and when I click that it says "there was a problem authenticating."
Now what?
Click to expand...
Click to collapse
That kinda sounds like a network issue of some sort. Try logging into your account from your pc. Also, can you browse the internet with the nook?
doncaruana said:
That kinda sounds like a network issue of some sort. Try logging into your account from your pc. Also, can you browse the internet with the nook?
Click to expand...
Click to collapse
Account works fine on the PC. Nook can browse the internet.
Any other ideas? Argh.
lexluthor said:
Account works fine on the PC. Nook can browse the internet.
Any other ideas? Argh.
Click to expand...
Click to collapse
You know, I had the issue where the market closed immediately on me when I tried to put mn4.6.16 on first. You could try a few things here...
Try going ahead with 6.16 and see if that works
or
Reapply 5.18
or
Reapply the 1.3 update and start over with the process
Unfortunately this thing seems to be a bit of a mystery (no one even knows why 5.18 first works for some), so just keep plugging at it and report back in case anything inspires someone more knowledgeable than me.
I reapplied 5.18 and then rebooted, same thing.
I then applied 6.16a and rebooted. This time I got the same thing about needing to added an account, but when I said yes, it let me add the account.
I then ran fix permissions and rebooted one more time for good measure.
Things all look good now!
Thanks so much.
Hopefully this helps anyone else with the same issue.
I guess I don't have to worry about a future OTA forced upon me now since I used the "a" version. What exactly does the "final fix for build.prop" do though?
lexluthor said:
I reapplied 5.18 and then rebooted, same thing.
I then applied 6.16a and rebooted. This time I got the same thing about needing to added an account, but when I said yes, it let me add the account.
I then ran fix permissions and rebooted one more time for good measure.
Things all look good now!
Thanks so much.
Hopefully this helps anyone else with the same issue.
I guess I don't have to worry about a future OTA forced upon me now since I used the "a" version. What exactly does the "final fix for build.prop" do though?
Click to expand...
Click to collapse
Glad that worked for you!
The build.prop thing is an issue where the original intent of MN was to change the fingerprint of the device for improved market visibility. It was supposed to change to "samsung/GT-P1000/GT-P1000/GT-P1000", but the script had an error and it just got left at zoom2. I can't tell you what the difference in visibility is, but it was a fix that never got implemented, so I slapped it in there.
BTW, I'm sure you're skittish at this point, but you might want to look at Dalingrin's OC kernel, if you haven't already. Although the first thing I'd do is take a full backup with CWM!!
Happy "Nook"ing!
Thanks doncaruana!
This worked for me too, however, I had the same initial problem with Market as two other posters where it would FC when fired up as per your instructions. But after applying the MN 4.6.16a, it fired up fine. I'm wondering if it had to do with my SD card though. I did not have my "normal" SD card installed when I first fired up Market, but I did have it in once I had applied MN 4.6.16a, so no big deal. Just successfully downloaded/updated a dozen apps. from the Market with no problem and definitely have root again. System reports BN software version 1.3.0. Thanks again for all of your work on this, esp. regarding no OTA updates; obviously the otacerts.zip rename doesn't work since that's what I had in place and I still got 1.3 pushed!
One question for you though - does the DB OTA fix disable any BN features other than OTA updates (e.g. in store stuff, etc.)?
So I often watch TV show episodes on the websites for CBS, ABC, and NBC and just today for the first time I tried doing so while tethering to my phone using the Mobile AP. When I clicked on an episode, however, I received an error telling me, "This video is either unavailable or is being blocked by an ad blocker installed in your browser." The thing is, I definitely don't have an ad blocker installed in my browser; and, when I disconnected from my phone and instead connected directly to my ethernet, the video worked fine right away. I tried it for shows on NBC.com as well as ABC.com and received similar errors all pointing towards Ad Blocking software. Has anyone else ever experienced this or does anyone know the relation between tethering to Mobile AP and an Ad Blocker detection? Any help would be greatly appreciated as I have two laptops and only one ethernet hookup, so I would like to be able to have good internet connected to both at once.
No one huh???
Sent from my SAMSUNG-SGH-I897 using XDA App
Install AdFree Android from the market, then choose revert.
do you have ad-blocking built into your rom? delete (or rename) the "hosts" file in system/etc
TRusselo said:
do you have ad-blocking built into your rom? delete (or rename) the "hosts" file in system/etc
Click to expand...
Click to collapse
Ohhh wow I didn't even realize that ad-blocking came built into ROMs. I just quickly checked in /system/etc and did see the hosts file, opened it up and checked out the text. I tried renaming it but it was read-only, and root explorer wouldn't let me remount as r/w. I guess I'll look into it more tomorrow. But I would imagine I wouldn't want to just straight delete it right, as whatever ads it was blocking would no longer be blocked? I could just rename it any time I encountered errors while tethering to my laptop?
Does reverting through Adfree simply delete that hosts file?
Sent from my SAMSUNG-SGH-I897 using XDA App
if root explorer wouldnt let you mount you might have lost root somehow. re root.
TRusselo said:
if root explorer wouldnt let you mount you might have lost root somehow. re root.
Click to expand...
Click to collapse
I don't think I did. I just updated the su binary and when I reopened root explorer, superuser asked me if I wanted to allow root access to root explorer. I've read that before somewhere of people having trouble remounting within the /system folder. It let's me remount on folders outside /system, just not inside it. I still haven't figured it out. I suppose I could use terminal emulator right?
Sent from my SAMSUNG-SGH-I897 using XDA App
TRusselo said:
do you have ad-blocking built into your rom? delete (or rename) the "hosts" file in system/etc
Click to expand...
Click to collapse
you were exactly right TR. i renamed the hosts file and re-tethered and i no longer received any errors about ad-blocking software. not to say the video is actually working too well tho - just keeps freezing. i guess streaming tv episodes while tethered to your phone isn't the best idea. anyway, thanks man!
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Version 7.3.0 is out. Here are the specs from the Amazon page:
"Support for X-Ray for Textbooks
Explore the “bones” of your textbook, and access all the most important terms and concepts, with glossary definitions and links to relevant textbook pages.
Simplified Chinese Support
In addition to the other languages offered, you can now change your device language to Simplified Chinese.
Track your reading progress with Time To Read
Kindle Fire HD 7” calculates your reading speed to let you know when you’ll finish a chapter or book.
Support for Kindle Editions with Audio/Video
You can now read books that contain audio and/or video clips.
Print Replica Textbook Enhancements
Scroll through thumbnails at the bottom of the screen to preview pages and jump quickly between chapters, and mark important notes and highlights in your Notebook for easy reference."
None of this seems overly important, but then again I do like to have the latest version as long as there is no harm to the root.
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Anything you install as a system apk will be deleted. When amazon sends an update it typically sends system.img, recovery.img and boot.img.
That is why the lmt launcher will not work because it has to be installed as a system.apk to work, same with root access since su binary is placed within the system files.
if you want to install the 2nd bootloader, you should not update. Amazon have fixed the bootloade with the update and so it dosn't work for now. i don't know, if it perhaps work with soupkit, because the insallation is a little bit different, but the resultat is the same (I could install kinelogy 1.1 after doing that).
I'm still on 7.2.1, found Wi-Fi performance/range considerably better than on 7.2.3, unless 7.3.0 improves it I won't be updating for quite some time.
This explains why I lost root and Go Launcher HD yesterday. Regained root with the same Noob Simple guide here with little more than annoyance. The file to prevent the OTA update had been moved per the guide (otacerts.zip) but think I deleted it in a cache cleaning frenzy... that will learn me
macbranson said:
I believe Amazon released an update today as my KFHD just rebooted itself and turned back on with a progress bar. My question or issue is this: does an update automatically cause a rooted KFHD to lose root access? I still have access to Google Play store and a bunch of apps I could only access through root. And most of the apps still work except LMT Launcher, which is the only one that is no longer working as far as ive noticed.So all I have to do is plug back in and root my KFHD again and I should be good, right?
Click to expand...
Click to collapse
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
EDIT: OK, I was able to re-root the same way I did before (used the tools in prokennexusa noob threads!) All back to normal!
markbc01 said:
Ouch! I got caught by this update . . . i am now running 7.30 on my KFTT 7"
Sad, since I had a nice rooted image all set up well. Unfortunately, I became a bit lazy and did not check on whether or not I had effectively disabled updates during my last restore/reflash of 7.2.3 (I had not done that ;-(
sigh! Like you, I have all my apps and the Play store working, but anything requiring root -like root explorer or TIBU, won't work until I can reroot on this version -or flashback. . . The only question is whether the root exploitation works on this new version, I am not sure any of us has tried yet. . .oh well. . here we go (again!)
Click to expand...
Click to collapse
Same root method worked, system feels about the same with tweaks installed and benchmarked similarly (7344 vs 7444 with AnTuTu)
I just can't get my launcher off of the stock one. Nothing will take.
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
macbranson said:
I simply plugged my KFHD back in and re-rooted. I regained access to applications that required system access. So my LMT is working again. I didn't lose any apps as far as I've noticed. This update turned out to be a pretty minor inconvenience.
Click to expand...
Click to collapse
Which method did you use to root again ?
Nop update here istill in 7.2.3
Damn just got the damn update like 5 min go
Sent from my Nexus 7 using Tapatalk 2
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
geeibara said:
Has anyone had any success of their launchers working correctly since the update?
I re-rooted my kindle but I'm not able to make the launchers...well launch.
Click to expand...
Click to collapse
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
quan_1986 said:
I'm update ver 7.3.0 normal,apex launcher and Gplay normal .Update Chrome from Gplay very good :good:
Click to expand...
Click to collapse
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
geeibara said:
I'm not able to move the apk files to /system/app
When I try to move it, it only moves to /System, I tried to install it in /system, but nothing works.
Click to expand...
Click to collapse
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
#3Clara said:
I had this issue as well - and then noticed something else that was really weird. When I tried to move to /system/app it only moved to system - but I also noticed (at least in my case) it was renaming the file by adding "app" (which was the folder name I was trying to move it to) on the front of the file name - so... GoLauncher HD.apk was being renamed appGoLauncher.apk but was landing in the /system folder instead of /system/app
So - I created a new folder called "temp" in the /System/App directory (i.e /system/app/temp) and moved the files there. Sure enough, they landed in /system/app with the the word "temp" appended to the front of the file name, so GoLauncher.apk was now tempGoLauncher.apk. However, it was in the right directory - so I then simply renamed it by removing the "temp" from the front of the name and continued with install
I still have lots of other issues though in getting it to work. It appeared to be working for a while, but has stopped again.
Click to expand...
Click to collapse
haha yah I noticed that too, I had files like appappappappappappapplauncher lol. Thanks this helped a lot
modmyphone said:
I just can't get my launcher off of the stock one. Nothing will take.
Click to expand...
Click to collapse
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Gah.. I actually tried to deactivating the manual update and some how the update still pushed through.. which really sucks cause I hard my set up perfect..hope all I have to do is reroot.. ..all that time spend for nothing
Sent from my KFTT using xda app-developers app
BmanCV-60 said:
Are you going through Google Play? I used Prokennexusa' post to get the launchers back:
http://forum.xda-developers.com/showthread.php?t=2069668
Click to expand...
Click to collapse
Actually, I tried 3 different ways.
1) I reluctantly attempted ProKennexusa's method via the KFFFirstAide tool. I say reluctantly since I'm pretty much a Nova snob. I guess luckily for me, it wouldn't take.
2) I then moved onto downloading Nova from the store. The store claimed that both installs went good, but had no option to change my launcher. Upon inspection, the Nova launcher file was nowhere to be found on the device. The pro unlocker could be found, but no the launcher.
3) Since I had a couple of older copies in Dropbox, I figured I'd try those. Usually I could install straight from Dropbox. Not last night. I could launch the install, but the Kindle wouldn't allow me to press the install button. I then just saved the file to the device and still couldn't get it to install. It wasn't until moving it to system/app that I was able to actually install it. But still, no option to set it as my launcher.
This morning, in a bit of Kindle rage, I literally rebooted the device 23 straight times pausing between boots to see what happened. On the 23rd reboot, it finally asked me which launcher to set as default. So now I finally have gotten away from the freakish kindle launcher and am back at home with Nova.