Hi all,
My Oneplus 7T shutdown and wouldn't boot. I did the following:
Tried the MSM tool - didn't work (booted up but then the screen went fuzzy and hung)
Now the phone wont even power up.
Is there anything I can do via software to troubleshoot?
Related
So i have a Rogers lg g3 (model d852)
The thing is i interrupted it in the middle of an update which was taking too long (was at 20 pourcent and didnt move)
So now its not working, its at a black screen with a flashing red and blue LED.
I was able to fix it before by entering download mode and reflashing the tot but now its worse than ever, before when i plugged it in to charge it showed the charging screen then blacked out and the LED turned on, now it goes to a backlight screen and then continues to a black screen with the LEDs, also i cant access factory reset or download mode.
However there is something Crazy with this phone when i plug it in on the black screen with the blue and red LED and i press volume up my pc detects it as qualcomm HS-USB qdloer however when i try boardiag 3.99 it says error device was not found in dload trying flash programmer.
So do i have to abandon and buy a new phone or can i do something about it
Any help is apreciated
Eghtesad
SO guys the thing is that i was able to run an sdram test that the phone past (willcrack 2.99) however still no dnload mode nor factory reset
Hello,
I own a OnePlus 3, running stock firmware (up to date). I never tinkered much with it*: it has never been rooted and the bootloader stayed locked.
Yesterday I have been welcomed by a white on black text saying “The dm-verity is not started in enforcing mode and may not work properly – your device will boot in 5 seconds”. Letting it continue the boot sequence shows the 1+ logo and then the phone becomes unresponsive with a totally black screen (pink notification led on though).
Pressing volume key on the dm-verity message reveal more options : Power off, Restart, Recovery, Fastboot, Back to previous page.
Recovery seems to restart the phone and bring me back to the dm-verity message.
Fastboot options (Start, Restart bootloader, Recovery mode) do nothing or bring me back to the dm-verity screen too.
What I have tried so far :
- Booting it with power button+vol up or power + volume dows ;
- Testing that is is seen by the fastboot command from my laptop (it is) ;
- Opening the phone and disconnecting the battery for several minutes and reconnecting the battery (does nothing).
Did I missed something ? Is there a way to have it working again and back-up my data ?
Any help greatly appreciated !
Rodoro said:
Hello,
I own a OnePlus 3, running stock firmware (up to date). I never tinkered much with it*: it has never been rooted and the bootloader stayed locked.
Yesterday I have been welcomed by a white on black text saying “The dm-verity is not started in enforcing mode and may not work properly – your device will boot in 5 seconds”. Letting it continue the boot sequence shows the 1+ logo and then the phone becomes unresponsive with a totally black screen (pink notification led on though).
Pressing volume key on the dm-verity message reveal more options : Power off, Restart, Recovery, Fastboot, Back to previous page.
Recovery seems to restart the phone and bring me back to the dm-verity message.
Fastboot options (Start, Restart bootloader, Recovery mode) do nothing or bring me back to the dm-verity screen too.
What I have tried so far :
- Booting it with power button+vol up or power + volume dows ;
- Testing that is is seen by the fastboot command from my laptop (it is) ;
- Opening the phone and disconnecting the battery for several minutes and reconnecting the battery (does nothing).
Did I missed something ? Is there a way to have it working again and back-up my data ?
Any help greatly appreciated !
Click to expand...
Click to collapse
It might be a hardware issue since you did not meddle with it. If so, you will have to go to the service center.
Before that, it is worth trying out the various Unbrick Tools available in the OP 3 forum. Search for them and try a few. Sometimes it requires repeated attempts before the phone responds. I know because i have gone through the unbrick procedure earlier. Please note that the tool is different for 3 & 3T.
Best of luck!
EDIT:
Before attempting anything, backup your data to the PC with adb commands (as it is working now, according to you). It is possible and search for it.
TNSMANI said:
It might be a hardware issue since you did not meddle with it. If so, you will have to go to the service center.
Before that, it is worth trying out the various Unbrick Tools available in the OP 3 forum. Search for them and try a few. Sometimes it requires repeated attempts before the phone responds. I know because i have gone through the unbrick procedure earlier. Please note that the tool is different for 3 & 3T.
Best of luck!
EDIT:
Before attempting anything, backup your data to the PC with adb commands (as it is working now, according to you). It is possible and search for it.
Click to expand...
Click to collapse
Thanks for your feedback TNSMANI, I’ll give those unbrick tool a try. As for adb it’s not working unfortunately… but that was expected given I never bothered activating USB debugging. Fastbook commands do work but I can’t do much with them regarding data recovery.
Hello,
I bought a "bricked" Galaxy Tab S4 on ebay. The only info I got was, that it is stuck in a bootloop since the last automatic update.
The bootloop is similar to this one. The tablet starts with the Samsung logo, then nothing happens and after a while I end up in recovery mode. Further, if I restart or hardreset the tablet, the screen stays black. The only way to boot it up again is to empty the battery while it is stuck in the bootloop. Afterwards I can enter download mode by holding "vol up and down" and plugin the usb cable.
In download mode this text appears at the bottom left:
#reboot recovery cause [unknown]
API: 3
manual mode 1.0.0
(Similar to this thread.)
OEM lock is on and of course I can't change this being stuck in the bootloop, or can I?
I successfully flashed the stock rom T830XXU5CUE2 with Odin3_v3.14.4 and latest samsung drivers. Unfortunately it does not help or fix anything. (I used virtualbox, but it worked and said "PASS" at the end).
After some research I would like to try my luck with a combination rom, but I can't find a U5 version which I should use because of T830XXU5CUE2, is that correct?
Any ideas how I could proceed from here? With OEM lock I guess there is no chance to flash TWRP on it?
So when I try to install TWRP (for Lineago OS) I was getting the "fastboot_init" screen and wasn't able to pass it. After some research I found out that my software may be the issue, so to turn the normal state of my phone I flashed this kdz file with LG Flash Tool 2014 in Download Mode.
After that, I booted. I was able to hear the constant starting song with black screen right after I saw the LG logo. After restarting the phone, I'm only able to see charging info and a red light when I plug a usb.
Notes:
- I tried to force restart with Power + Volume Up combination.
- First photo is not mine (shows the same thing)
Problem solved. Try the keyword "soft bricked".
Note that you enter the download mode if you, unplug battery & USB and press Volume Up connect the usb that you attached it to a PC.
Hello! I recently tried to install this ROM on my Redmi Note 8: MiuiTN_Ver1.8_Ginkgo21.11.24(0102)_ffc0. However, after the installation, the console indicated that the device may not start because there is no boot.img. I installed recovery.img, thinking that it was the same thing, but after restarting my phone, it displays a black screen for about one second and then turns off. When I try to boot into my bootloader or put my phone in fastboot mode, it displays the same black screen. Is there any solution or is my phone done for?
Hi, I have been attempting to use EDL mode for several hours, but I have not been successful in my attempts.