I successfully went through Hashcode's instructions for installing the second bootloader, rooting, and installing TWRP, and one of the Cyanogen nightly builds. All was working fine until I decided to try and go back to Kindle mode by restoring the original boot system and recovery images. The Kindle still seemed to work fine with the Kindle apps and I could use my Prime account. Now I am trying to switch back to Cyanogen. My problem is with TWRP. It does not see the sdcard files correctly. I have added some folders and zip files to the root of the sdcard but TWRP does not "see" the new files. It is like it has an image of the very original directory structure. How do I get TWRP to see the new files ????
If it isn't seeing the files you added to the sdcard you could always attempt a "adb sideload", personally i don't use this feature because I prefer pushing the rom and selecting it, but in your case it may be very useful. Oh that reminds me, the amazon os had a different symlink for sdcard I fi remember correctly. Look in the sdcard folder for a folder named 0, if you don't see it still look for it in /data/media/0, and if I have this backwards then it might actually be in the media folder rather than the 0 folder. Think the folder used to be called emulated... This is confusing me a bit, hadn't really looked at cm 11's sdcard paths.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
If it isn't seeing the files you added to the sdcard you could always attempt a "adb sideload", personally i don't use this feature because I prefer pushing the rom and selecting it, but in your case it may be very useful. Oh that reminds me, the amazon os had a different symlink for sdcard I fi remember correctly. Look in the sdcard folder for a folder named 0, if you don't see it still look for it in /data/media/0, and if I have this backwards then it might actually be in the media folder rather than the 0 folder. Think the folder used to be called emulated... This is confusing me a bit, hadn't really looked at cm 11's sdcard paths.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Yes, I found the 0 folder and that is what TWRP is reading/displaying. So now, how do I get TWRP to read/mount the sdcard and not the folder named 0 ???????????/
Just try browsing into /data/media, I would think that's where then old stuff would be, it is kinda the equivalent of what amazon os used i think. I would tell you for sure but I did internal storage wipe not too long ago so in don't have any files left over from amazon os anymore. There's one way you can check I think, boot into amazon os and run this from your PC
Code:
adb shell "ls -n /sdcard"
the part on the very right should should tell where it symlinks to, only problem is I believe it symlinks to another symlink, so whatever it outputs you might want ton run that command non again but with then new oath ton track it to it's original directory. Some of then sum links made created at startup so that's why in suggest doing this because there's no guarantee that the symlinks are in the same location in twrp. Sorry if this is a bit confusing, it makes more sense with a basic understanding of how linux works. I thinkmi traced cm 11's back to /mnt/shell/emulated, but I am sure that's a init.rc symlink... Annoying... Pretty sure that folder is the exact same as /data/media on mine. I'll see if I can help you out if you still can't find it.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Just try browsing into /data/media, I would think that's where then old stuff would be, it is kinda the equivalent of what amazon os used i think. I would tell you for sure but I did internal storage wipe not too long ago so in don't have any files left over from amazon os anymore. There's one way you can check I think, boot into amazon os and run this from your PC
Code:
adb shell "ls -n /sdcard"
the part on the very right should should tell where it symlinks to, only problem is I believe it symlinks to another symlink, so whatever it outputs you might want ton run that command non again but with then new oath ton track it to it's original directory. Some of then sum links made created at startup so that's why in suggest doing this because there's no guarantee that the symlinks are in the same location in twrp. Sorry if this is a bit confusing, it makes more sense with a basic understanding of how linux works. I thinkmi traced cm 11's back to /mnt/shell/emulated, but I am sure that's a init.rc symlink... Annoying... Pretty sure that folder is the exact same as /data/media on mine. I'll see if I can help you out if you still can't find it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
As I mentioned before, I found the "0" folder. It has the sdcard files and folders that TWRP is now reading. It is not the real root of the sdcard!
Should I just delete the "0" folder ????
erForman said:
As I mentioned before, I found the "0" folder. It has the sdcard files and folders that TWRP is now reading. It is not the real root of the sdcard!
Should I just delete the "0" folder ????
Click to expand...
Click to collapse
I wouldn't reccomend deleting it (but that's just me). Amazon's OS for the KFHD is based on Android 4.0.3. CyanogenMod is based on 4.2.2 - 4.4 (depending on which version of CM you download), which includes a user profile feature that saves each user's data to a different numbered folder (the default user being numbered "0" ).
At least, I think this is how it works...?
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11
Yea it should be the folder one level up from the 0 folder that has the amazon os sdcard directory I think.
Sent from my Amazon Tate using Tapatalk
Ph0enix_216 said:
I wouldn't reccomend deleting it (but that's just me). Amazon's OS for the KFHD is based on Android 4.0.3. CyanogenMod is based on 4.2.2 - 4.4 (depending on which version of CM you download), which includes a user profile feature that saves each user's data to a different numbered folder (the default user being numbered "0" ).
At least, I think this is how it works...?
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11
Click to expand...
Click to collapse
Got it sorted out now, I have to use the "0" folder for anything I want to use in TWRP. I am able to safely switch back and forth between Kindle mode and Cyanogen for pure Android. Now ready to experiment with other Rom's. Does anybody have a favorite running on the Kindle Fire HD seven inch?
erForman said:
Got it sorted out now, I have to use the "0" folder for anything I want to use in TWRP. I am able to safely switch back and forth between Kindle mode and Cyanogen for pure Android. Now ready to experiment with other Rom's. Does anybody have a favorite running on the Kindle Fire HD seven inch?
Click to expand...
Click to collapse
I'm using CyanogenMod 11. I like it because its just basic CM without any extra features, and runs smooth.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ph0enix_216 said:
I'm using CyanogenMod 11. I like it because its just basic CM without any extra features, and runs smooth.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
I flashed a nightly CyanogenMod (20140528) with Android 4.4.2. It is running just fine on my Kindle Fire HD 7 inch. Very nice mod with a ton of options.
Related
After installing 6/30 update on nook hd+ i get this odd path and what seems to be duplicate files.
I see it if i for example browse to change the mail notification sound. Or any app that presents an option to load a file.
I had accidentaly tried to flash hummingbird version That failed of course, and id already done clearing steps in cwm
So i had to restore my backup of 6/24 rom first, then booted up, copied ovation then rebooted to cwm and did 6/30 update.
It seems to be my sdcard path.
ANy way to fix this?
pdx1138 said:
After installing 6/30 update on nook hd+ i get this odd path and what seems to be duplicate files.
I see it if i for example browse to change the mail notification sound. Or any app that presents an option to load a file.
I had accidentaly tried to flash hummingbird version That failed of course, and id already done clearing steps in cwm
So i had to restore my backup of 6/24 rom first, then booted up, copied ovation then rebooted to cwm and did 6/30 update.
It seems to be my sdcard path.
ANy way to fix this?
Click to expand...
Click to collapse
That is a default path when on Android 4.2.2. It is just a symlink of your files that exist on the internal storage. If you delete a file in that path, it gets deleted in sdcard as well, and vice versa.
It is setup that way for the multiple users that are available to be setup in the newer Android versions.
0 - first user, 1- second user, etc.
Sent from my HTC One using xda app-developers app
I did some reading and heard about that.
But it usually happens as a result of upgrading an installation which is exactly when it started showing up.
I tried to disable multi-user in settings...that did nothing.
It's a bit of an annoyance as any apps that access the folder structure default to that
instead of the /sdcard/ alias.
Does anyone know if there is a setting or a file that can be modified so at least apps
default to /sdcard/ instead of /storage/emulated/0 ?
I suspect if I re-formatted my nook HD+ and did a clean install of CM 10.1 6/30
then I wouldn't be having this, but I've already got it all setup the way I like it lol.
I was having a similar issue on mine. I couldn't find my dang files I had downloaded when looking to flash them in CWM. It kept telling me I couldn't mount /sdcard, but I finally found the same data in the /emulated/0 path you referred to above. So at least now I know where to look. I'm debating moving my default download directory to the ext_sdcard, so I'll at least know where it is, and my ROMS won't eat up all my internal memory.
pdx1138 said:
I did some reading and heard about that.
But it usually happens as a result of upgrading an installation which is exactly when it started showing up.
I tried to disable multi-user in settings...that did nothing.
It's a bit of an annoyance as any apps that access the folder structure default to that
instead of the /sdcard/ alias.
Does anyone know if there is a setting or a file that can be modified so at least apps
default to /sdcard/ instead of /storage/emulated/0 ?
I suspect if I re-formatted my nook HD+ and did a clean install of CM 10.1 6/30
then I wouldn't be having this, but I've already got it all setup the way I like it lol.
Click to expand...
Click to collapse
Even with a clean install and format, you'll have that folder, its meant to be there.
My HD+ has the folder and I did a full wipe when I got the tablet to install CM10.1. Same when I installed a custom 4.2.2 ROM on my HTC One, the folder will exist. The only thing you can do if files keep showing up doubled in selection screens is to try to see if there's a setting to specify path selection. Failing that, try another clean install. You can backup settings and apps with Titanium Backup or another backup app.
Sent from my BN NookHD+ using xda app-developers app
ilal2ielli said:
Even with a clean install and format, you'll have that folder, its meant to be there.
My HD+ has the folder and I did a full wipe when I got the tablet to install CM10.1. Same when I installed a custom 4.2.2 ROM on my HTC One, the folder will exist. The only thing you can do if files keep showing up doubled in selection screens is to try to see if there's a setting to specify path selection. Failing that, try another clean install. You can backup settings and apps with Titanium Backup or another backup app.
Sent from my BN NookHD+ using xda app-developers app
Click to expand...
Click to collapse
I'm totally fine with it's existence, just prefer apps default to /sdcard/ alias
if possible. Comes in handy when you have to manually type the path...much less typing!
pdx1138 said:
I'm totally fine with it's existence, just prefer apps default to /sdcard/ alias
if possible. Comes in handy when you have to manually type the path...much less typing!
Click to expand...
Click to collapse
Apps should default to sdcard, mine do...
Sounds like you'll need to just do another clean install with a full wipe.
Sent from my HTC One using xda app-developers app
I personally like the stock android browser for quick internet (not to mention that it supports flash). I tried to copy the browser.apk file from another device and transfer it to my KF HD 7", but when installing got a message saying "Parse Error" - There is a problem parsing the package. So, obviously that method will not work.
Does anyone out there have a method to get the stock android browser onto the KF HD 7?
Thanks in advance!
You need to push it or copy it to the /system/app folder, and give it root permissions.
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
Ph0enix_216 said:
You need to push it or copy it to the /system/app folder, and give it root permissions.
Click to expand...
Click to collapse
Thanks for your reply. I had already moved the .apk file to the /system/app folder and attempted to run it there. That's when I got the parse error described above. It did not ask for root permissions, so I wasn't able to grant them. Unless there is something else that I am missing?
Thanks again for your help!
LeiraHoward said:
Thanks for your reply. I had already moved the .apk file to the /system/app folder and attempted to run it there. That's when I got the parse error described above. It did not ask for root permissions, so I wasn't able to grant them. Unless there is something else that I am missing?
Thanks again for your help!
Click to expand...
Click to collapse
There shouldn't be a superuser request. To install the stock browser, first:
a.) Move it to /system/app
b.) Give it root permissions from there like this: rw-r--r--. You can do this in an app like ES File explorer by holding the app and selecting "permissions." Just check the boxes that apply.
c.) Reboot--the app will probably crash if you try to launch it without restarting your system. After the Kindle reboots, try the app to make sure it works. This method is how you move any app to the /system/app folder and make it work correctly (although some won't work if you do this).
Hope this helped. If you have anymore questions, go ahead and ask
Ph0enix_216 said:
Hope this helped. If you have anymore questions, go ahead and ask
Click to expand...
Click to collapse
Thanks for the instructions. (And sorry for the delay getting back to you). I didn't get a chance to try this until just now.
Unfortunately, I'm still not able to get this to work. I keep getting the Parse Error when I attempt to install the .apk. I double checked everything, and the permissions are fine, and I restarted the Kindle Fire, and still no luck. I can only think of two things that might still be the issue:
(1) I got my browser.apk from a Jellybean 4.2 version of Android, it is possible that it is too new for the Kindle Fire version. (Not sure where I could get an older version, though).
(2) Amazon may just not play nicely with normal .apk files.
Yea you usually get a parse error if its for a newer version of android.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Yea you usually get a parse error if its for a newer version of android.
Click to expand...
Click to collapse
Any idea where I could pick up a clean copy of an older version? I'm actually not sure what version of android Amazon Kindles are running.
Kindles run ice cream sandwich based os, I don't know offhand where you could get a copy without having to download a ROM and extracting the apk from it without flashing it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Kindles run ice cream sandwich based os, I don't know offhand where you could get a copy without having to download a ROM and extracting the apk from it without flashing it.
Click to expand...
Click to collapse
Thanks... I just realized that my husband's android phone runs ice cream sandwich... I'm going to try to get the browser.apk file from him when he comes home tonight. If that doesn't work, I'll try grabbing it from a ROM. Thanks again.
LeiraHoward said:
Thanks... I just realized that my husband's android phone runs ice cream sandwich... I'm going to try to get the browser.apk file from him when he comes home tonight. If that doesn't work, I'll try grabbing it from a ROM. Thanks again.
Click to expand...
Click to collapse
Someone uploaded the stock AOSP Browser.apk on the Kindle Fire HD Themes & Apps forum a while back, which was pulled from a phone running ICS or something. I attached it at the bottom. I had it working fine on my Kindle when I was running stock OS. All I did was move it to my SD card, push it to "/system/app," and grant it root permissions. I had to do it this way, as it would force close if I tried to install it the normal way.
And Amazon does play nice with some .apk files. It's just a matter of finding the right ones. Unfortunately, you can't know until you install it as to whether or not it works or not.
Ph0enix_216 said:
Someone uploaded the stock AOSP Browser.apk on the Kindle Fire HD Themes & Apps forum a while back, which was pulled from a phone running ICS or something. I attached it at the bottom. I had it working fine on my Kindle when I was running stock OS. All I did was move it to my SD card, push it to "/system/app," and grant it root permissions. I had to do it this way, as it would force close if I tried to install it the normal way.
And Amazon does play nice with some .apk files. It's just a matter of finding the right ones. Unfortunately, you can't know until you install it as to whether or not it works or not.
Click to expand...
Click to collapse
Thanks. I somehow or another missed the notification of your reply, so just now got around to downloading and attempting to install this version of browser.apk. Unfortunately, it doesn't work for me, either. It fails in a different way, gets part way through the install process and then just gives me a message saying "Application not installed." *sigh* Ah well. Thanks for your help anyway!
Ph0enix_216 said:
Someone uploaded the stock AOSP Browser.apk on the Kindle Fire HD Themes & Apps forum a while back, which was pulled from a phone running ICS or something. I attached it at the bottom. I had it working fine on my Kindle when I was running stock OS. All I did was move it to my SD card, push it to "/system/app," and grant it root permissions. I had to do it this way, as it would force close if I tried to install it the normal way.
And Amazon does play nice with some .apk files. It's just a matter of finding the right ones. Unfortunately, you can't know until you install it as to whether or not it works or not.
Click to expand...
Click to collapse
I was finally able to get it working... I went back to the forum you mentioned and found an older version of the browser.apk that finally worked. Still won't "install" and I can only access the browser from an app manager software, not the KFHD system, but it exists. Thanks!
i put twrp on my kindle form this thread:
[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial
after that my free storage is reduced to 2 gb. when i look under device/ storage somthing called "others" using up 10 gb. i redid the whole thing still the same. what should i do?
What's the exact path to the folder you are referring to? All twrp does is flash the recovery partition, and 2nd boot loader doesn't really use up any space since its not exactly a physical file if I remember right, I believe it's stored in the kernel.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
moiragreen said:
i put twrp on my kindle form this thread:
[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial
after that my free storage is reduced to 2 gb. when i look under device/ storage somthing called "others" using up 10 gb. i redid the whole thing still the same. what should i do?
Click to expand...
Click to collapse
You probably had this issue before modding. Restore back to complete factory status and then let your tablet update automatically (OTA.) This should fix the issue.
I'm willing to bet if you poke around you will find a twrp backup folder they are typically 2 gigs and don't show up right in the used space
Sent from my XT907 using xda app-developers app
stunts513 said:
What's the exact path to the folder you are referring to? All twrp does is flash the recovery partition, and 2nd boot loader doesn't really use up any space since its not exactly a physical file if I remember right, I believe it's stored in the kernel.
Click to expand...
Click to collapse
I was misleading with using the slash. I ment 'Storage' under 'Device' in kindle settings.
LinearEquation said:
You probably had this issue before modding. Restore back to complete factory status and then let your tablet update automatically (OTA.) This should fix the issue.
Click to expand...
Click to collapse
After twrp, i modded with Kinology. Issue remained. Did a hundred reset, whipe cash, dalvik cash, ect. Still not working. Restored the whole thing with KFHD_SRTv1.3.5 option 1, thats restore back to stack whith root (without root option did not work, it kept saying device cannot boot). I think that was 7.3.1. Updated to 7.4.6, put twrp with fireflash and again there was a whole lot of nothing using 10 gigs.
mrkhigh said:
I'm willing to bet if you poke around you will find a twrp backup folder they are typically 2 gigs and don't show up right in the used space
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Poked around a lot looking for files like that, I found twrp backup folder whitch was empty, I booted in twrp and scavenged for hidden files, nothing came up like there wouldn't be anything except system.
I really would miss twrp, becase it allowed me to use Kinology which fullfilled my every need that I have for a tablet. Still dont want to sacrifice 10 gb for it. Is it possible that fireflash somehow partitioned it? Sorry if I ask stupid questions. I'm close to a surgeon when it comes to my kindle: I read a lot about it, only understood the half of it but doing it anyway.
moiragreen said:
Did a hundred reset, whipe cash, dalvik cash, ect. Still not working. Restored the whole thing with KFHD_SRTv1.3.5 option 1, thats restore back to stack whith root (without root option did not work, it kept saying device cannot boot). I think that was 7.3.1. Updated to 7.4.6, put twrp with fireflash and again there was a whole lot of nothing using 10 gigs.
Click to expand...
Click to collapse
Do a complete factory reset and then wait for an OTA update. Then this will fix it. You must let an OTA update happen. Get ris of root, the whole nine yards.
Hi every one,
first, sorry for my english. I'm french.
I root my Kindle fire HD with this tuto: http://forum.xda-developers.com/showthread.php?t=2069117
Then, I intall Playstore with this tuto: http://forum.xda-developers.com/showthread.php?t=2069329
Finally, I install Go launcher HD with this tuto: http://forum.xda-developers.com/showthread.php?t=2069668
But I have only black screen and no wallpaper.
I know it's a know issue, and I try to apply this fix: http://forum.xda-developers.com/showpost.php?p=42181794&postcount=75
But when I try to launch the RunMe.bat and choose the first choice, it say me:
"Your system partition is too low on disk space to complete the procedure, please delete your alternate launchers, widget picker, and livre wallpaper chooser if installed and try again".
I do that, I uninstall go launcher Ex and HD and every thing from the system/app folder, but it say me the same thing everytime. I really don't know How I can apply the fix... :/
My kindle Fire HD is on version : 7.4.8
Thanks a lot for your help!
This is a problem that happens when the system partition doesn't have enough space to safely install the fix, anything you added to the system folder should be uninstalled temporarily. If it was not for thisnpritective measure you would have had the device go into a boot loop. If you can verify that your device does have enough free space on the system partition(around 30-35 mb if I remember correctly) then technically you can modify the script to disable the failsafe pretty easily. Run "df /system" from a adb shell or terminal to find out how much so pace the system partition has free. Personally I recommend just flashing a new ROM over the amazon os because they are so much better but if you want to stick with amazon os then I will try to help you out with the wallpaper fix.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
This is a problem that happens when the system partition doesn't have enough space to safely install the fix, anything you added to the system folder should be uninstalled temporarily. If it was not for thisnpritective measure you would have had the device go into a boot loop. If you can verify that your device does have enough free space on the system partition(around 30-35 mb if I remember correctly) then technically you can modify the script to disable the failsafe pretty easily. Run "df /system" from a adb shell or terminal to find out how much so pace the system partition has free. Personally I recommend just flashing a new ROM over the amazon os because they are so much better but if you want to stick with amazon os then I will try to help you out with the wallpaper fix.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks a lot for your response!
It was that. Too mucuh stuff in my app's folder.
I clean it a bit, and the fix has began and succesfully finish.
But no wallpaper... :/
Just a black creen like before.
I try with wallchanger, but nothing.
Hard way just for a wallpaper... thanks Amazon^^
You have rebooted the device right? If it still doesn't work undo the fix and redo it again, also clearing the dalvik cache can sometimes help.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You have rebooted the device right? If it still doesn't work undo the fix and redo it again, also clearing the dalvik cache can sometimes help.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Yes, I have rebboted.
Automatically when the fix have finished, and again manually after.
I try to do it againt after cleaning, but I doesn't work.
I don't understand...
Can you be more specific? Did the script fail or you mean it applied it again but didn't work again?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Can you be more specific? Did the script fail or you mean it applied it again but didn't work again?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
The scripts finish and say me it finished successfully, and the wallpaper must now work. And the Kindle reboot automatically.
It say me to press key to finish, and the script close.
So I think, it's the normal process with the fix.
I try twice, but same result. The script say me it's good, but no wallpaper, just a black screen.
Hmm wonder if there were any errors along the way I don't have failsafes in place for. If you could copy and paste the output into a post in code brackets I could tell if there was a issue or just use the debugger batch file. Read the instructions for it though or you will think it's broken. You could always just downgrade the kindle is with kffa or flash another ROM to fix the problem.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Hmm wonder if there were any errors along the way I don't have failsafes in place for. If you could copy and paste the output into a post in code brackets I could tell if there was a issue or just use the debugger batch file. Read the instructions for it though or you will think it's broken. You could always just downgrade the kindle is with kffa or flash another ROM to fix the problem.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok, I try again (always blackscreen), and this is all the fix say during the process:
Code:
Could Not Find C:\WINDOWS\system32\framework-res.apk.orig
Doing prelim checks...
Passed!
***********************************************
* Checking For Backup *
***********************************************
* This may take a moment. *
***********************************************
remote object '/data/local/framework-res.apk.orig' does not exist
No Backup Found. (this isn't a bad thing)
***********************************************
* Beginning Wallpaper Fix! *
* This will take a few minutes to complete. *
***********************************************
5708 KB/s (34047391 bytes in 5.824s)
Decompiling framework-res.apk...
Input file (framework-res.apk) was not found or was not readable.
FINDSTR: Cannot open decompiling\res\values\bools.xml
Patching bools.xml...
'xml.exe' is not recognized as an internal or external command,
operable program or batch file.
'unix2dos.exe' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the path specified.
0 file(s) moved.
Recompiling framework-res.apk...
Exception in thread "main" brut.androlib.AndrolibException: brut.directory.Direc
toryException: java.io.FileNotFoundException: decompiling (The system cannot fin
d the file specified)
at brut.androlib.Androlib.readMetaFile(Androlib.java:164)
at brut.androlib.Androlib.build(Androlib.java:183)
at brut.androlib.Androlib.build(Androlib.java:176)
at brut.apktool.Main.cmdBuild(Main.java:228)
at brut.apktool.Main.main(Main.java:79)
Caused by: brut.directory.DirectoryException: java.io.FileNotFoundException: dec
ompiling (The system cannot find the file specified)
at brut.directory.ZipRODirectory.<init>(ZipRODirectory.java:55)
at brut.directory.ZipRODirectory.<init>(ZipRODirectory.java:38)
at brut.androlib.res.util.ExtFile.getDirectory(ExtFile.java:55)
at brut.androlib.Androlib.readMetaFile(Androlib.java:160)
... 4 more
Caused by: java.io.FileNotFoundException: decompiling (The system cannot find th
e file specified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.zip.ZipFile.<init>(Unknown Source)
at brut.directory.ZipRODirectory.<init>(ZipRODirectory.java:53)
... 7 more
'7za.exe' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the file specified.
Updating framework-res.apk
'7za.exe' is not recognized as an internal or external command,
operable program or batch file.
The system cannot find the file specified.
***********************************************
* Backing Up Original framework-res.apk *
* Please grant if a superuser request comes up*
***********************************************
Backup safety check temporarily disabled due to bug. (this doesnt really hurt a
nything as most people just flash back to fix it anyways.)
Installing Wallpaper Fix...
4791 KB/s (34047391 bytes in 6.939s)
***********************************************
* Congratulations! *
***********************************************
* Your wallpaper should now function! *
***********************************************
* Thanks for using Stunts Wallpaper Fix! *
***********************************************
Cleaning Up...
Could Not Find C:\WINDOWS\system32\framework-res.apk
Could Not Find C:\WINDOWS\system32\newframework-res.apk
Could Not Find C:\WINDOWS\system32\resources.arsc
The system cannot find the file specified.
Press any key to continue . . .
If there is no solution, I'll install a custom ROM I think. Simplest I think^^
But a question about that, with another ROM, can I'll still be able to use the Amazon market, read my books buy on, and everything like the Amazon ROM?
If It's ok with that, I think this is the solution.
Is there a really safe processus for? And good custom ROM with this device?
Sorry for all my stupid questions, I'm a really noob with root, etc...
Ah I see why the fix isn't working, its something to do with when it when it retrieved the framework-res.apk, or something of that nature because the file couldn't be found when it attempted to decompile.
To answer your questions about a custom ROM, I prefer stock cm personally, latest version is cm 11. I don't know too much about what's possible with the amazon market on the non amazon is. I think you can still read books, but forget about amazon prime movies and such. I'll check what the amazon app can do in a sec and edit the post. I personally son,t own any books on amazon market so I can't personally test if I can read them, I mainly read manga on my kindle with the pocket manga app. The process to install a custom ROM is safe if you follow the instructions and check things like the md5sum of the bootloader ahead of time and such, but it is possible to hard brick this device. Main point, you probably wouldn't hard brick the device, as long as you check the bootloader's md5sum before flashing it the worst you can do is soft brick it and that's fixable with a fastboot cable. The process is fairly easy and automated if you use the fire flash app.
Edit: OK so I think you can use the amazon app, I can neither confirm nor deny because my amazon kindle app is crashing at launch. I think it works on cm 11 though, I'm still on cm 10.1 because of I'm still having to figure out a way to keep my tablet ui when going to cm 11. Someone might post if they can use it or not because I am unsure. You can always flash back to amazon os, so I wouldn't worry about it too much.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Ah I see why the fix isn't working, its something to do with when it when it retrieved the framework-res.apk, or something of that nature because the file couldn't be found when it attempted to decompile.
To answer your questions about a custom ROM, I prefer stock cm personally, latest version is cm 11. I don't know too much about what's possible with the amazon market on the non amazon is. I think you can still read books, but forget about amazon prime movies and such. I'll check what the amazon app can do in a sec and edit the post. I personally son,t own any books on amazon market so I can't personally test if I can read them, I mainly read manga on my kindle with the pocket manga app. The process to install a custom ROM is safe if you follow the instructions and check things like the md5sum of the bootloader ahead of time and such, but it is possible to hard brick this device. Main point, you probably wouldn't hard brick the device, as long as you check the bootloader's md5sum before flashing it the worst you can do is soft brick it and that's fixable with a fastboot cable. The process is fairly easy and automated if you use the fire flash app.
Edit: OK so I think you can use the amazon app, I can neither confirm nor deny because my amazon kindle app is crashing at launch. I think it works on cm 11 though, I'm still on cm 10.1 because of I'm still having to figure out a way to keep my tablet ui when going to cm 11. Someone might post if they can use it or not because I am unsure. You can always flash back to amazon os, so I wouldn't worry about it too much.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok thanks for your responses!
I'll install CM11. But, Must I really buy this cable? http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
I don't have, juste the original cable and sector in the kindle's box.
On this video, he don't use special cable: https://www.youtube.com/watch?v=PVuvR-hHOLE#t=14
is this proccess is safe? I guess, but I prefer ask you before make a mistake^^
OK I haven't clicked the link yet but I don't tend to use video tutorials, there have been a few hard bricks from people downgrading to a incompatible bootloader. You don't need a fastboot cable/adapter unless you brick it. Lemme grab a link for you. And I will check the video out to make sure its the right one while I'm at it.
Edit: OK well that seems to be the right video, personally I prefer this tutorial: http://forum.xda-developers.com/showthread.php?t=2271909
Its pretty simple, and you don't have to verify the md5sum when downgrading the bootloadernsinc exit includes the file and I assume checks this itself. Only major steps I recommend are put the ROM and gapps on the sdcard ahead of time in case of a boot loop into twrp, and make sure you check the box off with red text around it warning about the bootloader needing to be downgraded. If you don't check the box that downgrades the bootloader then you are going to need a fastboot cable to fix the red screen brick that will result. Oh and another thing, the IMG link has not been updated yet to the twrp 2.7 build which is the latest, so when it says to grab twrp from that page, instead go here: http://forum.xda-developers.com/showthread.php?t=2218796
Once you go there download the zip and extract the img file from it and use it instead.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK I haven't clicked the link yet but I don't tend to use video tutorials, there have been a few hard bricks from people downgrading to a incompatible bootloader. You don't need a fastboot cable/adapter unless you brick it. Lemme grab a link for you. And I will check the video out to make sure its the right one while I'm at it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok, thanks a lot for your help. It's very appreciated!
So I wait your link for the good process to be sure everything will be ok.
Updated post ^^
I kinda put more into that post than I thought I would. I for some reason can't stand YouTube. I mean its great on occasion but I think I grew to dislike it from people constantly sending me instant messages with YouTube links back in the day, annoyed me so much that I grew to dislike it... Kinda funny if I think of it that way.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Updated post ^^
I kinda put more into that post than I thought I would. I for some reason can't stand YouTube. I mean its great on occasion but I think I grew to dislike it from people constantly sending me instant messages with YouTube links back in the day, annoyed me so much that I grew to dislike it... Kinda funny if I think of it that way.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok, I'll follow the tuto wich you gave me in link.
But, in the introduction, Seokhun wrote:
++Note: As of December 2013, Hashcode updated the freedom-boot.img to Amazon 7.4.6 so there should be no more bootloops or any other issues like that for those running 7.4.6 or lower, but to be safe, revert back regardless. If your tablet is running anything higher than 7.4.6, you will run into issues when completing the guide. Again, if you revert back to 7.2.3 like I pointed to above, then you will have no issues. If you didn't revert, always make sure your tablet is running the same or lower version than Hashcode's freedom-boot.img.
Click to expand...
Click to collapse
My kindle is on version 7.4.8. Is there a problem with that?
EDIT: ok I confirm, the tuto is very clear and easy to follow step by step.
I've been very careful and I've follow the written tuto with the video tuto in the same time to read and watch step by step to do no mistake, and It's perfect. Everything works perfectly!
CM11 is installed, no problem!
Thanks a lot for your help stunts, without you, I'll still be in the sand...
Great forum and great community!
Edit2 : Amazon store, apps, books, everything works perfectly... awesome!!
quicker fix
if u just want an easy way to wallpaper, then install vire launcher. i use it and it is nice. it could use more features but itll come along. i also ran into another launcher or 2 that also allowed wallpapers but cant remember the names offhand. i too never got the wallpaper fix to work for my kindle as well. 3rd gen KFSOWI. waiting for unlocked bootloader or whatever lol.
Hi all. Happy New Year! Let me start off by saying that this may be a stupid question because I don't know if it is even possible or if I am thinking that it is a lot harder than it actually is.
Anyway, I have had an HTC device for as long as I can remember and I would really like to have HTC Sense Launcher on my Fire Tablet. I have my Fire tablet rooted and it is running Google Now Launcher at the moment. I downloaded and installed HTC Sense Home launcher from the Play Store on my HTC M9 so I thought maybe I could just download it from the tablet. There aren't any results for the HTC Sense Home launcher if I search from the tablet. So...I used APK Extractor to save the apk from my phone. I have transferred the apk file from my phone to the Fire tablet. However, I have not installed it yet because of a fear of bricking the device.
My worries are...
When I installed it on my phone, it just works, there isn't an app that you can select that says "HTC Sense Launcher". Does that mean that I would have to put that APK in the folder, System->Priv Apps? That is where I had to delete the Fire Launcher file in order to get Google Now as my default launcher.
The other thing that worries me is that I know that I had to install 4 different files just to get the Play Store to work. Would I have to extract more APK's from my HTC phone in order to get the Sense Launcher to work?
Any help with this would be greatly appreciated.
Looks like you need rather more than just the one apk
http://forum.xda-developers.com/android/apps-games/htc-blinkfeed-plugins-devices-08-03-2015-t3049438
You are in the wrong fourm, this is for the Fire 7" model. Lucky for you I created a working tutorial on how to do this on all models, including the Fire HD.
http://forum.xda-developers.com/hd8-hd10/general/tut-remove-default-launcher-amazon-fire-t3288192
nyln said:
You are in the wrong fourm, this is for the Fire 7" model. Lucky for you I created a working tutorial on how to do this on all models, including the Fire HD.
http://forum.xda-developers.com/hd8-hd10/general/tut-remove-default-launcher-amazon-fire-t3288192
Click to expand...
Click to collapse
I think they've just mistakenly thought it was the HD. Plus they've already removed the fire launcher and are using google's one, it's just that the htc one is just bit more complex.
Pond-life said:
I think they've just mistakenly thought it was the HD. Plus they've already removed the fire launcher and are using google's one, it's just that the htc one is just bit more complex.
Click to expand...
Click to collapse
Oh okay, but either way the method I linked to him will work on any version of android without root .
nyln said:
Oh okay, but either way the method I linked to him will work on any version of android without root .
Click to expand...
Click to collapse
Fair enough but he says he's rooted anyway.
Pond-life said:
Fair enough but he says he's rooted anyway.
Click to expand...
Click to collapse
Ah, then you are right, he is a 7" tablet. In that case, here is the answer for him:
First, make sure you install the launcher you want.
Wait 30 seconds in between commands if you don't know what you're doing.
Code:
adb.exe reboot bootloader
fastboot.exe oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot.exe continue
adb.exe wait-for-device && adb.exe remount
adb.exe shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
adb.exe reboot
This will not backup the firelauncher btw, use
adb.exe shell "cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/com.amazon.firelauncher.apk"
if you have an sdcard to backup.
nyln said:
Ah, then you are right, he is a 7" tablet. In that case, here is the answer for him:
First, make sure you install the launcher you want.
Wait 30 seconds in between commands if you don't know what you're doing.
Code:
adb.exe reboot bootloader
fastboot.exe oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot.exe continue
adb.exe wait-for-device && adb.exe remount
adb.exe shell "rm /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk"
adb.exe reboot
This will not backup the firelauncher btw, use
adb.exe shell "cp /system/priv-app/com.amazon.firelauncher/com.amazon.firelauncher.apk /sdcard/com.amazon.firelauncher.apk"
if you have an sdcard to backup.
Click to expand...
Click to collapse
He's already deleted the fire launcher and put goggles one on.
Did you actually read his post?
Pond-life said:
He's already deleted the fire launcher and put goggles one on.
Did you actually read his post?
Click to expand...
Click to collapse
To be completely honest, no. It was everywhere and I assumed he was unsure of what he wanted.
---------- Post added at 02:16 AM ---------- Previous post was at 02:15 AM ----------
Iamjustian said:
When I installed it on my phone, it just works, there isn't an app that you can select that says "HTC Sense Launcher". Does that mean that I would have to put that APK in the folder, System->Priv Apps? That is where I had to delete the Fire Launcher file in order to get Google Now as my default launcher.
The other thing that worries me is that I know that I had to install 4 different files just to get the Play Store to work. Would I have to extract more APK's from my HTC phone in order to get the Sense Launcher to work?
Click to expand...
Click to collapse
No
No