Related
I was trying to root my defy with my macbook. I tried superoneclick, but it doesn't work on mac.
I tried z4root on this website [http://forum.xda-developers.com/showthread.php?t=833953]. But it didn't work for me as well it was stuck with "acquiring root shell". But on the website, it said it's compatible with defy.
Does anyone know how to root defy on a mac
Thanks a lot
Even if you could root your defy using a Mac, you'd still need Windows to run RDS lite.
Sucks, I know... but there it is.
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Being under Linux, I use sbf_flash for flashing and root the phone manually via adb.
Though I don't know about any macos alternatives.
sbf_flash has been updated; there's now a mac os x port, in addition, support has been added for the Defy, Charm and possibly the Atrix.
Click to expand...
Click to collapse
So it's also working for Macos, great.
MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
oh really? thanks a lot
Can u please put down the steps when ur free
MisterWB said:
On my side I get root with my Mac.
I put a binary on my sdcard, next I execute this binary with adb shell from ''Terminal'' to get root.
Regarding sdb flashing, only way I know it's RSD... But it's a win32 exe.
So I use Virtualbox to launch windows over macos.
This allow me to run RSD like if I was under windows. I flash several sbf without pb !!!
It's late now, but I can put details friday if you are interested.
Click to expand...
Click to collapse
Sent from my MB525 using XDA App
Wow! I didn't know about sbf-flash.
Thanks for the heads-up.
My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC
MisterWB said:
My process to obtain root access:
1) connect phone to your mac via usb cable
2) In Finder extract "Getroot.zip" on Desktop for exemple
you should have a Getroot directory now with files inside (su, busybox...)
3) Copy/Paste this "Getroot" directory on root of your sdcard
4) Eject sdcard in Finder
5) push down notification bar on Defy and click "USB..." item
6) Select "none"
7) Check in Defy Settings that "Applications->Developpement->USB debugging" is on
8) On Mac launch Terminal
9) type "adb shell", you should have a "$" prompt
10) type "cd /sdcard/Getroot/"
11) type "sh getroot.sh"
You'll be eject from adb shell, it's normal
12) type again "adb shell", prompt should be "#" now, that mean root privilege !
13) type "cd /sdcard/Getroot/"
14) type "sh copy_rootfile.sh", this copy root file, recovery application and remount script*
15) type "reboot" to reboot phone
16) after reboot don't forget to push down notification bar on Defy and click "USB..." item of your choice
17) Done
Take care that "Settings->Applications->Developpement->USB debugging" mustbe off to boot in recovery mode. In other way you'll get a black screen
Hope I don't make mistake during zipping and writing process !
-----------------------------------------------------
* remount script to use from adb shell or any terminal:
- type "remount rw" to mount /system read-write
- type "remount ro" to mount /system read-only
- type "remount sdcard" to mount /sdcard when usb cable is plug to PC
Click to expand...
Click to collapse
I am kind of stuck, What do u mean by "USB..." for step 5? Is it usb connection? and for step 6 is it "charge only" for "none"?
I typed "adb shell" in terminal and it was like "command not found".
What should I do now? Btw, thanks for helping
Right, step 5 is "USB Connexion"
and step 6 "Charge only", text may change with language and rom version.
Regarding "adb" it's part of Android SDK: http://developer.android.com/sdk/index.html
So you have to download full SDK kit and install it....
...or use adb executable for mac attached below
On my mac I putted it into /usr/bin
1) In Finder put adb.zip into Download directory
2) In Finder Download directory, extract adb.zip, you'll get an "adb" file
3) Open Terminal
4) Go into Download directory
cd ~/Download
5) Copy adb file into /usr/bin with executable permissions
sudo cp adb /usr/bin/ -> and type your session's password
sudo chmod 755 /usr/bin/adb -> and type your session's password
next you can use "adb shell" like any unix command
Keep me inform
I found the link to download sbf_flash for mac
http://blog.opticaldelusion.org/2011/02/sbfflash-updates.html
[A] How to Root Defy Android OS 2.1 on mac
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.
beefinit said:
I tried rooting the defy with z4root and SuperOneClick (using Mono to run it on a mac).
It appears that the z4root no longer works on later firmware updates for the defy, which others confirmed on another forum. For me it got stuck trying to run exploits. Similarly, SuperOneClick hung up during the "waiting for device" phase.
This other thread on xda did work and was super easy to do and I recommend it:
[ROOT] G2x Easy Root for Mac and Linux
http://forum.xda-developers.com/showthread.php?t=1048309
I checked it with "Root Checker Basic" from app store and it is indeed rooted.
Click to expand...
Click to collapse
I followed the simple directions in the thread recommended by beefinit. The root.command script that comes with the G2xRootMacLinux_v0.5.zip package appears to have successfully rooted my Defy. The script is designed for a Tmobile LG G2x, but is based on SuperOneClick 1.8, so the fact that is seems to work for the Defy is not that surprising.
Here is the terminal log from when I ran the script:
Last login: Thu May 17 10:41:29 on console
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
/Downloads/G2xRootMacLinux_v0.5/root.command ; exit;
Checking for connected device...
Pushing temporary root exploint (psneuter) to device...
2604 KB/s (585731 bytes in 0.219s)
Running psneuter on device...
property service neutered.
killing adbd. (should restart in a second or two)
Waiting for device...
Remounting /system read/write...
remount succeeded
Pushing su to /system/bin/su...
100 KB/s (26324 bytes in 0.255s)
Pushing busybox to /system/bin/busybox...
3162 KB/s (1062992 bytes in 0.328s)
Installing Superuser.apk android application...
775 KB/s (196521 bytes in 0.247s)
Removing psneuter from device...
Rebooting device...
Once device has rebooted you should be rooted.
Press Enter when you're ready to quit:
I'm very new at rooting phones but Superuser app is now installed and I've also installed ROM Toolbox Pro and confirmed that I can get a # prompt via it's Terminal Emulator.
My Defy is an unlocked MB525, Android 2.2.1, System version 34.4.9.MB525.T-Mobile.en.US, Kernel 2.6.32.9-g8431013, Build number 3.4.2-107_JDN-9
Hello there
so i rooted my kindle on the 6.2.1 and i had no problem
after that i used BUrito 2 to root 6.2.3
and strangely the super user app didnt work
so when the 6.3 was released updated my device and followed the method below
http://forum.xda-developers.com/showthread.php?p=24124828#post24124828
my device got stuck on yellow triangle and got an error on the cmd waiting for device .
so i searched that and fixed it using this method
http://forum.xda-developers.com/showthread.php?t=1422832
and continued using the ADB command .
and this didnt work .
i tried the KFU (witch is a great tool)
didn't also help
whenever i load the super user app it crash and give me an error
"the application super user(process com.noshufu.android.su) has stopped unexpectedly.please try again and a button Force close
tried to run SU Update fixer
it get stuck on gaining root access result fail solution download and flash and update zip fromandroissu.com
am not sure now why i cant root my device
can some expert direct me please
am thinking to reset to factory default and test but am not sure if that will work and i have FBmode on my device i dont want to lose my apps either .
would suggest to redo according to jcases thread and take care to not miss a point - maybe redownload the superuser.apk
and which version of kfu ? 0.9.4 ?
b63 said:
would suggest to redo according to jcases thread and take care to not miss a point - maybe redownload the superuser.apk
Click to expand...
Click to collapse
i tired that didnt help and also downloaded the superuser.apk and test didnt help much
[/QUOTE] and which version of kfu ? 0.9.4 ?[/QUOTE]
0.9.3
marakji said:
i tired that didnt help and also downloaded the superuser.apk and test didnt help much
0.9.3
Click to expand...
Click to collapse
0.9.3 uses the method for 6.2.2
0.9.4 uses the method for 6.3
would suggest to retry with the new version
b63 said:
0.9.3 uses the method for 6.2.2
0.9.4 uses the method for 6.3
would suggest to retry with the new version
Click to expand...
Click to collapse
just tested it didnt work
i acctually reinstall ed the ADB driver from the package and KFU couldnt find my device add another line to ADV_USB.INI 0x18d1
and installed the driver
and test KFU result
permanent root has been installed.
test my device still not rooted sighsssss bummer
at first kindle fire utility 0.9.4. did not work for me either and what I had to do was uninstall the drivers for the kindle fire, then plug it back in and let it install again. After that kfu worked perfect for me. I installed twrp, then I rooted, then I installed firefirefire
marakji said:
just tested it didnt work
i acctually reinstall ed the ADB driver from the package and KFU couldnt find my device add another line to ADV_USB.INI 0x18d1
and installed the driver
and test KFU result
permanent root has been installed.
test my device still not rooted sighsssss bummer
Click to expand...
Click to collapse
any error messages that can give us a hint ?
status of your drivers ?
from you'r first post it seems the driver for fastboot mode is'nt working
b63 said:
any error messages that can give us a hint ?
status of your drivers ?
from you'r first post it seems the driver for fastboot mode is'nt working
Click to expand...
Click to collapse
test of adb from my CMD:
C:\KindleADB>adb version
Android Debug Bridge version 1.0.26
----------------------------------------------------
From Device manager
Android Compsite ADB interface
Driver Provider : Google.Inc
Driver Date 12/6/2010
Driver Version 4.0.0.0
.Android installed in the correct location
------------------------------------------------------
KFU root msgs
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
3177 KB/s (510876 bytes in 0.157s)
The kindle has been told to reboot in Fastboot Mode.
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
< waiting for device >
downloading 'boot.img'... OKAY [ 2.662s]
booting... OKAY [ 0.003s]
finished. total time: 2.666s
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Recovery Bootmode.
Please wait...
<idme> write 5002 to offset 0x1000
214 KB/s (22364 bytes in 0.102s)
mv: can't rename '/system/bin/check_rooted': No such file or directory
<idme> write 4000 to offset 0x1000
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
Press any key to continue . . .
then the device reboot and nothing happen
----------------------------------------------
am not sure what i can trace down ????
puh - kfu seems to work perfect besides "mv: can't rename '/system/bin/check_rooted': No such file or directory"
is the kf booted to twrp at this point ?
the error seems to be because the file is allready renamed
the rooting process seem to be fine
only a idea : try to go to settings - apps - superuser and clear cache and data
then reboot - maybe this helps ...
same problem
I'm having the same problem using KFU 0.9.4 and 0.9.5. Root seems to work perfectly, but when the device reboots I do not have root. I don't even have superuser in my apps. When trying to install google apps I get "permission denied" for the last three apps due to not having root.
help?
Yeah, KFU 0.9.5 doesn't seem to be fully baked yet on 6.3 either. I tried installing the Google Apps and ran into permission issues also.
Here's what I got at the very end:
failed to copy 'apps\system\vending.apk' to '/system/app/vending.apk': Permissio
n denied
failed to copy 'apps\system\GoogleCalendarSyncAdapter.apk' to '/system/app/Googl
eCalendarSyncAdapter.apk': Permission denied
failed to copy 'apps\system\GoogleContactsSyncAdapter.apk' to '/system/app/Googl
eContactsSyncAdapter.apk': Permission denied
Well, I have the same problem drumaster12 has, i used KFU v0.9.5 the rooting process went smoothly but superuser wasn't there plz someone reply and thx for all of you guys.
FYI... according to the development thread, an updated version of KFU is forthcoming. So at the moment the best course of action is to wait and see.
http://forum.xda-developers.com/showpost.php?p=24275392&postcount=1164
b63 said:
http://forum.xda-developers.com/showpost.php?p=24275392&postcount=1164
Click to expand...
Click to collapse
sorry to say that didnt help either
i believe tons of people having the same problem
the problem is
C:\KindleADB>
C:\KindleADB>adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
mv: can't rename '/system/bin/check_rooted': No such file or directory
how can we get over this ?
marakji said:
sorry to say that didnt help either
i believe tons of people having the same problem
the problem is
C:\KindleADB>
C:\KindleADB>adb shell mv /system/bin/check_rooted /system/bin/check_rooted.bak
mv: can't rename '/system/bin/check_rooted': No such file or directory
how can we get over this ?
Click to expand...
Click to collapse
that error can be ignored because the file is allready renamed
for not rooting maybe see here:
http://forum.xda-developers.com/showpost.php?p=24291791&postcount=1184
and here:
http://forum.xda-developers.com/showpost.php?p=24286782&postcount=1180
6.3 root method
First off long time lurker first time poster here.
I got one of these kindles from the sale and was able to get root. I've unrooted and tried again and got root again so there are two different problems. 1 - Sometime superuser.apk doesn't get installed and 2 - The Play market doesn't get installed. I used 2 different methods to over come this. hopefully they'll help.
First steps to root with Kindle Fire Utility 0.9.5
1 - With the kindle not connected run the install_drivers.bat
2 - Connect the kindle and push disconnect when it comes up
3 - Run option 2 - "Install Permanent Root with Superuser"
4 - Run option 5 - "Install Latest FireFireFire"
5 - Run option 3 or 4 - "Install Latest TWRP/Clockwork Recovery"
Once those 5 steps are done you have 2 options to get superuser and play market
Option 1 (Easiest)
Since you now have FireFireFire and a custom recovery simply wipe and flash pre-rooted 6.3 rom This is the one I used [ROM] Stock rooted 6.3
Once that is flashed run Kindle Fire Utility again and in the Extra menu run option 5 - Mount Read/Write
Then run option 1 - Install Google Apps / Go Launcher EX
This is the easiest method the rom is already rooted and has busybox seems pretty fast too.
Option 2 (More involved)
After the initial 5 steps:
1a - run the extras option and Install google Apps / Go launcher EX (the last three will fail but that's ok)
1b - close Kindle Fire Utility and open a command prompt (start button type cmd)
2 - In the command prompt type: "cd " now drag and drop the tools folder that is inside the Kindle Fire Utility folder. (make sure you put a space after cd before you drop the tools folder on the command prompt.) This will auto fill in the path to tools folder. Push enter.
3 - Type "adb install " Drag and drop Superuser.apk located inside the files folder of kindle fire utility. This auto fills the path to Superuser.apk and push enter
4 - Now you need to install a root file explorer of your choice. I used ES File Explorer. *Important* the version of ES File Explorer from the amazon market is too old and will not work. Go To: http://www.estrongs.com/en/download.html and downloaded the latest version.
4b - Install the .apk you just downloaded by typing "adb install " and drag the .apk from your downloads folder and drop it on the command prompt and push enter
5 - Now you need to enable your kindle to drag and drop files to it. On the kindle: Tap the top status bar and tap "USB is Connected"
6 - go to the Kindle Fire Utility directory -> apps -> system. In this folder there are three .apk's GoogleCalendarSyncAdapter.apk GoogleContactsSyncAdapter.apk and Vending.apk Copy all three to the root of your "sdcard" on your kindle. (Drag and drop to your kindle)
7 - On kindle tap disconnect. You should see ES File Explorer icon on your carosel Tap to open it. In ES File explorer Tap menu at the bottom and tap settings.
8 - Under "Path settings" Check the box "Up to Root"
9 - Under "Root settings" Check the box "Root Explorer" Tap "yes" on the popup and tap "allow" on the super user window.
10 - Under "Root settings" check "Mount File System"
11 - now your ready to copy the files. Tap back to go back to the sdcard. Tap "Select" on the top toolbar. Select by taping the three .apks you copied over. Once all three are selected Tap "Copy" on the top toolbar
12 - Tap "Up" on top toolbar. Tap "system". Tap "app" and Finally tap "Paste" on top toolbar.
13 - Reboot your kindle and you should now have the Market working on your kindle.
Note this is what worked for me. I've done it both ways as well as rooting with out Kindle Fire Utility and just jcase's method. Regardless of the method to root one of these two methods were required to get market running.
Hope this helps someone.
ndpete, like I said in the other thread, SuperUser worked fine, your version of ES File Explorer worked fine, but I still get the permissions issues when installing Market. I'm at my wit's end here.
ok, this is funny.
i got the 6.3 update so I've lost the root and this is confirmed by root explorer. But:
.- i can install apps from the market
,- i can watch videos from the Amazon service.
any ideas?
I mean, I don't need to root anymore, since everything works just fine.
ndpete said:
First off long time lurker first time poster here.
I got one of these kindles from the sale and was able to get root. I've unrooted and tried again and got root again so there are two different problems. 1 - Sometime superuser.apk doesn't get installed and 2 - The Play market doesn't get installed. I used 2 different methods to over come this. hopefully they'll help.
First steps to root with Kindle Fire Utility 0.9.5
1 - With the kindle not connected run the install_drivers.bat
2 - Connect the kindle and push disconnect when it comes up
3 - Run option 2 - "Install Permanent Root with Superuser"
4 - Run option 5 - "Install Latest FireFireFire"
5 - Run option 3 or 4 - "Install Latest TWRP/Clockwork Recovery"
Once those 5 steps are done you have 2 options to get superuser and play market
Option 1 (Easiest)
Since you now have FireFireFire and a custom recovery simply wipe and flash pre-rooted 6.3 rom This is the one I used [ROM] Stock rooted 6.3
Once that is flashed run Kindle Fire Utility again and in the Extra menu run option 5 - Mount Read/Write
Then run option 1 - Install Google Apps / Go Launcher EX
This is the easiest method the rom is already rooted and has busybox seems pretty fast too.
Option 2 (More involved)
After the initial 5 steps:
1a - run the extras option and Install google Apps / Go launcher EX (the last three will fail but that's ok)
1b - close Kindle Fire Utility and open a command prompt (start button type cmd)
2 - In the command prompt type: "cd " now drag and drop the tools folder that is inside the Kindle Fire Utility folder. (make sure you put a space after cd before you drop the tools folder on the command prompt.) This will auto fill in the path to tools folder. Push enter.
3 - Type "adb install " Drag and drop Superuser.apk located inside the files folder of kindle fire utility. This auto fills the path to Superuser.apk and push enter
4 - Now you need to install a root file explorer of your choice. I used ES File Explorer. *Important* the version of ES File Explorer from the amazon market is too old and will not work. Go To: http://www.estrongs.com/en/download.html and downloaded the latest version.
4b - Install the .apk you just downloaded by typing "adb install " and drag the .apk from your downloads folder and drop it on the command prompt and push enter
5 - Now you need to enable your kindle to drag and drop files to it. On the kindle: Tap the top status bar and tap "USB is Connected"
6 - go to the Kindle Fire Utility directory -> apps -> system. In this folder there are three .apk's GoogleCalendarSyncAdapter.apk GoogleContactsSyncAdapter.apk and Vending.apk Copy all three to the root of your "sdcard" on your kindle. (Drag and drop to your kindle)
7 - On kindle tap disconnect. You should see ES File Explorer icon on your carosel Tap to open it. In ES File explorer Tap menu at the bottom and tap settings.
8 - Under "Path settings" Check the box "Up to Root"
9 - Under "Root settings" Check the box "Root Explorer" Tap "yes" on the popup and tap "allow" on the super user window.
10 - Under "Root settings" check "Mount File System"
11 - now your ready to copy the files. Tap back to go back to the sdcard. Tap "Select" on the top toolbar. Select by taping the three .apks you copied over. Once all three are selected Tap "Copy" on the top toolbar
12 - Tap "Up" on top toolbar. Tap "system". Tap "app" and Finally tap "Paste" on top toolbar.
13 - Reboot your kindle and you should now have the Market working on your kindle.
Note this is what worked for me. I've done it both ways as well as rooting with out Kindle Fire Utility and just jcase's method. Regardless of the method to root one of these two methods were required to get market running.
Hope this helps someone.
Click to expand...
Click to collapse
this is great! thanks so much for the guide!
also a quick question... this worked for me but i still have a limited (i.e can't download DC comics, draw something, etc.. etc..) android market (or play market) for some reason. is there any way to change that?
Hi,
I recently got a new Kindle fire and tried to root it.
I followed the instructions given in this post.
http://forum.xda-developers.com/showthread.php?t=1568340
However, my kindle fire seems to be stuck in an infinite boot loop after first step itself.
Here are the step I followed (I am using Windows 7 32bit).
1. Installed android sdk.
2. Updated the Kindle driver to install "android abd composite interface"
3. Downloaded all the required files in the platform-tools folder
Required files:
fbmode.zip - http://forum.xda-developers.com/show....php?t=1414832
twrp2 - http://teamw.in/project/twrp2/79
su - http://dl.dropbox.com/u/8699733/kindlefire/su
firefirefirefire http://forum.xda-developers.com/show....php?t=1369405
fastboot + adb for your OS of choice.
4. Followed following commands:
unzip fbmode.zip
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
5. After this, my kindle fire seems to have stuck in an infinite boot loop.
- It starts up only when a USB cable is connected.
- Power light is orange and not green
- It starts up Kindle Fire logo comes up, then shuts down again
- My computer is not detecting any device, probably because KF is in an infinite boot loop
- When I run adb devices -- no devices show up
- When I run fastboot command [fastboot -i 0x1949 flash bootloader .....] it says "waiting for devices"
- When I remove the USB cable from KF, It doesn't powers on (even after long pressing the power button).
- I tried many things posted on different forums on two laptops (Windows 7 32 bit as well as 64 bit) and using different USB cables but nothing worked.
- Only thing I haven't tried is Factory cable as I don't have it and don't have money to buy it.
PLEASE HELP!!
http://forum.xda-developers.com/showthread.php?t=1623244
Superuser not working
Thanks for the help with the charging issue Kinfauns!!!
I charged my kindle fire using stock charger and finally rooted it.
However, I am still not able to install android market on my KF.
After rooting Kindle (followed all the steps given in the thread), I installed Superuser.apk.
Then to install android market, I installed root explorer and downloaded Kindle Fire android market zip file. (followed instructions from one of the NAT3MIL's video on youtube).
First step is to install googleServicesFramework.apk file, which I did.
The next step is to move market.apk file to system/apps folder. However, when I tried doing that, I got a warning:
"Your phone doesn't appear to be rooted. This is requires in order to change or delete protected files such as this ......"
I don't understand why is it saying so as I have followed all the steps in the thread to root my KF?
How to check if the KF is really rooted?
Are there any settings to be changed in the superUser.apk?
Please help!!
Thanks a ton!!
Superuser not working
One more thing.
when I tried to update SU binary file,
I got following:
Downloading manifest .. OKAY!
parsing manifest.. Okay!
Latest Version = 3.0.3.2
Checking installed version .. legacy
Fixing database .. okay!
checking for busybox .. not found
Downloading custom busybox .. okay!
checking md5sum ... okay!
checking current install path .. fail!
Failed to find current installed su binary. Update cannot continue.
Does this mean I have to re-root the KF or just install the su binary file? how to do that?
Thanks!
Download the latest kindle fire utility and rerun it for permanent root.
Known Tricks
If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Please note: If your device can't be seen in fastboot mode, please make sure to install the drivers packaged with this, as it will show up afterwards. You can use the install_drivers.bat with the device plugged in for this.
Copied from the instructions of the kindle fire utility
Above are the tricks if you get stuck but after root install twrp then install fff
I would assume that your not rooted sounds that way to me.
By the way the yellow triangle will be replaced with the new bootloader a white kindle and a blue fire this will be considered the yellow triangle in the description. Good luck
Install permanent root
Install twrp
Install fff
All should be the newest at this point hopefully
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
I believe so the worst that could happen is it could fail if the file already exists but let's hope it goes fine
tanwar said:
Thanks ThePooch.
So, apparently I have to re-root my KF as for some reason it was not rooted correctly. Right?
Click to expand...
Click to collapse
You don't necessarily have to let KFU do its entire "rooting" process.
If you can get into recovery and you are comfortable with adb, you can follow the "Rooting the stock software" section in this guide...
http://forum.xda-developers.com/showthread.php?t=1638452
to push the 'su' binary into the /system partition and set ownership/permissions.
If you are not comfortable with that, you can use KFU, but it will be doing a lot of extraneous things that you probably don't need.
Under extras you will put on Google frame work and go launcher after you have confirmed bootloader recovery and root note that the market can only be seen using go launcher not the kindle one.
---------- Post added at 12:32 AM ---------- Previous post was at 12:13 AM ----------
The easiest way to test root is to download an app that will request root permissions like root explorer for instance if you open the app and you don't see a dialogue pop up requesting permission its very likely that it isn't rooted.
Read-Only file system
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
nevermind I see your on windows 7 like me. adb shell mount system will mount system to read/ write
its all in kinfauns post you just need to be it recovery to execute the commands I believe I would paste it here but its just as easy to read them from there
adb shell chmod 6755 /system/xbin/su not 755 you can probably safely copy and paste the commands from his post right into cmd he has it written up very nicely
tanwar said:
Thanks Kinfauns and ThePooch for tips.
@kinfauns, I tried following the steps given in "Rooting the stock software" section of the given link.
http://forum.xda-developers.com/showthread.php?t=1638452
However, when I tried to push su binary file to system folder
adb push C:\kfu\software\su /system/xbin/
I got following message:
failed to copy 'su' to 'system/xbin/su': Read-only file system.
How can I change the permissions of the folder to copy su file?
I tried using shell command:
adb shell chmod 755 /system
However, I got the same message again "Read-only file system"
Please help!!
Click to expand...
Click to collapse
I think you may be trying to do this while booted into the system software. That won't work because you don't have root access there and you won't be able to mount (or remount) a partition without those privileges. The rest of it won't work without R/W access to the partition, as you've already seen.
To be clear, the device needs to be booted into recovery (TWRP or CWMR) where you do have root privileges. Make sure you start with step one to get the system partition mounted. If successful, "mount" will provide no output.
(Note before you begin: If you have a SHIELD TV 2017, you will need a quality Male-to-Male USB Type A cable to connect your SHIELD TV to a PC. If you have a SHIELD TV 2015 or a SHIELD TV Pro, you may be able to just use a regular micro USB cable, because those two models have a micro USB port)
A. Download these files to your PC:
Download the Android SDK Platform-Tools
Download the Official NVIDIA SHIELD family Windows USB Drivers
Download the Magisk Manager APK (This is the latest version as of the time of writing)
Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model
(You will need to register for a Developer Account if you don't already have one. Flashing the wrong image will BRICK your device)
B. Setting up Android SDK Platform-Tools on your PC:
On your PC, extract the Android SDK Platform-Tools somewhere where you can find them
Add the platform-tools folder to PATH in the Windows System Environment Variables (Instructions HERE or HERE)
C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:
On your SHIELD TV, enable developer options and debugging (Instructions HERE)
Using a Male-to-Male USB Type-A Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC
On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them
Open Device Manager and find the new device
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
adb devices
On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access
On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)
Boot the SHIELD TV into bootloader/fastboot mode by typing the command:
Code:
adb reboot bootloader
(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)
On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
fastboot devices
The Command Prompt should show the serial number of your SHIELD TV
D. Unlocking the bootloader on your SHIELD TV (CAUTION: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)
Plug the NVIDIA SHIELD TV Game Controller or a USB Keyboard into the USB port closest to the HDMI port on your SHIELD TV
In bootloader/fastboot mode on your SHIELD TV, select "Unlock Bootloader", read the message and confirm
(Use the Y and X buttons to scroll UP and DOWN, and the A button to CONFIRM selection, if your button presses aren't doing anything you need to reboot the SHIELD TV into bootloader/fastboot mode with the Controller or Keyboard already plugged in)
On your PC, open a Command Prompt and reboot your SHIELD TV to the OS by typing:
Code:
fastboot reboot
This process only needs to be done once per device and you will not have to unlock the bootloader again for subsequent updates
(From now on while your bootloader is unlocked, your SHIELD TV will display a warning message when it first boots saying that the system cannot check for corruption. This is perfectly normal and the boot process will resume automatically after a few seconds. There is no need to relock your bootloader unless you are selling the device or something. NEVER lock the bootloader if you have anything other than 100% stock full RECOVERY Image installed. Never even try it.)
E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img
On your PC, extract the NVIDIA SHIELD Experience Upgrade v7.2 Image that you downloaded to somewhere where you can find it
Find the boot.img file in the folder that you extracted it to
Open a Command Prompt and type:
Code:
adb push boot.img /storage/emulated/0/Download/
Install Magisk Manager by typing 'adb install [path-to-magiskmanagerapk]' example:
Code:
adb install C:\MagiskManager-v6.1.0.apk
On your SHIELD TV, open Magisk Manager [Settings > Device > Apps > Magisk Manager > Open]
(The Magisk Manager App Interface is not designed to be operated with an Android TV Remote so I suggest you install the NVIDIA SHIELD TV app on your phone. Once paired with your SHIELD TV, the app has an option to let you use a virtual mouse to navigate and interact with your SHIELD TV. Alternatively, you can plug a USB Mouse into the USB port closest to the HDMI port on your SHIELD TV)
If Magisk Manager automatically pops up and asks you if you would like to Install Magisk, select Cancel
Make sure the "Preserve AVB 2.0/dm-verity" option is checked, and then select "Install"
Select "Patch Boot Image File"
Using the Virtual Mouse on the NVIDIA SHIELD TV remote app on your phone, or a USB Mouse, navigate to the "Download" folder on your internal storage and select the boot.img file that you copied over then click Open
Magisk Manager will take a few moments to patch the boot.img (pay attention to the message in the console about the path to the patched_boot.img - It should be "/storage/emulated/0/Download/patched_boot.img"
On your PC, in the Command Prompt type:
Code:
adb pull /storage/emulated/0/Download/patched_boot.img
F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:
On your PC, navigate to the folder where you extracted the NVIDIA SHIELD Experience Upgrade v7.2 Image
Find the boot.img and rename it to boot.img.bak
Rename the patched_boot.img to boot.img
Open a Command Prompt and type:
Code:
adb reboot bootloader
Once the SHIELD TV is in bootloader/fastboot mode, type:
Code:
flash-all.bat
(It will take a few minutes for the flashing process to finish and then the SHIELD TV will automatically reboot to the OS)
Optional Stuff and Additional Information:
Disable Auto-Upgrades by going to [Settings > Device > About > System upgrade > Auto-upgrade]
Enable Full OTA's instead of Partial/Differential by going to [Settings > Preferences > Developer options > Provide full system upgrades]
(It is the very last option at the bottom and this is very important when using a rooted device and modifications to the System partition are likely)
If you want to upgrade to a new OTA update with root without waiting on NVIDIA to post the Developer/Recovery images, the downloaded OTA file is in
Code:
/data/data/com.nvidia.ota/app_download
(You will need a root file explorer to be able to access this directory)
You can extract the boot.img from the OTA zip and patch it using the same method described in step E.5 through E.10
You can then install the OTA the normal way [Settings > Device > About > System upgrade > Check for upgrade]
(Make sure you have copied the OTA zip or extracted the boot.img to somewhere on your Internal Storage like "/storage/emulated/0/Download" BEFORE you install the OTA because the system will delete the file in "/data/data/com.nvidia.ota/app_download" when it installs the update and you will be unable to get it after that)
Copy the patched_boot.img that you made with Magisk to your PC
Reboot to bootloader/fastboot mode with:
Code:
adb reboot bootloader
Manually flash just the Magisk Patched boot:
Code:
fastboot flash boot patched_boot.img
Manually reboot back to the OS with:
Code:
fastboot reboot
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.
whiteak said:
Hey mate, just curious if you have full root access, eg, can you uninstall system apps or delete their folders in system/apps, only asking as I also thought I had gained full root access with patching the boot.img with Kantjers version of Magisk, but when I try to uninstall a system app or try and delete their respective folders, even though it appears in Magisk that I have full root access, when I try to uninstall or delete a system app folder, I actually don't have full root access.
Click to expand...
Click to collapse
I don't modify the system partition if I can avoid it. I just disable System Apps if I want them gone; however, I am fully confident that I could delete anything in /system if I wanted to. Is /system mounted as +rw? Not all Root File Managers are created equal. I recommend Root Explorer. It is not the most modern and feature rich file manager, but when it comes to Root File Managers specifically, I haven't found any other that can compare.
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.
whiteak said:
Thanks for the reply, not a big deal, was just curious if you actually did have full root access as it appears I do as well until I actually need it to do something like delete a system app etc. I may try flashing your patched boot.img and see if I get the same results as my patched boot.img, may just come down to the fact that I'm using Kantjers version of Magisk etc, wouldn't think it would be any different, but never know I guess until I try. Thanks again.
Click to expand...
Click to collapse
I would test it for you if I had a system.img for v7.2.1 that I could reflash real quick. I just don't feel like flashing v7.2.0 then updating to v7.2.1 again to restore an unmodified system partition.
ACiDxCHRiST said:
A. Download these files to your PC:
Download the Android SDK Platform-Tools HERE
Download the Official NVIDIA SHIELD family Windows USB Drivers HERE
Download Magisk Manager APK (Link to latest version at time of writing is HERE)
Download the ***CORRECT*** NVIDIA SHIELD Experience Upgrade v7.2 Image for your model HERE
(Flashing the wrong boot.img will BRICK your device You will need to register for a Developer Account if you don't already have one)
B. Setting up Android SDK Platform-Tools on your PC:
On your PC, extract the Android SDK Platform-Tools somewhere where you can find them
Add the platform-tools folder to PATH in the Windows System Environment Variables (Instructions HERE)
C. Installing the Official NVIDIA SHIELD family Windows USB Drivers on your PC:
On your SHIELD TV, enable developer options and debugging (Instructions HERE)
Using a Male Type-A to Male Type-A USB Cable, connect the USB port further away from the HDMI port on your SHIELD TV to your PC
On your PC, extract the Official NVIDIA SHIELD family Windows USB Drivers somewhere where you can find them
Open Device Manager and find the new device
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
adb devices
On your SHIELD TV, a prompt will pop up asking you to allow ADB access from your computer. Check the box to remember your selection and then Grant Access
On your PC, the Command Prompt should show the serial number of your SHIELD TV
(You may have to run the 'adb devices' command again since it may have timed out the first time waiting on you to authorize the ADB connection on the SHIELD TV)
Boot the SHIELD TV into bootloader/fastboot mode by typing the command:
Code:
adb reboot bootloader
(Alternatively, you can enter bootloader/fastboot mode by following the instructions HERE)
On your PC, open the Device Manager again and find the new device (it will probably have an error with a yellow triangle)
Right-click it and select Update driver
Select "Browse my computer for driver software"
Input the path to the folder where you extracted the Official NVIDIA SHIELD family Windows USB Drivers earlier (make sure the "Include subfolders" option is checked)
Click Next and Install the Driver (if there is more than one option, select the one NOT relating to ADB or Android Device Bridge)
Open a Command Prompt and type:
Code:
fastboot devices
The Command Prompt should show the serial number of your SHIELD TV
D. Unlocking the bootloader on your SHIELD TV (WARNING: THIS WILL WIPE YOUR DATA AND FACTORY RESET YOUR SHIELD TV)
Plug the NVIDIA SHIELD TV Game Controller or a USB Keyboard into the USB port closest to the HDMI port on your SHIELD TV
In bootloader/fastboot mode on your SHIELD TV, select "Unlock Bootloader", read the message and confirm
(Use the Y and X buttons to scroll UP and DOWN, and the A button to confirm selection, if your button presses aren't doing anything you need to reboot the SHIELD TV into bootloader/fastboot mode with the Controller or Keyboard already plugged in)
On your PC, open a Command Prompt and reboot your SHIELD TV to the OS by typing:
Code:
fastboot reboot
E. Installing Magisk Manager on your SHIELD TV and Patching your boot.img
On your PC, extract the NVIDIA SHIELD Experience Upgrade v7.2 Image that you downloaded to somewhere where you can find it
Find the boot.img file in the folder that you extracted it to
Open a Command Prompt and type:
Code:
adb push boot.img /storage/emulated/0/Download/
Install Magisk Manager by typing 'adb install [path-to-Magisk-Manager-APK]' example:
Code:
adb install C:\MagiskManager-v6.1.0.apk
On your SHIELD TV, open Magisk Manager [Settings > Device > Apps > Magisk Manager > Open]
(The Magisk Manager App Interface is not designed to be operated with an Android TV Remote so I suggest you install the NVIDIA SHIELD TV app on your phone. Once paired with your SHIELD TV, the app has an option to let you use a virtual mouse to navigate and interact with apps on your SHIELD TV. Alternatively, you can plug in a USB Mouse into the USB port closest to the HDMI port on your SHIELD TV)
If Magisk Manager automatically pops up and asks you if you would like to Install Magisk, select Cancel
Make sure the "Preserve AVB 2.0/dm-verity" option is checked, and then select "Install"
Select "Patch Boot Image File"
Using the Virtual Mouse on the NVIDIA SHIELD TV remote app on your phone, or a USB Mouse, navigate to the "Download" folder on your internal storage and select the boot.img file that you copied over then click Open
Magisk Manager will take a few moments to patch the boot.img (pay attention to the message in the console about the path to the patched_boot.img - It should be "/storage/emulated/0/Download/patched_boot.img"
On your PC, in the Command Prompt type:
Code:
adb pull /storage/emulated/0/Download/patched_boot.img
F. Installing Magisk rooted SHIELD Experience Upgrade v7.2 on your SHIELD TV:
On your PC, navigate to the folder where you extracted the NVIDIA SHIELD Experience Upgrade v7.2 Image
Find the boot.img and rename it to boot.img.bak
Rename the patched_boot.img to boot.img
Open a Command Prompt and type:
Code:
adb reboot bootloader
Once the SHIELD TV is in bootloader/fastboot mode, type:
Code:
flash-all.bat
(It will take a few minutes for the flashing process to finish and then the SHIELD TV will automatically reboot to the OS)
Optional Stuff and Additional Information:
Disable Auto-Upgrades by going to [Settings > Device > About > System upgrade > Auto-upgrade]
Enable Full OTA's instead of Partial/Differential by going to [Settings > Preferences > Developer options > Provide full system upgrades]
(It is the very last option at the bottom and this is very important when using a rooted device and modifications to the System partition are likely)
If you want to upgrade to a new OTA update with root without waiting on NVIDIA to post the Developer/Recovery images, the downloaded OTA file is in
Code:
/data/data/com.nvidia.ota/app_download
(You will need a root file explorer to be able to access this directory)
You can extract the boot.img from the OTA zip and patch it using the same method described in step E.5 through E.10
You can then install the OTA the normal way [Settings > Device > About > System upgrade > Check for upgrade]
(Make sure you have copied the OTA zip or extracted the boot.img to somewhere on your Internal Storage like "/storage/emulated/0/Download" before you install the OTA because the system will delete the file in "/data/data/com.nvidia.ota/app_download" when it installs the update and you will be unable to get it after that)
Copy the patched_boot.img that you made with Magisk to your PC
Reboot to bootloader/fastboot mode with:
Code:
adb reboot bootloader
Manually flash just the Magisk Patched boot:
Code:
fastboot flash boot patched_boot.img
Manually reboot back to the OS with:
Code:
fastboot reboot
Click to expand...
Click to collapse
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >
sconnyuk said:
Thankyou ever so much for putting this together but after following exactly what you said in this guide this is what i get:
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 10.295s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.641s
< waiting for any device >
Click to expand...
Click to collapse
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0
If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.
Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.
ACiDxCHRiST said:
Do you have a 2015 or a 2017 SHIELD TV? Assuming you didn't edit that directory name, it should be nv-recovery-image-shield-atv-2017-7.2.0
If you have a 2017 and did manage to flash that image without an error, it would have bricked your SHIELD TV.
Do you still have Minimal ADB installed? I kind of feel like your fastboot.exe is outdated. I feel like your Minimal ADB install is registered to PATH and whenever a command calls fastboot, it is running the outdated fastboot in your Minimal ADB install.
Click to expand...
Click to collapse
I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.
im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it. Also i can adb push/pull/install no problems.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.
sconnyuk said:
I have 2017 Shield TV 16gb, which is on stock 7.2.1
I am using platform tools you suggested previously.
im quite sure im downloading the correct version, yes i do rename certain folders when i extract (just like i did with platform-tools to platform tools etc.
Im wondering if because im using standard usb 2.0 a to a cable is problem ? , aswell as both my laptop and desktop computers are older usb 2.0 models?
Both cables i have are usb 2.0 a to a but never had problems using with other devices including amazon fire tv 2 4k box when i had to recover it.
I have tried selecting unlock bootloader again just to triple check its unloacked and it reports bootloader is already un locked.
Im running out of ideas to be honest, quite the nightmare im having.
Click to expand...
Click to collapse
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.
Also try running with an elevated Command Prompt with admin rights.
ACiDxCHRiST said:
I don't see USB 2.0 being an issue. You could try locking then unlocking your bootloader again.
Also try running with an elevated Command Prompt with admin rights.
Click to expand...
Click to collapse
Yes i always use admin rights with CMD.
I will try re locking and unlocking again later today. (i cant see how nobody else has had issues like mine)
Thanks, il report back.
---------- Post added at 09:00 AM ---------- Previous post was at 08:36 AM ----------
Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >
sconnyuk said:
Just tried re locking my bootloader then unlocking again and get same output:
Just for your info the download im using is 'nv-recovery-image-shield-atv-2017-7.2.0.zip' like i said i had a few downloaded alreadyh so just renamed it.
C:\Users\sconn\nv-recovery-image-shield-atv-7.2.0>flash-all.bat
Sending 'staging' (6436 KB) FAILED (Write to device failed in SendBuffer() (Unknown error))
Finished. Total time: 6.297s
Sending 'boot' (14115 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 15.853s
< waiting for any device >
Click to expand...
Click to collapse
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.
ACiDxCHRiST said:
I googled your error and I found a post that said changing cables fixed the problem. So that is at least one piece of information that points towards your hardware setup being the issue. I don't know what else to tell you.
Click to expand...
Click to collapse
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch. ?
sconnyuk said:
Yes even though I've got 2 here I'm going to try another, now if my local computer shop is open today I'll grab one to try.
As soon as I get a cable I'll report back and let you know, at the very least this might help someone with any issues that turn out to be similar to mine.
I was even thinking of trying to get twrp on or even boot to it to flash the boot.img but it's a no go on 7.2.1 and more so it's a no go because nothing will flash through fastboot for me at the moment.
I'll be in touch.
Click to expand...
Click to collapse
Here is the cable that I use: https://www.amazon.com/Cable-Matters-2-Pack-Male-Black/dp/B00HSS9IDW
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time
Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.
sconnyuk said:
Finally, i decided to butcher 2 good thick usb cables and bodge a new a to a cable together and it flashed first time
Thanks for all your help.
Cannot understand how i have had issues with 2 different cables but now we know this device must be picky.
Click to expand...
Click to collapse
Awesome
ACiDxCHRiST said:
Awesome
Click to expand...
Click to collapse
So from a virgin 7.2.1 we can after all flash a modded boot ??.
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.
sconnyuk said:
So from a virgin 7.2.1 we can after all flash a modded boot .
Just have to wait for a TWRP that is working on 7.2.1 now.
Thanks again for your help, I'd probably of given up after all that untill you mentioned the lead.
I did have a sneaky feeling myself but wasn't gunna try a new one till after Christmas.
Click to expand...
Click to collapse
What do you need TWRP for?
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.
I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?
Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?
ACiDxCHRiST said:
What do you need TWRP for?
Click to expand...
Click to collapse
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also ??
nadia p. said:
Thank you ACiDxCHRiST, for creating a new guide. It takes a considerable amount of time to first find a solution that is repeatable, document everything, test it, etc... :good: well done.
I have a question for you if I may. I've been trying to understand what Magisk actually patches. I've read through their web site and other than rooting it doesn't go into to many details about what else it patches or modifies. Do you have any additional information about this?
Once you've installed the patched_boot.img, and you first boot your Nvidia Shield TV are you required to first connect to the internet, then sign-in to Google Play and assuming the existing Nvidia Experience software is not already updated to the latest release, does it begin to download the and force you to install the latest update?
Click to expand...
Click to collapse
The SHIELD TV will only force you to update when you are going through the Initial Setup after a data wipe. If you follow the guide exactly as written and your bootloader is not unlocked yet, you will be forced to update to v7.2.1 after unlocking the bootloader. But since there aren't any more data wipes and the last step is to flash the v7.2.0 image that we modified, you will end up on v7.2.0 without being forced to do the Initial Setup again. In fact, you could likely use the same steps in the guide to install other versions.
As for what Magisk patches, it modifies the bootloader to trick the OS into thinking that the SU binary is in the system partition without actually modifying the system partition.
sconnyuk said:
Just for backups, I'd like to get my system all setup exactly like I want it and then create a backup.
Also if any magisk/xposed modules make my box not boot to restore also
Click to expand...
Click to collapse
Roger that, makes sense.
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.