I used TWRP to install a ROM, but I was accidentally not on a compatible build number. My SW3 is now stuck on the SONY screen, occasionally buzzing and getting hot. I can get it into fastboot thankfully, but I have been unsuccessful in restoring to any working version:
1. I tried to repair/restore using xperia but when installing/loading the repair the watch died. I am guessing that it is not really charging and might have died during the install, though I can't say for sure. I had left it on the charger overnight, but like I said it is hot.
2. I tried to load TWRP again so I could reflash that way. I successfully went into flashboot and booted the twrp image but when the watch rebooted it just went back to the SONY screen and buzzing again. How do I know if I have the correct twrp image? I don't remember the exact build number I was on. It was LDsomething.
Thoughts? For reference, I am to downgrade my SW3 and install NFC. I am too new to the forum to post a URL to the instructions, but you can see them if you google LibreAlarm and "How install NFC on Sony Smartwatch 3"
Related
Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.
Valorendk said:
Hoping someone can help me here.
My wife has a G3 that started acting up back in September or so. It would randomly turn off and reboot, usually while not even touching it. Did some looking around and found that the Facebook Messenger app could cause some instability. Removed the app, all was good for a couple of weeks before it started again. This time, we backed everything up, did a factory reset, all was good for about a week. Reboots started again so I did a hard reset from Recovery. Booted up, everything was good again for about a week again before the reboots started up. The wife ended up giving up on it and went back to her Galaxy S3.
I've been messing around with it today. Phone has been stuck in a boot loop at the LG logo. Battery is fully charged. I followed some guides and downloaded the V10c stock firmware TOT file, dated June 20th, 2014 and LGD851_20140611_LGFLASHv160.dll and loaded them up into LGFlashTool v1.8.1. Installed fresh LG drivers on my Win7 PC, followed the flashing instructions to the letter using a USB 2.0 port (as I read somewhere that 3.0 ports have caused issues on some devices). Everything flashes 100%, flash tool reads complete, phone shows a big 3 on the screen with a blue background. Unplug and reboot the device and it's right back to a boot loop at the LG logo.
Now at one point, during the flashing process, it would boot into LG MiniOS 3.1 and I was able to choose an option (chose Normal Boot) and it would go back into the boot loop. Also, I connected it to my Ubuntu machine just to see what would happen and I received an error "Unable to mount LGE Android Phone. Unable to open MTP device", which makes sense. However, the phone itself would get to the T-Mobile logo and briefly jump into the initial setup of the phone before jumping back to the LG logo and starting over again. Connecting back to my Win7 machine, it just boot loops unless I have the flash tool running. Not having USB connected, it just boot loops.
I'm at a loss here. I can usually muddle my way through these kind of things but this one has me completely stumped. Ordinarily, I wouldn't worry much about this but she's wanting to get a new phone through T-Mobile's JUMP program and we can't do that if the phone won't even boot.
Any help would be appreciated.
Click to expand...
Click to collapse
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.
cesarandres_8911 said:
Good afternoon, my recommendation is that flashes with lg flash tool 2015. All you need is your phone updated driver installed on your pc. Further, you need to download the KDZ (firmware of your stock rom) corresponding to your model. Look at the XDA thread as do or YouTube. If you need more help, you can consult here.
Click to expand...
Click to collapse
IIRC, he's talking about going back to the latest stock firmware available from LG and flashing with with @quangnhut123's flash tool.
Thanks for both of your help on this. I actually had given up on the phone for a while. The last time I flashed, it was allowing me to get into the first time setup but wouldn't let me complete setup before rebooting. So I ordered a new battery and everything is working like it's brand new. Thanks again!
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.
Hello.
I create a new post it will be better organized. Well, in the end I have a big problem with the c pixel. I wanted to flash Factory 7.1.2 ryu. I followed all the steps on the Google site. So install adb and Fastboot with their drivers. Then double click on Flash_all.bat. All went well it rebooted and I can use the tablet without any problem. The only thing I didn't do was lock the bootloader because I thought it would wait until tomorrow. So everything works fine I have test some features, then I test the restart and there is a big mistake. I see the message: bootloader is unlocked and os verification is off the device continues booting in 30 second. Then a high-pitched beep and the Google logo appears but never changes. So nothing left and blocked on this logo. And did I do something stupid, did I brick it. I'm lost ?
While trying to connect it in sector there was the animation of the four small rounds then it turns off and goes in bootloop. Is it over? ?? Or can I still fix it?
I'm going back to the message I posted earlier. Here, I undertook alone to look for my mistake to remedy it. So in the recovery I saw "enter in fastboot mode" so I pressed it and I reflashed the rom factory. then everything went well. And instead of continuing like yesterday I immediately locked the bootloader. Then I rebooted and for the moment everything is going well. The only thing I'm afraid to do is restart. But if everything goes wrong I'll just have to flash the rom factory again, I think. So here it is I solved my problem by myself
Edit: the restart works perfectly. My mistake was to restart without locking the bootloader.
Recently encountered an issue where I was able to get the watch factory reset and wiped then I was able to start the setup process and it started an update, but now its stuck on the multicolor G logo. I have a feeling I will need to do an update with a hacked up cable and ADB. Anyone else experience this?
I don't have too much experience, but the 4 pins at the top of the Pixel watch are just USB, so you should be able to use a hacked up cable to try flashing the stock firmware via fastboot, that is, if you can get a copy of the stock firmware.
So I found a solution by total accident. I isolated it to after the setup when it updates and restarts it would get caught in that boot loop and never actually boot. I was trying it again for about the 10th time after factory resetting which would allow me to at least get to the setup screen and continue forward. So it was on last step of the setup where it downloads the update and pushes it to the phone when I got up and answered the door because my buddy had called to say he was pulling up. Without knowing I walked away with my phone and it must have lost the connection because when I came back the watch was functional and got through that initial boot that it kept getting caught up on. In the watch app I now had a notification that the watch needed to update with the option to download and install. I was hesitant to do so but it worked.