XT907 Reset Help - Droid RAZR M Q&A, Help & Troubleshooting

XT907 Reset Help - Droid RAZR M Q&A, Help & Troubleshooting

Hello, I have an old Razr M (XT907) that crashed on me during an international trip back in 2017. I think Verizon pushed an OTA updated and since it was only on WiFi at the time, something got corrupted. I bought a new phone when I got back to the US and this old RAZR has been lying in a desk drawer. I’d like to try to get it working again as an emergency or travel WiFi only phone.
The phone will boot and go through the Screen Lock PIN, but once you get in to the Homepage, it is a never-ending loop of “Unfortunately, the process xxxx has stopped” It runs though all the Android processes and installed apps, then starts over at the top. Sometimes with enough persistence you can get to the settings menu, but it doesn’t seem like you can make any changes that have any lasting effect. My thought was to reinstall a clean version of the ROM, no problem losing the apps or any local data, anything important was on the SD card and moved to my new phone.
USB Debugging was enabled when the phone crashed, so ADB and Fastboot are available. The computer will recognize it and can give it commands through the Windows 10 CMD prompt. The Bootloader is locked and I haven’t found any way to get the unlock code for it. The phone is not rooted, has a stock bootloader and recovery, and is running an OEM Verizon ROM.
What I’ve tried with no changes:
Factory Reset through the Settings Menu, no change
Factory Reset through the Recovery, shows that it completed, but no change
Erasing User and Cache information using ADB and Fastboot, no change
Downloading a original ROM VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml
Uploading the ROM using RSD Lite (v6.2.4), It will unpack the ROM, but doesn’t recognize the phone. I’ve tried detecting the phone in ADB mode, Fastboot, and Recovery.
Flashing the ROM in Recovery mode with ADB from the computer
Flashing the ROM in Recovery mode from an SD card
Re-installing the ROM using MFastboot upgrade xxx.xlm (it runs but says android-info.txt is not available)
Re-installing the ROM using MFastboot line by line (as described here http://mrbluecoat.blogspot.com/2014/07/tutorial-restore-verizon-droid-razr-m.html) All processes claim to be successful, but when it reboots at the end after “Fastboot Continue” it boots up and there is no change
Rooting the phone with King Root v3.5, this was unsuccessful
Any suggestions for things that I’m missing or something that I’m doing out of sequence? Is there a different way to approach this problem? Thank you!!

crazyjcs said:
Hello, I have an old Razr M (XT907) that crashed on me during an international trip back in 2017. I think Verizon pushed an OTA updated and since it was only on WiFi at the time, something got corrupted. I bought a new phone when I got back to the US and this old RAZR has been lying in a desk drawer. I’d like to try to get it working again as an emergency or travel WiFi only phone.
The phone will boot and go through the Screen Lock PIN, but once you get in to the Homepage, it is a never-ending loop of “Unfortunately, the process xxxx has stopped” It runs though all the Android processes and installed apps, then starts over at the top. Sometimes with enough persistence you can get to the settings menu, but it doesn’t seem like you can make any changes that have any lasting effect. My thought was to reinstall a clean version of the ROM, no problem losing the apps or any local data, anything important was on the SD card and moved to my new phone.
USB Debugging was enabled when the phone crashed, so ADB and Fastboot are available. The computer will recognize it and can give it commands through the Windows 10 CMD prompt. The Bootloader is locked and I haven’t found any way to get the unlock code for it. The phone is not rooted, has a stock bootloader and recovery, and is running an OEM Verizon ROM.
What I’ve tried with no changes:
Factory Reset through the Settings Menu, no change
Factory Reset through the Recovery, shows that it completed, but no change
Erasing User and Cache information using ADB and Fastboot, no change
Downloading a original ROM VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml
Uploading the ROM using RSD Lite (v6.2.4), It will unpack the ROM, but doesn’t recognize the phone.
Click to expand...
Click to collapse
RSD Lite only works With older Windows 7 or XP machines, not 8 or 10.
http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
crazyjcs said:
I’ve tried detecting the phone in ADB mode, Fastboot, and Recovery.
Flashing the ROM in Recovery mode with ADB from the computer
Flashing the ROM in Recovery mode from an SD card
Click to expand...
Click to collapse
Moto doesn't allow to reinstall updates
crazyjcs said:
Re-installing the ROM using MFastboot upgrade xxx.xlm (it runs but says android-info.txt is not available)
Re-installing the ROM using MFastboot line by line (as described here http://mrbluecoat.blogspot.com/2014/07/tutorial-restore-verizon-droid-razr-m.html) All processes claim to be successful, but when it reboots at the end after “Fastboot Continue” it boots up and there is no change
Click to expand...
Click to collapse
Those instructions don't seem correct.
These are all I used to use.
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash system system.img
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
fastboot erase cache
fastboot erase userdata
crazyjcs said:
Rooting the phone with King Root v3.5, this was unsuccessful
Any suggestions for things that I’m missing or something that I’m doing out of sequence? Is there a different way to approach this problem? Thank you!!
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
It's been quite a while since I flashed a device this old.
I suggest finding an old Windows 7 machine and using RSD Lite.
[How To][XT907] Flash Firmware with RSD Lite to restore stock firmware/Unbrick (2015)
Requires a PC Download Official Motorola Drivers, and RSD Lite from [INDEX]Motorola Unbricking Tools Install drivers, with Razr M not connected to PC Reboot PC Install RSD Lite Charge Razr M's battery Download...
forum.xda-developers.com

If your firmware was older than 183.46.15 you should be able to unlock the bootloader with motochopper. That is if you didn't take the last update. Maybe @sd_shadow can tell you how to check what version you had from fastboot. If not you'll have to use the sunshine apk but I don't know if they still charge for it.

Wheels564 said:
If your firmware was older than 183.46.15 you should be able to unlock the bootloader with motochopper. That is if you didn't take the last update. Maybe @sd_shadow can tell you how to check what version you had from fastboot. If not you'll have to use the sunshine apk but I don't know if they still charge for it.
Click to expand...
Click to collapse
Code:
fastboot getvar all
Will show current software version and kernel.

sd_shadow said:
Code:
fastboot getvar all
Will show current software version and kernel.
Click to expand...
Click to collapse
He'll want to check that then before flashing and if older than 183.46.15 makes sure he flashes the same version.

My bad "getvar all" doesn't include kernel info with XT907, too old.
adb works
Code:
adb shell cat /proc/version

If kernel is before June 3, 2014 (like May X 2014)
See Towel Root (1a. ROOT - Locked Bootloaders)

sd_shadow said:
My bad "getvar all" doesn't include kernel info with XT907, too old.
adb should
Code:
adb shell cat /proc/version
Click to expand...
Click to collapse
Don't adb commands have to be run from a functioning system? He wants to find the kernel info before he re-flashes. Then if he wants to run other roms he'll have to flash back to jellybean anyway as no roms for KK exist. I had to flash my M and HD back to jellybean to use them.

@sd_shadow @Wheels564
Thank you for taking the time to troubleshoot this problem with me. My only goal is to get every process/app to stop crashing when the phone loads. I assumed that wiping the phone clean of all apps and starting with a fresh copy of the ROM would be the best way to do that. If there is another (better) way I'm open to it...
- Checked all the computers in house, everything is on WIN 10.
- I can give both ADB and Fastboot Commands to the phone
- Kernel Info from ADB:
C:\mfastboot>adb shell cat /proc/version
Linux version 3.4.42-gbd361ac ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Tue Jul 29 06:07:11 PDT 2014

This is what I get when the OS loads and I get through the Screen Lock PIN:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After much patience clicking "OK" to get into Settings in the half a second before the next error pops up...
Fastboot Screen Shot:
Recovery Screen Shot:
Fastboot GetVar All Screen Shot:

Looks like you are on the latest update. Your gonna have to use the sunshine apk to unlock the bootloader. You should still re-flash the stock rom. You can get windows xp now as freeware and do a dual boot. Or install windows seven long enough to run rsd lite, flash the rom then unlock the bootloader.

Wheels564 said:
Looks like you are on the latest update. Your gonna have to use the sunshine apk to unlock the bootloader. You should still re-flash the stock rom. You can get windows xp now as freeware and do a dual boot. Or install windows seven long enough to run rsd lite, flash the rom then unlock the bootloader.
Click to expand...
Click to collapse
Do you need to unlock the bootloader before using RSD?
Is there a way to run the Sunshine APK through abd shell commands? I can't copy or load or run any apps through the user interface on the phone.
Is there a way that the phone's internal memory could have gotten switched to a "read only" state? Trying to sift through the adb logcat results there were several lines similar to:
Unable to open stack trace file '/data/anr/traces.txt': Read-only file system
Click to expand...
Click to collapse
android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database
Click to expand...
Click to collapse
E/DropBoxManagerService( 908): Can't write: system_app_crash
E/DropBoxManagerService( 908): java.io.IOException: Can't mkdir: /data/system/dropbox
Click to expand...
Click to collapse

crazyjcs said:
Do you need to unlock the bootloader before using RSD?
Is there a way to run the Sunshine APK through abd shell commands? I can't copy or load or run any apps through the user interface on the phone.
Is there a way that the phone's internal memory could have gotten switched to a "read only" state? Trying to sift through the adb logcat results there were several lines similar to:
Click to expand...
Click to collapse
No you do not have to unlock the bootloader first. Your problem looks similar to what I had with Ubuntu where corrupt files made the system go into failsafe mode and went read only. Android is Linux based also. I was able to repair the bad files with the fsck command but I haven't had that experience on android. I would try RSD lite first but if that doesn't work maybe sd_shadow has a better idea.

Wheels564 said:
No you do not have to unlock the bootloader first. Your problem looks similar to what I had with Ubuntu where corrupt files made the system go into failsafe mode and went read only. Android is Linux based also. I was able to repair the bad files with the fsck command but I haven't had that experience on android. I would try RSD lite first but if that doesn't work maybe sd_shadow has a better idea.
Click to expand...
Click to collapse
Thank you for the suggestions. I've got an old netbook that probably shouldn't be running WIN 10 anyway, so I'll see if I can revert it back to WIN 7 and run RSD on it.

Related

nexus 4 stuck on google logo

Hi
my nexus 4 stuck on the google logo after updating to kit kat
i tried to flash stock room 4.3 but it is stop on the google logo
i tried to flash stock rooms 4.2.2 and 4.2.1 but the same thing is happen
importnat note:
1-I can not go into recovery mode (when choose recovery mode the phone stop on google logo)
2- I can go into bootloader
3- bootloader it unlocked
4-usb debugging is not enabled
please helpe me it is a challenge for me.

Sideload the ota update. Guide. Files. And make sure adb is properly configured on your pc.

arffrhn said:
Sideload the ota update. Guide. Files. And make sure adb is properly configured on your pc.
Click to expand...
Click to collapse
how i can check the adb configuration on my PC

hralzarwi said:
how i can check the adb configuration on my PC
Click to expand...
Click to collapse
If you don't know it then I assume you haven't have adb set up on your pc. No worries, look here for a step by step guide how to set it up.
Edit: How did you try to flash the 4.3 after a failed 4.4 ota update? Now that I see, if you can't enter recovery, then you can't sideload. Try and download wug's toolkits. Some said that it can work even if your device can't get pass the google screen.

arffrhn said:
If you don't know it then I assume you haven't have adb set up on your pc. No worries, look here for a step by step guide how to set it up.
Edit: How did you try to flash the 4.3 after a failed 4.4 ota update?
Click to expand...
Click to collapse
i did it using nexus 4 toolkit number 9 then 2 after in put the stock room in (put_factory_image_here) folder
also I used nexus root toolkit (flash stock + unroot)

hralzarwi said:
Hi
my nexus 4 stuck on the google logo after updating to kit kat
i tried to flash stock room 4.3 but it is stop on the google logo
i tried to flash stock rooms 4.2.2 and 4.2.1 but the same thing is happen
importnat note:
1-I can not go into recovery mode (when choose recovery mode the phone stop on google logo)
2- I can go into bootloader
3- bootloader it unlocked
4-usb debugging is not enabled
please helpe me it is a challenge for me.
Click to expand...
Click to collapse
Do you have any custom recovery installed?
Do you already tried flash using fastboot or ADB?
(You can use the Unified Android Toolkit and performer a full flash).

davidbranco said:
Do you have any custom recovery installed?
Do you already tried flash using fastboot or ADB?
(You can use the Unified Android Toolkit and performer a full flash).
Click to expand...
Click to collapse
thank you too much
no i do not have any custom recovery
yes i tried to flash more than one room using fastboot but nothing
i will search of unified android toolkit
thanks again

Maybe you should try lock your bootloader and than relock it again? Type in fastboot (when your phone is in bootloader mode) : fastboot oem lock, than fastboot oem unlock. It can help. Regards
Wysłane z mojego Nexus 4 przy użyciu Tapatalka

I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please

ProrokX said:
Maybe you should try lock your bootloader and than relock it again? Type in fastboot (when your phone is in bootloader mode) : fastboot oem lock, than fastboot oem unlock. It can help. Regards
Wysłane z mojego Nexus 4 przy użyciu Tapatalka
Click to expand...
Click to collapse
thank you
i did it but still the device is not working

hralzarwi said:
I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please
Click to expand...
Click to collapse
Are you sure the factory images got flashed properly? I once had this problem...but in my case adb doesn't work as the phone wasn't detected on pc. But luckily, recovery still works. You're stuck at Google screen because there is no system in your device. Maybe as a result of incomplete flash or broken system.img. Is your phone gets detected in adb? Plug in your phone. Open CMD in platform-tools and type in adb devices. See if your device serial number is listed as device in cmd.
Sent from my Nexus 4 using xda premium

hralzarwi said:
I used unified android toolkit to flash 4.2.2 but the device still not working it is stuck on google logo
any one can help me please
Click to expand...
Click to collapse
Try this.
1. Download a factory image from here. For my instructions, I'm using 4.4 KitKat, feel free to install previous versions of Android.
2. Extract it
3. Drill down into occam-krt16o (or whatever build you're using) Double check to make sure the folder name starts with "occam". That means it's the right image for the Nexus 4
4. Copy all of the contents of that folder, should be 6 files, into your platform-tools folder, where you are issuing adb commands from.
5. Once all 6 files are copied into your platform-tools folder (or wherever fastboot.exe is, really. Where you're issuing commands from.)
6. Boot into your bootloader (Turn phone off, hold power and Vol-, or just use 'adb reboot bootloader')
7. In the command prompt that you should have opened in the same folder as fastboot.exe and the 6 files from the factory image, type 'flash-all.bat'
8. Sit back and wait while it reformats and reflashes every partition on your phone.
9. Boot up and make sure it worked.
Let me know if that worked, or where you're getting hung up on and why and I'll try to walk you through this, step-by-step.

Johmama said:
Try this.
1. Download a factory image from here. For my instructions, I'm using 4.4 KitKat, feel free to install previous versions of Android.
2. Extract it
3. Drill down into occam-krt16o (or whatever build you're using) Double check to make sure the folder name starts with "occam". That means it's the right image for the Nexus 4
4. Copy all of the contents of that folder, should be 6 files, into your platform-tools folder, where you are issuing adb commands from.
5. Once all 6 files are copied into your platform-tools folder (or wherever fastboot.exe is, really. Where you're issuing commands from.)
6. Boot into your bootloader (Turn phone off, hold power and Vol-, or just use 'adb reboot bootloader')
7. In the command prompt that you should have opened in the same folder as fastboot.exe and the 6 files from the factory image, type 'flash-all.bat'
8. Sit back and wait while it reformats and reflashes every partition on your phone.
9. Boot up and make sure it worked.
Let me know if that worked, or where you're getting hung up on and why and I'll try to walk you through this, step-by-step.
Click to expand...
Click to collapse
I did it perfectly but i still have the same problem
but i find this and i do not know if it is an error or what?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my phone still stuck on google logo
thank you too much for your concern

arffrhn said:
Are you sure the factory images got flashed properly? I once had this problem...but in my case adb doesn't work as the phone wasn't detected on pc. But luckily, recovery still works. You're stuck at Google screen because there is no system in your device. Maybe as a result of incomplete flash or broken system.img. Is your phone gets detected in adb? Plug in your phone. Open CMD in platform-tools and type in adb devices. See if your device serial number is listed as device in cmd.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think no , please see the message

hralzarwi said:
I did it perfectly but i still have the same problem
but i find this and i do not know if it is an error or what?
my phone still stuck on google logo
thank you too much for your concern
Click to expand...
Click to collapse
Well that is kind of weird, espeically considering you just got a bunch of 'OKAY' messages. Does a device come up if you type 'fastboot devices' while you're in the bootloader? If not, your drivers aren't quite installed correctly and this is an easier fix than what it could be. If so, then maybe try letting your phone sit at the Google logo. The initial start ups are usually long, maybe it just needs time.
If your device DOES come up in fastboot devices and you think you've given it enough time to start and it won't, then we might try to flash the images manually (even though it says they flashed successfully, which is annoying). Since you already have the factory image inside your platform-tools folder, try this:
1. Extract the image-occam-krt16o.zip into the platform-tools folder
2. You should now have, among other files, 6 .img files in your platform-tools folder Again, make sure those images are from an 'occam' image
3. Run these commands:
Code:
fastboot flash bootloader bootloader-mako-makoz20i.img
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
4. Once those are all done, try rebooting
This all might seem redundant, but this is a weird case and we're taking everything one step at a time. If you're still stuck, try updating your sdk and getting a newer fastboot.exe. If you have the sdk installed, just open SDK Manager.exe in the sdk\ folder

hralzarwi said:
I think no , please see the message
Click to expand...
Click to collapse
Well the CMD images you post earlier shows no issues when it flashes the factory images. That archive does contain bla bla bla is normal. Seems your device is not properly detected in adb. But the try this, when you are in fastboot type fastboot device. See if your device is listed.

Johmama said:
Well that is kind of weird, espeically considering you just got a bunch of 'OKAY' messages. Does a device come up if you type 'fastboot devices' while you're in the bootloader? If not, your drivers aren't quite installed correctly and this is an easier fix than what it could be. If so, then maybe try letting your phone sit at the Google logo. The initial start ups are usually long, maybe it just needs time.
If your device DOES come up in fastboot devices and you think you've given it enough time to start and it won't, then we might try to flash the images manually (even though it says they flashed successfully, which is annoying). Since you already have the factory image inside your platform-tools folder, try this:
1. Extract the image-occam-krt16o.zip into the platform-tools folder
2. You should now have, among other files, 6 .img files in your platform-tools folder Again, make sure those images are from an 'occam' image
3. Run these commands:
Code:
fastboot flash bootloader bootloader-mako-makoz20i.img
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash userdata userdata.img
4. Once those are all done, try rebooting
This all might seem redundant, but this is a weird case and we're taking everything one step at a time. If you're still stuck, try updating your sdk and getting a newer fastboot.exe. If you have the sdk installed, just open SDK Manager.exe in the sdk\ folder
Click to expand...
Click to collapse
woooooooooooooooooooow you are great man
after I give him a time but it is very long time about 5 hours my device is work probably but when I restart it it is stuck on goggle logo
LOOOOOOOOOOOOOOOOOOOOOOL
what do you think why it is stuck now?

arffrhn said:
Well the CMD images you post earlier shows no issues when it flashes the factory images. That archive does contain bla bla bla is normal. Seems your device is not properly detected in adb. But the try this, when you are in fastboot type fastboot device. See if your device is listed.
Click to expand...
Click to collapse
MR.arffrhn
thank you too much for your help and what do you think now why it is stuck ?

hralzarwi said:
MR.arffrhn
thank you too much for your help and what do you think now why it is stuck ?
Click to expand...
Click to collapse
So your device is working now? Well there are many that complained that their device got stuck in google screen after upgrading to 4.4. And the solution to that is a simple factory reset. If you can boot into system and still stuck on google screen, you can try this. http://forum.xda-developers.com/showpost.php?p=47846788&postcount=2

Well I'm confused as ****.
Tried to install 4.4. Failed. Was stuck on google circles. Fast forward , I gave up and tried to install 4.3.
....google logo for like 5 minutes. Then the "X" goes on forever.....
bootloader,rooted,etc,etc. Running PA 4.2 before this. Now all I want is a working phone lol.
google factory images ofc
---------- Post added at 01:17 AM ---------- Previous post was at 12:53 AM ----------
arffrhn said:
So your device is working now? Well there are many that complained that their device got stuck in google screen after upgrading to 4.4. And the solution to that is a simple factory reset. If you can boot into system and still stuck on google screen, you can try this. http://forum.xda-developers.com/showpost.php?p=47846788&postcount=2
Click to expand...
Click to collapse
no /system and /cache, can't sideload.... didn't apply that .zip update though?
After redoing it all with the .zip update.. no cache... TWRP still can't sideload.
android can be such a nightmare sometimes. I should have been done like 6 hours ago. Luckily, just a few minutes ago, I found this:
http://forum.xda-developers.com/showpost.php?p=44322165&postcount=30
And found that locking, then unlocking the bootloader FIXED THE PROBLEM!!!!
I hate android so much after this. I'll probably forget all about it like last time (lololol)

[Q] Google nexus 7 (2012) - Unrooting leads to total failure(no recovery, no boot up)

Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated

Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk

Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )

Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid

Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid

Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk

I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?

Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet

Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...

ZUK Z1 Entered an endless restart loop

Hey guys,
I was hoping you might help me as I was struggling to find an answer through google search.
After using the ZUK Z1 (Cyanogen OS 12.1 with the latest update), a few days ago the phone suddenly restarted and entered an endless restart loop
I've tried wiping the data, the cache and the user files.
I've tried applying the latest CyanogenOS zip for the Z1 either through sideload or locally from the device.
Nothing worked and I'm becoming very frustrated
I thought that maybe if I could wipe the system partition and then apply the COS zip than maybe it would work.
Does anybody have any ideas?
Thanks in advance,
Yoav.

Sideload the official stock rom with zuk z1 tool. That s how i managed to un-brick my zuk. Download the stock rom , cm-12.1-YOG4PAS3OH-ham-signed.zip from this page https://cyngn.com/support. Use the toolkit provided here : http://forum.xda-developers.com/zuk-z1/development/win-zuk-z1-toolkit-0-1-alpha-t3235964 to sideload the rom. Wait until the phone restarts and thats it. You must also install adb and fastboot and have adb driver installed.I used the shenqi adb composite driver, but i guess the universal adb driver can work too too.

Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone has any idea what that means? Does that mean that it is a hardware failure?

yoavk said:
Can you tell me what exactly did you do?
As far as I can see nothing works for me with the toolkit...
Did you use a mac or windows?
I checked that the driver is recognized (ShenQI), also tried manually using fastboot commands to unlock the bootloader and flashing images, but since my device is bricked I am unable to allow OEM unlock from inside Android
Update:
So I came across a discussion in this forum about bringing a bricked ZUK back to life
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
Done that, seem to be successful, however the phone won't turn on and the QPST Configuration tool shows that the device is stuck in download mode.
Does anyone has any idea what that means? Does that mean that it is a hardware failure?
Click to expand...
Click to collapse
Ok, so first, don t panic. If you re able to acces recovery and fastboot mode, there is a strong hope. I have Windows 7 on my PC, btw.
I tried the qpst tool to flash the stock, but i couldn t. That is why i turned to the Zuk Tool Kit, which did the trick for me.
To use this tool, FIRST OF ALL YOU MUST INSTALL ADB AND FASTBOOT. you can find varius tutorials about this on te interent. I provide you some, too:
http://forum.xda-developers.com/showthread.php?t=2588979
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
It was hard for me too to understand what is going on at first, but i did some research on the topic, and i got it.
After you installed adb, you can check if it is instaled by running the command "adb version" in CMD:
You should recieve something like this if it is installed.
After you installed fastboot and adb, install the Zuk Toolkit following the steps provided in the thread of Lenvo Zuk toolkit. Download cygwin, open cygwin terminal and drag start.sh from zuk toolkit folder into terminal window, press Enter, and you will have the menu open like this:
Here, just naviagte by writing the number corresponding to the menu you want to access and hitting enter.
Under "6. Do some basic ADB and Fastboot commands.
" coomands, you will have this menu:
Do note that [fASTBOOT] marked commands will work only when your phone is in fastboot mode. To acces your fast boot mode of your phone, just select "reboot to bootloader" option from recovery menu.
Once you managed to reach this state, you can put your phone in fastboot mode, and try the command "10. [Fastboot] Reflash to stock using a manually downloaded factory image."....
IF this doesn t work, try to flash the stock rom via sideload option from recovery menu of your phone. To do this, you must chose the sideload option from recovery menu. Download the stock signed rom from here https://cyngn.com/support(NOT THE FASTBOOT ONE, JUST THE SIGNED ONE.) Rename your stock rom zip file you just downloaded "sideload" and place it on desktop. Then use THE command "4. [ADB] Sideload a zip file.
" from zuk toolkit to flash the rom. Also you must have the phone connected to pc with the USB-c cable during the whole process, of course. If it works, your phone will show the animation of flashing procees on its screen. Wait until the phone stops, chose wipe dalvik and reboot.
Use the snipping tool or PrtSc to take screen images from where you are stuck or you don t know what to do, and post them here.

Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
C:\ WINDOWS\ system32> fastboot -i 0x2b4c oem device-info
< waiting for device >
Click to expand...
Click to collapse
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg

yoavk said:
Well, the QPST method seemed to have worked (as indicated by the QFIN tool).
However, it seems that the bootloop is back, when I am only able to boot into the ZUI recovery without any option of fastboot.
Edit:
Here is a pic of the Recovery (there is no option of adb sideload)
http: //s10.postimg. org/flaa11g3d/IMG_20160120_121012.jpg
Here is the fastboot
http: //s22.postimg. org/rgz4rt3a9/IMG_20160120_122555.jpg
And this is what i get when I try to use fastboot commands
All devices are discovered correctly in device manager
http: //s30.postimg. org/g8m1taywx/Capture.jpg
Click to expand...
Click to collapse
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
When you chose the install Update pacakge option, what options are displayed on your phone?
Also, if u installed qpst, you shoudl have in your PC a program callled QFIL, which is the flasher tool for all lenovos including ZUK. You must flash the zui stock rom using qfil. Read this thread for more info and downloads: http://forum.xda-developers.com/zuk...ui-version-t3265741/post64865607#post64865607
Also, here is a thread of a guy who had pretty much the same problem as you and managed to flash the stoc using QFIL : http://forum.xda-developers.com/zuk-z1/help/bricked-zuk-z1-t3277257

Extentho said:
You have the ZUI version?? Because this does not seem to be the stock recovery of cyanogen. At least, i have the option to sideload in my recovery.
Click to expand...
Click to collapse
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.

yoavk said:
Yeah, it was cyanogen and with QFIN I flashed stock ZUI in hopes that it will the bootloop.
I contacted coolicool, which is from where I bought the device.
I will send the device to them. I hope that they'll be able to find the problem.
Click to expand...
Click to collapse
I think you could try un-bricking it by yourself. It is not that hard. But if those guys from coolicool will change your phone, that s ok too. Blease be advised that rooting voids warranty...soo

Lucky me I didn't have the chance to do it
I didn't even have the chance to unlock the bootloader
Does anyone here have any experience with the guys over at coolicool?

i flashed coldbird's zip for capacitive touch on the fingerprint sensor. got into an endless restart loop after that. to every option, the toolkit replies command not found.
eg: ./xposeduninstallbootloop.sh: line 128: adb: command not found
followed by whatever option was ordered, that has been done successfully but can see no change.

Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056

Easy bro easy, the steps that you are following are a bit confusing, aren't they?
Please tell me the current status of your phone. I might be able to help.

Error mode: error 11 no recovery, error 2 failed to load

Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.

How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.

Hmm....
Have you tried rebooting to fastboot using adb?

Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times

Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?

elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.

Dc unlocker needs cash and it doesn t always work.

I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.

3 button upgrade doesn't work either.

I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.

Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method

shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..

Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain

Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!

I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.

Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.

elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??

Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.

I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.

[TWRP & ROOT] Ticwatch E/S & Unroot Instructions for Updates - v003

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER:
I'm not responsible for any damaged watches or other broken things! All of this is still heavily in development and mainly a developer release, not at all recommended for normal usage!
The following tutorial CAN brick your watch if you're not careful enough! Once again I'm not taking any responsibility!
This has only been tested on Android N so far, Android O is not yet fully tested!
---------------------------------------------------------
Please read before doing anything:
This is a port of TWRP for the Ticwatch E. Currently we're not able to boot it via fastboot (well, it technically does but there's an issue with the video driver) and when trying to flash it the watch will instantly flash the stock recovery over it upon reboot.
To avoid this we have to do a little workaround! Once you reboot your watch it'll restore the stock recovery again! After following these steps your watch will be stuck in a bootloop which we'll fix too tho.
Please keep the Changelog below in mind and read what's working and what's not before asking. We may or may not have seen this issue before already.
Files you'll need:
v003 of "TWRP for Ticwatch E" (and most likely S) - OneDrive Mirror
Stock Recovery for Ticwatch E (and most likely S) - OneDrive Mirror
ADB and Fastboot drivers installed (I recommend "15 Seconds ADB Installer")
Changelog:
Updated Instructions:
Slightly updated the instructions so you won't lose any data if you're already on an bootloader unlocked watch!
v003 (OneDrive Mirror):
Managed to make TWRP persistent! Check Instructions on how to.
v002 (OneDrive Mirror):
Now includes systemless root package inside the TWRP image so you're able to root your watch!
v001 (OneDrive Mirror):
Initial release, no ADB so far. Can't be booted from fastboot directly either due to weird fastboot behavior and has to be flashed first. However upon normal reboot Mobvoi decided to flash over the stock recovery again so we have to do a workaround.
Instructions:
The new Instructions by Luxios require a few less steps AND if you've already unlocked your watch before you won't even lose data!
Enable ADB in the Developer Settings
Once done connect your watch to your computer and do "adb reboot bootloader"
THIS WILL RESET YOUR WATCH:*Once in fastboot mode type "fastboot oem unlock" (if you already have an unlocked bootloader you [font=Verdana, Arial, Helvetica, sans-serif]can skip this[/font])
Follow the on-screen instructions on your watch to unlock it (if you already have an unlocked bootloader you can skip this)
Reboot via "fastboot reboot" and wait until Android Wear fully starts up
One started reboot to the bootloader via the same command as above
Once the bootloader shows up again type "fastboot flash recovery TWRP_TicwatchE_v003.img"
After that type "fastboot oem reboot-recovery" to reboot to the TWRP recovery
In order to make TWRP persistent you need to go to "Install" > "Install ZIP" > "supersu" > "TicwatchE_TWRP_keeper.zip" and flash it
Upon rebooting you may notice it'll get stuck in an infinite TWRP bootloop. To fix this boot into TWRP, then choose "Reboot" > "Bootloader", back in fastboot type "fastboot boot StockRecovery_TicwatchE.img" and wait a few seconds, a few reboots later Android Wear should start right up again.
If you want to root your watch reboot it once again with "adb reboot recovery" and go to the same folder as above, tho this time flash "SuperSU-2.79-wear_systemless.zip"
Unroot/Remove TWRP for Android O Update:
Go to this thread to also update directly to the last Android O update and revert all customizations: https://forum.xda-developers.com/sm...es/android-o-super-easy-ticwatch-e-s-t3789835
Have fun!

You're the best! I'm gonna try as soon as I can, and let you know.

Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?

Piereligio said:
Ok, I'm trying to flash it.
Problem is, it flashes, but when I do fastboot reboot, it will boot in android wear instead that TWRP.
If then I reboot in the recovery with adb reboot recovery, it will be already the stock recovery again... Any tip?
Click to expand...
Click to collapse
If your bootloader is (or was) already unlocked you have to lock and then unlock it again for it to work.

Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.

Piereligio said:
Yes sorry, I noticed that right after posting, but I've bad network.
Now seems to have gone all fine, I'm booting it, I'm only unsure it flashed SuperSU well, since it shown an error at the end of the script, although the rest of the log seemed to report all to go fine.
Click to expand...
Click to collapse
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.

Sadly it looks like SuperSU failed to root. It gave a data partition mounting error at the end of the script, don't know if it is normal. TWRP isn't able to mount data either.
EDIT: Looks like I found a way to boot TWRP without having to lock/unlock bootloader.
Doing this, I managed to boot TWRP after setting the watch up, and in this way, it didn't fail to mount /data. Let's see...
EDIT2: now SuperSU still fails, but for a different reason. I'm gonna ensure that it failed though.
EDIT3: su command responded, so seems that root works. I'll do some more tests.

TWRP is now persistent! Check the updated guide

Rooting succeeded!
Seems like I managed to root the smartwatch using the version 2. For the moment I'm happy like this, next times I'll indeed use new procedures.
EDIT: Yes, I rooted it.
My steps (the ones on OP are the recommended ones):
-Bootloader unlock;
-Boot in Android Wear to enable ADB from Settings;
-Reboot in bootloader with "adb reboot bootloader";
-Flashed this TWRP v2;
-"fastboot reboot", then "adb reboot recovery" as soon as adb was detected while booting.
In this way I managed to avoid the system to flash stock recovery over TWRP.
By the way, I don't recommend my way of rooting it, it's less safe, just follow the updated instructions in OP.
Huge thanks to @EpicLPer

Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.

BackCheck said:
Wow, this is excellent. I had TWRP built days ago, I went through hell (long story) finding the kernel code and got help from Mobvoi's CTO. I just couldn't get it to boot to recovery. I tried the supplied TWRP, seemed to basically work except for not being able to mount all the partitions. I tried the one I build and I'm in a bootloop. Power button does nothing, we'll see what happened when it loses it's battery. Oh well, will probably order another one anyway.
Thanks for the recovery. I'll resume testing when I get another working device.
Click to expand...
Click to collapse
You can flash again the stock recovery with spflash tool.

EpicLPer said:
If the watch doesn't turn off even after holding the button for a minute then you've damaged something else than just the recovery. Holding down the button normally triggers all the time no matter what, even if you'd have bricked it.
Click to expand...
Click to collapse
I really wish I knew what. All I did was flash a bad recovery, pretty sure something was was wrong with the ram disk. All I get is the splash logo for 3 seconds and a brief vibrate.
Luxios said:
You can flash again the stock recovery with spflash tool.
Click to expand...
Click to collapse
I think I need a scatter file to even get started. I've never used the tool so any other instructions would be greatly appreciated.

Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?

elios93 said:
Great to hear someone that it is working on this! What about Android Wear updates? Did you try if it is possible to install them using TWRP?
Edit 1: Just tried to install twrp but inside "supersu" folder there is only "SuperSU-2.79-wear_systemless.zip", where can I find "TicwatchE_TWRP_keeper.zip"?
Click to expand...
Click to collapse
I have the same problem...
EDIT: I have a Ticwatch S.

Niktendo said:
I have the same problem...
EDIT: I have a Ticwatch S.
Click to expand...
Click to collapse
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!

elios93 said:
I've managed to install it anyway. First check if it is not already installed using command
Code:
adb reboot recovery
If it does not work try this after you are in bootloader:
Code:
fastboot flash recovery TWRP_TicwatchE_v003.img
fastboot reboot
Then, as suggested by @Piereligio send this command as soon as possible while the watch is booting:
Code:
adb reboot recovery
This should work
However it is interesting that you have a S model. By sharing the build.prop of your device should be possible unlock all watchfaces for E model for instance!
Click to expand...
Click to collapse
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)

EpicLPer said:
The guy who made it initially did send me a picture of it successfully rooted. Should work, errors can happen since TWRP can't write to all partitions yet.
Click to expand...
Click to collapse
Can you get me the device tree or at least BoardConfig.mk used for this? I have a working watch (still working on recovering the old one) and I think I can get the rest of the partitions working but I would really like to avoid any more mistakes.
Luxios said:
This is the best way i found to install the TWRP recovery:
- Unlock the boot loader
- Reboot, wait until android start again
- Reboot again in boot loader mode
- flash the twrp v003 recovery
- type:
Code:
fastboot oem reboot-recovery
- Flash the twrp keeper zip package
- flash the root zip package (if you want root)
Click to expand...
Click to collapse
That 'fastboot oem reboot-recovery' command sure is a nice find!

Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol

hassanabid94 said:
Hey, bought my ticwatch e used online.
The watch is almost new and everything works as it should, but it has these two developer orriented apps preinstalled and can’t be uninstalled via settings neither with a factory reset.
They dont do anything but i just want to remove them
https://photos.app.goo.gl/gTNg5QCPzBtKgnzy1
And yeah the watch also generates a bug report by itself everyday i also want to stop that lol
Click to expand...
Click to collapse
Maybe it's a specific developer unit. Don't do anything with it yet, we could loom further into this if it is something special.

Database Users

welcome