Database Info

[UNROOT] Unroot any android device

HOW TO UNROOT (ALMOST) ALL ANDROID DEVICES (SIMPLIFIED)
Firstly, in order to unroot your android device, you need:
1) An update available for your phone or an old nandroid backup that has a previous version of your phone android version
2) A nandroid backup done before you attempt the following steps below
Once the above conditions are met, you are ready to UNROOT your phone!
Before you read the procedure, read how it works
below and get a better picture:
HOW
Firstly, one known method of unrooting is to install an available system update. However, stock updates are signed with official keys and custom recoveries only accept updates signed with their custom keys.
So, to unroot, you need to have stock recovery installed. One way to get your phone`s stock recovery back is contained in the update zip.
The update zip is the key, literally. Look through it and you will find (usually in the system folder) a file called recovery.img, which will be used as your new stock recovery.
By flashing in the image into recovery, you can now install updates, keep your previous applications, enjoy being unrooted and updated.
There are other unroot options that tailor to specific android phones and versions, but this solution should work on all android phones.
Why unroot? Because sending in a rooted phone for repair will void your warranty. Also, by having a rooted phone, you run the risk of a rogue rooted application that does unwanted stuff to your phone.
PROCEDURE
Step 1) If you still have your original stock recovery that came with your phone, continue. Else search for my previous thread: "[RECOVERY] Reverting to original(STOCK) recovery" and follow the steps there. You can use the update file you used to revert to stock recovery here as well or vice versa
Step 2) Reboot you phone
Step 3) Check for system updates and download them
Step 4) Wait until phone reboots. All your applications and user settings will be retained.
Step 5a) Open up a terminal emulator on your phone and enter "su" (Check if unroot)
Step 5b) If you cant turn your phone on to check if unrooted, boot into recovery mode, open up adb enter:
Code:
adb shell
su
Step 6) If you get "permission denied" or something like that from step 5a/5b,
CONGRATULATIONS! YOUR PHONE HAS BEEN SUCCESSFULLY UNROOTED!
Step 7) If you don`t want to void your warranty, you should unistall applications that require root, especially Superuser
To date, I have rooted and unrooted my phone (Backflip) 3 times without any problems. In case your phone can`t be booted up, only to the bootloader or recovery, DO NOT WORRY! You can use the adb (android debug bridge) to flash in the stock recovery, push/pull the updates and reboot the phone into recovery mode or normal mode!!!
Useful ADB commands
Reboot Phone
Code:
adb shell
reboot
Reboot Phone into recovery mode
Code:
adb shell
reboot recovery
Flash a new recovery image temporarily (resets when rebooting)
Code:
adb shell
flash_image recovery /sdcard/recovery.img
Flash a new recovery image that does not reset when rebooting
Code:
adb shell
flash_image recovery /sdcard/recovery.img
exit
adb shell
cd system
su
mount -o rw,remount /dev/block/mtdblock1 /system
rm recovery.img
mount -o ro,remount /dev/block/mtdblock1 /system
exit
exit
Push file to sdcard
Code:
adb push file.blah /sdcard/file.blah
Push file to sdcard
Code:
adb pull /sdcard/file.blah file.blah
Here`s wishing you good luck and a belated happy new year!

Err.. Pretty cool info there but what if you don't meet above three requirements? I mean there are noobs like me who'd rather jump onto flashing while forgetting about nandroids etc. I guess there should be a one click unroot utility for all android devices like we have for rooting.

im really confused.
if the phone has been rooted (using fastboot oemunlock - yes) then how can we "unroot" this device? till today there has not been a way to do so.
but if what ur suggesting relocks the bootloader (removes the cross at bootup) then woohoo!

