Database Develop

[Root] Root and TWRP for R

Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years

Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.

One more just in case.

Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?

hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.

I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!

hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.

Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.

Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?

adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app

reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.

adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.

tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!

HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!

I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...

zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app

Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there

zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.

Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)

zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.

Everything urbane root easy how-tos and all the files you need in one place (11/26)

The purpose of this thread is to make the rooting process easier with all the files you need in one place to root and tutorials and a list of must have apps
You will be able to find everything you need in one spot.
I TAKE NO RESPONSIBILITY FOR ANYTHING YOU DO TO YOUR DEVICE.
* Please Leave Suggestions On What Else You Would Like To See Included In This Thread
Check back often as this will be a work in progress
Please vote yes or like so I can get a feel for how many people are interested in a thread like this so I can decide whether or not it's worth my time to continue it.
I've also provided two prerooted system images ( just be sure to follow steps 1 thru 12 and step 18 ( optional depending on the image )
Thanks Rob
__________________________________
Let's start by voiding your warranty lol by unlocking the bootloader ( Warning this will erase all data and factory reset your watch ). You will need an adb fastboot program of your choice installed on your computer. I prefer minimum ADB fastboot link in downloads section. Plus the proper drivers ( I will be providing links to them as well later)
Now what I like to do is create a folder on the desktop of my computer and name it urbane. Then download all the files and apps I will need and put the in the folder.
That way you can open that folder and have ADB open at the same time and you can just drag and drop the file your planning on pushing or flashing to your watch by placing it after the proper command. Which will be explained later.
1- On your Watch go to settings
2- Scroll down to about click on it
3- Find and click on build number 5 to 8 times
4- Swipe back and now go into developer options and enable USB debugging
5: Put watch in the charger and plug into computer wait for computer to recognize it and install the drivers
6- Now open terminal emulator (minimum ADB fastboot) on your computer and without the quotes and hitting enter after each command type in
"adb devices"
You should see your watch there
7- Now type
"adb reboot bootloader"
8- Wait for it to boot into fastboot mode then type
"fastboot oem unlock"
9- Follow instructions on device
device will factory reset & reboot
10- Wait for it to fully reboot then follow steps 1 thru 7 again and we can flash TWRP
This is where the drag and drop comes in. In the command line where you see (drop here) that's where you will grab the file/image from your urbane folder and drop it onto the terminal screen
11- Now that you're back into fastboot mode type in
"fastboot flash recovery (drop twrp image here)"
12- OK let's see TRWP so type in
"adb reboot recovery"
Alright now that we know we have TWRP
Do a backup and reboot
Now is a good time to install a file browser, if you haven't already done so and advanced settings. I prefer the file browser I listed in the downloads section as you can send and install apks and files from your phone to your watch.
Now we're going to pull that backup to our computer
Use the file browser on your watch to get the exact path to your backup location which will look something like this /scars/TWRP/BACKUPS/and a bunch of numbers and letters/
So type in
"adb pull /sdcard/TWRP/BACKUPS/*************/ (drop your urbane folder here)/"
Wait for it to finish will take a few minutes and reboot
13- Plug your watch back into computer and wait for computer to recognize it again. Now we can install super su
type in
"adb push (drop su zip here) /sdcard/
14- Reboot into recovery
" adb reboot recovery "
Now's the tricky part, using TWRP's tiny navigation go to install then install zip then to sdcard and find and click on the su zip and install. Reboot
15- Now let's install busybox ( Note if you are going to install skin's kernel you can skip this step and proceed to step 18 as his kernel had busybox built in ). With the watch plugged into your computer. ADB and your urbane folder open
Type in
"adb push ( drop busybox apk here) /sdcard/"
16- On your watch open the file browser and navigate to the busybox apk and click on it. It will install and do is thing, once installed go to your applications find and click on it. It will act weird then probably say it's stopped working but that's OK it's installed and working
17- Kernel time
Type in
"adb push ( drop kernel image here) /sdcard/"
"adb reboot recovery"
In recovery click install then click image then click boot image
And navigate to your sdcard and find skin's kernel click on it and swipe to install
18- Let's start by doing another backup, so assuming you've already backed up at least once already and have pulled the backups to your computer. You can if you haven't already done so delete the backups on your watch before you backup again
19- Next let's take some control over our new custom kernel by installing kernel auditor
Type in
"adb push (drop kernel auditor apk here) / data/local/tmp/"
"adb install -r ( drop kernel auditor apk here)"
Reboot and enjoy
*PLEASE HIT THANKS*

