Bricked or screen is broken? - Xiaomi Redmi 3s Questions & Answers

Hello, I have redmi 3s 32GB , I have had developer rom and last friday as a many of you my phone was not able to be used, so I tried to flash global stable rom via fastmode commands, but phone was bricked, so I removed back cover and reset pins,of course reconnnected battery, after this phone was detected in win10 and I have installed global stable rom, pc now detect phone as redmi 3s, I saw my internal sdcard...but screen is still blank, I cannot see recovery boot, fastboot and no logo too. Could you help me? Is screen broken or is this software problem?
Regards

undulus said:
Hello, I have redmi 3s 32GB , I have had developer rom and last friday as a many of you my phone was not able to be used, so I tried to flash global stable rom via fastmode commands, but phone was bricked, so I removed back cover and reset pins,of course reconnnected battery, after this phone was detected in win10 and I have installed global stable rom, pc now detect phone as redmi 3s, I saw my internal sdcard...but screen is still blank, I cannot see recovery boot, fastboot and no logo too. Could you help me? Is screen broken or is this software problem?
Regards
Click to expand...
Click to collapse
Hi, open ur phone again and check the display connector, try fully disconnecting it and reconnecting it and check if all other connectors in range are also properly connected. Then reassemble ur phone.
Next time, do not open your phone unless you really have to. I don't see why you have opened to reset it. You can press power for very long then after maybe 30 seconds or so, your phone will fully turn off. No need to open it for that.
Next time if you have a question, use the Q&A section, not this one. You'll get answers quicker there too.

Bricked or screen is broken
Without disassembling I was not able to detect my phone, after pin reseting phone was identified in windows. No recovery boot was working too... This is reason why I disassembled phone...
But thank you for reply..

undulus said:
Without disassembling I was not able to detect my phone, after pin reseting phone was identified in windows. No recovery boot was working too... This is reason why I disassembled phone...
But thank you for reply..
Click to expand...
Click to collapse
if that worked, i'd be curious to know

Related

[Q] Tattoo Bricked

