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
Enabling USB Debugging through ADB? Im Stuck at Black Screen W/ "Unauthorized" in ADB
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Mcfinnipoop said:
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Click to expand...
Click to collapse
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
macstibs said:
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
Click to expand...
Click to collapse
No recovery if bootloader remains locked.
Davey126 said:
No recovery if bootloader remains locked.
Click to expand...
Click to collapse
Still a pretty nice tablet - sucks that there's seemingly no fix to this (especially after I paid $100 for a new lcd)...
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.
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.
Hey, I have a problem with the adb device being unauthorized. I need adb for remapping a button on my phone (doesn't matter, the bottom line is I want it being authorized). I know this is a common problem, but I just couldn't find any other solutions.
USB debugging is enabled, the device is unauthorized though.
What I've tried so far:
- deleting the adb keys from my phone (/data/misc/adb) and from my PC c:\users\x\.android
- adb pushing the keys from my PC to the phone in Recovery
- running some script I've found on xda
- flashing a new Kernel
I DO NOT have the option to revoke USB authorization in the developer settings. Is there a way to revoke them without it? I never receive the promt to enable debugging.
I have a Galaxy S8, I'm currently on a custom PIE ROM that's based on stock Samsung. I have used adb on the same ROM with the same Kernel before.