DOWNLOADS
IF YOU ARE NEW TO THIS PLEASE READ THE OP ENTIRELY BEFORE TRYING TO FLASH OR INSTALL ANYTHING.
I TAKE NO RESPONSIBILITY FOR ANYTHING YOU DO TO YOUR DEVICE
Stock images provided by @Skin1980 -
Recovery- https://www.androidfilehost.com/?fid=24269982086988347
Boot- https://www.androidfilehost.com/?fid=24269982086988339
System- https://www.androidfilehost.com/?fid=24269982086988934
__________________________________
Rooted system images
After flashing be sure to wipe caches dalvik/cache
Rooted system imaged 5.1.1 LCA44B (super su installed) - https://www.androidfilehost.com/?fid=24269982087001702
The following images have some unnecessary system apps and watch faces uninstalled to slim down the system and to make room on the system partition to change other apps to system apps . ( you can get back any of the uninstalled apks by flashing the stock image file rebooting then using file browser on your watch navigate to the apk you want back and send it to your phone then after flashing this image send the apk back to your watch and install it)
Rooted system imaged 5.1.1 LCA44B ( su, busybox and kernel auditor installed ) to be combined with stock kernel as skin's kernel has busybox preinstalled -
https://www.androidfilehost.com/?fid=24269982087004874
Rooted system image 5.1.1 LCA44B (su and kernel auditor installed ) for use with skin's kernel-
https://www.androidfilehost.com/?fid=24269982087005360
My personal kernel auditor settings with skin's kernel for best performance-
https://www.androidfilehost.com/?fid=24269982087005023
___________________________________
Stuff for root ( images, apks, zips )
@Skin1980 kernel-
Original thread- http://forum.xda-developers.com/wat...rnel-skin1980s-g-watch-urbane-kernel-t3210691
Direct download-
https://www.androidfilehost.com/?fid=24269982086999750
TWRP 2.8.7.0 -
Original source- https://dl.twrp.me/bass/#
Alternate download-
https://www.androidfilehost.com/?fid=24269982086988968
Wear Supersu zip - https://www.androidfilehost.com/?fid=24269982086990060
Kernel auditor ported by @bitstra from @Grarak work -
Original thread- http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
Direct download-
https://www.androidfilehost.com/?fid=24269982086989489
BusyBox on rails apk - https://www.androidfilehost.com/?fid=24269982086989488
Minimum ADB fastboot for windows - http://forum.xda-developers.com/showthread.php?t=2317790
Google ADB drivers can be found here-
http://developer.android.com/sdk/win-usb.html
__________________________________
OTHER USEFUL APPS:
File manager for android wear - https://play.google.com/store/apps/details?id=com.woiapp.filemanagerwear&hl=en
Advanced settings - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
Reset Wear Client-
Original thread- http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
Direct download- https://www.androidfilehost.com/?fid=24269982087005403
Wear internet browser- https://play.google.com/store/apps/details?id=com.appfour.wearbrowser&hl=en
VFP benchmark for android wear-
https://play.google.com/store/apps/details?id=jp.flatlib.flatlib3.vfpbenchw
____________________________________
Useful apks that can be sideloaded:
Greenify - https://www.androidfilehost.com/?fid=24269982086999820
/system/appmover
Used to convert user apps into system apps and vice versa ( USE CAUTION )
https://www.androidfilehost.com/?fid=24269982087004923

