Related
Hi all,
I've recently flashed to MoDaCo 2.2 however I'm just assuming my device got rooted at the same time - but I don't know for sure.
What's the easiest way to verify it has been rooted?
Thanks!
1. use search forum or google..
2. adb shell su
thats it
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Breakthecycle2 said:
It keeps saying device not found, but works for my mytouch and G1. Any ideas?
Click to expand...
Click to collapse
Have you enabled USB debugging? Settings-Applications-Development
trice1921 said:
Have you enabled USB debugging? Settings-Applications-Development
Click to expand...
Click to collapse
Yup did that too...my other phones pick it up no issues.
I also get the exact same problem (i.e. Device not found) - I guess it is a hint that it isn't rooted maybe (although I assumed it was automatic with flashing MoDaCo 2.2)?
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
robboy said:
Sound like a problem with your driver. But you should have been able to connect before to install the custom rom?
Download astro file manager and you should be able to see files that you couldn't see before
Click to expand...
Click to collapse
OK I got a work around. You need to restore your PC to a point BEFORE you plug in your hero. I did this and now works great.
How I might undo root process?
I think that replace chmod 4755 permision to default in the "su" file, but I don't know how to
No need to do, but I'm intererested in the concept
There is a thread on how to unroot:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse
ZenorGR said:
There is a thread on how to unroot:
Click to expand...
Click to collapse
I'm sorry but could don't find ...Thanks!!!
its a sticky.. its really hard NOT to find it
edit: okay it WAS a sticky, but its also on the first site in this subforum.. so no problem to at least SEE it
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
I bought the Motorola Bravo which is similar to the Flipside and an app on the market called Z4ROOT was able to root the phone. It works on many phones not just the Bravo. Give that try and see if it works.
z4root does work for permanent root i have tried and can confirm
jediskywalker said:
i know it just came out and all but my room mate got one and we were hoping someone will look for root i have an evo so i dont think i can help him much plus i dont know code so just wondering
thanks
Click to expand...
Click to collapse
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Got my Flipside rooted and non market apps allowed
I followed the instructions given at modmymobile dot com forum. Look up "fully unlock 3rd party apps backflip" It allowed me to root my phone and install non market apps. I tried and tried to follow the instructions given here, but i guess they weren't idiot proof. It is for the backflip, but it worked perfectly for my Flipside. I couldn't post the link here.
Someone found some typos in my scripts. I have updated them so they are accurate. Should make things run better.
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
ishiiisbooyah said:
Hey I kinda need some help. I've gotten through all the way to entering "adb install z4root.1.3.0.apk" into the command prompt but all I get is a message saying "adb" is not recognized as an internal or external command, operable program or batch file. Anyone have any ideas on how this could be happening?
Click to expand...
Click to collapse
Lets say you installed your SDK in the default folder, you would need to type
Code:
cd c:\"Program Files"
cd Android
cd appinventor-extras
Now, I put mine in c:\SDK, so all I type is
Code:
cd c:\SDK
you either must add the SDK to your PATH, or find the directory that you installed it to, and then try running adb from there. If adb.exe isn't in the folder, you aren't in the right folder.
jonsjava said:
Rooting a Motorola Flipside
[/url]
Click to expand...
Click to collapse
hi
i m new in unlocking field
can i unlock this handset "flipside" by motorola came from usa at&T
if yes then plz explain
thanks in advance
RZ4root does not appear on the marketplace and when I click the link above it starts to download, then says the content is not supported on my phone.
Model num MB508 Motorola Flipside running Android 2.1 update 1.
You need to push it to the phone from a computer using adb to install z4root, now that it has been removed from the market.
Sent from my Liberty using Tapatalk
adb.exe not in the zip file
jonsjava said:
Rooting a Motorola Flipside
grab the ADB SDK files
android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
(...snipped...)
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Click to expand...
Click to collapse
adb.exe is not present in the SDK that you linked. Are you sure that is the SDK we need to root the Flipside?
You have to install it manually. It comes with the platform-tools.
how do i install adb.exe from platform-tools
lol, i may ask stupid questions but this one wasnt me, i shouldnt leave my laptop lying around haha
jonsjava said:
Rooting a Motorola Flipside
Download drivers for the phone:
http://www.motorola.com/staticfiles/Support/Experiences/Global_Drivers/USB_Drivers_bit_4.7.1.zip
With the phone unplugged from the USB, install the drivers
grab the ADB SDK files
http://dl.google.com/android/android-sdk_r08-windows.zip
Extract SDK files somewhere you will remember, and can easily type (for ease of use only)
Download z4root:
(you may need to sign up to download)
http://forum.xda-developers.com/attachment.php?attachmentid=446145&d=1290341328
Copy z4root.1.3.0.apk to your SDK folder
ON YOUR PHONE:
go to Apps Menu->Settings->Applications->Development and check "USB debugging"
Plug in your phone, and have it set to "Charge only"
go to the command prompt, and type
cd C:\"PATH TO SDK" <ENTER>
Now, type
adb install z4root.1.3.0.apk
Once that is complete, you can now go find Z4 in your programs list. I chose "permanently root". Your phone will
reboot, and then you are rooted.
Unknown sources is still disabled at this point, but you can now install apps that require super user
Tonight, I will try to enable "Unknown Sources" on my flipside.
UPDATE: To get "Unknown Sources" enabled, go to this thread:
http://forum.xda-developers.com/showthread.php?t=867637
Click to expand...
Click to collapse
Notice:
For anyone having trouble rooting the Motorola Flipside with these instructions, after much trial and error I managed to get my girlfriend's rooted. I'll provide the method I took.
Note: The easiest way to do this is to have downloaded and extracted "android-sdk_r08-windows" directly to your (C: ) drive. Not under programs or another system folder.
Once you have it extracted to (C: ), copy and paste z4root.1.3.0.apk into the "android-sdk_r08-windows" folder. ADB.exe will most likely not be in here. What you have to do now is click on SDK Manager within the SDK folder. A Black Command window will pop-up, ignore it. A secondary window will pop-up prompting you to install the packages I went ahead and installed all of them (better if you don't know which to install).
Now that they've all been installed, a command line will state that ADB has to be restarted. Let it restart and it should say completed.
Now -- here's where everything was messing up. When you click open the SDK-R08 folder, you should have the z4root.apk file right there amongst a list of folders. Go to the "platform-tools" folder and in there you should see the ADB.exe file. Ignore that for now. While in platform-tools press Ctrl+A so that everything is highlighted. Right click and select Cut, back out to the main directory of the SDK R08 folder and select Paste so that the ADB.exe, .dll, and all the other files from within platform-tools is out and listed alongside the z4root.apk.
Next - Follow all of the instructions up to "Plug in your phone, and have it set to "Charge only" Like JonsJava said, open up command prompt (type in CMD in the "search programs and files bar"). If you extracted the "android-sdk-r08-windows" file directly to the (C: ) drive, all you have to type in is...
(Note: Before I go into that, it'll be easiest to rename the file "SDK" instead of the whole "android-sdk, etc, name... I'll complete the instructions assuming you renamed it to SDK. Continued below... all you have to type in is...
cd C:\SDK
(The next line below will look like this)
c:\SDK>
Here, type in... adb install z4root.1.3.0.apk
Total should look like... c:\SDK>adb install z4root.1.3.0.apk
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Last note:
Uploaded with ImageShack.us
This is what the main directory of the SDK folder should look like before you enter anything in the command line.
I don't seem to be able to get this...
I'm using x64 windows 7, I have a Flipside MB508 on 2.1, and I can't get this to work.
I followed all the instructions, updated all the platform-tools stuff, and now my problem lies with the driver, I believe.
I installed those Motorola drivers that were linked, with my phone unplugged, successfully..
copied the apk to C:\SDK...
found adb.exe in the platform-tools folder..
...and this happened..
C:\SDK\tools>cd C:\SDK
C:\SDK>cd platform-tools
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\SDK\platform-tools>adb install C:\SDK\z4root.1.3.0.apk
error: device not found
C:\SDK\platform-tools>_
"error: device not found" every time i try this
USB debugging is on, phone is plugged in set to charge only..
Windows even sees it, the taskbar eject icon says 'Eject MB508"
please please help me get adb to see my phone.. I really want to be able to root this thing!!
EDIT: I noticed the Motorola drivers are 32bit.. I'm going to try 32 bit windows 7 instead of 64 bit and see if I get more successful results
EDIT 2: Bazinga!! Installed Win7 32 bit on my other HDD, booted up, followed the steps again, worked flawlessly! Thanks a lot for the easy instructions, got z4root installed, and my phone worked with permanent root
ErebusRaze said:
Notice:
Hit enter and it should go through a few instructions. From there look in the applist on your phone for z4root, click on it and select permanently root. Your phone will restart. From there you're rooted (test by downloading an app which requires root) and don't have to worry about the low memory issues every again. Glad I got the Captivate, lol. So much easier to root, rom, and overclock.
Click to expand...
Click to collapse
You wrote in here that once rooted, thebphone would no longer have low memory issues...i rooted my wife's phone, was able to sideload applications (but for some strange reason I am now unable to, as adb command prompt states 'device not found')- but she still gets low memory issues at least 2-3 times a week...
I should just hold up a sign...
LINK2SD
Its in the market
Sent from my MB508 using XDA App
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
thehotrod11 said:
Link2sd? What does this do? I briefly looked at the thread, but it is not entirely clear. The flip side is running 2.1. With this app, can we free up space by moving apps to the sd card? I thought that was only possible in 2.2?
Click to expand...
Click to collapse
Link2sd makes installing to sd card possible on 2.1...
Sent from my MB508 using XDA App
One click root with impactor now works. Works on <4.3. No need for unlocked bootloader. Does not wipe data.
http://www.saurik.com/id/17
Copy over the superuser.apk and the such binary onto your phone, then use the MV command to move it to /system/app and /system/xbin respectively.
Beamed from my Grouper
Mach3.2 said:
Copy over the superuser.apk and the such binary onto your phone, then use the MV command to move it to /system/app and /system/xbin respectively.
Beamed from my Grouper
Click to expand...
Click to collapse
What should the permissions on each be?
EDIT: Can you alternatively only push the su binary and download superuser from gplay?
krackers said:
What should the permissions on each be?
EDIT: Can you alternatively only push the su binary and download superuser from gplay?
Click to expand...
Click to collapse
If the binary is wrong, the one from play store may not work.
Permission should be rw-r-r(0644) for the su.apk and rwsr-sr-x(0645) for the su binary.
Beamed from my Maguro.
I tried it myself and while it appears that commands do run, they don't appear to work. I think it might have to do with running as system vs running as root. Why else would saurik use an indirect method of gaining root (using ro.kernel.quemu) as opposed to directly pushing the su binaries.
krackers said:
I tried it myself and while it appears that commands do run, they don't appear to work. I think it might have to do with running as system vs running as root. Why else would saurik use an indirect method of gaining root (using ro.kernel.quemu) as opposed to directly pushing the su binaries.
Click to expand...
Click to collapse
This is correct: sometime in the Android 4.1 release cycle, they removed the ability to use /data/local.prop as an attack vector to go from system->root. The signature bug lets you modify the code of any APK, but the most powerful user an app can ever run as is system, not root.
However, in an update to Impactor today, I've added a system->root escalation. This allows one-click rooting, and even though the system->root I'm using has already been patched in AOSP (the idea was not to waste something to go along with a shell->system that is already long burned) it works on my 4.2.2 Nexus 4 (and so I'd imagine will also work fine on a Galaxy Nexus) as Android sucks at getting patches to real devices ;P.
Using Impactor on my Panasonic Eluga dl01 does somehow not work.
(Android 4.0.4)
I get following error message:
/data/local/tmp/impactor-6[3]: /data/local/tmp/impactor-4: Operation not permitted
I also tried and played around with the command line in Impactor.
"adb devices" won't list my phone
But when I use the adb from the current Android SDK I just installed, it will display my phone with "adb devices".
I also downloaded a ICS 4.04 root zip file with a script and adb files inside. When using that adb version, my phone won't be displayed too. Now when I run adb from the android SDK, it will say something like "server is outdated" then something like "kill and restart with new server" --> "adb devices" lists my phone correctly again.
May be the adb version used in Impactor is outdated and responsible for the error message?
I would really appreciate any help with this topic, because the Panasonic Eluga phone was never rooted until now and no known root method is available. I always kinda hoped that someone would use the masterkey thing to make a universal rooting tool
saurik said:
This is correct: sometime in the Android 4.1 release cycle, they removed the ability to use /data/local.prop as an attack vector to go from system->root. The signature bug lets you modify the code of any APK, but the most powerful user an app can ever run as is system, not root.
However, in an update to Impactor today, I've added a system->root escalation. This allows one-click rooting, and even though the system->root I'm using has already been patched in AOSP (the idea was not to waste something to go along with a shell->system that is already long burned) it works on my 4.2.2 Nexus 4 (and so I'd imagine will also work fine on a Galaxy Nexus) as Android sucks at getting patches to real devices ;P.
Click to expand...
Click to collapse
Do you need to have an unlocked bootloader for the root exploit to work? I am hoping to get root without having to wipe the device by unlocking.
To the poster above me: Try using a different computer and if that doesn't work, switch operating systems.
krackers said:
Do you need to have an unlocked bootloader for the root exploit to work? I am hoping to get root without having to wipe the device by unlocking.
Click to expand...
Click to collapse
That's the whole point in securing Android, not that people have easier ways instead of unlocking a device.
Tested and works great. I now have root. Yay!
Does it show any of the problems that chainfire's superSU 1.41 shows?
Sent from my Galaxy Nexus using xda app-developers app
The root exploit only places the su binary and sets the right permissions. You can use any root manager you want (I used clockworkmod's superuser app).
mercuriussan said:
Using Impactor on my Panasonic Eluga dl01 does somehow not work.
(Android 4.0.4)
Click to expand...
Click to collapse
The feature of installing su will not work on every device: a lot of emphasis is put on "rooting" Android devices, but on many devices even root can't do things like modify the files in /system; I'd use the term "jailbreak" as to being what people really want to do with their device, but Android people seem to have that term ;P. What this means is that you really need a kernel exploit, not just a shell->system->root escalation.
mercuriussan said:
I get following error message:
/data/local/tmp/impactor-6[3]: /data/local/tmp/impactor-4: Operation not permitted
Click to expand...
Click to collapse
This error message actually indicates that Impactor succeeded in obtaining root control over your phone. However, when it tried to then, as root, remount /system writable so it could copy the su binary in place, it wasn't allowed to do so. A future version of Impactor will make it easier to drop to a root shell so you can test things out manually, but this means that while you can run code as root, you won't be able to install su.
However, if you have the time to play with it, get a copy of busybox and use adb to push it to /data/local/tmp (this is also something Impactor should help you do, but does not yet). (You will also need to make it executable, don't forget: "chmod 755 /data/local/tmp/busybox".) Then run the suggested Impactor command involving telnetd. Finally, via a shell, run "/data/local/tmp/busybox telnet 127.0.0.1 8899": you are now root.
You can verify that you are root because you will now have a # as a prompt instead of a $. Then run "mount -o remount,rw '' /system" (<- note, that's two single quotation marks as an argument between remount,rw and /system). This is the command that should fail with the "Operation not permitted" message. You are, however, root, so maybe there's something you want to do on the device at that point ;P.
mercuriussan said:
I also tried and played around with the command line in Impactor.
"adb devices" won't list my phone
But when I use the adb from the current Android SDK I just installed, it will display my phone with "adb devices".
Click to expand...
Click to collapse
The "Open Shell" in Impactor connects you to the device via adb: if you run adb on the device and ask for a list of devices attached to the device--something I didn't even realize was possible until you pointed it out here ;P I tested it, though, and wow: that actually is possible--you will get a blank list. However, suffice it to say that if you were able to type that at all, it can see your device.
Thanks for the suggestion, I'll try my luck in finding some exploit I can use...
So since Google patched this in 4.3, does this mean almost all devices before 4.2.2 can be rooted with this method?
bmg1001 said:
So since Google patched this in 4.3, does this mean almost all devices before 4.2.2 can be rooted with this method?
Click to expand...
Click to collapse
Yup - assuming they haven't been patched against the methods used (most haven't been).
Very interesting read. Thanks saurik & OP.
Eluga DL1
Hi there,
this post is in some ways a duplicate but different people seem to follow this thread because it is directly involving sauriks impactor.
Is there anything available that i can throw at Elugas 4.0.4 kernel to get r/w on the system partition?
I will try everything that is suggested to me.
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
I'm having a problem putting root in my phone (Asus zenfone 2)
I made the whole process, 7 clicks, enabled usb, and downloaded a zipped folder with one of the files named "Root_zenfone" which opens a cmd asking to press a key to start, but when I press it says "Fastboots is not known as a Internal command, or external an operable program or a batch file "and so I can not install root, can someone help me, please?
dashlatrell said:
I'm having a problem putting root in my phone (Asus zenfone 2)
I made the whole process, 7 clicks, enabled usb, and downloaded a zipped folder with one of the files named "Root_zenfone" which opens a cmd asking to press a key to start, but when I press it says "Fastboots is not known as a Internal command, or external an operable program or a batch file "and so I can not install root, can someone help me, please?
Click to expand...
Click to collapse
Which Android version is your phone running? Where did you download the zip file? Search for the right rooting method in this forum, never trust those unknown sites found in Google
Yes I downloaded the Zip file and my android is 5.0.
A good and bad news, I was able to activate root but I'm trying to use the emulator terminal to change my MAC address and the message that appears is "tmp-mksh NOT FOUND"
I use the "su" command and soon after when I will use the "busybox iplank show wlan0" and this message appears above. Can you help me?
Have you installed adb and the drivers on your computer? It would be easier to use the modder tool found in the general section. Everything you need is in the pkg.
Sent from my ASUS_Z00A using Tapatalk
Reply
kenbo111 said:
Have you installed adb and the drivers on your computer? It would be easier to use the modder tool found in the general section. Everything you need is in the pkg.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I did not install the drivers because I did not find it and I was able to activate root, now my problem is to change the MAC address of the mobile phone, I am using the android terminal and busybox, I was able to install the busybox but at the time of using the terminal only the message works "Su" later to use "busybox iplink show wlan0" does not work. The following message appears (tmp-mksh NOT FOUND)
What do I need to stop using, or am I using the wrong code?
dashlatrell said:
I did not install the drivers because I did not find it and I was able to activate root, now my problem is to change the MAC address of the mobile phone, I am using the android terminal and busybox, I was able to install the busybox but at the time of using the terminal only the message works "Su" later to use "busybox iplink show wlan0" does not work. The following message appears (tmp-mksh NOT FOUND)
What do I need to stop using, or am I using the wrong code?
Click to expand...
Click to collapse
That's why your fastboot commands were not working. As far as the other MAC address problem is concerned, I don't know about that
Sent from my ASUS_Z00A using Tapatalk