Related
I was wondering how to get GoLauncher on my kindle,
I have a file explorer app on it and from what I searched up, i need to go to a folder called system, but there doesnt happen to be one when I looked for it...
please help
jguy72 said:
I was wondering how to get GoLauncher on my kindle,
I have a file explorer app on it and from what I searched up, i need to go to a folder called system, but there doesnt happen to be one when I looked for it...
please help
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2069668
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.
I have rooted my Kindle fire and was trying to remove the ad, but I accidentally deleted the apk file: dtcp_apk.apk.and am now stuck with ads and no file to change. Any advice?
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Good luck
Hi, I've been browsing for a few days and looking for a way to make my rooted Kindle Fire HD 7" show up in my explorer so I can transfer files to/from it. I used to have this ability, but it went away somehow about a year ago. I have searched prior posts, things I have tried so far:
Downloaded Android Studio hoping it would have the ADB file (I don't think I got that advice here, it was my bright idea)
Downloaded Kindle Fire ADB drivers executable file (from a forum post here) and installed it, it appeared to install correctly but nothing changed
Downloaded a bundle of USB drivers (from a forum post here) and pointed my device manager (showing MTP only, occasionally Kindle appears, both with yellow triangles) to the folder, with search subfolders checked, and nothing changed.
I can report that I am using Go Launcher HD but I don't remember the root method I used, it was a couple years ago. I remember it involved doing a lot of manual changing of file permissions. If that information is needed, is there somewhere I can look in my Kindle to find out?
Anyway, I'm hoping to troubleshoot how I can regain the ability to move files/navigate from my PC, thank you for all of the dedication to helping us less-knowledgeable folks :fingers-crossed:
I searched the Games and Apps forum and the Amazon FIre forums, and didnt find anyone with this problem.
I have an Amazon 7" 5th Gen Fire, and I have installed Google Play store via sd_shadow's method, and I am very happy that it worked.
The thing I am having a problem is this:
Xcom: Enemy within downloads the full 3.4 gig game, but upon launching, within the app, it tries to "download" something in game, but fails every time, right at the start.
I have the game on my phone as well, and the md5sums are the same for the 2 OBB files, but that is all I can find of the game. There are no Android/media or Android/data files.
Suggestions? Does anyone have this working ?
Thanks,
WoodTablet
You could try to copy the files on your phone over to the fire, putting them into the same folder locations.
Where do I look though ?
These 2 directories dont have any files for the game.
/0/Android/media
/0/Android/data
The files in this directory are the same on the phone as on the tablet (I used md5sum to confirm they are exactly the same)
/0/Android/obb/com.tt2k???/xcom-ew/
Same problem
I've had the same issue with XCOM on my Fire (2015) and my Fire HD8 (2016).
My guess is that somehow they're trying to authenticate or get extra data, but the Amazon services mess that up by intercepting or blocking them in some way. Sort of like how if you try to open a google play link in an app you only get the option to open it in the amazon appstore.
My Fire 2015 is on stock at the moment, but I may flash SlimLP or CM to see if this issue still happen when there is not an Amazon service in sight.
I have the same problem with XCOM:EW on m Fire HD8 (2017).
I already opened a support ticket for 2K but honestly I don't think, they will or are able to solve this issue.
My guess is that as long as we don't have native Android custom rom like Lineage, resp. as long as we are completely depended on Amazon, this problem won't be solved for us
Has anyone figured out a workaround?
Any solution?
unknownsoldierx said:
Any solution?
Click to expand...
Click to collapse
Get a different device. Seriously, best answer given game requirements and device capabilities.
I have a solution
Hi everyone,
I'm digging up this thread because I have found a solution.
XCom:EW works differently when run on an Amazon device or on a standard Android Device.
On an Amazon device, it tries to connect to an AWS bucket to get en update. The AWS Bucket is not working anymore, that's why you have a download failed error.
To avoid this behavior, you need to:
- decompile the APK (using APK Easy Tool for example)
- Edit the Smali code of the main file to change a small comparison, and trick the application to think it is not running on an Amazon Device.
The file you have to change is:
com\tt2kgames\xcomew\UE3JavaApp.smali
Line 13203: nst-string v15, "Amazon"
Change it to
Line 13203: nst-string v15, "NONE"- Recompile and sign the APK
- Install it to your Fire Hd
And VOILA!
It works very smoothly on my Amazon Fire HD 10.
I hope you will enjoy it too.
Jon_Ge said:
Hi everyone,
I'm digging up this thread because I have found a solution.
XCom:EW works differently when run on an Amazon device or on a standard Android Device.
On an Amazon device, it tries to connect to an AWS bucket to get en update. The AWS Bucket is not working anymore, that's why you have a download failed error.
To avoid this behavior, you need to:
- decompile the APK (using APK Easy Tool for example)
- Edit the Smali code of the main file to change a small comparison, and trick the application to think it is not running on an Amazon Device.
The file you have to change is:
com\tt2kgames\xcomew\UE3JavaApp.smali
Line 13203: nst-string v15, "Amazon"
Change it to
Line 13203: nst-string v15, "NONE"- Recompile and sign the APK
- Install it to your Fire Hd
And VOILA!
It works very smoothly on my Amazon Fire HD 10.
I hope you will enjoy it too.
Click to expand...
Click to collapse
Thanks! I can confirm that this works. If only the devs would fix the app so this weren't necessary.
unknownsoldierx said:
Thanks! I can confirm that this works. If only the devs would fix the app so this weren't necessary.
Click to expand...
Click to collapse
Please forgive my N00bishness, but I found this thread while trying to install the game to my new Fire HD 10 9th gen.
I've installed APK Easy Tool to my PC, but... where even is the .apk to decompile? I can't find it anywhere on my device.
KamikazeCricket said:
Please forgive my N00bishness, but I found this thread while trying to install the game to my new Fire HD 10 9th gen.
I've installed APK Easy Tool to my PC, but... where even is the .apk to decompile? I can't find it anywhere on my device.
Click to expand...
Click to collapse
I used APK Export.
https://play.google.com/store/apps/details?id=com.ses.app.apkexport
Thank you!
Worked for me.
Seriously dude, how do you even come UP with something like this!?! Just amazing. Thank you so much.
I have the same problem with xcom on my Fire too.
I used APK Export.
But can't find the file UE3JavaApp.smali. Instead I edited UE3JavaApp.java.
But there is no line: nst-string v15, "Amazon"
Can someone help?
Can't find this file. Maybe apk changed? I have XCOM_EW 1.7.0
And btw the issue still exist on the new gen amazon fire tablets. I'm running on fire hd 10 plus
I've had success with this instruction above by user Jon_Ge in Post #9. Thx for that!
In Wordpad i found it under the line: const-string v15, "Amazon"
Besides this in the Apk Easy Tool you have to look for the correct folder after decompiling the apk. It creates another folder where you have to search for and set this new one in the directory for compilation.
Otherwise you would just compile the same unchanged file like i did in first time. Then i realized i had to change the file directory for the decompiled and changed file to have the correct file compiled. I hope this helps.
GetSAS said:
I've had success with this instruction above by user Jon_Ge in Post #9. Thx for that!
In Wordpad i found it under the line: const-string v15, "Amazon"
Besides this in the Apk Easy Tool you have to look for the correct folder after decompiling the apk. It creates another folder where you have to search for and set this new one in the directory for compilation.
Otherwise you would just compile the same unchanged file like i did in first time. Then i realized i had to change the file directory for the decompiled and changed file to have the correct file compiled. I hope this helps.
Click to expand...
Click to collapse
Thanks!