Other How-tos
Flashing images via fastboot
1- plug watch into computer and start ADB
2- Type in
"adb reboot bootloader"
"fastboot flash boot ( drop boot image here)"
"fastboot flash recovery ( drop recovery image here)"
"fastboot flash system ( drop system image here)"
__________________________________________
Returning to Stock
1- Download the stock images from the downloads section to your computer
2- Follow the above instructions for flashing images
3- Now on the watch click one of the arrows till you see recovery then click the circle (center button)
4- You will see a droid laying down with a red triangle
Swipe from the top left of the screen down to the bottom right
Now you're in recovery
Now you want to do a factory reset

I would just like to give a big thanks to those of you kind enough to hit the thanks button and that goes to a select few as I've had well over 100 downloads, 2100 views and only 21 thanks. I see it all over we really need to show the people that make this site great some appreciation

Awesome work! Keep it up!

Robshr said:
The beginnings of the downloads section is up.
Working on tutorials and links to threads
Also a prerooted (super su and busybox installed) latest version system image
Click to expand...
Click to collapse
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app

meand0g1 said:
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Yes that's what I'm hoping for. After you flash it you can test by typing
"adb shell"
"su"
And you should see something like this
[email protected]:/ #
If you do then super su is installed and you're rooted

meand0g1 said:
So I only have to flash the prerooted system image and I'm fine to be rooted?
(TWRP for a backup at first of course..)
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
Just wondering if it all worked out for you?

Will test it when I own the watch..
Sent from my HTC One M9 using XDA Free mobile app

Doing all of this right now. Will report back when finished! Thanks man
---------- Post added at 06:35 PM ---------- Previous post was at 05:38 PM ----------
Okay so I unlocked bootloader, flashed twrp and rebooted into recovery. I can't backup anything because nothing is mounted. I've tried mounting though twrp with no luck whatsoever. So I tried erasing system and boot using fastboot to flash system image and skins kernel. But when I reboot the watch it boots straight into recovery....

anthonyg45157 said:
Doing all of this right now. Will report back when finished! Thanks man
---------- Post added at 06:35 PM ---------- Previous post was at 05:38 PM ----------
Okay so I unlocked bootloader, flashed twrp and rebooted into recovery. I can't backup anything because nothing is mounted. I've tried mounting though twrp with no luck whatsoever. So I tried erasing system and boot using fastboot to flash system image and skins kernel. But when I reboot the watch it boots straight into recovery....
Click to expand...
Click to collapse
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up

Robshr said:
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up
Click to expand...
Click to collapse
I'm using preroot image for skins kernel with kernel auditor . I've tried using
Fastboot flash system "drag and drop system.img" then
Fastboot flash boot "drag and drop skins boot.img"
Then reboot and it goes straight into recovery
The only way I could get data to show up in twrp was formatting data

anthonyg45157 said:
I'm using preroot image for skins kernel with kernel auditor . I've tried using
Fastboot flash system "drag and drop system.img" then
Fastboot flash boot "drag and drop skins boot.img"
Then reboot and it goes straight into recovery
The only way I could get data to show up in twrp was formatting data
Click to expand...
Click to collapse
I'm not sure what happened but somewhere along the line a step was missed or something was either flashed wrong or a corrupt download. I would say to stay over boot into recovery and do a factory data rest and start over

Robshr said:
Boot into fastboot and if you already have skin's kernel flashed try just flashing the system image and make sure you wipe the caches Dalvic/cache
Questions- did you flash su or did you use a prerooted image. I think su needs to be installed to do a back up
Click to expand...
Click to collapse
Robshr said:
I'm not sure what happened but somewhere along the line a step was missed or something was either flashed wrong or a corrupt download. I would say to stay over boot into recovery and do a factory data rest and start over
Click to expand...
Click to collapse
Gonna try download stock images and flash those to see if I can e en get this thing to boot, it doesn't even try it goes straight into recovery.

anthonyg45157 said:
Gonna try download stock images and flash those to see if I can e en get this thing to boot, it doesn't even try it goes straight into recovery.
Click to expand...
Click to collapse
That's strange because I just had to reset my watch back to stock and prerooted with my above post and everything went fine
Please keep me updated so if I have to I can make any necessary changes or help in anyway

