Database Info

[Q] Nexus 5 power button doesn't work anymore

Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.

PeauMorte said:
Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
Click to expand...
Click to collapse
Hoping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?

Primokorn said:
Hopping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Click to expand...
Click to collapse
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.

PeauMorte said:
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
Click to expand...
Click to collapse
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.

Primokorn said:
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Click to expand...
Click to collapse
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?

PeauMorte said:
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
Click to expand...
Click to collapse
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)

Primokorn said:
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Click to expand...
Click to collapse
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*

PeauMorte said:
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
Click to expand...
Click to collapse
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
PeauMorte said:
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
Click to expand...
Click to collapse
Put the file into your platform-tools folder (where you have fastboot.exe file)

Primokorn said:
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
Put the file into your platform-tools folder (where you have fastboot.exe file)
Click to expand...
Click to collapse
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?

PeauMorte said:
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
Click to expand...
Click to collapse
Did you rename the downloaded file to "TWRP.img"? The file name must be the same into your command prompt.
Copy TWRP.img into your platform-tools folder then open a command prompt from this folder and enter: fastboot boot TWRP.img
The path is the directory of your file you want to use. If you open the command prompt from the folder you have TWRP.img (platform-tools) then you don't need to mention the path.

I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.

vin4yak said:
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
Click to expand...
Click to collapse
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.

Primokorn said:
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Click to expand...
Click to collapse
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:

PeauMorte said:
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
Click to expand...
Click to collapse
Happy for you... and your data

Primokorn said:
Happy for you... and your data
Click to expand...
Click to collapse
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.

PeauMorte said:
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
Click to expand...
Click to collapse
Yes, you can! Just make sure you don't restore the /efs partition which contains the imei and other files which are unique to every device!
- Sent from an IceCold Hammerhead!

Root Moto G on Lollipop 5.0.2

Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
Click to expand...
Click to collapse
can i use with stock recovery?
thanks.

vbnoob said:
can i use with stock recovery?
thanks.
Click to expand...
Click to collapse
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta

n1c00_ said:
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
Click to expand...
Click to collapse
My phone is unlocked bootloader with stock recovery.
Thanks.

vbnoob said:
My phone is unlocked bootloader with stock recovery.
Thanks.
Click to expand...
Click to collapse
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...

n1c00_ said:
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
Click to expand...
Click to collapse
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.

I think I screwed phone. Being a noob I didn't realise fastboot and Bootloader screens are different. I went and use chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions link
in fastboot. After error failed now it ADB doesn't detect my phone.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>
Any advise to help me? Tried hard method going to bootload still nothing either or at least I think its nothing since this is first attempt I ever tried root my phone. Everytime I plugin in fastboot or even in normal mode the pc does detect it. But it just won't show up in adb.
Decided to try again using leocuervo1983 method for fastboot it stated as fail as well but somehow I got root even though adb still no longer detect my phone.
Edit:
Just found out fastboot doesn't use adb commands or do they? I feel stupid. I Guess there are no issues then even if failed still got root. Fastboot commands works adb doesn't work.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
TAXXXXXXXX fastboot

The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.

pfufle said:
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
Click to expand...
Click to collapse
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?

Xicor Yagami said:
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Click to expand...
Click to collapse
Yes since the recovery isn't entirely compatible with the new kernel.

pfufle said:
Yes since the recovery isn't entirely compatible with the new kernel.
Click to expand...
Click to collapse
Tried latest TWRP? same results?

Xicor Yagami said:
Tried latest TWRP? same results?
Click to expand...
Click to collapse
yep.

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
Click to expand...
Click to collapse
Thanks a lot! Worked like a charm using mfastboot command.

Works fine
My bootloader was however unlocked...I tried this on CM12....extract the img file from the CF-Auto root File and then flash on the bootloader mode...with mfastboot boot filename.img

The method same as that of kitkat works for lollipop too...you could made some mistake unknowingly somewhere in the middle while following the original procedure
Sent from my Moto G using XDA Free mobile app

is there any method to root moto g?
Any side effects of chainfire method?

leocuervo1983 said:
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
Click to expand...
Click to collapse
It did'n work for me .... I ran the bat file , and when I pressed a key, it was waiting for the phone and nothing happened.
Edited:
Sorry... I forgot to unlock bootloader first.... worked fine!!! Thanks a lot!!!

Can I still install any recovery(CWM or TWRP) after I have forgotten my password?

My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.

Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.

Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk

joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.

Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?

dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.

Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?

Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.

How do I root my MT7-L09 B571 on Arch Linux

