I bought a used Moto X Pure from someone at a cheap price (to use it to learn how to debug apps and stuff) however, As soon as I turned it on. It keeps rebooting and goes to the "erasing" screen with the little android guy.
edit: Got it booting, I had to flash the stock firmware twice for some reason. Will update if something else goes awry.
edit 2: Everything is solid now. Fixed this by reflashing the stock firmware a 2nd time and skipped erasing userdata.
Related
I recently bought a vega for someone as a christmas present, installed modded stock v2. rebooted into recovery, wiped data, davlik cache and cache partition. Then installed vegacomb 9n and the update 3 and rebooted.
All seemed fine and vegacomb was working. Rebooted the vega and it gets stuck on stale boot (backlight on but blank screen). turned it off (held power button for about 6 seconds) and back on again and still stuck with backlight on but blank screen.
I don't want to have to keep reinstalling it every time I turn it off, and the person I bought it for would obviously like to use it.
Any ideas?
there is a lot of this happening with this honeycomb 3.2 roms. i think its something not right wiht the boot loader. some tablets display the usb boot loader message some just show a blank screen. either way the only way to fix it is to reflash it again.
this happened to me and i just went back to stock 2.2 firmware. its not pretty but it works and is reliable enough to leave with the wife without any complaints that its not working.
So for a few weeks now, my phone has been having bootloop issues. I've been trying to fix it on my own, but no luck so far.
I can get it into download mode. Up until I tried to restore it to its stock version via the User Tool, I could get it to the factory reset options, which led to the options to wipe cache, reboot, etc. However, none of those options worked. When I attempted to reset to factory settings, I got the "dead" green android with the red triangle. Then the screen goes black and starts bootlooping again.
Once in awhile I can manage to turn it on after having it turned off for hours, or even days and it works like normal, except that if I lock it or turn it off it will end up restarting and starting to bootloop again. Which is bad seeing as it drains somewhat fast due to being overheated while having the screen constantly on.
As for my experience trying to use update recovery, it gets to the downloading part then stops and gives me this message "[011.700.147.062.092]??? ??? ? ? ????". I don't even know if I am using the correct stock rom for my phone, since I only know its MEID and model name.
do u resolved this, i have the same problem
Can anyone PLEASE help??
My partner opted to do a suggested update on her S5, but didn't notice the wifi was off. The phone seemed to have done the update, but shortly after it rebooted itself, then again, then again. The frequency of reboot got quicker and quicker and now it loops between the Galaxy S5 splash screen and the SAMSUNG logo, but doesn't go any further.
I managed to boot the phone into reset mode, cleared the cache and then did a factory reset, but that did nothing to prevent the boot loop.
I then downloaded Odin (ver 10.3.7) and what I believed to be the correct firmware (G900FXXS1CPLV_G900FVFR1CPJ1_G900FXXU1CPIW_HOME.tar.md5).
Having checked the battery was charged, I followed the instructions of connecting the phone via USB, loading the md5 in the AP, checking Auto Reboot and F-Set time in the options and clicking the Odin Start button. I had removed the battery, replaced it and then booted it into the update mode (Power, Home, Volume Down, then volume up) with the screen confirming I was in the right place (....do not unplug.... etc).
The file loaded, (green bar at top of the Odin window on my PC) and Odin reported success. I then disconnected the phone, booted in recovery mode, reset the cache and then did a clear data, factory reset.
The same symptoms prevail, STUCK IN BOOT LOOP!!!!
The only thing different is that if I plug it into the USB on my PC, after a while the phone tries to turn itself on and goes into either a boot loop or freezes on the Galaxy S5 Splash screen or the SAMSUNG Logo.
I am charging another battery (just in case that is in some way to blame) and will try again to replace the firmware, but could I be missing something, do I need to do anything with PIT (I thought this was all taken care of by Odin using the MD5 file) or is there some other test I can perform that will show if the phone is fried???
MANY THANKS for looking!
ur going correct, try to reflash it again through odin and dont disconnect phone until it boots into system, it is taking some good time, so just wait and dont do anything this time like clearing anything or restoring. i hope ull get success.
THANKS - but...
Thanks Rayzen, I will try the whole thing again, but I think there is something more to this than a firmware fault!
There and gone again
OK, so on the 4th attempt I got the phone to take the firmware using Odin, it reported success and the phone rebooted itself (several times) and eventually appeared to boot to a new factory reset.
I put in a SIM card and entered my email and google account details and left it charging over night. This morning when I tried to use it, the screen froze and then it rebooted itself. Hey presto, the phone is back to square one with a boot loop.
ANYONE (please) got any suggestions?
THANKS
No one??
same here, same symptoms, same feeling.
when flash gone right... i feel lucky.. but for half hour only, rebooted and angain in boot loop.
I cannot even boot in recovery. flashed TWRP. from 5 boots in recovery only 1 success.
When trying to wipe phone in TWRP - it hangs.
still trying to install some other (custom) rom. still no success.
hope never dies
same things happened here! now cant get samsung galaxy s5 to boot...............
Are you sure your using right firmware? as it took me a few versions before it booted last time this happened?
Could any please confirm what is the right firmware for samsung galaxy s5 900F
It took another 6 or 7 attempts, left it over night and was about to trash it when it booted.
I then received a 'software update available' message and tried installing it. First attempt put the phone back into boot loop so I reflashed it again using Odin.
That worked immediately the over the network software update installed and now phone is 100%
Very frustrating but I got there!
glad you fixed it! ive tried three different firmwares and still nothing.
trying this one atm
G900FXXU1ANE2_G900FEVR1AND1_G900FXXU1ANE2_HOME.tar
oh and how long do they take to boot when there are sitting at the samsung glowing screen?>
I'm in UK and used what (I had to guess) was the best firmware.
I'll let you know which version it was when I get home tonight.
BUT I had all the problems with a single version and it eventually came good.
I read somewhere that overwriting a different core (from specific providers) with generic firmware, could lead to a world of pain until it gets full replaced... not sure if that's a good description (or has any fact to it) but it seemed to be re-loading and re-loading and re........ for ages, finally cracked it.
well mines booted now!but getting constant errors about samsung push!
If it'still booted, you'very made progress!
Push issues are mentioned elsewhere and can (eventually be sorted) but if you have a booted phone you should be able to get an over the air software update installed from the service provider....?!
Hi,
I picked up a second hand XT1622 super cheap the other day. It didn't seem to want to boot at first, and stuck around on the blue Motorola logo for a while, but eventually after leaving it alone for an hour or so it sprang into action.
Trouble was I then made the mistake of downloading the December OTA update, and since rebooting from that installation it's been stuck on the blue screen again.
I thought maybe something went wrong with the OTA, and flashed the December firmware through Fastboot hoping that would resurrect it, but I'm still getting the same result.
The bootloader is locked unfortunately, and I can't boot into recovery mode either - same issue.
Does anybody have suggestions other than me breaking the phone in half (which is probably going to happen today anyway)?
Phone suddenly sprang to life, but for some reason wouldn’t let me press return after entering my PIN after prompting for it in setup - maybe it’s a hardware issue and the phone’s on its way to the great G4 graveyard in the sky?
The original G destroys this nonsense of a phone.
For and download the stock firmware, and then flash it through fastboot. After that, see if it boots. If it does, unlock the bootloader so you will have b easier time if this happens again.
Howdy, all! This is my first post on XDA, and it comes after days of frustration. I'm relatively new to the back-end of phones, especially android. What happened is this:
About 4 or 5 days ago, I woke up to my phone completely dead, despite being plugged in. I tried turning it on, and got stuck on the "Samsung Galaxy S7" screen for a while, and then finally a blue screen with the android logo saying "Installing update." That process seemed to end rather abruptly and then went back to the first loading screen, followed by a black screen, then "Samsung," and repeat. At this point I tried plugging the phone in to see if smart switch would detect it... and this is where my ineptitude with phones starts to show.
I didn't realize that smart switch has an emergency recovery mode under "file," (*sigh*) so when my phone didn't show up on the main screen I assumed the worst. After some google-searches, I went in to clear the cache through Android Recovery. I was still trying to save my data at this point, so I didn't just erase everything and start fresh. I regret that now.
After clearing the cache, I rebooted the system through the menu, and was stuck in loop with the first screen being all black, except for some blue text in the upper left hand corner saying, "Recovery booting." The screen would then flash back to a blue screen with the android logo and "Installing system update," and then go black and repeat the whole process. Getting back into the recovery menu was sporadic after this, but was possible occasionally. This is where my ineptitude REALLY starts to show...
Despite having my current rom version displayed to me multiple times on the recovery menu, I neglected to write it down or record it in any way. Instead, I googled "SM-G935A stock firmware," and was able to find a presumably helpful link on these forums guiding me on flashing stock oreo files through Odin. I say presumably, because in the hands of someone who actually has knowledge on this subject, the thread was incredibly helpful. In my hands, however, it seemed to create a monster. I flashed the stock files downloaded from the link, and all looked good- Odin gave a solid pass, and the phone rebooted to the normal initial two loading screens. And then disaster- another boot loop. But this time, I have no idea what firmware used to be on my phone before I started fooling around.
At this point, I've had one near success with a flash of SM-G935AUCS8CRK1 through Odin where I actually got a blue LED indicator for the first time, as well as the AT&T logo and chime. Now, however, it seems that I either get stuck in that loop, or back to the original "Recovery Booting," "Installing Update," loop.
The phone is not rooted. I don't have a custom recovery installed, and I'm not even sure if I ever got around to enabling developer mode through the OS settings.
ANY help is appreciated. I'm pretty sure I've made the problem significantly worse than it was originally, but I've at least learned a lot in the process- hopefully I won't mess things up this badly in the future! Thanks for taking the time to read through this mess!