Bootloop mi 10T (can access fastboot mod and recovery) - Xiaomi Mi 10T / 10T Pro Questions & Answers

This is part of my other thread hopefully someone notice this since no one did with the other one
Bootloop with acces to recovery and fastboot
After the S20 screen screen died I decided to go Poco X3 pro then I was told that it dies randomly and after alot of googling the Mi 10T seemed like the perfect deal to ever exist for me so I went on and bought one yesterday 😄 so far so happy I...
forum.xda-developers.com
So like I said Xiaomi official repair centre refused to provide any help and after all my attempts have lead to failure I tried to check every phone repair centre I could find and non of them could help me at all so am here asking again can someone help me with the issue ? My phone been like that for weeks now
Somehow I keep attracting faulty phones one way or the other

Related

[Q] NVFlash tool "The Unbricker"?

I saw on this and any forums some NVFlasher tool unbrick posts.
So, my HTC One X is bricked and stuck in APX "NVFlasher" mode and i want to unbrick it.
A service in my country can't see the problem and returns my phone and i want to try unbrick...
Can anyone help me? How to use the NVFlasher?
Nobody got out of APX, there are a few guys working on it and they got out....but it lasted from a few hours to a day or so and the phone went back in APX. at this moment there is no real working solution. The main board needs replacement
But some guys got back to "life" if hold power button and some tricks...
Yeah and somebody else got out becose he rebooted like 100 times ! That's not really the solution mate .... APX is a hardware failure .... it will never be 100% anymore ......

xiaomi mi a2 lite - slow wake up, no sound after long standby and sporadic reboots

Hello,
6 days ago I got my second xiaomi mi a2 lite.
The first was rooted, enjoyed and finally sadly destroyed by accident.
The second one I've got is a little bit frustrating:
First, fresh out of the box, it did got stuck in an boot-loop.
Yes, I know, I should've get it replaced on first sight of the loop - but no, I had to try and did got it working again.
Then I rooted (thanks to https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952) and configured it.
Now I stuck with some disturbing problem:
1:
After it went in standby for some time, the phone will not wake up instantly after I press the power-button, but 3~6 seconds after the press.
2:
After wake up my whole phone is mute - No sound output what ever.
Only fix of this state, is to reboot the device.
3:
Sporadic reboots, mostly at night
Does anyone have any suggestions ?
I'm little bit frustrated
dl5doc said:
Yes, I know, I should've get it replaced on first sight of the loop - but no, I had to try and did got it working again.
Click to expand...
Click to collapse
I would have claimed warranty. Why do you want to live with a device which was faulty out of the box?
thorin0815 said:
I would have claimed warranty. Why do you want to live with a device which was faulty out of the box?
Click to expand...
Click to collapse
It was Saturday evening, nothing else to do and I was in need of an phone ... in short: despair
Is it be possible to claim warranty after rooting ?
have you tried to flash stock rom with MiFlashTool?
maybe your root/mods cause these problems
also you can relock Bootlader with Miflashtool.
warranty shouldnt be a Problem then.
merlin.berlin said:
have you tried to flash stock rom with MiFlashTool?
maybe your root/mods cause these problems
also you can relock Bootlader with Miflashtool.
warranty shouldnt be a Problem then.
Click to expand...
Click to collapse
Strange that no one else had encountered these Problems.
I've resigned and reflashed, relocked and reset the Phone.
Now it did went back to the store and I'm waiting for their analysis and reply.
[PROBLEM SOLVED] - kind of ...
Just got an new phone as an replacement.
I hope this one will live longer.
No boot-loop out of the box - so ... it seems be ok.

Honor 8 pro hard bricked

So long story short I tried to relock the bootloader with twrp installed. The result is the phone is in constant bootloop mode. I can't go to bootloader nor to recovery mode. The phone boots, paces the bluish honor logo and gets stuck on some EMUI logo on a black screen. Fastboot mode is not acccesible, the PC can't detect the phone at all. No combination of buttons pressed works. I also tried the dload method to no avail.
Anybody been in this situation before? Any solution or any ideas, guys?
Thanks in advance.
Guys, am the only lucky one in this situations?
Hello need help or a hint.on the hands of there is honor 8 Pro.I decided to roll back the firmware.flew off under roll all that can be and cannot be.wrote man he only was able help those that flashed his Board firmware.nothing has changed just started charging.dripped on.bought prog hcu client and phoenix.the first helped I was able to recover my IMEI and so on but still did not.Phoenix should actually liven up any bricks.but he didn't help.was poking around on say what script you need but what no one knows.
andryxa888888888888 said:
Hello need help or a hint.on the hands of there is honor 8 Pro.I decided to roll back the firmware.flew off under roll all that can be and cannot be.wrote man he only was able help those that flashed his Board firmware.nothing has changed just started charging.dripped on.bought prog hcu client and phoenix.the first helped I was able to recover my IMEI and so on but still did not.Phoenix should actually liven up any bricks.but he didn't help.was poking around on say what script you need but what no one knows.
Click to expand...
Click to collapse
Did you resolve an issue?

