I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Lirezh said:
I had android GE 4.3 on it, rooted.
I have the original GE bootloader (that robot) installed.
I downloaded the official 4.4 update through android, rebooted for install.
Now after the install the phone does not boot up anymore, instead it goes into RECOVERY and shows that triangle robot.
I tried wipe of cache and data wipe.
Whatever i try I am not able to get this device into fastboot / bootloader anymore!
It takes longer than usual,, it is stuck in that HTC screen since I have unlocked the bootloader but it does not enter the usual menu.
Instead it just directly goes to the robot.
I tried about everything I could think about,
It seems the OTA really bricked my phone by damaging the bootloader so it does not load at all anymore.?!?!
The only USB accessible feature I see is that in the robot screen it registers a device through USB.
Sadly not ADB or fastboot, it is a volume. It even loads as volume but is inaccessible (like a CD without disk)
Windows recognizes it as WDP FileSystem.
I doubt this will help at all, just wanted to note it.
I am about to throw the phone into trash, if it had not been so expensive.. Anything that can be done to repair this brick ?
Click to expand...
Click to collapse
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Alfa Kenny One said:
Now search for the right adb and fastboot driver. There is a .msi installer (adb + fastboot .msi) something like that. Than push the right recovery via fastboot. Voila
Click to expand...
Click to collapse
Hi,
I solved it.
It took about 30-50 reboots until the phone entered the fastboot menu.
The problem was that the phone kept skipping the whole fastboot menu and went into recovery instead.
A very strange firmware bug caused by the failed OTA
Hi guys,
I bought my Nexus 6 (64gb version) in December 15 from Amazon, the phone was perfect up until last month when it started randomly rebooting and most of the times it's stuck on the Google logo. At first it happened once or twice a day, now it happens every couple of minutes.
The phone was stock, I tried a number of things but nothing helped:
*Wiped cache partition
*Wiped data and factory reset
*Tried creating a new google account with no previously installed apps and no restore app data
*Unrooted the device and flashed Dirty Unicorn
*Flashed stock firmware again from Google
Is there something else to be done which I missed. The phone is as good as a brick now, reboots a dozen times a day...during calls, texting, playing games or even when just browsing through it.
I contacted Google and they said they'll transfer me to Moto who in turn offered a replacement device. Problem is I live in Bahrain and the warranty is for US only. I got the phone for 260 bucks.. and shipping it to the US and back won't cost me less than 50, and how can I be sure that the replacement will not have the same problems after a while.
So in short.. Help!
Does the reboot happen on the factory img? I would suggest returning the device to 100% and see if the reboots continue. best way to do this is back up internal storage. then follow the steps:
1. download latest factory img from google
2. use 7zip to break down the zip all the way to the folder structure.
3. open up a CMD on your pc.
4. make sure ADB and fastboot are working before moving on.
4a. type "adb devices" (should show S/N of the device and connection status)
4aa. adb reboot bootloader
4b. in booloader mode type "fastboot devices" (should show S/N of the device and connection status)
5. fastboot flash bootloader "name of bootloader.img" ( you can drag and drop the img after you type the first part if paths are not set up on the device.)
6. fastboot reboot-bootloader ( you must do this when installing new radio and bootloader)
7. fastboot flash radio "name of radio.img" ( you can drag and drop the img after you type the first part if paths are not set up on the device.)
8. fastboot reboot-bootloader ( you must do this when installing new radio and bootloader)
once that is done unzip the image-shamu-**** you will now see each partition img. Just flash one at a time.
recovery
boot
system
userdata
now if you dont want to have encryption enabled on boot you will need to find a boot img on here that has been edited to remove that option.
If the devices is still rebooting then its going to be a hardware issue and it will need to be sent back. Hope this helps.
Hi wolf,
I already flashed the factory img from google but I did it via the Nexus Root Toolkit, not how you mentioned.
Same problem, nothing changed.
I cannot understand if this was a hardware issue, it should've happened from day 1.. why did it take few months to happen. I was suspecting the power button but it works just fine. My buddy got one just a week after me and his is functioning just fine.
I read so many other posts about people facing the same problem.
My frustration is just killing me.
*edit* I just rebooted the device in Safe Mode and it started vibrating and wouldn't stop. Had to power off.
I am new to the forums and I need your help. The display on my LGWR went black after update even on cradle. It cannot even connect to my mobile via BT. The only thing it does is vibrate when the button is pushed and the heart sensor blinks a single time (when it turns on I guess.) as the vibration is a small one. When connected to PC running Windows 7, it is detected as Android Bootloader Interface, but ADB does not show any attached devices. Fastboot does show some alphanumerical device when (fastboot devices command is run). I have disassembled to remove the battery and tried to run it without the battery on cradle to no avail. Your help is needed as to what to do.
So it seems to hang in fastboot mode?
Try some fastboot commands then:
Code:
fastboot getvar all
fastboot reboot
Dear Ranf.
Many thanks for your reply. I ran fastboot getvar all and this is what I got. Screenshot is attached. Please guide me further.
Thanks.
Looks like you already downloaded the firmware? Right?
If so start with wiping cache and userdata:
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
I have downloaded the M1D63X boot, recovery and system (Disc Image Files) saved in my PC. They are not present in the SD card of LGWR. Shall I execute the commands or can I use fastboot and install this M1D63X on the LGWR. Thanks for your support.
The 2 format commands are basically the same as a factory reset. Please try them and then reboot.
Where did you download the file (URL please)?
Boot and recovery usually aren't trouble makers. system.img will if it's not a sparse image file.
The download like is as under Ranf:
http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Dear Ranf,
I tried to run Fastboot flash cache, and this is what the result was. Please guide.
Oh I see: you first need to unlock the bootloader with:
Code:
fastboot oem unlock
How can I dod that, as the screen is blank on the watch. I have tried it, fastboot says OKAY on my PC screen, but the watch does not reboot on its own and I have to manually restart it to get recognized in PC at Android ABD Interface. What can I do.
After running "fastboot oem unlock" you somehow need to acknowledge your decision (I'm a Sony SW3 user)
Either swipe the screen from tp left to bottom right or
press the power button.
Do you see anything on the watch screen when in fastboot mode?
Dear Ranf,
I finally able to unlock bootloader and formatted cache and userdata and then rebooted it, but the problem still exists i.e. black screen and only vibration.
Is there any way I can install stock Rom via fastboot and if so please guide me how and from which url should I download the files.
Thanks.
Screenshot of the fastboot format cache and userdata is attached for your perusal.
At 1st look the download you have is fine.
You need to flash 3 partitions:
Code:
fastboot flash boot M1D63X_boot.img
fastboot flash recovery M1D63X_recovery.img
fastboot flash system M1D63X_system.img
When you see errors at any of these steps post them here.
Thankfully all things well without any errors, but the watch is still the same, no display whatsoever. I am really devastated now. If there is anything else that can be done, please guide.
Screenshot of the processes is attached.
Sorry I must admit I'm a bit lost now. Best you ask @vt0r in the thread where you got the firmware from.
Thanks a lot Ranf. God Bless You.
You have done all steps that you can do, probably your display is broken...
I'm sorry...
When your watch starts, you see the lg logo?
Is there a way to check if the display is broken as when I disassembled the watch everything looked fine with no signs of wear or moisture. The battery also is not holding charge as when you put the watch on cradle it vibrates but off of it, vibration stops. How can I charge the battery manually.
Hey,
my watch had exactly the same problem.
I had to repair it. They had to replace the mainboard.
Luckily the warranty paid for this.
Lucas
Lucky for you that you had warranty left. For me there are two problems. First no warranty left and secondly replacement parts are not available here in Pakistan, so if there is any online store from I can manage the parts, do let me know Lucas.
History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!
So this watch was of my dad. One day it went into bootloop ....rebooting and stuck on lg logo. So first i unlocked its bootloader using fastboot commands. Then i tried to flash various roms,recoveries..but no luck. Basically only fastboot mode can be accessed..
When i try to go in recovery it just shows a black screen and reboots...so no adb
Any way i can revive it...?
Same problem here...
Use Fastboot to reflash all three image files. You may need a new battery first that is what caused my watch to start boot looping.