Related
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.
So if I got this right if I have busybox already I only have to do is step 7.
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Step 4, a quicker way: adb shell su , get you into shell as root right away
AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.
Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.
Updated with a link to another good tutorial about pushing ROMs to the phone
Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!
AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...
Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps
Dude add S3 stock recovery please.
Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.
After lots of hard work by a great team of people (listed at the end), we have finally made a working Root for the Acer Iconia Tab A110.
Warning:
Code:
*I, nor any of the people involved in the rooting process of this
tablet are responsible for any damage you may cause to your device.
*If you brick your device, we are not to blame.
*Your warranty may be void after doing this.
*By using this guide, you acknowledge that you are fully responsible
for any damage you cause to your device and the device accessories.
ACER ICONIA TAB A110 ROOT GUIDE 4.1.2
UPDATED NOVEMBER 13, 2013; Most Recent Version
You will need to download/install the following before starting:
Acer Iconia Tab A110 USB Drivers (Should install on first connect of tablet)
Android SDK
SuperSU
a110-412-CWM-recovery.img Mirror: a110-412-CWM-recovery.img mirror
___________________________________________________________________________
Once downloaded, extract the Android SDK to a known location, such as the Desktop. (Use an extracting application such as Winrar)
Next, install the Nexus 7 Toolkit.
___________________________________________________________________________
Once that is complete, you can begin the rooting process.
On your device go to:
Code:
Settings > Developer Option
Turn Developer Options on at the top, and enable USB debugging.
Navigate to your Android SDK folder:
Code:
adt-bundle-windows-x86_x64\sdk\platform-tools
Copy and paste the recovery file in this directory, and copy the SuperSU files to the Tablet's SD Card. This will make the process easier later.
___________________________________________________________________________
Bootloader unlock:
The next step will wipe all your data. Remember to create a backup of anything you want to keep before attempting this.
Open a command promt (CMD) window in the directory above by holding shift while right clicking in the window and selecting "Open Command Window Here."
Type in CMD:
Code:
adb devices
Code:
adb reboot bootloader
Wait for the tablet to load into the bootloader, then type:
Code:
fastboot oem unlock
Accept on the tablet via volume and power buttons.
Your bootloader should now be unlocked.
___________________________________________________________________________
Root:
Type:
Code:
fastboot reboot-bootloader
Wait for it to reboot, once again.
Next, type:
Code:
fastboot devices
Code:
fastboot boot a110-412-CWM-recovery.img
Wait for the "OK" notification.
___________________________________________________________________________
Now, you will be booted into the custom recovery.
Right click on the Acer A110, and select install driver. Choose to point to your own path, and point it at the path for the Nexus 7 Toolkit install. (Make sure you have include subfolders checked)
Now, the device should be recognized and the root can continue.[/Code]
___________________________________________________________________________
On the device, use the volume buttons to navigate and power button to choose.
Select Install from SD.
Now type:
Navigate to the CWM-SuperSU-v0.99.zip file.
You should receive a complete message.
Once that is complete, on the tablet, navigate to reboot, select yes at the prompt, and the tablet will reboot.
You are now successfully rooted on 4.1.2!
___________________________________________________________________________
Special Thanks to the following people for their ongoing hard work:
fringle
FriedBacon
Skellums
posterz
heX79
blokenfeffer (New Recovery Image)
Stock Recovery
Here is a link to the Stock recovery pulled off of my tablet.
Not sure if it works or not, but if someone wants to try:
Stock Recovery
Installing Applications/Games to the External SD Card
I spent a long time looking for a program that allows me to do this, and finally found one that fully works.
DirectoryBind works wonders.
Here is a link to the guide:
DirectoryBind
Enjoy your extra storage space!
Reserved for further development..
Reserved for further development...
Reserved for further development
Thanks to the root method ? Could you tell me how to perform full system backup?
DjDom said:
Reserved for further development
Click to expand...
Click to collapse
I am a newbie to android. could anybody tell me how to perfrom full system backup for acer a110 4.1.2?
There is currently no way to make a full nandroid. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
root error！ help！
DjDom said:
There is currently no way to make a full android. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
Click to expand...
Click to collapse
thanks!
it seems there is an error while i root：
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.
cooltravis said:
thanks!
it seems there is an error while i root：
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.
Click to expand...
Click to collapse
Did you download the most recent version of ADB?
Make sure you install all the drivers and follow the beginning of the guide.
Completed process but no root
I finished the process but it did not work with the first img I will try with the other one
francois2012morin said:
Does not work for my tablet. It does not unlock the bootloder so I don't get the recovery file to load.
Is it a problem with the version of my tablet software.
Here are the specifications
Android 4.1.2
Core 3.1.10
Image version Acer_AV051_A110_RV00RC09_WW_CUS1
BUILD NUMBER Acer_AV051_A110_1.049.00_WW_CUS1
Image ref FM.S1RA0.03E
Thank you if you can be of any help.
Francois
Click to expand...
Click to collapse
How did you try unlocking the bootloader?
after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks
running_onCode said:
after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks
Click to expand...
Click to collapse
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?
DjDom said:
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?
Click to expand...
Click to collapse
Yea. Everything. Anyway to get passed it?
Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery
darthpilsner said:
Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery
Click to expand...
Click to collapse
Yes i am having the same problem, mine does not see a110 but refers to google galaxy nexus adb interface. I have tried this about half a dozen times with the same result, no root. Oh well try try again. Do i need to factory restore after each failed attempt?
No Root....
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...
rocy1971 said:
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...
Click to expand...
Click to collapse
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Same
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Model a110
Android 4.1.2
Kernel 3.1.10
image acer_AV051_a110_rv00rc09_pa_cus1
Build acer_AV051_a110_1.049.00_pa_cus1
everytime I do it .... it looks like it will work... then check root with rootchecker or susuperuser.... no luck.....
If the root did work... would app2sd work... or do I have to wait for a custom rom?
Same result here!
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Exactly the same results as the previous guys, every step appears successful, including sideload, but no SU after reboot. My Firmware has WW in name.
Only messages seen during sideload which imply errors are E: can't mount /cache/recovery/log etc etc.
Anyone any idea what may be wrong?
I wiped the system thinking it was part of the system factory reset in TWRP but i didnt know that it would result in it saying NO OS INSTALLED. i read other similar threads about this problem but dont exactly understand what to do and how to restore my phone. i have a nandroid backup but its on my pc and not the internal storage on the phone. im fairly new to this so those replying, please explain exactly what to do. Im so scared about what to do now :crying::crying::crying:
Don't be scared its common and very, very easy to fix
Now I don't use TWRP so I have no idea of the directory structure so I can't advise you exactly.
But what you will essentially do is use adb push to get the files on your phone.
Click the link in my signature to go to the sticky roll up thread. All the important threads are linked there. Y
In that thread you'll quickly find my adb info thread. This should be most of what you need to know
Sent from my Nexus 5 using Tapatalk
First relax, your phone is not ruined. I assume you have a custom recovery. You're going to have to either side load a rom zip using adb or adb push a rom zip onto your phone and flash it in recovery.
Edit, OP you'll want to push the rom to /sdcard/Download. That'll put it into the folder twrp defaults to look for it.
Sent from my Nexus 5 using XDA Free mobile app
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
http://www.koushikdutta.com/post/universal-adb-driver
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
https://developers.google.com/android/nexus/images
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
raptir said:
]
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
All these guys have it spot on! I just wanted to mention that when you install a ROM system gets wiped automatically as this is a parameter in the zip's updater-script.
So in other words there is really no reason to wipe system manually. Just let the install process do it for you. If u wipe system manually and then you realize you do not have a ROM zip or a nandroid only ADB can save you. So this way you can save yourself a headache
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
\
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
thauri said:
I downloaded everything and ran the flash-all . bat file but its currently been on < waiting for device > for a while now. i think it didnt detect the phone although it is connected through the USB :/
Click to expand...
Click to collapse
Did you or did you not read my adb and fastboot thread?
And WHY are you going for the last resort first???
You really need to chill out and read things because I don't think you're thinking straight
Sent from my Nexus 5 using Tapatalk
raptir said:
Well, you have three pretty easy options.
TWRP supports ADB commands, but the stock Google driver won't work. If you install the Universal ADB Driver you should be able to push your backup to your device (adb push [file location on your computer] [where to push on your phone])
You could also flash a ROM through adb sideload. Download a ROM zip to your computer, then in TWRP choose Advanced -> ADB Sideload. Then run "adb sideload [zip file]" to sideload the ROM you downloaded.
Last, you can restore to the Nexus Factory Image.
All of these options will require you to have the Android SDK setup on your computer. The link for the factory images has instructions on how to get that installed.
Click to expand...
Click to collapse
rootSU said:
Luckily its easier install adb and fastboot than the ask method. Just go to the thread mentioned earlier and use the 15 second installer
OP, no matter what you'll need run that installer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah i did download the 15 second ADB installer but my computer isnt detecting the phone connected when i ran the flash-all . bat file.
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
rootSU said:
1) you need to read the whole of my thread. There are drivers to install
2) Still dont understand why you're running flashall bat when you can just adb push your backup to your sdcard. You know you lose all your data when you do that?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
ok yes im reading your thread and doing the ADB commands. i have a question though, the multi-line input for the code to ADB push goes in cmd right? how is that possible?
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes
Type one line, press enter, type another line, press enter
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
thauri said:
when i press enter after adb shell and mount data, it says data failed : Device or Resource busy
Click to expand...
Click to collapse
If "mount data" shows device or resource busy, then that usually means it is already mounted.
rootSU said:
If "mount data" shows device or resource busy, then that usually means it is already mounted.
Click to expand...
Click to collapse
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Messing up is scary but it's a great opportunity to learn. I think you'll get through this just fine.
thauri said:
i did everything but in the last part, it doesnt transfer the recovery files to the phone
Edit: The files are transferring successfully but only one at a time.
EDIT 2: All the necessary files were transferred but the TWRP recovery mode isnt detecting it as a restore option
Click to expand...
Click to collapse
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
rootSU said:
It must be in the exact location twrp needs to see it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did, I put it in the backup folder in TWRP where all the other backups usually were
thauri said:
I did, I put it in the backup folder in TWRP where all the other backups usually were
Click to expand...
Click to collapse
Take a new backup, then delete everything in the new backup folder and move everything from your old backop into the new backup folder,
So for example
Code:
adb shell
mount /data
cd /data/media/0/TWRP/backups
ls
^^ This should list the contents... You should see your old backup and your new backup (which will be mostly empty).
Lets pretend your new backup folder is 22222222 and your old backup folder is 11111111
Code:
rm -Rf 222222222/*
mv 111111111/* 222222222
The first command is a remove (recursive) of the contents of the new backup. second command mvs contents of old backup into new backup folder,
Try that.
I don't know TWRP so my assumptions of the path may be incorrect
Someone else posted twrp default path as /sdcard/downloads - try that.
Code:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DISCLAIMER
I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. I've attempted to minimize the chance of damage, but you will use this guide at your own risk.
Thanks to [mention]ejwith9953[/mention] for getting TWRP working correctly
Thanks to [mention]forgottonhacker[/mention] for proofreading and formatting
ABOUT
WINDOWS ONLY GUIDE
THIS GUIDE IS FOR THE PEOPLE SEEKING TO INSTALL TWRP AND OBTAIN A FIX FOR SOFT-BRICKED DEVICES
STEP 1
On a DESKTOP:
Download CURE_4 and extract to desktop (or a folder to your preference).
[Download Links at Bottom of Post]
On your PHONE:
Go to Settings > About phone > tap build number, till it says your a developer.
Go to Settings > Developer Options and enable OEM unlock, and USB debugging
Reboot Device
STEP 2
Connect Device to PC
Open your extracted folder and run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window, copy/paste commands individually.
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see the following:
Code:
26404+0 records in
26404+0 records out
Get ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see Alcatel splash let go of power but continue to hold volume up.
Say hello to TWRP!
STEP 3
Now we are going to install SuperSU it’s easy from here don’t fret!
IMPORTANT
BACKUP /SYSTEM PARTITION IN TWRP AND MAKE A COPY ON YOUR PC
Now that you have a backup go back and tap install. Tap on "up a level" then sdcard.
Find SuperSu.zip and swipe to install!
Reboot system! (this may take a few minutes so don’t freak out)
Verify that SuperSu got installed.
Go back to the extracted folder on your computer and run CLEANUP.bat
SOFT FIX
Boot up to custom recovery tap wipe > advanced wipe
Select Dalvik cache and Cache, then SWIPE to wipe
Go back to the Home Screen
Tap Advanced > fix permissions and Swipe
REBOOT AND ENJOY
If this fix did not work for you please do contact me as I have another method, I will be putting up a debloated version of the ROM soon.
I will be adding more to the guide, so make sure to turn on your notifications!
DOWNLOADS
Stock-ish ROM EXTRACT FROM ZIP FIRST! then flash as /system
password: fax
Dropbox Google Box.net Mega
EDIT: On payday going to buy another one of these phones for stock firmware.
Reserved
Broken Download Link
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!
WowTheDog said:
The Link to download the Code-4 package is broken, and it makes me oh-so-sad!!! Help!
Click to expand...
Click to collapse
try now. also "cure-4" XD
Cure-4 download link not working.
I tried to say...
faxanidu said:
try now. also "cure-4" XD
Click to expand...
Click to collapse
The cure-4 thing is missing again, can we get a hold of that?
Omg everyone flagging as malware give me a bit
Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!
Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?
ericcorp said:
Hey, it all worked, I had a soft bricked phone, and its booting now. I did the commands in OSX, I just opened the START_HERE.bat and saw your adb commands. The only hangup was that I couldn't push Supersu.zip to /sdcard/ because it wasn't writable for some reason, but I just pushed it to the tmp path from the other commands instead.
Thanks so much!
Click to expand...
Click to collapse
Odd it pushes supersu automatically. Might had something to do with the soft brick. Your welcome though! Spread the word!
sanpuyon said:
Good brother my problem is that I have my soft brick phone and I do not know what to do to revive it, do you have any idea how to repair it?
Click to expand...
Click to collapse
Follow guide fixes soft brick also just reboot it. let it sit awhile then plug it in. Should be a able to get ADB shell
faxanidu, I just tried on my dead device and I got twrp :good: but won't complete boot after fixing permission tho. Hey that's good enough for me, congrats on what you did! Just gonna wait till a rom gets put up.
To get started I did have to do some steps in oem recovery like I said from the other thread, otherwise my device shows as unauthorized tho, enable adb, then rock volume back and forth till I get mounted /system, then hit reboot. It seems I've tried just doing one or the other but it would still be unauthorized. Just sayin, and again like I told you I don't really know what I'm doing
Thanks again, and if you have any further advice or tips, I'm all ears
edit: I didn't have supersu show up either but I put it on an sdcard and installed it that way.
i am too afraid to try this, is this safe? if i brick my phone, how do i flash stock firmware
---------- Post added at 03:24 AM ---------- Previous post was at 02:59 AM ----------
faxanidu said:
Good news everyone! I have built a massive guide for the alcatel ideal! install custom recovery and more now! also fix for soft bricked phones! just follow this guide.
WIndows only
Thanks to ejwith9953 with getting TWRP working correctly, he is the bomb!
So dont forget to thank him!
STEP 0
DISCLAIMER! I am not responsible for bricks, cats being both alive and dead, heat death of the universe, etc. Ive minimized the chance of damage as much as possible, but still use this guide at your own risk.
STEP 1Goto settings > about phone > tap build number, till it says your a developer.
Goto settings > developer Options. slide on OEM unlock, and USB debugging
Download CURE_4 to your computer and extract folder to desktop (or somewhere).
Reboot phone.
Links are at bottom!
STEP 2Open your extracted folder, run START_HERE.bat
Let it run, it will copy files, execute temp root exploit, and open a new CMD window.
In the new window type in these codes from top to bottom letting each one finish. ( or copy/paste )
Code:
adb shell
run-as -s1
su
dd if=/data/local/tmp/twrp.img of=/dev/block/mmcblk0p25
When you see:
26404+0 records in
26404+0 records out
your ready to pull out the battery ( reboot recovery does NOT work )
Put the battery back in and hold the PWR and VOL UP at the same time, when you see alcatel let go of power but continue to hold volume up.
Welcome to custom recovery my friends!
STEP 3Now we are going to install SuperSU its easy from here dont fret! but first!
click backup, under partitions uncheck everything EXCEPT system. Now swype to backup.
Now that you have a backup go back and click install. click "up a level" then sdcard.
scroll down and click SuperSu.zip. Swipe to install! Now Reboot system! (this may take a few minutes so dont freak)
check that SuperSu installed, did it? great! go back to the extracted folder on your computer and run CLEANUP.bat
STEP 4 -SOFTFIX ONLYBoot up to custom recovery click wipe > advanced wipe
checkmark Dalvik cache and Cache, the SWIPE to wipe ( sounds dirty )
now click BACK all the way to main screen. now click advanced.
click fix permissions And Swipe. Now REBOOT. hopefully that will boot your phone if not let me know. i dont
have an extra one to purposfully softbrick to test. but ill have a debloated pre rooted ROM for you
to use soon regardless
More to the guide will be coming, for now this is the basics. im going to bed see you all later!
LINKS!
password: fax
Dropbox Google Box.net Mega
EDIT: 4 links encrypted
Click to expand...
Click to collapse
faxanidu said:
Click to expand...
Click to collapse
Thank you! i am now happily running twrp, though with some mods, i rooted with kingroot first then ran the commands
Now we wait for lineage os or cm13
For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?
scohut said:
For some reason I can't do this on my working phone. when it comes to the "getting uid" screen, everything that runs says "missing second argument" then I try entering the commands it says "run-as: Package '-s1' is unknown"?
Click to expand...
Click to collapse
What the? Never had that problem can't reproduce plz send screenshot
faxanidu said:
Good news everyone! I have built a massive guide for the alcatel ideal!
Click to expand...
Click to collapse
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
# Device:Alcatel_4060A
-Getting uid 0->Ok.
-Checking permissive run-as.->Ok
# turn off/on the bluetooth.....................................................
..............←[s←[0;34m
[email protected]:/data/local/tmp #
Click to expand...
Click to collapse
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.
faxanidu said:
What the? Never had that problem can't reproduce plz send screenshot
Click to expand...
Click to collapse
this..
Rush-O-Matic said:
Thank you so much for this.
I started and misread the text as a lowercase "L" instead of the number one for the "run-as -s1" part of the code. I wasn't sure how to correct it when I got an error, so I started over and ran the START_HERE.bat again. When the new cmd window opens, I can't type anything. It reads:
I'm not sure how to start over to get back on track for the adb shell code.
I know, it's pretty bad that I didn't get past the first part of Step 2. Any help is appreciated.
Click to expand...
Click to collapse
That happens rarely just reboot and start again
faxanidu said:
That happens rarely just reboot and start again
Click to expand...
Click to collapse
And it reads what?
scohut said:
this..
Click to expand...
Click to collapse
Looks like exploit.sh for corrupted or something plus if you have any mods like exposed might interfere with it. The script dumps info it need to patch see policy then creates run-as with info.
Edit: I'm basically using dirty cow exploit. Works on everything
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?