Robshr said:
That's strange because I just had to reset my watch back to stock and prerooted with my above post and everything went fine
Please keep me updated so if I have to I can make any necessary changes or help in anyway
Click to expand...
Click to collapse
Was looking over the steps again from OP and it looks like step 10 is missing? Maybe that's something, I'm starting from the beginning
---------- Post added at 07:54 PM ---------- Previous post was at 07:16 PM ----------
Starting to lose hope, I've even tried erasing all data, booting into fastboot
Fastboot flash system (stock system.img)
Fastboot flash boot (stock kernel boot.img)
Whenever I reboot it goes straight into recovery , I've never even saw the android screen

anthonyg45157 said:
Was looking over the steps again from OP and it looks like step 10 is missing? Maybe that's something, I'm starting from the beginning
---------- Post added at 07:54 PM ---------- Previous post was at 07:16 PM ----------
Starting to lose hope, I've even tried erasing all data, booting into fastboot
Fastboot flash system (stock system.img)
Fastboot flash boot (stock kernel boot.img)
Whenever I reboot it goes straight into recovery , I've never even saw the android screen
Click to expand...
Click to collapse
The missing step ten was just a mistake
Fastboot flash only the stock recovery then try to boot into recovery and you should see an upside down android just swipe across the screen to get into stock recovery then fastboot stock image and follow the instruction to root again
Please message me with any other problems as to no clog up the thread
As I will post our findings later

Figured everything out for anyone following this thread. I ended up starting over after formatting data. I flashed everything stock, flashed modified system image and skin1980 boot image then booted rom, went back andf flashed twrp again and everything is working as expected. Not really sure what caused the issue,
Thanks to @Robshr for all of his help

I installed a different file manager on the watch just like you installed the kernel auditor. this file manager gives the message "sdcard inaccessible" when I try to open the sdcard. Do you think that this is doing this because it was installed in the tmp folder? Do you recommend paying for the paid app and I should have access to the sdcard?
Also I was unable to pull the backup from the watch, some error stating some file was not created because it wasn't found?
any ideas?

cubandanger05 said:
I installed a different file manager on the watch just like you installed the kernel auditor. this file manager gives the message "sdcard inaccessible" when I try to open the sdcard. Do you think that this is doing this because it was installed in the tmp folder? Do you recommend paying for the paid app and I should have access to the sdcard?
Also I was unable to pull the backup from the watch, some error stating some file was not created because it wasn't found?
any ideas?
Click to expand...
Click to collapse
As far as the file manager it depends on what one you are using does it state the the free version can't access the sdcard otherwise it should be able to read it
Not sure about the error message you're getting without seeing it
But it sounds like you didn't first copy the image to the sdcard and that's why it can't find it or didn't give it sufficient time to copy before you gave the pull command

[ROM/GUIDE] How to Restore Stock A2017U B20 Firmware and Re-lock Bootloader

