yashsingh1/xdaforums huggingface dataset:
[LG G Watch R] superdave:
This only works coming from KNX01R!

Edit, Camazza has found you can flash the stock 5.0.1 bootloader and sideload the update. See here http://xdaforums.com/g-watch-r/development/manual-ota-update-root-t2969845

Download the update here http://android.clients.google.com/p....signed-lenok-LWX48P-from-KNX01R.149e0c34.zip

1. Root using tonu42's method here http://xdaforums.com/g-watch-r/development/root-root-twrp-r-t2960511

2. After verifying you have root re install the stock recovery for 4.4w.2 from intersectRaven here http://xdaforums.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 (same command used during rooting).

3. Boot in the system and upload the update

adb push 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip /sdcard/update.zip

4. adb shell

5. cp /sdcard/update.zip /cache/update.zip

6. echo 'boot-recovery ' > /cache/recovery/command

7. echo '--update_package=/cache/update.zip' >> /cache/recovery/command

8. reboot recovery

9. Update installs

Thanks to tonu42 for root and intersectRaven for the stock boot.

Use at your own risk.
[LG G Watch R] kashortiexda:
Does it remain rooted after the update ?
[LG G Watch R] nxt:
Would applying the update return the watch to stock? Including upgrading the bootloader and such?

I'm interested in manually updating, but I'd want the watch to be completely stock afterwards.
[LG G Watch R] superdave:
The bootloader and recovery are updated to stock, but, the device has still been oem unlocked so a fastboot oem lock command will need to be issued. This does remove the lock icon and the watch shows as locked, but, I don't know if lg can tell that is has been unlocked at one time. Root is lost after the update and will need to be reapplied.
[LG G Watch R] nxt:
Yup, I knew that part so didn't ask. But I finally got it working (had issues flashing recovery, had to switch usb ports).

All is good now, thanks!

EDIT: Looks like SuperSU is still installed though (won't run)

Everything else seems stock, I even did oem lock/unlock a few times, recovery is stock
[LG G Watch R] kashortiexda:
Between step 4 and 5 you need to type su
[LG G Watch R] tonu42:
You'll lose root and I am working on a fix.
[LG G Watch R] avchr:
Why all this manipulations? Why not use ADB Sideload?
[LG G Watch R] Koopa777:
I don't think LG cares as long as the lock icon is gone. I've already screwed up and sent them a G2 that was on older radios with TWRP installed, and they sent it back factory flashed to the latest firmware (ZVA at the time).

I'd like to know as well, which method is better/safer, this or ADB sideload?
[LG G Watch R] superdave:
Adb does not work in Stock recovery that is why twrp is needed, . I am having the same issue with supersu crashing once booted. I have not had a chance to look at it yet. If you shell in and su before the phone boots su works fine though.
[LG G Watch R] Camazza:
Actually there's a faster and safer way that does not involve rooting.

1) Unlock Bootloader

2) Flash 5.0.1 Stock Recovery

3) Enter recovery and sideload update (it works in the new recovery)

4) Profit
[LG G Watch R] superdave:
Nice, good catch. I'll add that to the first post.
[LG G Watch R] kanzone:
I did the same as following and it's work for me:

recoveryll.bin => 5.0.1 Recovery http://xdaforums.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964

1. adb reboot bootloader

2. fastboot oem unlock

3. fastboot boot recoveryll.bin

4. Select adb sideload then

adb sideload 149e0c34d0ab10d3e356d6301915dcc04552d9db.signed-lenok-LWX48P-from-KNX01R.149e0c34.zip

5. Done

6. Reboot to fastboot

7. fastbook oem lock

5.0.1 Recovery work with adb
[LG G Watch R] b0gd4n:
hey I am trying the same method:

