Hello everyone! This is the first time I'm posting something in this forum, I've had a serious problem with my Redmi S2 two days ago, it suddenly bricked with no reason (I didn't install any custom ROMS or tried to unlock the bootloader), so I've searched for some YouTube videos on how to unbrick the device with the EDL method (Two pin short).
So I've opened the phone, shortened the two pins, and connected to my PC, and after many attempts, it didn't work, I've tried everything, from installing custom drivers for Qualcomm, many different bootloader ROMS (Chinese and global), and often times it would give a "hello packet" error, or an error like this:
[15:24:14]:5 COM5 8,5382533s [15:24:14 COM5]:resdump:<?xml version="1.0" encoding="UTF-8" ?><data><log value="Write failed Sector 320, Errno 3" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 320" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried using different USB cables and ports, same thing...
I've contacted a repair shop to try fix it, but they said it couldn't be fixed because supposedly I've corrupted something in the phone (?)
Anyways, I'm doing everything to try recovering my phone, any help would be much appreciated!
Thank you!
massayuki said:
Hello everyone! This is the first time I'm posting something in this forum, I've had a serious problem with my Redmi S2 two days ago, it suddenly bricked with no reason (I didn't install any custom ROMS or tried to unlock the bootloader), so I've searched for some YouTube videos on how to unbrick the device with the EDL method (Two pin short).
So I've opened the phone, shortened the two pins, and connected to my PC, and after many attempts, it didn't work, I've tried everything, from installing custom drivers for Qualcomm, many different bootloader ROMS (Chinese and global), and often times it would give a "hello packet" error, or an error like this:
[15:24:14]:5 COM5 8,5382533s [15:24:14 COM5]:resdump:<?xml version="1.0" encoding="UTF-8" ?><data><log value="Write failed Sector 320, Errno 3" /></data><?xml version="1.0" encoding="UTF-8" ?><data><log value="Finished sector address 320" /></data><?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
Tried using different USB cables and ports, same thing...
I've contacted a repair shop to try fix it, but they said it couldn't be fixed because supposedly I've corrupted something in the phone (?)
Anyways, I'm doing everything to try recovering my phone, any help would be much appreciated!
Thank you!
Click to expand...
Click to collapse
It seems like your eMMC chip gave up just go to a xioami service center and try to repair it from there.
Sent from my [device_name] using XDA-Developers Legacy app
It seems almost practically impossible that a smart-phone gets "suddenly bricked", especially for a quality brand like Redmi.
I've seen my fair share of phone usage and even rooted a few phones. In my experience (and reading on Mi forums), an attempt at rooting or unlocking of bootloader is what causes a brick in about ~99% of cases. Otherwise, you can practically do almost anything you can think of including factory resetting your phone, do file-transfers, usb-debug an app using android studio, etc. and there is no chance it would even budge.
Remember what caused the phone to brick in the first place, that will help you with finding the solution. Perhaps you gave it to a friend or relative who tried to unlock the bootloader?
prahladyeri said:
It seems almost practically impossible that a smart-phone gets "suddenly bricked", especially for a quality brand like Redmi.
I've seen my fair share of phone usage and even rooted a few phones. In my experience (and reading on Mi forums), an attempt at rooting or unlocking of bootloader is what causes a brick in about ~99% of cases. Otherwise, you can practically do almost anything you can think of including factory resetting your phone, do file-transfers, usb-debug an app using android studio, etc. and there is no chance it would even budge.
Remember what caused the phone to brick in the first place, that will help you with finding the solution. Perhaps you gave it to a friend or relative who tried to unlock the bootloader?
Click to expand...
Click to collapse
I had a similar issue on a Nexus 5 It had a worn out Nand flash on beginning the apps started crashing then the phone randomly rebooted and finally died.
Sent from my [device_name] using XDA-Developers Legacy app
I also have the same problem, ..... always get an error, can not read from port com ....
Related
Hello everyone, I bought an LG L70 Dual D325F which was soft-bricked hoping it as to be easily fixed via flashing the stock firmware, but to my great surprise, I was unable to access the download mode, I was facing the "DemiGod Crash Handler : DBI Err Fatal!"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I tried this tutorial, but I after following the thread, the device switch to Qualcomm HS-USB QDLoader 9008, thus I started searching a solution, then I found out about this method, which involved the use of an SD Card, thus it did worked out, and I was able to boot to download mode in order to flash the firmware, but the firmware flashing was getting stuck and then reset while displaying 'ASSERT' in Red at 7%, sometimes at 15% and the maximum I did reach was 33%, before restarting again.
Then after spending hours on google, I found out that the it is normal and that I should keep forcing until 100%, but after my attempt to 33%, the process wouldn't past 7%, thus I googled for another method then I came across a method involving BoardDiag 3.99, thus when I tried it out, but during the test, it EMMC test fails and output the following:
Note: I used the other driver, this was just to show the error which was being output.
Despite that, I did continue with the method and flash the imgs. Then I decided to look inside the files and found out the partition.txt was incorrect, thus I did calculate and created my own using the files from my stock extracted firmware. But still it didn't worked out, thus after I googled, I came across a tutorial which was meant for LG G3 unbrick using BoardDiag, and it the tutorial, the guy mentioned that use the option erase and then switch it back to Read/Write, and it should fix the error, but it didn't worked out. and the EMMC partition was completely wiped. then check I checked the rawprogram xml in BoardDiag, It looked like it was incorrect, but I wasn't able to edit it properly, so I gave up on this one.
Then the next day, I googled and came across a tutorial from XDA that shows how to fix an LG L7 P715, so I started following the tutorial as from Step 4, but I was unable to continue as the application was search for the Sahara XML, I wasn't able to get my hands on. After some research I found out the provided files wasn't compatible with my device, thus I finally got my hands on some of the files.
1. MPRG8x10.hex (It is the eMMC programmer file to help download the bootloader into eMMC, and I guess it can be used with all Snapdragon 200 MSM8x10 processor. And I've already got this file somehow).
2. 8x10_msimage.mbn (It is the bootloader image file and specific to the phone. I wasn't able to get the file, because I wasn't able to determine the proper bootloader file for the device from the stock firmware.)
3. Raw XML and Patch XML files (These XML files contain the partition details of phone. And I don't have these two. And I was unable to even a edit the files properly as I wasn't able to exactly understand what was going on, so I gave up on this one.).
Then the next day, I tried again using the SD Card method, but once the SD Card is inserted, the device shows the Demi-God Crash error. Thus when I hooked it up to my computer, I saw the EMMC as a removable partition but I was unable to format it, thus I tried writing the partition table (PrimaryGPT) to the device, but no success. Then I download a full dump for the D325 and wrote it to the EMMC, but still fails to boot as the EMMC is clean once I unplug it and plug it again. Thus when I hooked up the SD Card through a card reader to my device, it shows that the SD Card was partitioned as a regular emmc for a phone to boot, I did try to to backup the partition table and then restore it to the EMMC, but still in vain. Then I tried to write the files manually using linux to partitions manually, including the system partition, which I did merge the different bin files to one img and then flash it, I took about 10min to fully write it. But still it didn't boot. Well I'm stuck here (am currently trying to write the full dump to the SD card and try to boot of it, if it does boot). I hope that someone will be able to help me out to fix this issue. Thanks in Advance!
Hello,
As a Senior Member you should be able to navigate the site and find the answers you are looking for.
XDA Assist is to help new members navigate the site.
Please have a look at the 2 sticky threads at the top of XDA Assist if you have any further questions.
Thread closed.
Thanks,
Sloth
Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
kevriveroc said:
Good night everyone.
I have a Nokia 2.2 TA-1188 to which I recently unlocked the bootloader successfully using the method from this guide:
[GUIDE] How to unlock the bootloader for Nokia 2.2
To content farms: DO NOT COPY AND PASTE THE ENTIRE GUIDE! Now the last piece of puzzle of Nokia x.2 series bootloader unlock line has been completed, thanks to the help of a member called Woke_World. After I read his procedure, I decided to...
forum.xda-developers.com
However, when I tried to flash the latest TWRP (v3.6.2) over stock Android 9 (the ROM used to unlock the bootloader from the guide above) following the exact procedure shown on TWRP's site, using both the recovery IMG and the vbmeta linked within the instructions (the vbmeta apparently comes direct from Google), the phone became bricked and totally unresponsive apart from periodic short vibrations whenever I try to boot in any way (system, fastboot, recovery, etc.).
What can I do to try revive it?
Click to expand...
Click to collapse
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
djinc91 said:
If you can connect to the phone with SP Flash Tool you should be able to flash it with Android 9 again and start over. Just download though, not format + download, because then you'll need to restore your IMEI and serial numbers.
Click to expand...
Click to collapse
I have just tried to do so, but to to no avail. I keep getting the following error message:
STATUS_STOR_LIFE_EXHAUST (0xC003001D)
The storage on your device has reached end of life, please change to use new device to do operations
I used the DA bundled with SP Flash Tool and drivers linked in one of the folders, apparently MTK ones.
Here's a screenshot of the error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was able to download the firmware again after unchecking the Storage Life Cycle Check box within SP Flash Tool's options, and the phone is now up and running, no troubles up so far.
Thank you very much for your help djinc91!
Uhm Ur phones storage chip is literally dying
Thats emmc for u
areallydumbperson said:
Uhm Ur phones storage chip is literally dying
Thats emmc for u
Click to expand...
Click to collapse
I've had no trouble with my storage during all the years I've owned this phone. Never experienced slowdown, errors, loss of data, etc, not now, not before.
Even so, this is just a backup/2nd device used for nothing important, so it doesn't bother or worry me in the slightest. I'll just keep it using it as is until it dies or I just can't make it usable anymore.
Thank you for your heads up, though.
Update:
My phone was not recognized by the computer since the usb flex was broken, the data lines did not work, but the charging lines did.
Watch this video for a solution:
Hello!.
Can someone who understands the subject explain to me how the startup architecture of an android device works at the hardware/software level.
I recently completely lost control of my android device, after some problems flashing a corrupt rom. I don't understand if I deleted any important files or what happened, but my device is not detected by any computer, leaving me unable to use adb or any USB flash tool. I also don't know if this problem has to do with the usb card, since this, if it sends power, the device charges, and is detected by the computer as a generic usb.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hard brick / Device not found. Sony M4 Aqua E2303.
I installed a faulty ROM which caused my phone to not be detected by my computer (it shows up as an unknown device). I want to flash the original rom, but there is no way, because when I do it with the flashtool and it asks me to connect the...
forum.xda-developers.com
Gretings!
RenzoMag said:
Hello!.
Can someone who understands the subject explain to me how the startup architecture of an android device works at the hardware/software level.
I recently completely lost control of my android device, after some problems flashing a corrupt rom. I don't understand if I deleted any important files or what happened, but my device is not detected by any computer, leaving me unable to use adb or any USB flash tool. I also don't know if this problem has to do with the usb card, since this, if it sends power, the device charges, and is detected by the computer as a generic usb.
Hard brick / Device not found. Sony M4 Aqua E2303.
I installed a faulty ROM which caused my phone to not be detected by my computer (it shows up as an unknown device). I want to flash the original rom, but there is no way, because when I do it with the flashtool and it asks me to connect the...
forum.xda-developers.com
Gretings!
Click to expand...
Click to collapse
The "device descriptor request:failed) issue is more than likely not a problem with your device, it is more commonly a problem with your PC or your device drivers that are installed on your PC.
If you do a Google search for:
"Unknown USB device(device descriptor request: failed)"
It should find links to guides and videos with troubleshooting steps to solve this issue. Try the methods they describe, sometimes you have to repeat the solution several times before the issue is corrected.
I tried a lot of things and i dont know what to do next ,but MI FLASH dose not need an autorized account but displays 2 erors:
First:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Second:
If someone knows how to solve it, please reply.
Try to rename your folders into short names. I think I had the same issue yesterday, after renaming it was fine.
IkarusVC said:
Try to rename your folders into short names. I think I had the same issue yesterday, after renaming it was fine.
Click to expand...
Click to collapse
No ,its not the problem.
It failed again after 90sec.
Antonio7489 said:
No ,its not the problem.
It failed again after 90sec.
Click to expand...
Click to collapse
Hi, Put the files inside C:\ not on your desktop and try
TempAccount10001 said:
Hi, Put the files inside C:\ not on your desktop and try
Click to expand...
Click to collapse
I get the same error after 90sec,its from somthing related to sahara_rx_data:237
try redownloading your rom, maybe it' corrupted. then flash again
icodix said:
try redownloading your rom, maybe it' corrupted. then flash again
Click to expand...
Click to collapse
Trust me i redownloaded the fastboot firmware around 3 Times ,its not about that.
Normally it shows the Device ID (it has 8 letters, like in Fastboot).
How do you connect your device on which OS.
SmartJuwel said:
Normally it shows the Device ID (it has 8 letters, like in Fastboot).
How do you connect your device on which OS.
Click to expand...
Click to collapse
This is if u don't have a driver
Antonio7489 said:
I get the same error after 90sec,its from somthing related to sahara_rx_data:237
Click to expand...
Click to collapse
Try getting latest mi flash tool
Its on EDL mode .. this is why no id only COM
I have a bricked one too, trying to solve it
In unloock tool :
it said snapdragon 855(sm8150) when reading the SoC
But the firmware only have firehose sm7150
Is this an issue? Or it already included in sm7150?
Need someone help to unbrick the phone
Tried multible firmwares with different versions
EFT pro, Unlocktool, Xiaome tool, pro all these tools and even Qifil
Is it from SoC? Because its auto EDL mode without test point
Help plz
SoJustMe said:
Its on EDL mode .. this is why no id only COM
I have a bricked one too, trying to solve it
In unloock tool :
it said snapdragon 855(sm8150) when reading the SoC
But the firmware only have firehose sm7150
Is this an issue? Or it already included in sm7150?
Need someone help to unbrick the phone
Tried multible firmwares with different versions
EFT pro, Unlocktool, Xiaome tool, pro all these tools and even Qifil
Is it from SoC? Because its auto EDL mode without test point
Help plz
Click to expand...
Click to collapse
Friend it's nothing to be done , send it to an authorized Xiaomi repair center and claim warranty while you have it.The phone can't exit edl mode without access codes, I repaired mine at a repair center authorized by Xiaomi , they replaced the motherboard (it taked around week) and then they send it back quickly.Trust me it's the only safe way(if you didn't open the back of the phone,then there is no warranty to be claimed) , you just need to tell them that the phone freezed,turned itself off and is not responding to power button,if you can drain it's battery so nothing is to be seen(any possible logs),good luck with repairing the phone.
Hey everyone,
A few days ago I was taking the battery out of my phone, to get to the SD card, without shutting it down properly first, which presumably broke some component in my system. When I booted the phone back up again, I was noticing some weird behavior: I am able to use the phone normally, but after about a minute, the whole phone freezes and I am not able to interact (touch or power / volume buttons) with it in any way anymore. After the phone has been frozen for about a minute, it will crash and restart and I will be thrown back into the boot sequence.
Luckily I discovered, that the Safe Mode worked fine and none of these problems ever occurred there. I am able to make phone calls and access the internet via the default browser just fine there.
When using adb to get the log below, I noticed I was still able to use the shell (cd, ls, etc.) after the display froze, so I assume only some of the system is having problems.
Phone: Fairphone 3
OS: Lineage 20.0 with MindTheGapps. I updated to 20.0 a few weeks ago and already tried OTA updating to the newest version after the phone started misbehaving, without any luck.
My phone is/was rooted using magisk, but I already uninstalled it trying to prevent the crash.
Below I added the output of adb logcat, which I ran as soon as the connection to the PC was established and until I saw the bool logo again.
One thing I noticed was the message
[ 06-20 00:07:09.165 1179: 9685 E/qdmetadata ]
Unknown paramType 4096
which was issued 4000+ times during the duration the log was taken. I don't know about the fatality of this error, but digging in the lineage Source-Code I think it relates to the display.
I already thought about resetting the phone to factory default, but I have a lot of stuff on there and would prefer to not do so, ignoring the fact that this might not even solve the problem, depending on how deep it lies.
Thanks in advance,
~Okaghana
That's what ChatGPT says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I already uninstalled all apps that I recently installed and even some older ones I didn't need.
One more thing I noticed: When my phone has low battery power (below 10%) it takes longer to freeze. I suspect a background activity is the culprit and when the phone is low on battery the power saver increases the time until it is executed
Okaghana said:
I already uninstalled all apps that I recently installed and even some older ones I didn't need.
One more thing I noticed: When my phone has low battery power (below 10%) it takes longer to freeze. I suspect a background activity is the culprit and when the phone is low on battery the power saver increases the time until it is executed
Click to expand...
Click to collapse
Do you have custom recovery ? To reflash the system, I think the update crashed the system.
Originally I had the Recovery that came with LineageOS, but I patched it for Magisk. I flashed the original, unmodified LineageOS Recovery, but that did not fix it :/
Okaghana said:
Originally I had the Recovery that came with LineageOS, but I patched it for Magisk. I flashed the original, unmodified LineageOS Recovery, but that did not fix it :/
Click to expand...
Click to collapse
What was your original os of the phone
The original OS is Fairphone OS
Okaghana said:
The original OS is Fairphone OS
Click to expand...
Click to collapse
Well my friend it's time for you try to trick your phone with firmware upgrade and return to the original os I suppose, but you said you have files one the phone am not sure about that but you can still flash twrp to backup, tell me what you think