I factory reset my Glass today because it wouldn't connect to my phone (I switched roms so I needed to pair Glass again). After I did the reset it went into a boot loop. When it's on the "Glass is Updating" screen it can't be accessed via ADB, but I managed to figure out how to get it into the bootloader via the buttons.
From the bootloader I've tried erasing and flashing 16.2, 16.11, and 16.0 but it just returns to the same "Glass is Updating" screen when I reboot.
When I erase, I erase boot, recovery, system, userdata, and cache. When I flash, I flash boot, recovery, and system. I've tried with and without flashing userdata.
Does anyone have any ideas as to what could be wrong?
EDIT: Something really weird is going on. I ran the erase without flashing anything back on and did a reboot. I expected it to stop at the bootloader since there should be nothing to load, but instead it continues to go into the "Glass is Updating" boot loop.
EDIT 2: I've been doing a lot of reading and it sounds like there are more partitions than just the bootloader and the 5 that I have been erasing. My guess right now is that my device downloaded the 16.2 update into some other partition before I did the factory reset and now every time it boots it's running that update. I can't get much info from the device because I can't use adb.
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
davezack said:
I had the same issue when I tried flashing 16.2. I went back to XE12 and it resolved the issue. The whole point was to get away from the train wreck that is XE16.x anyway, so I'm just going to stay on 12 until the XE17 images are available - then we'll see if that release is any more stable.
Click to expand...
Click to collapse
That did it! I didn't try a version back that far because as far as I know mine had XE16 on it when I first got it.
Thanks!
For a while I've been using the nonsense rom (provided on this forum) and it's worked fine. Just the other day however I tried turning on my phone, it would get to the boot screen with the animation of the android bot peeing on the apple logo and it would just play that animation over and over until eventually the phone turns off. I figured I just had to restart, but it was the same issue. After trying to reinstall that same rom, I had the same problem. I then tried different roms and the same issue with those, they would get to their respective boot animations and play them until the phone turns off, never going past the boot screen. The one rom that sort of worked with the cayonogenmod 12.1 rom, but the issue with that is after the boot animation, it appears to be starting the set up for the phone, but prompts me to enter a password, which I have no idea what it is. Doing a bit more research, it seems that there may be a problem with twrp and it not formatting (term?) properly.
As of right now, I've done a factory reset on the phone several times to no avail. I just need help getting this phone to work. I've tried looking at a few places and using adb, but the device wasn't found and I didn't have time to look any further because I'm busy with a project I'm working on and with moving. Some places I've looked said to put the phone into usb debug mode, which I can't do since i can't get past any of the boot screens.
Edit / Solved:
I went into twrp and instead of choosing "wipe data" i went to "format data" and that seemed to fix the problem. Although I did have an issue with the nonsense rom, it got past the boot animation, but then gave an error "unfortunately the process com.android.systemui has stopped". I instead installed the raptor rom and it's working fine.
I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
kamikazisolly said:
I have a Blu R1 HD that I have been on again off again fiddling with for a few months that is soft bricked. It will turn on but it will hang on the second "Bold like us" splash screen after the animation ends. It had no recovery installed to it prior to the bricking, I have attempted flashing a stock rom to it with SPFT but It gets interrupted less then 3 seconds in. From my reading It seems like I have the 6.6 preloader that stopped spft from working.
Is there anything that could be done with this to get it working once again?
Click to expand...
Click to collapse
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
mrmazak said:
Depends on few things.
Do you know what was last thing done before this brick?
Have you tried holding volume up when powering on, to enter recovery(stock, i know you mentioned no custom recovery installed)?
It goes to and past the animation , so i don't think it is a secure boot type of failure. But maybe a bad data problem. See above statement about recovery.
Click to expand...
Click to collapse
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
kamikazisolly said:
I have gone into the stock recovery menu, And i have attempted factory data reset, clearing the cache, and a root integrity check. The integrity check says one item fails the check and that is "/system/lib/libLLVM.so"
The last thing that I recall happening is that I had a pop up saying that an app had stopped working, But it reappeared immediately after closing it again several times. I thought rebooting it would stop whatever was happening, but it never came back to the OS.
The device has a small crack on the bottom right hand side of the screen that happened when it fell from my pocket on top of a ladder. A family member who also works with electronics as a hobby thinks that may have something to do with it but the phone worked for weeks after the break happened.
Click to expand...
Click to collapse
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
mrmazak said:
I do not know if there will be any way forward with this.
As you are not bootloader unlocked, sp flash refuses to connect, and only thing that can be done on stock is "factory reset" did not help, you might be done , other that see if can send to Blu.
Click to expand...
Click to collapse
Sending to blu isnt an option. Out of waranty period, And I also opened it to make sure there was nothing obviously physically wrong.
I also tried using the dirty cow tool, But i cant seem to see the device in ADB. Fast boot however, can see it.
Update over ADB/SD in the stock recovery wouldn't lead me anywhere would they?
I do apologise if I give too much information; I try to be thorough in documenting my methods and include as much information as possible so we can maybe skip some of the "what does it do when you ..." and the "did you try this" questions.
So I have been reading through these forums for the past few hours... Earlier today a friend gave me her AT&T Galaxy S5 to try and fix. When I received it, it would boot straight into recovery. She was on version G900AUCS4DQD1. I can say for nearly 100% certain that this lady knows nothing about modding her devices, so I am absolutely confident that this problem doesn't stem from her attempting to root the 6.0.1 firmware she was on, install custom recovery, or anything anywhere close to that. She said she had taken it to an AT&T Store and they were unable to fix the device; although I'm sure all they did was do a factory reset through recovery and when that didn't work they just said "Well, it's broke, come buy a new device." Either way, the information in bootloader mode doesn't show anything outside of what it's supposed to ... Current Binary is Samsung Official, System Status is Official, Reactivation Lock is off, and most importantly the KNOX Warranty Void flag is showing 0x0.
As I said, when I got it, the phone would boot straight to recovery by only person the power button to turn it on; but download mode was accessible via the option in recovery and by holding Vol-Down + Home during boot. Attempting to boot into safe mode, holding Vol-Down during boot results in nothing different than if I don't hold Vol-Down... sometimes it boots all the way to system where it reboots on Optimizing Apps, and sometimes it doesn't even clear the colorful animated Samsung Boot logo. While in recovery, the device is not visible in Windows Explorer. If I open my command line and type "adb devices" the S5 doesn't how up. However, if I select "Apply update from ADB", THEN type adb devices, it shows up as <device serial #> sideload. Attempting to issue the command "adb shell" while visible to adb results in "error: closed" being returned. Now, because I've been using the OnePlus 3T I have become somewhat familiar with bootloader mode and the fastboot command, and I don't know if Samsung devices are SUPPOSED to respond to the command "fastboot devices" while in bootloader/download mode, but I can say for 100% certain this one doesn't.
Remembering everything I learned when I owned the S4 AND after doing research on what firmware versions I could safely flash if my device was on 6.0.1, the first thing I went searching for was Odin and the factory firmware. I used the thread "G900AUCS4DQD1 ** FULL ODIN UPDATE ** v6.0.1 by toutanje to find the firmwares to download. I have also used the method and files in the thread "[Unbrick] Fix All For Samsung S5 AT&T (SM-G900A) Lollipop 5.1.1 by Birkyjon. Whichever method I use, all the files load and flash without incident in Odin. Before I attempt to boot to system, I boot into recovery and wipe cache and do a factory reset. (I have attempted do boot both with and without a factory reset after flashing the firmware in Odin) After doing that, obviously I hit reboot now... the phone passes the initial Galaxy S5 Logo, it goes to the multicolored Samsung Logo, then the AT&T screen, and SOMETIMES it boots into system, where it sits at the "Optimizing Apps, x out of 210." It will count up to around 30-40 or so, then reboot. After that initial boot where it gets to Optimizing Apps, all boots after that are unpredictable... as in, maybe it will make it back to Optimizing Apps, maybe it won't even make it to the AT&T boot screen before it restarts itself. Once it does that, I can boot back to recovery, do another factory reset, and it will make it to Optimizing Apps again every time. About the only thing I haven't tried was to attempt to flash the firmware via the "Apply update from ADB" option, though I honest don't see the point after everything else which has failed.
One last thing I have seen in my research so far but am unable to test: could these issues be caused by a bad battery? Being that I have no idea how the battery life on this particular device has been, I have no reference as to whether it has been draining incredibly fast, acting normal, or even just flat out dropping massive amounts or so at once.. I seem to remember noticing when I placed it on charge this afternoon, the device only had around 6%, and while connected to only a 1A charging brick, the percentage had magically jumped from 6% to upwards of 35% in what seemed like 3-4 minutes. I can't confirm for certain how long it was charging as I was also wrangling my two toddlers at the time and could have possibly just lost track of how much time had actually gone by...
Any ideas as to the issue I am facing? Any help would be much appreciated! Thanks guys!
I have this exact game problem with my wife's s5. I never got any type of response, I hope you do. I'm still having this problem as well.
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
fernandocg30 said:
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
Click to expand...
Click to collapse
Hey, download the stock rom for your from here:
https://motostockrom.com/motorola-moto-e4-plus-xt1773
And follow this process to flash the rom on to your phone:https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Warning for this phone flashing process:
In SP flash tool, "do not" select 'format all+ download'(the phone will be bricked). Only select 'Download only'.
Secondly deselect preloader after adding scatter file(flashing it will also brick the device).
This all warnings are already given in the flash guide, i just want you to give proper attention while doing it.