The main point
ok, i think you guys dont understand what my point on unrooting is...
What im trying to say is:
Updating your phone software with an original OTA update on the original rom the came with your phone will automatically reset root. However, custom roms and recoveries dont accept OTA updates, so you need to flash back your original recovery first, nevermind if you have a custom rom.
If you don`t meet the requirements, then i`m sorry, you`ll just have to wait for an available system update like me. However if you get one, be sure to come back here if you want to unroot.

Creating a one/two click-unroot application
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.

siidheesh said:
Actually, you may be right. The unroot procedures can also be carried out by adb alone , not by user interaction. So a desktop application can be created that automates the process
1) Open adb shell
2) Enter su
3) Pull the update zip from the phone
4) Recursive/y search the zip for the file recovery.img
5) Run 'flash_image recovery recovery.img'
6) Run 'adb reboot' to reboot phone
7) Phone will install update on stock update when rebooting complete
8) When update installed, root will be removed and your phone will be updated as well!
We can send keystrokes to the adb for the adb shell.
Click to expand...
Click to collapse
Shouldn't be too hard, probably only a simple script would suffice I'll see what I can come up with (if I can do anything ). Supply the script with your required update zip to make it work in a different way (maybe, I'm not great with details)

Automated Script
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?

Different definitions
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.

siidheesh said:
Sorry people, when i mean ota update, i dont just over-the-air updates, i am referring to original updates for your original android system that came with your phone.
Click to expand...
Click to collapse
So just to clarify, you could install any stock ROM for your device and it would remove root? Specifically if it was installed through stock recovery.
Thanks, hopefully I might be able to make some progress after this

not as easy as it seems
jonathongrigg said:
Can someone please clarify that this would work (as an unroot script):
1. Opens ADB shell
2. Enters su
3. (User) Supply script with stock update.zip - in case it's not on phone (correct if this is unnecessary)
4. recovery.img extracted from update.zip
5. recovery.img flashed to phone via 'flash_image recovery recovery.img'
6. Reboots phone via 'adb reboot'
That installs stock recovery, but what if there was no OTA update to install for that particular device? That's the only problem I can see with such a script, so I'm hesitant to make it right now (besides, I don't have my Nexus with me at the moment, so I couldn't test it).
Dumb question but would flashing a stock update.zip from the stock recovery remove root? Or does it have to be OTA? Never having done it before I'm not sure.
Edit: If it did have to be OTA, maybe you could find the original update.zip (ie. no updates before it) and flash that, so there would be a higher chance of an OTA update?
Click to expand...
Click to collapse
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.

siidheesh said:
You cant make an unroot script that easily. Im halfway working on a .net application that does it on desktop.
Also, almost all great things come with a *catch*. In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )

siidheesh said:
In this case, you need to wait for an ota update to be available. Or if you took a nandroid backup some time back and updated your version, you can revert back to the old verison and update again.
Click to expand...
Click to collapse
Another win for stock Android phones No waiting months for OTA updates! Well good luck on your .NET application, I only know Java and Python, so I can't really help you there, sorry.

dont know
my phone (Backflip) isnt a very popular phone and there`s only one rom for it. to date, i`be only tried unrooting via stock updating. Stock roms may work too, but im not sure...

adb shell
jonathongrigg said:
Oh well, I didn't realise I figured you could do it all from the command line, so a script of some kind might do. That said I wasn't entirely sure as I couldn't test the theory (no phone )
Click to expand...
Click to collapse
actually, i did mention that the unroot procedure can be done entirely from the adb shell, which is also in command line. im just making a program to enter those lines in automatically. normal batch scripts cant write to the adb shell as it is a separate shell in the command prompt...

What about doing a factory reset?

hi, would these unroot methods still work on the new updated highly secured samsung galaxy s2?
because i got the phone simlocked hoping to unlock it for t-mobile so rooted the phone but it was been unsuccessful at taking the sim lock off, so i wanted to make sure that this will still work on this phone.
Also after unroot i assume the yellow triangle will disappear, right?

oh yea thanks for replies and help in advance. Love the site

total noob here, I rooted my tab awhile bk, now needs warranty. I used 'superoneclick', but didnt backup anything first that i know of. U mention nandroid backup, update available for my phone, where do I get that, and how? Embarrassed I know nothing about these terms, trying to learn. Could u help me, please?

where can I find the recovery.img?
thanks

Does this work on all roots?

Bootloop after Trickdroid tweaks

Hello Forum,
I have a problem with my Htc One S today i installed Trickdroid 8.0 and it worked fine so i wanted to install the tweaks too. So i selected what i wanted and when the phone started it got stuck at the bootloader screen. I thought it just needed some time but after 15 minutes i gave up and turnt it off. Then i went into the recovery to install the rom newly but it always says it can't mount the sd card. Already relocked the bootloader and tried to install the europe ruu 1.78 but i got error 131 i have read that might be, beacause mine was branded by T-Mobile (but no simlock or else)
Really need help appreciate any answer

Really no one knows how i can fix this ? Need to fix it pretty soon because i need my phone :/ I can't even turn mine off, so i just let the battery die don't think that's to good either

Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.

j0hnh0lmes said:
Boot into recovery and ref lash. What tweak did you do? Not all work with 8.0. Tweaks have not been updated for this version. Make sure to do a full wipe.
Click to expand...
Click to collapse
I can't reflash in recovery, because it always says "can't mount sd card"
Don't remember all of the tweaks i did but i did the nova launcher, remove sense, some apps, all of the tweaks on the first page and some other.

Okay now I did a "clear storage" and a "reset to factory defaults" with a stock recovery and after that i reinstalled the custom recovery again. Now I can access the sdcard again but it's empty of course. Then i bootet in recovery and tried to push the trickdroid zip on to the sdcard via adb like this "adb push Trickdroid_v8.0.0.zip /sdcard/Trickdroid_v8.0.0.zip" but then it says:
daemon not running starting it now on port 5037
daemon started successfully
protocol failure
and simply ends. How can I push the Rom really need help, because my phone has no rom at all right now ?
ah okay needed to use the adb in the android sdk folder not in the little fastboot folder i had it just worked

Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"

rugmankc said:
Not at home to double check your command line--sounds like that is issue
But, you can type adb devices first to see if phone is recognized
I usually cd to the directory I have adb/fastboot files in, put zip on C: root
and type: adb push C: "then the rest"
Click to expand...
Click to collapse
Thanks for your help but as i have written i already got it back working thread can be closed

Sorry,
I posted before your edit showed up--

Glad to hear.

steps for next time
Hi, just before the thread is locked.
What has helped me in more of these occassions:
1. Make sure you read the install instructions of the ROM builder (I overlooked the 'flash Boot.img' which was added after some version)
2. Make sure you don't 'custom' work your memory (no partitioning etc).
3. First install the ROM and do REQUIRED afterwork (most often: Data/factory reset. Which doesn't wipe your photo's or just your account information and saved settings that will interfere with new rom options)
4. after making sure it boots and it reboots.
5. If this is the case, make sure you get the tweak package pointed out by the rom builder.
6. If all else fails, first read up on XDA and rom builder's site (often community on XDA) THEN start actions well informed.

[Q] Karbonn A30 Boot Loop Problem

Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.

Pinoy_Ako said:
Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.
Click to expand...
Click to collapse
1) Download the Android SDK (if you haven't already).
2) Run Android Debug Bridge using Command Prompt or Terminal (Depending if you are Windows or Mac)
3) Use ADB to pull the build.prop file to your computer.
4) Alter the LCD Density back to normal. Make sure the permissions are 644.
Alternative 3) Download the stock build.prop for your device.
5) Push either the build.prop (with normal LCD density) back to /System/ in ADB
Tell me how it goes

williamguy said:
1) Download the Android SDK (if you haven't already).
2) Run Android Debug Bridge using Command Prompt or Terminal (Depending if you are Windows or Mac)
3) Use ADB to pull the build.prop file to your computer.
4) Alter the LCD Density back to normal. Make sure the permissions are 644.
Alternative 3) Download the stock build.prop for your device.
5) Push either the build.prop (with normal LCD density) back to /System/ in ADB
Tell me how it goes
Click to expand...
Click to collapse
I already downloaded the Android SDK and installed it. I run the ADB by using the command prompt but it only gives me the commands ( like -d, -e, -s, -p). How do you use this thing? Can you please elaborate on how use this thing and how ADB can pull the build.prop since I can't seem to connect my device to computer?

Pinoy_Ako said:
I already downloaded the Android SDK and installed it. I run the ADB by using the command prompt but it only gives me the commands ( like -d, -e, -s, -p). How do you use this thing? Can you please elaborate on how use this thing and how ADB can pull the build.prop since I can't seem to connect my device to computer?
Click to expand...
Click to collapse
I'm not to familiar with ADB.
To pull files: adb pull /mnt/sdcard/path/to/file /path/to/local/file
To push files: adb push /path/to/local/file /mnt/sdcard/path/to/file

I manage to study the adb thing. The problem I face now is how to connect my phone to pc.My computer doesn't recognize my phone when I connected it. I tried to search for the device driver but I can't find any. Even the pc suite is missing for this phone.

Here is CWM recovery for A30. flash it using ANDROID AIO FLASHER in fastboot mode. using cwm you can easily fix your phone
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s

karan128 said:
Here is CWM recovery for A30. flash it using ANDROID AIO FLASHER in fastboot mode. using cwm you can easily fix your phone
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s
Click to expand...
Click to collapse
I dont know what fastboot mode means but I will try to see this ANDROID AIO FLASHER. Sounds that I will have to connect my phone to my pc. I just hope that it can help me to connect my phone easily.

Pinoy_Ako said:
Problem Details:
I recently rooted this phone (no custom recovery yet) and installed the ROM Toolbox Lite. I edited the build.prop to to change the lcd density to make it more nicer to look and it gone okay.
The problem arises when I tried the Font Installer in the ROM toolbox lite. It required a reboot and then the boot loop happens.
I went to system recovery and tried all the wiping methods but it didn't work. I tried the update from the sdcard but all installations were aborted because signature verifcation always failed.
Do you have any solutions to this ( or will I have to throw my phone to the trash cans now :crying? Any help will be highly appreciated.
Click to expand...
Click to collapse
install cwm . then flash it.. download cwm backup.. and just restore it ..
pree:good:

rajit said:
install cwm . then flash it.. download cwm backup.. and just restore it ..
pree:good:
Click to expand...
Click to collapse
If only it allows me to flash zip then it would be easy. the problem is i cant toggle off the signature verification.

Pinoy_Ako said:
If only it allows me to flash zip then it would be easy. the problem is i cant toggle off the signature verification.
Click to expand...
Click to collapse
You cannot toggle signature verification. You need to flash CWM first.
CWM is a custom recovery for android phones that provides many functions like system backup, restore, flashing zips, etc.
Flash cwm by going into fastboot mode

karan128 said:
You cannot toggle signature verification. You need to flash CWM first.
CWM is a custom recovery for android phones that provides many functions like system backup, restore, flashing zips, etc.
Flash cwm by going into fastboot mode
Click to expand...
Click to collapse
I already have this CWM before I rooted my phone. I just didn't flash it after I rooted it (silly on me ). Now my only hope is to have a fastboot but my problem now is how to get the drivers for my phone since I can't connect and my pc didn't recognize.

Can anyone give me a link where I can get the device drivers for this phone (windows user here)?

Install PDAnet on pc for drivers.
Sent from my A9 using xda app-developers app

I still can't connect my pc after installing the PDAnet. (Maybe it's time for me to get rid of this phone.)

Pinoy_Ako said:
I still can't connect my pc after installing the PDAnet. (Maybe it's time for me to get rid of this phone.)
Click to expand...
Click to collapse
h tt p: //adbdriver. com/ downloads /
download the 'adb driver installer'
run it
it will automatically detect the driver needed for u r device
and click install

Stock MF3 to MJ9 through sideload for those that can't update through OTA

Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.

Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.

Ota link
raidel00 said:
Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/show...&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.
Click to expand...
Click to collapse
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325

Bimboy said:
Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.
Click to expand...
Click to collapse
silrosriv said:
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Click to expand...
Click to collapse
Ok...fixed it. Thanks for pointing it out!:good:

Help!
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted

does this wipe the device? or does it keep all your apps / data?

Update
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.

silrosriv said:
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
Click to expand...
Click to collapse
probably due to some users having some issues with mms

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Interesting....It worked so smooth for me I don't know what else to say.

jherring002 said:
does this wipe the device? or does it keep all your apps / data?
Click to expand...
Click to collapse
If you do it by sideloading it from the computer it will not wipe the device. If you do it by running it from the SD card....it will wipe the device.

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.

dwanhala said:
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.
Click to expand...
Click to collapse
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.

scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yup. I chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
I think I'll jist wait for it to come back.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

It's working pretty good on my phone. I quit using the lookout security app though. It's not really needed. I know they pulled galaxy s3 update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Had the same problem when I tried to sideload the update. I was on MF3 and was rooted. What worked for me was to delete all busybox files and unroot using SuperSU and odin back to stock, just in case. After that, I was able to sideload and the phone booted up with no problems.

It works pretty good on my phone also. Was on mj6 and it was having random FC's also random vibrating but now on mj9 I don't have those problems anymore.
Sent from my SAMSUNG-SGH-I337 using xda premium

Thanks
Sent from my SAMSUNG-SGH-I337 using Tapatalk

I was getting the same error. What I did was re-load mf3 (via odin) and then sideload this update.

scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yeah, at this point I just rooted again (which of course set my device status back to official from the custom that it had changed to when I unrooted) and I'll wait to see if AT&T is going fix the problems before proceeding.

finally
I can't believe it
- Restore my S4 AT&T to 4.2.2 stock with Odin all the 4 files in MF3 using (download mode)
- Sideloaded to 4.3 ...MJ9 File with the Framework using (recovery mode)
Now my phone is even rooted with SuperSU (starting the root with vroot and converting it to SuperSU)
with the following sort video tutorial that found on youtube this morning
youtube.com/watch?v=isHYNqWCfSc

LG Urbane 2nd Edition Verizon W200V , Android Wear 2.0 Side load OTA Guide

Hey All,
This is my first ever post on XDA ,So forgive me if I have not done a good job. I will try my best to provide sufficient details on how to upgrade LG urbane 2nd Edition Verizon model watch to Android wear 2.0 from Android wear 1.5
Known Issues : **********Android Pay is not working as reported by few users ***********
YOU FLASH THESE FILES AT THE RISK OF BRICKING YOUR DEVICE. I AM SIMPLY PROVIDING THEM AND BEAR NO RESPONSIBILITY FOR ANY SUBSEQUENT DAMAGE FROM FLASHING THESE FILES. ALL DATA ON THE PHONE WILL BE ERASED.
Prerequisites:
[*]LG Urbane 2nd Edition Verizon Model (W200V) for all other model you should have received a OTA by now , Please check OTA software updates on you watch.
[*]ADB tools ( Minimal is also sufficient) google for files and install in your computer , in my case I did it in "C:\adb".
[*]twrp-3.1.1.0 (twrp-3.1.1.0.img) recovery Image Copy of the file :- https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k
[*]Android Wear 2.0 OTA udpate Copy of the file :- [*]Modified file link http://www.filehosting.org/file/details/699795/lg2.zip or original file https://android.googleapis.com/pack.../af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip
[*]notepad++ (to edit updater-script), You can use Notepad as well.
1)perform factory reset on your watch just to be on safer side.
**update** Few users have reported that they have faced error while flashing due to buggy USB cable and they could successfully overcome the error by holding the cable to the watch and making sure the cable is fully in contact with the watch while flashing .**Update**
2)now we need to modify the OTA update file to work with Verizon model W200V ( skip this step if you have downloaded modified zip file and jump to 3rd step)
unzip the 'af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip" downloaded earlier and Browse the folder Edit file (updater-script) the file can be fount in the below path in my case."C:\ADB\af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8\META-INF\com\google\android\updater-script". Use Notepad ++ and open the file and Remove 2 first rows,The file should start from "ui_print...", I used Note++ to edit the file and saved, as mentioned earlier you can use notepad as well.
Now Zip All files And name LG2.zip(Note : don't put all the files into a single folder and then zip, The zip should contain "META-INF" and other files) and place it in "C:\ADB\LG2.zip" for easier navigation in Cmd. (this file can be downloaded using above link Modified file")
3)next Connect your LG Urbane 2nd Edition watch to Computer and Enable ADB Debugging On watch (Settings-About-Tap about 8 times on "Build Number" and now go back to Setting and scroll down you should see new options "Developer Options" , Tap on "Developer Options" - and "ADB Debugging" select "Enable always from this computer" or something like that !!)
4)Now Check if your device has a connection to your computer using ADB tools
now on your computer under "Run" , type Cmd, this will bring windows command prompt.
Open Cmd in Windows and browse to ADB tools folder in my case I have placed ADB tools and all required files under "C:\abd"
Type "adb devices"
your device should show up under "List of devices attached"
Once device is found by computer we have to push the TWRP recover image to phone , To make life easy , I have downloaded all the above mentioned files to "C:\adb" folder
"adb push twrp-3.1.1.0 /sdcard/"
later boot into bootloader
"adb reboot bootloader"
Unlock bootloader
"fastboot oem unlock"
5)Now flash TWRP recovery (because we will be changing/modifying the original the OTA update file, stock recovery will fail to verify signature)
"fastboot flash recovery twrp-3.1.1.0.img"
boot to recovery to perform OTA side load
"fastboot reboot recovery"
Now you should see TWRP recovery welcome page,Allow read and write partition permission in TWRP.
6)now on your phone you should be in TWRP Main screen , press Install and you will find option to adb Sideload select that option and you will be presented with a option to wipe Dalvik and Wipe Cache , Select that and now go back to your cmd and type below code.
"adb sideload lg2.zip"
Now sit back and relax , The system will starts loading Android Wear2.0 to your verizon LG urbane 2nd edition watch (W200V) and once the process is finished , reboot to system.
1st boot will take some time , Have patience !! after all you have done ever thing right till now. (approx 5-10 mins, sometimes 15 mins)
Now your watch has Android wear 2.0 , enjoy.
Initially it might feel the OS is slow but allow the OS to settle down after that its snappy and the battery backup is also good in my opinion.
If you want to restore Stock recovery image just in case if you don't like TWRP, then
download the below targz file and extrat recovery.img file , LG Urbane 2 stock recovery image.
Link ,
enable ADB options under settings similar what we performed earlier.
1) Boot into bootloader
"adb reboot bootloader"
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE(extract the file and copy recovery.img file to your folder , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files and you will see recovery.img file .
Place a copy of recovery.img in "C:\adb\recovery.img"
"fastboot flash recovery recovery.img"
You can also Lock Bootloader to avoid the Notification at each boot.
"fastboot oem lock"
To get back to original android watch wear 1.5
if you don't like Android wear 2.0 use the below link and follow instruction to revert back to Android wear 1.5.
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files.
Extract the *.tgz(targz) into your folder ("C:\adb")
Perform a "fastboot oem unlock", then run "flash-all.bat". Afterwards, you can "fastboot oem lock". This should restore you back to 1.5, where you need to take 1 OTA (from June 2016 Patch to December 2016 Patch).
Thanks All,

Missed something
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!

Has anyone other than the original poster tried this guide and been successful?

Thxfctr said:
Tried a thousand times. Not working
Click to expand...
Click to collapse
Are you getting any specific error ?

djdubd said:
Has anyone other than the original poster tried this guide and been successful?
Click to expand...
Click to collapse
It does work I had problems but I think holding the USB to the watch helps. I tried it a lot but it was worth it. Suck it verizon!

Thxfctr said:
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!
Click to expand...
Click to collapse
I am Glad finally it worked for you!!

suresh.chikkanna said:
I am Glad finally it worked for you!!
Click to expand...
Click to collapse
Ty! I think my USB connector is just a bit jinky.

I'm going to give this a try soon, everything working like lte, messages+, and phone?

Almost got it working
Followed all the directions and all seemed to work ok without errors. However, on startup now the watch is stuck on the startup splash screen (the animated google logo, has stayed there for hours). Can still access fastboot but unable to connect via ADB since the OS is not starting fully.
I also tried to restore back to 1.5 but since i can only access fastboot, my only option is to sideload but wont work with the TGZ link above.
Anyone have any ideas? or the zip file I could use to sideload the stock Wear1.5?
Thanks

Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.

Locked /data won't allow sideload.
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.

Gphoton31 said:
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.
Click to expand...
Click to collapse
I had similar issue initially , had to restore back to 1.5 and then clean all the data and then sideload 2.0 back. Try that and let us know if that worked.

You are the man! That worked
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.

suresh.chikkanna said:
Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.
Click to expand...
Click to collapse
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]

Solved flash-all not working
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.
---------- Post added at 06:37 PM ---------- Previous post was at 06:05 PM ----------
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.

Gphoton31 said:
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.
Click to expand...
Click to collapse
I am really happy for you.

OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
Flash the original recovery.img extracted from the .tgz file and try again it should work.
For ADB access in TWRP use sideload using ADB option .

So will android pay work now with this

B
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?

I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?