Boot loop EASY FIX - Amazfit

Just attach watch to CHARGER. THEN , re-download a different face. I hope that you already paired phone otherwise, you outta luck.

Related

Viewsonic VSD220 - hardbricked

I unfortunately hard bricked my VSD220 the other day while trying to upgrade the android system. Bit of a noobie at this and learnt the hardway. The problem I have now is that the unit powers on but i get a totally black screen and a small panel saying "waiting" this disappears and then after a minute or so the unit powers off.
I have tried a number of flash tools using ADB and the device is not located. I cannot get into boot mode on this device as it has only a power button.
Apart from using this as a fishing sinker is there any other flash tools I might be able to use to do a lazarus on this thing and bring it back from the dead?
When plugged into the PC and turned on it is not recognized.
I have tried the Nexus root tool kit and Odin but Odin cannot located the adb for the device. cheers.
Exactly same thing happened to me but I wasn't trying anything weird on it, It happened while doing a factory reset (from android settings) and it just went off in the middle of factory resetting so now the only thing that works is plugging in a HDMI input so it works as a TV but still shows the "waiting..." box for a while and then nothing.. I also connected it to the router lan port using a pc-to-router lan cable and I can see the send/receive lights blink for some seconds and then go off (both in tv and in router), lights blink again after about 30/40 secs.. so I'm guessing this is a bootloop restarting the android part and keeping the HDMI working?.
****ing vsd220 I hate it, if you are reading this, don't buy one. It will be VERY troublesome to me having to send it to retailer for warranty coverage because of my geographic location.. I will appreciate feedback on the subject
Also Matt57 did your screen come with a CD/DVD? I have read other samsung screen models being able to recover with a external usb-dvd-r device and the DVD included with the screen (a kind of boot recovery helper). If this one came with the cd I don't have it, so if you got one, please make an iso and upload.
Matt57 said:
I unfortunately hard bricked my VSD220 the other day while trying to upgrade the android system. Bit of a noobie at this and learnt the hardway. The problem I have now is that the unit powers on but i get a totally black screen and a small panel saying "waiting" this disappears and then after a minute or so the unit powers off.
I have tried a number of flash tools using ADB and the device is not located. I cannot get into boot mode on this device as it has only a power button.
Apart from using this as a fishing sinker is there any other flash tools I might be able to use to do a lazarus on this thing and bring it back from the dead?
When plugged into the PC and turned on it is not recognized.
I have tried the Nexus root tool kit and Odin but Odin cannot located the adb for the device. cheers.
Click to expand...
Click to collapse
vsd220 bricked
gattytto said:
Exactly same thing happened to me but I wasn't trying anything weird on it, It happened while doing a factory reset (from android settings) and it just went off in the middle of factory resetting so now the only thing that works is plugging in a HDMI input so it works as a TV but still shows the "waiting..." box for a while and then nothing.. I also connected it to the router lan port using a pc-to-router lan cable and I can see the send/receive lights blink for some seconds and then go off (both in tv and in router), lights blink again after about 30/40 secs.. so I'm guessing this is a bootloop restarting the android part and keeping the HDMI working?.
****ing vsd220 I hate it, if you are reading this, don't buy one. It will be VERY troublesome to me having to send it to retailer for warranty coverage because of my geographic location.. I will appreciate feedback on the subject
Also Matt57 did your screen come with a CD/DVD? I have read other samsung screen models being able to recover with a external usb-dvd-r device and the DVD included with the screen (a kind of boot recovery helper). If this one came with the cd I don't have it, so if you got one, please make an iso and upload.
Click to expand...
Click to collapse
Sorry mate, no I did not get a CD/DVD with it.

[Q] LG Logo boot loop - help?