ok, so I unlocked the bootloader, flashed the 5.0.1 recovery, then booted to recovery, selected the adb sideload (the watch now says "Now send the package you want to apply to the device with "adb sideload <filename>"..."

however, in CMD, adb devices is not returning anything. there is no 'new devices connected' sound in windows when removing/replacing the watch from the cradle.

can someone please tell me what am I doing wrong?
[LG G Watch R] kanzone:
adb version

make sure the adb version is > 1.0.32
[LG G Watch R] b0gd4n:
hey, nevermind, I did fastboot flash recovery, not adb boot recovery. I just did that, and I am now uploading the zip....exiting!

thanks!
[LG G Watch R] Koopa777:
So wait, the command to flash recovery is what exactly? I've seen 3 different commands on this very page. Also, we do it from the bootloader screen, right?
[LG G Watch R] cottageboy:
i am unlocked and rooted with twrp and everytime I try and fastboot the boot img. it says "remote image is not a boot image?

what the hell am i doing wrong?

I have also tried to fastboot a new recovery and I get the same thing?
[LG G Watch R] superdave:
Are you trying to restore the stock recovery? If so, you fastboot flash recovery recovery.img on the stock image.
[LG G Watch R] shadow_empire1:
hi,

when I am trying to flash the recovery I get this error:

fastboot flash rcovery recoveryll.img

target reported max download size of 268435456 bytes

sending 'rcovery' (6634 KB)...

OKAY [ 0.312s]

writing 'rcovery'...

FAILED (remote: partition table doesn't exist)

finished. total time: 0.403s

adb version

Android Debug Bridge version 1.0.32

any idea?

do I need to flash the new boot.img before?
[LG G Watch R] superdave:
It should be

fastboot flash recovery recoveryll.img

Also make sure recoveryll.img is in the same directory that your running fastboot from.
[LG G Watch R] shadow_empire1:
lol :)

recovery not rcovery
[LG G Watch R] cottageboy:
I was up and running with 4.4 and was trying to upgrade to 5.0. I was unlocked rooted and twrp installed.

I tried installing over the air and everytime I tried flashing a boot.img or the 5.0 recovery fastboot keep saying that the file was not a boot img.

so then I went back to fastboot oem locked and then unlocked and it wiped y watch...

the only thing I have now is fastboot and twrp....Help?

never mind got it worked out...the file i was linked to was not the correct size, piece of cake once I had the right files.
[LG G Watch R] Moe5508:
Just flash the 4.4 boot image file using fastboot and you should be back in stock 4.4 firmware again...freaked me out yesterday as well..

---------- Post added at 11:47 PM ---------- Previous post was at 11:46 PM ----------

Now trying ADB via Bluetooth...am at stage where am copying the ota file to sdcard...holding thumbs...

https://developer.android.com/training/wearables/apps/bt-debugging.html
[LG G Watch R] BarateaU:
I did the manual update from 4.4w2 to 5.0.1.

I think the clock feels laggier/slower now, and that the pixel quality is lower now.
[LG G Watch R] Moe5508:
I get permission errors trying to use this method...I give up...
[LG G Watch R] gusano38:
Ok, it seems we have to remove the supersu.apk from /system/app in order to get a working su back:

shell into the watch during boot and run su. This should work... you have to be fast.

Once root:

mount -o rw,remount /system

rm -rf /system/app/SuperSU

rm /data/dalvik-cache/profiles/eu.chainfire.supersu

reboot (or ctrl-d and adb reboot)

su should work even after complete boot.
[LG G Watch R] lbrito:
I tried this during boot and got this:

C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb shell

shell@lenok:/ $ su

su

1|shell@lenok:/ $ mount -o rw,remount /system

mount -o rw,remount /system

mount: Permission denied

255|shell@lenok:/ $ mount -o rw,remount /system

mount -o rw,remount /system

mount: Permission denied

I'm on the latest Wear with TWRP installed, but SU crashes when i try to launch. Am I just not doing it fast enough?
[LG G Watch R] gusano38:
You have to adb shell at the very beginning of the booting process, start trying as soon as you see the LG logo. A correct su command should change your shell line to something like:

root@lenok:/
[LG G Watch R] tonu42:
I don't think you have rooted your device. Gotta flash the latest SuperSU via twrp.
[LG G Watch R] lbrito:
That appears to be the case... no root.

I can't launch a root shell, even at boot. I flashed the SuperSU (v1.94) zip via TWRP. I used the UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img for TWRP. SuperSU still crashes when I try to launch it from the watch, also.

What actually achieves root? The .img file with TWRP? or the installation of SuperSu? Doesn't root usually require an exploit? I was rooted before on 4.4W.2, and I would definitely get the root@lenok prompt at shell. But, in retrospect, I don't understand how that was achieved, as we follow the exact same instructions. It's back to wondering what was done to achieve root? And, did I not do something for this 5.0.1 version that I should have?

Thanks for any help figuring this out!
[LG G Watch R] tonu42:
At boot quickly adb shell

su

*root prompt should work*

than

mount -o rw,remount /system /system

cd /System/app/SuperSU

rm SuperSU.apk
[Sony Xperia Miro, Tipo (Dual), J, E] mo30:
please remove this
[XDA Assist] zoquetina:
Hello:

I'm trying to build a tun module for my cellphone android OS. I'm using this guide to learn what I'm doing since it is very complete and well written:

http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source

The problems that I found are a few:

- I can't find the source code of Gingerbread for my Galaxy Fit GT-S5670L.

Here comes confusion one, is the kernel itself the source code that I'm looking for or I need the kernel's source code? I'm confuse.

My cellphone has this kernel: Linux localhost 2.6.35.7-perf-CL700532 #1 PREEMPT Wed Nov 2 01:11:19 kst 2011 armv61 GNU/Linux

So according to this:

http://xdaforums.com/showthread.php?t=1808167

I've gone to all these pages looking for my kernel or kernel's source code which should be Gingerbread:

* http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=gt-s56
* https://www.codeaurora.org/cgit/quic/le/kernel/samsung/
* https://android.googlesource.com/kernel/samsung/

I can't find the source code or kernel's source code for my Samsung Galaxy Fit GT-S5670L because I don't even know what I'm looking for exactly. Should I look for Gingerbread's kernel, or Galaxy Fit GT-S5670L Gingerbread's kernel?

At Samsung code source there isn't even my model of cellphone. (Thank you Samsung, because my phone is old doesn't mean that I will not need support)

