I am basically screwed until somebody can make a custom recovery and do a system pull that I can use to recover.
Root Working
- Thread starter hecksagon
- Start date
Oh damn, no good. If someone can pull the Jawbone app and upload it for you, would that help get you up and running again? Or are you unable to boot?
Having root is good enough for me for now, I will hold off experimenting until I have an emulator running the root setup I have.
BTW, I will dump my ROM for you if that will help? Just not sure how.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:46 AM ---------- Previous post was at 07:45 AM ----------
How do you not have adb? Hard brick, or corrupted bios partition?
Sent from my Nexus 6 using Tapatalk
BTW, I will dump my ROM for you if that will help? Just not sure how.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 07:46 AM ---------- Previous post was at 07:45 AM ----------
How do you not have adb? Hard brick, or corrupted bios partition?
Sent from my Nexus 6 using Tapatalk
Device won't boot after making just a small change in build.prop. Adb access in recovery is limited to sideload only. Sideloads fail because I've removed Jawbone Up.
So you can't sideload jawbone... Heh.
Sent from my Nexus 6 using Tapatalk
Sent from my Nexus 6 using Tapatalk
Here's a crazy thought. We share a lot of internal hardware with the LG G Watch R, right? Would anyone want to try and see if their recovery and or ROMs may work on our watches? I'm not brave enough to do it myself, but I just wanted to throw the idea out there.
http://forum.xda-developers.com/g-watch-r/development
http://forum.xda-developers.com/g-watch-r/development
I guess since I'm already screwed I can try it. I'll fastboot the recovery when I get home from work and see what happens.
Be careful! Even if the recovery boots, I guarantee that the partition maps on the two devices aren't the same! The recovery might think your /system partition is what its writing to, but it reality, that could be ANY other partition. Corruption will follow. Then you run the risk of a true hard brick if any of the bootloaders (aboot, sbl1, sbl2, sbl3) get overwritten.
TL
R: DON'T USE ANOTHER DEVICE'S RECOVERY TO FLASH SOMETHING! (As for ADB access, mtp/adb will 99% be broken anyway, so there probably isn't a point, but you could try and boot the recovery if you want, /shouldn't/ be a harm in booting the recovery to test. If you do decide to test the G Watch R's TWRP, only fastboot boot the recovery, don't flash it.)
Onto helping you recover your device:
Good News: As long as you have fastboot access, you aren't bricked!
Bad News: Someone is going to have to pull their system image for you to restore from.
To do this, and help him, someone who is rooted will need to run:
Su
#Accept KingRoots SU PopUp
dd if=/dev/block/platform/(whatever this folder is on the zenwatch, it varies form device to device)/by-name/system of=/sdcard/system.img
Then just adb pull /sdcard/system.img, and post it up to DropBox of Google Drive.
Then, all you (the person I'm quoting) will need to do is fastboot flash system system.img.
Sideload will only install signed zips.
I'll hold off til somebody can get this for me. I ask that whoever does not to change anything on the system partition beyond what kingroot does before you pull. Once we have the pull we can tinker.Be careful! Even if the recovery boots, I guarantee that the partition maps on the two devices aren't the same! The recovery might think your /system partition is what its writing to, but it reality, that could be ANY other partition. Corruption will follow. Then you run the risk of a true hard brick if any of the bootloaders (aboot, sbl1, sbl2, sbl3) get overwritten.
TL
(As for ADB access, mtp/adb will 99% be broken anyway, so there probably isn't a point, but you could try and boot the recovery if you want, /shouldn't/ be a harm in booting the recovery to test. If you do decide to test the G Watch R's TWRP, only fastboot boot the recovery, don't flash it.)
Onto helping you recover your device:
Good News: As long as you have fastboot access, you aren't bricked!
Bad News: Someone is going to have to pull their system image for you to restore from.
To do this, and help him, someone who is rooted will need to run:
Su
#Accept KingRoots SU PopUp
dd if=/dev/block/platform/(whatever this folder is on the zenwatch, it varies form device to device)/by-name/system of=/sdcard/system.img
Then just adb pull /sdcard/system.img, and post it up to DropBox of Google Drive.
Then, all you (the person I'm quoting) will need to do is fastboot flash system system.img.
Ok, I followed the directions from @npjohnson and was able to extract the system.img file. Here you go:
https://www.dropbox.com/s/5mpbbt6cho74d75/system.img?dl=0
Good luck!!
EDIT - In case anyone needs it, the folder that npjohnson mentioned above is called msm_sdcc.1 on our watches.
Success. Two additional steps were required. I had to unlock the bootloader, which is simply fastboot oem unlock and follow prompts. The second was to run this on the img file: http://forum.xda-developers.com/showthread.php?t=2749797. This is required because the fastboot stores the file in memory before writing. With only 512mb of ram there is not enough room to fit the file in ram without splitting it up. To get it to work use the 512mb argument on the command line.
Great to Hear! Knew it would be simple.
I'm gonna compile a factory image for the ZenWatch, and /attempt/ a TWRP bringup. (no promises)
I will need testers (I don't own a zenwatch). I need some people that have root, and can give me the output of some commands. I am going to start a Telegram chat for ZenWatch development. PM me if you are interested in helping with TWRP/have root and can dump some files.
I saw this post and I was kind of inspired to try to bring up TWRP. I mainly want root to disable some apps, but if I can find some improved touchscreen drivers (my zenwatch has tap to wake issues. it doesn't work everytime, anyone else have this issue? This is even after exchanging the zenwatch once). My concern in doing so is can I guarantee an unroot. These devices are risky as they don't have recovery. Theoretically, wiping the su files with a file manager should unroot it.
Unrooting works fine using the KingRoot app that is installed on the watch. OTA requires certain files to be present to work, but if you just reflash the system.img that was posted earlier and then unroot using KingRoot you should be ok.
Still haven't gotten twrp working yet. I night try later today, but if I can get my custom kernel booting, I'll share it. Its near stock, but should improve performance and battery.
Custom kernel posted. Still looking into TWRP. It looks like I have everything configured right from what I can tell, but it just reboots.
Anybody else looking into TWRP? If not I may take a crack at it but I have no development experience and have never compiled anything before.... So it may take me a while. I have found an xposed mod for disabling low bit ambient but have had no luck manually installing the framework.
I sent a pm, but haven't heard back. Like you, I am not a developer by any stretch, but am happy to test or help where I can.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone