Database Develop

How to Install 4.2 images, keep root and all data

**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images

Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?

Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..

jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.

mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.

tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window

Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!

kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.

OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/

rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options

You have .bat file in the package.

Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.

Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions

I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?

I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app

mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.

Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app

can I install image-nakasi-jop40c.zip directly without upgrading bootloader?

Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.

Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!

Cannot root... CWR: repeatedly attempted supersu and superuser

Hello,
I've unlocked the bootloader on my One, then proceeded to install supersu via zip through clockworkmod recovery.
I rebooted, attempted to gain root access, and was unable to.
I then rebooted into clockworkmod recovery and attempted to install superuser from this thread, rebooted and was unable to gain root. I then installed supersu from the same thread, and was unable to gain root.
Lastly, I attempted to wipe the cache partition and dalvik cache in effort, and still I am not able to gain root.
I'm unsure exactly what to do from here on out, as the process is truly very simple, but just not working.
Should I flash an official recovery and start over?
Thanks,
Matt

Have you opened the su app and updated the binaries?

I used twrp recovery a few days ago when I rooted. try to flash latest version of twrp through adb and wipe, clear cache,and retry.
If you still have trouble, check out wwjoshdew on youtube. I followed his instructions and rooted/unlocked with no hiccups.

BD619 said:
Have you opened the su app and updated the binaries?
Click to expand...
Click to collapse
Thanks for replying quickly.
The state I'm in now is:
- The SuperSu apk is gone.
- Superuser is installed.
- Root Checker, Helium, ES File Explorer's "root explorer" report no root
- Shark reports root (aka starts).
- superuser info reports `su` 3.2.18
- Used ES File Explorer to verify presence of `/system/bin/su`
Any idea on what could be wrong?
Thanks again,
Matt

How about another try on TWRP 2.6.3.0 recovery?

Sure, I will try this, Originally I tried TWRP, but couldn't access my internal storage (don't know why). Attempted sideload and failed, so I install clockwork and was able to install superuser.zip from /sdcard/.
Thanks!

Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)

