Hi guys, my smartphone's screen gets black sometimes, and, after a quarter of second, it gets back. It's a Moto G Play (4th gen.). I want to unlock BL, root and change ROM too. But I'm scared about if it isn't a h/w issue.
If you can give me a hand, it'd be really appreciated.
Here's a logcat taken from the boot until 1 hour of activity reached: https://gist.github.com/FacuM/1bf3d99bf1c6c7dc4178051ab197074d
And here you can get a .zip packed version: https://gist.github.com/FacuM/1bf3d.../d2c32dcd9a3a30e28ae25e43d0c79f6427cda676.zip
Here, a logcat from when I wiped logcat until I opened a lot of apps with at least one black flashing: https://gist.github.com/FacuM/b72ae8c12bb50c5aebfec3c0eb3cf497
And here a .zip packed version: https://gist.github.com/FacuM/b72ae.../2e47f0cd8418ebda2c8522cac8b85b2bde826cdc.zip
Related
OK first, I will say that I have been reading for days and days and am getting nowhere at all. I am running out of time as I am leaving Monday backpacking from OKC to Portland to meet a friend, then proceeding immediately to about 35 national parks. I HAVE to get this thing functional so that I can depend on it on the road for communication. Its current state makes me nervous. I got this tablet already rooted, custom stock rom, and with an unlocked ICS boot loader version 0.3.11. The only problems with it were the common charger/screen response issue. For $100, I can deal with that.
I flashed the Lightspeed from from the main list, everything went well... Until it rebooted the first time. Since then, directly after the bootloader screen, it briefly shows what looks like semi-colorful TV static, then shows boot animation and boots into the OS. It has never frozen on either screen.
I decided Lightspeed was not at all what I wanted, so I flashed CM10. I have yet to find anywhere in the Aroma installer where I can choose the apps installed, ONLY THEME CUSTOMIZATION. After the flash, it kept the boot animation from CM, and loaded right back into what looked like Lightspeed, and shows Lightspeed in the about menu also. I reflashed it, choosing a different boot animation to test, and did the same thing again, except it loaded ZERO extra apps at all, not even the stock bloatware. Nothing from any of the 3 roms. I reflashed Lightspeed, same thing again. No extra apps and just bare basic stuff. EXCEPT SUPERUSER. THAT DID LOAD ONTO IT EACH TIME. I haven't lost root access, the recovery works fine.
I flashed the V8 bootloader, and tried the above again. Same issues still. All of them. I have read until I'm blue in the face. If there is a way to fix this without using a PC, that would be grand. I have very limited PC access.
Anyone have any ideas? I have followed every single step 100%, I'm positive. I'm not new to rooting, flashing, and jailbreaking (doesn't apply here I know),"so lay it on me.
EDIT- I downloaded the 4.0.4 FLEX-Reaper rom and going to try that now and then I give up for the night. Tomorrow is the last day I have to mess with this before I leave. I tried to upload screenshots of the problems, but it won't let me attach them. Maybe that is another problem. Ugh who knows. Help
EDIT- That rom bricked my tablet. Through that brick, I found a working solution for the SoD, found a way to recover without files on external SD, *THIS FIXES THE BRICKS CAUSED BY CM10 AND REFLEX!!!* and I didn't lose anything. This thing is back in pristine order. I can finally sleep! Will post later on how I did it. I need sleep now.
Hi All,
I hope I'm posting in the right place, apologies if not.
I have been running Cyanogenmod on my S4 i9505 since Christmas. A couple of weeks ago, for no apparent reason, the phone started switching itself off so I decided to try and flash back to a stock ROM using Odin and the most recent firmware (5.0.1) from sammobile.com. I'm pretty new to this and don't have much in depth knowledge at all - hence opting for the apparently easy Cyanogenmod rooting option in the first place. The Odin flash 'passed' yet on reboot I got stuck at the Samsung logo and the phone then gets stuck in a boot loop if I switch it off using the power button. I then tried to flash an older firmware (4.2.2) but it has failed twice, leaving me with a 'brick'.
As I said, my technicial knowledge here is very limited but any step by step help to trying to get the phone back up and running would be greatly appreciated. Have I completely ruined the phone past repair, or is there a way round this?
Many thanks in advance
Whenever you upgrade to Android 5.0.1 from an earlier version it takes up to twenty minutes before it fully boots. This is because of the internal change from the Dalvik app compiler to the new ART compiler Android now uses. Android apps come in multiple parts, and on old versions of Android these parts were assembled into a single running image every time you ran the app. This is called "Just In Time" (JIT) compiling. The new ART compiler uses "Ahead Of Time" (AOT) compiling. It assembles all the apps once, rather than repeatedly assembling an app when you run it.
When you upgrade to Android 5.x and future versions of Android, Android will need to spend time compiling every single app on the device before it fully boots. This can take quite a while if you have a lot of apps, and an unfortunate side effect of this is that the device looks like it's stuck in a bootloop.
If you're able to get into Download Mode, your S4 isn't bricked. Install 5.0.1 again, but this time don't touch the device for a while.
Many thanks, a little patience was all that was needed. Re-flashed 5.0.1 and waited for first boot - all sorted!
Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
albinhj said:
Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
Click to expand...
Click to collapse
Flash stock image from google... maybe some stuff from CM12 go wrong...
Not use CWM recovery...better TWRP...this is updated.
Could use some pointers, as it's been a while since I have ever tried to root/flash a GSI image (last time was my old phone running Oreo), and this is my first Pixel.
Did searching, and tried a few things, but am running into a hiccup -
Following this message here:
Using the vbmeta.img from this post, and downloading an AB GSI image, following those steps will cause my phone to boot up, play the initial Google logo, and then get locked on the "G" logo on white screen, never getting into the ROM.
For some reason my memory is failing me, and I feel like I'm forgetting something - or am I using (a) wrong method somewhere?
Thanks all-
Mike
I suspect this long loved device has reached EOL.
It recently spent a brief time in the bath and 14 hr later stopped working. Opened, dried, observed a bit of corrosion scrubbed off with alcohol. I was able to boot to TWRP recover and back it up. I wiped everything, rebooted and then installed the current OS download. But still it boots to a blank screen + blue led.
Anything else I should try before admitting the gods think deserve a newer phone?
bhydexda said:
I suspect this long loved device has reached EOL.
It recently spent a brief time in the bath and 14 hr later stopped working. Opened, dried, observed a bit of corrosion scrubbed off with alcohol. I was able to boot to TWRP recover and back it up. I wiped everything, rebooted and then installed the current OS download. But still it boots to a blank screen + blue led.
Anything else I should try before admitting the gods think deserve a newer phone?
Click to expand...
Click to collapse
Hello,
I'll link to an old post of mine but it is still valid: https://forum.xda-developers.com/t/...-oneplus-5-cheeseburger.3627003/post-81887593
That seemed hopeful "Black screen with blue led means tour recovery requires a higher firmware version, but your actual firmware version is too low."
I don't know how to discover the current firmware version in TRWP/adb, possibly adb getprop shows it indirectly?
So installed a fresh firmware and reinstalled the os.
Code:
firmware from https://forum.xda-developers.com/t/index-oneplus-5-cheeseburger.3810283/#post-76943628
OxygenOS Stable
OxygenOS Firmware + Radio Flashable Zips
OOS 10.0.1 with MD5: 45986705a030c6746f87944676203abb
Code:
OS from: https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156143164
OnePlus5Oxygen_23_OTA_069_all_2010292138_55db5445239246dd.zip os.zip with MD5
with MD5: 8f41d1cca57e8a91879f4b09088103b4
Both installs reported success, but reboot restores the blue led etc.