Hi,
I tried to sideload AW 2.0 through ADB, and everything was working fine. However partway through the update failed, and it said "failed to read command". The watch is now simply stuck on the LG logo. I've tried to sideload it about a dozen times now, but every time, part way through (at varying levels of percentage) it fails and says either "failed to read command: no error" or "failed to read command: invalid argument". I can't seem to find a similar issue elsewhere, so any help would be greatly appreciated.
Thanks
I had the same issue, tried everything I could think about from changing USB ports, to replacing the connecting cable, to placing the file to a different disk on my PC.
Eventually I got the process to work 100% when I used my Galaxy S7 charging cable instead of the LG one, also I took out the wristband from the watch (but I doubt that was the reason) to have a completely leveled area to sideload the update. It took me ~30 tries but finally succeeded.
Be resilient is all I can say.
I had no luck getting aw 2.0 to work so I decided to get back to 1.5
I flashed AW 1.5 system.img and boot.img and I ended up with a bootloop!!
I reflashed them again but also a bootloop!
What could I do! Please tell me
Related
Hi eveyone, I've been a lurker here for quite sometime...until now. I'm trying to use BionicRestorer.sh to flash my bionic back to 902 so I am able to receive the OTA update. My phone was rooted and failed to update everytime. After several factory resets and even unrooting it still would not update. I'm trying to use the above to flash back to 902. I've read every post and FAQ regarding Linux and SBF and all files are in the correct location when it comes time to use House of BIonic I get this message in terminal:
./utils/fastboot.linux: 3: Syntax error: "(" unexpected
./utils/fastboot.linux: 3: Syntax error: "(" unexpected
Press Enter to continue when the phone is back in AP Fastboot
The phone is in fastboot with a fully charged battery using a factory cable and plugged in to a rear USB port. I know it's communicating with the device because House of Bionic actually puts the phone in fastboot. I've tried manually putting the phone in fastboot with the same results...I've been at this for hours now. Someone please give me a little insight!!
I've had my Verizon LG G2 for almost a year and mistakenly upgraded to Lollipop. I researched downgrading to KitKat and it looked safe; I had dual booted my HP Touchpad with a similar process.
I tried rooting with ADB, but it was giving me fits. I used the LG One Click Root Tool. It worked fine. (Running on Windows 7.)
I installed TWRP v2.8.5.1, and downloaded a stock version of KitKat 4.4.4. (I'll admit, at this point, I had looked at multiple guides. Many had missing links or dead ends, but they were all about the same, and always stock.) I followed instructions on clearing and wiping caches, etc. I believe the exact ROM I tried to install was VS98011A_01.zip. It didn't work. It gave the error:
"assert failed: run_program("/tmp/loki.sh") ==0
E: Error executing updater binary in zip"
I looked for more ROMs and tried ParanoidAndroid "pa_g2-4.0-ALPHA-20131203-vs980.zip". At this point, I started to worry and tried installing the Gapps file I downloaded with the stock ROM, and it installed with no problems.
I then tried to install a newer version of TWRP "twrp-2.8.6.0-vs980.zip". (Again, I hadn't really found any great guides at this point, especially to fix my problem, so I was assuming there was something wrong with my ROMs.) It didn't work, and I tried to install Cyanogen Recovery because I ran across it and remembered it from my HP Touchpad. "cm-10.2-vs98012b.zip" did not work, and gave the error above.
I looked for Loki issues and tried downloading a fresh Loki (sorry, I don't have the link) folder and replaced all the files in the original KK .zip I tried. Same loki error. (Sometimes I'll get a "sysMapFile" error, but not often. At this point, I'd dragged a lot of things over to try to install and get anything to work.)
At this point, I tried the following:
http://forum.xda-developers.com/showthread.php?t=2448960
http://forum.xda-developers.com/showthread.php?t=2451696 (as well as a similar one by downloading a laf.img)
http://forum.xda-developers.com/showthread.php?t=2797190
http://forum.xda-developers.com/showthread.php?t=2432476
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
http://forum.xda-developers.com/showthread.php?t=2318497
http://www.androidayos.com/2014/10/06/fix-bricked-lg-g2-stuck-logo-twrp-bootloops-download-mode/
http://forum.xda-developers.com/showthread.php?t=2448960
There were definitely some more links I used but these were the most promising and the ones I still have open.
Several of the LGFlashTools were very close to working, but there were several issues:
1. I can't get it into Download Mode, as it gives a boot certification error.
2. There were some problems with the phone not showing up in Device Manager under "Ports" with COM41, and I thought I had largely resolved that issue. (Depending on the article I was looking at.)
3. Drivers, I'm not sure if they're an issue; I've downloaded several, and installed them, including 2.0 and a 3.1.
ADB does not recognize my device, as I've tried sideloading, although I can still drag and drop files. (I believe I pushed a file into the device early on and it worked though.)
4. Fastboot recognizes there's a device and can boot it via CMD but will not give a number when I use "fastboot devices". I've researched some flashing via Fastboot, and tried flashing the original KK .zip with it, but it said there wasn't enough space. I have about 14GB left on a 32GB device, however.
I hope I've provided enough information, because I've researched and tried so many ways to unbrick it, short of physically opening the phone as suggested here: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Any advice or suggestions would be greatly appreciated. I would love to know what I did wrong, because I know custom ROMs would be a great alternative to dealing with Lollipop until I can upgrade over a year from now.
Hi guys,
I am trying to help out a mate and unfortunately dont have much experience with HTC's.
This is where i stand...phone wont be recognized in normal boot, nor in TWRP, so adb is not working at all. FASTBOOT works.
i have been circling around with locking and unlocking the bootloader to try out all the methods of updating the system, RUU fails with error 155. when unlocking, supercid fails with some java error.
To get S-OFF, i definitely need adb to load the "much talked for" file, but that is impossible right now.
RUU normal way fails as i said above, so does FUU with rom.zip (found away to get it out of exe, so it is untouched) as soon as it "updates signatures" it'll fail, I even use the fastboot command with the renamed file firmware.zip ends up saying it cannot verify partition ...adding zip after flash command says file is out of size
I am on 4.20.651.10, and trying to get the latest package, and am out of ideas. I found out the hard way that if i lock back the phone, it wont boot to TWRP and nor on a modified system.
I am really not sure what to do, having adb on would've spared me a lot of trouble. Friend says the USB port has been changed twice, it is so odd to have fastboot and not even a single refresh in Device Manager when i plug the damn phone on...
There are more replies to question threads outside the Help section then in here...
Anyway, i lost fastboot too, and no idea why. tried in two pc's, one of them with 3 different os's, tried two macs, tried even an OTG cable with my other android phone, nothing.
I cant even relock the phone so i can update through the RUU ZIP in the sdcard, but that's a scratched off solution if no USB connection is delivered.
I even tried the S-Off unlocking file on /data/local/tmp, but it doesnt seem to execute from TWRP terminal, and ofc it wont through a booted system either...
I managed to install a custom rom since i have no OS, and tried the "AndroidHtcSync.apk" solution to no avail
i seriously hope anyone has the will to help me...
EDIT: port is definitely fine, as the phone charges from the charger, and fastboot shows "fastboot ac".
EDIT2: fastboot is back... renamed the zip in sdcard, now it fails flashing there too with "Device halted due to large image update fail"
I have had issues with my zenwatch 3 being crazy slow on android wear 2.0, and i read some possible solutions..
I also have an issue where whenever i turn my watch on it says "device software cannot be checked for corruption" and it makes it take an additional 10-15 seconds to boot up. This has been on the watch since i got it (i bought used and the bootloader was already unlocked, if thats why its doing that. When going through forums I also saw mention for disabling dm verity and wondered if that would get rid of that annoying screen.
I wanted to see if i could remove the zenfit stuff, cause i saw that some users claimed speed improvements, so i flashed twrp, and when i booted in i accidentally said to allow modifications (even though now i see that people say not too). I didnt make any changes while in here, but thought that might be important to state. In the instructions to remove zenfit i again saw to disable dm verity, so i moved onto that.
I then connected through adb and ran the command fastboot oem disable_dm_verity, but that didnt seem to do anything. I then ran the command "adb reboot "dm-verity enforcing" which i dont think was a good one to run, and i wonder if caused my issue. When i tried to boot back into twrp it would boot to a dead android.
I decided at this point that instead of screwing things up further, i would just flash to AW 1.5 and hope for speed improvement there. I downloaded the files, and through fastboot flashed the stock 1.5 boot, system, and recovery. using this thread https://forum.xda-developers.com/ze...stock-zenwatch-3-partition-dump-boot-t3535589
i rebooted the device and it went to the android wear screen and loaded for a while, and then to the upgrading android screen. when it got to step 7 it went back to the aw loading animation and then attempted to boot up and gave an error "unfortunately process android.process.acore has stopped" and started all over again trying to upgrade android and then getting to this point and failing. I then downloaded the images for stock 2.0 and flashed and got the same exact error.
I then tried to flash twrp again, and now if i try to flash 1.5 or 2.0 it just goes to a dead android screen. I can boot into twrp still with the boot adb command
I want to try flashing 1.5 or 2.0 through trwp, but my watch will not mount/connect at mtp to my PC while at twrp for some reason...
Any ideas or solutions? how can i flash everything straight back to default. Including whatever i may have done to the dm verity?
Please help
If ADB and Fastboot is working on your watch, try this
csrow said:
If ADB and Fastboot is working on your watch, try this
Click to expand...
Click to collapse
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Coltonbyu said:
Thanks for the help, but this wont work either. 2 issues
1. I forgot to mention this, but since posting i have found that my system partition will not mount correctly, and the data partition will not mount at all, meaning that i cant do any wipes or resets through twrp because it fails to mount
2. When i try to do the adp push, it fails and says no space left on the device, but this would be because the partitions wont mount. I also cannot connect to the watch through mtp to copy files to it.
any advice?
Click to expand...
Click to collapse
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
csrow said:
Did you erase userdata? If so, go back to fastboot and try
'fastboot format userdata'
That should allow you to mount the data in TWRP and also allow you to push to /sdcard/
What do you mean by system partition will not mount correctly?
Click to expand...
Click to collapse
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Coltonbyu said:
Son of a *****... you did it!!! oh my goodness... I cannot even begin to explain how big of a relief this is, and how happy i am right now!!..
I didnt even go back and reflash the boot, rom, or recovery yet. I just ran that fastboot command and put in the reboot command and let it go. It booted into android wear and is on the get started screen.... Oh goodness.... Thank you so much...
At this point i honestly felt so hopeless. I didnt think there would be anything else i could do. I had tried EVERYTHING that any forum could suggest. I had flashed back and forth between 1.5 and 2.0 at least 10 times, using slightly different steps, and trying again to see if i missed anything. ( i must have ended up on an odd number, because i am now on android wear 1.5!!)
Click to expand...
Click to collapse
Glad it worked out.
If you want to stay at 1.5, you know what to do.
Hey!
So i'm making this post after battling over 4 days with my friends old oneplus 3t.
All started maybe year ago when my friend asked me for help because his oneplus had suddenly gone into a bootloop kind of state (he told me that the phone was in his pocket working fine and when he tried to use it next time it started acting up.) Before i could even help him he had already bought new iphone, so the oneplus stayed in his drawer until last week when i remembered it and started to try to fix it.
So first thing that i noticed was this message "The dm-verity is not started in enforcing mode and may not work properly", the message eventually went away and i got to a recovery mode and thought that this is gonna be easy, hooked the phone to pc and started adb and tried to sideload the official rom from oneplus site, but everytime i tried it went to maybe 47 %or 66% and failed eventually. So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
Downloaded Oneplus 3T unbrick tool v3.0, and qualcomm drivers (turned windows driver signature off) everything went great and the green text came in oneplus unbrick tool and i proceeded to start the phone in excitement and the circling bootlogo started and it just stayed there, nothing, and after while shut down.
Things tried now:
-Sideloading (many times with different roms) no success.
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
- Unbricktool v3.0 (Works like a charm everytime, but phone doesent still boot to os) no success
-recovery (wiped cache and all data many times) no success
My friend never flashed anything to this device, he doesn't even now how to do this kind of stuff.
Phone not dropped even once, is in a perfect condition and has all the original stickers even.
I have grown obsessed to fixing this phone, so any help is greatly appreciated :laugh:
onlyoneplusproblems said:
So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
Click to expand...
Click to collapse
I haven't personally ever had to use the unbrick tool, so I can't help too much with the core problem. But what I can say, is that the steps I've quoted above (trying to flash recovery partition, etc.) are going to fail by design, since the bootloader is locked. This is the very purpose of the locked bootloader. The expected result is "remote: not allowed".
And as far as I am aware, you have to have a working OS and have "OEM unlocking" first toggled on, in the phone Developer settings. Otherwise (again, by design) the "fastboot oem unlock" command is going to fail.
Spontaneous failure of the phone to boot to OS, and dm-verity warning, to me probably indicates the OS has become corrupt/damaged. The damage is showing as a change to the system, therefore the dm-verity warning. Normally, I would tell you to flash the stock recovery image. But of course you have already tried that. Probably difficult to determine for sure. but spontaneous failure, and failure to flash recovery image (multiple times) may indicate a hardware failure such as bad emmc.