Database Users

S3 Now available in clockwork recovery

The S3 has been added to supported devices​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

anyone else having issues flashing CWM Touch from recovery? I can't get it to take even though it successfully completes.

contradude said:
anyone else having issues flashing CWM Touch from recovery? I can't get it to take even though it successfully completes.
Click to expand...
Click to collapse
You downloaded the d2spr version from download.clockworkmod.com?
Sent from my SPH-L710 using Tapatalk 2

:O i know two of those phones!
did the cwm on the connect and lucid

shabbypenguin said:
:O i know two of those phones!
did the cwm on the connect and lucid
Click to expand...
Click to collapse
When are we gonna get an update on the prevail?
Sent from my SPH-L710 using xda premium

Can't backup ROM, "sd marker not found"
Any ideas?

It said that to me when trying to use the app to backup but I did it manualy and it worked fine.

Any advantage/disadvantage of flashing the new CWM through ROM Manager, or manually through ODIN? Btw, do you flash this through ODIN or (old) CWM since this is a .img file?

Just so ppl know, you can find all CWM Recoveries here:
http://download.clockworkmod.com/recoveries/
Our device is d2spr
Towards the bottom you'll find the CWM Touch Recovery, I flashed the img using Mobile Odin and it's working fine
Sent from my SPH-L710 using Tapatalk 2

fergie716 said:
Just so ppl know, you can find all CWM Recoveries here:
http://download.clockworkmod.com/recoveries/
Our device is d2spr
Towards the bottom you'll find the CWM Touch Recovery, I flashed the img using Mobile Odin and it's working fine
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ah... flashed it through mobile ODIN... thanks for the tip, Fergie!

MinimalistChris said:
Ah... flashed it through mobile ODIN... thanks for the tip, Fergie!
Click to expand...
Click to collapse
No problem!
Another tip, backups made with the older CWM recovery (the unofficial one, the one you probably flashed after rooting initially), those older backups may not be compatible with the newer, official versions. I'm using the latest CWM Touch 5.8.4.6 and it seems to backup system and data differently
Sent from my SPH-L710 using Tapatalk 2

Can't seem to get the .img to flash when using mobile odin... I tried to click on Recovery then find the file, but it doesn't list the file, only the folders I have available. Am I doing something wrong?

klarthur said:
Can't seem to get the .img to flash when using mobile odin... I tried to click on Recovery then find the file, but it doesn't list the file, only the folders I have available. Am I doing something wrong?
Click to expand...
Click to collapse
If you downloaded the CWM img file rename it to just "recovery.img" then put it on the root of your SD
Open up Mobile Odin, Select "Open File", then select your recovery.img (I put it on Internal Storage)
After you select your recovery.img, before you select Flash Firmware, it should list the recovery.img in the recovery slot
Then you should be all set. Select Flash Firmware and after it flashes you should automatically be rebooted into recovery (I suggest making a backup ASAP just to be safe)

Phew... Glad to see there is a fix... I thought I was losing my freaking mind when I tried backup of my rom....
EDIT: something is borked...not right ...frustrated user...mad.mad.mad :crying::crying::crying:
Sent from my SPH-L710 using xda premium

Mobile Odin didn't help me much... could I install the touch recovery.img through adb? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 ?

wpjessie said:
Mobile Odin didn't help me much... could I install the touch recovery.img through adb? dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 ?
Click to expand...
Click to collapse
The mobile Odin way did not work for me. After I flashed the img file, rebooted and tried to do a backup using Clockwork mod, the phone rebooted and gave me the same errors as posted above! ???Help???
EDIT: Duplicated this same error/issue on my second GS3...so it is definitely CWM related...also..cannot "see" or view the backups on the phone via the Rom Manager app either..very frustrating...hope those smarter than me can fix...I am willing to assist in any way... thanks

I flashed the new touch cwm in the unofficial recovery and it works, but doesn't stick, reverts back to the old recovery after a reboot???
Sent from my SPH-L710 using xda premium

This may be a dumb question but, couldn't we just install ROM Manager and flash the CWM recovery with it, like I used to do on my EVO 4G?

