the device is a remote controller for a drone, I can get the device into developer mode but when I apply farmroot kingroot any root tool a window pops up and says you do not have permission from DJI to do this. so its like a lock
anyone who can help will be great.
I have done come digging about getting root on the Mavic Pro and it is possible there is an FTP 0Day exploit to allow the traversal to the init scripts to enable ADB and Root Shell. Apparently they were also able to get root on the Remotes as well but only by direct manipulation of the ROM onboard.
The Mavic Pro's are running KitKat
I found a nice discussion on Hak5 forums about it. There was also one on the Mavicpilots forums but that one got removed
I did Find an archived copy of it
Related
I've searched this forum for answers, but I wasn't able to find one for my particular situation. I have an AT&T Galaxy Tab that I would like to use as a wifi hotspot (wifi tethering, or whatever you want to call it). I do not want to tether this to another device that is running as a hotspot; I want the Tab to be the hotspot as this is the only device I own that can do this. I believe (feel free to correct me if I'm wrong) that I need to root it and install a different wpa_supplicant module to be able to set up the hotspot mode. I looked at installing z4root, but AT&T has disabled downloading that via the Market and also from running non-Market apps from the device (I tried putting z4root on the device via USB mass storage mode and running it with Astro file manager). Next, I tried using SuperOneClick by installing Mono for OSX (yes, I use a Mac) and running SOC from the command line using sudo, however "rageagainstthecage" failed to run and the process failed. I've searched for more information on the forums and I can't find anything so I'm asking for help getting the tab working as a hotspot. If I've made a mistake in my understanding, feel free to correct me. I don't own a Windows machine, so that's not an option for me. I have a Linux machine, however I'd really like to get this working on OSX as several of my friends and colleagues are in the same situation as me and only have OSX. Thanks in advance!
Flash the Euro ROM, the turn it on and use it, or root, get the hot spot app and use it....
CyberGhos said:
Flash the Euro ROM, the turn it on and use it, or root, get the hot spot app and use it....
Click to expand...
Click to collapse
How? It seems that they don't make Kies for OS X (or not that I can find), and as I said before I'm not able to root it via z4root or SuperOneClick.
Hello to all,
I'm a new Android user that has recently migrated from Windows Mobile 6.1. I have downloaded this FRX06_Full_Bundle_25.3.2011.zip and successfully installed it on my SD Card. This distribution works OK, but there are some minor issues I need to fix. So I need a root access to my phone. And here comes the problem how to do it.
I read several articles over the internet how to root your phone but all of them are about phones where Andoid is installed in the ROM. Moreover - they require USB access to the phone. And I have problems finding the correct USB drives or my phone USB does not work.
So could you point me an article that explains how to root my phone when Android is installed on the SD Card. Is there a way to do it by mounting the SD card on my laptop via the card reader. I want to avoid using the USB port.
BR
Are you trying on Windows or Linux?
Did you install ADB on your pc already?
Did you enable developers access on the android?
I think you need to provide a little bit more info.
Yea, sorry about that.
I'm using Windows 7 64bit. Currently I'm unable to find suitable drivers...
I have enabled the developers access on my phone, but the drivers problem wouldn't let me root my phone using the conventional approach.
So I'm wondering is there any other way to root the phone that does not include the USB port...
The build comes rooted out of the box. There's nothing additional you need to do in order to root.
You should probably read the FAQ if want more info on adb.
adb is not required for root access. Again, FRX06 comes rooted, nothing needs to be done to 'root' this build.
arrrghhh, thanks for the help. Indeed the distribution is rooted by default. I have confirmed this with the terminal application.
I have a problem with the Samba Filesharing (funkyFresh). The app website states states that the telephone is not rooted or Superuser not installed (I have already installed this). That's why I have tried to "root" my phone...
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
I've been thinking about this, and if I could just set up the android version of astrill directly in the micro sd (directly set up on nooter) I could then access youtube and finish the job properly.
Do you know if it's in any way possible to do that?
I wonder if you'd be able to use Orbot to be able to gain access to Youtube...
Karibou3 said:
Hi everyone, I've been trying to root my nook2 and I've been over all the steps many times, and I can't achieve ADB over USB or WIFI.
I've used the nooter technique and the device looks rooted, I can log into Gmail and get new mail, but as youtube is blocked in China, I can't login to youtube as i'm supposed to in the process described on nookdevs. (is youtube loging really important?)
I can install apps from the market, but can't use the search field (no results, no matter what I type).
I decided to try adb access from there anyway (before asking for help...), and here's where I'm stuck :
I installed the light sdk combo found here : "hXXp://forum.xda-developers.com/showthread.php?t=910008" and followed all the steps
I can connect to the device using wifi ADB, but the shell cmd doesn't get me anywhere (I get a hash mark and an endlessly flashing underscore)
I can't get adb access over USB, because no matter how many times I try uninstalling the basic drivers in the device manager(all of them), they always come back within 5 seconds when I plug the nook (and yes, I seem to have disabled automatic driver update in Gpedit.msc)
when I try to load the adb drivers manually over the preexisting ones it tells me no suitable drivers where found in my *.inf file (or that it already has the best driver for the device)
I've been over everything (apparently) countless times and I'm still stuck.
do you have any idea what the problem could be?
If I had to guess, it's either :
-It's not completely rooted (for lack of youtube login) so it will always be recognized as a Nook and nothing else in the device manager
-the factory defaults nook drivers are lurking somewhere on my laptop and prevail over the adb_usb drivers.
-there is another move to disable automatic drive install in Gpedit.msc which I haven't attempted yet.
Please if you have any ideas... My nerdy ego is absolutely hurt by this and it's begging for relief.
Click to expand...
Click to collapse
Read this, its all contained on my manual tutos, adb is gained just by changing uramdisk, there is one for wifi and another for usb, please, check which one you are using, then, follow this:
Here there is a list of all the tutos:
http://forum.xda-developers.com/showthread.php?t=1380400
and here the ones you should read:
Setting up adb manually on the nook touch:
Making the manual process LESS PAINFULL
Setting up root access on NST through adb and installing busybox:
Hope it helps.
For the youtube thing, just set adb correctly (when you get it right) sideload an app to use a proxy, or tor, or anything you like, and try to login on Youtube.
I'm really sorry for not responding to this
I managed to get it rooted in the few days after my post, and I didn't any email notifications of your replies (didn't check on control panel, i'm new here, please don't hurt me )
I found a chinese source for rooting (a seller on taobao.com explained it. The Chinese are quite fond of the nook because it's the only foreign e-reader you can use to read Chinese apparently, and Chinese e-readers are both more expensive than the nook AND crappy.
Anyway I painstakingly translated it and got it to work
what you tell me about the proxy is new to me though, I thought android couldn't run a proxy, that's great news not just for youtube but the zillions of website China blocks and that I could use my nook to check, I'll have a go at it when I get near a wifi network.
cheers
hello guys noob here ,
managed to root an old firhd 8.9 the other day using the bin4ry method
i went and bought a fire hd 8 2016 number thinking it was the 2018(it was described as this on fleabay) I only noticed the difference in boards when i went to short the terminal... So i used fire tools v7.1 to disable amazon apps etc But im wanting to get root access and have been trying the Rapid temporary root/permanent root method . each time i try and push mtk su im met with:
adb: error: cannot stat 'path/to/mtk-su': No such file or directory
i have the mtksu file in adb directory etc and device is showing up with serial number etc on adb. have also tried it with windows 10/ubuntu terminal though the tablet wont show up on that.
any help or advice on this or even to an automated adb root method would be appreciated guys thanks.
Bertonumber1 said:
hello guys noob here ,
managed to root an old firhd 8.9 the other day using the bin4ry method
i went and bought a fire hd 8 2016 number thinking it was the 2018(it was described as this on fleabay) I only noticed the difference in boards when i went to short the terminal... So i used fire tools v7.1 to disable amazon apps etc But im wanting to get root access and have been trying the Rapid temporary root/permanent root method . each time i try and push mtk su im met with:
adb: error: cannot stat 'path/to/mtk-su': No such file or directory
i have the mtksu file in adb directory etc and device is showing up with serial number etc on adb. have also tried it with windows 10/ubuntu terminal though the tablet wont show up on that.
any help or advice on this or even to an automated adb root method would be appreciated guys thanks.
Click to expand...
Click to collapse
That's the problem, microUSB cable or USB ports on your PC is broken. You can use another microUSB cables or use another USB ports on your PC.
Bertonumber1 said:
hello guys noob here ,
managed to root an old firhd 8.9 the other day using the bin4ry method
i went and bought a fire hd 8 2016 number thinking it was the 2018(it was described as this on fleabay) I only noticed the difference in boards when i went to short the terminal... So i used fire tools v7.1 to disable amazon apps etc But im wanting to get root access and have been trying the Rapid temporary root/permanent root method . each time i try and push mtk su im met with:
adb: error: cannot stat 'path/to/mtk-su': No such file or directory
i have the mtksu file in adb directory etc and device is showing up with serial number etc on adb. have also tried it with windows 10/ubuntu terminal though the tablet wont show up on that.
any help or advice on this or even to an automated adb root method would be appreciated guys thanks.
Click to expand...
Click to collapse
Change Path/to/mtk-su to /data/local/tmp/mtk-su and it will work but push it to there first
Kaijones23 said:
Change Path/to/mtk-su to /data/local/tmp/mtk-su and it will work but push it to there first
Click to expand...
Click to collapse
Brilliant kai that's sound advice m8. Is there any way of getting permanent root on this kfhd8 2016? I'm wondering if I actually need it now as the fire tools v7. 1 seems to have de-amazoned it anyways. Although I could be doing with getting rid of the junk leftover after disabling . Thanks man great work by the way
Sorry just read back there. By pushing files this is perm root ?
I have a Sharp Aquos LC-32Bi6E Android 9.0 smart TV and I need to install my own certificates for a university project (I need to set up a transparent proxy and no, unfortunately, I cannot change the project). Searching online I've found the only solution to be rooting the TV and then install those as system certs.
I never rooted anything (certainly not a TV) so I have no expertise in the field. I have tried with the main apks such as KingRoot et similia but none of those work (device not supported).
I am trying to explore the TWRP recovery + Magisk option but I am stuck.
Anyone can help or suggest another solution?
You will have to unlock the bootloader first then try to find a UART port on the board and use some kind of connection to do the rest