LeeDrOiD R Urbane Port V3.1 - Wear 1.3 - September 14th- Stable
- Thread starter LeeDroid
- Start date
@jimbobtexas were you able to rebuild your /data at least (TWRP: Wipe / Format Data / Yes) ?
I'm seeing if I can figure from TWRP's source how that was done and try to extrapolate to /cache. Apparently it is all a fuse thing.
I'm seeing if I can figure from TWRP's source how that was done and try to extrapolate to /cache. Apparently it is all a fuse thing.
Really sorry guys, it worked for me...
In TWRP, what about the partition repair option.
Tick Cache, then choose repair, and choose ext4
In TWRP, what about the partition repair option.
Tick Cache, then choose repair, and choose ext4
Yes, I was, thanks to your suggestion. I'm in the exact same spot you are.
Ok, got cache restored too. After /data is back, just swipe "factory reset". That'll do it.
Now rebooting to see what happens...
Now rebooting to see what happens...
Sorry guys, been spending time with the wife.. the partitions simply needed formatting in twrp... Sounds like you nailed it
Ok, reboot was a no-go. Does anyone know where I can find a zip of 5.1.1 (W110, not Urbane!) that I can flash from TWRP ? I would prefer not to play with fastboot at this time....
http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
I'm back up and running. Thanks!
I believe there is a thread with a link containing all stock system images... Flashing via fastboot is the way forward if you want to restore the stock setup
[/COLOR]
You did but apparently /data had to be solved before /cache was - hope you didn't feel blamed, thanks for the help!!Didn't I say that.....
Sorry for the mess up, guys.
Can't believe in this day and age we still have bootloaders with poor code that corrupt standard devices.
Reminds of the Moto Xoom that did the same!
I still stand by you should use this ROM in a as-new state. But perhaps just do the factory reset in TWRP...
Can't believe in this day and age we still have bootloaders with poor code that corrupt standard devices.
Reminds of the Moto Xoom that did the same!
I still stand by you should use this ROM in a as-new state. But perhaps just do the factory reset in TWRP...
Not sure what you mean by the "in a as-new state".Sorry for the mess up, guys.
Can't believe in this day and age we still have bootloaders with poor code that corrupt standard devices.
Reminds of the Moto Xoom that did the same!
I still stand by you should use this ROM in a as-new state. But perhaps just do the factory reset in TWRP...
Not a dirty flash.
Factory reset. As if the watch is booting for the first time.
A lot of the previous problems in the thread seem to be people just flashing system and rebooting with an already setup watch but a mishmash of ROM data making it go screwy.
Ah, thanks. That makes sense.
While I happen to have some attention here, any observations regarding the battery life with this ROM ?
While I happen to have some attention here, any observations regarding the battery life with this ROM ?
So far (though only a few hours and been trying to help you with lots of reboots etc.!) it's on par with standard GWR with wifi mod and dual core kernel...
The sources for the 5.1.1 kernel have just dropped, so there will be a new custom kernel any hour now, so I suspect with that, and reverting to single core, it'll be even better.
All in all, better than stock. And faster!
How's the battery life with that port?
Is pulse working fine?
Are there all new watchfaces too?
Sent from my HTC One using Tapatalk
Is pulse working fine?
Are there all new watchfaces too?
Sent from my HTC One using Tapatalk
New posts
-
[HOW TO] Fixing a hardbricked Yuphoria (lettuce) using an external SD card- Latest: Rajnikanth14112
-
-
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