Related
DISCLAMER and WARNING: I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or the current economic crisis. Please do some research if you have any concerns about this app.
Click to expand...
Click to collapse
Story:
Just received Sony Smartwatch 3 and decided to oem unlock for future so once root available I would not need to reset device.
Enabled adb
manually specified correct drivers in device manager
rebooted to bootloader using adb reboot bootloader
entered fastboot oem unlock twice and watch rebooted
but got stuck on boot for whatever reason.
I tried all the methods to get into fastboot (Swiping diagonal as on LG watch, and together with power button as on samsung ) to no avail.
The only other mode I was able to get into - s1 flash device w/o drivers.
Found Sony Emma software to work with unlocked Xperia, and after its installation it said that bootloader is locked and I need to either update from sony site or unlock bootloader first!
Installed Sony PC Companion software, but software update while listing smartwatch 3 said that there is no firmware for it.
After googling random forums on bootlooping sony xperias found that to reset device you need to click "repair my phone/tablet" in Phone/Tablet Software Update section
Click to expand...
Click to collapse
Guide to unbrick bootlooping SWR50 that is able to get into s1 bootloader/flash mode:
1. Power off device by holding power key until it reboots and then switches off with few vibrations
2. Connect to computer and check device manager - you should see unknown device
3. Install Sony PC Companion from this website http://www.sonymobile.com/us/tools/pc-companion/
Check if driver appeared in the Device Manager, e.g. unknown device will disappear and something like SEFLash will appear under usb controllers
If driver is still not found - try to install Emma (http://developer.sonymobile.com/services/flash-tool/) and get this driver to work
4. Go into PC Companion and click on "Support Zone", it will be downloaded
5. Then click on "Accessories software update" and try to update Smartwatch 3 (We might get new versions in the future, so it will be easiest to do so)
UPDATE: Now you can reflash from Accessories page, it will ask if you want to refrlash. Keeping steps bellow for information purposes.
6. If #5 not working:
Click on "Phone/Tablet Software Update" (yes, silly), click on "repair my phone/tablet", click Continue and Agree to all licenses, etc....
7. Once presented by the list of phones - Select anything I guess, but I selected Xperia Z2, it should start downloading and then updating.
8. Once done it will say build number watch was flashed, in my case it was KNX01V
9. Disconnect watch and boot it.
P.S. I guess they show phone selection just to provide instructions how to get into download mode and then flash based on the versions from bootloader.
P.P.S I'm glad I tried this last resort thing after being ready to deal with verizon support and waiting for new watch...
I've found that formatting cache and userdata partition like it says in the link below makes the device boot as expected:
source.android.com -> /source/building-devices.html#unlocking-the-bootloader
(sorry for faulty link, new user)
Good to know, I decided to wait a bit as I was eager to play with new toy.
Will unlock tomorrow if it is still locked after Sony reset.
And looks like I would have to write my own apps to test GPS and sensors performance.
And the good news is fastboot state unlocked after stock reflash.
XorZone said:
manually specified correct drivers in device manager
Click to expand...
Click to collapse
Can you please elaborate on which driver you used to get access to the Smartwatch 3 via ADB? I am trying to use the latest google USB driver, but the device is showing up as offline listed under "adb devices". Just tried the latest ADB v1.0.32 and it seems the watch shows up as "unauthorized". Did you see an ADB notification on the watch that you had to accept, because I am not seeing anything like that.
NVM, it started working after I restarted adb server like 25 times...
Device offline usually is not about driver. But I hit on device and manually picked google-adb composite device
OK, bricked watch today with corrupted /system and boot process hanged with non responsive power button. Had to wait for discharge and it was pita to get into flashmode with enough juice, because after black screen charging it boots instead of going into kernel charging.
Anyway it is up and running and has ROOT now!
Will upload files and create guide as soon as I will be with good internet.
See my sig!
*delete*
*deleted*
Well, there are different levels of bootloaders
At least Sony s1 flash, fastboot, kernel...
To flash with PC companion you need to boot into s1 by powering off and then hold power and connect to USB once sony logo shown (you should see black screen with backlight on). Make sure you sit on PC companion update screen and that watch had enough juice.
With charging there are different levels of charging:
1. Battery dead
2. Boot loader charging (about 4 min from USB port) with black screen
3. Kernel charging either offline (if you powered off before) or boot and operational charging.
When #2 charges it will boot kernel and if kernel or system is broken it might hang and discharge.
But you can force into s1 flash mode before it boots into kernel. Or if you lucky you could power on and power off before it boots and hang.
In my case I had not enough juice to flash it and watch didn't react to button in kernel mode, so I had to wait for discharge, then plugged into USB and start timer, figured it boots after ~3min 55sec. So I opened PC companion update screen, waited 3:53 and disconnected watch, then hold power button and connect to PC after 5 sec and was able to flash.
To power off - just hold power button until it reboots and continue holding until it vibrates 3 times.
Good luck
XorZone said:
Story:
Guide to unbrick bootlooping SWR50 that is able to get into s1 bootloader/flash mode:
1. Power off device by holding power key until it reboots and then switches off with few vibrations
2. Connect to computer and check device manager - you should see unknown device
3. Install Sony PC Companion from this website http://www.sonymobile.com/us/tools/pc-companion/
Check if driver appeared in the Device Manager, e.g. unknown device will disappear and something like SEFLash will appear under usb controllers
If driver is still not found - try to install Emma (http://developer.sonymobile.com/services/flash-tool/) and get this driver to work
4. Go into PC Companion and click on "Support Zone", it will be downloaded
5. Then click on "Accessories software update" and try to update Smartwatch 3 (We might get new versions in the future, so it will be easiest to do so)
UPDATE: Now you can reflash from Accessories page, it will ask if you want to refrlash. Keeping steps bellow for information purposes.
6. If #5 not working:
Click on "Phone/Tablet Software Update" (yes, silly), click on "repair my phone/tablet", click Continue and Agree to all licenses, etc....
7. Once presented by the list of phones - Select anything I guess, but I selected Xperia Z2, it should start downloading and then updating.
8. Once done it will say build number watch was flashed, in my case it was KNX01V
9. Disconnect watch and boot it.
P.S. I guess they show phone selection just to provide instructions how to get into download mode and then flash based on the versions from bootloader.
P.P.S I'm glad I tried this last resort thing after being ready to deal with verizon support and waiting for new watch...
Click to expand...
Click to collapse
This method is windows only. Is there no cross-platform way to do it?
I did the stupid thing.. and ended up with a softbricked phone.
Sony PC Companion did the trick for me!
I tried doing it through VMWare on my macbook, but didn't seem to work at all.
On windows it was plug'n'Pray
Sony companion will not let me restore my SW50. Detects it and tells me that the software is updated. If I try from the menu to repair phone, it makes me accept all agreements and finally tells me the same thing no updates.
Is in bootloop and do not start after open bootloader
My sw3 is in bootloop.I uesd your guide but still can't repair my watch. I tried many time to use pc companion but always got the same wrong message,wrong code(100) which couldn't connect to the Internet.
@swidon @KONG8691
I find myself in the same situation, you have found a solution to the problem?
Thanks for your help
best regards
jerry_italia said:
@swidon @KONG8691
I find myself in the same situation, you have found a solution to the problem?
Thanks for your help
best regards
Click to expand...
Click to collapse
Yes!, follow these instructions and you can enter in fastboot or recovery and flash a new firmware:
Detach any USB cable connected to the watch
Turn it off holding the power button and keep holding the button until the watch vibrates three times and then switches it off
Press the power button and keep holding. A blue screen that prompts to insert an USB cable will display
Double tap the power button
A black menu will display, with on-screen instructions
Move to Fastboot or Recovery Mode pressing the power button, once a time
Select Fastboot (or Recovery) by double pressing the power button
Good luck bro.
swidon said:
Yes!, follow these instructions and you can enter in fastboot or recovery and flash a new firmware:
Detach any USB cable connected to the watch
Turn it off holding the power button and keep holding the button until the watch vibrates three times and then switches it off
Press the power button and keep holding. A blue screen that prompts to insert an USB cable will display
Double tap the power button
A black menu will display, with on-screen instructions
Move to Fastboot or Recovery Mode pressing the power button, once a time
Select Fastboot (or Recovery) by double pressing the power button
Good luck bro.
Click to expand...
Click to collapse
you are my hero... stock recovery flashed and sw3 reboot! thankyou so much bro
jerry_italia said:
you are my hero... stock recovery flashed and sw3 reboot! thankyou so much bro
Click to expand...
Click to collapse
How do you go about getting stock recovery back at the moment I'm on 5.0.1 and I can't ota update to 5.1.1 because it thinks its on 5.1.1 when it's not the only way I can think of updating it is to get stock recovery then sideload the ota zip on stock recovert but I can't do that with TWRP can someone help?
Hi,
My watch boot loops on the marshmelow boot animation after I Got marshmelow
I tried XorZone instractions and it said it re-updated image. but it will boot looped.
I tried to factory reset from the menu (double tap at download screen then go factory reset).... didn't work. still boot loops.
I see I can go to fastboot or recovery, but what do I do there? Any instructions I can follow to try to revive my watch please? thanks.
wonderfull!
XorZone said:
Well, there are different levels of bootloaders
At least Sony s1 flash, fastboot, kernel...
To flash with PC companion you need to boot into s1 by powering off and then hold power and connect to USB once sony logo shown (you should see black screen with backlight on). Make sure you sit on PC companion update screen and that watch had enough juice.
With charging there are different levels of charging:
1. Battery dead
2. Boot loader charging (about 4 min from USB port) with black screen
3. Kernel charging either offline (if you powered off before) or boot and operational charging.
When #2 charges it will boot kernel and if kernel or system is broken it might hang and discharge.
But you can force into s1 flash mode before it boots into kernel. Or if you lucky you could power on and power off before it boots and hang.
In my case I had not enough juice to flash it and watch didn't react to button in kernel mode, so I had to wait for discharge, then plugged into USB and start timer, figured it boots after ~3min 55sec. So I opened PC companion update screen, waited 3:53 and disconnected watch, then hold power button and connect to PC after 5 sec and was able to flash.
To power off - just hold power button until it reboots and continue holding until it vibrates 3 times.
Good luck
Click to expand...
Click to collapse
Hello Everyone!
I recently tried to root my wileyfox swift but failed miserably. I did the following when fastbooting the recovery image -> fastboot flash system ****.img.
However, i realized my mistake too late, and now my phone is all messed up!
The phone doesnt show anything when i try to start it and i cant access fastboot again, to undo my mistake. My device manager recognizes my phone when its plugged in to my computer but i cant access any files.
Am i screwed or is there any solution to this?
Thanks in advance!!
Try to access the bootloader with the hardware button combo first (volume down + power / volume up + power). If you get into recovery, you will be able to get to the bootloader with adb or a menu entry. Depends on what recovery you have installed for the latter.
In case you have no access to the bootloader (proper soft brick), go for the QFIL method. Avoid using it unless there is no other option.
Here is the thread:
http://forum.xda-developers.com/wileyfox-swift/general/how-to-set-device-tampered-to-false-t3276317
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
Does the phone give any indication of being connected? Notification light, starting the display, etc?
If yes, make sure the phone is in the correct mode and check the drivers - some of the other forum members mentioned this and the gymnastics around the battery. This would be on my to-do list. The device might come up on the device manager as different one, so monitor the manager for any changes once you connect the device.
If you happen to have Windows 7 device laying at you house, you can try with it (if only not to worry about compatibility and sporadic Win10 behaviour).
It will be a good idea to check the turkish website for General Mobile 4G (one of the Android one derivatives of the hardware) where some people have faced similar problems using the same tool.
narmista said:
Cant access bootloader.
However, tried your second option and it went well until i got "SaharaDownload fail" at the last step, and now my computer doesnt recognize the phone in device manager. It does not show anywhere that my phone is connected.
Click to expand...
Click to collapse
If you need my help via TeamViewer then WhatsApp me at +27799261595 or pm me
Finally got my phone back on the device manager! However, I still get sahara error when trying the back to false method.
imgur.com/a/FsSX0
*It says no port available since i removed the phone*
Hello Gurus,
Well i am trying to boot my phone into download mode but i am continuously getting
secure booting error 1014 and my phone then boots lollipop 5.1 which is stock rom.
my lg g4 model is h81510h build number lmy47d, it is not rooting or flashed anyway.
I want to flash flash marshmallow kdz with lg flash tool but my phone is not booting into download mode, please help or suggest any other method
HALP PLS
I'm having more or less the same problem. I bought a used H815 and it came with Android 5.1 (software version h81510h)rooted and stock recovery. I tried upgrading to MM over OTA but tapping Update Center leads me directly to the App Update screen instead of giving me a choice between software update and app update.
That is when I decided to go the KDZ route but when i tried switching the phone to download mode it went there and in the top left corner there was this 'Secure Booting Error 1014' message and then it restarted in about 5 seconds. I have tried this multiple times with the same exact result.
ADB detects my phone but when I send the 'reboot bootloader' command it just does a plain reboot so I can't use any of the fastboot commands. I also have no idea whether this phone has an unlocked bootloader or not.
Also for some weird reason my phone is not using the MTP mode when I connect it to my PC. It either uses PTP or charge-only depending on what I select but if I select MTP it automatically reverts to the previously selected mode. LG Bridge doesn't detect it and neither does the Mobile Support Tool but I can transfer images just fine. MTP was working last night but it suddenly stopped working and I have no clue why.
I can get into the recovery without any problems.
Please help me get it working again
you-mair said:
I'm having more or less the same problem. I bought a used H815 and it came with Android 5.1 (software version h81510h)rooted and stock recovery. I tried upgrading to MM over OTA but tapping Update Center leads me directly to the App Update screen instead of giving me a choice between software update and app update.
That is when I decided to go the KDZ route but when i tried switching the phone to download mode it went there and in the top left corner there was this 'Secure Booting Error 1014' message and then it restarted in about 5 seconds. I have tried this multiple times with the same exact result.
ADB detects my phone but when I send the 'reboot bootloader' command it just does a plain reboot so I can't use any of the fastboot commands. I also have no idea whether this phone has an unlocked bootloader or not.
Also for some weird reason my phone is not using the MTP mode when I connect it to my PC. It either uses PTP or charge-only depending on what I select but if I select MTP it automatically reverts to the previously selected mode. LG Bridge doesn't detect it and neither does the Mobile Support Tool but I can transfer images just fine. MTP was working last night but it suddenly stopped working and I have no clue why.
I can get into the recovery without any problems.
Please help me get it working again
Click to expand...
Click to collapse
Any update ? I am also facing same issue. One wierd thing I noticed that adb devices displays phone as "LGLS991" can you tell me your result of adb devices ?
Im having the same problem.
Lg bridge, lgup and flashtool not detecting my phone. How to flash my phone with any os? Kindly help me
Same problem with my H811. Any solutions?
I cant get my g4 into download mode. I was able to earlier but it died on me. My buddy has the same phone so I am using his fully charged battery now (mine was around 40$) but I'm still getting nothing. Should I reformat the SD card and try again? I can't think of anything else.
Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
After a lot of trials I could solve the problem, but I dont know what I did different.
I did everything the same.
Anyway thanks to everybody who read.
Regards.
hagiwatt said:
Hello Guys,
My Lenovo P1A42 is stuck in Lenovo logo bootloop.
I tried to flash the stock rom "P1a42_S288_160721_ROW_RAW_QFIL" with QFIL.
So with QFIL, I see the Qualcomm HS-USB QDLoader 9008 (COM3).
I select "P1a42_S288_160721_ROW_RAW_QFIL\prog_emmc_firehose_8936.mbn" for programmer path.
I select build "P1a42_S288_160721_ROW_RAW_QFIL"
I also select rawprogram0.xml and patch0.xml.
It takes about 10 minutes to download and in the end "Download succeed. Finish download" message appears.
After this step, I press power+vol up+vol down together for around 12 secs to let the phone start with the downloaded new rom but again the phone goes to lenovo logo bootloop.
I have been continuosly searching for the solution but I still could not find it.
Probably I am missing a very small detail.
Can somebody please help me with this problem?
Thanks in advance.
Regards.
Click to expand...
Click to collapse
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
hagiwatt said:
Dear pavanpilot94,
Thank you for your message.
I had already made the procedure following the instructions in the link you sent to me. In the end of the download "Download succeed. Finish download" message appeared, but it did not restart automatically.
That is why as mentioned in the instructions you sent; ("If "ready" message appears and device does not go to reboot, then hold Volume UP + Power buttons for ~12 sec.")), I had to make the key combination.
But everytime the device went to reboot the old Android in the device, so flashing was not successful.
I do not know where the problem was. After many trials, I could flash successfully, but everytime I had to do the same things. I did not make anything different.
Anyway the problem is solved now, but next time flashing, I do not know how to avoid this problem.
Thank you very much.
Click to expand...
Click to collapse
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
pavanpilot94 said:
I now understand very clearly hagiwatt,
I'm happy that Device is back!!! :good::good::highfive:
On a Guess from the above understood there might be corrupt emmc locations, For this to be verified we might have to format the entire emmc. I'm too stuck with Logo Screen now, Unfortunately my Device is not getting detected by the Computer(Qcomm QDLoader) to have it flashed.
Trying to Fix it, I did a entire Format & Verified any Bad sectors as suggested by one of the developer, Unfortunately still not able to get the device detected.
Click to expand...
Click to collapse
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
hagiwatt said:
I struggled for it since I wanted to send the device to warranity for vibration problem. I am happy that I could flash with the raw rom. I also wanted to reset the binary counter but no way.
Triangle Away does not support Lenovo.
I hope they are not checking the binary counter in the service center.
Does anyone have an experience about it?
Thanks.
Click to expand...
Click to collapse
Hi Everybody!
I have just recieved the phone from service center. They fixed the vibration problem under warranity.
So binary counter did not affect the warranity status.
I dont know if they checked the counter or not.
For information to anyone who has the same issue.
Regards.
pavanpilot94 said:
Please follow Getting Ready and Flashing ROM from the link https://forum.xda-developers.com/vibe-p1/development/qpst-flashing-vibeui-3-1-s272-rom-t3386650 . Once Success, The system/Phone reboots itself, You need not hold any combination of keys to reboot
Primarily make sure Your PC?Laptop detects QComm Driver when you Hold Vol Up+USB. If the device is detected and Driver not installed, You can install the same from the above link.
Verify the above using Device manager.
Click to expand...
Click to collapse
and if the pc did not detecte the phone and i cant see any thing new in device manager ,plz help me
I am chasing the Z2 Force 1789-04 OREO ROM as released by AT&T in the OTA update.
I am using one in Australia (works great on Telstra) and I believe the reason I can't get the OTA update because I am not on the AT&T network. (Although I have had OTA updates on Taiwan model ASUS phones before).
Searched the web and XDA high & lo and there is never any mention of this one.
The software version of mine is also stuck.
And when I go and check if there is any update,it will say that my system is up to date.
dijia1124 said:
The software version of mine is also stuck.
And when I go and check if there is any update,it will say that my system is up to date.
Click to expand...
Click to collapse
Same as yours
Install Lenovo Moto Software Assistant on a Windows PC, enable USB debugging on the phone, and connect via USB to PC (assuming drivers are installed). The software will allow you to download the update and install via fastboot. This will wipe your device, so be sure to back up your data.
209pcs said:
Install Lenovo Moto Software Assistant on a Windows PC, enable USB debugging on the phone, and connect via USB to PC (assuming drivers are installed). The software will allow you to download the update and install via fastboot. This will wipe your device, so be sure to back up your data.
Click to expand...
Click to collapse
Stuck on 7.1.1, system update saying up to date. This method I used to get oreo but with July 1 security patch which broke fingerprint option?
Lenovo Assistance is still saying OCXS27.109-47-11(July patch) is the lastest
Oreo Update
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
westec2 -
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade.
Click to expand...
Click to collapse
Unfortunately, I am unable to replicate this. When I turn off my device, LMSA reverts to not seeing the device.
I've tried to use the RESTART BOOTLOADER option which seems to do something, but even though LMSA advances to 100%, the update didn't actually do anything.
So, I'm still stuck.