First of all, I would like to say thanks to @DrakenFX, @tenfar, @rczrider, and @tennear for their work on the Axon 7.
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or any other mishaps that may occur. YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*/
This guide is intended to help anyone wishing to return to stock B20 firmware on the A2017U for the purposes of re-locking the bootloader (either for sending a device in for an RMA or whatever you may need). After much trial and error, I have finally come up with a guide and attached all necessary files to do this. I performed the following steps on my Axon 7 2017U on the B29 firmware and successfully downgraded to the B20 firmware with a re-locked bootloader.
Here are the files you will need:
Stock system
Stock boot stack
Stock fastboot
Stock recovery
TWRP
Make sure you have ADB and fastboot set up properly on your computer.
Use the TWRP linked in this post. I know for sure that this version works towards the end of this process when your bootloader is locked again.
After you have the zip files, you will need to move them to your phone to flash in TWRP. Follow these steps:
1. Make a backup of all of your important data. EVERYTHING will be wiped in this process, including internal storage.
2. Power off the phone.
3. Download the the axon7tool executable file from this link: Here Check the post for instructions pertaining to drivers needed.
4. Boot the phone into EDL mode. Do this by holding down the Volume Up and Volume Down keys simultaneously and then plugging the phone in to your computer while keeping these keys pressed. (The phone's screen will be completely black and it will appear like nothing is happening. This is EDL mode.)
5. Open a command prompt in the directory with the axon7tool executable. (Windows: right click while holding shift and select "Open command window here." Linux: Open a terminal and cd into the directory)
6. Dump your gpt with the tool. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -r gpt
Linux: ./axon7tool-1.5-linux -r gpt
7. The axon7tool will automatically reboot you. Reboot to TWRP.
8. Make a backup of your EFS partition by going to "Backup" with only the EFS box checked.
9. Copy the "TWRP" folder from your internal storage to your computer. This folder contains the EFS backup.
10. Go to "Wipe" -> "Advanced" -> "Format Data." Type "yes." WARNING: THIS DELETES ALL DATA. MAKE SURE YOU HAVE A BACKUP.
11. Reboot back into TWRP. Ignore anything TWRP says or asks you to do upon a reboot.
12. Copy the "B20_stock_system," B20_stock_bootstack," and "B20_stock_fastboot" zip files to your internal storage.
13. Flash the stock system zip first, then the boot stack zip, and finally the fastboot zip.
14. At this point you are on the stock B20 system, but with an unlocked bootloader. TWRP will probably be overwritten, so follow these next steps regardless.
15. Reboot the phone and let it get to the set up screen. This step can take a while; my Axon took almost a minute to get off of the ZTE splash screen initially.
16. As soon as you see that the phone boots, power off the phone and reboot to EDL mode.
17. Flash TWRP again with the axon7tool as it has been overwritten at this point and will be necessary soon. Download the linked TWRP recovery image and rename the file to "recovery.bin" Place it in the same folder as the axon7tool. Flash the recovery. (Note: you may need root access to run the following commands on Linux)
Code:
Windows: axon7tool-1.5-win64 -w recovery
Linux: ./axon7tool-1.5-linux -w recovery
18. Reboot the phone into the bootloader. You can do this by going to TWRP and by choosing reboot to bootloader or by manually doing so.
19. Type "fastboot oem lock" into a command prompt. This will lock your bootloader.
20. After I did this, I thought I was done. However, when I rebooted my phone, I saw that /data required a password to be decrypted upon a reboot. This is why we flashed TWRP. Go into TWRP and format data again.
21. Copy the "TWRP" phone from earlier back onto your internal storage. Restore your EFS in case anything has happened to your IMEI in this process.
22. At this point your phone is completely locked but with a custom recovery. To restore the stock recovery, reboot into EDL mode and replace the TWRP recovery.bin file from a few steps ago with the B20_stock_recovery.bin file you downloaded. Rename the B20_stock_recovery.bin file to recovery.bin and make sure it's in the same folder as the axon7tool.
23. Flash the stock recovery with the same commands for the axon7tool as listed earlier for TWRP.
24. Profit

As tennear has noted, do NOT backup or restore the EFS partition.

Never restore EFS using TWRP. You will lose its contents and probably your IMEI.

@tennear Thanks for the heads up. I'll remove that part from my guide.

Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?

mortkarg5 said:
Hi
I flashed the twrp recovery on locked bootloader but i lost my recovery
My firmware was 0b15
Can i flash the 0b20 stock recovery.bin to restore it?
Click to expand...
Click to collapse
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?

Yoshi_Guy said:
Were you trying to restore your whole firmware to b20 as the guide demonstrates or were you only flashing the TWRP linked in this post?
Click to expand...
Click to collapse
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?

mortkarg5 said:
Oh no...
I had tried to flash twrp to install a custom rom...
And i used the Miflash tool to flash it,but i forgot to unlock bootloader, and i think if i flash the stock recovery, i will be able to change the situation...
Are you think this will work?
Or i have to downgrade my firmware to 0b20 and then flash the full pack?
Click to expand...
Click to collapse
You can try, but I'm not sure if it would work. The recovery is for stock b20 so try it at your own discretion.

Every time I try to do the fastboot oem lock it fails, I have the twrp you mentioned in the post and followed the steps as listed. Did you run into this issue?
Sent from my ZTE A2017U using Tapatalk

i can't found same file u can upload again?

Yeah.... most links are dead. Does anyone else have them?

Flapjack said:
Yeah.... most links are dead. Does anyone else have them?
Click to expand...
Click to collapse
I'll fix them.

Yoshi_Guy said:
I'll fix them.
Click to expand...
Click to collapse
Thanks, brotha.

Flapjack said:
Thanks, brotha.
Click to expand...
Click to collapse
Try again, they should be working now.

Yoshi_Guy said:
Try again, they should be working now.
Click to expand...
Click to collapse
Thanks... but holy f*ck... this MEGA bs. What a piece of garbage. Why do I need to create an account?

I'm getting the following error (Win 10). Others have gotten the same error in various versions of linux, as well. The only one who resolved the error had forgot to elevate his terminal (which I've done):
Code:
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
c:\Temp\Axon>axon7tool-1.5-win64 -r gpt
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.

