Related
For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Would you support the archos G9 devices
jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now
Quit following me around jcase
Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry
jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.
Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.
Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?
b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen
wrong - switch back to normal boot and use the utility
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Its simple if u have a backup. I have not heard of anyway of getting to build.prop thru recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
You need to restore from backup (nandroid) or start over if you don't have a backup..
Did you copy the original file to ur sd card then back over?
Chances are you did.. I did the same thing lol.. And when u do that it doesn't save original permissions of the file.
The reason the wallet post says to use root explorer is because it saves the file in the same folder permissions and all and you can just rename it back.
Sorry dude u are sol.. Restore from back up or flash a new rom and start over.
Sent from my SAMSUNG-SGH-I747 using xda premium
Get into recovery, do a factory reset.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
Any resolution. I have the same problem.
mrhaley30705 said:
Get into recovery, do a factory reset.
Click to expand...
Click to collapse
I don't think that would work, as far as I know a factory reset only wipes data and cache. The build.prop is part of the system, so it will not change.
Sent from my SPH-D710 using xda premium
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Side note--> twrp recovery has a built in terminal and the ability to copy/paste files from internal and external SD cards. Not so sure about changing permissions easily....but through the built in terminal....might be able to load what you need (plus twrp flashable found in android dev forum) on external SD card with an adapter on a computer. Flash twrp and transfer files or use built in terminal to change perms. Good luck....
I know editing build props with es file explorer will cause That.
Sent from my SAMSUNG-SGH-I747 using xda premium
Fixed it!
Thanks everyone for your help, i feel like an idiot for not replying to anyone i didnt have it set up to notify me of replies, i figured out it was the build prop that was messed up, im not sure how this worked but i figured i would try to root again and flash the root files using the simple root steps using odin and it actually fixed the file and booted up fine! i appreciate everyones help and hope this thread helps other people because i know many people screw this up the same way i did. (i will never do anything like this without doing a nandroid backup again). THANKS AGAIN!
thanks but..
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
ibanezbass said:
Permissions probably got reset. Resetting to factory will not change the build.prop. Either re-install the rom or...
Do this. This will reset permissions to the correct value without affecting your data. This is easy once you get the hang of it. I do not know if I'm allowed to post up the adb file or I would.
I'm going to run through a quick setup of the Android SDK so that you can use adb if you choose to go this route. The SDK will be useful all though rooted phone usage, so I suggest you download it and use it. ADB is a very powerful tool. First, Google Android SDK. The first result should be the official site for the Google developer section. Just open that top link and the page should have a huge button that says "Download the SDK for (Windows or Mac or whatever)". Click it. Mac users.. Yours does not actually setup. You need to find the SDK Manager app within that zipped download and run it. Windows users... Run the setup. When it's done it will open the SDK manager. Both Users... Check the box next to the "Android SDK Platform-tools". Bottom Right, Install x Packages. Make sure you take note of the SDK path displayed at the top of the manager. EG. C:\Users\Josh\AppData\Local\Android\android-sdk. Mac users: Yours will be in the downloaded folder that you extracted. All Users: Navigate to that folder via terminal (mac) or cmd.exe (windows). Windows: cd C:\Users\Josh\AppData\Local\Android\android-sdk ... Mac: cd /Users/josh/Downloads/android-sdk/ ... Then navigate to the platform-tools folder that is within the SDK folder. Here is where ADB is located.
Windows instructions:
Download adb.exe, either through the Android SDK or elsewhere. Use Google.
Connect phone to computer via USB.
Boot phone into recovery.
Use cmd.exe (Use Windows key+R, and type cmd in the run window) to navigate to the folder containing adb.
E.g. "cd c:\Users\Josh\Downloads\adb"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone. If you get an error, make sure you have the drivers loaded for your phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Mac Instructions:
Download the adb application, either through the Android SDK or elsewhere. Use Google. Make sure you download the Mac version, not the Windows or Linux version.
Connect phone to Mac.
Reboot phone into recovery.
Open Terminal on Mac. /Applications/Utilities/Terminal.app or use spotlight to find it.
Navigate to folder containing the adb app. E.g. "cd /Users/josh/Downloads/adb/"
Run "adb shell"
This should initiate a shell to the phone allowing you to run commands on the phone.
Run "cd /system"
Run "chmod 644 build.prop"
Optional: Run "ls -l" and make sure that the permissions on build.prop show RW-R--R--.
Reboot phone.
Click to expand...
Click to collapse
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
prior to running that command, type su then hit enter
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
stratatak7 said:
If I made a CWM flashable unedited build.prop from a stock SGS3 rom would that help anyone? It just seems easier than all those ADB commands assuming you can still access recovery.
Click to expand...
Click to collapse
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
lyrictenor1 said:
I'm sure that'll probably helpful to a lot of people. Unfortunately, I'm using the stock recovery so it probably wouldn't help me...
Click to expand...
Click to collapse
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
crammer04 said:
I have a major problem but i think there is a way to fix it, i just cant figure it out. i was adding google wallet on my rooted s3 and when reverting the build.prop file to its original form, i just copied and pasted the backup and renamed it to the original build.prop to replace the new one using root explorer. my phone does not boot up now i get the samsung startup screen and it shuts off. i could get into cwm recovery mode. any way to fix the build.prop without being able to fully boot the phone? i am on a mac but i could have access to a pc tomorrow if i need.
Click to expand...
Click to collapse
_________________________________________________________________________________________________________________
If you got no back up give us your phone information one of us can send you one I have aTT D2att you
?
Its all in my sig get mobile odin bellow, get the tar for which ever recovery you got. I got all three. CWM, CWM Touch and TWRP for d2att (only) if different phone then use other ones.
Thats my build prop im D2att SG3 ok so just make sure. But you can grab mobile odin bellow and fix it.
_________________________________________
Just get mobile odin HERE
and flash your reocvery there CWM, TWRP, CWM TOUCH... all of them latest all in my sig bro
Here is all drop box to get any of the recoverys --------------------> Recoverys Drop Box
Get mobile odin Here along with the s3 kernal extension its all in here -----------------------> Mobile Odin
If you get hardware id missing error install these old samsung dricers this is a bonus, don't update it ----------------> Hardware ID samsung driver fix
__________________________________________________________
S3 build prop here --------------> here
Mobile odin is simple if download zip in my drop box just install it (or get it form market) download the driver you need (in my drop box) or go mobile odin thread and find it if your on a different phone. Rest is simple just load what your going to flash click the OPEN FILE option in mobile odin click tar and run it.
_________________________________________________________
Get android comander. You can mod build prop easy with it its nice GUI for installing programs or uninstalling or backups or moving files around. awesome try out here --------------------------------> ANDROID COMANDER
need anything else?
---------- Post added at 09:42 PM ---------- Previous post was at 09:20 PM ----------
lyrictenor1 said:
Okay, I got the adb shell to run, but I run into this snag:
"Unable to chmod build.prop: Operation not permitted"
Anyone know what this means?
Click to expand...
Click to collapse
Tiy need to remount system Read Write i don't think its a SU problem it could be but normaly you already got su i forget comand in adv its mount system -r i beleive. I dunno I run a script that mounts it for me let me check it out real fast
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
crammer04 said:
So the problem with this route was that for some reason the device was not being recognized by adb, i dont know why, i thought it was a driver issue but once i fixed the phone, i was able to get adb access, so i guess that boot error was preventing it from getting recognized (which i didnt understand because my friend screwed up like me the next day and was able to adb.) but finally fixed it a few days later after trying many things and the fix for some reason was a simple process with odin, i think this article shows what i did, i dont remember exactly tho - http://smartphonefix.blogspot.com/2...r-Recover-Bricked-ATT-Galaxy-S3-SGH-I747.html
Click to expand...
Click to collapse
Just so you no a common problem when doing commands you forget to do it just trying help didn't know fixed
#!/system/bin/sh
busybox mount -o remount,rw /system
My build.prop got messed up while trying to install Google Wallet on my rooted sg3 and my phone became soft bricked. I had to reinstall the stock jellybean ROM with root that I had been running before this happened, through Odin. Solved my problem. Never got wallet to work though.
Sent from my Amazon Kindle Fire2 using xda app-developers app
Would this work on S3 T-Mobile T-999?
stratatak7 said:
If you're not comfortable with ADB: You should try to flash recovery (recommended TWRP but at this point take anything you can get) from ODIN. I know I've seen it around here somewhere. Once you do that, then flash the attached file.
This will flash in CWM/TWRP etc. I haven't tested it, so send me a PM if it doesn't work and I'll fix it up.
Edit: I've located the proper recovery file for you to flash. It's cwm, but you flash this with ODIN. Download it from here http://k0nane.info/rom/ecm/CWM-Recovery-LTE-SGS3-v5.tar.md5 . ODIN will increase your flash counter, but Chainfire's Triangle Away app takes care of that like it never happened. Odin can be found in the development thread. If you want to automate this process even further just download the qcom toolkit which walks you through the process of installing recovery. I hope this helps.
Lastly, here's the latest TWRP image file with ADB instructions. Short, sweet and simple. http://teamw.in/project/twrp2/104
Click to expand...
Click to collapse
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Boosoth1st said:
I am having the same problem.... as the person above... Will this .Tar file below work for S3 T-Mobile T-999? Can you make one for that phone?
Thanks for your help!!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1746682
Try downloading the toolkit from there. It should contain the necessary T-Mobile files. If you are having an issue, please PM me. Make sure you flash the right one! Be careful and read the whole thread.
I am having issues. The first time I tried this I thought it was a success as I went through the steps and got the loading screen on the fire tv to come up. I waited for about 10 minutes and then the firetv reset but Kodi did not install.
Now I am trying to do it and when I hit enter after the string to sideload the .apk nothing happens. I get no response in the terminal and it just goes to the next line. I cannot figure this out for the life of me.
I am using terminal on a mac. This method http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/
please help.
Try the additional "-r" option during install ('-r' means reinstall the app, keeping its data).
For e.g.:
Code:
adb install -r kodi.apk
Calibaan said:
Try the additional "-r" option during install ('-r' means reinstall the app, keeping its data).
For e.g.:
Code:
adb install -r kodi.apk
Click to expand...
Click to collapse
Thanks - I am brand new to mac so this is new to me. So basically my string would be
./adb install /Users/YourUserName/Desktop/-r filename.apk
?
seagood3 said:
Thanks - I am brand new to mac so this is new to me. So basically my string would be
./adb install /Users/YourUserName/Desktop/-r filename.apk
?
Click to expand...
Click to collapse
No. The option "-r" must be used before the complete path to the APK file. Have a look:
Code:
./adb install -r /Users/YourUserName/Desktop/filename.apk
Calibaan said:
No. The option "-r" must be used before the complete path to the APK file. Have a look:
Code:
./adb install -r /Users/YourUserName/Desktop/filename.apk
Click to expand...
Click to collapse
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
seagood3 said:
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
Click to expand...
Click to collapse
Couldn't you use adbfire on your mac..... it's available from this link http://forum.xda-developers.com/showthread.php?t=2786505 it might make things a little easier...
slackbladder said:
Couldn't you use adbfire on your mac..... it's available from this link http://forum.xda-developers.com/showthread.php?t=2786505 it might make things a little easier...
Click to expand...
Click to collapse
I haven't used that because I am running into all kinds of issues. First I got the "Can't create log file" error. I googled that and see that I need to drag the app onto the desktop or into the applications folder. The problem is when I try to move it I get another error message "The operation can’t be completed because you don’t have permission to access some of the items". I feel like such a newb with this Mac. I have no clue how to troubleshoot.
any help?
Any chance you have a Windows PC connected to your network that you can try? I did this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-windows/) and had no issues.
If you can get ES File Explorer onto the FireTV, then you can go to Network/Cloud and add an account, connected it to a Dropbox account, then just download apks and open them from ES File Explorer, you won't need the PC or adb any more.
seagood3 said:
I just tried this and got the same issue where when I hit return, it just drops down to the next line. I don't understand this.
Click to expand...
Click to collapse
Can you even connect to the aTV?
Try some ADB commands to see if ADB does really work:
Code:
adb devices
This should list all via ADB connected devices. If the list is empty you´re not connected.
When your device is connected try some basic shell commands:
Code:
adb shell
This opens a bash shell. Within this shell type
Code:
ls
and the directory content of the actual folder should be listed.
ADB shell can be left with:
Code:
exit
If this isn´t working, check your ADB version you have installed and try to install a newer/other one. I had such an issue once on Windows with an Android tablet which couldn´t be connected with the ADB version I had already installed on my PC so I took another ADB version and it worked. Of course this shouldn´t be but it seems that this can happen.
Another hint might be your problems regarding adbfire. Perhaps your user restrictions prevent ADB from proper working. I´m not firm on MAC´s but I think they support the "sudo" command (explanation: http://en.wikipedia.org/wiki/Sudo). So try your ADB commands again with an additional sudo before similiar like this:
Code:
sudo adb install kodi.apk
I can't figure this out - I am following this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/) perfectly and I got it to work the first time but it just didn't complete it for some reason and now every time when I hit enter on the last step nothing happens.
I can't use the adbfire app because of the other issue.
WTF? why isn't the method through terminal working?
seagood3 said:
I can't figure this out - I am following this (http://sideloadfiretv.com/sideload-apps-amazon-fire-tv-mac/) perfectly and I got it to work the first time but it just didn't complete it for some reason and now every time when I hit enter on the last step nothing happens.
I can't use the adbfire app because of the other issue.
WTF? why isn't the method through terminal working?
Click to expand...
Click to collapse
I don't know...on mac you need to use ./ unless you configure it otherwise so to connect I'd type ./adb connect myipaddress
If you are connecting then you have adb working. I use adbfire but here's what I'd do...
I like keeping my adb folder with platform tools on my desktop. Put the apk you want to install in that folder
type "cd" <space> then drag the whole folder into the terminal--hit enter
now type ./adb connect youripaddress--hit enter
if it says connected type ./adb install<space>then drag the apk from inside your adb folder right into the terminal--hit enter
If you did it right nothing will happen instantly. It depends on how fast your connection is. Wait up to 5 minutes I'd say and you'll either get a success message of an error. If it's the latter, post it here.
Did you read my previous topic and tried what I´ve written?
Forget this Howto since it is just a general guideline and it can´t help you with your actual problem since it is more or less a first time installation guideline but you have already had a previous installation which makes the difference. It can also not deal with restrictions on your system side for e.g. if ADB wouldnt´be allowed to access USB.
If you´re sure that your system is not restricted anyway and ADB should work and if you still prefer to work only with this guideline do a factory reset within your FireTV. This should set the box in a state back again where this guideline should work how it is intended.
Or try SPMC from Amazon App Store which would be the easiest way:
http://www.amazon.com/Semperpax-SPMC/dp/B00MK49LL8
Hi, i have a fire tv and nexus player. I'd like to try and install some of the apps designed for the fire tv to see if they will work on the nexus, seeing as these apps should be designed to be used with a remote.
I've tried following this guide .. http://www.aftvnews.com/how-to-transfer-amazon-fire-tv-apps-to-a-fire-tv-stick/ .. but i must be doing something wrong as i get an error at the last step, maybe i am not entering the directory correctly as i get a 'no such file or directory exists' error.
this is the string i am entering. 'adb pull /data/app/uk.co.bbc.iplayer-2.apk F:/Downloads'
can anyone help?
thanks.
..
hendoben said:
Hi, i have a fire tv and nexus player. I'd like to try and install some of the apps designed for the fire tv to see if they will work on the nexus, seeing as these apps should be designed to be used with a remote.
I've tried following this guide .. http://www.aftvnews.com/how-to-transfer-amazon-fire-tv-apps-to-a-fire-tv-stick/ .. but i must be doing something wrong as i get an error at the last step, maybe i am not entering the directory correctly as i get a 'no such file or directory exists' error.
this is the string i am entering. 'adb pull /data/app/uk.co.bbc.iplayer-2.apk F:/Downloads'
can anyone help?
thanks.
Click to expand...
Click to collapse
Enable ADB DEBUGGING on your Fire TV.
Find the IP address of your Fire TV.
Install adb on your windows machine.
Type
Code:
adb connect 192.168.1.115
(Just replace the IP I listed with your IP address)
then to confirm it connected type
Code:
adb devices
You should get an output like this:
Code:
192.168.1.115:5555 device
then do
Code:
adb shell
then run
Code:
pm list packages -3 -f
You will get an output that looks similar to mine:
Code:
package:/data/app/com.amz.games505.Terraria-1.apk=com.amz.games505.Terraria
package:/data/app/com.concretesoftware.pbachallenge_amazonfree-1.apk=com.concretesoftware.pbachallenge_amazonfree
package:/data/app/com.digitalx.amazonvirtualfireplace-1.apk=com.digitalx.amazonvirtualfireplace
package:/data/app/com.digitalx.amazonvirtualsnowfallhd-1.apk=com.digitalx.amazonvirtualsnowfallhd
package:/data/app/com.dotgears.flapfire-1.apk=com.dotgears.flapfire
package:/data/app/com.ea.life_full_azn-1.apk=com.ea.life_full_azn
package:/data/app/com.edgeway.firefliesambience-1.apk=com.edgeway.firefliesambience
package:/data/app/com.edgeway.moonlightocean-1.apk=com.edgeway.moonlightocean
package:/data/app/com.edgeway.perfectstorm-1.apk=com.edgeway.perfectstorm
package:/data/app/com.edgewaysoft.snowyambience-1.apk=com.edgewaysoft.snowyambience
package:/data/app/com.edgewaysoft.stormyambience-1.apk=com.edgewaysoft.stormyambience
package:/data/app/com.estrongs.android.pop-1.apk=com.estrongs.android.pop
package:/data/app/com.fallentreegames.amazon.quellmemento-1.apk=com.fallentreegames.amazon.quellmemento
package:/data/app/com.fallentreegames.amazon.quellreflect-2.apk=com.fallentreegames.amazon.quellreflect
package:/data/app/com.inxile.BardTale-1.apk=com.inxile.BardTale
package:/data/app/com.lego.starwars.thenewyodachronicles-1.apk=com.lego.starwars.thenewyodachronicles
package:/data/app/com.mg.meteoearth-1.apk=com.mg.meteoearth
package:/data/app/com.pbs.video-1.apk=com.pbs.video
package:/data/app/com.playrisedigital.ttaf-1.apk=com.playrisedigital.ttaf
package:/data/app/com.playrisedigital.ttra-1.apk=com.playrisedigital.ttra
package:/data/app/com.serenity.calmfireplace-1.apk=com.serenity.calmfireplace
package:/data/app/com.the10tons.trouserheart-1.apk=com.the10tons.trouserheart
package:/data/app/com.vectorunit.purple.amazon-1.apk=com.vectorunit.purple.amazon
package:/data/app/com.wukongtv.wkhelper-1.apk=com.wukongtv.wkhelper
package:/data/app/com.zenstudios.ZenPinball.amazon-1.apk=com.zenstudios.ZenPinball.amazon
package:/data/app/org.chromium.youtube_apk-1.apk=org.chromium.youtube_apk
Now copy and past that into notepad and go to Edit, then Replace... and under "Find what" put "package:", and under "replace with" put "adb pull " (make sure there is a space after the word 'pull')
Now click on Replace all, then you will have an output similar to this:
Code:
adb pull /data/app/com.amz.games505.Terraria-1.apk=com.amz.games505.Terraria
adb pull /data/app/com.concretesoftware.pbachallenge_amazonfree-1.apk=com.concretesoftware.pbachallenge_amazonfree
adb pull /data/app/com.digitalx.amazonvirtualfireplace-1.apk=com.digitalx.amazonvirtualfireplace
adb pull /data/app/com.digitalx.amazonvirtualsnowfallhd-1.apk=com.digitalx.amazonvirtualsnowfallhd
adb pull /data/app/com.dotgears.flapfire-1.apk=com.dotgears.flapfire
adb pull /data/app/com.ea.life_full_azn-1.apk=com.ea.life_full_azn
adb pull /data/app/com.edgeway.firefliesambience-1.apk=com.edgeway.firefliesambience
adb pull /data/app/com.edgeway.moonlightocean-1.apk=com.edgeway.moonlightocean
adb pull /data/app/com.edgeway.perfectstorm-1.apk=com.edgeway.perfectstorm
adb pull /data/app/com.edgewaysoft.snowyambience-1.apk=com.edgewaysoft.snowyambience
adb pull /data/app/com.edgewaysoft.stormyambience-1.apk=com.edgewaysoft.stormyambience
adb pull /data/app/com.estrongs.android.pop-1.apk=com.estrongs.android.pop
adb pull /data/app/com.fallentreegames.amazon.quellmemento-1.apk=com.fallentreegames.amazon.quellmemento
adb pull /data/app/com.fallentreegames.amazon.quellreflect-2.apk=com.fallentreegames.amazon.quellreflect
adb pull /data/app/com.inxile.BardTale-1.apk=com.inxile.BardTale
adb pull /data/app/com.lego.starwars.thenewyodachronicles-1.apk=com.lego.starwars.thenewyodachronicles
adb pull /data/app/com.mg.meteoearth-1.apk=com.mg.meteoearth
adb pull /data/app/com.pbs.video-1.apk=com.pbs.video
adb pull /data/app/com.playrisedigital.ttaf-1.apk=com.playrisedigital.ttaf
adb pull /data/app/com.playrisedigital.ttra-1.apk=com.playrisedigital.ttra
adb pull /data/app/com.serenity.calmfireplace-1.apk=com.serenity.calmfireplace
adb pull /data/app/com.the10tons.trouserheart-1.apk=com.the10tons.trouserheart
adb pull /data/app/com.vectorunit.purple.amazon-1.apk=com.vectorunit.purple.amazon
adb pull /data/app/com.wukongtv.wkhelper-1.apk=com.wukongtv.wkhelper
adb pull /data/app/com.zenstudios.ZenPinball.amazon-1.apk=com.zenstudios.ZenPinball.amazon
adb pull /data/app/org.chromium.youtube_apk-1.apk=org.chromium.youtube_apk
Now on each line just delete everything after apk, for exmaple:
Code:
adb pull /data/app/org.chromium.youtube_apk-1.apk=org.chromium.youtube_apk
becomes
Code:
adb pull /data/app/org.chromium.youtube_apk-1.apk
Now just save that file as a bat file and run it from whichever directory you want the files stored in on your PC and it will copy all your apks from your Fire TV (Stick) to your PC. It may take a few minutes.
Hi thanks for your thorough explanation. Just a bit stuck on the last part, how do i save as a .bat?
okay i know how to make a bat, but i'm still unclear what the bat needs to consist of? all the txt from each box above?
hendoben said:
Hi thanks for your thorough explanation. Just a bit stuck on the last part, how do i save as a .bat?
Click to expand...
Click to collapse
Just rename the text file from .txt to .bat
thanks again. i had just edited my post before i realised you replied. is there any chance you could post a sample .txt? just so i know exactly what to include before i make the .bat. as the one i created didn't work.
also got this error 'error more than one device and emulator' after i entered..
Code:
adb shell
hendoben said:
thanks again. i had just edited my post before i realised you replied. is there any chance you could post a sample .txt? just so i know exactly what to include before i make the .bat. as the one i created didn't work.
also got this error 'error more than one device and emulator' after i entered..
Code:
adb shell
Click to expand...
Click to collapse
There I attached a zip file of the text file that I actually found can just save directly as a bat file if you, when saving, select *.* all files and just type in the name and put ".bat" at the end of the name when saving. As far as the error you're getting, just disconnect whatever other devices you have connected that have adb debugging enabled..
Any chance I can get someone to download and pull HBO GO for the fire TV? I have an ADT-1 and comcast is not allowing activation of hbo go on android tv's but will allow it on Fire Tv's so I want to see if I can use the apk from the Fire Tv to get it working. Thanks!
Hello, can someone sideload the Amazon Video apk for me from a Fire TV and make available (public or PM). I would like this install on my nvidia shield TV.
Could someone please extract the following apps so the community can try to use them on Android TV?
All4, ITVHub, Demand 5, RTÉ Player, 3Player, and TG4 .
---------- Post added at 07:52 PM ---------- Previous post was at 07:17 PM ----------
dusf said:
Could someone please extract the following apps so the community can try to use them on Android TV?
All4, ITVHub, Demand 5, RTÉ Player, 3Player, and TG4 .
Click to expand...
Click to collapse
Mod, please delete my post as I am creating a separate thread.
First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...unt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.
So I haven't ever really looked into putting custom roms on my fire stick before so I had to look up what PlayFire was. I haven't had time to mod mine yet but I'm a little confused as to why PlayFire (not upgraded since 2017) would be needed if the LeanBack launcher is already on the rom, Is it just reinstalling it with all the xposed and HDXposed stuff it comes with?
Could you please post or message me your twrp backup I have tried everything and can not get it working tried many times. When I run the script nothing happens still can't use Google play or login to it. Followed the steps to the tee.
Worked without any issues! thanks!
Thank you very much @theflashfromthecw it work great, but do you have a patch for working mic search ?
---------- Post added at 05:04 PM ---------- Previous post was at 04:43 PM ----------
The device is freezig after 3 minutes with the newest gapps and the linkes Google ACC manager. Any solutions ?
Try to install xposed-v87-sdk22-arm.zip with Xinstall and Downgrade option enabled before or adb install -d com.google.android.gsf.login_5.1-1743759-22_minAPI21(nodpi)_apkmirror.com.apk to downgrade if PlayStore update it afterward.
Is this still working? I have tried to get this working on FTV Tank running Lineage, but no luck with sign in..
Thanks!
update: I was able to get it working, I needed to enable developer options, and then root access because the script was not completing (needed for making changes to /system).
Thanks again for putting this together!
theflashfromthecw said:
First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...nt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.
Click to expand...
Click to collapse
Hi.... Will this method work on pre-rooted stock image ROM?
Unable to sign-in
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.
Hi guys, nice work! Will it work on a 1st generation FireTV (box, not stick)?
NihaalMoosa said:
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.
Click to expand...
Click to collapse
You must run
sh /sdcard/PlayFire/LazyNoTouch.sh
no luck
Hi
I am not able to run the script, as I have created a folder called "sdcard" on the root of the internal storage and placed the PlayFire folder there. Furthermore, I used the "sh /sdcard/PlayFire/LazyNoTouch.sh" in ADB Shell, but no luck. Do we need to root Lineage OS before we use the script? If it is, can someone kindly show me a guide, how to root, as I have never done it before.
Flash supersu
https://redirect.viglink.com/?key=e...2-1-t4016981/amp/&ref=https://www.google.com/
In twrp
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
0815hoffi said:
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
Click to expand...
Click to collapse
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).
any advice on how to properly activate recommendations on leanback
everything else works
lars1384 said:
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).
Click to expand...
Click to collapse
would this work with the latest lineage os..?
For me it has not works with the latest.
With
lineage-12.1-20200221-UNOFFICIAL-tank.zip
It has worked.
I Think MicroG support in latest is the Problem maybe.
Cant seem to download tvstock version for the gapps you mentioned. As soon as I select platform and android version.. the tvstock button gets disabled
seems like tvstock is available from android 6.0 onwards for arm platform.
Please help or point me to a compatible gapps zip
Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated
Mhtkmr25 said:
Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated
Click to expand...
Click to collapse
Me too. Seems like opengapps doesn't have a mirror for that one anymore. I tried everything I could think of to search for it too, I even tried to build it from source and failed. But I kept reading every post I could and the best I could come up was finding this link:
https://www.androidfilehost.com/?fid=8889791610682906163
from this post from @diegocr, who is the OP of this build of LOS 12.1 for tank:
https://forum.xda-developers.com/t/rom-unlocked-tank-lineageos-12-1.3961110/post-83220635
It works! Didn't have to mess with any scripts because I couldn't actually find the gapps .zip I needed for those anyway. It's already modified. I just had to reboot into TWRP and flash it.
I'm not sure what the actual tvstock would have had that this doesn't. It does seem stripped down, but that was what I was hoping for when I opened up the thing to short out CLK.