Nevertheless I've downloaded the kernel/samsung from Android Google source with git command.

- Confusion two, nothing downloaded, I mean, the folder was created but it was empty.

.Where the 400 MB, more or less, went?!

I'm running Debian on my desktop computer.

- Confusion number three, I got the ADK and NDK tools, have no idea how to install them but I'll search and figure this out.

- Confusion four: the ADB, could someone point me to a good tutorial how to work with this.

- Confusion five: I know because I've bricked my phone several (SEVERAL) times that is not the same: Fit GT-S5670 than Fit GT-S5670L so I can't download or test or work with a kernel that it's not meant to be for my cellphone, that is if there is a kernel or kernel's source code for each model or variant of the Fit cellphones.

Please oh please help me!!

I have been trying to work with this for the last 3 weeks and surf the net for hours and I don't know what to do anymore. I have even contemplate the idea of buy a second-hand phone, though I really like mine.

PS. Sorry for my bad english.

Hope, reeeeeeally hope you guys can help me.
[XDA Assist] Darth:
Hi,

There are many guides and tutorials here, and you can ask for help if you're still stuck,

> Chef Central > Android

Good luck!
[Galaxy Tab 2 Q&A, Help & Troubleshooting] alternativecarb:
Hi guys mi galaxy tab 2 10.1 P5113 got damaged after one OTA update i cannot be turned off and when i try to do that it only ends restarting the device, may i still be capable of rooting or installing a room to a tablet whit this problem? has someone in my situation tried to do the same?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] PanchoPlanet:
If you can go into recovery you can try a factory reset.

Power + volume up.

If you can go into download mode you can flash a rom with Odin.

Power + volume down.