@Yoshi_Guy
In step 22) where stock recovery has to be restored, instead of reusing axon7tool in EDL mode, maybe it would be easier to flash stock recovery by the signed tenfar TWRP itself (by using TWRP Install/flash image option, boot partition). This is a kind of "hara-kiri" (current TWRP destroys itself) but it should work.

Flapjack said:
I'm seriously stuck. I did everything up to step 15, but it starts to boot, sits at the ZTE screen for about 30 seconds, then shuts off. When I try to reboot, it does the same thing. I had two problems getting up to step 15. The first problem was that the axon tool refused to work. I posted the error a few days ago, but no one replied. Since the phone has to go back to ZTE and I'm running out of time, I decided to press on.... since it only seemed like a backup, which I have plenty of.
The second error was at step 12. After Step 10, I could not read/write anything on the internal sdcard. It is obviously encrypted... which begs the question... what good is step 10 if it doesn't blow away the encryption? At any rate, I copied the the three zip files to an external SD card flashed the bootstack and fastboot, both of which completed without error.
As of now, I can get into the ZTE MiFavor recovery and then to bootloader mode, but it won't take any of the fastboot commands. Running fastboot devices shows the phone, but every fastboot command fails with "unknown command".
I've also tried flashing the B20 system and fastboot zips from the MiFavor recovery, but both say "signature verification failed".
Not sure what to do now.
---------- Post added at 08:13 PM ---------- Previous post was at 07:26 PM ----------
I just tried the official ZTE file here, but it said "signature verification failed" also. Not sure how that's possible.
Click to expand...
Click to collapse
That's quite odd, what version of Linux are you using? Also, are you able to try the Windows version of the tool? I've used the tool on Arch Linux and had no problems. Also, the program does need to be run as root, as you mentioned. The signature verification probably failed because you are trying to downgrade your version, I wouldn't recommend using the official ZTE zips entirely. I would take what you need and flash just that, downgrading is rather complex.

Thanks for the guide, but wish you would've used androidfilehost. I hit MEGA quota at 80%, so I'll have to wait til late tonight to give this a shot.
nvm: using megadownloader now

[How-To] Install Oreo OTA! [T-Mobile]