w8setter said:
I flashed the new touch cwm in the unofficial recovery and it works, but doesn't stick, reverts back to the old recovery after a reboot???
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
the team epic guys has set us up with a recovery that would stick cause the first samsung ota automatically reverted to their own recovery instead of cwm. maybe this issue is related. it just keeps overwriting what you flashed thinking that it's a bad (Samsung) recovery. don't know for sure as i haven't tried it yet.

gtpdjw said:
It said that to me when trying to use the app to backup but I did it manualy and it worked fine.
Click to expand...
Click to collapse
that defeats the purpose of this new, "supported" recovery as i would like the option to flash things and manage backups via rom manager.
jf11time said:
This may be a dumb question but, couldn't we just install ROM Manager and flash the CWM recovery with it, like I used to do on my EVO 4G?
Click to expand...
Click to collapse
thats what i did.
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
mine sticks, just rebooted 2 times, and after booting into recovery again still version 5.8.4.6 which is latest.
installed via rom manager
about to try touch

4.2.2 update

Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4

Yes.
http://forum.xda-developers.com/showthread.php?t=2144330
There's a long thread on 4.2.2 already.

What about the bootloader? Will it relock it? Or is it left alone?
Sent from my Nexus 4

Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4

Slender Troll said:
Also, I was just reading through that thread and it said if you have SuperSU that it won't unroot. Is that true? Or do I need to use ota rootkeeper? I know that thread may have the answers I'm looking for, but I'm too tired to read through it all. I ask all these questions because I have no computer to reroot and reunlock the bootloader with.
Sent from my Nexus 4
Click to expand...
Click to collapse
Afaik it won't relock your bootloader.
Sent from my HTC One X

I flashed back to stock.
Flashed the update
Flashed a SuperSU.zip
Rebooted
Then reinstalled twrp through goo.Im app
When I flashed update I lost root and recovery
And all is good again
Sent from my Nexus 7 using XDA Premium HD app

