Related
rooted via ubuntu and have recovery
i tried doing stuff in windows, but it wont install the drivers properly.
SO I NEED HELP!
what do i do to get this to work?
i want to be able to install 3rd party apps and get rid of att bloatware.
i have no idea where to start.
HELP!!!!!!!!!
thanx
ubuntu or windows...
download the Android SDK for Windows
http://developer.android.com/sdk/index.html
install and download ONLY THE USB DRIVERS
open cmd window, connect usb cable, navigate to the <folder>\tools where you installed, ie. c:\android\tools
paste the following into a small batch file, call it anything you want dot bat,
ie. c:\android\tools\yourname.bat
---cut here--
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot
-- cut here--
ok i'll try right now
still must be missing something
what setting is my phone on when i plug it in? recovery? or just regular charge only or hard disk mode?
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
when i run that .bat file it says a bunch of things, but basically says device not found.
please start from step #0.
there is no one place that has every single step we need to do.
it makes it next to impossible to get this to work.
dh4645 said:
how do i get the usb drivers to work? when i try to install them is says "windows was unable to install your adb". is there something else i need on my pc?
Click to expand...
Click to collapse
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
ocswing said:
I'm not sure I've ever seen this error come up before by anyone. Saying this is impossible isn't really true since several people have gotten it working, and the information is on these forums. The best thing to do would be to go to the IRC channel and get stepped through it. http://webchat.freenode.net/?channels=#liberatedAria
I'm not quite sure what's up with your ADB install, but you should download HTC Sync from the HTC site, because it includes a driver install. http://www.htc.com/us/support/aria-att/downloads/. Then go through the process in the post above. Your phone should be in the "Charge Only" mode when connected to the computer.
Click to expand...
Click to collapse
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
dh4645 said:
i know it's not impossible, it's just that usually when the people explaining the steps to accomplish this leave out steps that they think is common knowledge/sense, but is not to total noobs.
it would be nice to have a definitive step-by-step guide:
step 1 - root your phone (this was actually really easy with the ubuntu cd)
step 2 - go back to windows and download/install these specific programs . . . (i did not know i needed htc sync, the steps i saw said just to use the sdk and the usb drivers in there to set up my phone)
step 3 - enable debugging on phone, plug your phone into pc and use charge only. (don't we use recovery for anything, i've seen steps about having this open and using the mount /system to do stuff)
step 4 - get the adb usb drivers to install properly (i guess this is my main issue at the moment...is that what is causing the device not found error when i run the .bat file?)
step 5 - copy and paste code into notepad an save as a .bat file.
step 6 - run the .bat file (within cmd? double click on the file? does it matter?)
step 7 - ????
alternate step 2 through whatever - use the ubuntu cd to do everything... (???)
Click to expand...
Click to collapse
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Shad0wguy said:
Run the bat file in the cmd window. Once the bat has successfully run you can unplug the phone and you'll be good to go.
Click to expand...
Click to collapse
so what is the point of the sdk...other than to have the tools folder to run that .bat? so i'm the only one that can't get the sdk usb drivers to work?
and by good to go, u mean i can install 3rd party apps?
how do i get rid of the the at&t bloatware?
There are other threads explaining how to install third party apps and remove ATT bloatware.
Sent from my HTC Liberty using XDA App
The problem with trying to do a step-by-step guide is that things like rooting, removing bloatware, and sideloading apps are all separate processes that require different steps and can be done in multiple ways. Some stuff requires you to be in recovery, some stuff doesn't, and other methods may require additional software. That's why there are specific separate threads that discuss them.
You've rooted your phone already, yay! Now you decide what you want to do next. Remove the bloatware? It's important that you don't lump everything together when trying to figure out what you need to do.
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
ocswing said:
....
It seems like the first step you need to do is get ADB working and recognizing your phone when it's plugged in. ADB is necessary because it provides all the tools/commands necessary for us to interact with the phone through the command line. Windows is notoriously bad about the USB drivers. That's why the Ubuntu method was streamlined for people so they wouldn't have to deal with it. (Linux and Mac have no such usb driver issues.)
Click to expand...
Click to collapse
thanks for the reply.
yeah i rooted via the ubuntu disc, but then all the other steps people were telling me were using the sdk, getting the drivers, htc sync, yada yada. via windows. so thats the method i've been trying.
is there a step-by-step guide on how to allow 3rd party apps using the ubuntu disc? or... removing bloatware?
is it the same steps, but you just dont have to worry about the drivers?
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
ocswing said:
The steps listed once you're in the SDK are actually the same regardless of what OS you're using.
So for Ubuntu install the SDK. Steps should be the same, just make sure you download the Linux version. Then you'd open a Terminal window (should be called Terminal in Ubuntu.) Then you should be able to use the same commands/steps you find in the other threads.
Since you've been having trouble getting your phone to connect the first thing to do is make sure SDK can actually see your phone. You should be able to open up your Terminal window, navigate to the SDK folder, connect your phone and then type 'adb devices' in the terminal window. It should then list out your phone as HTXXXXXXXX. X being some numbers and letters. If it does show that then you're on your way.
After that I'd go with removing bloatware and the steps listed in this thread. http://forum.xda-developers.com/showthread.php?t=735255
Click to expand...
Click to collapse
ok cool thanks a lot!
i didn't even think to go back to linux to try this stuff until today at work.
i'll check it out later tonight after i mow the lawn and eat dinner....priorities...
i tried in windows one last time. it actually found the htc sync drivers (i in/uninstalled htc snyc earlier...i guess thats what did it)
adb devices command finds my phone, but when i try and run that .bat file, it goes through a bunch of things, but basically says:
remount failed: operation not permitted
failed to copy...
permission denied
all those types of things. then it says to hit enter and then it restarts my phone
???
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
b_atman said:
did u try installing HTC sync connect phone to htc sync, then unistall the htc sync software usb drivers should stay behind
Click to expand...
Click to collapse
i said i did that above...that was the only way i got the usb drivers to work/recognize my phone...the sdk ones didnt work)
my phone is recognized when i run adb devices command
i'm having issues when i run the .bat file as i said in my last post
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
b_atman said:
my bad
maybe i missed it, after you did the mount command did you do the read/writes permissions change?
Click to expand...
Click to collapse
uuu, no, whats that?
i thought i just had to open cmd and run the .bat file
so what did i miss now? ha
thanks for your help!
i ran this .bat file
cd\android\tools
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
pause 1
adb reboot
Win 7 x64
AT&T Xperia X10a
I was trying to root my X10a, using the one click method (X10Root.1.0.8.apk), and got hung up when trying to side load the app. ADB nor SWM could find the device. I finally got ADB to find my device. Here is how I got it to work.
Xperia- have debugging on
- have titanium backup free installed
- have busy body free installed
- do NOT mound SD
- have allow mock locations on
- have stay awake on
PC- have pc companion installed BUT terminate the process
- have the android sdk installed. (when installing I just installed everything)
- have android-sdk_r07-windows folder in C:/
- I changed the folder name above (android-sdk_r07-windows) to sdk
- have X10Root.1.0.8.apk file in C:/
- if google calander sync installed exit it.
With X10 plugged in and all above met.
Open command prompt
Type or copy and paste(if you changed folder name) cd C:\sdk\tools
Hit enter
Type adb kill-server
Hit enter
Type adb shell
Hit enter
Type adb install C:\X10Root.1.0.8.apk
Hit enter
Now the app should be on your phone. I hope this helps some AT&T X10 owners out there. Everyone keep up the good work.
Good info, I bet it will become very usfull to other in case they need to SideLoad. I did mine after 4 hours of time spending and finding the issue couple days ago.
Cheers,
Someone did post a fix for this on a java issue too...I like the adb method though..The sideloader and at&t just don't like each other! Would be awesome if we could use RSDlite to flash it though!
download and install this driver :
http://developer.sonyericsson.com/cws/download/1/825/494/1279522933/X10_drivers.zip
PS : APK files are like setup.exe on wondows... you must to copy it on your X10's SD card, and execute it on the X10, NOT on your PC !!
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Added English version manual on Lenovo-Forums.ru
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
Do this root apply to the s8-50F ?
EDIT: This method indeed does work on the S8-50F variant. Was having problems with device staying in adb while running program, but a reboot of pc fixed that and gained root effortlessly. THanks!
Glad It Helped !!!
Hash.H said:
Its finally here guys, the moment you've been waiting for, ROOT for the Lenovo Tab S8-50. To Root Your Device, All you have to do is enable developer options/mode by tapping on your build number multiple times. Then navigate to Developer Options and make sure you enable USB Debugging or else your PC wont recognize the tablet. Make sure that you have Installed the proper ADB drivers for your device and its Drivers.
Requirements and conditions:
1-Make sure that your computer is not connected to other Android devices
2-Make sure that you have installed the ADB drivers for S8-50 tablet
3-Make sure that the machine is turned on USB debugging
4-Connect the device to your computer via USB
5-Download the below attached file, extract it, and run the program
6-If all the conditions and requirements are met, after working program closes automatically, the device will reboot automatically and will appear on the unit program SuperSU .
Download Links will be provided at the end of this post ! I/we are not responsible for any harm or damage done to your device during the process of rooting it. If it fails and bricks, that's your fault. I've successfully rooted mine and it was easy.
If you get an error during the rooting process that said "adb server is out of date killing adb server didn't ack" or something like that, there is a way to fix it. Open Task Manager on your PC and try closing adb.exe and restarting it, or just Google the error and you will most likely find a way.
All Credit Goes to its Respectful Owner "Xakep" From Lenovo-Forums.ru.
Requires 7-zip to open or WinRar
Click to expand...
Click to collapse
The download isn't working for me. It's not downloading as a zip? Any suggestions?
If youre using windows, download a program called 7-zip and downoad the file. right click the root software and click extract here. or open with 7-zip. You could also use winrar. The format of the file is in .7z right ? that means search up http://www.7-zip.org/
Any idea how to unroot?
Not sure. Have you tried the full unroot method in the su app?
__McB__ said:
Any idea how to unroot?
Click to expand...
Click to collapse
SuperSU.apk.....in the setting, unroot, cleanup...
icanttinkofaname said:
Not sure. Have you tried the full unroot method in the su app?
Click to expand...
Click to collapse
jazzespresso said:
SuperSU.apk.....in the setting, unroot, cleanup...
Click to expand...
Click to collapse
Thanks both of you. I ended up returning it, root and all, but I'm sure your suggestion would have worked.
After rooting, has there been anything anybody's been able to do about battery life? I don't imagine there's been any Roms built for this device yet, but didn't know if maybe someone's figured out something that's helped extend their battery life, because when playing certain games like clash of clans for instance, I'm lucky to get an hour and a half of game play, and that's with my brightness turned all the way down. Any suggestions would be greatly appreciated. Thanks
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
This root guide works on s8-50f! thanks Xakep
This is a very easy and usefull root instruction, i rooted my tab s8-50f with no problems.
I followed the steps described and got instant root without any issues.
My machin is windows pc with windows 8.1 pro 32bit. Plug your tab and windows recognized the drivers just make sure your device mngr shows lenovo s850 and you are all set. Then just run the flash tool and it will run in less than a minute your tablet will reboot and your tab will be rooted.
Yes this is probably the easiest I've ever rooted any device in the past. If at first it doesn't take, don't worry it will. Just repeat the process till it does. Thanks Hash.h for putting up this thread and passing along the info
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Where can I download the ADB drivers for S8-50 from?
I think drivers come with tablet. Try to connect the tablet and it will show CD drive on which is the driver.
error: device offline?
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Worked great. Thank you.
Awesome little tablet.
Jirbo said:
I followed this with no luck. I have adb installed and running "adb devices" shows the tab connected, but when I run the tool "error: device offline" scrolls repeatedly and no root.
Any suggestions?
Thanks
Click to expand...
Click to collapse
Tried on another computer and succeeded.
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
moogthedog said:
This worked brilliantly...
but then I upgraded my firmware using the in-built system and it de-rooted. Now the exe no longer works.
New firmware is S8-50F_S000200_150121_ROW
Exe -appears- to run well, but appears to fail on the last command. Unfortunately it disappears off the screen before I can check the exact nature of the error. It appears to go fine until the final attempt to copy the SU binary into place fails with a 'File not found' error.
I've also tried the other method here:
http://forum.xda-developers.com/general/rooting-roms/guide-lenovo-s850-row-t2927400
The flashtool fails to find the device (I know the drivers are installed), so I'm unable to install the new boot image.
ADB shell fails
mount -o remount,rw /system
with the response
mount: Operation not permitted
so none of the 'push' operations will complete as the /system folder is read-only.
Any suggestions?
Click to expand...
Click to collapse
Same problem here. Lost root after the last update and now I can't get either root method to work.
Hey Guys,
Been lurking for a while. I want to get into some Android development. I bought a cheap Galaxy Tab s SM-T800 from ebay. It was a retail unit, so came with the usual retail protection, but that was no issue, I've reflashed it and rooted it, it is now running 6.0.1 with build number MMb29K.T800XXU1CRJ1.
The issue is, there are a bunch of apps and files that appear to be left over from the retail demo mode, and I can't remove them. The apps won't uninstall, it just says "uninstall unsuccessful", and the files, when I try to delete them, it just says "failed to delete".
Even after freshly restoring the new firmware, the storage on this device is pretty much zero, a lot of the space being taken up with the files and apps that I can't remove.
There was just about enough space remaining to install System App Remover, but that couldn't delete the files and apps either.
How are these files being write protected? How do I go about removing the write protection? I'm wondering if this device, because it was a retail demo unit, was configured with some kind of write protected partition, which is why the storage is so low, and why I can't delete the apps?
Any thoughts, this is driving me nuts.
Thanks
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
jwoegerbauer said:
Install a file manager that allows to mount the partitions in question as READ-WRITE, thus folders/files can get deleted
Click to expand...
Click to collapse
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
DotNetDude said:
Thanks, but I can't install any of the file manager apps, as there is not enough free space. I'll need to do it by connecting from Windows. What android partition/file manager would be a good one to use from Windows?
Click to expand...
Click to collapse
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
jwoegerbauer said:
Because your device is rooted, you use ADB ( read: Android Debug Bridge ) - what you've to install on your Windows computer - to manage this device - you must have turned on Developer options -> USB Debugging on it, of course: IMHO the only the chance you have.
Once done so, you connect your device via USB cable with Windows computer, then in Windows command prompt run the commands as follows - one after one:
Code:
adb devices
adb root
adb shell mount -o rw,remount / -t auto
If success then your Android device completly is switched to READ-WRITE mode, you then via further relevant ADB commands can remove folders/files which you consider dispensable, even apps if you know their package name, and so on ...
Click to expand...
Click to collapse
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
DotNetDude said:
Thanks for your details.
So I tired this but the adb root command wasn't working. It was coming up with the message:
adbd cannot run as root in production builds
So after a bit of research, I found the adp insecure app from Chainfire, that apparently resolves this exact problem. So I've deployed that to the tab and run it, but now when I connect the tablet to my PC, the PC doesn't connect. I get the charging symbol on the tab, so the connection is in place, but it is not detected by the pc, so I can't connect using adb.
Any suggestions would be much appreciated?
Thanks
Click to expand...
Click to collapse
I realise I am responding to my own message!
Now that I am running with adb insecure, I have realisd that the USB debugging mode from developer settings is working in reverse. That is, if I enable it, the tab detaches form the PC. If I disable it, the tab reconnects to the pc. However with that setting disabled, and the pc connected, when I then run the command adb devices, it says there are no devices connected (even though I can browse to the tablet through windows explorer)
From within the adb insecure app on the tablet, when I enable the app, I can see it displays a message that says USB debugging is disabled.
I have no idea what is going on here...
Any help much appreciated?
Thanks
@DotNetDude
May be reading this helps.
jwoegerbauer said:
@DotNetDude
May be reading this helps.
Click to expand...
Click to collapse
Thanks for this. Actually, adbd insecure was just causing more problems. In the end I have resolved this by extracting the PIT file and re-partitioning. Firmware then restored correctly and all the problems are now gone, and there is plenty of free space remaining.
Hi all!
I'm testing some device because I need to install a MDM application to remote controlling the device. This Ugoos likes me but I can't find how install de MDM apk with owner permission and not getting a reboot loop.
I'm setting up the owner permission with this adb command:
Code:
adb shell dpm set-device-owner com.hmdm.launcher/.AdminReceiver
After that, if I rebooting device, when it loading the launcher the background image is displayed for a second and restarts again. If I installed MDM apk but not execute adb command, device works fine. I need owner permission for a silent install/update application, remote reboot...
I'm trying debugging with adb, but I've connected just via WiFi and with the reboot loop I can't do that. With male to male USB cable I can't to connect. I've little experience with Android, but I'm good with linux.
Can you give me any recommendations to get owner permission? Or how debugging it?
P.D: I've installed another launcher (Nova) and setup as default I device works fine.
ppalacios said:
Hi all!
I'm testing some device because I need to install a MDM application to remote controlling the device. This Ugoos likes me but I can't find how install de MDM apk with owner permission and not getting a reboot loop.
I'm setting up the owner permission with this adb command:
Code:
adb shell dpm set-device-owner com.hmdm.launcher/.AdminReceiver
After that, if I rebooting device, when it loading the launcher the background image is displayed for a second and restarts again. If I installed MDM apk but not execute adb command, device works fine. I need owner permission for a silent install/update application, remote reboot...
I'm trying debugging with adb, but I've connected just via WiFi and with the reboot loop I can't do that. With male to male USB cable I can't to connect. I've little experience with Android, but I'm good with linux.
Can you give me any recommendations to get owner permission? Or how debugging it?
P.D: I've installed another launcher (Nova) and setup as default I device works fine.
Click to expand...
Click to collapse
to make an app owner you need to add/edit device_policies.xml and device_owner_2.xml, these then need to be started by init in the post-fs-data section in the /data/system partition, to copy the XML files to system/data use init.rc to copy the files to /data/system, not sure if much help
heres some info may be useful https://burningthumb.com/setting-the-device-owner-in-an-aosp-build-for-android-9-pie/
aidanmacgregor said:
heres some info may be useful https://burningthumb.com/setting-the-device-owner-in-an-aosp-build-for-android-9-pie/
Click to expand...
Click to collapse
Thanks Aidan.
I read that days ago but in my case, the app is not developed by me. Is headwind mdm application.
Can I follow the instructions of the link even if is third party app?
Thanks for your help
ppalacios said:
Thanks Aidan.
I read that days ago but in my case, the app is not developed by me. Is headwind mdm application.
Can I follow the instructions of the link even if is third party app?
Thanks for your help
Click to expand...
Click to collapse
yes looks like you will be modifying the firmware rather than the app, the info is there but your not building from source so you will need root to add the files and to edit others
aidanmacgregor said:
yes looks like you will be modifying the firmware rather than the app, the info is there but your not building from source so you will need root to add the files and to edit others
Click to expand...
Click to collapse
Sorry for bother you Aidan, I appreciate your help so much
I've got root access and I've seen that set-device-owner adb command execution create the device_owner_2.xml and device_policies.xml automaticly and they are storage in /data/system. In fact, I'm reading dpm command (adb) is the new way to grant the owner permission without modifing xml files The bad news, I'm still getting reboot loop.
I can't to write into init.rc because the file is in /system and this partition is read only. The same way, can't copy decice_owner_2.xml and device_policies.xml in /system partition (this I read on some forum on internet).
Could I get a logcat from adb to get more info about the crash app? I've only wifi adb connection. I've a male-to-male USB and it connected to OTG port of Ugoos device.