*DON'T FLASH BACK TO NOUGAT IF YOU ENJOY USING YOUR PHONE*
Ok guys ive made my return and im happy to bring the oreo ota with me.!
Steps to install if your on a rom.
1. Use this flash all link Here
2. After finished and setup your going to need a pc and sideload knowledge
3. Download these ota files
Latest August https://drive.google.com/file/d/1OhWZPTWcuo7zRu9bjiezjKEZxreOk6v7/view OREO
4. Get your phone into recovery mode.
4.a the file is gonna have a lot of letters please do not rename or it wont work
4.b before you get into recovery you will see a dead Android. This IS normal. Your going to want to hold power and push volume up. It's a split second kinda thing. Not something you guys forever. Hot that a few times if it doesn't work the first time.
5 your going to want to go to in recovery to apply update via adb for the August one
6. run the command adb sideload (now drag the file to the command prompt and press enter)
7 if all good you will see a verifiying update the step 1/2 when you see that your fine.
8 Let it do its thing and at the end you may see and error about a drive disregard that.
9 now follow steps 4-7 again but with Oreo ota
10 reboot your system and now you should have oreo!
If your stock locked and never been cocked you can try to install the same method above without using the flash all and if it works congrats if not unlock your bootloader and use the method above.
if any help is needed contact me @ [email protected]
HOW TO ROOT
1. DOWNLOAD THIS. https://drive.google.com/file/d/1zz3Fl9m4-_ozWW1U3ww_e6K_cHPPEMSv/view?usp=drivesdk
2. FASTBOOT BOOT OR FLASH IT RUNNING "FASTBOOT BOOT /PATH/TO/BOOT.IMG" OR FASTBOOT FLASH /PATH/TO/BOOT.IMG
3. REBOOT AND PROFIT.
TWRP 3.2.1-0 Bootable and Permanent
Bootable Fastboot boot this *ONLY FOR OREO*
*Permanent is broken* Use boot able
Unencryption for oreo
Encryption Remover *FOR OREO ONLY*
*Must format then flash*
OREO FLASH ALL OREO *YOU CAN ONLY FLASH THIS AFTER YOU HAVE TAKEN THE OTA* *IF YOU FLASH THIS AND YOU HAVENT AND YOUR PHONE BLOWS UP PLEASE VIDEO IT SO I CAN POST IT ON HERE AND SHOW WHAT NOT TO DO*
Thank to @XirXes for the ota files

There is no root available as of yet we need a boot image to get root once there is one we will have roms and root coming.

Screenies
Here you go

Installation went smooth. thanks for the OTA.

now towait for the root and all will be set

wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
No. As of right now Oreo starts you clean when you do this

Amd4life said:
wow you are FAST. awesome work for those that did not get the notification. Can you go "back" to 7.1.1 if desired for whatever reason?
Click to expand...
Click to collapse
I recommend (from experience) not trying that.

Making a test twrp real quick

Damn...thanks for your work

joemossjr said:
Making a test twrp real quick
Click to expand...
Click to collapse
Looking to this!
Oreo build is almost as fastest as the Flash [emoji3][emoji16]
Sent from my Moto Z (2) using Tapatalk

Thanks, @joemossjr ! It installed for me too. In my case, for some reason, I had to rename it to update.zip before adb sideload would work, but I'm not sure why. Oreo, yayyyy!

can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff

where's the TWRP, so only use a fastboot flash boot image.zip?

joemossjr said:
can someone please pull a system backup not image? i have a twrp that you can boot not flash and pull the stuff
Click to expand...
Click to collapse
I could, do you have the TWRP link?
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
What I wanted to do was boot slot _b rooted 7.1.1 and copy slot _a stock Oreo, but it nagged me about potentially bricking in fastboot after fastboot set_active _b (i.e., due to invalid bootloader, etc.). A bootable TWRP straight to recovery would solve the issue. All I wanted to do was get a copy of Oreo boot_a, but adb as non-root user does not have permission to dd copy /dev/block/bootdevice/by-name/boot_a . So, yay for bootable TWRP!

@jhofseth please write me on hagnouts

please message me on hangouts people who want to help [email protected]

When you brick and have to go to a leaked 8.0 image

Unable to flash update
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
Code:
E:failed to unmount /
E:failed to set up expected mounts for install; aborting
failed to open driver control: no such file or directory
installation aborted
also when selecting install from ADB it says
Code:
Supported API: 3
stopping adbd...
failed to open driver control: no such file or directory
failed to open driver control: no such file or directory
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.

Shiro12 said:
For whatever reason i'm unable to flash the update, and i'm currently left with a soft-bricked device. When trying to flash the update via recovery gives me
also when selecting install from ADB it says
is there something i can do to remedy this??
forgot to mention that yes i did install the first package and properly executed the flashall command from the first zip folder, and i did try sideloading the second package as it was and as an update.zip file to no success.
Click to expand...
Click to collapse
Do you go completely stock?

Help rooting stock without loosing data

