XT1622 stuck on blue boot logo - Moto G4 Questions & Answers

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.

Related

Storm Bricked and Fastboot Broken

Hi all,
I got my Wileyfox storm running stock CMOS 13.0 in April and had no problems for about a month. Eventually, I got a pop-up notification with an "Incremental Update" for the phone. I downloaded it and when ready to install, I did so - or at least tried. The update finished and booted into recovery for some reason. At the time I didn't question it and just rebooted the phone from recovery. This led to a boot hang on the "Cyanogen Mod Ready" boot screen.
After searching around for a fix I eventually tried to flash over the stock ROM via Fastboot - which for some reason errored on emmc_appsboot and the phone rebooted itself - with a penguin instead of the Wileyfox boot logo and STILL hangs on the Cyanogen screen. I can also now not boot into fastboot and not boot to fastboot from recovery either (which I CAN still boot to).
Does anyone have any ideas on how to fix this ASAP??? Help would be greatly appreciated!
Many thanks.
I've finally found something that works, unplug the battery for a day or two, then plug in and charge and turn on and might boot properly. Frustrating having to do it every time you get into the bootloop hang and doesn't work every time but still probably salvageable.....I discovered after being bricked for 14 months.

Sm-g900f (uk) galaxy s5 - arrgghhhhh

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....?!

[Solved]Device keeps "erasing" and reboots

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.

Verizon Moto Z Force stuck in bootloop after getting wet

Okay, so heres my issue. Moto Z got wet. It happened during an accident at work and I got a bit side tracked and after a while I noticed the phone was getting really hot so I accidentally restarted it instead of turning it off. Now the phone is stuck in a boot loop. I can get to the boot loader screen. I can restart boot loader via button commands but anything else I try for instance, recovery mode, it goes in to the loop again. My laptop ( windows ) see the phone but not a as a Moto z and I can talk to it with commands on the laptop. I"ve tried flashing with no success. Maybe I'm not doing something right on that part. I'm not trying to unlock the bootloader mainly because I can't considering the model of it. I just want to restore the firmware on the phone. Is it possible? Many thanks in advance.
Yeah I own this cell phone as well. Some trick you could try is to let it drain power wise out. Get a zip-lock page for freezer add a folded paper towel with it and your phone. Leave it in the freezer for 30 hrs. Plug it up to power turn i on. Note if you have changed anything to the firmware to the cell phone this might not work.
Thanks for tip tipstir. I have been trying to restore the firmware for a few days now, researching like hell. I didn't touch the phone for about a week before attempting to restore it. Yesterday I used an all in one tool form a developer here and managed to stop the boot loop. Now all it does is boot to the fast boot screen. It still won't go in to recovery or anything. Flashing fails on RSDlite 3 out of 38 steps. Anything else I can try?

Can't stay in download mode

Every time I go into download mode my phone boots itself after a couple of seconds. This started to happen after I downgraded my phone from marshmallow. I was following a youtube video (How to root Verizon Galaxy S5 (SM-G900V) by LightningForce), but I didn't understand what I was doing since I'm very new to this. I got stuck at 9:14. My phone got stuck on the Verizon screen, and I did a factory reset. After that, I saw my phone was downgraded, and it asked me if I wanted to upgrade, which I did eventually because I kept coming across difficulties and gave up.
So now my phone is back to where it was before I started everything (I'm not 100% if it actually is though), but when I go to download mode my phone boots itself after a couple of seconds while I'm there. The only time I was successful staying in download mode was when I left my phone alone overnight and tried in the morning.
Does anybody know how I could fix it?

Categories

Resources