While fiddling around in some game, the device goes out due to empty battery (without warning beforehand).
Battery should have lasted several more hours, but the battery status is at 0% so I have to wait a few
minutes before being able to restart. On restart, device boots up normally. (weird: my background got replaced by
stock image). After entering PIN, a few dozen error messages appear (something stopped working), after
clicking 'ok' on the last message, screen goes black (not out).
Next restart, same same, thoug now after maybe a dozend error messages (which I am clicking happily away)
somewhere I spot the message "Android updating"..... black screen.
Boot to recovery:
AP Fastboot Flash Mode (S)
48.82(*) (sha-e004609, 2014-12-19 14:35:02)
CPU: bla
eMMC: more bla
DRAM: blabla
Battery OK
Device is UNLOCKED. Status Code: 3
(BTW: What is status code 3?)
Selecting any option (except 'Barcode', which works nicely) the Moto G boots up 'normally'. No recovery screen, nothing.
Straight to "Warning, Bootloader unlocked", same same, .... black screen.
I tried exposing front camera to bright light because some people seem to have problems with
automated brightness control. That's not it.
The history of that device:
Stock rom
-> some things I don't remember, prob some KitKat 4.4.4 custom roms
-> OTA update (yay, soft brick \o/ )
-> stock 5.0.2 according to tutorial of same hero from around here
(of which for the most part, ofc, I don't know what the hell I am doing by typing all that)
Now i tried flashing new Marshmellow 6.0 roms according to instructions by heroes
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
http://forum.xda-developers.com/moto-g-2014/general/official-firmware-titan-xt1068-t3312933
which cmd and the console in phone bootloader acknowledge one by one, no errors.
Upon reboot, same same, .... black screen.
Then I tried to get rid of that (stock?) bootloader by installing TWRP
mfastboot.exe flash recovery twrp-3.0.2.1-titan.img
but the next time I enter recovery, I'm back to that stock bootloader.
It seems the device is writing all instructions into the Nether.
Things I don't want to read:
- hard bricked
- Motorolla doesn't care about unlocked phones
- you're f*cked
Everything else will be greatly appreciated Any ideas what to try next?
Related
I tried a flash and think i messed my tab...now its just a black screen with a faint light in the background like its on but its no images.......my battery icon pops up then distorts away and thats it ....can get into download mode but not recovery.....tried holding all 3 buttons got this lil android dude in the corner with a sign sayin something about power reset but cant select nothing......help me please......
Put it in d/l mode and flash one of the stock roms with Heimdall.
D
i tried a stock flash with heimdall it flashed successfully but i still get the SAMSUNG logo that flashes and go away,buttons light up at the bottom,can go in download mode but not reboot mode,phone stay on with a faint light ,so i assume that its on somehow.....help
Did you follow this exactly?
http://forum.xda-developers.com/showthread.php?t=967175
One thing I missed here before was to wipe data and cache. Otherwise I go into boot loop.
how to get recovery mode
i cant wipe nothing because i cant get to recovery,just download mode
done it step by step
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
chubbyflood said:
i followed evrything it flashed successfully but when it rebooted i turned off.and tried recovery but nothing......
Click to expand...
Click to collapse
Use UnBrickable Mod
http://forum.xda-developers.com/showthread.php?t=1341753
Although you get a black screen on boot, it might still be working....
Chubbyflood,
If you are in the same situation as I am then the tab is still working, you are just getting black screen on boot up. It played tricks on me for ages when I was first rooting by tablet; but it turned out it is just the boot up screen that isn't showing.
This is my situation:
-Press and hold Power button to turn on.
-I see the Galaxy Tab / Samsung initial boot image for about 1 second, and also hear the "boot chime"
-Then the screen goes completely blank (but you can tell it is still on with a little light showing.
-The four "hard button" lights will light up briefly a couple times
-Wait approximately 30 seconds to a minute (to be safe and give the tablet time to boot up - it is actually booting up)
-Tab the Power button once, to turn the tablet off (now the screen is clearly off)
-Tab the Power button again, and the tablet will be up and running as normal.
I am guessing the boot animation / images are failing in some way, but the tablet is booting up as normal.
I've just learned to live with it, because I haven't had a chance to figure out what's going on, but it honestly took me a good hour or so, and a few (unnecessary) flashes, before I realized the thing was up and running fine, it just need to have the button pressed on and off.
One final thing to mention; don't have the tablet plugged into anything. I seem to remember leaving it plugged into the PC didn't help (I think).
Hope that makes sense.
Cheers
Ed.
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Juiced_RL said:
Has your situation been resolved?
I am in the same boat. What I have done to temporarily fix this was to Flash a ROM that uses Hemdall and it will boot as flukebu stated but only with the Galaxy Cubed ROM.
I cannot get the factory files to boot as you have stated.
I have continually tried to return to stock using the files provided on this forum and all "unbrick" posts.
While flashing the stock images everything completes and works well. The device reboots and the Samsung Splash screen appears. Once it appears it disappears and scrambles the screen. I believe it then goes into a bootloop which easily enough I could access factory recovery to correct but when I do attempt to access factory recovery the screen is as posted above (black but illuminated).
Once I flashed Galaxy Cubed ROM and it booted I hit the power button and the locksreen appeared. I can tell you I was excited but there are some issues with that ROM I have not tried to correct yet because my main goal is to return to stock.
Even with this ROM working correctly I have attempted to access CWM once installed to complete a Data Wipe and that does not show up either.
I would really like to find a solution to this I want to return to stock and not have this custom ROM running.
Click to expand...
Click to collapse
Have you found a resolution to this? Mine tab is doing the exact same thing as yours after the cubed rom.
Hello everyone,
first of all thanks for your amazing work and all the stuff you provide. I was a silent reader for a long time, but now my phone is trolling that much, I cannot fix it on my own/with the guides I found here.
I do have an HTC One M7, rooted (superuser) and S-OFF (revone) with Androidd Revolution HD 71.1. I used to update my ROM every month, but I got stuck after the last update. My recovery was TWRP as CWM did not work properly when I rooted my phone.
My issues as a list:
- cannot enter recovery anymore
- cannot connect via USB (tried every port)
- screen turning randomly black on homescreen and sometimes in apps (but they usually work), screen does work, but i cannot see a thing
- since today graphical issues after a reboot (flickering screen, parts of the screen get duplicated)
Since the last update I cannot enter recovery anymore. Getting in bootloader is no problem but i get stuck in the "entering recovery...." screen. It does not move, tested it for some hours. I tried updating the recovery (-), trying to flash stock recovery and reflashing custom (-), trying cwm (-).
After I tried cwm i noticed that it didnt overwrite the recovery but i got both. cwm and twrp, but i cannot delete one of them (didn' work before either). I can start TWRP oder CWM on a booted phone, but updating both bugs and I can't enter recovery with these tools too.
Today I wanted to try again on my own, but my phone won't connect on USB. Tried every port on my computer with and without USB-Debugging. I will try on a other computer, but I could not do this until now. Additionaly I want to wait for some ideas of fixing, as I think "my" trys are not going to work suddenly .
Screen started to turn black a few days ago. Dont know why but I think it could be a software issue. but i cannot update (see above ). When i try to turn my screen on it often just turns instantly black. soft keys are enlightend and it does work (more or less). if i success in sliding down the service bar on the top, i can start my alarm clock app and from there use the soft keys to get in other started apps. From there it works most of the time. Sometimes i need a couple of trys, sometimes it just works as its intended without turning black and sometimes i need several minutes to succeed.
Cannot say more as I did to the graphical issues. Just had them once until I started an app (screen worked). could not reproduce this error.
I would prefer a solution without wiping, but if necessary i will ofc.
Thanks in advance for your help, as I am rather helpless right now.
I attached a photo of the bootloader.
Yours Laexxi
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.
---Update---
Nevermind, I see this has already been discussed in this thread:
https://forum.xda-developers.com/moto-x4/help/to-force-8-1-ota-project-fi-x4-t3786726
This is a common problem with no solution ATM.
_________
The update screen comes up (see pic1), I click "download and install", and after it downloads the 945MB update file, I get this error screen (see pic2).
After I click "OK", the update screen reappears a few minutes later, and the cycle repeats.
Would getting a logcat help me diagnose this problem?
I've got the XT1900-1 A1 model, and the bootloader is unlocked, but nothing else (no root, no custom kernel or recovery).
(screenshots)
The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.
same problem here
Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt
Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.
Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....
Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.
Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!