Pp.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] alternativecarb:
Thx I already solve that problem all I have to do was apply the ota update in recovery mode with the cache option and that was all now i am thinking in go ahead and root the device normally.
[Sony Xperia Z Ultra] michael0617:
I used to make roms for the note 2 and am not a newb the amnospherum rom but things have changed a lot can some one just point me to a root that works on 4.4.4 it's the unlocked version I tried towelroot and easyroot and lots of others need root to start work on rom
[Sony Xperia Z Ultra] jnx_r:
Flash rooted boot.img for stock KitKat roms from the root thread via fastboot, after backing up your TA partition.
[Galaxy Tab S Q&A, Help & Troubleshooting] xmilar:
I was just wondering how everyone typically sets up there various pages on the Tab S. I found it kind of strange how by default only a few of the main apps show up on the homescreen and then to access all the other apps you have to click the app button in the bottom right corner. Would it make more sense to move all the apps out of the apps page and put them on the various homepage screens? That way you could flip through everything similar to an ipad and have no need for that app button screen. Is there a specific reason to have the majority of the apps accessed through the app button screen?

Im still pretty new to this so Im still learning and any input or suggestions is greatly appreciated.
[Galaxy Tab S Q&A, Help & Troubleshooting] Kahun:
The homescreen is so you can put shortcuts to your most important apps just like in windows, and the app drawer shows all the apps because some app icons can ruin the look of the homescreen as their icon is ugly :P I would personally keep homescreen for apps you need most and widgets. This is my homescreen for an example I keep it nice and clean got most important at homescreen and access others using app drawer.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
There's a reason why IOS has all apps on each pages. While on Android you can choose what apps you want on your home screen. It's for customization.

Sent from SMT800 using Tapatalk.

-Helper around Tab S forums√

Active Everyday√
[Galaxy Tab S Q&A, Help & Troubleshooting] Kahun:
Exactly that's the beauty of Android, you can make it how you want it unlike Apple's iOS where all you can do is change the wallpaper!
[Galaxy Tab S Q&A, Help & Troubleshooting] xmilar:
Ok I just found out that my newly downloaded apps show up on my home screens but still remain on my apps page if I remove the icon. I am still slowly learning. Thanks for the input.
[Galaxy Tab S Q&A, Help & Troubleshooting] Kahun:
No worries, If your stuck drop me a pm or open a new thread and I'm sure someone will help you.
[Galaxy Tab S Q&A, Help & Troubleshooting] xmilar:
Thanks for the help I appreciate it.
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
Hi,

my HTC One won't boot in any Recovery after the TWRP 2.6.0.1. The Recoverys before are working. The broken recoverys are in the 'Entering Recovery...' Loop, they're showing the splashscreen, give a kind of 2 seconds blackscreen and show the 'Entering Recovery...' Splashscreen again

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-OFF
***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.083s

I tried it with the newest radio, with the oldest radio, with reinstall the ruu, with Lock it and writesecureflag 3. ROM is Stock, because I can't flash another ROM^^

Can you help me pls?
[One (M7) Q&A, Help & Troubleshooting] little123:
try "fastboot erase cache" after flashing recovery
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
I've done it, still in bootloop
[One (M7) Q&A, Help & Troubleshooting] little123:
you have a pretty old firmware running. maybe your old bootloader is your problem. check out vomer´s guide. and watch out, there were some problems when you update such old firmware

and erase your imei from your info ;)
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
I flashed every firmware that i have found, no other results there^^ And thank you :)

btw: I updated my firmware last night

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3942mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
[One (M7) Q&A, Help & Troubleshooting] majmoz:
I think your problem stems from having a hboot 1.57 and firmware that is three versions below it. Follow these steps to get you back to present day.
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
still in recovery bootloop, except with the original recovery.
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3843mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.086s
[One (M7) Q&A, Help & Troubleshooting] majmoz:
Did you install the RUU? It looks like you flashed the firmware OK, were there any issues with the flash?
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
no, there were not any issues and yes I flashed the RUU too^^
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
sorry for the double post. The sh*t that is confusing me is that the twrp 2.6.0.1 is already working, but every recovery that is newer is trolling my phone. Now I'm on Super CID too. Does it have anything to do with the boot.img or something? New log of getvar all: "uuu.img" is 2.8.1.0 "reco.img" is 2.6.0.1

C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-OFF
***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s

C:\adb>fastboot flash recovery uuu.img
target reported max download size of 1514139648 bytes
sending 'recovery' (11864 KB)...
OKAY [ 1.538s]
writing 'recovery'...
OKAY [ 0.932s]
finished. total time: 2.470s

