Hi all,
My G Watch R needs to be re-flashed through Fastboot (Boot, System, Recovery) every time I reboot/Shutdown/Run out of battery.
It's running stock, and the only thing I've ever done to it is unlock the bootloader in order to repair it the first time it crapped out.
It's annoying as hell - does anyone else have this issue, and if so - is there a fix?
Cheers
Related
hi folks, have a big problem.
have a rzr i with JB (4.1.2)
with ICS i have had my phone rootet, since jellybean upgrade not
now i wanted it rootet again and was starting with unlocking the bootloader like in the tutorial-video in mattlgroffs post
http://forum.xda-developers.com/showthread.php?t=1928551
ulocking works fine for me, just took a look if phone ist still working, fine...
installed some backups and than restarted phone again...
and there my problems startet...
after the "Warning unlocked"-screen there comes the red "M" and starts waving - ok
but when the "intel inside" appears on the screen it just go to "intel ins"
after that, the red M shows up again...
only for 3 or 4 seconds and than disapearing and coming again and so on...
really need your help guys, does anyone has an idea?
Factory Reset.
Something went wrong with your backups.
already tried factory reset, same result
I had the same problem
Do you have CWM installed? If you do you could flash another rom, but before wipe data cache and the cache on the advanced settings, if not loot at this link http://forum.xda-developers.com/showthread.php?t=2140491
I've left my phone with 60% charge yesterday night.When I woke up the battery was at 0%.I charged it to 100%, rebooted and the phone was stuck at LG loading screen.I got CM11 nightly 26.
Then I restored 2 diff nandroid backups after a full wipe.It did not work and I finally decided to use lg mobile support tool.It successfully downloads, installs the firmware but somehow the phone is stuck at bootanimation.
I've tried to reinstall USB drivers; flashed the KDZ about 5 times now and I really am hopeless.
I haven't dropped my phone; haven't done any physical damage to it and as far as I know if it was just corrupt internal storage I could get over the problem by wiping the partitions.What could be causing this problem?
Weird part is; when this happened I wouldn't even get to see CM boot animation but after attempting to unbrick the phone with mobile support tool, I got to see the bootanimation but it didn't boot (waited approx 30 mins)
Has anyone faced such annoying brick before? What could be causing it? Any solutions/recommendations?
EDIT : According to logs the s/w upgrade completes successfully.No errors nothing, but the phone won't go thru the boot animation.
Mobile support tool .KDZ flashing logs
EDIT2[SOLVED] : Seems like I've found the issue and solved it.The O/S crashed somehow during the night; damaging the TWRP date file(s).As specified in this post (under warning title) it led to a softbrick which can only be recovered after flashing a firmware and wiping data/cache partitions afterwards.I actually had TWRP 6.3.0 and was made by a different user but issue seems to persist.Guess I'll stick with CWM.
I hope this helps someone if they face the same issue later on.
Hi all,
I really need your guys help. Out of nowhere today my phone restarted and then got stuck in a bootloop. When I went into recovery, it gave me the "android is updating" pop-up. I knew there was no update and within 20 seconds or so it said "no command". I went through to wipe the cache, and after rebooting it back up, strangely it didn't give me the "android is updating" screen that occurs after wiping cache. I went ahead and tried to factory reset through recovery and everything was fine until I got a msg "E: could not mount (file or directory could not be found) or something a long those lines. I'm assuming the EFS is fried? I rebooted it after and even at the "Welcome Screen" it started boot looping again. I'm stock lollipop unrooted. I never rooted this phone or flashed any ROMs. I called T-Mo and they will send me a replacement but I still want to see if this can be fixed. I also don't have a replacement phone so..there's that. Would anyone be able to help?
Edit: The only thing I haven't tried is flashing the stock firmware via odin. Would this trip the knox counter though? I really want to avoid that especially since I am having these issues and I don't want tmo/samsung to think I caused this issue.
Bad phone. Ur new phone will be good to go.
BAD ASS NOTE 4
Hello guys...
I need a help. First, I will not gonna blame anyone for spreading the beta/alpha ROM links here.
I believe that many of Mi3w users are very exciting to hear that their device will get an upgrade. And I, one of them who want to be the first to taste Android M on Mi3, officially with MIUI.
The problem is, when updating from 6.1.12 to 6.1.21, suddenly my Mi3w experiencing short bootloop. Normally, boot process will display android text below MI.com, this short bootloop only display MI.com for about 2 seconds and after that, my device turn off, and on again with the same symptom. This process will drain battery very-very fast.
I tried several times to flash fastboot (yes, I still can access the fastboot via vol down + power), at the end of the process, the bootloop happens again and again.
If I kind of lucky, I can access recovery. I tried also to wipe all data, after I reboot, the bootloop happens again and again.
I have search the MIUI forum and found that many, not only me, experiencing the same. Is it possible that this is an error, a weakness, faulty the Mi3 devices have? If so, it was so shameful since Mi3 is one of their flagship.
Oh, anyway... Is there anybody here who can help me fix this problem?
Same for me. Flashed twrp via fastboot and installed ivans 6.0 for now because of the new partition table. Waiting for fix.
Hi all
I'm here to ask you guys about this strange bootloop. This is my brother's phone, fully stock. It was on Lollipop, was never rooted, flashed, and even hard reseted. He was using normally last night, and this morning he woke up to see what time was it and the phone was bootlooping itself.
My first idea was enter in recovery mode and wipe the cache (but then I discovered that LG's stock recovery is very simple...), but I simply can't go into recovery mode, I tried a lot of combinations and nothing happens.
It's strange because is a stock phone, and he has it for like 3 years now. I'm guessing this is a hardware problem.
I made a small video showing the problem:
https://youtu.be/TZ9R5yqlfI8
Any help will be appreciated.
"solved."
The phone's motherboard is dead. My brother now bought an Moto G4 Play.