HEllo,
I'm actually trying to hack THOMSON THBK1-10 tablet (also know at VOYO A1).
This is a dual boot system with Android 4.4.2, and Windows 8.1, based on Bay Trail (Atom Z3720) CPU. Running kernel is 3.4.43
After a long fight, i gained accesses to /system and /data partitions.
I have so copyed su binary, and changed the access mode to ugo+rx. Good !
Sadly, this is not enough to gain root access. everytime i'm issuing su command i got into a $ prompt.
I must mention i only have ADB wireless for this device: the USB is acting as an USB host, it is not possible to plug it into a PC/MAC.
My question is what i must check, do, to gain root accesses ? What should i look, try, dig ?
Thank you !
Self reply: you only need to have SU installed, as i mentionned.
Related
Hello everyone!
I've recently purchased a Vodafone Smart Tab 10 running Honeycomb 3.2.
I would like very much to root the device and kill the bloat a bit.
The hardware is good, but it seems that Honeycomb + bloatware is not the best way to go for a smooth experince...
Maybe the process would be similar for the Vodafone Smart Tab 7, too:
[Q] How to root Vodafone Smart Tab 7
Smart Tab on Vodafone's site:
Vodafone Smart Tab 7/10
Thanks.
We need a compatible CW recovery. There is the 3e recovery onboard like in Samsung devices. We have a working adb and fastboot. Bootloader is unlocked.
Sent from my SmartTab10 using Tapatalk
You can get source on
HTML:
http://www.vodafone.com/content/index/about/what/devices/vodafone_smart_tab.html
You can pull config from device.
Yeah, this device is cheap and good, but we need root for it. Come on, I'm sure that someone can make custom recovery and root for this device.
I would go and try this.
But downloading of the source would take me years on my sucky hotel internet now. Maybe when I get home.
Yes but you'll need a rooted devices to dump recovery.img and to read the partition layout. We need to root it first. I have tried the gingerbreak with gingerbreak.apk and oneclickroot but without success. Any ideas?
Sent from my SmartTab10 using Tapatalk
Does anyone know the password to bluez package of the source?
Noup. Whay they set the password at all? Any progress with the recovery buildup?
Sent from my SmartTab10 using Tapatalk
BlueZ
Unless I'm mistaking, BlueZ is a package dealing only with bluetooth functionality.
It should be of no concern in the early stages of root/custom ROM implementation.
sangemaru said:
Unless I'm mistaking, BlueZ is a package dealing only with bluetooth functionality.
It should be of no concern in the early stages of root/custom ROM implementation.
Click to expand...
Click to collapse
You are right about BlueZ. Any idea of the method we could use to root this device?
Sent from my SmartTab10 using Tapatalk
To my understanding, it's possible to perform a root through ADB.
Since the device is unlocked in just about every other possible way, it shouldn't be too much of a chore.
I'll be having a look over possible ways to do that tonight.
$ adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
liuyuanyuan prjName is <V11A>
liuyuanyuan exit adbd if usb_mass_storage is enabled on V66 or V68
error: device not found
What the f this liuyuanyuan wants from me He is good o yes
EDIT: This device does not have cmdclient & cmd_server_daemon running!
mobilx said:
$ adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
liuyuanyuan prjName is <V11A>
liuyuanyuan exit adbd if usb_mass_storage is enabled on V66 or V68
error: device not found
What the f this liuyuanyuan wants from me He is good o yes
EDIT: This device does not have cmdclient & cmd_server_daemon running!
Click to expand...
Click to collapse
I think it's more likely that you don't have the proper device drivers on your computer.
I have the links at work, I'll try to see about them tomorrow. Were you in Recovery or Development mode?
I'm using a pached by myself drivers from ZTE 3g phone archive that I found somewhere. ADB works fine. This is a root method for the Acer iconia 100 but it doesn't work because our device does not have cmdline binary in /sys/bin. I tried to pull it out from some Iconia ROM and adb pushed it to /data/local but there is the catch also. Cmd_server_daemon needs to be started which is impossible without the root permissions.
If you have the original drivers for this device please provide us a link.
Sent from my SmartTab10 using Tapatalk
Here's a link to the original V71 drivers, which I'm assuming would be the same for the V11 here.
For my device, the daemon runs properly with these drivers, but I need to have no drivers installed first, connect the device, then install the drivers with the device connected. The drivers came included on the device.
You should first try uninstalling all drivers relating to tablets/phones, then connecting the device and seeing if any drivers show up in a new detected "CD Drive" (ZTE loves doing this).
Also, any owners of the SmartTab7/SmartTab10 a.k.a v71a or v11a please vote for these devices on the new device voting thread. We need all the effort we can spend if we're going to see these devices properly supported.
mobilx said:
I'm using a pached by myself drivers from ZTE 3g phone archive that I found somewhere. ADB works fine. This is a root method for the Acer iconia 100 but it doesn't work because our device does not have cmdline binary in /sys/bin. I tried to pull it out from some Iconia ROM and adb pushed it to /data/local but there is the catch also. Cmd_server_daemon needs to be started which is impossible without the root permissions.
Click to expand...
Click to collapse
For me, i could push files to /data/local just fine, i can perform apk installations through adb, however i can't execute almost any command.
Everything would have been fine if we could do $adb shell su, but i get permissions error even with modified su file, so i have no idea what to do.
The weird thing is that cmd_server_daemon runs just fine for me, however i can't get any permissions at all.
Using adb root tells me that root is not available for production models.
Do you have the cmd_server_daemon listed in ls -l /system/bin ?
If you have you can use this Method
Sent from my SmartTab10 using Tapatalk
No, i don't have it listed. Which is weird, because I've seen mentions of it booting and running successfully... i think.
We are pretty stuck. If someone could get stock firmware. We need a boot.img or a hc 3.2 exploit.
We're not stuck at all, actually.
We have the source code, remember?
If i can find any instructions on how to integrate root with it, I can just build the rom.
I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needing a PC).
So..... Would it be possible?
This would fare better in the Android Q&A forum. I'll flag it to the forum mod and ask them to move it
Done, and Thank You Sir.
adb
pokepal101 said:
I'm sorry If I'm missing something really obvious, or if this question has been asked before, but I didn't find anything in the search, so here goes:
Firstly, as the title suggests, I'm wondering whether it would be possible to run ADB (Android Debug Bridge) inside an existing Android device. I saw this, but what I want is to be able to compile an ADB binary (plus any necessary libraries) for Android, put it on my sdcard, and run ADB commands from within a terminal emulator.
Secondly, I'm wondering whether, after installing ADB on one device (device #1), I could connect that device and another device (device #2) together, and use device #1 to perform ADB commands on device #2 (for example, rooting device #2 without needinig a PC).
So..... Would it be possible?
Click to expand...
Click to collapse
I want to start by saying I'm no expert, but to the best of my knowledge, this is how it works.
adb runs native on android, the android property is ro.secure=1 this is found in the default.prop file. ADB is run in user privilege mode with this property setting. Not all of the adb shell commands will work with the device in this mode. With ro.secure=0 property setting, adb will run with root user privileges and all adb shell commands will function. There is an adb comand that when issued will return the value of the setting, but off the top of my head I could not tell you it. The file default.prop is part of the boot.img and will load every time the device is booted, so to edit the file the boot.img would have to be unpacked, edited, repacked, and pushed to the device boot partition.
I don't know why you would want to connect two smartphones using adb and don't know if it is even possible. It is probably best to run the binary with a script on the device where you want it installed. Good Luck with your project.
Sorry, I don't think I quite understand....
fdaconta said:
Not all of the adb shell commands will work with the device in this mode
Click to expand...
Click to collapse
I'm sorry if I'm not making myself clear, but I'm talking about running the ADB client/server on an android phone (normally done on a development computer), not the ADB daemon.
fdaconta said:
It is probably best to run the binary with a script on the device where you want it installed
Click to expand...
Click to collapse
That's also not possible, as the script involves running some complicated ADB-ish things like "adb restore" and running while device #2 is turned off - hence the need for device #1.
I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
MrJinx123 said:
I'm really enjoying remix OS, So much so, I seldom use my windows partition at all any more except for one thing. Bootloader updates and firmware installations on my various android devices. (Most Nexus Player android TV boxes)
Remix shipped with adb support and I have been using it to push bulk installs onto my own and customer devices, I would like to perform the firmware updates as well and found remix does not ship with fastboot installed in system/bin. There is a fastboot file but it is for the Intel 915 graphics support libs.
Is there a way I can add it? been looking at a few pre compiled bin packages for linux but can't seem to get any of them to work correctly. can't seem to get the fastboot.bin to be executable.. even with root.
Any help would be appreciated. Asked the remix folks as I am on the beta program but have not gotten an answer.
Thanks!
Click to expand...
Click to collapse
Try the one here: it's seems to show the help page fine. Haven't checked any of the command though;
alternatively you could compile a version from source
Thanks for the lead
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
MrJinx123 said:
Looking around thru XDA , I found a few fastboot packages that should have worked. My device filesystem is RW and root is obviously present. I copy the file and chmod it as executable but still get access denied trying to execute it as root, Most the versions I found expect you to adb copy it into the device, With remix OS, I'm not sure how to to do that since there is no OTG port. If the filesystem is RW, Should I need to use adb to copy the file in? Looking at compiling a copy since the remix install I'm using is x64 on intel and maybe the fastboot executable needs to be for this specific target?
Click to expand...
Click to collapse
Definately at least executes for me; will check tomorrow if it can detect a fastboot device. One from @osm0sis : http://forum.xda-developers.com/showthread.php?t=2239421 also seems to run fine and I think its a different one; some of the others posted are a copy of that first one I posted without giving credit.
Looks like you did point me to the right one.
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
MrJinx123 said:
Since remix OS on a laptop doesn't support an OTG adb transfer... I manually copied adb, adb.bin and fast boot to the system/xbin directory as root.
Then used
chown 0:0 on all 3 files, As found in the included install script (adb shell script)
then chmod +755 (all 3 files) also tried chmod +777
No errors or complaints from the command line..
attempt to execute as user or root, Get permission denied..
"ls" the file shows -rwxrwxrwx root root ?
When I compare against other files in xbin, they all have lrwxrwxrwx. I'm assuming the "l" is a symbolic link pointing to the busybox install.
Am I missing something? that is preventing fastboot from being executable? I don't claim to be a linux expert in any way...
Click to expand...
Click to collapse
adb is already installed (/system/bin/adb); other than that I have it as 777 root:root as well, any chance you have forgotten to execute fastboot as root [su]?
Screenshot attached; and just checked if device detected in fastboot and it is.
NB with adb you might have to use adb -s 0123456789ABCDEF reboot bootloader for example as theres an emulator device running on RemixOS.
Hi there
I fiddle largely with MTK based phones and when I tweak a phone, I normally only need ADB root access. So my general process has been to:
1. OEM Unlock the device
2. unpack the boot.img and change the default.prop values (ro.adb.secure etc) to allow ADB root access.
3. Use ADB to get temporary write access using adb Root, then ADB remount Rw. Then you can pull and push files.
However I have an MT8735b, Android 7.0, Alps based device that will simply not give me ADB root access. so when I run "adb remount rw" or any of the equivalent shell scripts you can use instead, it just won't give me write access.
So I heard that newer phones based on these chipsets and also ones like 6737M are locking the device up in other ways.
My question is, does anyone have any ideas or knows anything I could try to get root access?
Any help is much appreciated.
Hi,
I'm new here afterwards I use this forum a lot of times before but its the first time I'm writting because i don't find too much information about my problem:
I have a mt6735 device with Android 5.1 unrooted, bootloader locked and a factory ROM. I know, I know... maybe you think I'm mad because I have a not rooted Android, but I can explain:
I need the phone unrooted because I use some apps which dont work propertly if the device its rooted. Furthemore I need to pass Basic integrity of SAFETYNET check.
Everything its ok but SELinux its in permissive mode by default (and f**k SAFETYNET check), and I need root access to change it. I'd it with ADB with engineer mode and enabling User2root witch give me access to root shell and the command setenforce 1. But the other day the device restarted itself and SELinux become permissive again... I needed to get access a PC install drivers again and use ADB to change it again but it isn't always an option (For example in the middle of a trip) I tried to change permissions of enforce file, but that only work before restart...
I see many solutions witch require to modify and flash boot.img but I prefer to avoid that.
My questions are the following:
1.- Its posible to change default SELinux mode? Or change permissions of the enforce file so I'll can use setenforce command without root from terminal?
2.- Its posible to run terminal (or a comand on terminal) with root privileges with user2root? It seems to be not possible, but if anyone can confirm it...
3.- Its posible to run ADB Shell locally (Without loosing configuration when device restart) to run comands like root as I do on the PC?
4.- Its posible to achieve this without flashing or using SuperSu? Maybe I ask for the imposible
Many thanks to everyone