Hallo there,
at first sorry for the nearly 10th post about this topic, but as you can see I'm in a different position than the most of you. I'm on Arch Linux here and I don't rly want to root my phone with a windows box.
I got adb and fastboot installed, but I can't find a general guide how to flash recovery and root with them, because there are always these click-click-shiny-shiny gui .exes for windows, which take some tasks.
I did root my Droid 3, but this was years ago, and I did never get into this stuff so deep it would help me now. I am a lil exhausted from the day, and don't rly want to puzzle my way through the google search results, which as described above lead to a .exe with a gui at some point.
Anyone here, who knows the basics and is willing to give me a hand here?
As I said I'm a Linux aka a terminal user so you don't need to be soft on this, I just need it compact but complete.
Thanks in advance
p.s. What I think will be relevant at some point, based on the search results so far:
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
http://forum.xda-developers.com/showpost.php?p=66546853&postcount=53

Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.

Mother_Teresa said:
Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.
Click to expand...
Click to collapse
aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
And there is another question. The part after
NOW LETS GET XPOSED AND LUCKY PATCHER WORKING
Click to expand...
Click to collapse
is not necessary if I use a different launcher than EMUI, or is it?
EDIT: A VM is not an option, would be the same for me than using a physical windows box.

quote: aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
sounds good to me, so now it is twrp and not cwm?
And there is another question. The part after "NOW LETS GET XPOSED AND LUCKY PATCHER WORKING" is not necessary if I use a different launcher than EMUI, or is it?
it allows customizing advanced settings and is implemented in boot. not necessary
EDIT: A VM is not an option, would be the same for me than using a physical windows box.
if you have recovery etc just flash supersu for root

Okay, good was just checking, if it's the way I puzzled it together. Don't want to wipe me phone.
Mother_Teresa said:
sounds good to me, so now it is twrp and not cwm?
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
What's the difference between twrp and cwm?
Mother_Teresa said:
it allows customizing advanced settings and is implemented in boot. not necessary
Click to expand...
Click to collapse
Okay, nice.
Mother_Teresa said:
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
Just like in the guide i guess. Thx.

This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?

pepper-jk said:
This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?
Click to expand...
Click to collapse
Yay well done and also on posting the solution. I reread what I typed and couldn't make sense to why I mentioned cwm and twrp (same stuff, diff developers or so) so maybe I mixed up bits of another topic

ROOT huawei watch2 (how to)

Hi guys,
long time is past after my last post, no matter, hello to all of you!
I am in China, owner of watch2, trying to root it but nothing happen.
I am wondering if there is a special recovery for it cause the one I am using for my huawei watch(1) is not working.
adb command, all fine, push recovery on it, all fine, after this no recovery start on the watch.
regards
edit: found the way to go to recovery (stock one) once in bootloader, select boot recovery, when you will see android logo with red triangle press for few seconds the "new second" button on the watch, recovery command will appear on the watch.
this is just one step more, anyway........ cant run custom recovery(flash it is ok), maybe we should find the right buttons combination to be pressed....

Any news on this?

giangishanghai said:
Hi guys,
long time is past after my last post, no matter, hello to all of you!
I am in China, owner of watch2, trying to root it but nothing happen.
I am wondering if there is a special recovery for it cause the one I am using for my huawei watch(1) is not working.
adb command, all fine, push recovery on it, all fine, after this no recovery start on the watch.
regards
edit: found the way to go to recovery (stock one) once in bootloader, select boot recovery, when you will see android logo with red triangle press for few seconds the "new second" button on the watch, recovery command will appear on the watch.
this is just one step more, anyway........ cant run custom recovery(flash it is ok), maybe we should find the right buttons combination to be pressed....
Click to expand...
Click to collapse
You can succeed in the root?

webcard said:
You can succeed in the root?
Click to expand...
Click to collapse
hello,
I have to say NO.
still reading and doing some test...
keep you update
regards

giangishanghai said:
hello,
I have to say NO.
still reading and doing some test...
keep you update
regards
Click to expand...
Click to collapse
Thank you for your reply, I have a few days to find the root method.

webcard said:
Thank you for your reply, I have a few days to find the root method.
Click to expand...
Click to collapse
Pardon? What's your meaning?

Found this thrad
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
could it work?
Follow this guide to flash SuperSU on the latest version of android wear for your watch, it should have the same OS compatibility as normal SuperSU and should work all the way upto android 7.1.1
(from PC)
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
adb reboot bootloader
fastboot oem unlock
2.flash TWRP for your device (REQUIRES read only access to system!, will post working builds in post below)
Code:
fastboot flash recovery recoveryname.img
3.Download SuperSU with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip
Code:
adb push nameofzip.zip /sdcard/
4.IGNORE SYSTEM NOT INSTALLED Boot watch to system and Now your root apps from 5.1 should work perfect
REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop.
If you would like to modify system use any Linux distro and unsquash the system then resquash it (will make guide if enough interest)
If you would like to change pixel density perform this command in either adb shell or a terminal emulator:
Code:
wm density <dpi>
Click to expand...
Click to collapse

Wagner.B said:
Found this thrad
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
could it work?
Click to expand...
Click to collapse
hello,
there is no recovery out jet for our HW2, we cant flash files so we cant do test.
btw we can change dpi on watch by adb without root.
regards