[TUT] how to fix swr50 with working fastboot - Sony Smartwatch 3

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.

Related

[Q] Can't mount SD Card in TWRP

I recently rooted my kindle fire and installed twrp along with cm7, but I accidently did a factory reset inside cm7 and was stuck on the firefirefire logo, I used an unbrick tool, but that erased all my user data and did not help. I managed to get my boot back to 4000 and install twrp again, but it won't let me mount sd card and will only allow me to mount system.
Sorry Im a noob
Im having the same issue, trying to moun it, but I keep getting
Error mounting /sdcard!
Is there a way to fix it? Im stuck on recovery (CW)
Heres a great idea get off of the discontinued recovery and switch to touch screen clockworkmod recovery its way better when it comes to things like that
Link: http://forum.xda-developers.com/showthread.php?t=1454241
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Thanks b63 for the fast reply. I dont have twrp I have CWM recovery, im trying to install TWRP but I get an error:
error: device not found
Is there another way to install TWRP?
Thanks
i don't know about cwm but i would try to boot to it and test if adb is working
then it should be the same - you only need adb root access
if you have this access with cwm also then there is no need to install twrp
Well if I boot into CWM
I can do adb shell
But then nothing happens
If I let Kindle boot normally (after the Yellow triangle) the screen goes black and I cant adb shell anymore
What im doing wrong or what im missing.
Thanks again
BTW
When I boot int CWM I get this message
E:Can't Mount /cache/recovery/command
stay in your recovery
after the command the sdcard should mount to your computer
check your device manger
follow the first desciption
if you can't get it gimme a pm ...
Wooooot!
Thank you so much b63!!!!I couldnt sleep for this damn problem
In the end this one help me out
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
I dont know why it worked with >> its the same (for this case) but I could finally mount it on windows
Now im back to CM7, really thanks!!!!!
really glad that it worked ...
b63 needs a medal lol.
Sent from my HTC Glacier using xda premium
Thanks b63 I got twrp to mount the sd card, with this:
echo /dev/block/mmcblk0p12 >> /sys/devices/platform/usb_mass_storage/lun0/file
But, when trying to install cm7 I get an error:
E:Cannot load volume /misc!
ignore it - the kf don't have a volume "misc"
Stuck in twrp!!!!
b63 said:
guys this has nothing to do with twrp - it's working fine
just do following:
- boot to twrp
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
- choose quick format and let it format it as fat32 block size 4096
Click to expand...
Click to collapse
I can get into TWRP, but when I type in ADB DEVICES in command prompt, it says the standard daemon not running, then daemon started successfully. This is followed by List of Devices attached, but it's blank after that.
I used the Kindle Fire Utility to install drivers, and when I use ADB DEVICES Command Prompt with my T-Mo Vibrant, I can get into ADB Shell.
Any advice?
Please note, this isn't mine. I've never owned a Kindle Fire, so I'm banging myself raw with information overload on this type of device. I'm trying to help a co-worker out with his Fire that he borked. I've owned three android phones/tablets and rooted/ROMed all of them, so I follow instructions. So far, I've tried the Kindle Fire Utility and the Kindle Fire Unbrick Utility found in these forums. My co-worker didn't get to the point of making a back-up or installing the Stock Image as an Update.zip. I have the stock image downloaded, and have renamed it, but I can't get it onto the tablet at all. Selecting Mount in TWRP always locks everything up, and there is nothing to Install or Restore. So, like I said, I'm getting bloody here, but no joy.
Any help would be appreciated!
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
b63 said:
what's the status of the kf ? -> you can get into twrp - that is good - do that
what's the status of the drivers in device manager ? -> which driver loaded ?
what have you/he done/tried to get to this point?
i'm asking to give you the right method ...
Click to expand...
Click to collapse
He says he rooted it, installed FireFireFire, and the ICS-ish launcher (name eludes me at this point). Then, it basically boot-looped (Yellow Triangle, then Kindle Fire, back to Yellow Triangle).
My first thought was ADB Shell, but the KF is apparently a stranger animal than most of the other Androids I've dealt with, so it didn't automatically pop up. I installed KFU (Kindle Fire Utility, most recent version), installed the windows drivers (I have Win7 Pro 64-bit) that came with the KFU, and attempted to get it to boot normally, recovery, or anything. Note - A couple of times (like 4 or 5 out of 100), it did make it to a full boot for a few seconds, but would crash within seconds. TWRP was not installed at that point, so I successfully pushed that with the KFU. I also downloaded the stock image, and renamed it. TWRP won't mount the SD card so that my computer can see it, so I'm losing that battle. Also, at some point along the way, the KF started attempting to connect to the PC when plugged in, with the typical USB device connected sound, but two seconds later, it acts like it is unplugged, with that sound. If the KF is visible in the Device Manager, it must be hidden, cuz I can't see it. This was not the case at first, with an Unmount icon for the Kindle being displayed in the notification (right) side of the Windows toolbar. This is in conjunction with the device now booting straight to TWRP, and not even attempting to go the normal boot route. I've also tried a Kindle Fire Unbrick Utility to restore it, with no luck. It wipes the User Data, wipes cache, downloads the update.zip, but can't mount the unit to push the data. I've never been able to get ADB to find the unit.
If I can get the update.zip to the SD root, or if I can ADB shell it, I think I've won. But I'm being blocked on both those counts.
Thanks for being willing to look into this for me!
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
b63 said:
the problem is the ics launcher - it simply don't work
would recommend to use go launcher instead, for the future
now to the problem:
one solution is to boot to twrp - there is adb root access available
maybe check and update drivers - look here:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
then delete the ics launcher .apk (don't know the exact name) with adb commands
this should make the kf startable again and nothing is lost
an other solution is to flash a new rom but i don't think that this is necessary
and never ever flash the original rom from amazon unless you want to return the device - there is a risk of bricking it and you will loose fff,twrp and root
there are prerooted stock images available for returning to stock rom:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
if you need closer help gimme a pm ...
Click to expand...
Click to collapse
You're giving me a lot of hope. I'll give this a try when I get home tonight, and I'll contact you with any other hurdles. THANK YOU SO MUCH!
halfway there
Ok so I have run the command under the adb shell after adb did detect the device, however when I run the command it says that "non existent directory" What am I missing?
echo /dev/block/mmcblk1p1 > /sys/devices/platform/usb_mass_storage/lun0/file
/sbin/sh: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexis
tent directory
Getting that when i try to issue the command,
Any hint?

[SOLVED] Sideload from recovery: Watch does not appear in adb devices

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

Yet another OTA softbrick thread. How screwed am I?

Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.
adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery
Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!

[TUTORIAL] Complete Guide on How to Flash English Rom to China Local Huawei Watch

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!

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...
oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .
Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?
TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work
in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?

Categories

Resources