Related
I've noticed some people looking for a working temp root for software versions 2.08.651.2 and .3 (and now 2.17.651.5) so that they can backup all their files with Titanium Backup before the HTC Unlock, here ya be.
I take absolutely no credit for this.
from jcase's post on tacoroot
jcase said:
This vulnerability was independently discovered by Justin Case (http://twitter.com/teamandirc) and Dan Rosenberg (https://twitter.com/#!/djrbliss). Unrevoked and (http://twitter.com/unrevoked) and AlphaRev (https://twitter.com/#!/alpharevx) were also aware of it as well. TacoRoot was written by Justin Case (jcase), with the help of Reid Holland (erishasnobattery).
Click to expand...
Click to collapse
I transcribed the root from tacoroot.sh off jcase's git
The license for tacoroot is included in the zip
The basics for getting local superuser access on the phone I took from a batch file written by Eugene373
Extract all the files.
Make sure wifi is disabled. - Thanks DreamWalkerGuy
Run root.bat
This will require a bit of interaction from the user, namely, rebooting from stock recovery back to system, twice. And you have to unplug the phone toward the end. Just follow all the prompts carefully. When it's says rebooting into recovery, wait for the black screen with the red triangle
This is very unstable. The status bar drop down will probably not work, neither will vibrate.
After your done, you can run unroot.bat to make the phone operational again.
I make no claims about the long terms effects of this, I mean for you to run this, back-up your apps and data, then use the HTCdev Unlock which wipes the phone. And of course if this breaks your phone, sets it on fire, and burns your house to the ground with your dog inside... totally not my fault. Do this at your own risk.
I also personally recommend only using this if you already understand what everything in the batch file is doing.
And make sure you understand what the HTCdev Unlock does to the phone, I'm so tired of people *****ing about some such ROM being broken because they don't know how to flash a ROM with HBOOT 1.50
If you use this, please head to the original threads and give them a thanks, or a donation.
I haven't seen eugene since my T-Mobile Vibrant days, he is a beast of a dev.
I still don't understand what is this for. I have an htc unlocked device with s-on, flashed a custom recovery and then flashed a rooted rom on my phone. My phone is basically fully rooted.
why just temp root?
What we people with hboot1.5 are looking for is S-OFF and not root access.
When you used the HTCdev Unlock it wiped all your data. Some people have been looking for a temp root so they can use an app like Titanium Backup to backup everything, and then restore it after the unlock. It won't do any good if you've already unlocked your phone.
doesnt work on the 2.17 update
Crsdr37 said:
doesnt work on the 2.17 update
Click to expand...
Click to collapse
This is going to require HTCDEV method to unlock the bootloader.
Might be a dumb question but, what would happen if you had temp root then used a program like boot manager?
faugnom1 said:
Might be a dumb question but, what would happen if you had temp root then used a program like boot manager?
Click to expand...
Click to collapse
Nothing much. To make permanent changes to /boot you must have nand unlocked. Otherwise all changes are undone on reboot. And that if you don't get a read only file system error. Sorry.
Crsdr37 said:
doesnt work on the 2.17 update
Click to expand...
Click to collapse
Yup, looks like they patched zergRush
Code:
C:\Users\Administrator\Android\Android-SDK\platform-tools\root>adb shell /data/l
ocal/zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
C:\Users\Administrator\Android\Android-SDK\platform-tools\root>
TacoRoot works for 2.17.651.5 with some tweaking.
Edit: ah, snap, I'm retarded. finishing up now, will update the OP tonight
updated op
2.17
When I reboot into recovery, I get ADB device not found. Works fine when phone is booted to OS. Any ideas?
lyric911 said:
2.17
When I reboot into recovery, I get ADB device not found. Works fine when phone is booted to OS. Any ideas?
Click to expand...
Click to collapse
From what little I know, ADB is only achievable when the phone is powered on and the OS is running.
Recovery is used locally on the phone itself, outside of the OS.
fastboot commands are used to push items outside the recovery, such as the boot.img/splash.img
Maybe, you could access ADB commands while the phone is in fastboot? Not sure.
intrlude said:
From what little I know, ADB is only achievable when the phone is powered on and the OS is running.
Recovery is used locally on the phone itself, outside of the OS.
fastboot commands are used to push items outside the recovery, such as the boot.img/splash.img
Maybe, you could access ADB commands while the phone is in fastboot? Not sure.
Click to expand...
Click to collapse
I should have been more specific I guess. I tried running the root.bat first (due to some things @ work I had to return to stock. Just want to restore some of my items with TI now that I'm stock.)
The first time the batch reboots to recovery, the job just freezes. So I decided I'd try to run the steps manually - then I get the adb device not found.
---------- Post added at 07:24 PM ---------- Previous post was at 06:55 PM ----------
Ignore my posts, I have it working now.
intrlude said:
From what little I know, ADB is only achievable when the phone is powered on and the OS is running.
Recovery is used locally on the phone itself, outside of the OS.
fastboot commands are used to push items outside the recovery, such as the boot.img/splash.img
Maybe, you could access ADB commands while the phone is in fastboot? Not sure.
Click to expand...
Click to collapse
ADB will not work in fastboot usb mode, only fastboot will. ADB will work in any ROM in which the adroid debugging bridge feature is enabled. This is an option you must chose to enable in stock ROMs but is default in most others. ADB can be used to communicate with a recovery image if the image is programmed to allow it, this is the case with custom recoveries like TWRP and CWM. However, the HTC stock recovery image is not configured to allow it. Otherwise I would have programmed the batch file to issue an ADB command to reboot from recovery.
lyric911 said:
I should have been more specific I guess. I tried running the root.bat first (due to some things @ work I had to return to stock. Just want to restore some of my items with TI now that I'm stock.)
The first time the batch reboots to recovery, the job just freezes. So I decided I'd try to run the steps manually - then I get the adb device not found.
---------- Post added at 07:24 PM ---------- Previous post was at 06:55 PM ----------
Ignore my posts, I have it working now.
Click to expand...
Click to collapse
Code:
adb wait-for-device
is a command that pauses the job to allow the user time to manually reboot the phone. When the phone reaches the point in the boot process where it initialized the debugging bridge, ADB allows the batch to continue. The command is usually used to allow users to interact with the phone during scripted processes, or to prevent a script from erroring out while a phone reboots itself during a script. Or to allow nerds to know exactly when there phone is up and linked again... seriously big time and patience saver
lyric911 I'm glad you resolved your issue, so take this not as directed at you, but rather using you as an object lesson to others. By the by, glad you got root
Read the OP, completely.
USSENTERNCC1701E said:
This will require a bit of interaction from the user, namely, rebooting from stock recovery back to system, twice
Click to expand...
Click to collapse
USSENTERNCC1701E said:
I also personally recommend only using this if you already understand what everything in the batch file is doing.
Click to expand...
Click to collapse
from the file said:
please press Volume+, Volume- and Power at the same time, and reboot the system
Click to expand...
Click to collapse
I wasn't chosing to ignore anyone or blow you off by not responding. I'm Army Reserves, this was a drill weekend, so... sorry for the delay However, I'm really not motivated to be kind about questions which I've already given all the answers to.
blizzard1017 said:
I haven't seen eugene since my T-Mobile Vibrant days, he is a beast of a dev.
Click to expand...
Click to collapse
Now he's got his Galaxy S2 over on the T989 forums. It's going to be so beast.
Having Trouble
Hey guys, I'm not getting this to work, so I have a couple questions:
1. am I supposed to extract the files into the Android SDK? Or can they be anywhere?
2. when it gets to "wait for the phone to finish booting, unplug the usb, wait for the led to go out, plug the phone back in" I unplug it and my screen quickly shuts off like the phone dies or something. I plug it back it and it doesn't turn back on. So when it tries to go through all the push commands it fails and claims I have temp root but I don't...
Any ideas will help! Thanks!
jddunkley said:
Hey guys, I'm not getting this to work, so I have a couple questions:
1. am I supposed to extract the files into the Android SDK? Or can they be anywhere?
2. when it gets to "wait for the phone to finish booting, unplug the usb, wait for the led to go out, plug the phone back in" I unplug it and my screen quickly shuts off like the phone dies or something. I plug it back it and it doesn't turn back on. So when it tries to go through all the push commands it fails and claims I have temp root but I don't...
Any ideas will help! Thanks!
Click to expand...
Click to collapse
The zip contains all the adb files necessary for it to run.
When do you unplug the phone? I realize finish booting can be a little arbitrary.
I mean when the Sense interface is functional again, mind you the pull down bar won't work, but basically when you can unlock the screen and Rosie loads it is good to go.
Two things to try.
1. Unplug your phone, if it turns off, pull the battery, turn it back on. When it finishes booting, plug it in.
2. Run Unroot.bat, then try root.bat again.
If those don't work please give me every detail you can.
USSENTERNCC1701E said:
The zip contains all the adb files necessary for it to run.
When do you unplug the phone? I realize finish booting can be a little arbitrary.
I mean when the Sense interface is functional again, mind you the pull down bar won't work, but basically when you can unlock the screen and Rosie loads it is good to go.
Two things to try.
1. Unplug your phone, if it turns off, pull the battery, turn it back on. When it finishes booting, plug it in.
2. Run Unroot.bat, then try root.bat again.
If those don't work please give me every detail you can.
Click to expand...
Click to collapse
I'm unplugging it while it's still locked so that may be the problem. I'm kind of OCD how I run my phone so i didn't think to unlock it first. I'll try it tomorrow and let you know. Thanks for the quick response!
Hey that worked, thanks so much for your help! Just FYI, I'm on the latest OTA 2.17.651.5, so maybe it'll be useful to write the .bat again to say unlock the screen and let Rosie load. Up to you I guess...or they could just read what we've already said haha. Thanks again!
EDIT: Rooting the device is now possible! Download the image here! (Thanks to Justin Case!!)
Alright, you've unlocked your bootloader and you're ready to tear it up with custom roms and other assorted mods. But wait, this is probably a good time to stop. No, I'm not messing with you. Justin Case and I only just acquired root on the G Watch on July 4th, and there's very little that can be done with it at this point. Additionally, there are no superuser managers (eg. Chainfire's SuperSU or Koush's Superuser) available to prevent an app from abusing root for malicious purposes. This situation will surely change over a matter of days, or even hours, but that's where we're at for the moment. I'm not suggesting that people avoid rooting, only that they wait until it can be done a little more safely.
If you're one of the people that wants to get started on building some root apps, or you just need to be on the bleeding edge, you're in the right place. So far, we only have the process worked out for the LG G Watch, but the Samsung Gear Live should be ready fairly soon.
Now, reboot into the bootloader:
adb reboot bootloader
And boot the G Watch using the modified boot image. Warning: Do not flash the boot image, just boot from it!
fastboot boot LGGW-rootboot.img
The watch will play the boot animation for about 2 seconds, then automatically reboot. This time it will boot normally. There will be no outwardly obvious signs it has been rooted, but you can check it by opening a shell over adb and running su.
adb shell
su
If your prompt turns from [email protected] to [email protected], then you've got root on your G Watch. Congratulations!
Click to expand...
Click to collapse
From http://www.androidpolice.com/2014/0...nlock-the-bootloader-and-root-the-lg-g-watch/
Smith7018 said:
So I've started looking into rooting the G Watch and it's not going to be simple. Here are some of my findings:
1. There's a firewall running that blocks any outside communications that aren't sent out by Google-sanctioned apps.
2. The build time is Jun 23, 2014. That means towel root won't work...
3. The device codename is Dory.
4. Many apps will sidled but a lot of them will crash. Once we get root, this could be as simple as moving over libs.
5. Installing the Android keyboard apk allows the user to have a keyboard when necessary! I know this never worked on Glass.
So yeah, we have our work cut out for us. Anyone else looking at this?
(I've attached the build.prop)
Click to expand...
Click to collapse
Hi Smith,
I've ordered a watch but hasn't come yet.
What about accessing a shell via adb? Is this possible?
I certainly assume it is, so I'd bet root would come this way.
Doing some more research...
In theory...
We can unlock the bootloader (fastboot oem unlock)
Flash a recovery (TWRP?)
Flash either a kernel to root the device
OR
Flash a zip which just places an appropriate su binary in place.
Right now we will have to wait for a super user application to be ported to Android Wear....I imagine ChainFire or another will have that before too long.
Stericson said:
Doing some more research...
In theory...
We can unlock the bootloader (fastboot oem unlock)
Flash a recovery (TWRP?)
Flash either a kernel to root the device
OR
Flash a zip which just places an appropriate su binary in place.
Right now we will have to wait for a super user application to be ported to Android Wear....I imagine ChainFire or another will have that before too long.
Click to expand...
Click to collapse
I can confirm that fastboot oem unlock successfully unlocks the boot loader! Also, I can confirm that side loading the Gear Live's stop watch runs on the G Watch. The clock faces install (and are visible in the selection menu) but crash when selected. Interestingly enough, logcat says the app is unable to bind to the Wear home screen... I wonder what could be stopping the legit Android app from running... OEM checks?
If you can in fact unlock the bootloader, rooting is just a matter of waiting for a custom recovery to be ported over to it.
(and being updated to both support such small displays and no buttons at all)
TheManii said:
If you can in fact unlock the bootloader, rooting is just a matter of waiting for a custom recovery to be ported over to it.
(and being updated to both support such small displays and no buttons at all)
Click to expand...
Click to collapse
How would we get into recovery... Seems like a recovery would be best done from a computer.
It hasn't been mentioned on how to do it while it was booting,
but currentl you can enter it by doing
Code:
adb reboot bootloader
The issue is that doing it that way requires an already working rom that also has debugging turned on.
Updated the first post with instructions on how to root the G Watch!
Smith7018 said:
Updated the first post with instructions on how to root the G Watch!
Click to expand...
Click to collapse
But why would you without SuperSU or SuperUser?
I'd wait until it's properly supported unless you're REALLY comfortable with your security.
Sent from Nexus 5 or 7.
It's finally official for AT&T Htc one m8 read the details of the ota here http://www.droid-life.com/2014/08/2...eed&utm_campaign=Feed:+DroidLife+(Droid+Life)
Sent from my custom M8
Yeah got the update just now. Digging around for changes.
Thanks man just got the update. Waiting for reboot now so I can re-root.
They added a file manager.
Before folks start diving into the OTA pool without thinking, remember a couple things:
1) OTA won't install with custom recovery. You need to return to stock recovery or else the OTA will send you into a bootloop trying find a stock recovery that isn't there.
2) Root is usually okay, as is unlocked bootloader (OTA will install) however, if any system files were frozen or removed, they will need to be returned to their "stock" condition otherwise the OTA will not install. Flashing the stock rooted ROM or RUU might be the fastest way to do this.
3) It won't be known whether sunshine and/or firewater s-off methods will work (firewater was already squashed, so its very unlikely to work) unless somebody actually tries it. If sunshine doesn't work, this means you will be stuck s-on until a new exploit is found. So s-off before you OTA if you want to be sure you can get s-off (until folks report this OTA is sunshine-friendly).
4) Back it up before you OTA. Personal data, pics whatever. If its important to you, and you will be sad to lose it, than back it up. Copy to your computer, cloud, whatever, your choice. OTA is not "supposed" to delete any personal data. But you know . . . Murphy's Law. This goes for any major system change, ROM flash, etc.
redpoint73 said:
Before folks start diving into the OTA pool without thinking, remember a couple things:
1) OTA won't install with custom recovery. You need to return to stock recovery or else the OTA will send you into a bootloop trying find a stock recovery that isn't there.
2) Root is usually okay, as is unlocked bootloader (OTA will install) however, if any system files were frozen or removed, they will need to be returned to their "stock" condition otherwise the OTA will not install. Flashing the stock rooted ROM or RUU might be the fastest way to do this.
3) It won't be known whether sunshine and/or firewater s-off methods will work (firewater was already squashed, so its very unlikely to work) unless somebody actually tries it. If sunshine doesn't work, this means you will be stuck s-on until a new exploit is found. So s-off before you OTA if you want to be sure you can get s-off (until folks report this OTA is sunshine-friendly).
4) Back it up before you OTA. Personal data, pics whatever. If its important to you, and you will be sad to lose it, than back it up. Copy to your computer, cloud, whatever, your choice. OTA is not "supposed" to delete any personal data. But you know . . . Murphy's Law. This goes for any major system change, ROM flash, etc.
Click to expand...
Click to collapse
Good write up and reminder to the folks who aren't experienced [emoji2]
Sent from my custom M8
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Anyone have the ota they can post?
Sent from my custom M8
THizzle7XU said:
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Click to expand...
Click to collapse
Always best to do a FDR after an ota it's actually recommend to do that by the manufacturer I know that's a best bet in possibly fixing the issue. Please give that a try and post an update so everyone else can know and thanks for your post
Sent from my custom M8
Sent from my custom M8
The standard root tools work on the 4.4.3 update. To update-
1. Flashed stock recovery
2. Did the OTA Update
3. Flashed TWRP
4. Rooted
I did S-Off a while ago, so I can't say whether this breaks the tools for that. All in all, easy peasy
THizzle7XU said:
Anyone else's battery suddenly draining super quick after the update? My phone is warm to the touch when idle/screen off and I'm getting the error about the PC USB cable not being able to charge the phone fast enough all of a sudden. Something is running like crazy on the phone since the update. Battery Manager says cell standby and Blink Feed are using a lot of battery at the moment.
Click to expand...
Click to collapse
YES! Plummeting like a rock in a swimming pool. Can't even get it to stay level whislt plugged in to a USB port.
Dan
Buddhake said:
YES! It's plummeting like a rock in a swimming pool, I can't even get it to stay level while plugged into a USB port.
Dan
Click to expand...
Click to collapse
Mine is charging fine, as for the drain though I'll have to report back.
My battery is also crap now.
Sent from my HTC One_M8 using XDA Free mobile app
Harshpatil said:
Yeah got the update just now. Digging around for changes.
Click to expand...
Click to collapse
For what it's worth, here's the Changelog-
Android 4.4.3
Security fixes
Wi-Fi fixes
Bluetooth fixes
Mobile network fixes
Camera app update
Gallery (Image Match)
Settings (Power History)
HTC Sync Manager
Boomsound optimization
Extreme Power Saving Mode optimization
Motion Launch optimization
Quick Setting optimization
californiarailroader said:
Mine is charging fine, as for the drain though I'll have to report back.
Click to expand...
Click to collapse
To clarify, I get the charing error when plugged into a PC, which used to charge the phone just fine, even when not in power saver mode. It's still charging with an outlet, albeit probably not as fast as before. I'll try the factory reset even though the message when you are about to update basically says it's an in-place update that won't affect you files.
I'm now having other issues too. Apps won't update. Texts are sending but the apps are saying they are failing to send. The update really hosed this thing.
THizzle7XU said:
To clarify, I get the charing error when plugged into a PC, which used to charge the phone just fine, even when not in power saver mode. It's still charging with an outlet, albeit probably not as fast as before. I'll try the factory reset even though the message when you are about to update basically says it's an in-place update that won't affect you files.
I'm now having other issues too. Apps won't update. Texts are sending but the apps are saying they are failing to send. The update really hosed this thing.
Click to expand...
Click to collapse
Oh, okay, I have mine plugged into a charger. I'm not having any issues with apps not updating or apps saying messages aren't sending, see if the factory reset clears the errors.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
If all else fails, the RUU is up on HTC's web site-
http://www.htc.com/us/support/htc-one-m8-att/news/
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
That will wipe everything though.
Anyone get the ota or ruu downloaded and can upload somewhere?... Would be appreciated...
californiarailroader said:
Oh, okay, I have mine plugged into a charger. I'm not having any issues with apps not updating or apps saying messages aren't sending, see if the factory reset clears the errors.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
If all else fails, the RUU is up on HTC's web site-
http://www.htc.com/us/support/htc-one-m8-att/news/
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe
That will wipe everything though.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Anyone get the ota or ruu downloaded and can upload somewhere?... Would be appreciated...
Click to expand...
Click to collapse
Can't you download it from the link in my post?
Itll take 8+ hrs to download from that link...was asking if anyone had it already and could upload it elsewhere so it wouldnt take so long to start working on it.:silly::silly:
californiarailroader said:
Can't you download it from the link in my post?
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Itll take 8+ hrs to download from that link...was asking if anyone had it already and could upload it elsewhere so it wouldnt take so long to start working on it.:silly::silly:
Click to expand...
Click to collapse
I have it, do you have a preference for sites to download from? I have Mediafire, Drive, Box, Dropbox and One Drive.
I'm uploading it to Google Drive and Microsoft One Drive. It might take just a bit, I have a 120 Mbps download with Comcast, but only 12 Mpbs on the upload.
Edit-What's your email? I can also share it through WeTransfer.
Apparently there is a new update out there.
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
Apoplectic1 said:
Apparently there is a new update out there.
http://www.androidpolice.com/2015/0...2-update-starts-rolling-google-fit-fixes-tow/
Click to expand...
Click to collapse
Yeah I don't want to update. I wish there was a way on Gomer 2.3 I could dismiss it permanently.
alansupra94 said:
Yeah I don't want to update. I wish there was a way on Gomer 2.3 I could dismiss it permanently.
Click to expand...
Click to collapse
I do, but that's because I've been having a lot of bugs lately, from apps force closing upon opening to the watch just plain not wanting to show any notifications.
Unfortunately, since I'm rooted any attempt at updating will abort.
Oh I mean I have the update downloaded and it keeps saying "system update" and I just want it to go away but I don't see a way to remove it.
alansupra94 said:
Oh I mean I have the update downloaded and it keeps saying "system update" and I just want it to go away but I don't see a way to remove it.
Click to expand...
Click to collapse
If you know the path to the OTA file you could delete it from your system through adb and the notification should go away.
I have no idea what that path is though. I've got a post on Q&A asking for where it might be, I'll let you know when I find out.
Apoplectic1 said:
If you know the path to the OTA file you could delete it from your system through adb and the notification should go away.
I have no idea what that path is though. I've got a post on Q&A asking for where it might be, I'll let you know when I find out.
Click to expand...
Click to collapse
Once the OTA is downloaded and Android prompts to install it should be stored in '/cache'.
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Lasiu said:
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58963155&postcount=175
You can adb push it to /cache/, but it will only fail again if you have rooted it.
There are a few guys playing around with the update to see if they can get it to flash, and some trying to see if they can make a bash file to take your watch back to stock in order to take the OTA.
Lasiu said:
Actually i tried installing even though im rooted and my installation was aborted. How can i make it appear again? (I will try go back to stock for a moment from Gohma and after update, flash Gohma again). In "system updates" it's now showing "up to date" but of course it wasnt updated
Click to expand...
Click to collapse
At this point even going back to "stock" will NOT work as the "stock" image has been pre-rooted which breaks the OTA update files. We are all currently waiting for the amazing XDA developers for updated roms / OTA fix capabilities. Until released, even if you have reverted back to "stock" and locked the bootloader etc. if you get the notification it will FAIL to install.
Moguledyouth said:
At this point even going back to "stock" will NOT work as the "stock" image has been pre-rooted which breaks the OTA update files. We are all currently waiting for the amazing XDA developers for updated roms / OTA fix capabilities. Until released, even if you have reverted back to "stock" and locked the bootloader etc. if you get the notification it will FAIL to install.
Click to expand...
Click to collapse
What I meant by going back to stock was by flashing a completely stock image to the watch, not the return to stock option in the LG G Watch Toolkit.
I think I read that Tomsgt is working on a tool that will completely reimage the watch in order to take the OTA.
Here it is: http://forum.xda-developers.com/showpost.php?p=58967268&postcount=257
Apoplectic1 said:
http://forum.xda-developers.com/showpost.php?p=58963155&postcount=175
You can adb push it to /cache/, but it will only fail again if you have rooted it.
There are a few guys playing around with the update to see if they can get it to flash, and some trying to see if they can make a bash file to take your watch back to stock in order to take the OTA.
Click to expand...
Click to collapse
I wanted to go back to stock and install it and then flash Gohma again but i see, that its pointless I have to wait... Actually im REALLY hyped for these improvements. The only thing i hated about 5.0 release were crashes and bugs
Lasiu said:
I wanted to go back to stock and install it and then flash Gohma again but i see, that its pointless I have to wait... Actually im REALLY hyped for these improvements. The only thing i hated about 5.0 release were crashes and bugs
Click to expand...
Click to collapse
You and me both brother.
Apoplectic1 said:
You and me both brother.
Click to expand...
Click to collapse
It seems i wasnt alone with that Most annoying thing was "android wear is not responding. Do you want to close it?" Hell yeah i want to close system, maybe even delete it, huh google? xD
Lasiu said:
It seems i wasnt alone with that Most annoying thing was "android wear is not responding. Do you want to close it?" Hell yeah i want to close system, maybe even delete it, huh google? xD
Click to expand...
Click to collapse
I never had that, mainly just having to try two or three times to open settings because it would always force close a split second after opening, every now and then it's go full retard and tell me that I had to open the Maps app on my phone to use Navigation (REALLY annoying if you're driving), and it would randomly stop getting notifications for no reason until I rebooted it.
Apoplectic1 said:
I never had that, mainly just having to try two or three times to open settings because it would always force close a split second after opening, every now and then it's go full retard and tell me that I had to open the Maps app on my phone to use Navigation (REALLY annoying if you're driving), and it would randomly stop getting notifications for no reason until I rebooted it.
Click to expand...
Click to collapse
It seems that you even experienced worse bugs than I did I hope that this update will fix everything!
Wife's moto 360 updated yesterday but my LG still no update
Got the update but not sure if I want to revert to stock to install it. Anyone varify what it fixes?
Just by the way, considerating that i have no problem with reseting my watch data. What should i do to take this update? Go back to stock? Relock bootloader? Then take ota, and then unlock bootloader and flash gohma again? Or there is no point in this cuz gohma is not 5.0.2 compatible? (though somewhere on rootwiki dev stated that it should work anyway, but also there was statement that ota shouldnt fail, so now im not sure if i can believe in this part xd)
---------- Post added at 12:40 PM ---------- Previous post was at 11:51 AM ----------
Is it possible to flash this ota through TWRP?
Lasiu said:
Just by the way, considerating that i have no problem with reseting my watch data. What should i do to take this update? Go back to stock? Relock bootloader? Then take ota, and then unlock bootloader and flash gohma again? Or there is no point in this cuz gohma is not 5.0.2 compatible? (though somewhere on rootwiki dev stated that it should work anyway, but also there was statement that ota shouldnt fail, so now im not sure if i can believe in this part xd)
---------- Post added at 12:40 PM ---------- Previous post was at 11:51 AM ----------
Is it possible to flash this ota through TWRP?
Click to expand...
Click to collapse
I was trying to figure this out as well. I'd even be OK if I could disable the notification for the update. I'm on an unlocked bootloader and Arter97's kernel, no custom ROM. Seems as though this device is suffering from a lack of devs or or a lack or interest or probably both.
altivoid said:
I was trying to figure this out as well. I'd even be OK if I could disable the notification for the update. I'm on an unlocked bootloader and Arter97's kernel, no custom ROM. Seems as though this device is suffering from a lack of devs or or a lack or interest or probably both.
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/moto-360/development/rom-gohma-2-3-1-11-2015-t2999582/page15
Or this:
"It took me a while to figure out how to edit build.prop to stop the OTA notifications, so I thought I would tell you what worked for me.
adb kill-server
adb start-server
adb pull /system/build.prop build.prop
I then edited the build.prop file and did 2 global replacements:
5.0.1 --> 5.0.2
LWX48P --> LWX49L
a diff between the old a new version gave:
# diff build.prop build.prop.ORG
4c4
< ro.build.id=LWX49L
---
> ro.build.id=LWX48P
10c10
< ro.build.version.release=5.0.2
---
> ro.build.version.release=5.0.1
35,36c35,36
< ro.build.description=platina-user 5.0.2 LWX49L 1627902 release-keys
< ro.build.fingerprint=lge/platina/dory:5.0.2/LWX49L/1627902:user/release-keys
---
> ro.build.description=platina-user 5.0.1 LWX48P 1627902 release-keys
> ro.build.fingerprint=lge/platina/dory:5.0.1/LWX48P/1627902:user/release-keys
Finally, I moved the new files to the watch:
adb push build.prop /sdcard/build.prop
adb push build.prop.ORG /sdcard/build.prop.ORG
adb shell
su
mount -o rw,remount /system
cp /sdcard/build.prop* /system/
exit
exit
adb reboot
This seems to be working for me."
Second one is by haltriumph from rootzwiki (Y) Didnt try them. Decided to go to 5.0.2 and just run script for longer vibrations But it might help you.
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
adogg222 said:
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
Click to expand...
Click to collapse
Since you just got your phone, I would say get to know it on 4.3 first. Lollipop is prettier, but you can do more root things on JB, it runs better, has better battery life, and is an all around better experience, IMO.
Lollipop doesn't have xposed either, if you planned on using that. On top of that, it is missing some core functionality like a startup manager(apps that should be running after a reboot are not!) and has a crippling audio bug.
First thing you have to do for root is email Huawei with your IMEI and SN asking for a bootloader unlock code.
[email protected]
Here is the email I sent them:
Hello, I would like a code to unlock the bootloader on my Huawei Ascend Mate 2, please.
Serial - *********
IMEI - *******
Thank you
Click to expand...
Click to collapse
I then got an unlock code within minutes, so it may or may not be somewhat automated.
TWRP for Mate2
Basically that is a zip file with everything that you need to install TWRP on the Mate2. It has:
SHM's Unified TWRP(v2.8.7.3).
Huawei drivers
ADB/Fastboot
SuperSu(v2.46)
stock 5.1 recovery(just incase)
!Readme file with step by step.
TWRP is needed to install SuperSu, which in turn gives you root.
First, make sure you leave all the files in the same folder. Extract them anywhere, like your desktop. Install the Huawei drivers if you don't already have them installed.
***Put the UPDATE-SuperSU-v2.46.zip on your phone's sdcard somewhere easy to find***
1. Turn off your phone
2. Hold Volume DOWN and Power button for a few seconds. When the screen turns on let go of the power button.
3. Now you should be on the bootloader screen, also known as fastboot.
4. Plug your phone into your PC and wait a minute to make sure any additional drivers are installed and setup.
5. Hold shift and right click an empty space in the folder you downloaded with adb.exe and fastboot.exe and select "Open command window here". A command window should open.
6. In command window type 'fastboot devices' and make sure it says there is a fastboot device. If it doesn't, that means your drivers didn't work. Try unplugging your phone and using another USB port.
7. If it showed a device, its working. Type 'fastboot flash recovery twrp.img'
8. If successful, your phone now has twrp installed
9. While still in fastboot, hold VOLUME UP and the POWER BUTTON for about 8 to 10 seconds, as soon as the screen turns off and then back on again, let both buttons go.
10. In TWRP, hit install and find your UPDATE-SuperSU-v2.46.zip and flash it.
11. Should be rooted and good to go.
12. I included the stock recovery if you ever want/need to go back. Just follow the same steps but replace "twrp.img" with "stock_recovery.img"
Click to expand...
Click to collapse
To lower DPI on our phone, a line will need to be added to the build.prop in the "root/system/" directory.
Add:
Code:
ro.sf.lcd_density=264
to the end of the text on a new line. 264 is the lowest you can go without causing multiple apps to crash.
You can go lower, but you will need Xposed and App settings to change the crashing apps to 264 or above.
Wow, thank you SO much for all of this!! So awesome of you!
adogg222 said:
Wow, thank you SO much for all of this!! So awesome of you!
Click to expand...
Click to collapse
Build prop editor on Google play store can very easily change your dpi. And makes a backup if you want to go back. Better than modding it yourself. And I agree with ark. Hold.off on L until things are fixed. Or until Tom get cm12 up and going.
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
My advice to this self proclaimed "noob" is to read the threads and get more educated before just posting a question that has already been answered with it's own thread. All of the info that Ark posted is in these forums. Please don't get in the habit of asking to be spoon fed. That is certainly frowned upon on XDA.
kimtyson said:
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
Click to expand...
Click to collapse
I had most of it done and copy pasted from another post I already made.
I'm glad someone finally gave simple comprehensive instruction. Unlike someone stated above, it was not that easy to find. I have had my phone for about 1 1/2 months since I returned from vacation in Europe. Ordered it online from Frys while I was there. Anyway, I have searched many times for instructions and couldn't find one thing definitive. Always comments alluding to root, and "does this keep root after update" or "how to get root back" or "this root method didn't work" etc... But never could I find instructions on how to achieve root on stock 4.3 until now. So Thank you sooo much. Now are we sure about the email link you provided above? Because I sent them (Basically copy and pasted ) your email above email twice. About a week ago, and a few days ago. And still no response! Any other suggestions? And shouldn't this be stickied since Root is the most basic of function of what we all want?
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
TheIgster said:
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
Click to expand...
Click to collapse
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
---------- Post added at 11:41 PM ---------- Previous post was at 11:36 PM ----------
TTJB said:
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
Click to expand...
Click to collapse
If you have the code, just boot into fastboot and use the command
Code:
fastboot oem unlock *your code, no asterisks*
ArkAngel06 said:
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
Click to expand...
Click to collapse
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
TheIgster said:
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
Click to expand...
Click to collapse
It's on Google Play or XDA. Try looking for it.
kimtyson said:
It's on Google Play or XDA. Try looking for it.
Click to expand...
Click to collapse
Thanks. Maybe try being less snarky next time?
Just a simple question in a forum that doesn't have a helluva lot of posts anyway.
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Callmebaus said:
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Click to expand...
Click to collapse
Just let it update itself.
Moody66 said:
Just let it update itself.
Click to expand...
Click to collapse
how? selecting normal? instead of twrp?
Callmebaus said:
how? selecting normal? instead of twrp?
Click to expand...
Click to collapse
Normal
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Callmebaus said:
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Click to expand...
Click to collapse
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
xordos said:
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
Click to expand...
Click to collapse
that's the exact post that I used yesterday, haha
all fixed and rooted
thank u