I put it on the sd card;; xiaomi.eu_multi_MI11Lite5G_V12.0.7.0.RKICNXM_v12-11-fastboot..I ran it with twrp.. I don't think it's installed but from what I remember, I'm wondering about restarting in A or B partition. Now it doesn't start at all, not even in fastboot. It's a dead phone. Does anyone know how I can do it fix it. sorry for my English. thank you
georgevintila said:
I put it on the sd card;; xiaomi.eu_multi_MI11Lite5G_V12.0.7.0.RKICNXM_v12-11-fastboot..I ran it with twrp.. I don't think it's installed but from what I remember, I'm wondering about restarting in A or B partition. Now it doesn't start at all, not even in fastboot. It's a dead phone. Does anyone know how I can do it fix it. sorry for my English. thank you
Click to expand...
Click to collapse
Xiaomi.eu ROM named "fastboot" as yours should be installed through Fastboot, not through TWRP
Why didn't you first do your homework to read and study instructions for installation from Xiaomi forum?!?!
Table says that ROM is Fastboot type, and below, in the same post you have instructions for Fastboot installation:
'https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
Now you probably have to use MiFlash to install the stock ROM first
zgfg said:
ROM-ul Xiaomi.eu numit „fastboot” deoarece al tău ar trebui să fie instalat prin Fastboot, nu prin TWRP
De ce nu ți-ai făcut mai întâi temele să citești și să studiezi instrucțiunile de instalare de pe forumul Xiaomi?!?!
Click to expand...
Click to collapse
My mistake. Can someone help me fix it? And if YES with luxury details. I am a beginner in phones and computers
zgfg said:
Xiaomi.eu ROM named "fastboot" as yours should be installed through Fastboot, not through TWRP
Why didn't you first do your homework to read and study instructions for installation from Xiaomi forum?!?!
Table says that ROM is Fastboot type, and below, in the same post you have instructions for Fastboot installation:
'https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
Now you probably have to use MiFlash to install the stock ROM first
Click to expand...
Click to collapse
Sorry for the insistence. Connected to the laptop, it says -waiting for device. I tried ADB with fastboot getvar all, and it says waiting for device. In Mi Flash I see it connected to COM 10. but I can't install the rom. Nice evening and thanks for the tips
georgevintila said:
Sorry for the insistence. Connected to the laptop, it says -waiting for device. I tried ADB with fastboot getvar all, and it says waiting for device. In Mi Flash I see it connected to COM 10. but I can't install the rom. Nice evening and thanks for the tips
Click to expand...
Click to collapse
First, try different cable, reinstalling drivers, maybe another PC
I don't know what exactly might happened to your device when you tried installing Fastboot ROM through TWRP
If the same PC, with the same cable was recognizing the phone through Fastboot previously, and now you can no more make Fastboot to work - maybe you will need to seek for help from authorized EDL support (they charge), for low-level flashing
You can make sure your phone actually needs unlocking by inserting a SIM card from another network into your mobile phone. If it's locked, a message will appear on your home screen. The simplest way to unlock your device is to ring your provider and ask for a Network Unlock Code (NUC). For more information also see https://forum.xda-developers.com/ sinuanonoche 10elotto
Related
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.
hello i have i mi note pro that has been bricked for a while and im trying to fix it.
i think it has 2 problems that has to be solved but im not sure.
first thing that i tried to fix was that the device only started up when i was charging it from an adapter. when i connected it to the computer it just flashed the red dot with second in interval. i searched for a solution in forums and found out that similar problems had been solved by pulling the battery out and putting it in again after some minutes, but it did not fix the problem. and thats when i get to the second problem.
2nd prob is that, when i get my device started ( by having it connected to the adapter) it only flashes the mi logo. And i realized that i could start fastboot, and then quickly while fastboot is on connect to my computer. when i write sudo command "fastboot devices" i can see that it recognizes the device. (fastboot is unlocked also if that is to any importance.)
When i last used the phone i had a twrp and an unofficial ROM installed and it got bricked because i tried to install a new twrp or ROM, i cant remember.
I have a feeling that i tried install either a twrp or rom that wasnt compatible with what i had. i had marshmallow 6.x on the device and i think i tried installing something older or probably newer like nougat 7.x
i was wondering if i could some how install a new clean TWRP and ROM on my device trough fastboot so i can continue using this device again.
i would be grateful for any response or help
Hi read this post maybe can helo you
http://en.miui.com/thread-242767-1-1.html
Teddy Lo said:
Hi read this post maybe can helo you
http://en.miui.com/thread-242767-1-1.html
Click to expand...
Click to collapse
hey, thanks for the reply! i did try that tutorial on unbricking my phone. but i only have an laptop with linux on it and, 2 of the steps are not possible for me to do (install MiFlash and finding any Qualcomm HS-USB QDLoader 9008 drivers for linux).
i've tried to install a new rom through an unofficial tool that i found here on XDA - https://forum.xda-developers.com/android/software/tool-miflash-linux-t3708847 . But i haven't had any success with it yet.
maybe if you would know how i can force install a new ROM on my phone through the terminal on my computer the problem might get fixed?
this phone use mt6739.so i want to flash it the twrp to my phone.i dunno to unlock the bootloader but the twrp file not have for this device.
I just saw this post as I too have a Honor 7S
There is NO TWRP for our device.
The TWRP for the Honor 7A/7C/7X and Honor 7 doesn't work on our device and you got to pay 4 euros to unlock the bootloader before you can even flash TWRP (and there isn't one)
This Device is treble compatible but now I've found out there is zero development and no Devs Interested in it it's a complete and utter waste of time and has gone back into its box, never to be seen again.
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Samuel Ladziansky said:
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Click to expand...
Click to collapse
Hi I have a problem. I'm having brom issues in trying to flash it
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
usab1oy said:
Hi I have a problem. I'm having brom issues in trying to flash it
Click to expand...
Click to collapse
and little hint
dont flash whole rom if the phone can boot becasue after clean flash "format+download"
you lost log and cust partition because the image files are not secureboot signed and your phone get in to bootloop
and also you lost imei codes so no cellular after that
If you do so
you can fix it in that recovery were I enabled option to format log partition
after you format log to ext4, your phone will boot but without huawei/honor bootanimation
you dont need to worry about cust partition, if you didnt format it it still boot but without bootanimation and you lost some of garbage apps that are in that partition (amazon etc...)
(twrp boots in russian language, idk for now how to change it to boot in english or slovak lanuage (because Im from slovakia) and also it have Lenovo Logo becasuse I use sources from Lenovo A5 that have same cpu)
I will make in future separated thread for this....
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Samuel Ladziansky said:
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
Click to expand...
Click to collapse
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
usab1oy said:
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
Click to expand...
Click to collapse
you can patch it or flash it without disconecting the battery
Here is how:
turn it off
Push and hold volume down
While holding volume down connect usb cable
But is recomended to disconect battery because the phone can boot up instead to go in flash mode.
usab1oy said:
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Click to expand...
Click to collapse
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Samuel Ladziansky said:
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Click to expand...
Click to collapse
Yeah. For the flash mode, I wonder why his own he said I need to hold the volume up and down button at the same time. But thanks I'll do it and let you know.
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Samuel Ladziansky said:
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Click to expand...
Click to collapse
At this point. Might just abandon it. Thanks for everything. Ran into laptop issue on my third trial lol.
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Samuel Ladziansky said:
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Click to expand...
Click to collapse
Honestly. I spend a whole night researching videos for the phone. Only to get that link I send. And after all that. It still didn't work. Lol. I have a Poco x3 pro. I wonder if snapdragon android 12 can be rooted. Probably going to try it next month or so.
Snapdragon is eazy for root.
I have Redmi note 11 and it was easy, now I running on Android 13 from stock android 11, if you will need some help with something, I'm here, and I think there is device forum so there is community for that device
Update 2021.01.24: I consider the problem mentioned here as solved, since it can be resolved with MTK Bypass explained in the Guides Section. BE CAREFUL however to ONLY choose "Download Only" from the dropdown box in SP Flashtool! DO NOT select anything with "Format" in it, else you will lose S/N, MACs and IMEIs!
--- Original post ---
Hi, I have hard-bricked my new Realme 6 while trying to root it with Magisk. At the moment I am stuck in a bootloop at the power-on logo (realme in white letters). The boot animation (yellow realme letters) does not appear, instead the phone reboots after ~35 seconds. The bootloader says "Orange State".
I can NOT enter fastboot nor recovery mode by any key combination. Holding Power and Vol- makes the string RECOVERY MODE appear for a split second in the lower left part of the screen, however nothing happens afterwards.
I can power down by holding Power and Vol+ an releasing them immediately after the screen goes blank.
Holding Vol- and Vol+ while the phone is off and connecting USB makes a USB serial device appear on a windows machine for about 1-2 seconds before it disappears again.
I am very thankful for any hints on how to unbrick the device.
Here's what I have done in detail to mess up the phone:
1. OTA-Update to the latest OS in my region (EU11.A.48)
2. Unlocked the bootloader with the realme In-depth Test app (everything fine so far)
3. Download stock firmware RMX2001EU_11.A.48 ozip from realmeupdater.com
4. Unzipped with gnu unzip (content was readable, no extra decrytion tool for the ozip needed?) and extracted boot.img
5. Installed Magisk Manager and uploaded boot.img to the phone
6. Patched boot.img with Magisk Manager (and if I remeber correctly DIDN'T UNCHECK Preserve AVB 2.0/dm-verity)
7. Certainly FORGOT to do anything with vbmeta.img
8. Did NOT erase cache and userdata
9. Flashed patched boot.img directly and WITHOUT --disable-verity or --disable-verification
10. Rebooted the phone.
Am I correct that my problem is the AVB/dm-verity part?
Why does the modified boot.img affect the recovery (I thought they were seperate)
Can I try something with SP Flashtool?
I do have a second intact device that I didn't dare to touch yet, if that helps resolving the issue (e.g. for SP Flashtool readbacks).
As said any advice is highly welcome. Please ask I you need any more information to help.
I did that too... Magisk patched boot .img process of rooting is the risky process , I bricked my device, got it into red state.. tried thick and thin to revive using various flash tools, unable to do it, finally went to a shop , got it fixed, go-to a good repair shop, if you go to the service center, they will say replace motherboard for 5 k , I hope it helps, do traditional unlock bootloader TWRP recovery then flashing Magisk zip method for rooting process.
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Yes, you are right , red state means that, I guess bcoz, I may have formatted it and ran again unlocked bootloader but it showed unlocking failed, but I thought that I had previously unlocked it so it should be unlocked but I forgot to do that app thing process of deep test again, and I was on Android 10 latest and patched boot img of previous version using magisk, now I understand what mistake I made, I should have used boot IMG of current version of a 10 , but still I am afraid of doing this magisk method of rooting by patching boot IMG bcoz repair cost me 800/- , and I found out on YT that the latest version of a 10 of my device doesn't readily allows twrp and flashing zip of magisk.... Plus there are half baked info on important things, this is new device for me, I have had rooted Samsung and Lenovo, but rooting this is kind of tricky, bcoz it's still new, I think.... Want to try .... But I m afraid.... Tried fastboot method of TWRP flashing but can't replace stock room, so I guess I can't root .....
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
cmfan said:
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
Click to expand...
Click to collapse
Thnx man, I have rmx 1825 , but the process would be same for my device, I would have to search for it...
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
daeSundae said:
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Click to expand...
Click to collapse
I think there is no Emergency Download Mode in Realme devices.. pls guide ...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
daeSundae said:
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thnx that's a life saver, I am afraid to go forward with the device, this is promising, I will try, I found out that the new version c17 os Android 10 I am unable to root by twrp magisk zip flashing method, twrp isn't installing, there's an .ofp extracter, but it gives virus with software, unable to do, even talked on WhatsApp and gave him Gmail id, will try this method , I wanted the SP flash tool method, it's simple and can readily restore the stock rom... Thnx Sundae.. daesundae ... What kind of name is that...?? .. chuckles...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
cmfan said:
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
Click to expand...
Click to collapse
I saw everything that You posted, incidentally the YouTube video on this is on rmx1825 , thnx, whatever you posted it helped..
Hello, after a week waiting for unlocking the phone, i tried to install twrp unnoficial following a guide on the web... now the phone is totally bricked., it dosnt go into recovery mode only fastboot and after 10 seconds it restarts, i have adb installed properly on the pc, it detects my old poco f1 but the x3 gt isnt recognized and reboots after 10 seconds...
have anyone experienced this, or know of a possible solution? i really need help
ohh adding more info... maybe i messed up the boot partition, cause extracting the rom and looking at the flash_all.bat it says boot_ab and i did to boot... after this it entered the loop, it was recognizing the phone but i tried installing the room via miflash, gave error everytime i tried and now it isnt being recognized plus after 10 sec in fastboots it restarts... there is no charging battery creen just the loop
Just get a new device now
lol i dont want tooo... was thinking bout that
well... slowly, step by step using SP flash tool i am now able to see the poco logo and charging batery again... algo into fastboot i can get... gonna keep this updated in case anybody has this issue
btw.. there are 3 files i cannot flash, it gives error...
dpm_a.img
cust.img
rescue.img
rescue.img says mismatch, but i extradted the files from the downloaded poco rom, dows anybody know thy this happen?
well almost fixed... i managed to flash the room a while ago... now it can go into recovery mode, but says NV corrupted, any idea?
it can only boot into fastboot and recovery... i supose as it has something corrupted it wont boot into the system
Hello! (Read it fully)
I had the same problem, but i finally got it. First download the 12.5.7.0 rom from this page (Fastboot rom)
Xiaomi Poco X3 GT (chopin) Stock Firmware Collections
On this page, we will share all the latest Xiaomi Poco X3 GT (codenamed chopin) firmware flash files. To flash the firmware file, you need Xiaomi Mi Flash
www.getdroidtips.com
Then, go to Mi Flash Tool (also download from that page). The version you need is 20210226
Then unzip the rom as many times as it needs, and copy it (the most decompressed folder) to the desktop. Then, launch Mi Flash tool and install the drivers in drivers page. In the right corner you need to select "Clean all". And.... FLASH!
It solved my problem. I had the same as you. If your computer doesn't recognize your device, stay in fastboot 30 minutes and it will turn off automatically (with usb unplugged) or if it says no digest file found, turning off in 5 seconds turn it off.
I hope this can solve your problem.
Edit: Then update the firmware to 12.5.8.0 OTA way. Don't obey people saying stupidities like "Buy a new one". This is a forum, to help people, and if u don't know the solution, DON'T SAY ANYTHING
Bye
Ocelado said:
Hello! (Read it fully)
I had the same problem, but i finally got it. First download the 12.5.7.0 rom from this page (Fastboot rom)
Xiaomi Poco X3 GT (chopin) Stock Firmware Collections
On this page, we will share all the latest Xiaomi Poco X3 GT (codenamed chopin) firmware flash files. To flash the firmware file, you need Xiaomi Mi Flash
www.getdroidtips.com
Then, go to Mi Flash Tool (also download from that page). The version you need is 20210226
Then unzip the rom as many times as it needs, and copy it (the most decompressed folder) to the desktop. Then, launch Mi Flash tool and install the drivers in drivers page. In the right corner you need to select "Clean all". And.... FLASH!
It solved my problem. I had the same as you. If your computer doesn't recognize your device, stay in fastboot 30 minutes and it will turn off automatically (with usb unplugged) or if it says no digest file found, turning off in 5 seconds turn it off.
I hope this can solve your problem.
Edit: Then update the firmware to 12.5.8.0 OTA way. Don't obey people saying stupidities like "Buy a new one". This is a forum, to help people, and if u don't know the solution, DON'T SAY ANYTHING
Bye
Click to expand...
Click to collapse
eres español?
Ocelado said:
eres español?
Click to expand...
Click to collapse
Ocelado said:
yeah i speak spanish... well i will try, i flashed using sp flash tool, maybe its different using miflash?
Click to expand...
Click to collapse
i wanted to root my x3 gt but the unnoficial twrp around is what bricked my phone ahahaha
Hi bro! This is an unofficial twrp that works for me
POCO X3 GT TWRP
Download POCO X3 GT TWRP for free. None
sourceforge.net
Ocelado said:
Hi bro! This is an unofficial twrp that works for me
POCO X3 GT TWRP
Download POCO X3 GT TWRP for free. None
sourceforge.net
Click to expand...
Click to collapse
how did you installed, fastboot? what partition name did u use? i followed a guide that said recovery but x3 gt uses rescue i believe... this is wht bricked me
ohh btw i installed an enginering rom and now i was able to get into the phone... sadly on info, i have no mac address no imei... do someone know how to fix this?
Ocelado said:
Hi bro! This is an unofficial twrp that works for me
POCO X3 GT TWRP
Download POCO X3 GT TWRP for free. None
sourceforge.net
Click to expand...
Click to collapse
i flashed it to boot like the site says, but there is no recovery now... i can get into the system but no twrp recovery holding vol up and power
Rynhe said:
ohh btw i installed an enginering rom and now i was able to get into the phone... sadly on info, i have no mac address no imei... do someone know how to fix this?
Click to expand...
Click to collapse
you must turn on wifi to see mac address
Gaderg1992 said:
you must turn on wifi to see mac address
Click to expand...
Click to collapse
nope it wont let me.. i turn it on and does nothing...
I installed twrp on boot partition, and if you can't enter twrp reflash it.
Ocelado said:
I installed twrp on boot partition, and if you can't enter twrp reflash it.
Click to expand...
Click to collapse
man you are right.. idunno what hapened.. suddenly it jst booted in twrp
gl i hope i can help you. If you need more help just write here
Ocelado said:
gl i hope i can help you. If you need more help just write here
Click to expand...
Click to collapse
thanks... do you know of any custom rom for x3 gt? i cant use miui cause it says cant connect to google server at forst boot config
iv tried many gsi but none of these bots up after flashing to system
No... I don't know any rom...
2 things: have you installed the global rom? Try the global. Else, try skipping the logging in and then try it by entering gmail or in settings