Hi,
I got a new Mi Mix 6GB/256GB and am very happy with it. I have stock MIUI Global 9.2.1.0 NAHMIEK. I've been rooting my phones for a long time, but can't seem to succeed with this one.
I unlocked successfully. I tried multiple TWRP advised for this phone but get stuck with the password to decrypt my data partition. I tried to remove the pattern, use the digits associated to the pattern, set a password instead of a pattern, remove fingerprints, remove all security, but still could not decrypt. I tried both flashing and just booting to TWRP from fastboot.
Worst, I bricked a couple of times with the recovery flashing, or even simply booting remotely with twrp, being stuck in the "unlocked" logo on boot. Had to use mi flash to reflash stock ROM.
What I see is advice to wipe data and format unencrypted, but I prefer to keep my data partition impact to avoid reinstalling everything.
Any other idea on how to root? Basically, I need to install gcam which is my primary need.
Thanks!

If I'm not mistaken you need the modified rains twrp, somebody correct me if I'm wrong.
IV been unlocked and rooted for along time and don't really remember what process I used. But I do remember having to use rains twrp.

You can enable camera2.api via TWRP without rooting.
Read the whole thread.
https://xiaomi.eu/community/threads/google-camera-for-mi-max-2.42976/
As far as I know no-one has solved the problem of making a TWRP that can encrypt/decrypt.
If you don't really need the encryption it is better to format.

Thanks for your answers. I had tried TWRP by Mr Raines, but it seems an old version that must have worked on MIUI 8, but not on MIUI 9. TWRP 3.2.1 by Raupe is supposedly the only one working, but not in my case and still not able to bypass encryption...
I tried booting TWRP to push the build.prop with adb with APICamera2 enabled, I had high hopes, but every time I touch it, the phone gets soft bricked and I need to flash back stock...

Just got a solid breakthrough! I simply sideloaded magisk.zip. Then, from Android, used a buil.prop editor to enable cameraAPI2. It seems to work great so far. More precisely:
Install fastboot and adb on PC
Get TWRP 3.2.1 by raupe, and copy it in same folder as adb and rename to twrp.img
fastboot.exe boot twrp.img
From TWRP, cancel decryption, mount system, then go to advanced > ADB sideload
From PC, open cmd as admin, then: adb sideload Magisk.zip (where you would also have put the latest magisk zip in adb folder)
I then used a build.prop editor to add the line: persist.camera.HAL3.enabled=1
I can't believe it!

pzkfwg said:
Thanks for your answers. I had tried TWRP by Mr Raines, but it seems an old version that must have worked on MIUI 8, but not on MIUI 9. TWRP 3.2.1 by Raupe is supposedly the only one working, but not in my case and still not able to bypass encryption...
I tried booting TWRP to push the build.prop with adb with APICamera2 enabled, I had high hopes, but every time I touch it, the phone gets soft bricked and I need to flash back stock...
Click to expand...
Click to collapse
Yeah I meant to say Raupe instead of Mr Rains sorry for tell you that you should try rains. Like I said it's been awhile kinda forgot.. Again my apologies.
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Let me see if I can find the twrp I used I'm on miui 9.

pzkfwg said:
Just got a solid breakthrough! I simply sideloaded magisk.zip. Then, from Android, used a buil.prop editor to enable cameraAPI2. It seems to work great so far. More precisely:
Install fastboot and adb on PC
Get TWRP 3.2.1 by raupe, and copy it in same folder as adb and rename to twrp.img
fastboot.exe boot twrp.img
From TWRP, cancel decryption, mount system, then go to advanced > ADB sideload
From PC, open cmd as admin, then: adb sideload Magisk.zip (where you would also have put the latest magisk zip in adb folder)
I then used a build.prop editor to add the line: persist.camera.HAL3.enabled=1
I can't believe it!
Click to expand...
Click to collapse
Good for you!
Yes, I used raupes latest TWRP also, forgot to write that before.
Raupe has posted a lot in the otherwise abandoned "official" TWRP thread, you can read about his attempts on encryption:
https://forum.xda-developers.com/mi...y-official-twrp-xiaomi-mi-mix-t3498960/page57