All
While flashing my LS990 back to stock (was rooted/TWRP) my dog hit my laptop and the USB cable unplugged and the battery popped out right in the middle of the process. Now when I try to enter download mode it simply reboots to the LG logo and when trying to enter recovery I get the same (says Entering Recovery then just reboots). Am I screwed/bricked? Is there any way to recover from this or am I buying a new phone? UGH UGH UGH.
Any help would be greatly appreciated - I work in technology so being without a phone, even for a few hours won't fly so I may be driving to Sprint here in a few minutes...
-Ross
When you have it plugged in is it not recognizing or what is it doing? The reason I am asking is because, depending on how your dog pulled out/ stepped on the wire may tell you if the adapter in the phone is broken. When your in flashtool and it is searching try moving the wire in phone up and down till you find a "Sweet spot" then just hold it like that till it is done. Also change the usb on the computer you are using like try a different usb port. Not on the software on the sides
If you need any more help like really fast just PM me or else I wont check this till like tomorrow
First thanks for taking the time to help. It's never recognized by my Windows 8 box as it never gets into recovery or download mode. When I try download mode it simple reboots back to the LG screen and with recovery it says its entering recovery then reboots. So the PC never ever sees it in device manager at all as it won't boot that far. Honestly I think it's toast and I'm just gonna have to replace it. Ugh.
-Ross
Since your phone is in that little area you maybe able to run the command: adb reboot bootloader
defiantly try the wire jiggle thing that maybe the reason I had a similar problem with a nexus 4 my dog stepped on the wire while it was charging and the bottom adapter messed up and I had to hold a wire for like a half hour to get it to flashback then I just had to return it to t-mobile.
All change usb port use another one that you know works.
It's not a physical connection issue now - that works fine. it's that since it got cut off mid flash I think the boot loader is only half written or something. So it never shows in ADB since it just reboots over and over and over. Nothing can get it to stop/settle down.
I assume I'll be taking it to Sprint tomorrow to see if they'll be nice to me...

Possible New Method - UNBRICK! LG LS980

Okay so one day i decided to Mess around with My LG G2 LS980, i got this phone from a friend and told me that this phone was working originally until he got it stuck between recovery and download mode, their was no fix for this because, i couldnt get my computer to detect that their is a phone connected to it and or it always kept reading it as "Unkown Device". So this one day i spend a few hours thinking and trying a few things. And this is how i fixed it.
Attempts-
-Cleaning the USB port on the phone with a qtip and some alchohal on it 70% -90% doesnt matter it did however make it to where my computer read something but it didnt fix my problem.
-I tried after a one day cleaning attempt and i did 10 minute to 20 minute wait for it dry and same result.
-I tried using my OTF by samsung and it didnt work maybe it was just because its samsung and not lg
- i also tried ADB sideloading and that didnt work because it kept saying it was trying to start and nothing at all.
- I also tried mounting the my OTG or anything nothing seemed to work.
Fix-
-Now here's the weird thing. My phone was already taken apart i used a guitar pick to remove the back cover and then i had a handy dandy mini philips screwdriver to remove the two back plastic peaces and look around the first barrier of the motherboard so im specifically looking and wondering if its the USB port/ Headphone jack chip and i didnt find anything that looked damaged but if that is the case i would have spent money to replace the whole USB port thing but i thought at least minute maybe it needs to be bent in someway to work.
-I had a preset desktop fresh and practically ready with drivers already installed for this flashing or fix, so nothing really would interfere.
-It was a pain in the ass really it was trying to get a certain position the usb port and be at and still hold the plug into the phone at the same time. Reinserting and checking my PC and Device Manager for a good 10 minutes. AS soon as i got a spot where it was best at.
- My Computer read it as a phone and other stuff from the guide. At first it installed drivers successfully but after i jiggled it a bit it messed up and it went into QHSUSB_BULK and idk what that meant and then windows prompted to me to format all this weird drives, i didnt do anything but leave it alone for a bit and i think it mightve went out of the mode because if it bends in a certain it stops being read i guess and then all of sudden after a few 3-4 trys plugging in after about minute during each removal and reinstering my computer read it as the LGE Android Modem and i check the ports and it was exactly the same thing as picture in the guide, i switched it to port 41, started the flash tool and i just waiting and it eventually started flashing and i got it working again but right now i can only seem to charge it theirs no way i cant MTP or anything at the moment.
So i use MoboDaemon to wirelessly transfer files. Kinda handy actually. you guys should try it out.
{ROOT}
Also downloading TowelRoot will root the phone easy peasy and then installing SuperSU or whatever and then hitting continue and normal and then rebooting of course and then everythings fine. The only part to flash a recovery is to flash an old one via. Free Gee by that app and allowing root rights and then downloading an updated TWRP 2.x for that phone and flash it via Rashr or Flashify, everything should be fine and dandy after that.
Thanks for looking at this, i hope some of you guys can fix your phone if this happened to you, its been 3 months and i didnt think about this at all until now at last minute.

