Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?
Related
Update:
New Test build to see if it is finally working. I no longer have V500 to test with so if anyone wants to test and give me feedback.
Well it does not work...file removed
This will flash the persist.img from V510 to V500 which might be the key to get wifi and other hardware working. If it does not work and you need to flash old one back let me know. Make sure you back everything and be prepared to do a restore to stock if all else fails. That is the worst that can happen. Easy thing if it does not work is you flash the old persist.img which I will make if needed. I am downloading the TOT file now for v500 if it is needed...
Web Presence:
Twitter
Google+
Thanks to @Demetris for latest tip..
Thanks to @thoughtlesskyle and @Mixinitup4Christ for the system dump and all of their help.
Download HERE - File name V500_to_V510.zip
Awesome,good work!
Sent from my Nexus 7 using Tapatalk
Apart from Wifi and Bluetooth, is it functioning 100% Can it play games, which CM11 can't?
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Im assuming you did a factory reset first?
yes, i did
ekolb123 said:
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Click to expand...
Click to collapse
It should have not touched your recovery. Did you use the right button combo to the get into the factory reset screen and then keep pressing power button to get into TWRP?
Enter recovery mode do full wipe and try again
To enter recovery follow my guide in general
Through some miracle of button combinations i was able to get back into twrp. Back on CM. Thanks guys!
ekolb123 said:
I flashed this using TWRP (was previously on cm11) and the G pad doesnt boot up. I just stay at that beginning screen where there is an LG logo with the text on the top left corner (secure booting error!, Cause device unlock so boot success!). I've had this message since i flash cm11 though.
Any idea what to do, it doesnt look like i can start-up in TWRP.
Click to expand...
Click to collapse
Happened to me too
Sent from my LG-G2 using Tapatalk
I have been trying to get wifi to work for the past few hours but no luck...
AndroidUser00110001 said:
I have been trying to get wifi to work for the past few hours but no luck...
Click to expand...
Click to collapse
Thank you for your awesome work!! I´m sure you´ll get it!:laugh:
somebody else having no sound from the speakers?
I mdofied patch and got 4.4.2 up and running but no wifi or bt yet
Yeah so after I got the basic patch to flash with no boot.img or aboot and other images, I decided to flash the imgs to see if I can covert tablet to GPE. Well folks...DO NOT TRY TO CONVERT!!! You may end up with a nice paper weight. Tablet will not even turn on now
AndroidUser00110001 said:
Yeah so after I got the basic patch to flash with no boot.img or aboot and other images, I decided to flash the imgs to see if I can covert tablet to GPE. Well folks...DO NOT TRY TO CONVERT!!! You may end up with a nice paper weight. Tablet will not even turn on now
Click to expand...
Click to collapse
not even download mode?
thoughtlesskyle said:
not even download mode?
Click to expand...
Click to collapse
Nope and it is showing as QHSUSB_DLOAD in my device manager on PC.
AndroidUser00110001 said:
Nope and it is showing as QHSUSB_DLOAD in my device manager on PC.
Click to expand...
Click to collapse
That's rough bro I'm sorry
Sent from my LG-G2 using Tapatalk
thoughtlesskyle said:
That's rough bro I'm sorry
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
**** happens when you do things you should not...lol. Maybe I can play dumb and return it
AndroidUser00110001 said:
**** happens when you do things you should not...lol. Maybe I can play dumb and return it
Click to expand...
Click to collapse
i've never done something like that.........
Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
fibroman said:
Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
Click to expand...
Click to collapse
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Dees_Troy said:
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Click to expand...
Click to collapse
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
mortis2600 said:
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
Click to expand...
Click to collapse
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
Try running the backup again. If you get an error, adb pull /tmp/recovery.log without rebooting and attach or paste the log to a paste site.
Lokifish Marz said:
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
Click to expand...
Click to collapse
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
Click to expand...
Click to collapse
I quit anyways so no biggie
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Click to expand...
Click to collapse
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Lokifish Marz said:
I quit anyways so no biggie
Click to expand...
Click to collapse
Did you build the stock rom? If so, I meant no offense.
mortis2600 said:
Did you build the stock rom? If so, I meant no offense.
Click to expand...
Click to collapse
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Lokifish Marz said:
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Click to expand...
Click to collapse
I don't have yours installed. Mine is just running completely stock firmware right now.
And it sucks that you're quitting. Your build looked to be the one thing that might make the OS on this thing worth using.
---------- Post added at 08:09 PM ---------- Previous post was at 07:42 PM ----------
kuronosan said:
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If I had the expertise to do so, I would be inclined to do so. Sadly, I'll just have to settle for reporting bugs and making feature requests and being happy to have my device at all.
[SOLVED] backup failed on TWRP
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
nbarm2 said:
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
Click to expand...
Click to collapse
That did the trick!!! Renaming the backup. Thanks.
One final question here: I have been using apps like goomanager to reboot into recovery, but how can you enter TWRP straight from turning the watch on.
Is there a key combo that needs to be held when turning the watch on to get right into TWRP? I tried holding down the bottom right key and that did not work.
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This, but your battery pretty much has to be fully charged or else it will just flash the Omate logo on the screen for a couple seconds and then shut off.
Forgive me if this is the wrong place for this. I followed a few different guides on xda and managed to build a cwm recovery from source. I can fastboot boot into my recovery image and it works fine, makes backups etc. But when i fastboot flash the .img and reboot into recovery it boots to a black screen. Im just not sure where to start in diagnosing the issue. I managed to get a few other issued solved like DTB and malformed fstab, but im stumped here. It might be something silly i did or didnt do. This is for a new device the lg ls740. I can post the recovery.img or the split files from unmkbootimg it it helps, thanks!
I'm having the same issue
Sent from my LGLS740 using XDA Free mobile app
notreal456789 said:
I'm having the same issue
Sent from my LGLS740 using XDA Free mobile app
Click to expand...
Click to collapse
because you were using my recovery, the recovery that doesnt work right! Im asking here for help on what i need to do differently before i compile it.
Ya I figured that out lol ; ) and sorry..I think?I mean, didn't mean to upset you?
Sent from my LGLS740 using XDA Free mobile app
danhalen1 said:
Forgive me if this is the wrong place for this. I followed a few different guides on xda and managed to build a cwm recovery from source. I can fastboot boot into my recovery image and it works fine, makes backups etc. But when i fastboot flash the .img and reboot into recovery it boots to a black screen. Im just not sure where to start in diagnosing the issue. I managed to get a few other issued solved like DTB and malformed fstab, but im stumped here. It might be something silly i did or didnt do. This is for a new device the lg ls740. I can post the recovery.img or the split files from unmkbootimg it it helps, thanks!
Click to expand...
Click to collapse
I think it's because of a brightness problem. You need to enable brightness permanently. For enabling it you need to follow these steps:
1.Unpack your builded recovery(with kitchen)
2.Place "qrdsys.sh" in /ramdisk/sbin/<here>
3.Add the following line into init.rc:
"service qrdtrd /sbin/sh /sbin/qrdsys.sh
oneshot"
4.Repack and flash
Source I got this from: https://github.com/dhinesh77/device_micromax_a57
Get the "qrdsys.sh" file from here: https://github.com/dhinesh77/device_micromax_a57/blob/cm-10.1/recovery/qrdsys.sh
Thanks to dhinesh77 :good:
Try it, if it don't work, report it to me.
GeekyDroid said:
I think it's because of a brightness problem. You need to enable brightness permanently. For enabling it you need to follow these steps:
1.Unpack your builded recovery(with kitchen)
2.Place "qrdsys.sh" in /ramdisk/sbin/<here>
3.Add the following line into init.rc:
"service qrdtrd /sbin/sh /sbin/qrdsys.sh
oneshot"
4.Repack and flash
Source I got this from: https://github.com/dhinesh77/device_micromax_a57
Get the "qrdsys.sh" file from here: https://github.com/dhinesh77/device_micromax_a57/blob/cm-10.1/recovery/qrdsys.sh
Thanks to dhinesh77 :good:
Try it, if it don't work, report it to me.
Click to expand...
Click to collapse
Thanks for the reply, i just tried it here this morning and i still have the same black screen result. Thanks for your help!
danhalen1 said:
Thanks for the reply, i just tried it here this morning and i still have the same black screen result. Thanks for your help!
Click to expand...
Click to collapse
No problem. Actually I thought it would fix it!
Well, what about you try to monitor your screen through ADB to your desktop?
If the recovery works, but has graphical issues, it should show there. If not, it's actually not booting or either not working.
Maby? We haveto zero out the recovery?? Just like the laf partition to access fastboot?
Sent from my LGLS740 using XDA Free mobile app
Welcome to Twrp 3.0.0.0 for our Zenwatch 2's
This release I was able to flash the recovery, flash the supersu zip, and flash some others, so far I have not encountered our wild soft brick madness.
Thanks to @acbka for showing me how to get into log files, essentially helping me figure out why the partitions were not mounting correctly when I compiled and recompiled.
Here is TWRP 3.0.0.0
Directions:
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot flash recovery twrp3.img
OR load up your tethered twrp and flash the image under that.
Hope you guys enjoy! So far I have not encountered soft bricks so it should be safe and sound
thank you, will test now
---------- Post added at 09:21 PM ---------- Previous post was at 09:01 PM ----------
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
okaay3D said:
Thank you very much! I hope this will be one of the first steps into advanced development for our watches! Does this work for WI502Q? But what's a benefit of rooting this watch?
Click to expand...
Click to collapse
That im not sure, it might, wouldnt hurt to fastboot boot it and see if itll start twrp. I have the 501
Root will go with modifying the Momentum kernel so you wont have much lag on the watch, and any other root modifications that can go with it, like maybe xposed?
Next step in development is fixing twrp so it can be flashed, then maybe modifying the wear os? Or maybe porting some stuff
T10NAZ said:
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting
Click to expand...
Click to collapse
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
matze19999 said:
Works perfectly, my zenwatch 2 is now rooted
thank you, you`re amazing
Click to expand...
Click to collapse
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Awesome! Got supersu flashed and was able to use Advanced Settings to disable some of the built-in bloatware apps. I'll have to try out the kernel but I'm currently at work and don't want to spend all day messing around with my watch (well... I want to, but I like not getting fired).
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I do have the 5.0.1 wear downloaded and installed! And as far as i know, Its working ok
okaay3D said:
I want to test it. But how do I backup my watch and restore it to get updates? And is there something like a KNOX-counter to tell whether the device was modified?
Click to expand...
Click to collapse
You can tell twrp to preserve the system protection, back every single thing up that you can in the twrp option, push that backup to your computer, and then you can disable system protection. twrp itself wont do anything, however playing with options will modify the watch.
OR you can fastboot pull things off the watch, the system.img and boot.img yourself, in case the ones uploaded in my general thread didnt have the protection enabled.
If you want to hang tight until 1.4 comes out, that can be a good thing too
And im not sure if there is something like that on the watch. I have not seen anything about it before
My attempt was a failure on my WI502Q. I got the following messages. And, OP, how do you pull system.img from a device through fastboot? I thought you needed root permission to do that through adb.
"
C:\adb\zw2>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.834s
"
Thanks for this! I was losing hope on any development for this watch but now we have the most crucial component to modifying anything on android, a custom recovery. Going to perform a backup, root and flash your custom kernel you kindly released as well!
T10NAZ said:
Hello everyone, I have been working hard last night to make twrp run on our watches, and this I think is a good representation on what itll be like with actual development going on
As far as I understand people are able to get backups of their watch in order to preserve OTA's before rooting, and I was able to flash some zips and kernels successfully, and I fixed the UI to look better and actually usable on the watch
Also, I was able to flash this puppy, and I got android wear to boot with it flashed, however most of the time, it goes haywire and only boots into recovery. Same thing applies, this shall be a Tethered recovery only until I know why its going crazy.
As always, problems can arise on your watch, so be careful!
read the entire instructions, This is a known way to get system protection off, and to flash zips/kernels when need be. Do not flash please.
Here is the link to the updated twrp
Get into fastboot, either by enabling adb by enabling developer options going into settings, about, and taping the Build number 8 times, and going back, down to developer options and enable ADB Debugging.
Then you can type into your CMD or terminal adb reboot-bootloader or by powering down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
continue to boot the recovery by typing fastboot boot recovery.img like the other one.
I also have a kernel underway if people would like to try it out and test it in the next couple days
Click to expand...
Click to collapse
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
yash92duster said:
What are the Advantages of installing TWRP in Zenwatch 2 WI501Q..???
does it allow to uninstall stock apps..!!
Click to expand...
Click to collapse
it could lead to that, yea, since this is the only root method basically, it adds a few extra steps to do it
can we root with regular supersu .zip, or do we need a special build for wear devices?
slothdabski said:
can we root with regular supersu .zip, or do we need a special build for wear devices?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view?usp=sharing there ya go. dunno if the regular supersu works. havent tried that out. this one does. and alrdy has a busybox installer wear app included which u need anyway sooner or later.
there is no supersu manager app in it though like on phones. apps requiring root just have it. tested advanced settings so far for disabling built-in stuff and a reboot option. but maybe there is a supersu-wear.apk somewhere?
not my link. taken from here: http://forum.xda-developers.com/showpost.php?p=65759835&postcount=14 he took it from the G watch R forums iirc.
zenwatch2
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
mehdi.ahmadi said:
hi dear freind
after the flash twrp recovery
after the wipe
my watch was brick and hang on asus logo
help me plase
Click to expand...
Click to collapse
Let me know the steps you took from when you downloaded it, to when it sits on the asus logo, and do you have the 502 or the 501 watch?
mehdi.ahmadi said:
after the flash twrp recovery
Click to expand...
Click to collapse
guess that means he flashed it. now his watch is bricked. not that it hasent been mentioned NOT to flash it just fastboot boot ...
flash the stock images via fastboot or tethered (NOT flashed) twrp and you should get your watch working again.
4RK4N said:
what did u flash to get root? the one twrp offers (if this one does)? the one xda tv featured for 5.0.1 wear http://www.xda-developers.com/root-android-wear-5-0-1-xdatv/ ? or just the newest non-systemless supersu.zip used for phones? with a phone i would just flash away anything. but im a bit hestitant on the watch yet. couldnt find clear info yet.
Click to expand...
Click to collapse
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
matze19999 said:
I flashed this zip file
https://drive.google.com/file/d/0B3zB2zRyWlLBNmhwSmNBUEp1SVU/view
Click to expand...
Click to collapse
found it about 2 weeks ago somewhere here on xda and alrdy linked it to several ppl here in the thread.
but thx
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Thank you so much!! Very happy to finally have write access to /system! Nice work!
I'm just hoping we get some ROM support on this phone. I always run gappless. Lol.
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Yo just curious can you explain to me how you built this i cant seem to get it build rigjt or send me your source files
svoc said:
So I have a twrp that will boot but has no touch on mouse support right now I only boot it do not install it it will boot loop your device use fastboot boot recovery.img
Click to expand...
Click to collapse
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
arkansawdave74 said:
Sorry, but I have to ask. You say it's working but if it has no touch then how does it work? Command line?
Click to expand...
Click to collapse
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Here is a updated TWRP with everything working use at your own risk
treesus said:
would be presumably by way of a USB connected hub to attach a mouse and maybe a keyboard too, though there is another version of TWRP 3.5 which I've just gotten working on my xt2114-7 running 11. I also used it to flash magisk which appears installed but has yet to prompt me to give root perms to anything.... which seems odd. hmm.... anyway there's another TWRP in these forums that may do the trick https://forum.xda-developers.com/t/...o-android-11-based-updated-11-4-2021.4354855/ as far as I can tell this is only working on 11 currently and seems a bit touchy about the touchscreen driver when it first boots, but I did a fastboot flash magisk_boot.img and then did a fastboot boot into the TWRP, and from there I actually flashed the TWRP file from within the booted TWRP environment. That sounded more complicated than it is...
Click to expand...
Click to collapse
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
I now have the phone I meant to get in the first place, the Moto G9 Power with an official TWRP build.
arkansawdave74 said:
Oh. My bad, man. I had misread the dude's typo. It says, "no touch on mouse support," and I thought he'd meant to say "or," but I later realized that he'd meant to say "only." It apparently has mouse support.I broke my Power 2021 right after I got it, but I did get it rooted using this twrp in an adb shell to pull my kernel because the kernels in the lolinet firmwares, after patching, caused the 2021 to lose touch functionality completely. But, even though it's the same damned kernel, when you pull it with:
"adb shell"
"twrp backup B"
it will make a backup in the usual spot in internal storage (/sdcard/TWRP). Go in there and find the file and rename it to boot.img (or something like twrpdboot.img to keep it from being confused with the other boot images) and if you patch that one with magisk it will boot fine and your touch screen will work. The only reason I haven't told others about that is because of two reasons. For one, everyone's using some windows program that sources its downloads from a different spot than lolinet, and those kerels, I assume, work ( I wouldn't touch windows with my worst enemies computer, myself, so I had to find another way using Linux). And for two, I broke my Moto G power 2021 just a day after I got it. This TWRP in here won't work with all these commands but some of them do work. Backup sure does.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
Click to expand...
Click to collapse
I used lolinet files on my 2021, no touch issues, but mine uses the Ilitek display. But since you seem to be familiar with Linux as you put it, you could unpack and repack yours and ramdisk, having pulled files like I outline in https://ilitekforum.xda-developers....ased-updated-11-4-2021.4354855/#post-85885471, so you may be able to make your TWRP have touch, unless you meant damaged so much that's broken too.
I posted a fixed twrp file for you all
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Onoitsu2 said:
unless you meant damaged so much that's broken too.
Click to expand...
Click to collapse
It's out of there. I'lI maybe get another one though because I really want to try Visible Wireless Service and this G9 Power doesn't have esim capability. True unlimited with no hotspot cap for $40/month. Maybe too good to be true, but I gotta check it out. Until then, Check ya laters borneo dudes.
treesus said:
which version of TWRP is this one? Can I find a changelog to check out somewhere?
Click to expand...
Click to collapse
I dont make change logs this is twrp 3.4
svoc said:
I dont make change logs this is twrp 3.4
Click to expand...
Click to collapse
I build for myself then when it working I give it away I do t keep track of what I do to get it working I just get it working then give it out sorry I'm working on LineageOS right now I got the device trees working last night I got my first build working but still a lot to test out before release
Excited to follow development for the Borneo. Thank you.
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
svoc said:
If you have any features you would like let me know when I build a rock I make it 100% Google stock no anything extra so let me know if you want any fluff
Click to expand...
Click to collapse
No fluff - just stock. thanks for your hard work.
svoc said:
I posted a fixed twrp file for you all
Click to expand...
Click to collapse
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
4xc7xy said:
Is there a way to get this working on the G Power (2021) model XT2117-4 (OS is android 11)? I tried running fastboot boot twrp_fixed.img and it just sent me back to the boot loader. Also if its important for me to post my touchscreen stuff, here it is.
Code:
borneo:/ $ cd /sys/class/touchscreen
borneo:/sys/class/touchscreen $ ls
ft8009
Click to expand...
Click to collapse
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Onoitsu2 said:
Did you 'fastboot reboot bootloader' first before the boot attempt? You need be in the Fastbootd, not the normal Fastboot screen. I know it's odd, but that's how I got mine. Because apparently fastboot itself won't boot even my TWRP but fastbootd does. The device being an A/B device is the only reason to ever use fastboot (not fastbootd), to flash the sparsed system image is my understanding.
Click to expand...
Click to collapse
No I did not, let me try that right now and then do a follow up reply to tell you how it goes