I need help.
The problem?My phone is bricked AF.
Where it started:So, a few days ago I was flashing custom ROMS on my Redmi 9C, at this point everything was good, although I did brick the phone twice, I was able to get it back up and running again using MTK Bypass and SP Flash tool.
You see, 2 days ago I stupidly it was a good idea to flash a custom ROM (Arrow OS) on top of another one (DotOS) ~I'm not a noob, I KNEW this probably wasn't going to work~. I thought it would work since it's still using the same base but shortly after flashing when I restarted my phone there was nothing, no boot logo, no sound, no vibration, nothing.
I couldn't boot to fastboot or anything, it wouldn't respond to ANY input.
At this point I already knew well how to fix the issue but this time it didn't work at all.
The first attempt kinda worked, I was able to bypass auth and flash but after like 2 seconds the flash tool stopped, and I got a STATUS_EXT_RAM_EXCEPTION error and after that I tried to reflash. It did get detected by the bypass tool a few times but after that every time I plug my phone into my pc, I get this:
{
"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"
}
and I see this in device manager:
Libusb won't even detect it.
I tried driver after driver, I switched the cable, I tried a different computer, I waited a day, I read thread after thread, installed python, tried tool after tool, but to no avail.
I tried all sorts of button combinations but the only one that does anything is vol+ and pwr but that just makes it disconnect and reconnect to my pc with the same results.
I watched a bunch of videos about it and tried every method but still, no luck. I am confused where they say remove the battery because some do and some don't, but I can't really do that in my current position anyway...
I know there are MANY similar threads on this, but I haven't been able to find anything to help me in this situation.
I've tried all sorts of solutions but now I just don't know any more.
Please. Help. Would really appreciate it.
I had a similar brick yesterday, when I tried to use mtkclient but it only got halfway. As far as I understand, the system was actually on, but it got stuck in a state where it wouldn't respond to anything.
What fixed it was power cycling the device by disassembling it, and disconnecting and reconnecting the battery (search for battery replacement videos). The idea is from this comment by bkerler, the author of mtkclient. I guess my warranty really is void now.
(Another thing I considered was power cycling it by waiting for the battery to run out, and then recharging it. But I've no idea if this might have got it into a state where it wouldn't even charge, so I didn't do it.) I'll avoid mtkclient from now on when possible, and prefer to use fastboot or a recovery for flashing.
I am a noob; no guarantee that I'm right about anything (other than that my phone works now), nor that your situation is identical to mine.
Here is solution if you are not noob,
Post in thread 'HARDBRICKED REDMI 9C ANGELICA NO BOOT NO RECOVERY NO FASTBOOT ONLY VIBRATES' https://forum.xda-developers.com/t/...-fastboot-only-vibrates.4494095/post-88308869
Related
{
"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"
}
Okay, firstly, this all started when I flashed the new Sense 7 Insert Coin Rom. My phone would not boot up after having turned off/lost battery.
Here is a list of the problems:
1. Cannot boot into recovery, gives purple loading text and then bootloops again
2. When charging it charges for 5-10 seconds minimum and then bootloops
3. The device has turned on before during these bootloops once before
4. The device could be left charging all night and bootloops all night, no way to power down
5. Upon attempting to power the device on after 12 hours of charging it has no battery charge left
6. Cannot flash a new recovery for some reason (via cmd)
7. Tried flashing TWRP, CWM and PhilZ again, none worked all resulting with the error code 'error: cannot load recovery.img' having put the code 'fastboot flash recovery recovery.img' with no results
8. Device can only boot into bootloader, nothing else.
9. And also, the above CMD error too..
I have been without my phone for 3 days now and having tried all the possible options I knew of this was my last resort.
Hope someone has a solution, thanks
I had a similar issue with my device. Turned out that the flash storage had died.
Took it in to my operator and they replaced it with a refurbished HTC One
Had to pay because the phone had some nicks and scratches.
Mat214 said:
I had a similar issue with my device. Turned out that the flash storage had died.
Took it in to my operator and they replaced it with a refurbished HTC One
Had to pay because the phone had some nicks and scratches.
Click to expand...
Click to collapse
Oh dear... was hoping this wasn't serious. Thanks.
Matthew.One said:
Oh dear... was hoping this wasn't serious. Thanks.
Click to expand...
Click to collapse
not so much a solution, but it sounds to me like your battery is dead dead, as in you need a new battery, if the phone is dyiong pretty much as soon as you unplug it from the charger then it has to be the battery, and as a safety feature, you cant flash anything with a battery that low, which would also explain the flashing error your getting.
I managed to brick my ME375CL in my attempt to root it, it only shows the "Intel Inside" logo when I boot it up.
After much driver install/reinstall and cursing at my computer, I managed to get it to be recognized in Intel Phone Flash Tool.
I've read the instructions on doing custom flashes in blank phone mode for other tablets, but for the life of me, I can't figure out which file is supposed to go in which field.
I would greatly appreciate any insight into this that anyone can provide.
I already have the firmware downloaded.
This is where I am at:
{
"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"
}
This is the list of files I have to work with from the firmware download:
Thanks in advance!!!
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
johnkirchner said:
The link below may be your best bet to reload the system and root it. I would recommend reading the entire thread first.
https://forum.xda-developers.com/memo-pad-7/help/official-rom-att-asus-memo-pad-7-lte-t3554127
Click to expand...
Click to collapse
Thanks for the reply. I've already read through that post and attempted the steps within. The problem is that I followed those steps and they failed, now it can only be recognized as an Intel SoC by my computer, so ADB, fastboot commands and Asus Flash Tool will not work.
The only programs I've gotten to recognize the tablet is Intel's Phone Flash Tool and Flash Tool Lite.
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
johnkirchner said:
If you haven't yet, try using the boot, system and recovery images from the firmware you downloaded in the android section of the flash tool and see what happens.
Click to expand...
Click to collapse
I've tried all kinds of combinations in this software, but it always fails at either the IFWI step or gives me this error:
10/08/17 14:03:09.468 INFO : Port 5/1/1: Rebooting in Provisonning OS (current state = UNKNOWN_STATUS)
10/08/17 14:03:09.468 INFO : Port 5/1/1: Cannot Reboot android device, status is UNKNOWN_STATUS
Based on the reading I've done in other threads, the only way to correct this is through a firmware flash in blankphone mode, but it won't accept any of the IFWI files that I have found for this tablet.
I appreciate you trying to help, but I can't do what you are suggesting when it's not even being detected as an Android device. Fastboot commands will not work because there's nothing on the tablet for ADB to make a connection to.
Here's what happens when I try:
Here is what my tablet is doing:
When it's detected by Intel Phone Flash Tool, it usually has a blank screen. Otherwise, it just shows that Intel logo for about 15 seconds, reboots and then does it again, endlessly.
Oh, I forgot to mention that Asus support was kind enough to offer a repair or replacement for $155, since it's out of warranty. I'm hoping for a much cheaper option.
I have never seen the intel logo on mine? Have you tried booting the tablet in to fastboot mode by shutting it down and then turn it on by holding the volume up button and the power button? If you can get to fastboot mode, you should be able to use adb commands. Unfortunately, i am not familiar with the flash software you are using.
So I bought my sister a oneplus 3t and after 3 days she told me that the phone had died on her and was charging but wasn't booting up. I took the phone off her and tried using OnePlus' recovery to wipe everything hoping that would fix it. It didn't. Now the phone won't boot up at all. It won't even go into a bootloop. No lights, no anything. It's completely dead. Using the msmdownload tool gives a Sahara communication failed error and I've currently tried everything. Any idea about what I can do?
NotAbdShahid said:
So I bought my sister a oneplus 3t and after 3 days she told me that the phone had died on her and was charging but wasn't booting up. I took the phone off her and tried using OnePlus' recovery to wipe everything hoping that would fix it. It didn't. Now the phone won't boot up at all. It won't even go into a bootloop. No lights, no anything. It's completely dead. Using the msmdownload tool gives a Sahara communication failed error and I've currently tried everything. Any idea about what I can do?
Click to expand...
Click to collapse
Please use the search function before posting here. There are plenty of circumstances where the issue you've described has happened.
thes3usa said:
Please use the search function before posting here. There are plenty of circumstances where the issue you've described has happened.
Click to expand...
Click to collapse
Except that I have and I've not found a solution to the sahara communication failed problem. I've tried different computers, usb ports etc. Still gets stuck at Sahara Communication failed.
ashokmor007 said:
Click to expand...
Click to collapse
Thanks but I've tried this and it still gets stuck at the same flippin error.
Download the current adb ... use the original cable ... there was a process done with cmd as well as signing the certificate in win10, have you done these?
[Oneplu 3t] md5 checksum failed:system and recovery failed
My Oneplus 3T(with android 8.0.0) suddenly turn off and it wouldn't boot or other option, i didn't ever rooted, it was new and updated. I tried to go to recovery, tried a hard boot hold the power button for 30s, connected to pc, and giving a charge... it just stayed dead... so i did a find the OnePlus3 Unbrick Tool, did find the phone on the tool and i run... after that it boot in a cycle where appear the 1+ logo and them the md5 checksum with the system and recovery failed
{
"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"
}
it does that loop, and now i can enter fastboot but can do nothing than going to that cycle and power off
phone apear in the device manager as "Qualcomm HS-USB QDLoader 9008(COM3)"
and using the tool again, goes to a error saying "Sahara Communication Failed£ Please try again after power off phone" and already tried what it said..
please help me, what can i do to boot my device?
PS: I dont know how to put images on the thread...
Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"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 mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:
Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!
Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!
Basically i have been trying to root my phone (Redmi 9c) everything was going well until i got to the pathching the boot.img with magisk and got the error
'booting...
FAILED (status read failed (Too many links))'
and after that i was stuck on a boot loop i looked for a guide and i re-flashed (not sure if i'm using the correct terminology. sorry im a noob) the original xiaomi angelica boot.img it fixed the issue but i was still not rooted i went to another guide everything went smoothly until i got to the booting part and...... got the same error i have tried everything, (changing charger, usb port, using windows power shell and normal CMD) and nothing all i get is this:
{
"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"
}
and once again to a boot loop. i have tried re-flashing the factory boot.img and nothing. Im seriously starting to go insane because i cant fix this problem and can't get the phone to boot again or even find something to help me.
thanks to anyone who might help me in advance
Elizabeth_304 said:
Basically i have been trying to root my phone (Redmi 9c) everything was going well until i got to the pathching the boot.img with magisk and got the error
'booting...
FAILED (status read failed (Too many links))'
and after that i was stuck on a boot loop i looked for a guide and i re-flashed (not sure if i'm using the correct terminology. sorry im a noob) the original xiaomi angelica boot.img it fixed the issue but i was still not rooted i went to another guide everything went smoothly until i got to the booting part and...... got the same error i have tried everything, (changing charger, usb port, using windows power shell and normal CMD) and nothing all i get is this:
View attachment 5373903
and once again to a boot loop. i have tried re-flashing the factory boot.img and nothing. Im seriously starting to go insane because i cant fix this problem and can't get the phone to boot again or even find something to help me.
thanks to anyone who might help me in advance
Click to expand...
Click to collapse
Hey has it been sorted out already? Try flashing with fastboot ROM. Also see thread about rooting redmi 9c under guides
You cant boot into recovery from fastboot command, just enter recovery manually by pressing vol+ and power button.