moisture detected

Since last night I've been getting moisture detected on my note8.
But unlike other cases,this only happens when the phone is off and wont charge unless I put on.
Please i need help
brayne_lil said:
Since last night I've been getting moisture detected on my note8.
But unlike other cases,this only happens when the phone is off and wont charge unless I put on.
Please i need help
Click to expand...
Click to collapse
Hi there. It happened to me too. I tried everything and nothing worked. At the end I ordered an usb-c Board for the NOTE 8 from ebay for 7€ and replaced it. Because of the moisture error my Gear VR whould not turn on.
Anyway 7€ for the Board and 10€for the Glas Back Cover. I actually managed to save my original Backcover.
This obscure solution worked for me!
Same problem here. I tried a ton of fixes: new cables, new chargers, safe mode boot, USBDevice data wipe, Dalvik Cache wipe, full reset, etc. but none of them worked for me. Closest I got was holding down Bixby button on boot and then plugging in cable-- which would let me charge normally UNTIL I unplugged the first time; would always get moisture detected after that until next reboot....
UNTIL I found this solution in a single obscure Youtube comment:
1. Reboot
2. Plug in cable on first logo
3. Unplug when 1st logo goes away
4. Quickly plug in again on 2nd logo.
It worked like a charm for me. Now I have no issues.
This confirms to me that there was some odd software flag that was tripped. My guess is that there's a baseline voltage the phone measures for charging, and when the voltage is under that baseline, it throws a moisture error. I bet this sequence causes the phone to measure a new baseline, thus resetting the bad data that tripped the moisture flag previously.
Just a guess, but would make sense.
brayne_lil said:
Since last night I've been getting moisture detected on my note8.
But unlike other cases,this only happens when the phone is off and wont charge unless I put on.
Please i need help
Click to expand...
Click to collapse

Gtr2 stuck at Logo

Hi!
My Amazfit GTR2 rebooted alone and then got stuck at Amazfit boot logo.
My phone can't connect to it.
Tried to reboot the whatch by the main button, but it reboots and does not go past the logo.
Any ideas?
Thank you
someone2kill said:
Hi!
My Amazfit GTR2 rebooted alone and then got stuck at Amazfit boot logo.
My phone can't connect to it.
Tried to reboot the whatch by the main button, but it reboots and does not go past the logo.
Any ideas?
Thank you
Click to expand...
Click to collapse
maybe it´s a low battery ?
I know that you can reset the watch, I´ve forgot how.
Hey, I have a GTR 2, and at first I thought that the bootloop issue is software based. That can be easily fixed if you put the watch on the charger as it can finish loading even with a corrupted watchface installed.
In my case however, the watch only worked for a short time after I've put it in the freezer. That is a hardware issue. All that can be done is to get it replaced by the store that sold it to you, or in case that option is not available to you, you need to actually heat the board over 300C so that, hopefully, the bad connection is fixed (mobile repair shops can actually help with that).
As a test: put device in freezer, connect, reset, whatever, then shutdown the watch.
Wait for the watch to reach room temperature (non working state). If it's a hardware bootloop, the watch will not react to any buttons, will not show he charging animation, nothing. Basically black screen.
I also tried removing the battery for 10 seconds, holding any combination of buttons, charging states, screen presses, so simply don't waste time with that.
Every electronic equipment has a failure rate of 0-5%, we just happened to buy those 0 to 5% watches.
From what I understand, it is a design error and some contacts on the circuit board may not make contact...

Categories

Resources