Slender Troll said:
Will the 4.2.2 OTA for my Nexus 7 take away root access?
Sent from my Nexus 4
Click to expand...
Click to collapse
I was on JOP40D (4.2.1) Stock, rooted, with CWM 6.0.2.3. I downloaded this OTA file http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip from the link in the other 4.2.2 thread (http://forum.xda-developers.com/showthread.php?t=2144330)
I booted into CWM, and flashed the downloaded ZIP file as normal
When I told CWM to reboot, CWM warned me the update would flash stock Recovery and do I want to STOP this from happening and I said YES.
It then said I had lost root, and do I want to restore root, and I said YES.
It then booted into Android and continued with the upgrade.
I now have 4.2.2 stock installed (JDQ39), and still have root and custom recovery, and an unlocked bootloader.
From what I have read, if you 'sideload' the update using ADB, or do a normal OTA update, you will lose root and custom recovery. However, using the steps above will keep root and recovery for you

What if I'm using TWRP?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
im in the same boat,
im on 4.1.2 twrp what do i need to do to get to 4.2.2? just use that ota root keeper?

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.

Benjoy Ericsson said:
TWRP is same to CMW, but for sure you should install Voodoo OTA Rootkeeper, backup SU then flash the 4.2.2 update.zip. Finally, open Voodoo and restore the backup SU --> your Root is kept. Just in case you need to verify root will work or not. Go to Play Store, install Root Checker (joeykrim) and check your root permisson.
I updated my N7 to 4.2.2 without removing root by these steps above.
Click to expand...
Click to collapse
Can I do this without a computer?
Sent from my Nexus 4

Slender Troll said:
Can I do this without a computer?
Sent from my Nexus 4
Click to expand...
Click to collapse
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.

Benjoy Ericsson said:
Yes, if you can put your 4.2.2 OTA update.zip in your N7 Internal Storage.
Maybe by downloading the zip through wifi connect.
Click to expand...
Click to collapse
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4

Slender Troll said:
What if I'm using TWRP?
Sent from my Nexus 4
Click to expand...
Click to collapse
I don't think it matters...
I used TWRP to flash the update.
Afterwards, the bootloader was still unlocked... but had been updated from 4.13 to 4.18.
And I had to reflash TWRP as the update had wiped it out, effectively resetting recovery back to Googles default recovery.
Rgrds,
Ged.

Slender Troll said:
Wi-Fi connect? And where do I put it once I have it?
Sent from my Nexus 4
Click to expand...
Click to collapse
This is OTA link for N7 Wifi Only.
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.

Benjoy Ericsson said:
Connect to wifi, download the 4.2.2 update.zip to your internal storage from this link http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip (anywhere is ok, be sure to remember the path). Reboot your N7 to recovery mod (TWRP), choose install and browse to where you put your zip in internal storage.
Click to expand...
Click to collapse
Just to clarify, I can leave it in the download folder?
Sent from my Nexus 4

So I'm in recovery and at the part where it gives me the option to flash. Is there anything I need to do or back up before I flash the OTA so that I don't lose root?
Sent from my Nexus 4

Success!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 7 using Tapatalk HD

Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.

dalanik said:
Just downloaded the OTA zip, went to recovery and tried "install" (both checkmarks to check md5 and zip off) and got FAILED! The device booted normally afterwards. I copied file via USB cable in standard media mode... what am I doing wrong? On 4.2.1, stock, rooted, 16gb Wifi only N7.
Click to expand...
Click to collapse
Try downloading it using Wi-Fi from the link above, and then back everything up. what recovery are you using? I left the zip in the download folder, so I wouldn't lose it.
Sent from my Nexus 4

I think my phone died

Hello xda,
I got à big problem. Let me start from the beginning. I was using latest pacman rom nightly. In the forum they said hat I need to install color fixed zip to install so I can use Franco kernel. After that this happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. So I tripped a bit. I did factory reset and I restored to an old bad backup where my keyboard was broken, but it worked aigain. Then I resetted aigain and updated to latest rom. Then keyboard still broken and other stuff, so I thought if I format system files and reinstall rom it will work, but then it went wrong I also deleted my rom by accident and now when I boot it's stuck on google screen and in cwm it says when I want to reboot: root acces is missing, click yes - root device (/system/xbin/su). Has my phone died?? Other ways I have big problem. Could anyone please help me? Thanks in advance guys.

Your options:
1. Boot into cwm, use adb to push a ROM to the phone, then flash it.
2. Flash the factory images.
Sent using xda-developers app

Chromium_ said:
Your options:
1. Boot into cwm, use adb to push a ROM to the phone, then flash it.
2. Flash the factory images.
Sent using xda-developers app
Click to expand...
Click to collapse
Could you be more specefic please. I'm still a noob. Where can I use adb? And If I flash rom isn't it the same as factory images?

ion_elgreco said:
Could you be more specefic please. I'm still a noob. Where can I use adb? And If I flash rom isn't it the same as factory images?
Click to expand...
Click to collapse
1.
-Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
-Then download a ROM and out it on your desktop. Rename it to ROM.zip
-Put the phone into cwm, and open a command prompt
-Type "adb devices" to see if the phone is recognized. Then type "cd Desktop", and finally "adb push ROM.zip /sdcard/"
-Wait till its done, then on your phone browse to the ROM and flash it.
2. To flash factory images: http://forum.xda-developers.com/showthread.php?t=2010312
Flashing the factory images is more thorough than simply flashing a ROM. You will lose pretty Mich everything including your custom recovery, so your phone will be like it was when in came out of the factory.
Sent using xda-developers app

Chromium_ said:
1.
-Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
-Then download a ROM and out it on your desktop. Rename it to ROM.zip
-Put the phone into cwm, and open a command prompt
-Type "adb devices" to see if the phone is recognized. Then type "cd Desktop", and finally "adb push ROM.zip /sdcard/"
-Wait till its done, then on your phone browse to the ROM and flash it.
2. To flash factory images: http://forum.xda-developers.com/showthread.php?t=2010312
Flashing the factory images is more thorough than simply flashing a ROM. You will lose pretty Mich everything including your custom recovery, so your phone will be like it was when in came out of the factory.
Sent using xda-developers app
Click to expand...
Click to collapse
Is it necesseray to flash factory images? And I will keep root if I do it? cause you say will be like it was when it came out of the factory,

ion_elgreco said:
Is it necesseray to flash factory images? And I will keep root if I do it? cause you say will be like it was when it came out of the factory,
Click to expand...
Click to collapse
No you wont keep root. Only flash factory images if my first suggestion doesnt work.

Chromium_ said:
No you wont keep root. Only flash factory images if my first suggestion doesnt work.
Click to expand...
Click to collapse
Ok thank you very much. I downloaded the sdk tool, but it looks different then in the tutorial...

ion_elgreco said:
Ok thank you very much. I downloaded the sdk tool, but it looks different then in the tutorial...
Click to expand...
Click to collapse
What do you mean?

Chromium_ said:
What do you mean?
Click to expand...
Click to collapse
In platform tools I have adb.exe and fastbook.exe, but how do I setup i dont quite understand it. I have used before to root an other tool, isn't it easier to use that.

ion_elgreco said:
In platform tools I have adb.exe and fastbook.exe, but how do I setup i dont quite understand it. I have used before to root an other tool, isn't it easier to use that.
Click to expand...
Click to collapse
No I forbid you from using a toolkit
Just follow the guide. I think that you are now on step 3.

Chromium_ said:
No I forbid you from using a toolkit
Just follow the guide. I think that you are now on step 3.
Click to expand...
Click to collapse
How can I enable usb debugging when I can't get in to android?

ion_elgreco said:
How can I enable usb debugging when I can't get in to android?
Click to expand...
Click to collapse
You dont need to. Adb works while the phone is in cwm.

Chromium_ said:
You dont need to. Adb works while the phone is in cwm.
Click to expand...
Click to collapse
In cwm still says adb not recognized.....

ion_elgreco said:
In cwm still says adb not recognized.....
Click to expand...
Click to collapse
Install drivers: http://forum.xda-developers.com/showthread.php?t=1992345
Sent using xda-developers app

Chromium_ said:
Install drivers: http://forum.xda-developers.com/showthread.php?t=1992345
Sent using xda-developers app
Click to expand...
Click to collapse
I have installed the drivers. Never mind I used nexus 4 toolkit v2.0 and pushed file to sdcard and installed rom.zip! And its working, thank god, otherways my mother would have killed me hehe

[VK810] Official Kit Kat Update Information

We're all in the process of receiving and installing this update, and there are many questions about recoveries, rooting, etc. This is a thread to gather all the info we know so people don't have to be searching through tons of posts.
(I'm in the process of installing now, so I'll answer as many of these questions as I can. I will also update the OP with info from other users. If anything I state is untrue, please post and let me know.)
Can I take the update while rooted?
Yes! If you are on 4.2 and rooted but on STOCK RECOVERY, you can take the OTA and keep root.
Can I take the update with TWRP installed?
No! You will bootloop into recovery.
Is there an alternative/manual/TWRP method of installing?
Yes, see below post.
How am I supposed to update if I installed TWRP?
See below post, "README if you are currently on JB4.2.2"
Alternative method: "download flashify from the play store, backup twrp, then flash the recovery.img from OP. No pc needed & 100% pain free." Thank you to 86shelby. Then take the OTA.
Can I root the 4.4 version?
As of 8/26, yes! Stumproot works with the Bruteforce method. http://forum.xda-developers.com/show....php?t=2850906
Can I downgrade from 4.4 to 4.2?
Yes
If anyone else has questions they'd like posted, please let me know, and I'll put them in.

NOTE: If you want root/twrp in KK4.4.2, you'll need to pre-root in JB4.2.2 before OTA update(towelroot works in JB4.2.2, but not in KK4.4.2)
Looks like Stumproot works with KK4.4.2
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
Do one of the options below:
A) If you still want 4.4.2 via Verizon OTA, flash stock recovery
Go into TWRP, restore stock recovery via link below
http://forum.xda-developers.com/showpost.php?p=52975059&postcount=65
B) If you want to stop the bootloop, and flash 4.4.2 via TWRP backup from below...
Go into TWRP, wipe OTA partition (which signals the device to keep going into recovery)
http://forum.xda-developers.com/showthread.php?p=51749086#post51749086
Click to expand...
Click to collapse
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)​
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
If you have TWRP installed, you'll need to flash stock recovery. Either (A)
restore stock recovery only, or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
NOTE: some people have problems with OTA even after restoring stock recovery. You'll have to restore using the (B) method, and lose everything
[*]If you want root in 4.4.2, you'll need to apply root BEFORE OTA (via towelroot, ...?). root is allowed during OTA, will be maintained after OTALooks like stumproot works
Apply OTA, hope nothing goes wrong
Yay!
Click to expand...
Click to collapse
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
Root ? (Towelroot isn't working though)
Flash 4.2.2 aboot.img and TWRP.img
A) Upload aboot.img from 4.2.2 to device, then do
Code:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
B) Follow steps in TWRP thread to install TWRP
Click to expand...
Click to collapse
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Install TWRP (see section above)
Get 4.2.2 TWRP backup from here and restore
or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
Click to expand...
Click to collapse
​