C:\adb>fastboot flash recovery reco.img
target reported max download size of 1514139648 bytes
sending 'recovery' (8014 KB)...
OKAY [ 1.079s]
writing 'recovery'...
OKAY [ 0.784s]
finished. total time: 1.863s
[One (M7) Q&A, Help & Troubleshooting] majmoz:
Did you use the command: fastboot erase cache

After you flashed the recovery? If not the recovery will not take.
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
for sure I've used it
[One (M7) Q&A, Help & Troubleshooting] Selfmade Rulez:
LOL, I think I've found the issue. The Theme doesn't work. I've flashed TWRP with the Venom Theme and it's working.

Edit: Mhm, Venom Theme with TWRP Version 2.6.3.3 is working, 2.6.3.4 is not

Edit2: I'm at the point that I want. I'm on the Rec. Version where I can install todays ROMs (Viper One 7.0.1), Thank You guys
[P3600 Software Upgrading] Arnobreker:
Dear All !

I have successfully upgraded my Trinity to the Dopod 810 Rom. Works fine and has GPS Chip support....but I got a sad surprise: this Rom does only support WDCMA 3G and not UMTS !!! Since I am in Europe, I need either to get back to a UMTS enabled ROM (but I will loose GPS Chip support) or get around the problem with your help in another way. Do you think it is possible to enable the (now) Dopod Trinity to support UMTS ?

Thank you for reply. Please feel free to mail my mailbox arnobreker@libero.it

Arno
[P3600 Software Upgrading] anonimo:
They are the same thing.

PS: It's WCDMA not WDCMA
[P3600 Software Upgrading] tukan:
WCDMA (UMTS)

With WCDMA (UMTS) it acts around a portable radio standard of the third generation (3G), which of operators instead of used the so far, GSM based 2G-Netzwerke to be used can. WCDMA (UMTS) supports higher data transmission rates, which offer customers and enterprises world-wide an improved mobile Konnektivität.

UMTS (universal mobile Telecommunications service) is implemented in Europe, in order to replace GSM/GPRS.

WCDMA (Wideband CDMA) is implemented by operators in the USA and Japan, in order to replace TDMA/GSM/GPRS/PDC.

The terms WCDMA and UMTS can be used synonymously.
[P3600 Software Upgrading] CutePinkSox:
I had some trouble with 3G with Dopod ROM

Perhaps you need to select the band in phone settings, I am in England on Vodafone and use:

Goto phone, Menu, Options, Band and then choose Auto for Network Type and for Band Choose GSM(900+1800)+UMTS(2100)

This gave me back 3G (UMTS) and also works with HSDPA even shows H icon when downloading, very nice speeds indeed sometimes in excess of 1MB.

Hope that helps.
[P3600 Software Upgrading] Arnobreker:
Lieber Tukan, zur Sache: kann mein HTC P3600 Dopod 810, der WCDMA benutzt ins UMTS Netzwerk eines Europaeischen Carriers einloggen oder kann er nur, wie es mir im Moment scheint, GSM/GPRS-Frequenz ausnutzen ?

Dear Tukan, let's go to the point: does my HTC P3600 Dopod D810 that is WCDMA enabled log into a European's Phone Company UMTS network or, as it seems to me now, can it just log into the GSM/GPRS band ?

Thank you/Danke schoen

C
[P3600 Software Upgrading] Arnobreker:
Thank you. But, could you please specify the following:

1) are you using a HTC P3600 (Trinity) ?

2) did you flash it with the Dopod ROM that was once available on XDA Developers, now from Rapidshare ?

Thank you

Arnobreker
[P3600 Software Upgrading] CutePinkSox:
Of course I am !!!

Look at my signature and the bottom of my previous post post and read my post carefully follow the instructions and you should be okay.
[P3600 Software Upgrading] CutePinkSox:
[/I]:

Read the subject of the post please pretty clear which ROM I am using I think but yes is answer anyway.

Look at my signature at the bottom of my previous post quite revealing really ;)

Read again carefully follow the instructions and you should be okay.