Database Develop

LGWR only vibrates, no display whatsoever, does not connect via BT or USB cable.

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.

Oddest Brick Ever - Kindle Fire (Tate)

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!

Mi A2 BOOTLOOP can't get into Fastboot or Recovery

So i followed this guide to root my Mi A2 "theandroidsoul (insert dot here) com/xiaomi-mi-a2-root/"
It went all fine but the phone was still not rooted. So i thought maybe get the newest Magisk.zip wich i put on the phone.
So I went back to step 11. to install the new version with TWRP but it didnt go to TWRP although i held the volume up butten and then used the command "fastboot reboot" and then it weent into bootloop
so i Guess i am stuck on my Partition A (in my case) where i installed TWRP but i cant shut the phone dont to get into fastboot and ADB says Error: no device Found".
I Need Help plssss :crying:

If you cant go to fastboot then you need open up phone and use testpoint to force edl mode
But before that hold volume down and power for 10-15 sec to force fastboot

The battery is drained now, i tried to plug it in to the wall and boot into fastboot right away, i saw the fastboot screen for a splitsec but it cut off because it had not enough charge, so i left it plugged in and tried to go to fastboot constantly till the phone had enough charge to hold the boot, i was in fastboot for about 1 minute or so (my plan was to charge it in fastboot mode, leave it like that and then go to the pc to change the active partition back, but the pc didnt recognise the phone) but after that it startet bootlooping again while it was in fastboot.
Could i try to got to TWRP with "volume up + power button" ? and change the active partition in there?

Facing almost similar problem like you yesterday.
Try method I post here
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page24
1. Have phone in fastboot mode
2. Launch adb cmd (NOT your pc usual cmd)
3. Connect to pc, type 'fastboot devices'

Mi A2 won't boot past Android One

I charged my Mi A2 overnight and woke this morning to find that it won't boot past the Mi A2 splash screen; it shows the splash screen for a few of seconds and then dies. I read advice to hold down power and 'up' keys, this just resulted in the same. I tried power and 'down' key and that got me as far as the Fast Boot splash screen, but no further (phone just continued to display that splash screen). I've tried taking the SIM out and turning it on - no change. I tried opening it up and disconnecting the battery for 3 minutes - no change. I'd be very grateful if anyone could suggest a fix. I know this is hugely unhelpful, but I can't remember what I did to the phone in terms of unlocking the bootloader and/or rooting, but I have a feeling I left it stock (I've owned the phone for a couple of years and haven't changed anything material since initial setup).

Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?

Martinocom said:
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Click to expand...
Click to collapse
Thank you very much for your help.
Executing fastboot reboot via adb just brought me back to the Android One splash screen for a few seconds before the screen went black.
Changing the active slot to both A and B gave me the following error message:
FAILED (remote: 'Slot Change is not allowed in Lock State')
Pressing up + power when turning on just brought me to the Android One splash screen for a few seconds before the screen went black. I held those two buttons down for several minutes and the same thing kept happening: splash screen followed by black, repeatedly.
Is there anything else I can try?

You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!​
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.

Martinocom said:
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!​
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Click to expand...
Click to collapse
Thank you.
If anyone reading knows of a way to get my phone to boot without losing my data I'd be very grateful for your help.

Question Stuck in bootloop, cannot reach fastboot

Hey, I have tried flashing a GSI ROM but got an error after attempting these two commands :
MrScarl3t said:
./fastboot erase system
./fastboot flash system Gsi.img
Click to expand...
Click to collapse
The "system" partition could not be found and after reading some of your comments I figured I had to reboot into fastbootd and not fastboot. Therefore I rebooted my phone but I am now stuck into a bootloop without being able to reach fastboot whatsoever. Holding down the volume down key does not seem to have any effect.
A few more details:
- adb does not detect my device anymore.
- I was previously on a stock ROM.
- I only managed to flash the vbmeta.img before the bootloop happened.
- Upon holding the volume up button, my phone briefly connects to my PC (for about 2 seconds) then disconnects and restarts again.
What could I do to be able to reach fastboot and flash the stock ROM again?
Thanks for reading

Hold power button + volume down button for 30 second if fails then drain the battery then repeat the process.

My battery is drained and no matter how long I hold the two buttons I can't get out the bootloop unfortunately...

-let the cable connected to pc and press (+ and power) when the splatch screen appears wait 3 secondes and release the power button keeping + button only.
-if not, try with an OTG disk inserted and do the same as above.
-if not, type on pc terminal: adb reboot recovery before connecting your phone.
Good luck.

Hey, thanks a lot for your reply
I have tried all the steps you've described me and I unfortunately can't reach recovery.
It seems as if the phone is reacting to it though as a black screen screen is displayed much longer than usual, although a few seconds later, the MI splash screen appears once again. Also, I can hear the beep from the pc when the phone connects but it keeps disconnecting 1 second later and proceeds to reboot. Seems like recovery is corrupted or something...
The phone does not show up under adb devices throughout the whole process. My pc only recognizes the usb port being connected (when the beeps are triggered) but does not identify the device as an android device.