Guess I got lucky - never got around to installing the custom recovery. I MEANT to do that....

https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot

So this is what I get when I check for update. I'm stock unrooted I even did a FDR. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1080 using Tapatalk

Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.

modus81 said:
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
Click to expand...
Click to collapse
have you tried other root methods?
ioroot, or this root below? (
http://forum.xda-developers.com/showthread.php?t=1886460&highlight=4+2+2

paperWastage said:
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
Click to expand...
Click to collapse
How do I install this?
Sent from my VK810 4G using Tapatalk

gfullwr70 said:
How do I install this?
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
you don't. go through Settings-> System update

paperWastage said:
you don't. go through Settings-> System update
Click to expand...
Click to collapse
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk

gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Same here

Flashing comletely stock via .kdz file
I'm getting the 0X13E error. Does anyone have the the process for this? I saw a different thread that directed to a droidreviews.com website but one of the files it said to download, my Chrome browser scanned as malicious so I stopped pursuing that route.

ssinn said:
Same here
Click to expand...
Click to collapse
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
Thanks this is what I was looking for. I'll give it till tonight to see if the ota shows up then I'll try this method.
Sent from my XT1080 using Tapatalk

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?

prana22 said:
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
Click to expand...
Click to collapse
first one.... my tablet wasn't able to find an OTA on 4G LTE (on t-mobile's network), but wifi works fine

Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
That's interesting, and good to know. Can anyone else verify this? I didn't think the update would go through if you were rooted. Now I might downgrade through kdz again and root before I take the OTA.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
go flash TWRP, make backup of stock and share it please?

