Hi all,
I'm facing a curious issue with my Oneplus 5. I bought it back in July on launch day and though I have rooted and used custom ROMs on all my previous phones, I never got around to doing it on my OP5 (never felt the need, no availability of root early on etc)
I started facing a problem with my mic not registering in Google Assistant/Alexa and while on speakerphone, all while sound recording works fine in recorder apps.
Tried attempting to reset the cache from recovery,
1. On pressing vol down+power while turned off, I get nothing. No vibration or anything.
2. On trying to reboot to recovery by turning on advanced reboot, I'm greeted with the 1+ powered by android splash screen, followed by a black, blank screen. Have to long press power button to get the phone to boot again (takes quite long).
Could anyone help if they are aware of a similar issue, or any ideas to correct the problem? I'd be really grateful.
I'm on latest Oreo Stock update.
https://androidfilehost.com/?fid=745425885120760474
Downlod the zip , extract it connect the phone to pc with pressing volume up and then use the tool for flashing up .
Related
Im so lost with this, im all stock but one day my phone just freezes then bootloop, I would be able to get it work by just leaving it and let it drain itself since it will be boot looping and lock me out completely, like the power button + low volume button would not work even after 10 minutes of holding it, would not boot to download or recovery mode, just the soft touch keys light on and the blue LED.
I reflashed my ROM from sammobile yesterday but did it half-effort, just dirty flashed it but it seemed to reformatted my phone anyway, after reflashing it, everything seemed to work properly for 20 hours and then now im back to this piece of ********* boot looping...
S7 Edge
running the Australia unbranded XSA-G935FXXS1DQG4 from the branded G935FXXS1DQG5,
would flashing de-branded affect this? or this is hardware?, one thing I did that I think was a mistake is that I chose to restore from old device, can apps cause this?
the very first time this happened, I plugged it in to charge then crash and bootloop.
UPDATE:
Things I've tried,
-Booting with NO sim card and SD Card
-Wiping cache and partition then reflashing stock XSA and OPS firmwares
im convinced that this is a hardware issue and will go to Samsung.
mine does this too. crashes then gets into a bootloop at the Samsung logo. I usually try holding the lock and volume down button. I factory reset the phone once but it still keeps happening, this started happening around 4 weeks ago
Guys your Main/Mother-boards are broken.. u need to replace it, or send back to Samsung..
Damn! Crash reboot samsung logo
Damn you say broken mother board...
did this. Press vol down, power button and home key...hmmm... i think...pressed so many combos hard to tell themapart
Hi all,
My Oneplus 2 mobile was got stuck in bootloader menu option. I thought some problem with os and done formate data and clear catch all the options and try to flash new rom using adb side load but it got faile. later only i noticed my volume. Down button got struck. Then i resolved that isse and phone started to boot but when it turns on screen suddenly goes black. Only volume button, power button working.
Tried to root the phone and flash nw os unable to do it since phone is not in debugging mode. Only adb sideload load working that to not able to install anyting transfer getting failed
Kindly someone help
So, I rooted and tried flashing the stock ROM (from Sammobile, same country, same exact model [SM-G950F], I already had the stock ROM and had never flashed anything else to the phone other than root, June security update, my phone had July's) to see if I could fix a problem that couldn't be fixed with any other method I had tried.
Everything in Odin seemed to go well, I got the PASS green box at the end. But then the phone couldn't go pass the Samsung logo when booting up. I left it quite a few minutes, before trying to boot into recovery mode and wiping data. Only to realize that I couldn't boot into recovery mode. In fact, I can't even turn the phone off. No combination of hardware keys works other than power button + bixby + vol down, to get into download mode. But that's of no use, because when I plug my phone into my PC (with the same cable and port I used before to root and flash the firmware into it) it is not recognized by Odin or the PC.
It just has the Samsung logo flashing slowly over and over because I can't turn the device off. By the time the battery dies out I'll most likely have the logo burnt into the display.
I also haven't been able to find any help online. Everyone's suggestion is “boot into recovery and wipe data”, but I can't do that.
Is my phone gone for good?
Hi guys!
I need your help with my Moto E4 Woods. I left it charging overnight. In the morning, it had a black screen. I tried pushing the power button with no result. I removed the battery and tried to boot again with no result. I thought that maybe an intervention in the TWRP recovery is needed (yes, it is rooted). When I try to access recovery, I have the screen working in the fastboot screen (or whatever you call the screen where you select to launch recovery, factory reset, start, etc...).
Whenever I choose recovery or start, nothing, black screen!!!
It was working on stock ROM, so I flashed it again using SP flashtool. Still the same issue. It works when I push Vol- and power, just to let me choose recovery or start then dive in darkness again.
Could it be a software issue? or hardware? what makes the screen work in fastboot mode then refuses to work when I select start or recovery or even push the power button normally? I might have thought the screen needs replacement, but it works just fine in fastboot. It is really annoying me and would really appreciate your help in the matter.
Thank you in advance!
Up
Hello, I have 2x S10 + Performance Edition (White and black)
SM-G975F/DS
1.5 years ago, the bootloaders were unlocked and the magisk (android 10) was installed, some time ago the root was removed by a normal restart in the black one
I updated the second (white) with odin to android 12, but then I couldn't root it at all, it just crashed a bug every time (while making magisk zip or after all while trying to start the phone), finally had to install stock 12 again.
I decided to sell black one, but now I have a problem that I cannot solve. At first I tried to lock the bootloader, it hung on the samsung log for 2-3 hours, then reseted it and crashed into a bootloop. Download screen and at the top the message
"ODIN MODE (AVB Fail) avbmeta: Error verifying vbmeta image: OKNOTSIGNED (3)
CUSTOM CBMETA
CBMETA: No sign info
VBMETA. "
From this position, I can reset it (vol down + power), quickly hold down vol down + bixby and connect the power to get to standard downloadmode.
Once I managed to start the system somehow, but I have no idea how. Cannot go to recovery, cannot start the system, it only bootloops to "downloadmode" with description above.
Normally, I would just install new stock with Odin, but the real problem is that my PC doesn't see the phone at all, nothing in Devices' manager, nothing in Odin.
When It comes to the white one - everything is visible and fine, so there is no problem with cables, drivers or PC itself. This phone is messed up.
I have no idea what to do with it now, any suggestions?
Thanks a lot