Help with unusually bricked device

Hey everyone, I would like to say thanks in advance for any help/time spent towards helping me resolve this issue.
I've had a Redmi Note 5a Prime for a little over a year now. 2 days ago, it was dropped in water. Completely submerged. As soon as I realized, I took the back off and removed the battery. Every attempt I made to revive it didn't work. Finally, I tried a last ditch solution. I removed the logic board and remove the cameras from it and soaked the board in a solution of 91% alcohol. I scrubbed it clean with a toothbrush and also the connector ends. I let it dry for a very long time and finally got it to boot to the Mi logo. That's as far as I got. So, I figured software was corrupted. I looked into unlocking the bootloader to reflash stock firmware, but I get an error that the account isn't attached to the device. I am 100% sure I used the correct account. It's the only one I have. I'm not sure if it's because I also have a Redmi Note 4 attached to the same account or what.
Anyways, between trying different methods to restore firmware, somehow I randomly got the phone to boot and used it all night last night. Today, it's back to being stuck on Mi logo. I tried EDL test point method to flash fastboot rom, and it was successful but still stuck on Mi logo.
Any ideas? Maybe a hardware problem? Maybe it's done for. I'm not sure but I do apprectiate the help. Thanks.
Also, I apologise if this is in the wrong section. I looked thoroughly before posting.
Also, forgot to mention, I don't have usb debugging enabled and the bootloader is locked. I can access both fastboot and Mi Recovery. When choosing to wipe all data in recovery, it switches to a blank screen with 1% and then completely goes blank and I have to hard reset/ battery pull.

Xiaomi Hard Brick Story - (RN8 Pro) Share your experience

