hello everyone
i think i bricked my xiaoxin pad p11 pro 2021 trying to root it
i was able to install TWRP and while i was browsing inside it, i pressed partition B and the tablet went to black
and is completely unresponsive now.
is not turning on, or charging or vibrating or flashing or anything.
i conected it to the pc to see if fastboot was there but it doesnt find the device no matter in what way i try to reboot it
but the usb port still is recognizing a devices plugged in, so i used QFIL and discover than the tablet is in "Download Mode"? i dont really know was that means.
so i tried to flash the stock rom into the tablet in download mode, aparently if i press vol down and power for 20 seconds or so the tablet reboot without giving any signal except for the conexion to the pc, but the flash doesnt work.
i tried QFIL with the proper qualcom drivers, also lenovo download tool and even in the rescue and smart assistant, but like it doesnt include support for this tablet, i tried with similar models and roms but it also fail.
i dont know if it is because is in the wrong partition or why there was a second one but fails every time, even tried with different roms from different links but nothing.
is there a way to flash the tablet or recover the fastboot or anything that stop me from declare it lost forever?
i'll attach the error log from the QFIL if that can help.
thank you for your help and your time.
Related
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
you found any solution i have the same problem ?
:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me
So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.
any luck with a solution? How close to one have you got to...
ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.
Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.
Alcatel 5020t T-Mobile plis help flshe file
please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
chc2918 said:
Hi guys.
I have for a few weeks one Xiaomi Mi3 16GB Snapdragon (WCDMA). Because I thought it was too slow, I flashed another rom by Mirecovery, but I think I used a wrong one because the phone is completely dead! I am not able to get access to the recovery mode or fastboot. The keys don’t work anymore.
This is the rom I flashed: xiaomi.eu_multi_NX403A_4.7.11_jb-4.2. downloaded on miuiandroid.com.[later I heard this is a rom for zte z5s mini, so really wrong one ]
After installing of MiPhone2.11.6, the first time when I connected the phone with the pc, the red led kept lighting on and the driver wasn't installed, but the phone was recognized by MiFlash(com20, i think): flashing did't work because there wasn't a communication with the port. After that I tried to reinstall MiPhone and afther some attempts, when I connected the phone with the pc, the red led kept lighting on for a few seconds and the driver was installed. But the phone wasn't anymore recognized by Miphone, so again no possibility to flash it.
I’m really desperate because i used the phone just for 2 weeks.
I would really appreciate if somebody would come with a good solution.
Thank you.
Click to expand...
Click to collapse
if you have no access to recovery or fastboot, the phone is finished
one of the worst things you can do to a device is flash the wrong software, as you see.
Hello,
I have a new Lenovo A606, that came with a strange ROM (IMEI not recognized, some weird WIFI setup) from 2014. I was able to set it up and correct the problems (thanks to google), but I still had some language issues (the Lenovo Apps including dialer, contacts, sms, etc… were English only). I was able to root it fine, and no working problem.
I decided to install a clean stock ROM, ROW: the A606_USR_S036_1502271022_V3_MP_ROW that is more recent and fully supports multilanguage.
I took a PC with Windows XP, and installed the latest SP Flash Tool, following a tutorial.
I was able to install android adb drivers and the MTK driver from the ROM image. The phone was showing in the devices, then was disappearing, then showing again… I had an error, but then I tried again with the option to update the firmware, and the Flash Tool reached the end and said it flashed succesfully.
Problem: after that, the phone was totally bricked. It would not start at all. When I plug it on the PC, it shows sporadically a device called "VENDOR 0E8D - communication" that disappears very quickly. I cannot flash it again. I just lost my brand new phone…
I tried with SP Flash Tool, and Flash SPMDT, with different ROMs, CN only, ROW, different versions… But nothing. It always says that Flash failed. Even when the phone is not plugged, I have an error with Flash SPMDT, with all ROMs, saying that (1)COM ports number is repetitive or invalid, or (2) Brom and preloader have the same comport number! and it asks me to modify them in INI file or scan again. Of course, scan fails, when I plug the phone pressing vol up + vol down (only way to make the phone recognized by the computer without a battery), the progress goes to 100% then either stays stuck there, or says it failed. SP Flash Tools gives this error: 'BROM ERROR s_ft_enable_dram_fail (4032)'
I tried several drivers, to clean drivers with usbdview, I tried several versions of SP Flash Tools… I don't know what to do anymore. I hope that Lenovo has a warranty and that they could flash it back to normal.
I don't know if it is a problem accessing the META mode on the phone, or bad roms… I tried on one computer with XP, and another with Windows 8.1, and the problem is the same.
ANY HELP would be appreciated, thank you!
Hi, thank you for using XDA Assist. It sounds like you've tried everything possible. Since it sporadically shows up on your pc try a different USB cable. If that doesn't work then I think it is bricked and you'll have to check with whomever you purchased the device from to see if they can fix it.
Thread closed.
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
It doesn't turn on, can't be hard-reset, can't go to recovery/fastboot, only EDL mode via test points. Last time (April 2019) it also happened overnight, but I was able to restore it to proper function by EDL flashing it using QFIL and a modified programmer (prog_emmc_firehose_Sdm660_ddr.mbn). The rom I flashed back then was the most recent at the time, Redmi Note 6 Pro Global V10.3.2.0.
This time was a bit different in that I was actually able to hard-reset it at first (it vibrated and seemed to boot), but it then got stuck on the mi-logo during startup. I wasn't able to get it into recovery, but the fastboot screen came on ok. However, the phone didn't register on the pc and I wasn't able to actually send any fastboot commands to the phone, nor flash roms. I don't think fastboot was actually working which might be pointing to chip issues... Unfortunately...
After a few attempts at hard-resetting and failing recovery, I think the battery actually ran flat. Now it is dead-dead. Doesn't react at all, doesn't do anything, just like back in April last year. When I plug it in to my pc it delays for about 10 seconds and then shows up as if it's in EDL mode (Qualcomm HS-USB QDLoader 9008) but it's not really flashable - it doesn't react to QFIL correctly.
I then pulled the phone apart, shorted the EDL points and got it into 9008 mode immediately after plugging in the usb cable, no 10 sec delay doing it this way. However, when trying to flash the phone now it fails and reports a generic 'Firehose FHLoader error'... Please see log attached in this google drive link: drive.google[dot]com/file/d/1nj_0f95qLnLHqIgTEODmilY9ObmAkowz/view
Apologies for the link - I don't have 10 posts yet...
The most recent miui rom for the phone now is "tulip_global_images_V11.0.4.0.PEKMIXM_20200514.0000.00_9.0_global" and that's the one I primarily tried flashing. I also tried the one I had success with last year (fearing though it might re-brick due to the roll-back protection) but that didn't work either, same error. I also tried flashing using different USB cables, all high quality, but the error remains. I also tried it using a laptop, just to rule out windows issues. I've also tried the tips for resolving QFIL errors mentioned on the hovatek forum: forum.hovatek[dot]com/thread-30141.html but with no luck there either.
Have you guys got any ideas how I might proceed? Any tips I could try?
I am kind of resigned to this perhaps being a hardware issue, perhaps this particular chip has failed and that is why not even EDL mode is working properly. But I just wanted to ask the community if you had any ideas. If not, then it's not an expensive phone. However, I would love fixing it if I could, my wife loves it...
I suggest to first short the pins then open the flash tool and try to flash the factory rom. The programmer file will be inside the extracted rom directory, select that and proceed. If it does not work try installing Qualcomm driver and retry .
Talix said:
Hey guys
I'll just let you know first up, this is the second time I've had this issue with this particular phone being hard-bricked, but this time I can't seem to fix it.
Click to expand...
Click to collapse
I'm sorry for re-opening an old thread, but I'm in a really similar situation.
My Redmi self-bricked, and I don't have any ideas since I have already tried a flash in ELD mode but the Flash Tool says that it's not able to receive the hello packet from the phone.
Have you been able to solve the issue in some ways?
Ps. Here's my post, in case you need further informations
Hi, I accidentally bricked my phone flashing the wrong image.
Now i can't turn off the phone, cant access to recovery or fastboot. (device doesn't respond when i click any button).
'Poco' logo is in loop. Anyone knows a way to install a ROM? Any way to access fastboot in this situation?
Try pressing the buttons for a long time. It resulted for me to get to recovery mode, but no to download mode. Sometimes it works.
I bought a poco x4 gt like that too, hoping to get it fixed, I believe the way to get it is via EDL mode and miFlas, but for now miflash still doesn't recognize the image of the poco x4 gt. I hope that in some future update I will recognize it.
i have same problem
Same problem here
did anyone was able to find a fix? or at least locate the test points for EDL?
mtk devices use a different way to access edl mode. in my case I access the edl mode, the computer recognizes it, the software recognizes it, but when running it says that SPflash still does not work with the scartter version of the rom that I downloaded
how did you manage to boot into edl mode? i tried several hw key combinations but it gives me "preloader handshake failed" or several BROM error.
i think my scatterfile seems ok. its just the brom/edl connection.
when you turn it on with the volume button less pressed and it connects quickly to the pc install the MTK driver and then run the python where it will read the brom
Mine already fixed
butaw1 said:
Mine already fixed
Click to expand...
Click to collapse
what did you do?
if any one want to fix his poco x4 gt bootloop only. can't reach fastboot or recovery. at first you need auth to bypass dim 8100 security. i found a person on github name Rafon he fixed my phone and it's working perfectly right now. his username on telegram is @Rafon24
same issue
the only way of fixing is through an authorized xiaomi account sadly
i however found a way to turn it off when nothing works:
press all 3 buttons (volume up, down and power for like 20 seconds)
and then it will turn off