branded said:
Grabbed TWRP 2.3.6.0 from: http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
> REBOOT BOOTLOADER
> BOOTLOADER
> RECOVERY
I then located the SuperSu zip and installed. Now I receive "There is no SU binary installed and SuperSu cannot install it. This is a problem!"
Rebooted into recovery and installed SuperUser.
Rebooted the system and attempted to access SuperUser, and it works. Verifies the presence of `/system/bin/su`.
Accessing helium and I don't have root.
So what do I do from here?
(sorry didn't brick my phone)
Click to expand...
Click to collapse
Get the latest version of SuperSU from here
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
I would suggest using it as it is updated more often then superuser as far as I know

Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt

Glad you got it enjoy

So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!

dtracycar said:
So I was having the same problem. I got TWRP recovery installed. I copied the SuperSU zip file to the root, but now when I try to install the SuperSU zip file, I don't see it!
Click to expand...
Click to collapse
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...

Devilish_Angel said:
... check the extension of the file you downloaded. Recoveries shouldnt oversee zip files ...
Click to expand...
Click to collapse
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?

dtracycar said:
Oh if only it were that easy. It is definitely a zip file with the proper extension. Any other ideas?
Click to expand...
Click to collapse
... Does it show rest of the files ...

Devilish_Angel said:
... Does it show rest of the files ...
Click to expand...
Click to collapse
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.

dtracycar said:
It doesn't. I'm baffled, I don't even know what its showing. Attached is a screen shot of the sdcard directory. When I navigate to the sdcard in recovery, it doesn't show anything like that. It has 6 folders, audio, GPU, mms, musicchannel, TWRP, and zchgd. When I browse my phone folders, I can't find any of those! OMG help.
Click to expand...
Click to collapse
... you might want to install TWRP 2.6.3.0.
Get it from here http://techerrata.com/file/twrp2/m7wls/openrecovery-twrp-2.6.3.0-m7wls.img
this is the .img file so you ought to flash it from fastboot ...

branded said:
Thanks,
I saved the file to my internal storage, restarted in TWRP, installed and erased the caches.
After rebooting... it works! You're the man!
I just got the One and just performed the OTA update the other day, so I am on 4.3. I bet this is what the "problem" was! So the updated SuperSU must be compatible with 4.3.
Thanks again!
Matt
Click to expand...
Click to collapse
4.3 was your problem. You needed to use a different SuperSU and this is the case with anyone else who wants to root 4.3 or 4.4. I believe I used SuperSU v1.65. Glad you got it working!

mHamers since
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse

dtracycar said:
Devilish_Angel said:
... you might want to install TWRP 2.6.3.0.
Ok, we're making progress! I installed the new TWRP recovery. Then I was able to find the SU zip file and flash it from there. All signs pointed to it working fine! There were no errors that I could see. Rebooted. Tried to open Titanium Backup and it hangs up with a message saying Asking for root rights... I do not find SuperSU anywhere in my apps tray. You've been super helpful so far! Now what?
Click to expand...
Click to collapse
... might be a bad SU file. download from here and flash from recovery
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip ...
Click to expand...
Click to collapse

Devilish_Angel said:
dtracycar said:
... might be a bad SU file. download from here and flash from recovery
Well, I finally got it to work! Thank you for all your help! Now if I could only get wifi hotspot or foxfi to work. Thats the whole reason I rooted in the first place!
Click to expand...
Click to collapse
Click to expand...
Click to collapse

[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.

[RECOVERY] Stock Recovery Image - v1.1.1.1929530

Here is a copy of the stock recovery.img from version 1.1.1.1929530 if anyone needs it:
Must enable ADB Debugging in developer menu! (About > tap build number to unlock developer options > developer options > Enable ADB Debugging) Make sure to grant access to your computer select ALWAYS.
Must have Unlocked bootloader: (which I assume you have if you are trying to go back to stock from TWRP)
Currently there is an unofficial build of TWRP that you can find here: http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005 (thanks @Tasssadar)
Instructions:
ADB DEBUGGING ENABLED!
- adb reboot bootloader
- fastboot flash recovery <location of stock img file>
- reboot to recovery to make sure everything worked.
- adb reboot
I am not responsible for anything that happens to your device, please do not come to me if you brick your Android Wear, I am just providing the stock recovery for anyone who needs it.
I have tested this myself after flashing TWRP recovery. Works fine for me so you should have no issues.
Download Link:
http://1drv.ms/1FOVnNR

sharky481232 said:
Here is a copy of the stock recovery.img from version 1.1.1.1929530 if anyone needs it:
Must enable ADB Debugging in developer menu! (About > tap build number to unlock developer options > developer options > Enable ADB Debugging) Make sure to grant access to your computer select ALWAYS.
Must have Unlocked bootloader: (which I assume you have if you are trying to go back to stock from TWRP)
Currently there is an unofficial build of TWRP that you can find here: http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005 (thanks @Tasssadar)
Instructions:
ADB DEBUGGING ENABLED!
- adb reboot bootloader
- fastboot flash recovery <location of stock img file>
- reboot to recovery to make sure everything worked.
- adb reboot
I am not responsible for anything that happens to your device, please do not come to me if you brick your Android Wear, I am just providing the stock recovery for anyone who needs it.
I have tested this myself after flashing TWRP recovery. Works fine for me so you should have no issues.
Download Link:
http://1drv.ms/1FOVnNR
Click to expand...
Click to collapse
Are backups and restores working? Or is there not enough memory? Anyone??

suzook said:
Are backups and restores working? Or is there not enough memory? Anyone??
Click to expand...
Click to collapse
I usually do a backup then once its done I use "adb pull" to my PC and delete the copy on the device. just safer that way. Anytime i need to restore I just "adb push" back to the same directory I pulled from.

sharky481232 said:
I usually do a backup then once its done I use "adb pull" to my PC and delete the copy on the device. just safer that way. Anytime i need to restore I just "adb push" back to the same directory I pulled from.
Click to expand...
Click to collapse
Thanks, gonna try and leave it on. I switch between my note4 and nexus 6...thinking I could just restore my backup when I switch. I wish wear was able to sync to multiple phones.

suzook said:
Thanks, gonna try and leave it on. I switch between my note4 and nexus 6...thinking I could just restore my backup when I switch. I wish wear was able to sync to multiple phones.
Click to expand...
Click to collapse
Havent tried this myself but seems like a faster process then restoring backups:
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962

sharky481232 said:
Havent tried this myself but seems like a faster process then restoring backups:
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
Click to expand...
Click to collapse
Thanks, I'll give that a look. BTW, I'm trying to flash recovery, my adb sees my watch, but when I try fastboot OEM unlock, I get stuck at "waiting for device"..... Any ideas???

suzook said:
Thanks, I'll give that a look. BTW, I'm trying to flash recovery, my adb sees my watch, but when I try fastboot OEM unlock, I get stuck at "waiting for device"..... Any ideas???
Click to expand...
Click to collapse
If you are using Linux, make sure you are in SU mode, also sometimes - I have to wait til the watch is in bootloader mode then remove the watch from dock and put it back on then the computer will find it.

Any chance you could provide a system.img too? I semi-bricked my watch and I need a system.img dump to get it up and running again - I can't use adb to push and flash a .zip, so a .img is my only option right now.

BJSerpas said:
Any chance you could provide a system.img too? I semi-bricked my watch and I need a system.img dump to get it up and running again - I can't use adb to push and flash a .zip, so a .img is my only option right now.
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005. There is a TWRP Urbane 5.1.1. image backup, including boot and system. Follow the instructions there and you'll be fined. I have just done so and recovered my urbane from a failed ROM.

Hello,
I have installed TWRP in order to root my Urbane (to increase the vibration intensity).
I need to reinstall the stock recovery to allow ROM to auto-install OTAs when available? or TWRP can be used by the system to install OTAs?
Thanks!

[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?