First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
teletype said:
I just managed to get TWRP running on the new Shield console, and installed SuperSU successfully. Two caveats: the display is upside down, and the USB host ports don't work. I had to plugin a mouse via an OTG cable in order to interact with it. ETA: That's only an issue when booted to TWRP. Everything's working fine in the stock ROM after rooting.
Procedure:
- enable developer tools / USB debugging
- adb push supersu.zip /sdcard
- adb reboot bootloader
- fastboot oem unlock
- fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img
- unplug USB cable, connect mouse via USB, install SuperSU
TWRP boot image is attached. Off to explore...
EDIT: by request, some more detailed instructions:
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Go to Settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download and extract recovery.zip from this thread.
Head to the SuperSU forum and download the latest version.
Open a command prompt and navigate to the directory where you downloaded everything. (Google this for your OS if you don't know how).
With the Shield still booted, run "adb push supersu.zip /sdcard" (change supersu.zip to appropriate file name). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
If that worked fine, run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done (this was the case on my Xperia Z3 Compact). I will say that Grid streaming still works fine after doing this.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is visible.
Run "fastboot oem unlock" and follow the prompts on the screen. Your bootloader is now unlocked.
Now, boot the TWRP image with: "fastboot boot twrp-2.8.6.0-shieldtv-unofficial.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting.
You should now see a TWRP recovery menu (upside down for now).
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse
does this have to be done with an otg cable
You can use the supplied micro USB cable to do the adb portion. You shouldn't ever need otg with this device since it also has 2 full sized USB ports.
Sent from my nexus 9 using XDA Free mobile app
Instructions got updated
Hi,
I have updated the instructions to ones that more closely aligned with my experience of doing this. The initial instructions were good for me - but some were in slightly the wrong order or not quite clear enough to be immediately intuitive. I've tried to fix that Hope it helps.
On the Shield device, head to Settings -> About, and click "Build number" 7 times. This will enable Android's Developer options.
Exit settings, then go back in to settings -> Developer options, and enable USB debugging.
Install the ADB/fastboot drivers and utilities on to your PC if you don't already have them. When "adb devices" shows your Shield, you're good to go.
Download the latest Super user zip file from the super user thread here.
Download and extract the recovery file from here. (it needs to be a .img not a .zip)
run "adb reboot bootloader". Your device should shut down, and display the Fastboot screen after a few seconds.
FOLLOW THE NEXT THREE INSTRUCTIONS AT YOUR OWN RISK. This WILL wipe all your user data, back it up with ADB first if you want to preserve it. DISCLAIMER #2: I have no idea if there are any DRM keys or anything that get wiped when this is done.
This step will unlock your bootloader to enable booting unsigned images.
Run "fastboot devices" and make sure your Shield is listed when you do so.
Run "fastboot oem unlock" and follow the prompts on the Shield's screen. You use the power button on the shield device itself to navigate the menu, and long press to select an option. Once you have confirmed, this can take along time to unlock (hour and a half for me on the Pro version). Your bootloader is now unlocked.
"Fastboot reboot" to reboot to AndroidTV.
run "adb push supersu.zip /sdcard/" (change supersu.zip to appropriate file name that you downloaded earlier). This will upload the SuperSU update zip to your device, which you'll install from TWRP.
Now, boot the TWRP image with: "fastboot boot RECOVERYFILENAME.img" - Note: I used this instead of "fastboot flash" so I could keep the stock recovery around, to grab an image of it after rooting. (change the name of the file in the instructions to the name of your recovery file that you downloaded).
After a short while you should now see a TWRP recovery menu.
Connect a keyboard or mouse via OTG cable, and select "Install", navigate to your SuperSU zip, select it, and follow the prompts.
Click "reboot" and you should now be rooted.
Click to expand...
Click to collapse
Anyone tried kingroot?
Sean09 said:
Anyone tried kingroot?
Click to expand...
Click to collapse
We have a factory supported way to unlock and root. No real point in trying to exploit the system. If you are rooted, you should have a custom recovery anyway, which means you need to unlock the bootloader anyway in case you need to fix something.
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Gig11gs said:
Hey, I have rooted my shield and I didn't backup my stock recovery, anyone have a stock recovery img, I want to update to 1.4
Thanks
Click to expand...
Click to collapse
You can download the 1.4 firmware and flash it manually. There's a discussion on it a few pages back :good:
Will I be able to get OTA updates if I root ?
rahulkadukar said:
Will I be able to get OTA updates if I root ?
Click to expand...
Click to collapse
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Can I still root it this way if I already updated to 1.4 as I'm still fully stock and took the OTA
Im asking the same, im on the latest as of 2015 10 19, can i root using this method ?
baileyjr said:
You'll get the OTA notification but I was not able to install the OTA. You will need to download and new firmware and flash from fastboot.
Click to expand...
Click to collapse
You're guided imagery? I read without understanding very much
Can anyone confirm this rooting method works for new firmware 2.1?
garz said:
Can anyone confirm this rooting method works for new firmware 2.1?
Click to expand...
Click to collapse
I struggled to get root with this write up, and I am not a rookie. There were a few key steps missing, for example, you actually have to flash twrp, you can't just boot from twrp as suggested, if you are on 1.4 and up. Also, you have to let the unit reboot after you do the OEM unlock before flashing twrp. I didn't and mine just froze after flashing the recovery img. I found this write up http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
That one in the shield zone forum was so much more complete. And yes, it worked just fine with the 2.1 update. I did it yesterday with no problems. It will wipe out your data, and it will take a long time after you do the fastboot oem unlock, especially if you have the PRO version. But root is working with no problems.
RyanInBinary said:
First of all, let me say this isn't my post, and I didn't develop this method. The user, "Teletype" got this all figured out and did an amazing write-up for it. I'm posting it on their behalf so it can be in this newly added forum. The link to the recovery zip is also in his original thread, which I've linked below.
Here's the link to his original thread. If you feel the urge to press "thanks", please go to his original thread and press it for him, he deserves all the credit.
Click to expand...
Click to collapse
Do you want to build pre-root shiled TV firmware by nvidia open source？ and have experience？
Rooting.
KingRoot dose not work on this device.
Good guide thanks.
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
bearkilla said:
OK i have a 16gb model on 2.1, got adb hooked up but get this when trying to push supersu.zip to sdcard0:
C:\shield>adb push supersu.zip /sdcard1
failed to copy 'supersu.zip' to '/sdcard1': Read-only file system
Any ideas?
Click to expand...
Click to collapse
Try
Adb push supersu.zip /sdcard/
Inviato dal mio SHIELD Tablet utilizzando Tapatalk
Related
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
Hi all,
I have seen mentions in several places (including here http://9to5google.com/2014/12/18/how-to-update-android-wear-manually-ota-downloads/ and there http://forum.xda-developers.com/showpost.php?p=61430452&postcount=6 ) that it is possible to sideload an OTA to the SmartWatch 3 without using fastboot or rooting, just rebooting in recovery and running adb sideload.
However, in my case, although the watch properly appears in "adb devices" when it's powered on, when I go into recovery, it does not appear anymore... And thus I can't run "adb sideload" as adb, obviously, says "no devices found"
Any idea? Am I missing some trick? I have tried this both on Windows 8 and on Ubuntu, both behave in the exact same way.
I have also tried going into recovery using two different means: "adb reboot recovery" and using the menu that has fastboot/recovery options, nothing solves the issue.
Thanks!
PS: The reason why I am trying to sideload the OTA is to go 4.4 -> 5.0.1 and not 4.4 -> 5.1.1 because of all the 5.1.1 issues + I hate 5.1.1 UI
Did you click the adb sideload button in recovery? This enables adb.
If that does not work, try using fastboot to temporarily boot twrp from fastboot, but you will need to install fastboot drivers on your p.c. and find a 4.4 version of twrp.
The command is
Code:
fastboot boot twrp.img
From there you should be able to use adb.
Hi!
Do you mean selecting the "sideload" option in recovery? Yes I have selected this (by swiping down and then right to validate the choice) and my device still does not show up in adb. Have you been able to do this on the SmartWatch3? I feel like most people have experience with the LG G Watch...
In order to flash TWRP. I need to unlock the bootloader, don't I? If I can avoid voiding my warranty, that'd be great...
Thanks!
My first thought was the sideload option. I did not do it, but am on an SW3. I went right to option 2.
This does not unlock your boot loader, or void your warranty. What it does is hotboot another Rom (in this case recovery) without writing it to disk. I did do this, and it worked well.
This is the thread I followed. Skip the fast foot unlock step. That. An void your warranty.
http://forum.xda-developers.com/showthread.php?t=3107501
Oh! This is pretty awesome. Trying it, thanks a lot!
YESS! lekofraggle, I owe you a good one
So, for future readers, here is the procedure I went through. I have tried many different ways, this is the only which yielded results, so I'll only explain this one:
1) First, make sure that when your watch is connected to your phone, it displays the notification prompting you to upgrade your andoird wear version (I am not sure it will work if you don't have this notificaiton) (note that this notification only appears when the watch is connected to the phone in bluetooth, for me)
2) Follow http://forum.xda-developers.com/showthread.php?t=3107501 instructions to hot boot TWRP 5.0.2 (yes, even though you're in 4.4, does not matter (too much)). (command: fastboot boot twrp.img)
3) Root your watch by downloading the rooting zip from http://forum.xda-developers.com/attachment.php?attachmentid=3342605&d=1433157678 and "adb push yourzip /sdcard/root.zip"
4) In TWRP, your watch, go to "Install" and select "root.zip". You watch is now rooted.
5) Reboot your watch in normal android boot. Now push the OTA zip to it: "adb push yourota.zip /sdcard/update.zip"
6) Now is the trick: Replace the official OTA by yours: do "adb shell" and then "rm /cache/update.zip" and "cp /sdcard/update.zip /cache/update.zip".
7) Now check you still have the notification prompting for upgrade (your watch needs a bluetooth connection to phone, else it does not display it). Check the zip in /cache is still your by looking at the size, for instance: "ls -l /cache/update.zip" and compare with the size of your file.
8) If you're confident it is still your file, use the notifcation prompt on the watch and say you are ready to apply the upgrade.
9) Watch restarts and upgrade.... using your OTA file !
I tried using the custom "recovery command" that tutorials like http://www.carbontesla.com/2014/12/tutorial-update-smartwatch-3-lwx48p-android-5-0-1/ tell you to use but it would not work for me, only the notification would really trigger the upgrade...
Hope it helps!
PS: The reason for not using "adb sideload" directly from TWRP is that my OTA package (4.4 -> 5.0.1) would not be applied, it would complain that I am trying to apply it from a 5.0.2 system while it should be applied from a 4.4 system (oh, really?).
Great, I am glad it worked for you.
Two points for others travelling this path.
1)I am not sure you need to be rooted to do this, because twrp has its own permissions.
2) Did you try to use the install update.zip feature of twrp? That should have worked too.
Either way, I am glad you got there.
~Leko
Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol
bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs
Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.
can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!
Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..
Which guide did you use to do all of this? I will help us understand where you started
Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot
Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.
UNLOCKING BOOTLOADER:
a) Download Koush Universal adb driver from https://clockworkmod.com and adb setup.
b) Install the driver first and install adb after that.
c) Type n and press Enter when adb setup asks for installing drivers.
d) After the installation, run command prompt as administrator.
e) Open File explorer, and navigate to C:\adb
f) Please take backup of your data before proceeding further.
g) In C:\adb press Shift+right click and select Open Command Window here.
h) Enable USB debugging on your phone and connect your phone to pc using USB cable.
i) Type
Code:
adb devices
and press enter.
j) If it shows some device to be connected, only then proceed further.
k) Type
Code:
adb reboot bootloader
and press enter.
l) Phone will boot into fastboot mode.
m) Type
Code:
fastboot devices
and press enter.
n) If it shows some device to be connected, only then proceed further.
o) Type
Code:
fastboot oem unlock
and press enter.
p) On the phone screen, the phone will ask for confirmation to unlock bootloader.
Once fastboot shows "Success" or "Done" or something else signifying that the command was successful, type
Code:
fastboot reboot
and press enter.
q) Your phone will reboot normally.
Congrats, you have successfully unlocked bootloader.
ROOTING:
1. For Dr. Fone - Root:
a) Download and install Dr. Fone - Root on your PC.
b) Enable USB debugging on your phone.
c) Open Dr. Fone - Root and select Root option.
d) Connect your phone to your PC with USB cable.
e) Dr. Fone - Root will detect your phone in a few minutes.
f) Click "Root" button and wait.
Congrats, you have a rooted phone now.
2. For Magisk:
You'll find instructions to install Magisk over here.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3.Through TWRP:
a) Download SuperSU.zip or Magisk.zip
SuperSU link:
http://download.chainfire.eu/696/supersu/
THIS IS A LINK FOR AN OLDER VERSION OF SUPERSU SINCE supersu.com IS SHOWING DOWNLOAD ERRORS.
Magisk link:
Given in method 2 of rooting.
b) Download and flash TWRP from this thread, instructions have been provided in the thread for flashing it:
https://forum.xda-developers.com/ca...nofficial-twrp-3-2-3-micromax-canvas-t3833332
c) Boot into TWRP.
d) Select "Install" option.
e) In the File Manager that opens, select the zip you want to flash.
f) Follow the instructions on the screen.
g) Select "Reboot System"
Congrats, you have a rooted phone now.
Note: Kingoroot used to work before but it only provides temporary root now. Once you reboot, you lose root.
HIT THANKS IF FOUND USEFUL
mali_ said:
Any custom rom for this phone?
Click to expand...
Click to collapse
Not yet
mali_ said:
Is there an official stock firmware download link or just the thirdparty links?
Click to expand...
Click to collapse
androidmtk.com provides official firmware
mali_ said:
Magisk works on this?
What are the safe to remove apps?
Click to expand...
Click to collapse
Yes, Magisk works on this. I am using it right now.
You can uninstall any app you want without any side effects as long as the app is not an essential part of system.
For example, Firsttouch Launcher, Swiftkey Keyboard, Email, Amazon Kindle, App Center, App Bazaar, Chaatz, Hangouts etc.
You can use Debloater.
It is a magisk module you can use by terminal emulator to remove bloatware.
HIT THANKS IF FOUND USEFUL
if device doesn't show anything after writing fastboot devices command what is to be done...???
Masumilicioz said:
if device doesn't show anything after writing fastboot devices command what is to be done...???
Click to expand...
Click to collapse
Have you installed the drivers I mentioned or some other ones?
Btw, are you running adb and fastboot in Windows or Linux?
Thanks You for this post.
WHen I get to step "K" the device simply reboots fully back into normal OS
then further steps are not recognized if I do not keep putting "adb" in front
like it will not recognize fastboot devices
but it will recognize "adb fastboot devices"
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
Not sure if I got the adb drivers right because I did not see any "koushes adb" I mesn the site was clearly koushes but no where did I see a download names or called "koushes adb" Am I missing something?
protomind said:
WHen I get to step "K" the device simply reboots fully back into normal OS
then further steps are not recognized if I do not keep putting "adb" in front
like it will not recognize fastboot devices
but it will recognize "adb fastboot devices"
---------- Post added at 08:15 AM ---------- Previous post was at 08:13 AM ----------
Not sure if I got the adb drivers right because I did not see any "koushes adb" I mesn the site was clearly koushes but no where did I see a download names or called "koushes adb" Am I missing something?
Click to expand...
Click to collapse
You can get adb from SDK Tools from
https://developer.android.com/studio/ and Universal ADB Drivers from https://clockworkmod.com
I got TWRP recovery installed created by you. Big thanks !
I'm having issues in installing magisk via zip as well as patched boot image. Was the process smooth for you?
I got it to work by editing boot.img.
Are you working on any custom rom ?
Do you have any roms which can be ported to Q394 ?
Ashishoswal said:
I got TWRP recovery installed created by you. Big thanks !
I'm having issues in installing magisk via zip as well as patched boot image. Was the process smooth for you?
Click to expand...
Click to collapse
Yes, there were no problems at all.
Tell me the problem in detail so that I would be able to help.
Augustoandro said:
Yes, there were no problems at all.
Tell me the problem in detail so that I would be able to help.
Click to expand...
Click to collapse
Solved by changing some values in default boot image.
Are you working on any custom rom for this device ?
Ashishoswal said:
Solved by changing some values in default boot image.
Are you working on any custom rom for this device ?
Click to expand...
Click to collapse
I am working on creating a device tree first, but it will take some time.
Im not a developer but if there's any task which can be done by following a guide, and is helpful for you then let me know. I will be glad to help you.