Please share your stories or your thoughts what stupid thing you did to make your RN8 Pro Bricked (If not: tell how the first time you bricked your device :crying: )
My side story: I tried to flash Android 9 with Android 10 unofficial recovery & in result Bricked/Dead & device with no response at all, just light blinks & that's it. :crying::crying::crying:
Also Please share your story & also update your answer how you guys fixed it.
Also I will update my Story How I fixed my Hard Brick RN8 Pro Device in this Dark Time :'(
I Hope this thread will make some of you laugh by hearing someone's funny story,
or you will able to understand someone else feelings or you will able to feel better by hearing your experience or hearing someone's else story like yours in this Hard Brick World.
Hope this thread will make good people or devs to come here & start helping each other. hope soon we will get a new way to fix our device without having mi authorized account.
simply poor move
Xiaomi did the worst thing, I could imaging. I proudly recommended Xiaomi over Huawei, because the bootloader is unlockable.
I also own a Mi 9T, which easily modable.
The simple thing like flashing TWRP and a boot.img fried my Redmi Note 8 Pro after 7 days of ownership.
I opened the device (falsely first from the front removing the display, then gettin the guts that it must be done from the back. Cracked the back glass, ordered a new glass for 3 bucks). Pulling the battery and ack that this will not solve the EDL Mode issue.
The device was now a warrantly less mess, no service center in the world would take on.
I replaced the back and reglued the screen and payed a russian savior to bypass the Xiaomi Authorized Challenge ( a russian GSM forum, I don’t know if posting a link is allowed, so I won’t). It was 20$, far cheaper than a new Mainboard.
Device is now reborn, bootloader still unlocked, but I won‘t ever try to root this piece again.
Hardlocking a flash tool, which is commonly used for cheap 80$ MTK phones is strange. I understand that Xiaomi Shop Rom issue a while ago, but a flash only allowed by China and Russia seams not really better than the Huawei way...
The phone is now used as a Escooter Dashboard/Tachometer, because I don‘t value it any more.
Ceynt said:
Xiaomi did the worst thing, I could imaging. I proudly recommended Xiaomi over Huawei, because the bootloader is unlockable.
I also own a Mi 9T, which easily modable.
The simple thing like flashing TWRP and a boot.img fried my Redmi Note 8 Pro after 7 days of ownership.
I opened the device (falsely first from the front removing the display, then gettin the guts that it must be done from the back. Cracked the back glass, ordered a new glass for 3 bucks). Pulling the battery and ack that this will not solve the EDL Mode issue.
The device was now a warrantly less mess, no service center in the world would take on.
I replaced the back and reglued the screen and payed a russian savior to bypass the Xiaomi Authorized Challenge ( a russian GSM forum, I don’t know if posting a link is allowed, so I won’t). It was 20$, far cheaper than a new Mainboard.
Device is now reborn, bootloader still unlocked, but I won‘t ever try to root this piece again.
Hardlocking a flash tool, which is commonly used for cheap 80$ MTK phones is strange. I understand that Xiaomi Shop Rom issue a while ago, but a flash only allowed by China and Russia seams not really better than the Huawei way...
The phone is now used as a Escooter Dashboard/Tachometer, because I don‘t value it any more.
Click to expand...
Click to collapse
hmm in a same situation, decided to never gonna root this device again
just don't want to take any risk now, will try to use it normally.
glad i didn't opened the back panel, i don't wanted to take a risk
also my device was in warranty so i decided to send it to Xiaomi Service Care Center.
also there was a Gyro Problem in my device. hopefully they will return in a week,
& they also took my Gmail account/password for some reason.
I have a story fot my RN8P goes yo HARDBRICK, the first
I want to reflash the stock rom ( android 9 ) using LR TWRP, and reboot device is normal, no brick or bootloop, and next week I want to reflash again, because my Lucky Patcher can't instal app.
And I think if I reflash my stock Rom, my TWRP is lost, and I think flash stock is done, I flash TWRP .img using TWRP, but I wrong because I choose flash for "boot" not "recovery",
And I think the first reboot to TWRP for fix it, and my RN8P goes to HARDBRICK, from Mei until now -_-
cyberz2 said:
I have a story fot my RN8P goes yo HARDBRICK, the first
I want to reflash the stock rom ( android 9 ) using LR TWRP, and reboot device is normal, no brick or bootloop, and next week I want to reflash again, because my Lucky Patcher can't instal app.
And I think if I reflash my stock Rom, my TWRP is lost, and I think flash stock is done, I flash TWRP .img using TWRP, but I wrong because I choose flash for "boot" not "recovery",
And I think the first reboot to TWRP for fix it, and my RN8P goes to HARDBRICK, from Mei until now -_-
Click to expand...
Click to collapse
Hmmm i received my device from customer care center after 17 days but without charges that's good for me
Nouman112 said:
Hmmm i received my device from customer care center after 17 days but without charges that's good for me
Click to expand...
Click to collapse
How thet figure it?
Nouman112 said:
Please share your stories or your thoughts what stupid thing you did to make your RN8 Pro Bricked (If not: tell how the first time you bricked your device :crying: )
My side story: I tried to flash Android 9 with Android 10 unofficial recovery & in result Bricked/Dead & device with no response at all, just light blinks & that's it. :crying::crying::crying:
Also Please share your story & also update your answer how you guys fixed it.
Also I will update my Story How I fixed my Hard Brick RN8 Pro Device in this Dark Time :'(
I Hope this thread will make some of you laugh by hearing someone's funny story,
or you will able to understand someone else feelings or you will able to feel better by hearing your experience or hearing someone's else story like yours in this Hard Brick World.
Hope this thread will make good people or devs to come here & start helping each other. hope soon we will get a new way to fix our device without having mi authorized account.
Click to expand...
Click to collapse
My story isn't too funny because this is the only time I got hard bricked and fortunately had anti brick flashed.
I was just tinkering around with logo.bin, the bootlogo of device, I found a MTK boot logo editor tool on XDA, succesfully edited and gave to my tester to test, turns out it didn't work, usual bootlogo showed up but didn't go past it, turns out the flashing location of logo.bin in auto generated flashable zip was wrong, I edited it to correct one and took the courageous step to flash it on my device, my bad luck, I would't exactly say it got hard bricked because I could access vol down menu in CFW 1, but still clicking on recovery or fastboot made it reboot with backlight on, my heartbeat went rapidly up LOL, but by god's grace I easily flashed the device with SP flash tool
samuuurai said:
My story isn't too funny because this is the only time I got hard bricked and fortunately had anti brick flashed.
I was just tinkering around with logo.bin, the bootlogo of device, I found a MTK boot logo editor tool on XDA, succesfully edited and gave to my tester to test, turns out it didn't work, usual bootlogo showed up but didn't go past it, turns out the flashing location of logo.bin in auto generated flashable zip was wrong, I edited it to correct one and took the courageous step to flash it on my device, my bad luck, I would't exactly say it got hard bricked because I could access vol down menu in CFW 1, but still clicking on recovery or fastboot made it reboot with backlight on, my heartbeat went rapidly up LOL, but by god's grace I easily flashed the device with SP flash tool
Click to expand...
Click to collapse
And how did you do it, because i've tried many tutorials and none of them works... I think i'll just buy a new board.. Because its impossible to do anything, Tried sp flash with error 0xC0060005 that says i need authentication (that mi authorized account)
Any help is appreciated.

Categories

Resources