Hi, I was trying to revert back to realme UI stock from Pixel Experience ROM on my Realme 5i device(RMX 2030 EX). So, first I tried to install stock recovery through Orange fox. But after installing the recovery, my phone got bricked and now it's not even being detected by the pc nor I can access fastboot mode. As PC is not detecting my phone, I can't use Realme Flash tool or cmd to change my recovery. What can I do? Please if you know, give me a fix. I would be so grateful to you. Thanks for your time.
Here are some methods that might work for you.
How to Access an Android Phone with a Broken Screen
Dealing with a broken screen on your Android phone is a hassle. Although phone screens are pretty tough, one nasty drop can shatter them completely. Given that most people have a lot of irreplaceable content on their phones, it is
www.alphr.com
@Aranya Kishor Das
My POV: If on Android device side neither adbd ( requires USB Debugging got enabled ) nor fastbootd ( requires OEM unlock got enabled ) is accessible although the device's matching OEM USB driver got installed on Windows computer, then it's recommended to take phone to authorized service center and let them try to fix it.
Related
Hello everybody,
My phone had some weird glitches, factory reset didn't work, and the capacative buttons didn't work anymore, and I had to restart the play store to install the apk after it downloaded the app. I made a new User, the buttons worked again and I could normally install apps. But it was a temporary fix, and as I couldn't factory reset I decided to unlock my bootloader because that resets your phone. So what I did is:
1. I installed all the proper drivers
2. I opened an commandprompt in the adb folder
3. I typed adb devices, it said unauthorized, I authorized it on my phone, and it said that it was authorized after that.
4. I typed adb reboot bootloader
5. I waited untill it went into fastboot mode and typed fastboot oem unlock (I had the function to unlock the bootloader enabled in developer options).
My phone rebooted after this, now it only shows the OnePlus logo and powered by android, it doesn't boot further. I can't return the phone as I bought it second hand. When I connect the phone to the laptop that I used for it (The usb cable was connected directly to the motherboard, incase that matters and it was an original 4 pin samsung cable), it recognizes it as an Android device, so I think it's a soft brick.
How to fix this? Thanks in advance.
-Oczosinkoo
Hi !
You can try this tutorial
https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Good luck !
Hi everyone,
A couple of days ago I rooted my Op6 and then decide to flash No limits rom via recovery (blu spark), as I was used to do with my last android phone, the Samsung Galaxy Note II.
Unfortunately I missed something and now it is stuck in the bootloader screen. Nothing works from the phone and I couldn’t revive it. I use a Mac but I tried all tools that are adviced here on XDA with my friend’s Sony Vaio but without success.
I managed to update drivers but I cannot run a flash-all.bat and I cannot use MSMdownload tool.
How can I do? Thanks to anyone who will manage to help me!!
EDIT: Sorry, just noticed you say you cant use the MSM tool. This one worked for me.
You could try this
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
Worked for me.
Check the guide about unbricking and if You are unable to use flash-all.bat so you Have to flash commands One by One. It's worked for me a few of months ago.
It doesn’t work either that way. I updated my drivers, but no computer is recognizing the phone.
I tried from changing usb cable or port to changing computer, to change methods.
I didn’t found any solution here on XDA, I tried everything!!
Make sure u use the cable included with the phone. Some cables doesn't work
Neither. I tried with the original and two others that I have.
if possible do you have windows? the flash-all.bat works for windows and is better to use(i was unable to use it normally in linux). What happens when you show flash.bat?
I tried Mac and Windows. On Windows it always shows in terminal "waiting for any device", even if I uploaded the drivers and made everything possible.
Did you put your OP6 into fastboot mode in correct way? I mean you might be doing the wrong procedure when entering fastboot mode.
It happened to me for the first time, I came from Samsung and I thought the phone needs to be stayed on the fastboot menu screen just like Samsung but no.
You need to turn it off and reboot it while pressing home and vol down button simultaneously until the PC recognize.
Good luck unbricking~
I always powered it on via power+volume up before connecting to the usb cable, because connecting it while powered off always resulted to power it on automatically on bootloader screen
i installed corvus os on Xiaomi Mi A3. After the process is completed i rebooted my phone and its not starting. no power on (my battery was 100% when i installed corvus os)
cant just turn on the phone
is the phone hard bricked.
or how can i fix it
Hardbricked means a hardware component no longer is working ( e.g. power button is broken ).
My guess is that the operating system you flashed or the installed software is corrupted, what means the phone got softbricked.
jwoegerbauer said:
Hardbricked means a hardware component no longer is working ( e.g. power button is broken ).
My guess is that the operating system you flashed or the installed software is corrupted, what means the phone got softbricked.
Click to expand...
Click to collapse
Ok thank you for the info
How do you think if its soft bricked could be started again atleast on fastboot
and i dont think its ard bricked because when i hold my power button after 5-8 seconds i can see my phone connected in the pc but only in device manager
i think this could maybe help me for something to fix it
When in Windows's Device Manager under tab Portable Devices phone is listed that simply means phone is connected in USB-MTP mode.
You can check whether phone is accessible by means of Fastboot running these commands - one by one - in Windows CMD prompt
Code:
fastboot devices
fastboot getvar all
jwoegerbauer said:
When in Windows's Device Manager under tab Portable Devices phone is listed that simply means phone is connected in USB-MTP mode.
You can check whether phone is accessible by means of Fastboot running these commands - one by one - in Windows CMD prompt
Code:
fastboot devices
fastboot getvar all
Click to expand...
Click to collapse
i checked but its not showing the device also i can see that my phone is connected by the icon at there but still the problem persists
it maybe a unsupported rom that i installed.
i tried for adb as well but no devices found
As I can see you're proud owner of a softbricked phone, what is neither accessible via Fastboot nor ADB.
My recommendation: Take phone to authorized service center and let them try to fix it.
jwoegerbauer said:
As I can see you're proud owner of a softbricked phone, what is neither accessible via Fastboot nor ADB.
My recommendation: Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
ok Thank you for your suggestions
yes:
my desktop (cause im in bootloader mode i'll need to use it) is artix linux with kde. sadly i cant install on it adb/fastboot and other drivers due to lack of systemd and empty repos so will do it probably from a random linux-based bootable usb...
my mobile is (as was in title) - xiaomi redmi go - european version.
what means ? my mobile have encryption after removing system what makes me unable to boot things... for the now i can still boot stock ROM. although i wanted to remove all associations with google in system (all google apps, bugs caused by removal etc...)
any ideas what i should do with it? wanna have it to tomorrow cause we use our mobiles at work and my current mobile got "marked as over outdated" by boss so i cant use
why noone ?
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go DinarGuru.com
Christinakim said:
This same things happen with me also but You need a USB cable to connect your phone to PC. You need to download ADB and Fastboot Tools to your PC and Extract it First of all, you need to enable the developer option and activate the USB debugging on Xiaomi Redmi Go. Now activate the OEM unlock status on your Xiaomi Redmi Go
Click to expand...
Click to collapse
this i actually know. i have one heavily modded lg so im not a newbie. its more about "encryption unsuccesful" broked roms leading to non-booting state (bootloop) etc... nothing from xda surely doesnt work, yep
surely nothing from : https://forum.xda-developers.com/m/techyminati.8245761/ works. was trying loads of times always bootloop. recovery posible to load but then tends to not make factory reset and lock in "encryption unusccesful", and thats worst... im in europe but have global version btw...
dead chat ?
Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.
I believe it's more likely motherboard. Is there any fix for it?