How can I revert to stock recovery in OSX? All I see is the LG Mobile tool for windows?

Everything stock, suddenly stuck on Boot loop after reboot.

Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !

cart00nist said:
Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
Click to expand...
Click to collapse
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.

ariesgodofwar said:
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.
Click to expand...
Click to collapse
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!

cart00nist said:
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!
Click to expand...
Click to collapse
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.

theminikiller said:
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.
Click to expand...
Click to collapse
About 10 minutes.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?

cart00nist said:
About 10 minutes.
Click to expand...
Click to collapse
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.

theminikiller said:
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.
Click to expand...
Click to collapse
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?

cart00nist said:
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?
Click to expand...
Click to collapse
You shouldn't, just make sure it's for the same android version.

theminikiller said:
You shouldn't, just make sure it's for the same android version.
Click to expand...
Click to collapse
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?

cart00nist said:
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?
Click to expand...
Click to collapse
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.

theminikiller said:
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.
Click to expand...
Click to collapse
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me

cart00nist said:
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me
Click to expand...
Click to collapse
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear. ☺

theminikiller said:
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear.
Click to expand...
Click to collapse
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

cart00nist said:
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
Click to expand...
Click to collapse
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

theminikiller said:
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?

cart00nist said:
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?
Click to expand...
Click to collapse
Do you get any feedback if you use the command "fastboot devices"?

theminikiller said:
Do you get any feedback if you use the command "fastboot devices"?
Click to expand...
Click to collapse
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.

cart00nist said:
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.
Click to expand...
Click to collapse
In that case I unfortunately don't have any more ideas, sorry. I wish you luck with your phone tho, maybe some other member here at xda has any other ideas.