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 everyone,
just to clarify that It's my first time I try to unlock and root my phone, so no much knowledge.
I basically followed the steps to unlock the bootloader.
Everything worked perfectly, I reached the recovery, went on 'apply update from ADB'.
But then, when I enter in cmd: 'adb sideload <whatever the filename>'
it prints out the Android Debug Bridge instructions rather than transferring the zip file to my phone, and the phone keeps on asking "now send the package you want to apply to the device with adb sideload filename "
N.B.: the phone is recognized by adb, even when I enter adb devices, it is recognized
Any help?
did you try issuing the adb sideload command BEFORE pressing the button in recovery?
I had this issue before when trying sideload, in fact I think it WOULDN'T work if I started it via recovery FIRST. it has been a long time since I did this though, but I swear I remember not even having to press the button in recovery, I think it just automatically started once I issued the command from computer.
Yea, just tried it and same results
which recovery version are you using?(CWM or TWRP? and which version also)
and which adb version do you have on your computer? are you certain it is the latest available? did you install it through the Android SDK?
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
hi people,i wanna share a fix solution for any smartwatch 3 with working fastboot mode...
so,presuming u already have adb drivers installed lets proceed
https://drive.google.com/open?id=0B14BmzmcIZ4cVDBjRnliUDVXU1k is link to a shared folder with all needed files,inside folder are :
repacked rom 5.0.1 - swr50.zip
stock recovery image - swr50.img
twrp recovery image for old rom version - twrp.img
twrp recovery image for new rom version - twrpnew.img
update packages that can also be sideloaded if watch dosent update itself after first flash
updatep-k.zip -its from verison lwx48p tp lwx48k
then k to d and d to lca43(5.1.1)
so,boot into fastboot and fastboot boot twrp.img (that will boot twrp image on watch).then,adb push swr50.zip /sdcard/swr50.zip
in twrp push install and select the newly copied swr50.zip flashable rom...flash it,then adb reboot
let watch reboot,presuming all went fine,ull watch will boot in 5.0.1 rom,let it connect to phone.inside settings,open options/about,and push built version until u get dev mode...in dev mode enable usb debug,confirm also on phone
so right now u have watch connected to pc with usb debug on....write adb reboot bootloader ,so watch goes in fastboot again
now,flash stock recovery...fastboot flash recovery swr50.img (watch will get the stock recovery),after u can fastboot continue
right now u can update watch,connected to phone,via own update ota service,settings/about/system update,it will download and install next version,the update again and again.if u dont wanna wait thatu can adb sideload files i provided,its actualy stock ota update
so....
adb reboot recovery,select adb sideload,and adb sideload updatep-k.zip,reboot watch and let update,then sideload again updatek-d.zip,reboot and let it update,then again last update
AFTER THIS UPDATE TWRP.IMG NO LONGER WORK,DONT BOOT IT,WATCH WILL ENTER BOOT LOOP,WE WILL BOOT TWRPNEW.IMG.....becouse 5.1.1 updated also boot image,so fastboot twrpnew.img if u wanna use twrp in some way.....
i hope its was helpfull,any questions fell free to leave,im no developer,i just like to play with things
BIG thanx to those who packed,repacked flashes and recovery images!!!!
l
alex_SW said:
hi people,i wanna share a fix solution for any smartwatch 3 with working fastboot mode...
so,presuming u already have adb drivers installed lets proceed
https://drive.google.com/open?id=0B14BmzmcIZ4cVDBjRnliUDVXU1k is link to a shared folder with all needed files,inside folder are :
repacked rom 5.0.1 - swr50.zip
stock recovery image - swr50.img
twrp recovery image for old rom version - twrp.img
twrp recovery image for new rom version - twrpnew.img
update packages that can also be sideloaded if watch dosent update itself after first flash
updatep-k.zip -its from verison lwx48p tp lwx48k
then k to d and d to lca43(5.1.1)
so,boot into fastboot and fastboot boot twrp.img (that will boot twrp image on watch).then,adb push swr50.zip /sdcard/swr50.zip
in twrp push install and select the newly copied swr50.zip flashable rom...flash it,then adb reboot
let watch reboot,presuming all went fine,ull watch will boot in 5.0.1 rom,let it connect to phone.inside settings,open options/about,and push built version until u get dev mode...in dev mode enable usb debug,confirm also on phone
so right now u have watch connected to pc with usb debug on....write adb reboot bootloader ,so watch goes in fastboot again
now,flash stock recovery...fastboot flash recovery swr50.img (watch will get the stock recovery),after u can fastboot continue
right now u can update watch,connected to phone,via own update ota service,settings/about/system update,it will download and install next version,the update again and again.if u dont wanna wait thatu can adb sideload files i provided,its actualy stock ota update
so....
adb reboot recovery,select adb sideload,and adb sideload updatep-k.zip,reboot watch and let update,then sideload again updatek-d.zip,reboot and let it update,then again last update
AFTER THIS UPDATE TWRP.IMG NO LONGER WORK,DONT BOOT IT,WATCH WILL ENTER BOOT LOOP,WE WILL BOOT TWRPNEW.IMG.....becouse 5.1.1 updated also boot image,so fastboot twrpnew.img if u wanna use twrp in some way.....
i hope its was helpfull,any questions fell free to leave,im no developer,i just like to play with things
BIG thanx to those who packed,repacked flashes and recovery images!!!!
l
Click to expand...
Click to collapse
Thanks for putting this together. My sw3 has been stuck on the MM dots / symbols for some time. After several attempts of running various roms, img, simg, XC, etc, I could get no further than the original software issue. With your post, I was able to get it to the LCA43 update. Although, for some reason I could not use the twrp.img in your file list (I found another one) and I could not adb the recovery file (I had to flash it), nevertheless, it provided a way for me to update the sw3. I did not flash the updates, but just let the watch do it. While that was a slow process, it was working so I continued...until.
I could not get the MM update to work though. It downloaded and installed on the sw3. But when booting up, I got the dreaded 4 dots / symbols again. If you are still around and have any ideas of updating this procedure to include the MM updates, it would be much appreciated. Again, the XC does not work for me even though both the repair and update options in the software said they were successfully installed.
Hi!
I really need to do this for activate the NFC and use to check glicemia on the watch.
But i'm stuck almost at the first point.
I already activate the adb on the watch and put him "runnig fastboot".
On the pc I write on command prompt "adb reboot bootloader" and returns: "error: device '(null)' not found"
Anyone can helps?
Regards,
Same position as Moitas
Realy would appreciate if somebody could help me and at the same time moitas. I run windows10 and have the same problem. The device is called Tetra when it shows up in fastboot and I can´t get any driver to work with it. Have tried several differet ones but none seem to fit. Any clever one with a solution I would salute you
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
ajolly said:
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
Click to expand...
Click to collapse
Thanks Ajolly! I finally managed to get it done. As new to this rooting buisness there were a lot of steps that where more complicated than the manual I followed applied
Hi! i have problem after downgrade...
After I push SWR50.zip and reboot, my devices is unauthorized. When i enter in fastboot manually there's any devices (null). I install drivers like You said, and form adb, google. If somebody can help me this i will be very grateful
any one can help me. After failed up SW3 by sideload, they ignored PC conncetion. Try "adb devices", fastboot mode, recovery mode, MTP, - anything happend in device manager.
ajolly said:
@moitas @tobas70 you need to install the correct drivers - http://forum.xda-developers.com/attachment.php?attachmentid=2480396
Click to expand...
Click to collapse
I just got a new SWR50 for the sole purpose of using NFC (with FreeStyle Libre).
On the Win10 PC I don't have "Android Device" as a hardware type. -- I'm not sure if this is causing the problem that in Fastboot (white background) I cannot communicate with the watch from the PC anymore.
Also, when turned on for the first time watch automatically upgrades to M1D64T and I don't seem to be able to stop that and don't seem to be able to downgrade to be able to use this package.
Any suggestions? Thanks
Restore to the latest firmware
After downgrading to LCA43, what would be the easiest way to restore the watch to the latest firmware, is there a real factory reset?
Not pair after downgrade
I have downgraded from version M1D64T to LWX48P and now my phone do not see the watch in bluetooth devices. I tried few things to start BT working like:
- remove Android Wear from phone
- clear Google Play Services
- send few intent through adb like bluetooth.REQUEST_DISCOVERABLE
- return to M1D64T by Sony PC Companion
Bluetooth still not works and I cannot connect to any phone.
Maybe somebody have an idea how to repair my watch?
Ok, I've got another issue when downgrading the watch.
When I get to the Install the swr50.zip it starts to complain.
It says, Unable to mount /cache, Unable to mount data and so on. So clearly something is not going right at this point (or earlier more likely).
What's going wrong and how do I fix it?
Same thing here - /data can't be mounted read/write
I'm seeing the same thing. I can use "adb shell" and "mount -r /data" (readonly) which works, but when I try to mount it normally ("mount /data") I get an error about a bad argument. This is certainly related to the errors re. not being able to mount /data, which I see when I try using twrpnew.img to install the SWR50.zip image.
I'm stuck!
Maybe a solution...
(I'm still going through applying updates, but this looks hopeful!)
I found that apparently the "unable to mount data" seems to have to do with the /data partition (in my case, "/dev/block/mmcblk0p32") having some internal flag which seemed to not allow it to be mounted read/write. I could do "adb shell" to get to the watch and then to "mount -r /data" and that worked just fine. I decided to rebuild the entire /data partition. Use "adb shell" to get a shell prompt on the watch, do "mount" to make sure /data is NOT mounted. If it is, do "umount /data", which should unmount it. you can see what's being mounted where via "cat /etc/fstab". You want to rebuild the disk partition which will be mounted on /data. On my watch this was "/dev/block/mmcblk0p32", so "/sbin/make_ext4fs /dev/block/mmcblk0p32". Then "exit" to get back to your system where you're running adb.
So, I followed the "How to install NFC on Sony Smartwatch3" instructions (I'm not allowed to post a link or else I would, but you probably have these instructions already.)
(I'm doing the "downgrade" part of the instructions, which is where the "install" failed.)
Just after "fastboot boot twrpnew.img", I inserted the above work to rebuild the /data partition. DO NOT mount /data after having rebuilt it! You should also should see that /cache is NOT mounted at this time. Do "exit" to get back to your adb system and continue following instructions at "adb push SWR50.zip /sdcard/", and the "install" worked for me after this!
frippegubben said:
Ok, I've got another issue when downgrading the watch.
When I get to the Install the swr50.zip it starts to complain.
It says, Unable to mount /cache, Unable to mount data and so on. So clearly something is not going right at this point (or earlier more likely).
What's going wrong and how do I fix it?
Click to expand...
Click to collapse
Sony Smartwatch SWR50 unable to install SWR50.zip
Hello Friends,
Iam trying to configure NFC on my Sony Smart Watch 3. After command adb push SWR50.zip /sdcard/, I try to intall SWR50.zip, It's not flashing.
It says Failed with message " UNABLE TO MOUNT" etc
Can you kindly help please
KIR71 said:
Hello Friends,
Iam trying to configure NFC on my Sony Smart Watch 3. After command adb push SWR50.zip /sdcard/, I try to intall SWR50.zip, It's not flashing.
It says Failed with message " UNABLE TO MOUNT" etc
Can you kindly help please
Click to expand...
Click to collapse
I was working with a Sony Smartwatch 3 a few years ago (using the NFC to read a Blood Glucose sensor) and encountered this same error during installation of some of the code. Here are my notes on the solution, in case it helps:
I found that apparently the "unable to mount data" seems to have to do with the /data partition (in my case, "/dev/block/mmcblk0p32") having some internal flag which seemed to not allow it to be mounted read/write. I could do "adb shell" to get to the watch and then to "mount -r /data" and that worked just fine. I decided to rebuild the entire /data partition. Use "adb shell" to get a shell prompt on the watch, do "mount" to make sure /data is NOT mounted. If it is, do "umount /data", which should unmount it. you can see what's being mounted where via "cat /etc/fstab". You want to rebuild the disk partition which will be mounted on /data. On my watch this was "/dev/block/mmcblk0p32", so "/sbin/make_ext4fs /dev/block/mmcblk0p32". Then "exit" to get back to your system where you're running adb.
Hope this helps! Good luck!
Thank you for this tutorial, I'm having the same problem. My swr50 stuck on the dots screen after battery replacement. I tried to follow the steps above but my system does not see the device at all.
I tried to add legacy device drivers but it come back with code 10.
After connecting swr50 device manager don't detect any device and I can't install drivers. So when I run ADB I get message "device null" Did someone had the same problem? Is there any solution?
Help please, When I plug in my watch to the charger sometimes it gets stuck on sony logo and sometimes doesn't display anything also tried connecting to pc but it keeps on booting also tried pressing the power key to get into the fastboot mode but doesn't work.
You could have been frustrated with all the features that’s supposed to be in your New Huawei Watch is nowhere to be found. Like Wi-Fi, Bluetooth and Language Selection are all hidden in the China Stable Rom of the Huawei Watch.
I have talked to the CSR of Huawei in China, they honestly told me that the Wi-Fi certificate for the watch is not yet certified that’s why they cannot unleash it yet but it is embedded inside the watch should future updates allows the Wi-Fi to be used. Regarding the language selection, local China release is locked to Simplified Chinese, whether you like it or not.
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Step 1: Put the Watch to Fastboot Mode
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Another alternative for Step 1:
1.) Install ADB SETUP V1.3
https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit
2.) Enable ADB and connect to computer
How to Enable ADB:
- Go to About
- Click 5 times on Build Number to access Developer Mode
- Go to Developer Options
- Enable ADB Debugging
3.) Go into command prompt mode
4.) Reboot watch into Fastboot mode using this code:
adb reboot-bootloader
Step 2: Unlock the Bootloader
1.) On command prompt mode, type this command: Fastboot Oem Unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 3: Flashing
Download first the three files before proceeding:
Boot Img: https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
Recovery Img: https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
System Img: https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g
After downloading the three files, lets proceed:
1.) While on Fastboot mode, type this on the command prompt one at a time:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
2.) and then go to recovery and do a wipe data / factory reset.
Congrats! Your done!
Further Reading if you are stuck on flashing System.img
There are some reason beyond my explanation why the system.img cannot be flashed to the watch, here is the workaround:
1.) First of all download the TWRP and fastboot boot it:
TWRP download: http://forum.xda-developers.com/attachment.php?attachmentid=3505656&d=1444766757
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2.) Now your watch is in TWRP and you can no longer use ADB commands, go to your watch and select Advanced, then select ADB Side Load
3.) Going back to command prompt, push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
4.) Now flash it:
Code:
adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
This is the most complete guide I can come up with based on my own explorations. Hope this helps.
Where can i find the drivers for this watch.
When i plug this watch into my computer Windows doesn't detect the drivers. I've tried looking on the HuaWei website but there are no downloadable drivers. Any help?
coolcaty said:
Where can i find the drivers for this watch.
When i plug this watch into my computer Windows doesn't detect the drivers. I've tried looking on the HuaWei website but there are no downloadable drivers. Any help?
Click to expand...
Click to collapse
Look here : https://m.reddit.com/r/hwatch/comments/3n9ckp/how_to_get_adb_access_over_usb/
"Fastboot Oem Unlock" should be "fastboot oem unlock" otherwise it won't work. Also make sure to have ADB 1.0.32 at least for watches!
hello!
i do all step and complete flash with twrp mode . but when reboot and will go to reboot recovery the watch restart and restart!
sry for weak english!
j.spectator said:
hello!
i do all step and complete flash with twrp mode . but when reboot and will go to reboot recovery the watch restart and restart!
sry for weak english!
Click to expand...
Click to collapse
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
Hi, first of all thanks for this awesome guide.
This is the first thing I am looking for after bought a Chinese watch from China.
Manage to go through ONLY I tried key in "fastboot oem unlock' all in small letters.
Then follow the guide instruction to goto recovery to wipe data after successfully go through the other flashing steps smoothly.
This is where I got stuck in infinite looping in Android lying and screen flashing every few seconds. I got panicked after trying multiple times failed to recover from this symptoms for a while.
Until finally manage to pull back to fastboot menu by keep press holding onto the power button. The steps of holding till first vibration then do a quick short press doesnt work.
I am glad that now I am back to normal with the English screen.
Next I will proceed to flash the TWRP and 1.4 update.
Hopefully everything goes smoothly.
Thank you for the guide once again and wish everyone success in updating and Enjoy!
Update: (9:29am)
Did a system update. Before was something like LBC49A, after system update it becomes LBC43B. I suppose this is 1.4 update as the name is the same.
Hence decided not to flash the TWRP recovery for the time being if it can continue auto system update.
Update (9/3/2016):
Sorry, nvr read through all the posts. Was thinking that (LBC43B) was the latest update.
So proceed to flash TWRP recovery then try to update to MEC23L (latest update) but failed to run "adb sideload update.zip"
Every time once enter into Recovery mode, the connection dropped. Then tried to do OTA update by factory reset as suggested but failed (confirmed my location can OTA as one use from same location didi it.)
This morning went back to PC flash back the original Stock Recovery from here.
Restart the watch and goto System Update, receive message "Charge the watch to update to MEC23L"
My thot - OTA only allow with Stock Recovery?
Update done but still cannot sms. ??
Btw, for LBC43B, many functions cannot work properly like sms, call and no sound at all. Thx n Enjoy.
P.S. Using Minimal ADB and Fastboot, PDAnet driver(for watch USB driver), running on Win7, connect via watch USB charge docking station.
help me please
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
richboy324 said:
You could have been frustrated with all the features that’s supposed to be in your New Huawei Watch is nowhere to be found. Like Wi-Fi, Bluetooth and Language Selection are all hidden in the China Stable Rom of the Huawei Watch.
I have talked to the CSR of Huawei in China, they honestly told me that the Wi-Fi certificate for the watch is not yet certified that’s why they cannot unleash it yet but it is embedded inside the watch should future updates allows the Wi-Fi to be used. Regarding the language selection, local China release is locked to Simplified Chinese, whether you like it or not.
If you happen to buy from China or received a gift with a China local release Huawei Watch, here is the guide on how to flash with an English Rom which I have already tested mine on.
Here is the complete guide:
Step 1: Put the Watch to Fastboot Mode
1) Hold down the power button
2) The screen will go black for about 2 seconds and then boot into the Huawei logo. Keep holding down the power button.
3) Wait for the first vibration, release the power button and then immediately give the power button one short press.
Note: If you feel the second vibration, you waited too long to do the release and press. Start over again with Step 1.
Another alternative for Step 1:
1.) Install ADB SETUP V1.3
https://drive.google.com/file/d/0B_1zjuazXSqbQ0p6NWtvRk9OMzA/edit
2.) Enable ADB and connect to computer
How to Enable ADB:
- Go to About
- Click 5 times on Build Number to access Developer Mode
- Go to Developer Options
- Enable ADB Debugging
3.) Go into command prompt mode
4.) Reboot watch into Fastboot mode using this code:
adb reboot-bootloader
Step 2: Unlock the Bootloader
1.) On command prompt mode, type this command: Fastboot Oem Unlock
2.) accept the prompt on the watch.
Note: If successful, command prompt will say your bootloader is already unlocked.
Step 3: Flashing
Download first the three files before proceeding:
Boot Img: https://mega.nz/#!rgRQHRrb!lgQCvqH-qkuqitPRRXfCad29MdmJ6ynaUHJDr0hjeLM
Recovery Img: https://mega.nz/#!ahgjxA4R!y8Hb0CBVBRwUr0tA3HeFrrqh0ALAiMyqJu0pLsBsAD8
System Img: https://mega.nz/#!2pYVBDpA!wQJT8LDcffk7uxEmrsqna6MKWIODD-FqBO_k4Poml7g
After downloading the three files, lets proceed:
1.) While on Fastboot mode, type this on the command prompt one at a time:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
2.) and then go to recovery and do a wipe data / factory reset.
Congrats! Your done!
Further Reading if you are stuck on flashing System.img
There are some reason beyond my explanation why the system.img cannot be flashed to the watch, here is the workaround:
1.) First of all download the TWRP and fastboot boot it:
TWRP download: http://forum.xda-developers.com/attachment.php?attachmentid=3505656&d=1444766757
Code:
fastboot boot TWRP2.8.7.0-Sturgeon.img
2.) Now your watch is in TWRP and you can no longer use ADB commands, go to your watch and select Advanced, then select ADB Side Load
3.) Going back to command prompt, push the system.img in the sdcard so:
Code:
adb push system.img /sdcard/
4.) Now flash it:
Code:
adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
5.) Reboot.
Now you may encounter bootloop after flashing which I did, go back to Step 1 Fastboot mode and select Reboot Recovery, then wipe data and then clear cache, then you are good to go!
This is the most complete guide I can come up with based on my own explorations. Hope this helps.
Click to expand...
Click to collapse
Hi, I have a problem, when I do this :
"select Advanced, then select ADB Side Load" after 4 or 5 minutes processing it saids "failed"
and then I can do this step "adb push system.img /sdcard/"
but not this "adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system"
Any idea please, thank you.
jbctiong said:
Hi, first of all thanks for this awesome guide.
This is the first thing I am looking for after bought a Chinese watch from China.
Manage to go through ONLY I tried key in "fastboot oem unlock' all in small letters.
Then follow the guide instruction to goto recovery to wipe data after successfully go through the other flashing steps smoothly.
This is where I got stuck in infinite looping in Android lying and screen flashing every few seconds. I got panicked after trying multiple times failed to recover from this symptoms for a while.
Until finally manage to pull back to fastboot menu by keep press holding onto the power button. The steps of holding till first vibration then do a quick short press doesnt work.
I am glad that now I am back to normal with the English screen.
Next I will proceed to flash the TWRP and 1.4 update.
Hopefully everything goes smoothly.
Thank you for the guide once again and wish everyone success in updating and Enjoy!
Update: (9:29am)
Did a system update. Before was something like LBC49A, after system update it becomes LBC43B. I suppose this is 1.4 update as the name is the same.
Hence decided not to flash the TWRP recovery for the time being if it can continue auto system update.
Update (9/3/2016):
Sorry, nvr read through all the posts. Was thinking that (LBC43B) was the latest update.
So proceed to flash TWRP recovery then try to update to MEC23L (latest update) but failed to run "adb sideload update.zip"
Every time once enter into Recovery mode, the connection dropped. Then tried to do OTA update by factory reset as suggested but failed (confirmed my location can OTA as one use from same location didi it.)
This morning went back to PC flash back the original Stock Recovery from here.
Restart the watch and goto System Update, receive message "Charge the watch to update to MEC23L"
My thot - OTA only allow with Stock Recovery?
Update done but still cannot sms. ??
Btw, for LBC43B, many functions cannot work properly like sms, call and no sound at all. Thx n Enjoy.
P.S. Using Minimal ADB and Fastboot, PDAnet driver(for watch USB driver), running on Win7, connect via watch USB charge docking station.
Click to expand...
Click to collapse
Hi there
All i know is you can flash the stock rom then update via OTA
mine is running marshmallow already now MEC23L
This is the safer way coz i never tried to flash in the MEC23L
Cheers!
alesramosfj said:
Hi, I have a problem, when I do this :
"select Advanced, then select ADB Side Load" after 4 or 5 minutes processing it saids "failed"
and then I can do this step "adb push system.img /sdcard/"
but not this "adb shell dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system"
Any idea please, thank you.
Click to expand...
Click to collapse
I did not encounter this error
did you try the first method before doing the TWRP?
A Problem
Hi. I have a problem. I complete step3. I code command: fastboot oem reboot-recovery . Its Failed. I seclected recovery on watch. But when selecting this plan is faulty. Only flashing screen icon Android. I tried again, but still the same. Can you help me?
h**ps://drive.google.com/file/d/0B0F7_Vdg_eg3Nms3M2oyVmZ1RjA/view?usp=sharing
begioxx said:
Hi. I have a problem. I complete step3. I code command: fastboot oem reboot-recovery . Its Failed. I seclected recovery on watch. But when selecting this plan is faulty. Only flashing screen icon Android. I tried again, but still the same. Can you help me?
Click to expand...
Click to collapse
hi there
i think you need to do a further reading on the one after step three
there are chances that you will get stuck in flashing the system image file
there is a workaround.
try it again
hope it helps.
richboy324 said:
I did not encounter this error
did you try the first method before doing the TWRP?
Click to expand...
Click to collapse
Hello,
I'm also encountering this error. I did try the first method, and I'm getting stuck on activating ADB Side Load. Any tips?
Hi, there's a problem and i can't mount partition /data and /cache
plz help
Thanks a lot man you are a gem
I in hurry formatted system from twrp and was without OS. very detailed tutorial for beginners with adb. I am back with watch booting fine now
Just a note. I tried doing this while in China without vpn access for my phone. This made it so I couldn't sync up or pair because it kept trying to access google which was blocked. Once I got back to Canada I was able to do everything and update to newest OTA. If you leave it on chinese rom you can use in china and pair with the Android Wear China version app.
alesramosfj said:
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
Click to expand...
Click to collapse
Hey, did he ever get back to you? I've got the same thing going on right now.
alesramosfj said:
No OS installed! Are you sure you wish to reboot?
This is my problem, I can´t install it-
I send you a private message Richboy234, can you help me please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/hua...ock-huawei-watch-t3219596/page11#post66771952
Not sure if he got back to you. I had the same problem, and it involved the system.img that I downloaded from the link above. It wasn't complete for some reason. On this thread attached, it has a zip that has it all. My watch works fine now. I want to thank the OP here for showing me the steps to take. You all ROCK!