This is a copy of the comment I made in the [Help] topic, figured I would make a separate post since that thread is a mess. Anyway, credit for the method is to krytikul and evelpotatoman. I am not responsible for any damage/unwanted results/house fires. Use at your own risk yada yada.
Without furher ado, here is my tutorial for those who want working SuperSU on their MDZ-16-AB Mi Box 3. Warning: since the bootloader isn't unlockable yet, you will have to connect a laptop to run some commands EVERY TIME YOU BOOT UP THE MI BOX. If you do not connect to run the specified commands YOUR DEVICE WILL BOOTLOOP, it won't even be able to boot in unrooted state. Luckily, this doesn't apply to waking up from standby mode, so as long as you keep your Mi Box plugged in and don't power it off, you'll be fine.
You will need:
A USB male to male cable (I made one myself soldering two cable plugs together)
Mi Box Marshmallow userdebug firmware ROM (this guide will not work if you are already on Nougat test build)
SuperSU installation files
The ability to use adb on your computer
The steps:
Put the downloaded userdebug firmware ROM on a FAT32 formatted drive.
Enable developer options on the Mi Box. This can be done in your settings, find "About" and then click on "build" 7 times to enable the developer options. It will confirm you've done this with an on-screen toast notification.
Connect the Mi Box to your computer and check if a device comes up when typing "adb devices" in command prompt. If not, wait for the Mi Box to display a dialogue confirming you want to allow adb on this computer.
Type "adb reboot recovery" to put the Mi Box in recovery mode. Once in recovery, unhook the cable and plug in your usb, click "Apply update from EXT" then "Update from udisk" and select MiBOX3_USA_once_r454.zip, then just let the update do it's thing.
Reboot the device. Once we're back, see if the box is still under adb devices.
Now run these commands:
Code:
adb root
adb remount
adb disable-verity
adb reboot
The device will reboot. Once it's rebooted, run these commands to disable OTA updates (otherwise it will immediately update to an unrootable firmware
Code:
adb root
adb remount
adb shell pm disable com.google.android.gms/.update.SystemUpdateService
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
adb reboot
Wait for the device to reboot. Now we've disabled OTA updates we can install SuperSU. Unzip the SuperSU installer and run the installer BAT script. When the script is done, it will seem as if the device is bootlooping. From now on, this will happen EVERY TIME THE DEVICE BOOTS. If you do not connect to run the specified commands YOUR DEVICE WILL BOOTLOOP, it won't even be able to boot in unrooted state. Below are the steps you should perform to get your device to boot in SuperSU-rooted state.
While the bootanimation is running, keep executing "adb devices" until your device is in the list.
Once the Mi Box is in the adb devices list, type "adb root" and press enter. your device will be disconnected from adb again.
Keep executing "adb devices" again until the Mi Box reappears. When it's there, type "adb shell setenforce 0"
All these steps are performed while the bootanimation is playing. The device will boot shortly after the last command is executed. Be patient as it can take a while for the device to re-enter the adb devices list.
thanks. all works fine
maybe i'd try this.
but is there a way also to undo the rooting without reflashing the firmware? or is there also a script to undo or remove the root?
Hey guys;
hope you are all doing great, I need your help.
I have Oreo on my device and I really need to have permission to change my stupid launcher. I hate the original one.
does anybody know how to give this permission to my device when I have Oreo?
you know? before Oreo there were a lot of problem with device and wifi.
But all gone with Oreo, and now I don't have any admin Permission.
please help.
thanks a lot.
arashdan89 said:
Hey guys;
hope you are all doing great, I need your help.
I have Oreo on my device and I really need to have permission to change my stupid launcher. I hate the original one.
does anybody know how to give this permission to my device when I have Oreo?
you know? before Oreo there were a lot of problem with device and wifi.
But all gone with Oreo, and now I don't have any admin Permission.
please help.
thanks a lot.
Click to expand...
Click to collapse
N o Can Do!!
Final answer.......
The link to google drive is dead can someone plz repost
LgPWN'd said:
The link to google drive is dead can someone plz repost
Click to expand...
Click to collapse
Won't do you much good if your mdz-16-ab is not on a MM build
Uart
bigtalker said:
Won't do you much good if your mdz-16-ab is not on a MM build
Click to expand...
Click to collapse
I have decided to go a different route...
Ordered a uart rig
LgPWN'd said:
I have decided to go a different route...
Ordered a uart rig
Click to expand...
Click to collapse
Good luck wid dat!
I'm happy to tell you magisk and twrp on mdz-16-ab is possible. And I managed to do this. It need a small hack on u-boot. I need someone who have this device to do more tests for this method.
Related
I looked all over the internet for help with this phone. I rooted it for a friend and a week later, he said he restarted the phone and everything started force closing.
I troubleshot all day, and came to figure out that my only known to me as of now, is flashing CWM to it, via ADB. I am having several issues with setting up ADB, and getting the phone to communicate with my computer. Device manager DOES show that there is an ADB device installed correctly, so what would my next move be? I got the phone into FTM mode, (fastboot?) and I know that that is what I need to do to get ADB to communicate with my phone.
halp pls
Really no one can help???
bamp
cammiso94 said:
bamp
Click to expand...
Click to collapse
ADB Drivers for Windows Vista/7
Tutorial- http://www.youtube.com/watch?v=RDA8PpPSFuk
If you havn't found this yet...
Your answer is here: androidforums.com/flash-all-things-root/ Good luck!:good:
CWM Beta
From Android Forums ... Thanks to Junkie2100
this is an unfinished copy of cwm, tested to be almost completely functional
standard warnings apply, use at your own risk, you try to blame me for breaking your phone i will laugh at you
instructions:
fastboot method is possible, but i will go through the terminal/adb method
download the recovery file, and put it on the root of your sd. no folders, just directly on the sd
get your phone rooted and get a copy of terminal emulator or connect to it through adb on your computer, adb will require zte drivers and the adb program on the pc. the choice is yours
fire up adb by typing
Code (Text):
adb shell
in the command prompt, if its not working you dont have adb in the directory youre in, just copy adb.exe and the two .dll files to c:\windows\system32\ and itll work from anywhere, or learn how command prompt works
or fire up terminal emulator on the phone
on adb shell or terminal emulator type
Code (Text):
su
dd if=/sdcard/flash_cwm_test2.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
you will then need to run
Code (Text):
reboot recovery
and then hit reboot when cwm comes up, if it asks to disable recovery flashing press yes or it will put stock recovery back next time the rom boots
known bugs:
unmounting doesnt work
downloads:
w.ww.4shared.com/file/2qBR2Kfr/flash_cwm_test2.html
i apologize for it being 4shared, if someone wants to make a mirror ill put it up
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
You need to have USB debugging enabled on your phone, adb installed on your computer and the LG drivers installed. If you have all that the steps to unlock are quite clear.
Also your phone needs to be on and you need to keep an eye on it as you will have to enable a couple of things when they pop up on your phone, one is to allow your computer to see your phone in debugging mode and the other is to Grant super user permission.
batsup606 said:
Okay so as we all know Bootloader was unlock and they specify the steps, but im not able to do the command prompt section.(Below)
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/twrp-2.8.0.0_vs985-signed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
I have the twrp image on my storage, but i used mtp not Ethernet due to the reason that Ethernet mode won't read my phone.
Can anyone help me on how to void my warranty and get CP working
Please no hating, barely learning this stuff
Thanks!!
Click to expand...
Click to collapse
You need to be able to get the phone operating in Ethernet mode; otherwise the computer cannot pass it commands. Alternatively, you can use a terminal emulator ON your phone itself. That's what I did as I didn't want to boot my desktop rig up before I left. It works exactly the same, except you don't type "adb shell", just open the term emu and start with the SU line.
It works fine if you do it from a terminal emulator on ur phone just fyi
laxattack said:
It works fine if you do it from a terminal emulator on ur phone just fyi
Click to expand...
Click to collapse
Can confirm. This is the way I did it since I don't have access to a computer until later tonight. Just type the exact commands (except for adb shell) in a terminal emulator and you are done.
I can also confirm this is working.
I had to download the LG updater or whatever (when you first plug the phone in; says installer) despite Win7 saying it had autoinstalled the drivers then ADB could see the device when in ethernet mode.
Also the last command didn't work (guess I didn't have the TWRP in the right place) and was forced to do a battery pull after the Factory Reset (didn't erase my data or settings), booted fine and then I just flashed the recovery with Flashify (and now can get into recovery) but YMMV.
FLASHIFY
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
airintak25 said:
Hey whats up the easiest way to install this is an app called Flashyify in play store works great im unlocked without using adb. Let the roms begin. Thanks for the hard work that everyone put in. Just put twrp image on phone before you open flashyify and open and install and recovery will be installed
Click to expand...
Click to collapse
+1
Hi!
I have RN2 with MIUI 16.6.7.0 with root access.
ADB v1.0.32
Win 8.1
If I run "adb devices" when phone is running system, I get response "s/n device" as I should. But when I boot phone to recovery (MI-Recovery 2.0.1) I get "s/n unauthorized".
I have tried rebooting PC and phone, disabling and enabling USB debugging, deleting adbkey and adbkey.pub on PC (only instance was in users/user/.android/), revoking USB debugging authorizations, changing USB ports. Nothing.
The last thing I did:
1. reboot phone to system.
2. developer options > turn developer options on/off > turn debugging on/off <> Revoke USB Debugging Authorization
3. reconnect phone to PC
4. was asked: RSA key fingerprint + always allow from this computer > OK
5. run "adb devices" gives "s/n device"
6. disconnect phone
7. power off phone
8. phone to recovery
9. reconnect phone
10. run "adb devices" gives "s/n unautorized"
11. disconnect phone from USB
12. run "adb kill-server"
13. run "adb start-server"
14. reconnect phone
15. run "adb devices" gives "s/n unautorized"
I guess something is wrong with recovery mode on the device. Any ideas?
Thank you
MK
+ run "adb shell" gives " error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device."
+ from hxxps://android.googlesource.com/platform/system/core/+/d5fcafaf41f8ec90986c813f75ec78402096af2d
"On the device, vendors public keys are installed at build time in /adb_keys. User-installed keys are stored in /data/misc/adb/adb_keys."
On my device user-installed keys are stored in /data/misc/adb/adb_keys. The only other instance of adb_keys is /bin/adb_keys. If it has any relevance.
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Namaless said:
You need to check in the device the popup, the device ask if you want authorize your computer for connection with adb, remember you need to enable adb debug first with push 7 times on miui version into about device.
Click to expand...
Click to collapse
Hi!
Thanks a million for your reply. :good:
I did all that already in steps 2, 4 and 5 and it worked. My problem is adb in stock recovery mode.
In recovery adb isn't available you can enable only the adb transfer from the advance menu.
Click to expand...
Click to collapse
Damn I have much to learn (hundreds of pages in a few days and I still dont know anything . So stock recovery doesn't come with ADB access and I am trying to do something that can not be done? ClockworkMod recovery for example should have ADB support if I understand correctly?
I also have that proble my device not connected to phone what I do tell me..
Jay's said:
I also have that proble my device not connected to phone what I do tell me..
Click to expand...
Click to collapse
If problem is PC <> phone then install drivers for your phone on PC.
Or describe your problem better.
Poslano z mojega Redmi Note 2 z uporabo Tapatalk
Hello everyone,
I've spent a little bit of time trying to unlock the bootloader/obtain root on the recently released Mi Box (Android TV MDZ-16-AB).
I spliced together a USB-A Male to Male cable and first started messing around with ADB.
I figured if I could get into fastboot (bootloader mode) I might be able to make some progress.
Here are some issues I'm running into:
1. Rebooting to the bootloader via the adb command(s) (adb reboot bootloader/adb reboot-bootloader) does not work, the device simply reboots without going into bootloader mode.
2. Rebooting to the bootloader through the recovery (image below ) does not work, the device simply reboots without going into bootloader mode .
3. All of the automated rooting applications fail to work (As I expected since this is MM)
Does this rom not have fastboot or download mode enabled?
If anyone could provide some help it would be greatly appreciated.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
did you try to sideload SU zip package? Just got my MI Box today, haven't opened it. what did you do to get it to boot into recovery mode?
mattvirus said:
did you try to sideload SU zip package? Just got my MI Box today, haven't opened it. what did you do to get it to boot into recovery mode?
Click to expand...
Click to collapse
Sideloading anything other than official firmware won't work in the stock recovery unfortunately (afaik). I tried sideloading a SuperSU zip with no luck.
I also tried sideloading the official firmware ( "MiBOX3S_USA_Once_260516.zip") for the Mi Box 3S (not Android TV) since the hardware is the same. It seems that they sign both the Mi Box and Mi Box 3S the same since signature verification passed when trying to flash the mentioned firmware, but the process failed when checking the date of the build.
To get into recovery you can use the adb command "adb reboot recovery" or you can hold both the back button and center button of the directional pad while booting.
Yep I tried same and had same result. I have some older fw packages I will try. I thought maybe their stock recovery might not check sig . Wishful thinking I know, oh well....
Does your USB port work for normal flash drives? I can't get anything to work on it.
Can you upload the full latest official firmware or give link to it?
I can try to help.
I was able to get this rooted, but haven't been able to unlock the bootloader.
Download MiBOX3S_USA_once_r454.zip from 4PDA.ru unrar it and put it on a USB stick.
Turn on adb from the developer options, connect, and "adb reboot recovery"
Unplug the USB cable and plug in the USB stick. Choose "Install from EXT">"From UDISK", and flash the update.
Reboot it and plug the USB cable back in. Re-enable usb debugging (if your settings were cleared) then disable dm-verity by typing "adb root" then "adb disable-verity" and then "adb reboot"
Once it reboots, you are now free to modify the system partition as you see fit by typing "adb root" then "adb remount". you are effectively 'rooted' at this point.
I went further and manually installed SuperSU to enjoy some rooted app goodness, but to be honest, it was a pain.
One thing I noticed is that the most recent OTA wipes your changes, so you may want to disable updates until I can come up with a more elegant solution:
Code:
adb root
adb shell pm disable com.google.android.gms/.update.SystemUpdateService
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
** edit **
I have a bootloader unlock authorization for this device from xiaomi, but I can't seem to get it into either bootloader mode or EDL mode. Any help on this front would be appreciated.
evilpotatoman said:
I went further and manually installed SuperSU to enjoy some rooted app goodness, but to be honest, it was a pain.
Click to expand...
Click to collapse
What method did you use to install SuperSU? Was it necessary to flash anything, or did you just copy the binary into the system partition? I'd like to toss tasker and the sixaxis controller apps on this box to expand its functionality a bit, but not having SuperSU is a showstopper.
Can you guys tell me how this unit compares to the other "Andoird TV boxes". I just got this from walmart last week. It seems to lack an SD card, but has a USB port etc... I see it has bluetooth. But for $69.00 I see andorid boxes on ebay for 24 or so from china.
Thanks
evilpotatoman said:
I was able to get this rooted, but haven't been able to unlock the bootloader.
Download MiBOX3S_USA_once_r454.zip from 4PDA.ru unrar it and put it on a USB stick.
Turn on adb from the developer options, connect, and "adb reboot recovery"
Unplug the USB cable and plug in the USB stick. Choose "Install from EXT">"From UDISK", and flash the update.
Reboot it and plug the USB cable back in. Re-enable usb debugging (if your settings were cleared) then disable dm-verity by typing "adb root" then "adb disable-verity" and then "adb reboot"
Once it reboots, you are now free to modify the system partition as you see fit by typing "adb root" then "adb remount". you are effectively 'rooted' at this point.
I went further and manually installed SuperSU to enjoy some rooted app goodness, but to be honest, it was a pain.
One thing I noticed is that the most recent OTA wipes your changes, so you may want to disable updates until I can come up with a more elegant solution:
Code:
adb root
adb shell pm disable com.google.android.gms/.update.SystemUpdateService
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
** edit **
I have a bootloader unlock authorization for this device from xiaomi, but I can't seem to get it into either bootloader mode or EDL mode. Any help on this front would be appreciated.
Click to expand...
Click to collapse
what do you lose with this firmware? does it still have playstore and so on? would be nice to root the stock firmware. wonder if this "dirty cow" exploit could be utilized in someway...
I've been working with this box for a week now and managed to replicate all of the steps evilpotatoman has explained EXCEPT for the manual SuperSU install and the update disable. Some more technical advice would be appreciated. I can attest to the issue that this device is similar to the mi box 3 AA rev but several more hoops to jump through to get a proper root. I don't want to keep the device if I can't root it. Hopefully a solution pops up before my refund period ends.
Goonshark said:
I've been working with this box for a week now and managed to replicate all of the steps evilpotatoman has explained EXCEPT for the manual SuperSU install and the update disable. Some more technical advice would be appreciated. I can attest to the issue that this device is similar to the mi box 3 AA rev but several more hoops to jump through to get a proper root. I don't want to keep the device if I can't root it. Hopefully a solution pops up before my refund period ends.
Click to expand...
Click to collapse
is this new image you flat the same as the original image? as in, still have plays tore and everything? i am still waiting on a male to male cable so just gathering info...
Goonshark said:
I've been working with this box for a week now and managed to replicate all of the steps evilpotatoman has explained EXCEPT for the manual SuperSU install and the update disable. Some more technical advice would be appreciated. I can attest to the issue that this device is similar to the mi box 3 AA rev but several more hoops to jump through to get a proper root. I don't want to keep the device if I can't root it. Hopefully a solution pops up before my refund period ends.
Click to expand...
Click to collapse
The disabling of update should be simple. just enter those commands at adb prompt...
dustintinsley said:
The disabling of update should be simple. just enter those commands at adb prompt...
Click to expand...
Click to collapse
Your right, didnt manage to do it right the last time. The update.zip evilpotatoman posted is the same except for the file browser, live channel, and movie player apps.
Now im at the point where i need supersu. You cant sideload, thats for firmware. Do i need some script or location to copy or apk? Not sure how to manually install it.
Goonshark said:
Your right, didnt manage to do it right the last time. The update.zip evilpotatoman posted is the same except for the file browser, live channel, and movie player apps.
Now im at the point where i need supersu. You cant sideload, thats for firmware. Do i need some script or location to copy or apk? Not sure how to manually install it.
Click to expand...
Click to collapse
so play store is on the firmware posted by evilpotatoman?
dustintinsley said:
so play store is on the firmware posted by evilpotatoman?
Click to expand...
Click to collapse
yes
Goonshark said:
yes
Click to expand...
Click to collapse
sweet! i was concerned it would be a chinese firmware image or something. attached is a file that should flash the new boot images needed for this to work but allow you to keep your updated system will remain untouched. you will use the steps as before:
Code:
1. Download mibox_3s_boot_upgrade.zip, unzip it and put the contents on a USB stick.
2. Turn on adb from the developer options, connect, and "adb reboot recovery"
3. Unplug the USB cable and plug in the USB stick. Choose "Install from EXT">"From UDISK", and flash the update.
4. Reboot it and plug the USB cable back in. Re-enable usb debugging (if your settings were cleared) then disable dm-verity by typing "adb root" then "adb disable-verity" and then "adb reboot"
5. Once it reboots, you are now free to modify the system partition as you see fit by typing "adb root" then "adb remount". You are effectively 'rooted' at this point.
To disable system updates:
adb root
adb shell pm disable com.google.android.gms/.update.SystemUpdateService
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
This method will allow you to be running at the latest system update that is available...
Now, to work on installing SuperSU.... Like I said do not get my cable until tomorrow, so I can't test until then, but I think I have a way to easily install it.... Will update.
dustintinsley said:
sweet! i was concerned it would be a chinese firmware image or something. attached is a file that should flash the new boot images needed for this to work but allow you to keep your updated system will remain untouched. you will use the steps as before:
Code:
1. Download mibox_3s_boot_upgrade.zip, unzip it and put the contents on a USB stick.
2. Turn on adb from the developer options, connect, and "adb reboot recovery"
3. Unplug the USB cable and plug in the USB stick. Choose "Install from EXT">"From UDISK", and flash the update.
4. Reboot it and plug the USB cable back in. Re-enable usb debugging (if your settings were cleared) then disable dm-verity by typing "adb root" then "adb disable-verity" and then "adb reboot"
5. Once it reboots, you are now free to modify the system partition as you see fit by typing "adb root" then "adb remount". You are effectively 'rooted' at this point.
To disable system updates:
adb root
adb shell pm disable com.google.android.gms/.update.SystemUpdateService
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
This method will allow you to be running at the latest system update that is available...
Now, to work on installing SuperSU.... Like I said do not get my cable until tomorrow, so I can't test until then, but I think I have a way to easily install it.... Will update.
Click to expand...
Click to collapse
unfortinatly the file is not flashable something about a signiture and footer. I been trying all kind of stuff too wish didn't have to do long setup after wipe
mr0187 said:
unfortinatly the file is not flashable something about a signiture and footer. I been trying all kind of stuff too wish didn't have to do long setup after wipe
Click to expand...
Click to collapse
odd, it should work. once i get my cable i can actually test, i will have a smoother method soon...
mr0187 said:
unfortinatly the file is not flashable something about a signiture and footer. I been trying all kind of stuff too wish didn't have to do long setup after wipe
Click to expand...
Click to collapse
Ok, I am pretty sure i found the error with the zip file i posted. attached is updated boot image flash that should work this time. please let me know.
I am trying to root my tablet but i cannot find anything that has the model listed specifically. Any help would be greatly appreciated.
Smartab
Manufacturer Southern Telecom
Model ST1009
Android version 6.0.1
Firware 1.0.0
Kernel version 3.14.0+
Build St1009_20160629
Bn 02.04.009.106.01
I'm trying to do the same thing, so far with no luck. I will add that this tablet goes by other names, including Polaroid Q1010, Q10, and M10.
I've tried all the usual Android app one-click root apps (iroot, vroot, kingroot, etc.) and they all failed. I tried a PC program called Impactor, which also failed. I've been able to push Supersu.apk, su, and busybox to /data/local/tmp but can't get any further. I tried an adb sideload of something called Poladoiq10root.zip and it complained about an invalid signature.
I've tried adb on Windwos XP, 8.1, and Ubuntu 16.10. I can see the USB device in Ubuntu but can't mount it. The suggestion here (http://forum.xda-developers.com/showthread.php?t=2684210) is that you can open nautilus in su mode and then move stuff on the tablet but nautilus doesn't see the tablet even though the USB driver is loaded. In short, a brick wall at every turn.
How hard can it be to root a generic Chinese tablet?
Michele31415 said:
I'm trying to do the same thing, so far with no luck. I will add that this tablet goes by other names, including Polaroid Q1010, Q10, and M10.
I've tried all the usual Android app one-click root apps (iroot, vroot, kingroot, etc.) and they all failed. I tried a PC program called Impactor, which also failed. I've been able to push Supersu.apk, su, and busybox to /data/local/tmp but can't get any further. I tried an adb sideload of something called Poladoiq10root.zip and it complained about an invalid signature.
I've tried adb on Windwos XP, 8.1, and Ubuntu 16.10. I can see the USB device in Ubuntu but can't mount it. The suggestion here (http://forum.xda-developers.com/showthread.php?t=2684210) is that you can open nautilus in su mode and then move stuff on the tablet but nautilus doesn't see the tablet even though the USB driver is loaded. In short, a brick wall at every turn.
How hard can it be to root a generic Chinese tablet?
Click to expand...
Click to collapse
Have you tried unlocking the bootloader in settings? The option is in developer options once unlocked. I'm curious what exactly this does and if it'll help making root possible. I really hope someone figures this out! Maybe KingRoot will eventually get around to it.
I added the st1009 to the list on KingRoot's device request Google doc.
Also have same tablet no luck here on the one click root apps please post update if root comes available
Racer030 said:
I am trying to root my tablet but i cannot find anything that has the model listed specifically. Any help would be greatly appreciated.
Smartab
Manufacturer Southern Telecom
Model ST1009
Android version 6.0.1
Firware 1.0.0
Kernel version 3.14.0+
Build St1009_20160629
Bn 02.04.009.106.01
Click to expand...
Click to collapse
I just got the smartab ST7150 from the Walmart Black Thursday sale for $28
SmartTab ST7150 7inch tablet specs include a 7inch display with an HD resolution of 1024×600 pixels, quadcore processor, 1GB of RAM, 16GB of memory, Micro SD support, Android 7.1.2 Nougat operating system, front and rear cameras, WiFi, Bluetooth and a 2500mAh battery which should give you a good five hours of battery life. Although GPS support on the SmarTab 7inch ST7150 Tablet is not highlighted by Walmart’s product listing,
I am able to see it fine on both windows 7 and My Linux Mint Mate duel boot configuration. Adb works fine and I can boot the tablet into the recovery mode, but it appears that there is no fastboot or bootloader partition installed on it or it is somehow hidden in Nougat. Diskinfo does not list a bootloader partition but because of Nougat's enhanced security, maybe it is hidden without root? I'm not sure.
it does however, have the option in developer options to allow the bootloader to be unlocked. as far as I know, from my Nextbook Ares 8a root solution thread, this does not unlock the bootloader. It allow the bootloader to be unlocked with the fastboot command:
Code:
fastboot flashing unlock
One problem is that I can't get a booloader mode. from recovery, when I choose it, it boots to a black screen. It appears that there is not bootloader partition.
Maybe this was done on purpose to foil would be rooters?
have smartab st1009 too
Racer030 said:
I am trying to root my tablet but i cannot find anything that has the model listed specifically. Any help would be greatly appreciated.
Smartab
Manufacturer Southern Telecom
Model ST1009
Android version 6.0.1
Firware 1.0.0
Kernel version 3.14.0+
Build St1009_20160629
Bn 02.04.009.106.01
Click to expand...
Click to collapse
Just checking to see if you have any new info on rooting or backup upsoftware solutions for this tablet
thankyou for your time
Managed to unlock bootloader, but no TWRP I can find.
I did manage to unlock the bootloader on my Polaroid Q1010/Southern Telecom ST1009, running 6.0.1. But I haven't been able to find a custom recovery to install as of yet. The method that worked for me to unlock the bootloader was first enabling developer options and allowing both OEM Unlocking and USB Debugging, then I opened ADB and typed "adb reboot fastboot", and that brought up a green screen with an android logo in the middle. There was no text visible on the tablet, but fastboot commands worked, most importantly "fastboot flashing unlock" which did the trick. Now I just have to figure out how to either build a custom recovery or pull the files needed for someone else to build it, as I'm not a developer, just a hobbyist. I hope this helps, and I'll update if I get farther.
Note: I just noticed that I couldn't detect this tablet at all via USB unless it was undocked from it's keyboard.
Have you tried searching for this model as "Viking" or possibly, "Viking Pro"? Good Luck guys. I had a rooted one. Your journey is an educational one.
i managed to get mine recognized by adb, tryed adb reboot fastboot, gets to the smartab powered by android screen, and hangs. tryed the oem unlock command, since that could very well be fastboot. no responce from device.
---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------
HippieFlasher said:
I did manage to unlock the bootloader on my Polaroid Q1010/Southern Telecom ST1009, running 6.0.1. But I haven't been able to find a custom recovery to install as of yet. The method that worked for me to unlock the bootloader was first enabling developer options and allowing both OEM Unlocking and USB Debugging, then I opened ADB and typed "adb reboot fastboot", and that brought up a green screen with an android logo in the middle. There was no text visible on the tablet, but fastboot commands worked, most importantly "fastboot flashing unlock" which did the trick. Now I just have to figure out how to either build a custom recovery or pull the files needed for someone else to build it, as I'm not a developer, just a hobbyist. I hope this helps, and I'll update if I get farther.
Note: I just noticed that I couldn't detect this tablet at all via USB unless it was undocked from it's keyboard.
Click to expand...
Click to collapse
send me your repo and i will develop twrp for your tablet. it will take less than a day.
Hey did you develop the twrp for the tablet? I too am looking to root it
the_R00ter said:
i managed to get mine recognized by adb, tryed adb reboot fastboot, gets to the smartab powered by android screen, and hangs. tryed the oem unlock command, since that could very well be fastboot. no responce from device.
---------- Post added at 06:45 PM ---------- Previous post was at 06:43 PM ----------
send me your repo and i will develop twrp for your tablet. it will take less than a day.
Click to expand...
Click to collapse
Hey did you develop the twrp for the tablet? I too am looking to root it.
Is there any way to update this tablet to latest android I can't find anything on it
Unlocked with fastboot, rooted with Magisk:
Code:
adb reboot-bootloader
once in fastboot mode (it takes a few seconds or so for the screen to show fastboot mode):
Code:
fastboot flashing unlock
I couldn't get kingoroot ro kingroot to root the device. You can use mtk-su from this thread (download to PC, extract and use arm64). Once extracted place mtk-su into your adb/platform-tools folder then push it to the tablet, and follow the rest of the commands:
Code:
adb push mtk-su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 mtk-su
./mtk-su
That will pop a root shell and make SELinux permissive. If your tablet is on Android 7.0 (Nougat), pull the boot image to internal storage (make sure you are still in a root shell on the tablet. This may have to be repeated):
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/boot.img
Now download the latest Magisk zip, extract it to your PC and open the common folder and copy the magisk.apk to you adb/platform tools folder and install it on the tablet:
Code:
adb install magisk.apk
Once installed, open magisk and select the install option, then patch a file. Select your boot.img you just pulled. Let Magisk patch it. It will be saved to /sdcard/Download/magisk_patched.img. Then you need to reboot to fastboot again and flash the boot image.
Code:
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
You are now unlocked and rooted.
I also have an ST7150. I'd really like to root it since 1gb ram isn't worth a damn. I tried a good handful of apps and such (kingroot, framaroot, etc...) all failed. My bootloader is able to be unlocked and I have usb debugging enabled... I guess ill give adb a try and dabble til I get bored with, as Im pretty noob when it comes to software, I went to school for electronic engineering, which is more or less hardware, so I'm hoping someone with some extensive knowledge will delve into this and find us all a solution.
Error running mtk-su
DragonFire1024 said:
Unlocked with fastboot, rooted with Magisk:
Code:
adb reboot-bootloader
once in fastboot mode (it takes a few seconds or so for the screen to show fastboot mode):
Code:
fastboot flashing unlock
I couldn't get kingoroot ro kingroot to root the device. You can use mtk-su from this thread (download to PC, extract and use arm64). Once extracted place mtk-su into your adb/platform-tools folder then push it to the tablet, and follow the rest of the commands:
Code:
adb push mtk-su /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 mtk-su
./mtk-su
That will pop a root shell and make SELinux permissive. If your tablet is on Android 7.0 (Nougat), pull the boot image to internal storage (make sure you are still in a root shell on the tablet. This may have to be repeated):
Code:
dd if=/dev/block/mmcblk0p10 of=/sdcard/boot.img
Now download the latest Magisk zip, extract it to your PC and open the common folder and copy the magisk.apk to you adb/platform tools folder and install it on the tablet:
Code:
adb install magisk.apk
Once installed, open magisk and select the install option, then patch a file. Select your boot.img you just pulled. Let Magisk patch it. It will be saved to /sdcard/Download/magisk_patched.img. Then you need to reboot to fastboot again and flash the boot image.
Code:
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
You are now unlocked and rooted.
Click to expand...
Click to collapse
@DragonFire1024 I followed these instructions but I when I get to the step to run "mtk-su" I get this error:
Code:
./mtk-su: not executable: 64-bit ELF file
and just for clarification, I am running
Code:
chmod 755 mtk-su
beforehand but it does not seem to make a difference.
ligmo said:
once in fastboot mode (it takes a few seconds or so for the screen to show fastboot mode):
I couldn't get kingoroot ro kingroot to root the device. You can use mtk-su from this thread (download to PC, extract and use arm64). Once extracted place mtk-su into your adb/platform-tools folder then push it to the tablet, and follow the rest of the commands:
That will pop a root shell and make SELinux permissive. If your tablet is on Android 7.0 (Nougat), pull the boot image to internal storage (make sure you are still in a root shell on the tablet. This may have to be repeated):
Now download the latest Magisk zip, extract it to your PC and open the common folder and copy the magisk.apk to you adb/platform tools folder and install it on the tablet:
Once installed, open magisk and select the install option, then patch a file. Select your boot.img you just pulled. Let Magisk patch it. It will be saved to /sdcard/Download/magisk_patched.img. Then you need to reboot to fastboot again and flash the boot image.
You are now unlocked and rooted.
@DragonFire1024 I followed these instructions but I when I get to the step to run "mtk-su" I get this error:
and just for clarification, I am running beforehand but it does not seem to make a difference.
Click to expand...
Click to collapse
Are you sure you downloaded the proper ARM version of mtk-su? you will have to use arm64 mtk-su. And I doubt that it's been patched.
DragonFire1024 said:
Are you sure you downloaded the proper ARM version of mtk-su? you will have to use arm64 mtk-su. And I doubt that it's been patched.
Click to expand...
Click to collapse
@DragonFire1024
I did but I think the issue is my version of this tablet is using an Intel atom x3 Sofia processer. And this is for mtk. Please correct me if I'm wrong.
ligmo said:
@DragonFire1024
I did but I think the issue is my version of this tablet is using an Intel atom x3 Sofia processer. And this is for mtk. Please correct me if I'm wrong.
Click to expand...
Click to collapse
That is correct. unfortunately this will only work on devices that have a mediatek CPU.