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.
Hello. I'm an owner of a Xiaomi Redmi 9A and I have following rooting problems with it:
1. while beeing in phone's fastboot mode and after sending from the computer's terminal (after sucessfull connection):
"fastboot oem unlock"
the phone "thinks" for a short bit before restarting itself without doing anything
2. I have a Xiaomi account bound to the phone and when selecting the "check unlock state" the phone ask me to turn off wifi, enable the (paid) data transfer and bind the phone to the account
3. while using the official Xaiomi unlock tool (with was downloaded from the phone producer's website), the phone isn't even seen in it
Could anyone help me ?
Try installing usb drivers or the phone will never be detected.
VD171 said:
Try installing usb drivers or the phone . never be detected.
Click to expand...
Click to collapse
in case of adb and fastboot, I had used them on Linux.
Only the official unlocking tool was for Windows, on with the usb drivers were installed.
Linux detect it without any issue
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
VD171 said:
Just use it to unlock on Linux:
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
xiaomitool.com
Click to expand...
Click to collapse
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
mcgiwer said:
thanks, but it seem to don't work correctly with my phone.
After my phone had become detected when was in the fastboot mode and after clicking the "select" button in the app, the phone has rebooted to the normal mode and asked to scan again. It hasn't done anything except the mentioned above.
Click to expand...
Click to collapse
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
VD171 said:
Did you enable usb debugging on developer settings?
Did you allow the usb debugging for the actual computer?
Click to expand...
Click to collapse
yes in both cases... I have even enabled the "oem unlock" option in the setting
Install windows on partition 30Gb, change cable
yaro666 said:
Install windows on partition 30Gb, change cable
Click to expand...
Click to collapse
The cable is new and I won't wipe my Linux to install a Windows (about with I have a bad opinion)
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
yaro666 said:
Make a dual boot, just resize partition, you need 30Gb and in 45min you will know what is the problem.
Or you can try to liveboot windows from usb stick.
Click to expand...
Click to collapse
Question: Why do you push so much on me to install Windows?
This forum is dedicated to mobile phones and my topic is about anormal phone behaviour of a phone while attempt to root it. Wiping out a safe Linux and installing a Windows won't help at all....
I tryed to root the phone on friend's laptop with a Windows (with the latest drivers and software installed) and it didn't worked.
I suspect that the producer probably has fabrically instaled a damaged or improper firmware
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
yaro666 said:
As you wish. Windows is more device friendly. I just suggest to do it on W, nothing more.
You state that fastboot works, but Linux don't see your phone, like in case you don't have drivers for adb. We don't know if you installed everything on Linux properly
Click to expand...
Click to collapse
hello. You had missread my post. I wrote that it isn't seen only in the unlock software. Fastboot and ADB detect it correctly
My Xiaomi Redmi Note 8 Pro isn't booting anymore.
I'm stuck in the fastboot screen, I don't even reach the redmi logo in the boot, I need to recover the data on the phone but I have no idea about how to do that.
Any suggestions?
(Already tried going to recovery with power down + volume up, isn't working)
I'm stuck in the fastboot screen
Click to expand...
Click to collapse
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
OldNoobOne said:
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
Click to expand...
Click to collapse
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
BrickedXiaomi said:
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
Click to expand...
Click to collapse
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
OldNoobOne said:
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
Click to expand...
Click to collapse
I'll try tomorrow, thanks for all the precious details btw!
Just a question, shouldn't I unlock the phone with mi unlocker before that?
BrickedXiaomi said:
Just a question, shouldn't I unlock the phone with mi unlocker before that?
Click to expand...
Click to collapse
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
OldNoobOne said:
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
Click to expand...
Click to collapse
As said, I never modified this phone, is basically as if it was brand new, OS side.
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
BrickedXiaomi said:
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
Click to expand...
Click to collapse
Wow thats great link, I hope it works so you don't lose data.
The link is fresh so you can also ask there. All the Best
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
BrickedXiaomi said:
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
Click to expand...
Click to collapse
Is your phone In-Warranty? If yes or no i would suggest go your own way, once purchased an used any device, don't connect with OEM servers ever again for any OTA update coz lots of recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates and after that the phone doesnt boot, no recovery no fastboot too, so careful with contacting/updating through OEMs if out -of-warranty specially. Once out-of-warranty always use ROM channels to upgrade to new handroid versions instead of direct OTA upgrade/update, that way you may still be able to roll back the OS to previous version in case you don't like the new handroid version, lots of people don't like handroid 12 but they cant roll back to handroid 11 .
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
BrickedXiaomi said:
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
Click to expand...
Click to collapse
Yes they might not try doing that with uropean customers but they might try in other countries where there no proper legal system for things like these, also they wont do it with everyone in a particular country to avoid suspicion, theyre smart enough to know what theyre doing, but unofficially speaking many retailers have told me about such a thing (OTA Kill Device) happening in Weaker-Law-N-Order countries, so just saying precaution is always good.
BTW i've put my Retmi Noat 10 up for sale, its still in warranty & I havent used it in the last 10 months, no sim card, unused totally, just once I loaded Gcam to check how the camera is, shamshung is always better than chyneez phones mainly coz better build and component-life, chyneez devices only look shiny from outside but it doesnt last beyond 3-5 yrs, not built to last, just use-n-throw devices u knw. Such devices are only made for mass-surveillance in mind not with customers-focus. This A/B partition thing and super partition thing is adding more bad than good.
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded* to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup off your device in preloader mode (SLA/DAA bypass and VCOM drivers needed)
After that important step you can unlock bootloader with mtkclient, install TWRP and *proof me wrong (xiaomi devices are hackable/have weak security implementations). In any case do not perform factory reset, your backup is always only backup of android OS and therefore incomplete (there are several OS on every device)
btw fastboot doesn't require usb-debugging (that's adb, not fastboot)
Do you have a tutorial about it?
aIecxs said:
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup of your device in EDL mode (patched firehose programmer and deep flash cable needed)
Click to expand...
Click to collapse
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?