Hello,
I tried to update the radio and the SPL version on my Tattoo. Everything went fine until I had to reboot my phone. It shut down alright, but it never powered on again.
These are the following problems I am having with my Tattoo at the moment:
Cannot power on phone.
Cannot boot into recovery mode.
Cannot boot into FastBoot.
When I connect it to my computer via USB, nothing happens.
The only thing that it's responding to is when I connect my it to my charger.
Does anyone have a solution or is my phone dead forever?
Thanks ahead!
bump? anyone?
Send it back to HTC. If anyone can do anything about it they can. There's nothing else you can do. Sorry
boo.. that sucks..
Well, thanks anyway
Ehm, I don't want to post a New Thread so I'm gonna ask here:
Does anyone have the pinout for the Tattoo?
Take a look at this. I guess they fix such things (but you never know if they just are after your money. http://www.ort-jtag.com/index.php
Yeah I saw that already. Also, there is a file name Tattoo Jtag on their website in the Support section. However, to access that section you have to enter your products serial number (which is I'm guessing the phone's serial number). I have tried several serial numbers (including mine) and all of them were 'invalid' so I never checked the files out.
Also, they only have one thing in the shop which is a kit and it costs $330 so no thanks
I have a similar problem, I would like to share my knowledge although I must be completely out of way.
My experience is based on the BeagleBoard and Angstrom so I really don't know the HTC HW and Android at all...
- The device boots from an xloader that instructs the device how to proceed with the boot
- the bootloader takes place (great u-boot in the beagleboard ?? in the HTC phone) the bootloader allows for ROM or kernel+rootfs flashing and much more
- now the kernel is loaded.....
User mode applications do not allow to have access to the memory area where xloader and u-boot lie so they should be safe all the time to allow for device reflashing.
So we should have access to the device via bootloader anytime if we knew how... maybe somebody can help us further.
Fabio
Same here...Exact same issue...No Recovery mode...No USB Connectivity, Screen turns on but is blank, alhough I did see Tattoo popping up initially but not any more...All I can see is the LCD back light turns on...Battery does charge...Also when I try to enter Recovery mode screen keeps blinking as if it is trying to restart again and again...Someone help
similar problem here, but i get absolutely no response from the phone, it doesn't even recognize the charger. do i just throw it away and buy a decent one or is there a solution?
Sparky the only way for now to fix that click is to bring it to some service point that have that ort jtag, because only way to fix that is to writte new boot sector on phone . Im sure that i know at least 2 services that have ort jtag in Novi Sad . Look for marvel *Miroslav in Ns, or send me private message
same thing happened to me
just this morning, and in desperation I tried hard to remove the batt cover (prob pressed some of buttons, I felt a jerk and ho it was back in amon ra`s recovery, nect time I just removed the battery waited for 30 secs, then press off&home and hold it till recovery came back) but for good half hour NO REACTIONS , ABSOLUTE BRICK, nothing when I put the usb in PC or in socket, dead screen, no sounds and no reaction to ANY combination of keypress. I guess you could call me lucky (in last few days I flashed at least 3 versions of froyo roms, this afternoon I bought =8GB class4 Kingston, formated it in PC FAT32 default size, copied EVE. from my 2gig rom then just turned it down (yes I am brave) and put the 8gig in tattoo, it works like a charm (finger crossed it will continue)
So is there an available Jtag for the Tattoo yet?
I'm in the same situation. No recovery no fast boot, Damm!
I`ve update psfreedom with psgroove_hermes_v4 zip file then my tattoo reboot and now I only get the Tatto title screen but nothing happends.
Somebody have clue to give back life my phone.
Thanks!
if you can get to the title screen, that means you can connect it to your pc via USB and recover from a backup (I hope you made one)
Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.
payasi35 said:
Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.
Click to expand...
Click to collapse
You have to enter in fastboot.
Hold volume down and turn on phone.
Cheers
Sorry but as i said before, I can't access to recovery menu neither fast boot menu.

I can' get it to boot properly. Help me please!

A friend of mine gave me this phone after unexpected self shutdown. The phone was in a boot loop. At this point where I am right now I think I tried everything I can. I have read various guides and tutorials how to bring this phone back to life and nothing works for me. I suppose that there is some damage on mainboard but till I losse this phone I want to be sure. So the situation looks like this. Since the bootloader in locked and there is no working OS I am not able to unlock the bootloader. (If I am wrong here tell me please because I can't find a solution "how to unlock bootloader without having working OS"). The only metode to flash this phone in this state is to use QFIL. Flashing through fastboot fails everytime - booloader locked -> no *.img flashing. So I have 4 various versions of stock ROM for this phone and after flashing via QFIL the phone doesn't boot. It end with 3 possible ways. 1'st way - clasic bootloop. 2'nd way - frozen on loading screen. 3'rd way - black screen with blue LED, USB diagnostics state, 9006 port opened, no chance to flash because of closed QD port 9008. After this I have to erase every single one of the partitions made through flashing. Then I am able again to flash with QFIL.
I have no idea where is the problem here or what am I doing wrong. I tested the internal memory with a partitioning program in search of bad sectors -> 100% OK. Filled the whole memory with zero's and then formated it. It didn't help. Are every of my stock ROMs broken or is this phone realy damaged? Dear XDA community help me please! I have no clue what can I still try.
Tried ZUI QPST image or CM one?
ankurpandeyvns said:
Tried ZUI QPST image or CM one?
Click to expand...
Click to collapse
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
kotex said:
CM through QFIL already tried. Doesn't boot. I've got .zip ROM images but without TWRP no chance to use it. I have got also an image in .qsb file but no idea how to push it into the phone. Will it work through fastboot to put the file into the phone and than flash through diagnostic mode ?
Click to expand...
Click to collapse
Download the CM QFIL image from my video. It should work.
ankurpandeyvns said:
Download the CM QFIL image from my video. It should work.
Click to expand...
Click to collapse
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Borja Viera said:
I just recommend you downloading this https://drive.google.com/open?id=0B7zm16vLHfdBVi1lWlMwelBBdXc . It's ZUI 2.0.49 for qfil, hope it works for you.
Click to expand...
Click to collapse
OMG This room booted normaly. Thank you some much my friend! You made my day. It is a step forward. However all connections aren't working. I can't find "OEM unlocking" under Developer Options. I want to unlock the Bootloader as soon as possible so I will be able to put TWRP recovery and then flash it with any available CustomROM
kotex said:
Already tried your copy. To be honest tried it many times in every way I could. The phone is now sitting for over 3h frozen on loading screen. It is never going to boot or tell me that this is normal... Ereased the whole internal memory by delting every existing partition and then flashed it via QFIL. Also tried to format the whole memory in ext4. Same result. Like I said the phone is laying right now for over 3h on the same CYANOGEN screen with some graphical artifacts.
Click to expand...
Click to collapse
What's the result after flashing ZUI 2.5.330 image?
ankurpandeyvns said:
What's the result after flashing ZUI 2.5.330 image?
Click to expand...
Click to collapse
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
kotex said:
Many hours frozen on black screen with blue led. 9008 QD port blocked. 9006 USB Diagnostics port opened. No chance to flash until all partitions are erased and the port is reset. Otherwise I need to try getting to the 9008 port by puting the USB cable while holding the "Vol Up" button and then flash it agin with QFIL.
Click to expand...
Click to collapse
Got successful in flashing?
ankurpandeyvns said:
Got successful in flashing?
Click to expand...
Click to collapse
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
kotex said:
Yes
Right now thanks to Borja Viera I used the working OS to make a "sdfuse" folder on the internal memory, put the .qsb image file into the folder and flash the phone through diagnostic mode. I have got right now android 5.1.1 on it and it booted normaly However the connections still aren;t working. I managed to enable "OEM unlocking" then got to the fastboot mode with a bit of help from AIO tool (because turning the phone with pressed "Vol Up" and "Vol Down" buttons at the same time makes the menu but no "go to bootloader" shortcut over there). Unlocked the bootloader manualy with minimal ADB. Then I wasn't able to put TWRP as the recovery because of some weird error comming every time I tried the command. So I flashed the phone once again back to CM 12.1 soft only to get other "the better one - with many options" bootloader. Tried flashig TWRP once again and voila! TWRP working!! Bootloader unlocked! In a while I will be downloading some CustomROM and turn this phone back to life... I hope so
[UPDATE]
Tried 5 different ROMs:
Two Cyanogen:
1'st - black screen blue led usb diagnostics state with port 9006 opened
2'nd - frozen on loading screen
Three CustomROMs:
1'st Official Lineage
2'nd Unofficial Lineage
3'rd AICP-12.1
All three are not booting. Phone resets itself on loading screen -> boot loop. Do you have any sugestion right now? In TWRP everything wiped and ROM installed on clean phone. Gapps installed too from Open Gapps website. Eveything done right with the instructions.
Is this phone really damaged?
Click to expand...
Click to collapse
Do you have any telegram account, we could make things faster if we communicate that way.
ankurpandeyvns said:
If you're still in warranty, the best bet will be to get it replaced. Because it seems like a serious issue in the hardware.
Click to expand...
Click to collapse
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
kotex said:
Asked my firend about it. The phone is like 1 month old. He was making some pictures and the phone suddenly died and got to boot loop. He bought it new on ebay. Shipped from China. He already made some research about the warranty before he gave it to me. He made some calls and emails to customer service here in Germany and they told him that he has to send the phone back to China. No warranty in Germany. It is not worth to send it back to China because of duty tax on the way to China. They send him this phone on some special shipping method to avoid this taxes and stay with profitable shipping price. But if you need to send it back they won;t help you at all. And the dispatch price is a no-go.
Since I have decent experience with electronics and flashing various smartphones he gave it to me with a though that I will be able to bring it back to life.
I already said when I started this topic that I suppose that this phone has some damage on the mainboard because of the weird behaviour. I just want to be sure about that and try everything I can before I tell him that he wasted his money by buying this phone.
I want to thank you for your support! If you have some ideas what could I still try I will gladly listen.
Click to expand...
Click to collapse
If you have telegram, drop a message @ankurpandeyvns

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.
Ouh....DFU? I think this thing is totally bricked.
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...
twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.

[HELP] Redmi Note 4(3+64) RED STATE

I have a redmi note 4 mediatek variant and it's been stuck in bootloop for the past 2 days. It keeps restarting and doesn't go into fastboot mode.
The bootloader is locked. It won't go into recovery or fastboot. Sometimes it turns on when holding the power button but then goes into a bootloop.
This was the message last displayed on the phone:
RED STATE
YOUR DEVICE HAS FAILED VERIFICATION AND MAY NOT WORK PROPERLY
YOUR DEVICE WILL BOOT IN 5 SECONDS
And then it shut down and hasn't responded since.
Going to a service center probably won't help since this is a chinese variant and I live in India. The service centers here are mostly useless.
All help is greatly appreciated.
You can always try to do test point. Download official rom file and flasher, make sure to install fastboot drivers. Take apart your phone and connect two golden contacts on the motherboard while plugging in USB cable connected to PC. The phone should boot up to bootloader and you should be able to flash rom.
Test points should look like this: http://en.miui.com/thread-646232-1-1.html (scroll down, there is one photo)
If you need anything you can e-mail me on [email protected]
timipisoboy said:
You can always try to do test point. Download official rom file and flasher, make sure to install fastboot drivers. Take apart your phone and connect two golden contacts on the motherboard while plugging in USB cable connected to PC. The phone should boot up to bootloader and you should be able to flash rom.
Test points should look like this: http://en.miui.com/thread-646232-1-1.html (scroll down, there is one photo)
If you need anything you can e-mail me on [email protected]
Click to expand...
Click to collapse
I somehow got it working by completely draining out the battery and then booting. It worked for a while normally (around 30 min) and then went into a bootloop again.

Has anyone succeeded in repairing a bricked Poco M3?

My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
me too
waiting, someone pls
LeandroFarias said:
waiting, someone pls
Click to expand...
Click to collapse
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed).
That is the points
vinod3362 said:
That is the points
Click to expand...
Click to collapse
What?
me too. after i reboot my poco m3. it came to black and wont boot up. i google everything, the only need to flash is to modified the firehose. badly needed.
KaMyKaSii said:
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
Click to expand...
Click to collapse
how do you get into fastboot?? i tried mine but it wont boot in fastboot. i'm stuck in QDLoader.
did someone successfully recover their bricked poco m3 ?
gasleak08 said:
did someone successfully recover their bricked poco m3 ?
Click to expand...
Click to collapse
nothing yet. we need firehose to bypass miflash authentication. or drain the battery then press vol down + power for 10secs.
KaMyKaSii said:
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed). Are you Brazilian too? Call me on telegram
Matheus
You can contact @MatheusCoelho1998 right away.
t.me
Click to expand...
Click to collapse
can u tell me how?mine too?
my phone has bricked with UBL condition and i flash whole partition with twrp and magisk to solve the heating problem now its alive again
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Minoda86 said:
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Click to expand...
Click to collapse
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
I did update it and now my phone wont boot at all,after the battery hits 1%,it just wont do anything and its been 2 weeks,pc does detect it as qualcom loader but flashing without auth wont work,Im just waiting for firehose file for this stupid phone.People with auth asking for $30 for fixing it but without guarantee that it will work,what a joke.
So did you fix your phone?
yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
Yeahhh,my phone finally boot up!
But sadly the latest update failed to install.Guess I should just wait until someone patch the firehose file and try not to update until then.Fingercross!
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
vinzikidz said:
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
Click to expand...
Click to collapse
how did u fix deadboot can you elaborate? how did you flash from edl ?
gasleak08 said:
how did u fix deadboot can you elaborate? how did you flash from edl ?
Click to expand...
Click to collapse
sorry, there's is no tutorial for this and it has a quite process. you just need to throttle the proc temperature of your phone board using hot blower or any device you have. while your phone is in high temp. both pin board and battery is in unplug hold vol down then put back the board pin and battery pin at the same time. it will vibrate and fastboot will be fine.
Guys this is my procedure to turn on the phone:
I can make it turn on Android after messing with the battery and sub-board cables but this is just a workahound, trying to turn it on normally through the power button always makes it turn on in edl mode
But opening the device voids the warranty, so anyone who has access to a repair center is better off asking for the warranty
What to do:
1. Disconnect the battery cable and the secondary board cable.
2. Connect charger.
3. Hold the power button.
4. Connect the secondary board cable and quickly connect the battery cable.
5. Release the power button when the device vibrates.
It doesn't always work the first time, you may need several tries to get it
VID_20210514_152510.mp4
drive.google.com

Categories

Resources